For the redo transfer to take place efficiently, the password file on standby should be a copy from the primary and renamed standby. We can use v$pwd_file_users data dictionary view to check if the password file is used
1.copy the password file from the primary to the standby and renamed the password file in the following format ie orapw<sid> .
2.Restart the media recovery process on the standby.
Once the above steps are completed we could see that redo shipping and redo apply is taking place.
Copy the latest Password file from available PRIMARY Node to rest of PRIMARY and STANDBY nodes:
scp orapw<sid> oracle@PROD_NODE_2_hostname:/oracle/home/dbs
scp orapw<sid> oracle@DR_NODE_1_hostname:/oracle/home/dbs
scp orapw<sid> oracle@DR_NODE_2_hostname:/oracle/home/dbs
select * from gv$pwfile_users;
we have to check sec_case_sensitive_logon parameter on primary and standby.
SQL> show parameter sec_case_sensitive_logon;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
sec_case_sensitive_logon boolean FALSE
We have to recreate the passwd file or copy Primary server to Standby server.
In cause sec_case_sensitive_logon parameter value is true, we have to use below orapwd command.
orapwd file=$ORACLE_HOME/dbs/orapwPROD password=password123 entries=10 ignorecase=y
In cause sec_case_sensitive_logon parameter value is false, we have to use below orapwd command.
orapwd file=$ORACLE_HOME/dbs/orapwPROD password=password123 entries=10
cancelling MRP process:
alter database recover managed standby database cancel;
starting mrp process:
alter database recover managed standby database disconnect from session;
select inst_id,process,status,thread#,sequence#,block#,blocks from gv$managed_standby;
check DR sync and see the difference.
Until you can do the following:
sqlplus sys/pass@Standby as sysdba (from the primary system)
sqlplus sys/pass@primary as sysdba (from the standby system)
You will not be able to ship redo.
If it is your password file not only do you have to copy it to the standby and rename it, but you need to stop recovery and restart the database on the new password file.
Also double check this parameter;
If the 1031 stops and you get another error try:
Shutdown listener and Database
SQL> alter system register;