ORA-16737: the redo transport service for standby database "BHU_B" has an error
Error message
DGMGRL> show database verbose 'BHU_A';
Database – BHU_A
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
BHU_1
BHU_2
BHU_3
Error: ORA-16737: the redo transport service for standby database "BHU_B" has an error
Database Warning(s):
ORA-16629: database reports a different protection level from the protection mode
#1
CHECK: when you have the above problem, you will get the protection mode in the Primary & standby v$database.protection_level shows as "RESYNCHRONIZATION"
SQL> select protection_mode, protection_level from v$database;
#2
CHECK: whether you are getting any in the archive location
SQL>select dest_id,status,error from v$archive_dest;
#3
CHECK: Check whether online redo log are configured in the primary & standby database properly, it includes size & accessibility
Note: primary &standby online redo log should be same
SQL>select group#,thread#,sequence#,bytes,archived,status from v$log;
#4
CHECK: Check whether standby redo log are configured in the primary &standby database properly, it includes size & accessibility
Note: primary &standby standby redo log should be same
select member from v$logfile where type='STANDBY';
#5
CHECK: Check parameters are configured properly; some times instance parameters have a different value.
Ex: some common parameter will have different value for each instance in the cluster database. You need to check on the primary &standby cluster database environment.
#6
Check whether maximum Availability is enabled, when you have LogXptMode is synchronization
SYMP:
ORA-16629: database reports a different protection level from the protection mode
In DG Broker
DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS MAXAVAILABILITY;
Succeeded.
#7 check your password with the setting
A)
1) check for the "sec_case_sensitive_logon" parameter.
2) if the problem exist, create the password file with ignorecase option in the orapwd password creation.
3) after recreating the password, restart both the primary & standby database.
B)
DGMGRL> show database verbose 'BHU_A' LogXptStatus;
LOG TRANSPORT STATUS
PRIMARY_INSTANCE_NAME STANDBY_DATABASE_NAME STATUS
BHU1_1 BHU1_B
BHU1_2 BHU1_B ORA-16191: Primary log shipping client not logged on standby
Error message
DGMGRL> show database verbose 'BHU_A';
Database – BHU_A
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
BHU_1
BHU_2
BHU_3
Error: ORA-16737: the redo transport service for standby database "BHU_B" has an error
Database Warning(s):
ORA-16629: database reports a different protection level from the protection mode
#1
CHECK: when you have the above problem, you will get the protection mode in the Primary & standby v$database.protection_level shows as "RESYNCHRONIZATION"
SQL> select protection_mode, protection_level from v$database;
#2
CHECK: whether you are getting any in the archive location
SQL>select dest_id,status,error from v$archive_dest;
#3
CHECK: Check whether online redo log are configured in the primary & standby database properly, it includes size & accessibility
Note: primary &standby online redo log should be same
SQL>select group#,thread#,sequence#,bytes,archived,status from v$log;
#4
CHECK: Check whether standby redo log are configured in the primary &standby database properly, it includes size & accessibility
Note: primary &standby standby redo log should be same
select member from v$logfile where type='STANDBY';
#5
CHECK: Check parameters are configured properly; some times instance parameters have a different value.
Ex: some common parameter will have different value for each instance in the cluster database. You need to check on the primary &standby cluster database environment.
#6
Check whether maximum Availability is enabled, when you have LogXptMode is synchronization
SYMP:
ORA-16629: database reports a different protection level from the protection mode
In DG Broker
DGMGRL> EDIT CONFIGURATION SET PROTECTION MODE AS MAXAVAILABILITY;
Succeeded.
#7 check your password with the setting
A)
1) check for the "sec_case_sensitive_logon" parameter.
2) if the problem exist, create the password file with ignorecase option in the orapwd password creation.
3) after recreating the password, restart both the primary & standby database.
B)
DGMGRL> show database verbose 'BHU_A' LogXptStatus;
LOG TRANSPORT STATUS
PRIMARY_INSTANCE_NAME STANDBY_DATABASE_NAME STATUS
BHU1_1 BHU1_B
BHU1_2 BHU1_B ORA-16191: Primary log shipping client not logged on standby
No comments:
Post a Comment