Adding Standby Redo Log and Resolving Data guard Error

ORA-16801: redo transport-related property is inconsistent with database Settings

Data Guard Setup: Primary with Two Standbys

DB Version: 10.2.0.4.0 64Bit

OS: Enterprise Linux 5.3 64Bit

Data Guard Broker: Yes

Redo Transport Mode: ASYNC

Second standby database created using rman duplicate command. Started the managed recovery process and logs are started applying. Data Guard broker enabled for this database.  While enabling & verifying the configuration for this database, I got the following error.

ORA-16801: redo transport-related property is inconsistent with database setting
ORA-16715: redo transport-related property LogXptMode of standby database "stby2" is inconsistent

Note: I tried to add Standby Redo Log (SRL) immediately after  creating standby but before starting the managed recovery, but I got the error ORA-301 signalled during: ALTER DATABASE ADD STANDBY LOGFILE GROUP  and not able to add the standby redo logs.

I performed the following steps to resolve this issue.

1.       Stop the redo apply on the standby database

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL

2.       Create the Standby Redo Log on standby

a) The size of the standby redo log files must match the size of primary database online redo log files. Find the size of the primary database online redo log files. Number of Standby Redo Logs should be at least one greater than number online redo logsSQL> select bytes from v$log;
   BYTES

   ----------

  52428800

  52428800

  52428800
Here the size of my online redo log files is 50M.

b) Use the following query to find the details of the log files in the primary database.

SQL> select group#,type,member from v$logfile;
    GROUP# TYPE    MEMBER

---------- ------- --------------------------------------------------

         1 ONLINE  /u03/oradata/prod_redo01a.log

         1 ONLINE  /u03/oradata/prod_redo01b.log

         2 ONLINE  /u03/oradata/prod_redo02a.log

         2 ONLINE  /u03/oradata/prod_redo02b.log

         3 ONLINE  /u03/oradata/prod_redo03a.log

         3 ONLINE  /u03/oradata/prod_redo03b.log

         4 STANDBY /u03/oradata/prod_redo04a.log

         4 STANDBY /u03/oradata/prod_redo04b.log

         5 STANDBY /u03/oradata/prod_redo05a.log

         5 STANDBY /u03/oradata/prod_redo05b.log

         6 STANDBY /u03/oradata/prod_redo06a.log

    GROUP# TYPE    MEMBER

---------- ------- --------------------------------------------------

         6 STANDBY /u03/oradata/prod_redo06b.log

         7 STANDBY /u03/oradata/prod_redo07a.log

         7 STANDBY /u03/oradata/prod_redo07b.log

From above output you can see that I already have standby redo logs on primary.

c) Now I have created the standby redo log files in the standby database.alter database add standby logfile group 4 ('/u03/oradata/prod_redo04a.log’, '/u03/oradata/prod_redo04b.log’) size 50M ;

alter database add standby logfile group 5 ('/u03/oradata/prod_redo05a.log’, ‘/u03/oradata/oas2/prod_redo05b.log’) size 50M;

alter database add standby logfile group 6 ('/u03/oradata/oas2/prod_redo06a.log’, ‘/u03/oradata/oas2/prod_redo06b.log’) size 50M;

alter database add standby logfile group 7 ('/u03/oradata/oas2/prod_redo07a.log’, ‘/u03/oradata/oas2/prod_redo07b.log’) size 50M;

3.       Start the log apply

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

4.     Enable second standby (SSTD)

DGMGRL> enable database stdby2;

5.       Verify the configuration

DGMGRL> show configuration;

Patching oracle apps with data guard

Lately we have applied a ptach on our apps instance with physical standby database.



Following are the steps used.



1. Stopped the recovery delay in standby db

2. Stopeed application tier services on production

3. Switch the log in prod db and get the last sequence#

4. verify on standby that last log applied

5. Stop recovery on standby

6. Take the apps prod instance to maintenance mode using adadmin

7. Perfoem patching

8. Re-start redo shipping and apply on standby

9. Run middle tier pre-clone on prod

10. Run DB tier pre-clone (Only if patching updates ORACLE_HOME)

11. Synchronize the application tier file system with standby (use rsync on linux)

12. When sync completes create new context file using adclonectx.pl

13. After new context file created configure file system using adconfig.pl

14. Optinally configure standby DB file system if you did step 10.

15. End.



Now the production and stnadby oracle applications instances are in sync.