ORA-00308: cannot open archived log

Standby database recovery stopped with the following errors:

Wed Aug 17 10:43:35 2022
Managed Standby Recovery starting Real Time Apply
Parallel Media Recovery started with 8 slaves
Waiting for all non-current ORLs to be archived…
All non-current ORLs have been archived.
Media Recovery Log /fra/PRDB/archivelog/2022_08_11/o1_mf_1_68911_kh8kkwp0_.arc
Error opening /fra/PRDB/archivelog/2022_08_11/o1_mf_1_68911_kh8kkwp0_.arc
Attempting refetch
MRP0: Background Media Recovery terminated with error 308
Errors in file /u01/app/oracle/diag/rdbms/prdb/PRDB/trace/PRDB_pr00_17264.trc:
ORA-00308: cannot open archived log '/fra/PRDB/archivelog/2022_08_11/o1_mf_1_68911_kh8kkwp0_.arc'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Managed Standby Recovery not using Real Time Apply
Recovery interrupted!
Some recovered datafiles maybe left media fuzzy
Media recovery may continue but open resetlogs may fail
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE THROUGH ALL SWITCHOVER DISCONNECT USING CURRENT LOGFILE
MRP0: Background Media Recovery process shutdown (PRDB)

Check the missing archive log does exist:

$ ls -ltr /fra/PRDB/archivelog/2022_08_11/o1_mf_1_68911_*_.arc
-rw-r-----. 1 oracle oinstall 910116352 Aug 11 09:58 /fra/PRDB/archivelog/2022_08_11/o1_mf_1_68911_kh8kjvh9_.arc

SOLUTION

Subscribe to get access

Read more of this content when you subscribe today.

./ggsci: error while loading shared libraries: libnnz12.so: cannot open shared object file: No such file or directory

While running ‘ggsci’, the following error occures:

$ cd GG_HOME
$./ggsci: error while loading shared libraries: libnnz12.so: cannot open shared object file: No such file or directory

Solution

Set up correct env variable $LD_LIBRARY_PATH by :

$ . oraenv
ORACLE_SID = [oracle] ? amer
The Oracle base has been set to /u01/app/oracle
$ ./ggsci

Oracle GoldenGate Command Interpreter for Oracle
...
..
.

Oracle CPU/PSU/BP/RU/RUR : Loading Modified SQL Files into Database

After applied Oracle CPU/PSU/BP/RU/RUR patch sets, one post installation task is “Loading Modified SQL Files Into the Database”.

For RAC and non-RAC, Exadata including ExaCC, ExaCS and non-Exadata, OJVM and non-OJVM, before 12c and after 12c versions, the way to execute SQL files are different from version to version. This post will demonstrate how to run it under different circumstances.

Subscribe to get access

Read more of this content when you subscribe today.

TNS-01101: Could not find listener name or service name LISTENER_SCAN1

A non-grid user tries to run the following command with TNS-01101 error:

$ /u01/app/19.0.0.0/grid/bin/lsnrctl status LISTENER_SCAN1

...
..
.

TNS-01101: Could not find listener name or service name LISTENER_SCAN1

SOLUTION

Subscribe to get access

Read more of this content when you subscribe today.