Error in standby db while applying logs

Question

Hi,
we have a manual standby db of version 9.2.0.6 on sun solaris
in alert log file i found error in one og the log i.e Errors with log /arch/log/1_1817.dbf
ALTER DATABASE RECOVER    CONTINUE DEFAULT
Wed Oct 22 18:33:03 2008
Media Recovery Log /arch/log/2_1616.dbf
Wed Oct 22 18:35:47 2008
ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
Wed Oct 22 18:35:47 2008
ALTER DATABASE RECOVER    CONTINUE DEFAULT
Wed Oct 22 18:35:47 2008
Media Recovery Log /arch/log/2_1617.dbf
Wed Oct 22 18:36:50 2008
ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
Wed Oct 22 18:36:50 2008
ALTER DATABASE RECOVER    CONTINUE DEFAULT
Wed Oct 22 18:36:50 2008
Media Recovery Log /arch/log/1_1817.dbf
Errors with log /arch/log/1_1817.dbf
ORA-308 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
Wed Oct 22 18:36:50 2008
ALTER DATABASE RECOVER CANCEL
Wed Oct 22 18:36:50 2008
Media Recovery Cancelled
Completed: ALTER DATABASE RECOVER CANCEL
Wed Oct 22 18:37:38 2008
alter database open read only
Wed Oct 22 18:37:38 2008
SMON: enabling cache recovery
Wed Oct 22 18:37:38 2008
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication fo
nd)
Completed: alter database open read only
Wed Oct 22 18:39:33 2008
Errors in file /arch/dump/udump/icai_ora_25288.trc:
ORA-00600: internal error code, arguments: [2662], [0], [1823949223], [0], [197
003713], [4194306], [], []
Wed Oct 22 18:39:45 2008
Errors in file /arch/dump/udump/icai_ora_25288.trc:
ORA-00600: internal error code, arguments: [2662], [0], [1823949225], [0], [197
003713], [4194306], [], []
ORA-00600: internal error code, arguments: [2662], [0], [1823949223], [0], [197
003713], [4194306], [], []
003713], [4194306], [], []i want to konw the whether the system had applied the 1_1817.dbf logs or not if db server generates an error on one of the logs...
looking for your reply...

Answer 1

SQL> select * from v$log_history;
     RECID      STAMP    THREAD#  SEQUENCE# FIRST_CHANGE# FIRST_TIM NEXT_CHANGE#
      3421  668092912          2       1613    1821523608 08-OCT-08   1822019922
      3422  668092971          1       1809    1821576072 08-OCT-08   1821777080
      3423  668093151          1       1810    1821777080 10-OCT-08   1822019918
      3424  668093340          1       1811    1822019918 11-OCT-08   1822282436
      3425  668284338          2       1614    1822019922 11-OCT-08   1822677394
      3426  668284525          1       1812    1822282436 13-OCT-08   1822526199
      3427  668284721          1       1813    1822526199 14-OCT-08   1822781536
      3428  668801898          2       1615    1822677394 15-OCT-08   1823381495
      3429  668801993          1       1814    1822781536 15-OCT-08   1823106551
      3430  668802398          1       1815    1823106551 17-OCT-08   1823381490
      3431  668802577          1       1816    1823381490 18-OCT-08   1823923486
     RECID      STAMP    THREAD#  SEQUENCE# FIRST_CHANGE# FIRST_TIM NEXT_CHANGE#
      3432  668802783          2       1616    1823381495 18-OCT-08   1823814529
      3433  668802947          2       1617    1823814529 20-OCT-08   1824079514
453 rows selected.
SQL>so here we can see that there is not recid for 1817 sequence that has been corrupted ,so now does it mean that archived have not been applied to the stanby database.....
SQL> SELECT MAX(R.SEQUENCE#) LAST_SEQ_RECD, MAX(L.SEQUENCE#) LAST_SEQ_SENT FROM
  2  V$ARCHIVED_LOG R, V$LOG L WHERE
  3  R.DEST_ID=1 AND L.ARCHIVED='YES';
LAST_SEQ_RECD LAST_SEQ_SENT
------------- -------------Edited by: user00726 on Oct 23, 2008 3:21 AM