Had an ODG configuration which contains 1 primary and 1 physical standby databases running with 19c on Oracle Linux 7. We moved them to Oracle Linux 8 with the forklift method. However, because we didn't copy the online redo logs over from old OL7 servers to the new OL8 servers, an incomplete recover was done … Continue reading ORA-16700: The standby database has diverged from the primary database
Tag: DataGuard
ORA-16766: Redo Apply is stopped
If you see this ORA error "ORA-16766: Redo Apply is stopped" when you check your dataguard configuration in Data Guard command-line interface (DGMGRL) DGMGRL> show configuration; Configuration - DG_PROD Protection Mode: MaxPerformance Databases: PROD1 - Primary database PROD2 - Physical standby database Error: ORA-16766: Redo Apply is stopped Fast-Start Failover: DISABLED Configuration Status: ERROR And … Continue reading ORA-16766: Redo Apply is stopped
ORA-01033: ORACLE initialization or shutdown in progress with Dataguard
Got an ODG patched recently and after that, Dataguard was out of sync. DGMGRL> show database verbose "PROD2" Database Status: DGM-17016: failed to retrieve status for database "PROD2" ORA-01033: ORACLE initialization or shutdown in progress ORA-16625: cannot reach database "PROD2" PROD2 is the physicla standby. Normally in a Dataguard envrionment, it means something wrong with … Continue reading ORA-01033: ORACLE initialization or shutdown in progress with Dataguard
ORA-16038 — when network is slow
One day I opened a standby database to run some heavy queries. Because we don't have the license for Active DataGuard, I had to stop the redo apply before I opened the standby database. After a few hours I finished my queries and I put the database back into the mount state and started the … Continue reading ORA-16038 — when network is slow
ORA-16649: possible failover to another database prevents this database from being opened
We have a newly upgraded 19c primary database which was in ODG configuration. We didn't use the ODG rolling upgrade, but just built the new server and restored/recovered database on it. So the standby was still on old 12c database and we were planning to do it in a week. The application using the database … Continue reading ORA-16649: possible failover to another database prevents this database from being opened
Fatal NI connect error 12514 and TNS-12564
If you see the following error in the alert log of the new primary server during a switchover, that's normal. It's a transient one. ******************************************************************** Fatal NI connect error 12514, connecting to: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(Host=OL6DB01)(Port=1521)))(CONNECT_DATA=(SERVICE_NAME=PROD1)(CID=(PROGRAM=oracle)(HOST=ol7db02)(USER=oracle)))) VERSION INFORMATION: TNS for Linux: Version 12.1.0.2.0 - Production TCP/IP NT Protocol Adapter for Linux: Version 12.1.0.2.0 - Production Time: 30-OCT-2020 15:08:40 … Continue reading Fatal NI connect error 12514 and TNS-12564
ODG — ORA-16854: apply lag could not be determined
An ODG system has been upgraded recently to 19C and redo apply stopped working. I was asked to take a look at it. It is managed by ODG broker. When checking it in dgmgrl using "show configuration;", I saw the error "ORA-16810: multiple errors or warnings detected for the database" on the standby database. Then … Continue reading ODG — ORA-16854: apply lag could not be determined
Redo & Standby Redo files created as OMF when duplicating a standby database
Redo log is crucial for recovery. An Oracle database consists of two or more redo log files. If a database is in archive mode, Oracle database writes changes (change vectors, a.k.a redo entries) to one of redo log files while others are being archived. Redo records are buffered in a circular fashion in the redo … Continue reading Redo & Standby Redo files created as OMF when duplicating a standby database
ODG broker error: ORA-1005: null password given; logon denied
I have an Oracle DataGuard envrionment that it has been upgraded from 12.1.0.2 to 18C recently. After the upgrade, the ODG broker gave the following error: ORA-1005: null password given; logon denied DGMGRL> show configuration; Configuration - DG_APROD Protection Mode: MaxPerformance Members: DB1 - Primary database Error: ORA-1005: null password given; logon denied DB2- Physical … Continue reading ODG broker error: ORA-1005: null password given; logon denied