ORA-27125, SGA: Realm creation failed (hugepages)

— pełny błąd:

2022-05-02T11:50:30.341692+02:00
Adjusting the default value of parameter parallel_max_servers
from 880 to 348 due to the value of parameter processes (500)
Starting ORACLE instance (normal) (OS id: 231844)
2022-05-02T11:50:30.362069+02:00
Sys-V shared memory will be used for creating SGA
2022-05-02T11:50:30.365273+02:00
Dump of system resources acquired for SHARED GLOBAL AREA (SGA)

2022-05-02T11:50:30.365469+02:00
Domain name: system.slice/oracle-ohasd.service
2022-05-02T11:50:30.365587+02:00
Per process system memlock (soft) limit = UNLIMITED
2022-05-02T11:50:30.365658+02:00
Expected per process system memlock (soft) limit to lock
instance MAX SHARED GLOBAL AREA (SGA) into memory: 3192M
2022-05-02T11:50:30.365765+02:00
Available system pagesizes:
4K, 2048K
2022-05-02T11:50:30.365868+02:00
Supported system pagesize(s):
2022-05-02T11:50:30.365920+02:00
PAGESIZE AVAILABLE_PAGES EXPECTED_PAGES ALLOCATED_PAGES ERROR(s)
2022-05-02T11:50:30.366069+02:00
2048K 16792 1596 1109 ORA-27125
2022-05-02T11:50:30.366123+02:00
Reason for not supporting certain system pagesizes:
2022-05-02T11:50:30.366193+02:00
4K – Large pagesizes only
2022-05-02T11:50:30.366275+02:00
SGA: Realm creation failed

–odpalamy skrypt z Doc.ID 401749.1 (najlepiej aby wszystkie instancje były odpalone):

https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&sourceId=361323.1&id=401749.1

[oracle@dm02 ~]$ vi hugepages_settings.sh
[oracle@dm02 ~]$ chmod +x hugepages_settings.sh
[oracle@dm02 ~]$ ./hugepages_settings.sh
Recommended setting: vm.nr_hugepages =


RMAN-06094: datafile 1 must be restored

Podczas odtwarzania DB do innej lokalizacji (powiedzie się), ale przy próbie przesunięcia o kilka scn-ów w 12.1.0.2 może być błąd:

Starting recover at 2022-04-28 10:25:30
released channel: ch1
released channel: ch2
RMAN-00571: ====================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
RMAN-00571: ====================================
RMAN-03002: failure of recover command at 04/28/2022 10:25:31
RMAN-06094: datafile 1 must be restored


DB 19 – recovery catalog

Przygotowanie home-a, rozpakowanie instalek, patchy itp. (użyszkodnik: oracle)

mkdir -p /u01/app/oracle/product/19/dbhome_1
unzip /u01/install/V982063-01-19.3_DB.zip -d /u01/app/oracle/product/19/dbhome_1/
mkdir -p /u01/app/oracle/product/19/dbhome_1/patch/RU
unzip /u01/install/p33192793_190000_Linux-x86-64_patch_RU_DB_19.13.zip -d /u01/app/oracle/product/19/dbhome_1/patch/RU
rm -rf /u01/app/oracle/product/19/dbhome_1/OPatch/*
unzip /u01/install/p6880880_210000_Linux-x86-64 -d /u01/app/oracle/product/19/dbhome_1/

Instalacja (aplikowanie RU) i tworzenie DB:

cd /u01/app/oracle/product/19/dbhome_1
./runInstaller -applyRU patch/RU/33192793
./dbca


Zabbix: Locale for language „en_US” is not found on the web server. Tried to set: en_US, en_US.utf8

Po instalacji zabbixa na czystym debianie 11 możemy trafić na:

Locale for language „en_US” is not found on the web server. Tried to set: en_US, en_US.utf8

Sprawdzamy jakie mamy locale:

root@Zabbix:~# locale -a
C
C.UTF-8
POSIX

edytujemy plik /etc/locale.gen i odhashujemy np. en_US.UTF-8

root@Zabbix:~# vi /etc/locale.gen
en_US.UTF-8 UTF-8

odpalamy locale-gen i reboot zabbixa na bogato


EBS clone DB (adcfgclone), RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack, ouicli.pl INSTE8_APPLY 1

Podczas clona DB w EBS:

| 0% completed RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack
ERROR while running Apply…
Fri Apr 8 11:59:58 2022
ERROR: Failed to execute /12.1/appsutil/clone/bin/adclone.pl
Please check logfile.

log:

WARNING: [AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution. Errors are grouped by directory and phase.
The report format is:

[APPLY PHASE]
AutoConfig could not successfully execute the following scripts:
Directory: /12.1/perl/bin/perl -I /12.1/perl/lib/5.14.4 -I /12.1/perl/lib/site_perl/5.14.4 -I /12.1/appsutil/perl /12.1/appsutil/clone
ouicli.pl INSTE8_APPLY 1

za wiele nam to nie mówi dlatego sprawdzamy:


ERROR: Not enough file system free space in filesystem '/’

— sprawdzamy co chcemy rozszerzyć

[root@dm01dbadm01 ~]# df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VGExaDb-LVDbSys1 30G 25G 3.7G 87% /

[root@dm01dbadm01 ~]# lvs | grep LVDbSys
LVDbSys1 VGExaDb -wi-ao—- 30.00g
LVDbSys2 VGExaDb -wi-a—– 30.00g

— ile mamy miejsca dostępnego

[root@dm01dbadm01 ~]# vgdisplay VGExaDb -s
„VGExaDb” 1.63 TiB [285.00 GiB used / <1.36 TiB free]

— dorzucamy 20G

lvextend -L +20G /dev/VGE


ORA-00600: internal error code, arguments: [krccacp_badfile], (CTWR)), summary=[abnormal instance termination].

błąd:

Fri Jan 28 14:13:11 2022
ERROR: Unable to normalize symbol name for the following short stack (at offset 204):

ORA-00600: internal error code, arguments: [krccacp_badfile], [6964816530811], [6956618400402], [], [], [], [], [], [], [], [], []
Incident details in: /u01/diag/rdbms/baza/baza/incident/incdir_32483/baza_ctwr_14549066_i32483.trc

Fri Jan 28 14:13:13 2022
Dumping diagnostic data in directory=[cdmp_20220128141313], requested by (instance=1, osid=14549066 (CTWR)), summary=[incident=32483].

Fri Jan 28 14:13:25 2022
Errors in file /u01/diag/rdbms/baza/baza/trace/baza_ctwr_14549066.trc:
ORA-00600: internal error code, arguments: [krccacp_badfile], [6964816530811], [6956618400402], [], [], [], [], [], [], [], [], []
CTWR (ospid: 14549066): terminating the instance due to error 487
Fri Jan 28 14:13:25 2022
System state dump requested by (instance=1, osid=14549066 (CTWR)), summary=[abnormal instance termination].
System State dumped to trace file /u01/diag/rdbms/baza/baza/trace/baza_diag_22282266.trc
Dumping diagnostic data in directory=[cdmp_20220128141325], requested by (instance=1, osid=14549066 (CTWR)), summary=[abnormal instance termination].
Instance terminated by CTWR, pid = 14549066

W przypadku, gdy odtwarzamy bazę na tej samej maszynie jako kolejną i pomimo tego, że mamy zmieniony dbid, nazwe itp. jedna baza w danym czasie może być dostępna, bo mamy włączony block change tracking (odnosi się do tego samego pliku), sprawdzamy na 2ch bazach: