RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/17/2011 07:38:34
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on p1 channel at 11/17/2011 07:38:34
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-01017: invalid username/password; logon denied
ORA-17629: Cannot connect to the remote database server
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/17/2011 07:38:34
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on p1 channel at 11/17/2011 07:38:34
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-01017: invalid username/password; logon denied
ORA-17629: Cannot connect to the remote database server
We need to see first the script we execute to create the standby.
As this is 11g, we have a feature that we can make a standby database using rman duplicate db, even when the backup of primary database is not available.
So to use that feature executed below RMAN commands on target server.
rman target / auxiliary sys/pass@STANDB
run
{
allocate channel p1 type disk;
allocate auxiliary channel sb1 type disk;
duplicate target database for standby from active database;
}
{
allocate channel p1 type disk;
allocate auxiliary channel sb1 type disk;
duplicate target database for standby from active database;
}
And this ended up with above error.
Two things to be checked in this case:
1. Simply try logging in to each of the database using service name from the other server.(remote login)
from standby - sqlplus sys/passs@PRIME
from primary - sqlplus sys/passs@STANDB
from standby - sqlplus sys/passs@PRIME
from primary - sqlplus sys/passs@STANDB
2. For executing this we have to connect both the databases using service name and if the target is connected as / then above error occurs.
Another error message will appear if we connect standby as /, but that states clearly to connect auxiliary database using service name.
So the right way of connecting using service name is
rman target sys/passs@PRIME auxiliary sys/pass@STANDB
No comments:
Post a Comment