OGG-00303 OGG-10124 Caused by DYNAMICPORTLIST Parameter When Starting GoldenGate Manager

The following errors occur when starting GoldenGate Manager:

2022-08-19T21:21:04.281+1000  INFO    OGG-00987  Oracle GoldenGate Command Interpreter for Oracle:  GGSCI command (oracle): start manager.
2022-08-19T21:21:04.325+1000  ERROR   OGG-00303  Oracle GoldenGate Manager for Oracle, mgr.prm:  Unrecognized parameter (DYNAMICPORTLIST        15100).
2022-08-19T21:21:04.325+1000  ERROR   OGG-01668  Oracle GoldenGate Manager for Oracle, mgr.prm:  PROCESS ABENDING.
2022-08-19T21:38:26.148+1000  INFO    OGG-00987  Oracle GoldenGate Command Interpreter for Oracle:  GGSCI command (oracle): start manager.
2022-08-19T21:38:26.207+1000  ERROR   OGG-10124  Oracle GoldenGate Manager for Oracle, mgr.prm:  (mgr.prm) line 3: Parsing error, value "15100 - 15150" is not one of the legal values ((0*((6553[0-5])|(655[0-2][0-9])|(65[0-4][0-9][0-9])|(6[0-4][0-9][0-9][0-9])|([0-5][0-9][0-9][0-9][0-9])|([0-9]{1,4})))([-](0*((6553[0-5])|(655[0-2][0-9])|(65[0-4][0-9][0-9])|(6[0-4][0-9][0-9][0-9])|([0-5][0-9][0-9][0-9][0-9])|([0-9]{1,4}))))?)([, ]+(0*((6553[0-5])|(655[0-2][0-9])|(65[0-4][0-9][0-9])|(6[0-4][0-9][0-9][0-9])|([0-5][0-9][0-9][0-9][0-9])|([0-9]{1,4})))([-](0*((6553[0-5])|(655[0-2][0-9])|(65[0-4][0-9][0-9])|(6[0-4][0-9][0-9][0-9])|([0-5][0-9][0-9][0-9][0-9])|([0-9]{1,4}))))?)* for [dynamicportlist].
2022-08-19T21:38:26.207+1000  ERROR   OGG-01668  Oracle GoldenGate Manager for Oracle, mgr.prm:  PROCESS ABENDING.

SOLUTION

Subscribe to get access

Read more of this content when you subscribe today.

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.

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.

How to Tune OEM 13c Agent Parameters when Agent is Monitoring Big Amount of Targets

In Exadata environment, the OEM agent is monitoring up to one hundred of targets. The agent always stopped or bounced by itself with the following different errors. This post demonstrates how to tune the agent parameters to improve the agent satiability and performance.

Subscribe to get access

Read more of this content when you subscribe today.