cancel
Showing results for 
Search instead for 
Did you mean: 

Archived Redo Logs not applied in standby database

Former Member
0 Kudos

Hi,

I have configured ODG for SAP ECC6.0 server. Two days back, due to the disk space issue, archived redo logs stopped transferring to the standby database, so missing archived redo logs have been copied to the standby database and started the automatic recovery. After the automatic recovery, there are some redo logs that are not shown in the output of query "select sequence#, archived, applied from v$archived_log order by sequence#;".

Output is as mentioned below:

SEQUENCE# ARC APP

50651 YES YES

50652 YES YES

50686 YES YES

50760 YES YES

50761 YES YES

50793 YES YES

50794 YES YES

50795 YES YES

50796 YES YES

Here, between 50652 and 50686, some archived redo logs are missing, but these archived redo logs are available in the oraarch directory.

Please let me know, how to resolve this issue.

Regards,

Ranjith

Accepted Solutions (1)

Accepted Solutions (1)

stefan_koehler
Active Contributor
0 Kudos

Hello Ranjith,

> so missing archived redo logs have been copied to the standby database and started the automatic recovery.

Did you copy these missing archive logs manually? How did you trigger the recovery?

Maybe you forgot to register these archive logs.

Regards

Stefan

Former Member
0 Kudos

Hi Stefan,

Thanks for replying.

Some of the archived redo logs have been copied manually from Production server (at this time, managed recovery was active in the standby database) and some files from backup tape. Once all the archived redo logs have been copied to standby database, stopped the managed recovery, which was active in background and below mentioned command was used to start the automatic recovery.

alter database recover automatic standby database until cancel;

Once the recovery is completed, i stopped the recovery and started the managed recovery using "alter database recover managed standby database disconnect from Session;"

When i run the query "SELECT THREAD#, SEQUENCE#, FIRST_CHANGE#, NEXT_CHANGE# FROM V$LOG_HISTORY;" in standby database, it is showing all the archived redo logs, which were missing when i executed query "select sequence#, archived, applied from v$archived_log order by sequence#;".

THREAD# SEQUENCE# FIRST_CHANGE# NEXT_CHANGE#

-


-


-


-


1 50644 454675785 454679473

1 50645 454679473 454682160

1 50646 454682160 454685181

1 50647 454685181 454687375

1 50648 454687375 454689647

1 50649 454689647 454691885

1 50650 454691885 454694093

1 50651 454694093 454696416

1 50652 454696416 454698637

1 50653 454698637 454701589

1 50654 454701589 454704057

Please suggest.

Regards,

Ranjith

stefan_koehler
Active Contributor
0 Kudos

Hello Ranjith,

as you mentioned, that you have done manual steps you need to register the archive log file.

Please execute the following command for every manual copied archive log file on the standby database:


shell> sqlplus / as sysdba
SQL> alter database register logfile '<ARCHIVELOG_PATH>';

After that check it again.

Regards

Stefan

Former Member
0 Kudos

Hi Stefan,

After registering the archived redo log files manually, issue has been resolved.

Thanks a lot.

Regards,

Ranjith

Answers (0)