We're here to help!

Source and Target Archivelog Name Differences

Follow
Problem Description

If I create (CSD) or sync (Synchronise) the standby database, I discovered an incorrect archivelog format on the standby system.

For example, on the primary database:

SQL>show parameter log_archive_format
log_archive_format string ORCL_%t_%s_%r.arc

host server01: ls -tlr /FRA/ORCL/archivelog 
-rw-r-----. 1 oracle dba 986624 Mar 12 13:00 ORCL_1_67_869993216.arc
-rw-r-----. 1 oracle dba 530944 Mar 12 13:10 ORCL_1_68_869993216.arc
-rw-r-----. 1 oracle dba 432128 Mar 12 13:20 ORCL_1_69_869993216.arc
-rw-r-----. 1 oracle dba 303616 Mar 12 13:29 ORCL_1_70_869993216.arc
-rw-r-----. 1 oracle dba 1024 Mar 12 13:29 ORCL_1_71_869993216.arc
-rw-r-----. 1 oracle dba 478208 Mar 12 13:40 ORCL_1_72_869993216.arc
-rw-r-----. 1 oracle dba 655360 Mar 12 13:57 ORCL_1_73_869993216.arc
-rw-r-----. 1 oracle dba 965120 Mar 12 14:18 ORCL_1_74_869993216.arc
-rw-r-----. 1 oracle dba 197120 Mar 12 14:19 ORCL_1_75_869993216.arc SQL>show parameter log_archive_format
log_archive_format string ORCL_%t_%s_%r.arc host server02:
-rw-r--r--. 1 oracle dba 432128 Mar 12 13:20 1_69_869993216.arc
-rw-r--r--. 1 oracle dba 303616 Mar 12 13:30 1_70_869993216.arc
-rw-r--r--. 1 oracle dba 1024 Mar 12 13:30 1_71_869993216.arc
-rw-r--r--. 1 oracle dba 478208 Mar 12 13:40 1_72_869993216.arc
-rw-r--r--. 1 oracle dba 655360 Mar 12 13:57 1_73_869993216.arc
-rw-r--r--. 1 oracle dba 965120 Mar 12 14:19 1_74_869993216.arc
-rw-r--r--. 1 oracle dba 197120 Mar 12 14:19 1_75_869993216.arc

Is it necessary to configure a special parameter in the dbv_*.env file?

Solution

Dbvisit Standby Version 7 and Version 8 renames the archive logs on the standby server to the new name format. This is not configurable and is not related to any database parameters such as log_archive_format.

For more detail please see:

https://dbvisit.atlassian.net/wiki/display/UGDS7/Dbvisit+Standby+Version+7+New+Features

  • New default naming of archive logs on the standby server. Archive logs transferred to the standby database server is now renamed to a specific format:

    <thread>_<sequence>_<resetlogs\_id><STANDBY\_ARCHIVELOG\_NAME\_EXTENSION>

    Where STANDBY_ARCHIVELOG_NAME_EXTENSION defaults to .arc.

    For example: 1_45628_ 812975118.arc

For more details on the ARCHDEST location also see:

https://dbvisit.atlassian.net/wiki/display/UGDS7/Standby+Server+Settings

Archive logs must be shipped (copied) to the standby using Dbvisit Standby as the archive logs are renamed during this process. If archive logs are not copied to the standby using Dbvisit Standby, the archive logs might not be in the correct naming format as mentioned above and the recover process will not pick up the correct archive logs - unless they are renamed. This approach of not using Dbvisit Standby to send (copy) archive logs to the standby is not recommended.

Summary

Dbvisit Standby will rename the archive logs as part of the transfer and the archive log located on the standby database server will have a new specific name format, which is unique to that primary database.

Mike Donovan March 16, 2015 09:30

Have more questions? Submit a request

Comments