Error 1033 received logging on to the standby | orapwd and Password file

I got ” Error 1033 received logging on to the standby ” error in Oracle Dataguard.

Error 1033 received logging on to the standby

Details of error are as follows in the Alertlog of Production database.

TT00 (PID:294392): Error 1033 received logging on to the standby
TT00 (PID:294392): Error 1033 received logging on to the standby
TT00 (PID:294392): Error 1033 received logging on to the standby
TT00 (PID:294392): Error 1033 received logging on to the standby
TT00 (PID:294392): Error 1033 received logging on to the standby

This error is related with the missing of password file on both production and standby side. Sometimes password files may be corrupted or removed accidentally.

orapwd file=orapw$ORACLE_SID password=welcome1 entries=5 FORCE=Y

If the password file is missing, then create it as follows.

orapwd file=orapw$ORACLE_SID password=welcome1 entries=5 FORCE=Y

Then copy this password file to Standby. If your database is Oracle RAC, then copy this file to all node.

Mostly DBAs are changing the sys password of Production database but they forget to copy it to Dataguard database.

To solve this error, check your sys password and password file.

You can check and test the Production and Standby Side connections as follows.

Primary Side:

run sqlplus as follows.

sqlplus /nolog

Then run the following code, type your sys password and TNS Alias correctly.

connect sys/welcome@PROD_ALIAS as sysdba
Connected.
SQL> connect sys/welcome1@STANDBY_ALIAS as sysdba
Connected.

Standby Side:

run sqlplus as follows.

sqlplus /nolog

Then run the following code, type your sys password and TNS Alias correctly.

connect sys/welcome1@PROD_ALIAS as sysdba
Connected.
SQL> connect sys/welcome1@STANDBY_ALIAS as sysdba
Connected.

If the above connection test is not worked fine, then fix your password file or create it again.

Or you can copy it from the correct Primary Node to Other Primary nodes and Standby Side.

Sometimes if there is no free spaces for archives on Primary and Standby side, you may get this error. So you should check for free spaces.

If there is no problem with the above options, then check your log_archive_dest_state_X parameter, this parameter may be defer.

If they are not enable , then you can enable it as follows.

alter system set log_archive_dest_state_X=enable scope=both sid=’*’

Do you want to learn Oracle dataguard, then read the following articles.

Oracle DataGuard Physical Standby Installation Step by Step Using RMAN -1