As a database administrator, one of the issues you can encounter during a switchover or failover is the dreaded "invalid username/password" error. I recently faced this issue while working with Oracle 12C Broker and, after much investigation, discovered the root cause. Let me walk you through my experience and how I resolved it.
The Problem
While attempting a switchover, I repeatedly encountered the following error message despite knowing the username and password were correct and the password files were synchronized between the primary and standby databases:
DGMGRL> switchover to ldnprod; Performing switchover NOW, please wait... Operation requires a connection to instance "ldnprd" on database "ldnprd" Connecting to instance "prd"... ORA-01017: invalid username/password; logon denied Warning: You are no longer connected to ORACLE. DGMGRL> switchover to ldnprod;
not logged on DGMGRL> connect sys@drsng Password: ORA-01017: invalid username/password; logon denied
After extensive troubleshooting, I realized that the issue was due to the complexity of the password. Oracle 12C requires passwords to meet certain complexity requirements, and my initial password did not comply with these standards.
The Solution
To resolve this issue, I ensured that my password met the complexity requirements. Here’s how the process unfolded after updating the password to a more complex one:
Update the Password:
Ensure your new password includes a mix of upper and lower case letters, numbers, and special characters to meet Oracle's complexity requirements.
Reconnect and Retry the Switchover:
With the complex password in place, I reconnected and executed the switchover command again:
DGMGRL> connect sys@drsng Password: Connected as SYSDBA. DGMGRL> switchover to ldnprd; Performing switchover NOW, please wait... Operation requires a connection to instance "ldnprd" on database "ldnprd" Connecting to instance "ldnprd"... Connected as SYSDBA. New primary database "ldnprd" is opening... Operation requires startup of instance "drsng" on database "drsng" Starting instance "drsng"... ORACLE instance started. Database mounted. Switchover succeeded, new primary is "ldnprd"
DGMGRL> show configuration Configuration - dg_conf Protection Mode: MaxPerformance Databases: ldnprd - Primary database drsng - Physical standby database Fast-Start Failover: DISABLED Configuration Status: SUCCESS
This time, the switchover completed successfully without any errors.
Conclusion
Ensuring your passwords comply with Oracle's complexity requirements is crucial for seamless switchover and failover operations. If you encounter an "invalid username/password" error, double-check your password's complexity. This simple step can save you a lot of troubleshooting time and headaches.
By sharing this experience, I hope to help fellow DBAs avoid similar pitfalls. Happy database managing!
No comments:
Post a Comment