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:


[FAIL] *** dm02dbadm01: Stale map files found in /etc/oracle/maps. You may need to remove the stale map files to avoid the cluster start up issues – Refer the confluence page for more details

— sprawdzamy kiedy byl ostatni boot crs-a (na wszystkich nodach)

cat /u01/app/grid/diag/crs/dm02dbadm0*/crs/trace/alert.log | grep 'CRS-1301′ | tail -n 1 | awk '{print $1,$2,$3}’

— szukamy plików z ostatnim accessem wczesniejszym niz data wyzej czyli boot-a crs-a (mozna find z atime, albo stat)

[root@dm02dbadm01 maps]# ls -latr –time-style=long /etc/oracle/maps/
total 44
-rwxrw—- 1 grid oinstall 0 2020-10-20 19:28 gipcds_gipc_diag_b026c96e3249ff41ff85063dfaaa7e0e_dm02dbadm01_lock
-rw-r—– 1 grid oinstall 66304 2020-10-21 06:14 gipcds_gipc_diag_b026c96e3249ff41ff85063dfaaa7e0e_dm02dbadm01-0000000000
-rwxrw—- 1 grid oinstall 0 2021-01-29 00:25 gipcDS_dm02dbadm01_gipcd_b026c96e3249ff41ff8


[FAIL] *** dm02dbadm01: HugePages does not match value in sysctl.conf. This may prevent system boot. (found: 46581, sysctl.conf: 46077)

— sprawdzamy jak to wygląda:

[user@dm02dbadm01 ~]$ cat /etc/sysctl.conf | grep -A1 -B1 vm.nr_hugepages
##### End: Generated by Oracle Exadata ipconf
#vm.nr_hugepages=13827
vm.nr_hugepages=46077
##### BEGIN DO NOT REMOVE Added by Oracle Exadata
[user@dm02dbadm01 ~]$ grep Huge /proc/meminfo
AnonHugePages: 0 kB
ShmemHugePages: 0 kB
HugePages_Total: 46581
HugePages_Free: 20272
HugePages_Rsvd: 11160
HugePages_Surp: 0
Hugepagesize: 2048 kB

— w err/zaleceniu jak i w pliku mamy poprawną wartość czyli: 46077, ale w pamieci jest wartość większa (gdy zmieniamy na wartość mniejszą i HugePages_Free zje całe, to bezpieczniej jest polożyc crs-a)

[root@dm02dbadm01 ~]# sysctl -p

— sprawdzamy


SRL log 1 needs clearing because log has not been created

Po aplikowaniu incrementala (DG move forward: https://ora-600.com/2021/03/err-replikacji-danych-data-guard-move-forward-czyli-aplikowanie-intrementala/) możemy trafić na:

SRL log 1 needs clearing because log has not been created
SRL log 2 needs clearing because log has not been created
SRL log 3 needs clearing because log has not been created
SRL log 4 needs clearing because log has not been created

Zatrzymujemy aplikowanie archow, czyścimy grupy logów i odpalamy:

alter database recover managed standby database cancel;
alter database clear logfile group 1;
alter database clear logfile group 2;
alter database clear logfile group 3;