Thanks guys for your reply, my problem is solved, one of my node's tnsnames entry was different for others. I have changed it and now not facing same problem. Now it's a different error. It seems to be related with password file.
My Password parameter is EXCLUSIVE. I have copied orapwracdb1 and orapwracdb2 to standby database's $ORACLE_HOME/dbs location with filename orapwst_racdb
[oracle@dg dbs]$ ls
hc_racdg.dat hc_st_racdb.dat init.ora lkRACDB orapwracdb1 orapwracdb2 orapwst_racdb
RMAN Duplicate command from stand by server:
rman target sys/sys@racdb auxiliary sys/sys@dr
DUPLICATE DATABASE FOR STANDBY FROM ACTIVE DATABASE NOFILENAMECHECK DORECOVER;
Following error shows:
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-03002: failure of Duplicate Db command at 06/01/2014 06:45:45
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on DISK8 channel at 06/01/2014 06:45:45
ORA-19505: failed to identify file "/u01/app/oracle/product/11.2.0/dbhome_1/dbs/orapwracdb1"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
I think red lines are the problems. how can I solve it, please suggest.
Hasan Al Mamun
I hope you did not "move" the pwd file from your current Primary node.
Also, why did you have to get the 2 password files shipped to Standby site, you can just take one and rename that to "orapw<name_of_sby_instance>", that itself should work.
Message was edited by: 1826067 Sorry, forgot to mention 2 important points.... 1st thing, it's always recommended to run the Duplicate command from a Primary Node, though it's not a mandate! 2nd, Are you using a scan-name when trying to connect to the target Database(Primary), if so, you may face the problem. Connect to just one instance either racdb1 or racdb2.
Finally Standby database has been created. Had to go through series of corrections. First, i had mistaken db_name and db_unique_name
Then had to configure snapshot control file. and then some output file newname conventions. Standby completed, but of no use. Standby does not seem to be in sync with primary database. I had applied redo, and switched logs in primary checked archive changes in standby but it's not changing in standby database.
Now when I see Enterprise Manager of Primary database at the data guard section I see the following errors.
Jun 2, 2014 9:09:15 AM Error ORA-12154: TNS:could not resolve the connect identifier specified Jun 2, 2014 1:07:45 AM Error ORA-12154: TNS:could not resolve the connect identifier specified Jun 2, 2014 1:02:45 AM Normal ORA-00000: normal, successful completion
Actually I am doing my home work in my vmware before a big deployment. I don't want to stuck in a situation in the production database.
Hasan Al Mamun