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;


DLL – brak biblioteki (gdzie ją wcisnąć)

Jeśli brakuje jakiejś dll-ki tak jak tu orannzsbb12.dll i nie wiemy gdzie ją wcisnąć, to odpalamy Process Monitor (@sysinternals) i od razu widać gdzie powinna być (patrz screen):

16:53:27,6562347 impdp.exe 4048 CreateFile C:\Windows\System32\orannzsbb12.dll NAME NOT FOUND Desired Access: Read Attributes, Dispositi


ORA-29701: unable to connect to Cluster Synchronization Service, Error 29701

Pacjent: Grid 19.13, DB 12.2.0.1, OL 7.9 – NODE2 łapie freeza po starcie i trzeba pocisnąć go z palca (po błędach związanych z interconnectem w logu CRS-a)

— w alercie DB NODE1

2021-11-04T14:26:11.977078+01:00
JIT: pid 44720 requesting full stop
2021-11-04T14:26:18.243731+01:00
JIT: pid 44720 requesting full stop
2021-11-04T14:33:53.984937+01:00
IPC Send timeout detected. Sender: ospid 20158 [oracle@NODE1 (LCK0)]
Receiver: inst 2 binc 16 ospid 18523
2021-11-04T14:33:53.994876+01:00
Communications reconfiguration: instance_number 2 by ospid 20158
2021-11-04T14:34:42.795807+01:00
Detected an inconsistent instance membership by instance 1
Evicting instance 2 from cluster
Waiting for instances to leave: 2
2021-11-04T14:34:42.950298+01:00
IPC Send timeout to 2.1 inc 20 for msg type 65521 from opid 24
2021-11-04T14:34:42.950358+01:00
IPC Send timeout to 2.1 inc 20 for msg type 65521 from opid 24

— a w logu CRS-a NODE2 (na NODE1 są jedynie informacje o problemach z NODE2 bez countdownu):

2021-11-04 14:37:21.717 [OCSSD(10029)]CRS-7503: The Oracle Grid Infrastructure process ocssd observed communication issues between node NODE2 and node NODE1, interface list of local node NODE2 is 172.30.1.2:20313, interface list of remote node NODE1 is 172.30.1.1:64128.

2021-11-04 14:37:27.240 [OCSSD(10029)]CRS-1612: Network communication with node NODE1 (1) has been missing for 50% of the timeout interval. If this persists, removal of this no


ORA-02062: distributed recovery received DBID xxx, expected xxy – wycofanie transakcji

błąd:

Errors in file /u01/diag/rdbms/baza/baza/trace/baza_reco_20054068.trc:
ORA-02062: distributed recovery received DBID xxx, expected xxy

— sprawdzenie oczekujących transakcji

SELECT LOCAL_TRAN_ID, GLOBAL_TRAN_ID, STATE, MIXED, COMMIT# FROM DBA_2PC_PENDING;

— jezeli status prepaired to wycofujemy, albo commitujemy (LOCAL_TRAN_ID):

ROLLBACK FORCE '107.16.2563092′;
COMMIT FORCE '107.16.2563092′;

— albo:

DELETE FROM SYS.PENDING_TRANS$ WHE


Suspending MMON slave action kewrmafsa_ for 82800 seconds

Suspending MMON slave action kewrmafsa_ for 82800 seconds

— ORA pod większym obciążeniem stwierdził, że MMON jest mniej istotny i go uspił
— jeżeli potrzebujemy na teraz SNAP-a (AWR-a) to wymuszamy:

EXEC DBMS_WORKLOAD_REPOSITORY.create_snapshot;

— sprawdzenie snapow:

SELECT * FROM (SELECT instance_number, startup_time, begin_interval


clnt_create: RPC: Port mapper failure – Unable to receive: errno 113 (No route to host)

# edytujemy i dorzucamy po stronie serva:
vi /etc/sysconfig/nfs
MOUNTD_PORT=”888″
STATD_PORT=”889″
RQUOTAD_PORT=”890″
LOCKD_TCPPORT=”891″
LOCKD_UDPPORT=”891″

# FW

iptables -I INPUT -m state –state NEW -p tcp –dport 888 -j ACCEPT
iptables -I INPUT -m state –state NEW -p udp –dport 888 -j ACCEPT
iptables -I INPUT -m state –state NEW -p tcp –dport 889 -j ACCEPT
iptables -I INPUT -m state –state NEW -p udp –dport 889 -j ACCEPT
iptables -I INPUT -m state –state NEW -p tcp –dport 891 -j ACCEPT
iptables -I INPUT -m state –state NEW -p udp –dport 891 -j ACCEPT
iptables -I INPUT -m state –state NEW -p tcp –dpo


Drop private dblink from sys

— user: sys

select db_link from dba_db_links where OWNER=’USERname’;
dblink_name

— tworzymy procedurkę:

CREATE OR REPLACE PROCEDURE USERname.drop_dblink AS
BEGIN
EXECUTE IMMEDIATE 'drop database link db


ORA-29024: Certificate validation failure (UTL_HTTP – HTTPS)

Podczas pobrania adresu „https://…” pojawia się błąd:

select UTL_HTTP.request(’https://…’) from dual
*
Error at line 1
ORA-29273: HTTP request failed
ORA-06512: at „SYS.UTL_HTTP”, line 1530
ORA-29024: Certificate validation failure
ORA-06512: at „SYS.UTL_HTTP”, line 380
ORA-06512: at „SYS.UTL_HTTP”, line 1470
ORA-06512: at line 1

tworzymy wallet-a:

mkdir -p /u01/app/oracle/product/11.2.0.4/dbhome_1/wallet
orapki wallet create -wallet /u01/app/oracle/product/11.2.0.4/dbhome_1/wallet -pwd Password123 -auto_login

dodajemy certyfikaty:

orapki wallet add -wallet /u01/app/oracle/product/11.2.0.4/dbhome_1/wallet -trusted_cert -cert „/tmp/INTERCA.crt” -pwd Passwo