Using redo_transport_user DGMGRL Switchover Command Fails With ORA-1033 AND ORA-1219
(Doc ID 2266328.1)
Last updated on FEBRUARY 04, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Using redo_transport_user for redo transport connections.
Switchover via DataGuard Broker in a multi-tenant Active DataGuard environment when REDO_TRANSPORT_USER is set to a user defined user, fails with ORA-01219
using password file authentication. Although the roles are switched the former primary database, now the standby, is left mounted showing errors in alert and drc logs which looks like a password file problem ORA-1033.
Data Guard broker shows ORA-16665: timeout waiting for the result from a database
Notifying Oracle Clusterware to prepare primary database for switchover
06/27/2016 12:22:28
Failed to connect to remote database TEST_B. Error is ORA-01033
Failed to send message to site TEST_B. Error code is ORA-01033.
Switchover Aborted due to errors
Site named: TEST_A is still primary
error = ORA-01033
DGMGRL> switchover to 'TEST_B';
Performing switchover NOW, please wait...
Operation requires a connection to instance "TEST2" on database "TEST_B"
Connecting to instance "TEST2"...
Connected as SYSDG.
Error: ORA-16665: timeout waiting for the result from a database
Failed.
Unable to switchover, primary database is still "TEST_A"
Changes
Configured redo_transport_user for Data Guard
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |