916143 wrote:What is your OS version?
I have a failover configuration which was running fine until now.Now whenever "start observer" command is issued it is giving DGM-16979 : Unable to log on to the primary or standby database as SYSDBA error.
* passwords of 'system' user is same on both primary and standby.
* I recreated the password file on both primary and standby but same error persists.
Please help! Not getting any solution to this on web.
916143 wrote:Ok, Have you tested connectivity in both primary & standby databases?
I have disabled case sensitive passwords for DB and also have created the password file with ignorecase=y.
DGMGRL> connect sys/*****Also refer this link http://www.dba-oracle.com/fast_start_failover.htm
OR in a script
nohup dgmgrl -silent sys/*** "start observer" &
#!/bin/bash ### Script to start observer dgmgrl -echo -logfile /tmp/dgmgrl.log << EOF connect sys/passwd@connect_string start observer EOF
dgmgrl -logfile /tmp/observer.log sys/passwd@connect_string "start observer" &
Thanks! resolved the issue with passwordfile, i was making the mistake of not bouncing one of the DB primary or standby.
Now while starting the observer it is giving the same error DGM-16979: Unable to log on to the primary or standby database as SYSDBA.
Got back to same place from where it all started! I am using sys user, still getting the error!
Edited by: 916143 on 22-Feb-2012 03:20
DGMGRL> edit database <prim> set property LogShipping=off;2. Change the SYS password in the Primary
SQL> alter user sys identified by oracle;3. Copy the Primary Site password file to the Standby Site
using CP command4. Enable Log Shipping between the two Sites
DGMGRL> edit database <prim> set property LogShipping=on;5. Check shipping and the Data Guard configuration is working normally
Thanks, Resolved the issue.Welcome
One more thing, how to keep the observer running all the time because whenever the ssh session expires the observer stops monitoring the DB's after some time. While scheduling it in cron job, it is throwing the error :Normally this error will be occurred because of en-queue too. If already observer is running, if you try to start it throws as above.
DGM-16954: Unable to open and lock the Observer configuration fileFailed cron job.
DGM-16954: Unable to open and lock the Observer configuration file Cause: The Observer configuration file cannot be opened or cannot be locked for exclusive access. Action: Make sure the Observer has the correct operating system privileges to write the file and there is no other Observer that is using the same file. Try the command again.
But while executing the same script from command line it works fine. I have added all the path variables,dgmgrl is working fine, the observer stops successfully but gives the above error while starting it.Here's the excerpt of the script:In this step, you executing manually also using Stop observer as first command from DGMGRL, so it has no issues, implement same in script too.
dgmgrl << eof
DGMGRL> Connected.-- connected
DGMGRL> Done.-- stop observer worked here
DGMGRL> DGM-16954: Unable to open and lock the Observer configuration file-- start observer failed.
While executing the same script from command prompt it is not throwing any error.Can you split(after stop observer) it into two script or put a time gap between stop & start observer commands? --> for testing purpose
If i use "nohup &" instead of cron job, will the script run forever or would it die after some time??