RMAN ALert Log Message: ALTER SYSTEM ARCHIVE LOG

Created a new Database on Oracle 10.2.0.4 and now seeing "ALTER SYSTEM ARCHIVE LOG" in the Alert Log only when the online RMAN backup runs:
Wed Aug 26 21:52:03 2009
ALTER SYSTEM ARCHIVE LOG
Wed Aug 26 21:52:03 2009
Thread 1 advanced to log sequence 35 (LGWR switch)
Current log# 2 seq# 35 mem# 0: /u01/app/oracle/oradata/aatest/redo02.log
Current log# 2 seq# 35 mem# 1: /u03/oradata/aatest/redo02a.log
Wed Aug 26 21:53:37 2009
ALTER SYSTEM ARCHIVE LOG
Wed Aug 26 21:53:37 2009
Thread 1 advanced to log sequence 36 (LGWR switch)
Current log# 3 seq# 36 mem# 0: /u01/app/oracle/oradata/aatest/redo03.log
Current log# 3 seq# 36 mem# 1: /u03/oradata/aatest/redo03a.log
Wed Aug 26 21:53:40 2009
Starting control autobackup
Control autobackup written to DISK device
     handle '/u03/exports/backups/aatest/c-2538018370-20090826-00'
I am not issuing a log swiitch command. The RMAN commands I am running are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/exports/backups/aatest/%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/u03/exports/backups/aatest/%d_%U';
BACKUP DATABASE PLUS ARCHIVELOG;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT ARCHIVELOG UNTIL TIME 'SYSDATE-2';
I do not see this message on any other 10.2.0.4 instances. Has anyone seen this and if so why is this showing in the log?
Thank you,
Curt Swartzlander

There's no problem with log switch. Please refer to documentation for more information on syntax "PLUS ARCHIVELOG"
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup003.htm#sthref377
Adding BACKUP ... PLUS ARCHIVELOG causes RMAN to do the following:
*1. Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command.*
*2. Runs BACKUP ARCHIVELOG ALL. Note that if backup optimization is enabled, then RMAN skips logs that it has already backed up to the specified device.*
*3. Backs up the rest of the files specified in BACKUP command.*
*4. Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command.*
*5. Backs up any remaining archived logs generated during the backup.*
This guarantees that datafile backups taken during the command are recoverable to a consistent state.

Similar Messages

  • Question about ALTER SYSTEM ARCHIVE LOG START

    Good morning,
    I'm trying (unsuccessfully) to get my database to be in archive log mode.
    These are the steps I followed:
    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount;
    ORACLE instance started.
    Total System Global Area  535662592 bytes
    Fixed Size                  1375792 bytes
    Variable Size             377487824 bytes
    Database Buffers          150994944 bytes
    Redo Buffers                5804032 bytes
    Database mounted.
    SQL> select log_mode from v$database;
    LOG_MODE
    ARCHIVELOG
    SQL> show parameter log_archive_start;
    NAME                                 TYPE        VALUE
    log_archive_start                    boolean     FALSE
    SQL> alter system archive log start;
    System altered.
    SQL> show parameter log_archive_start;
    NAME                                 TYPE        VALUE
    log_archive_start                    boolean     FALSE
    SQL>I've gone thru that process twice but, I don't seem to be able to get the ARCH process to start. (newbie mistake I'm sure...)
    Thank you for your help (again!),
    John.

    The parameter log_archive_start is no more needed John (as suggested already) and the best way to check the archive options is through the archive log list command.
    [oracle@edhdr2p0-orcl oui]$ sqlplus / as sysdba
    SQL*Plus: Release 11.2.0.1.0 Production on Tue Aug 10 10:51:57 2010
    Copyright (c) 1982, 2009, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
    With the Partitioning, Automatic Storage Management, OLAP, Data Mining
    and Real Application Testing options
    SQL> archive log list
    Database log mode              No Archive Mode
    Automatic archival             Disabled
    Archive destination            USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence     11
    Current log sequence           13
    SQL> shut immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area  418484224 bytes
    Fixed Size                  1336932 bytes
    Variable Size             318769564 bytes
    Database Buffers           92274688 bytes
    Redo Buffers                6103040 bytes
    Database mounted.
    SQL> select process,status from V$archive_processes;
       PROCESS STATUS
             0 STOPPED
             1 STOPPED
             2 STOPPED
             3 STOPPED
             4 STOPPED
             5 STOPPED
             6 STOPPED
             7 STOPPED
             8 STOPPED
             9 STOPPED
            10 STOPPED
       PROCESS STATUS
            11 STOPPED
            12 STOPPED
            13 STOPPED
            14 STOPPED
            15 STOPPED
            16 STOPPED
            17 STOPPED
            18 STOPPED
            19 STOPPED
            20 STOPPED
            21 STOPPED
       PROCESS STATUS
            22 STOPPED
            23 STOPPED
            24 STOPPED
            25 STOPPED
            26 STOPPED
            27 STOPPED
            28 STOPPED
            29 STOPPED
    30 rows selected.
    SQL>
    SQL> alter database archivelog;
    Database altered.
    SQL> alter database open;
    archive log list;
    Database altered.
    SQL> Database log mode         Archive Mode
    Automatic archival             Enabled
    Archive destination            USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence     11
    Next log sequence to archive   13
    Current log sequence           13
    SQL>
    SQL> select * from V$archive_processes where status <> 'STOPPED';
       PROCESS STATUS     LOG_SEQUENCE STAT
             0 ACTIVE                0 IDLE
             1 ACTIVE                0 IDLE
             2 ACTIVE                0 IDLE
             3 ACTIVE                0 IDLEHTH
    Aman....

  • Alter system archive log current

    Hi everyone,
    I write code to alter system archive log current in PL/SQL as following:
    declare
    start_sequence number;
    end_sequence number;
    begin
    --- get start sequence# ---
    select SEQUENCE# into start_sequence from v_$log where status='CURRENT';
    --- get end sequence# ---
    alter system archive log current;
    select SEQUENCE# into end_sequence from v_$log where status='CURRENT';
    end;
    When I run it, I got the following error:
    alter system archive log current;
    ERROR at line 11:
    ORA-06550: line 11, column 6:
    PLS-00103: Encountered the symbol "ALTER" when expecting one of the following:
    begin case declare end exception exit for goto if loop mod
    null pragma raise return select update while with
    <an identifier> <a double-quoted delimited-identifier>
    <a bind variable> << close current delete fetch lock insert
    open rollback savepoint set sql execute commit forall merge
    pipe
    What does it mean? How can I fix it/
    Thanks!

    That is because you are trying to issue a DDL call in PL/SQL. The only way you can achieve this is to use DYNAMIC SQL.
    If you change your ALTER statement to:
    EXECUTE IMMEDIATE 'ALTER SYSTEM ARCHIVE LOG CURRENT';It should work.
    HTH!

  • RMAN-06054: media recovery requesting unknown archived log

    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 05/16/2013 09:03:43
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 34751 and starting SCN of 8923445274I am receiving the error above on performing RMAN Active cloning, please advise how to resolve this

    In addition to what was said, I can think of two other possibilities for RMAN-6054 during duplicate: bugs such as 12625205 (also see 8554110); duplicate was run earlier without removing the old restored files (Note 1549172.1). In the first case, just specify SCN or find the actual log file and speficy log sequence, instead of time. In the latter case, remove the old restored files or speficy noresume.
    Edited by: user11989003 on May 29, 2013 10:17 AM

  • ICal writing tons of log messages into system.log

    Hi all,
    I've got an issue with iCal under Leopard 10.5.1.
    Sometimes my syslogd process grabs ~100% CPU time and so I took a look into system.log.
    I saw MANY lines like this:
    Jan 27 19:23:34 Tigger com.apple.syncservices.SyncServer[4225]: 2008-01-27 19:23:34.363 iCalExternalSync[4230:10b] ISyncSession deleteRecordWithIdentifier: ignoring delete for unknown record Event/p774
    Jan 27 19:23:34 Tigger com.apple.syncservices.SyncServer[4225]: 2008-01-27 19:23:34.364 iCalExternalSync[4230:10b] ISyncSession deleteRecordWithIdentifier: ignoring delete for unknown record Event/p2754
    Jan 27 19:23:34 Tigger com.apple.syncservices.SyncServer[4225]: 2008-01-27 19:23:34.364 iCalExternalSync[4230:10b] ISyncSession deleteRecordWithIdentifier: ignoring delete for unknown record Event/p288
    Jan 27 19:23:34 Tigger com.apple.syncservices.SyncServer[4225]: 2008-01-27 19:23:34.365 iCalExternalSync[4230:10b] ISyncSession deleteRecordWithIdentifier: ignoring delete for unknown record Event/p2056
    Jan 27 19:23:34 Tigger com.apple.syncservices.SyncServer[4225]: 2008-01-27 19:23:34.366 iCalExternalSync[4230:10b] ISyncSession deleteRecordWithIdentifier: ignoring delete for unknown record Event/p148
    Jan 27 19:23:34 Tigger com.apple.syncservices.SyncServer[4225]: 2008-01-27 19:23:34.367 iCalExternalSync[4230:10b] ISyncSession deleteRecordWithIdentifier: ignoring delete for unknown record Event/p73
    Jan 27 19:23:42 Tigger com.apple.syncservices.SyncServer[4225]: 2008-01-27 19:23:42.497 iCalExternalSync[4230:10b] SyncServices precondition failure in [ISyncConcreteSession clientAcceptedChangesForRecordWithIdentifier:formattedRecord:newRecordIdentifie r:]: you can't change the record identifier from 4183D93C-A813-4AB4-BA0F-C246414B2DA1 to node_BirthdayCalendar/p7: it is already associated with a different record.
    Jan 27 19:23:42 Tigger com.apple.syncservices.SyncServer[4225]: 2008-01-27 19:23:42.521 iCalExternalSync[4230:10b] [ICalExternalSync ]Encountered [ISyncConcreteSession clientAcceptedChangesForRecordWithIdentifier:formattedRecord:newRecordIdentifie r:]: you can't change the record identifier from 4183D93C-A813-4AB4-BA0F-C246414B2DA1 to node_BirthdayCalendar/p7: it is already associated with a different record.
    Jan 27 19:23:42 Tigger com.apple.syncservices.SyncServer[4225]: 2008-01-27 19:23:42.526 iCalExternalSync[4230:10b] [ICalExternalSync ]NSException name:NSInvalidArgumentException reason:[ISyncConcreteSession clientAcceptedChangesForRecordWithIdentifier:formattedRecord:newRecordIdentifie r:]: you can't change the record identifier from 4183D93C-A813-4AB4-BA0F-C246414B2DA1 to node_BirthdayCalendar/p7: it is already associated with a different record.
    Any idea how to fix this?
    Here's another problem that might be related to this: my "Private" calendar was published in 10.4 but now the webdav server that was used for this is no longer existent (and can't be setup again).
    So I wanted to unpublish my Private calendar but this wasn't possible. When trying to unpublish it I get the error message "This calendar could not be unpublished. Authentication information may be incorrect."
    If I select the "Cange location..." menu entry in the context menu of the Private calendar I still see the webdav server address and the Login and Password fields are filled. But because this server no longer exists publishing is no longer possible. Which is fine with me.
    So, how can I get rid of the publishing? Because I get tons of error messages in system.log, too, for this behaviour. Everytime the system tries to publish this calendar...
    Thanks,
    Stefan.

    I am not much of a help, but I just wanted to say that my iCal just experienced the same problems for the first time today...

  • RMAN - specification does not match any archived log in the repository

    Hi All,
    Oracle 11G R2 on WIndows woo8 R2 Std Edition
    I am running RMAN (almost for the first time), and i am using a script previously used. As i am checking through the log, i notice some 'errors' though the backup finishes successfully.
    RMAN> crosscheck archivelog all;
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=352 device type=DISK
    specification does not match any archived log in the repository
    RMAN> crosscheck backupset;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
    2013_04_23\O1_MF_NCNNF_TAG20130423T134331_8QFL24F7_.BKP RECID=16 STAMP=813505412
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
    2013_04_23\O1_MF_ANNNN_TAG20130423T134334_8QFL26K1_.BKP RECID=17 STAMP=813505414
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
    2013_04_23\O1_MF_NCNNF_TAG20130423T134423_8QFL3S48_.BKP RECID=18 STAMP=813505465
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
    2013_04_23\O1_MF_ANNNN_TAG20130423T134427_8QFL3V9J_.BKP RECID=19 STAMP=813505467
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
    2013_04_23\O1_MF_NNNDF_TAG20130423T134428_8QFL3XDT_.BKP RECID=20 STAMP=813505469
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
    2013_04_23\O1_MF_NCSNF_TAG20130423T134428_8QFM4C5S_.BKP RECID=21 STAMP=813506507
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=D:\ORACLE\DATABASE\ORADATA\MMSPRD7\ORAFRA\MMSPRD7\BACKUPSET\
    2013_04_23\O1_MF_ANNNN_TAG20130423T140148_8QFM4DOT_.BKP RECID=22 STAMP=813506508
    Crosschecked 7 objects
    RMAN> crosscheck copy;
    released channel: ORA_DISK_1
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=352 device type=DISK
    specification does not match any datafile copy in the repository
    specification does not match any control file copy in the repository
    specification does not match any archived log in the repositorySo there are 2 instances of the errors:
    1) crosscheck archivelog all - when the error happens here, i think this means that there are no archived redo logs in the archivelog destination?? ..or something to that nature.
    2) crosscheck copy - not sure what the other errors mean here.
    Thx in advance!

    1) crosscheck archivelog all - when the error happens here, i think this means that there are no archived redo logs in the archivelog destination?? ..or something to that nature.
    2) crosscheck copy - not sure what the other errors mean here.
    specification does not match any archived log in the repositoryI don't see the error here, it's only a msg that mean : There is no files on XXX destination, which is normal when no files found.

  • Hangup transport archive log in primary and archive log apply

    Hi
    I am building Dataguard from 3-node primary cluster to 3-node standby cluster
    Oracle Version:10.2.0.4
    Operating system : LInux 64 bit
    After I restored standby database, I configured dataguard broker with wrong unique_name parameter in standby cluster using grid control
    after I corrected mistake, disabled dataguard broker parameters, delete dataguard broker files and reboot standby cluster but don't reboot primary cluster because is production enviroment.
    I have problem with following symptoms:
    -Hangup transport archive log while recovery database in standby then gap archivelog is produced.
    -Copy and register all archivelog gap in standby but don't apply archive log.
    - Don't register like applied in v$archived_log in primary the archives applied in standby manually.
    -RMAN command: "backup as COMPRESSED BACKUPSET tag 'Backup Full Disk' archivelog all not backed up delete all input;"
    don't delete in primary archive log applied because message " archive log is necessary"
    I think that is necessary reboot primary cluster.
    Please helpme

    Post the results of queries. It is difficult to understand.
    post from primary
    SQL> select thread#,max(sequence#) from v$archived_log group by thread#;select     ds.dest_id id
    ,     ad.status
    ,     ds.database_mode db_mode
    ,     ad.archiver type
    ,     ds.recovery_mode
    ,     ds.protection_mode
    ,     ds.standby_logfile_count "SRLs"
    ,     ds.standby_logfile_active active
    ,     ds.archived_seq#
    from     v$archive_dest_status     ds
    ,     v$archive_dest          ad
    where     ds.dest_id = ad.dest_id
    and     ad.status != 'INACTIVE'
    order by
         ds.dest_id
    Post from standby.
    SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
    select * from v$managed_standby;

  • Standby database is not applying redo logs due to missing archive log

    We use 9.2.0.7 Oracle Database. My goal is to create a physical standby database.
    I have followed all the steps necessary to fulfill this in Oracle Data Guard Concepts and Administration manual. Archived redo logs are transmitted from primary to standby database regularly. But the logs are not applied due to archive log gap.
    SQL> select process, status from v$managed_standby;
    PROCESS STATUS
    ARCH CONNECTED
    ARCH CONNECTED
    MRP0 WAIT_FOR_GAP
    RFS RECEIVING
    RFS ATTACHED
    SQL> select * from v$archive_gap;
    THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
    1 503 677
    I have tried to find the missing archives on the primary database, but was unable to. They have been deleted (somehow) regularly by the existing backup policy on the primary database. I have looked up the backups, but these archive logs are too old to be in the backup. Backup retention policy is 1 redundant backup of each file. I didn't save older backups as I didn't really need them from up to this point.
    I have cross checked (using rman crosscheck) the archive log copies on the primary database and deleted the "obsolete" copies of archive logs. But, v$archived_log view on the primary database only marked those entries as "deleted". Unfortunately, the standby database is still waiting for those logs to "close the gap" and doesn't apply the redo logs at all. I am reluctant to recreate the control file on the primary database as I'm afraid this occurred through the regular database backup operations, due to current backup retention policy and it probably might happen again.
    The standby creation procedure was done by using the data files from 3 days ago. The archive logs which are "producing the gap" are older than a month, and are probably unneeded for standby recovery.
    What shall I do?
    Kind regards and thanks in advance,
    Milivoj

    On a physical standby database
    To determine if there is an archive gap on your physical standby database, query the V$ARCHIVE_GAP view as shown in the following example:
    SQL> SELECT * FROM V$ARCHIVE_GAP;
    THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
    1 7 10
    The output from the previous example indicates your physical standby database is currently missing log files from sequence 7 to sequence 10 for thread 1.
    After you identify the gap, issue the following SQL statement on the primary database to locate the archived redo log files on your primary
    database (assuming the local archive destination on the primary database is LOG_ARCHIVE_DEST_1):
    SQL> SELECT NAME FROM V$ARCHIVED_LOG WHERE THREAD#=1 AND DEST_ID=1 AND 2> SEQUENCE# BETWEEN 7 AND 10;
    NAME
    /primary/thread1_dest/arcr_1_7.arc /primary/thread1_dest/arcr_1_8.arc /primary/thread1_dest/arcr_1_9.arc
    Copy these log files to your physical standby database and register them using the ALTER DATABASE REGISTER LOGFILE statement on your physical standby database. For example:
    SQL> ALTER DATABASE REGISTER LOGFILE
    '/physical_standby1/thread1_dest/arcr_1_7.arc';
    SQL> ALTER DATABASE REGISTER LOGFILE
    '/physical_standby1/thread1_dest/arcr_1_8.arc';
    After you register these log files on the physical standby database, you can restart Redo Apply.
    Note:
    The V$ARCHIVE_GAP fixed view on a physical standby database only returns the next gap that is currently blocking Redo Apply from continuing. After resolving the gap and starting Redo Apply, query the V$ARCHIVE_GAP fixed view again on the physical standby database to determine the next gap sequence, if there is one. Repeat this process until there are no more gaps.
    Restoring the archived logs from the backup set
    If the archived logs are not available in the archive destination then at that time we need to restore the required archived logs from the backup step. This task is accomplished in the following way.
    To restore range specified archived logs:
    Run {
    Set archivelog destination to '/oracle/arch/arch_restore'
    Restore archivelog from logseq=<xxxxx> until logseq=<xxxxxxx>
    To restore all the archived logs:
    Run {
    Set archivelog destination to '/oracle/arch/arch_restore';
    Restore archivelog all;
    }

  • Mysterious repeat log entries in System events log

    I tried unsuccessfully to share internet connection with 2 iMacs without router(That doesn't matter). But after this, my iMac (24" 2.8 GHz) not networked or on internet now shows this repeated log entries every minute:
    com.apple.launchd[1] (com.apple.InternetSharing): Throttling respawn: Will start in 10 seconds
    This message gets repeated every minute on System events log. Daily, Monthly maintenance was not done automatically earlier today on this iMac (usually it did without any problem) which was on all-night.
    I checked with Disk Utility, repaired permissions. Although no problems in working, this continuous log writings disturbs me.
    Thanks for any help & Happy New Year!
    Best.

    Thanks, V.K. Did that (was asked password). System log showed after restart:
    com.apple.launchd[1] (com.apple.InternetSharing[152]): Exited with exit code: 1
    com.apple.launchd[1] (com.apple.InternetSharing): Throttling respawn: Will start in 10 seconds
    com.apple.launchd[1] (com.apple.InternetSharing153): Exited with exit code: 1
    com.apple.launchd[1] (com.apple.InternetSharing): Throttling respawn: Will start in 10 seconds
    Then it started again the same way as above - with each aditional line each time as shown above. Thanks for sticking with me on this. Hope you will offer other suggestions.
    Best.

  • To Archive Log or Not to Archive Log

    I was recently in a discussion w/ a senior oracle dba who said that you shouldn't run your database in archive log mode if it is possible to take a complete cold backup each night. His recommendation was to have large enough redo logs where, in a days time, they wouldn't be overwritten by log switches. Are there any opinions out there on this?
    Thanks.

    This option depends on requirements on your DB.
    If your DB is in production state and must be running 24x7 and also data loss is not acceptable then best backup strategy is hot backups with RMAN (this option requires Archivelog mode).
    If your DB is not in production and data loss is acceptable then cold backup is enough but this backup strategy has some disadvantages.

  • For streams , database in Archive log mode or non archive log mode?

    Hello ,
    I have a basic question,
    To set up oracle streams, what should be the the database mode (archive log or non archive log mode)?
    Thanks in advance,
    Raj

    It needs to be in archive log mode..thts the place frm where it captures the necessary information....
    Kapil

  • RMAN failure for "archive-log ... not found in controlfile"

    Recovery Manager: Release 8.1.6.0.0 - Production
    RMAN> connect target sys/XXXX@cldb;
    2> connect catalog rman/XXXX@rmandb1;
    3>
    4> resync catalog;
    5>
    6> # Backup the database
    7> run {
    8> allocate channel ch1 type disk;
    9> backup incremental level 0 format
    10> '/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/backup_%t_%s_%p' database;
    11> sql 'alter system archive log current';
    12> }
    13>
    14> # Backup the archived redo logs
    15> run {
    16> allocate channel ch1 type disk;
    17>
    18> backup incremental level 0 format
    19> '/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/archivelog_%t_%s_%p' archivelog all;
    20> sql 'alter system archive log current';
    21> }
    22>
    23> # Backup the control file
    24> run {
    25> allocate channel ch1 type disk;
    26> sql 'alter database backup controlfile to trace';
    27> copy current controlfile to
    28> '/tools/cm/clearquest/orabackup/cldb.cqdbserver/controlfile.bak';
    29> }
    30>
    31>
    RMAN-06005: connected to target database: CLDB (DBID=1292102281)
    RMAN-06008: connected to recovery catalog database
    RMAN-03022: compiling command: resync
    RMAN-03023: executing command: resync
    RMAN-08002: starting full resync of recovery catalog
    RMAN-08004: full resync complete
    RMAN-03022: compiling command: allocate
    RMAN-03023: executing command: allocate
    RMAN-08030: allocated channel: ch1
    RMAN-08500: channel ch1: sid=17 devtype=DISK
    RMAN-03022: compiling command: backup
    RMAN-03023: executing command: backup
    RMAN-08008: channel ch1: starting incremental level 0 datafile backupset
    RMAN-08502: set_count=816 set_stamp=422358010 creation_time=22-FEB-01
    RMAN-08010: channel ch1: specifying datafile(s) in backupset
    RMAN-08522: input datafile fno=00001 name=/opt/orabase/oradata/cldb/system01.dbf
    ---snip----
    more like this
    ---snip----
    RMAN-08013: channel ch1: piece 1 created
    RMAN-08503: piece handle=/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/backup_422358010_816_1 comment=NONE
    RMAN-08525: backup set complete, elapsed time: 00:01:46
    RMAN-03023: executing command: partial resync
    RMAN-08003: starting partial resync of recovery catalog
    RMAN-08005: partial resync complete
    RMAN-03022: compiling command: sql
    RMAN-06162: sql statement: alter system archive log current
    RMAN-03023: executing command: sql
    RMAN-08031: released channel: ch1
    RMAN-03022: compiling command: allocate
    RMAN-03023: executing command: allocate
    RMAN-08030: allocated channel: ch1
    RMAN-08500: channel ch1: sid=17 devtype=DISK
    RMAN-03022: compiling command: backup
    RMAN-03025: performing implicit partial resync of recovery catalog
    RMAN-03023: executing command: partial resync
    RMAN-08003: starting partial resync of recovery catalog
    RMAN-08005: partial resync complete
    RMAN-03023: executing command: backup
    RMAN-08009: channel ch1: starting archivelog backupset
    RMAN-08502: set_count=817 set_stamp=422358179 creation_time=22-FEB-01
    RMAN-08014: channel ch1: specifying archivelog(s) in backup set
    RMAN-08504: input archivelog thread=1 sequence=85 recid=2610 stamp=422352397
    RMAN-08504: input archivelog thread=1 sequence=86 recid=2611 stamp=422352397
    ----snip----
    more similar stuff here
    ----snip----
    RMAN-08504: input archivelog thread=1 sequence=140 recid=2732 stamp=422358121
    RMAN-08013: channel ch1: piece 1 created
    RMAN-08503: piece handle=/tools/cm/clearquest/orabackup/cldb.cqdbserver/backup/archivelog_422358179_817_1 comment=NONE
    RMAN-08525: backup set complete, elapsed time: 00:00:17
    RMAN-08009: channel ch1: starting archivelog backupset
    RMAN-08502: set_count=818 set_stamp=422358197 creation_time=22-FEB-01
    RMAN-08014: channel ch1: specifying archivelog(s) in backup set
    ----snip----
    more like this
    ----snip----
    RMAN-08504: input archivelog thread=1 sequence=164 recid=2756 stamp=422358123
    RMAN-08504: input archivelog thread=1 sequence=165 recid=2757 stamp=422358123
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAG E STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03006: non-retryable error occurred during execution of command: backup
    RMAN-07004: unhandled exception during command execution on channel ch1
    RMAN-10035: exception raised in RPC: ORA-19571: archived-log recid 2011 stamp 419161314 not found in controlfile
    RMAN-10031: ORA-19571 occurred during call to DBMS_BACKUP_RESTORE.BACKUPARCHIVEDLOG
    I added the resync catalog command to the backup. But I am still getting this error. What is happening? I have the control_file_record_keep_time = 14 in the paramater file. Do I need to change this to something greater?
    null

    The error message is pointing to an inconsistency between what RMAN "thinks"
    should be there and what is in control files.
    There are a few things you can try to do
    1. Compare V$LOG, V$LOGFILE, etc. Some of these views are based on control files
    2. Shutdown and restart the instance.
    This may help in synchronizing control files
    with internal structures.
    3. Trace RMAN session using oradebug and even 10046 to find out what it is doing
    4. Dump entire controlfile to trace using
    alter session set events 'immediate trace name controlf level 10';
    Or dump loghist only
    alter session set events 'immediate trace name loghist level 4';
    This will dump 2**level entries.
    5. Re-create controlfiles with CREATE CONTROLFILE
    Regards,
    Sev

  • Error when I backup with rman plus archive log

    Hi All,
    I tried below command
    run {
    SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT';
    BACKUP DATABASE INCLUDE CURRENT CONTROLFILE PLUS ARCHIVELOG DELETE ALL INPUT;
    and that show below error
    archived log file name=+DATA/pimprd/archivelog/pimarch_2_95_698703544.arc RECID=128 STAMP=706186164
    archived log file name=+DATA/pimprd/archivelog/pimarch_2_96_698703544.arc RECID=130 STAMP=706186173
    Finished backup at 21-DEC-09
    ORACLE error from target database:
    ORA-03114: not connected to ORACLE
    Starting backup at 21-DEC-09
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=259 instance=pimdb1 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=153 RECID=113 STAMP=705896703
    input archived log thread=1 sequence=154 RECID=116 STAMP=705983105
    input archived log thread=1 sequence=155 RECID=119 STAMP=706069504
    archived log file name=+DATA/pimprd/archivelog/pimarch_2_95_698703544.arc RECID=128 STAMP=706186164
    archived log file name=+DATA/pimprd/archivelog/pimarch_2_96_698703544.arc RECID=130 STAMP=706186173
    Finished backup at 21-DEC-09
    ORACLE error from target database:
    ORA-03114: not connected to ORACLE
    Starting backup at 21-DEC-09
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    ORA-03114: not connected to ORACLE
    RMAN-03002: failure of backup plus archivelog command at 12/21/2009 11:00:18
    ORA-03114: not connected to ORACLE
    There are RAC 11.1.0.6.0 on AIX 5.3 with ASM.
    Please advise,
    Thank you,
    Hiko

    ็Hi All,
    I tried backup archivelog again and show same error,
    Line: -----
    rman target /
    Recovery Manager: Release 11.1.0.6.0 - Production on Mon Dec 21 14:48:29 2009
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    connected to target database: PIMDB (DBID=3834713912)
    RMAN> run
    2> {
    3> backup archivelog all;
    4> }
    Starting backup at 21-DEC-09
    current log archived
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=275 instance=pimdb1 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=161 RECID=131 STAMP=706190624
    input archived log thread=1 sequence=162 RECID=133 STAMP=706200525
    input archived log thread=2 sequence=97 RECID=132 STAMP=706190625
    input archived log thread=2 sequence=98 RECID=134 STAMP=706200526
    channel ORA_DISK_1: starting piece 1 at 21-DEC-09
    channel ORA_DISK_1: finished piece 1 at 21-DEC-09
    piece handle=/oradata/backup/pimdb/rman/pimdb_Fulldata_20091221_97_1.bck tag=TAG20091221T144854 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    Finished backup at 21-DEC-09
    Starting Control File and SPFILE Autobackup at 21-DEC-09
    piece handle=/oradata/backup/pimdb/rman/pimdb_Controlfile_c-3834713912-20091221-02 comment=NONE
    Finished Control File and SPFILE Autobackup at 21-DEC-09
    ORACLE error from target database:
    ORA-03114: not connected to ORACLE
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    ORA-03114: not connected to ORACLE
    RMAN-03009: failure of REFAF command on default channel at 12/21/2009 14:59:33
    ORA-03114: not connected to ORACLE
    RMAN> exit
    Recovery Manager complete.
    Line: -----
    And I check in alert log file that show below error
    Line: -----
    Mon Dec 21 14:48:44 2009
    Thread 1 advanced to log sequence 163
    Current log# 1 seq# 163 mem# 0: +DATA/pimdb/onlinelog/group_1.282.698703549
    Mon Dec 21 14:49:17 2009
    Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x3E00000000] [PC:0x10180AA48, kxfpg1srv()+04e8]
    Errors in file /oracle/diag/rdbms/pimdb/pimdb1/trace/pimdb1_ora_5095646.trc (incident=64044):
    ORA-07445: exception encountered: core dump [kxfpg1srv()+04e8] [SIGSEGV] [ADDR:0x3E00000000] [PC:0x10180AA48] [Address not mapped to object] []
    Incident details in: /oracle/diag/rdbms/pimdb/pimdb1/incident/incdir_64044/pimdb1_ora_5095646_i64044.trc
    Mon Dec 21 14:49:31 2009
    Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x3E00000000] [PC:0x10180AA48, kxfpg1srv()+04e8]
    Errors in file /oracle/diag/rdbms/pimdb/pimdb1/trace/pimdb1_m000_1831050.trc (incident=64163):
    ORA-07445: exception encountered: core dump [kxfpg1srv()+04e8] [SIGSEGV] [ADDR:0x3E00000000] [PC:0x10180AA48] [Address not mapped to object] []
    Incident details in: /oracle/diag/rdbms/pimdb/pimdb1/incident/incdir_64163/pimdb1_m000_1831050_i64163.trc
    Mon Dec 21 14:49:33 2009
    Trace dumping is performing id=[cdmp_20091221144933]
    Mon Dec 21 14:49:34 2009
    Sweep Incident[64163]: completed
    Mon Dec 21 14:59:33 2009
    Process 0x70000020477df88 appears to be hung while dumping
    Current time = 1584185732, process death time = 1584124482 interval = 60000
    Attempting to kill process 0x70000020477df88 with OS pid = 5095646
    OSD kill succeeded for process 70000020477df88
    Line: -----
    Please advice,
    Thank you
    Hiko

  • RMAN: How to apply Archive Logs after recoverying of all physical files

    Hi;
    I am using RMAN Oracle10g; my test database has being corrupted. I have already taken 0 level backup through this command
    run {
    allocate channel c1 type disk;
    backup incremental level 0 tag = Test_Weekly_database format 'O:\rman\backup\Full_Weekly_%d_%s_%p_%t'(database);
    release channel c1;
    configure controlfile autobackup format for device type disk to 'O:\rman\backup\Auto_Ctrl_weekly_%F';
    allocate channel c1 type disk;
    sql 'alter system archive log current';
    BACKUP tag = Test_Weekly_Arch ARCHIVELOG UNTIL TIME 'SYSDATE-7' format 'O:\rman\backup\Archive_weekly_%d_%s_%p_%t';
    DELETE ARCHIVELOG UNTIL TIME 'SYSDATE-7';
    release channel c1;
    After backing up I inserted few records in TEST123 table. And switch current log file.
    Then my database has been corrupted. Now I have last 0 level backup (RMAN) and archive logs files on OS level.
    I am recovering my database with the following commands; but archive logs have not being applied. And my inserted records were not presented in TEST123 table.
    Kindly guide me
    SQL> startup nomount
    CMD> RMAN target=/
    RMAN>set DBID 1168995671
    RMAN>RUN {
    SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'O:\rman\backup\Auto_Ctrl_weekly_%F';
    RESTORE CONTROLFILE from autobackup;
    RMAN> ALTER DATABASE MOUNT;
    RMAN> RESTORE DATABASE CHECK READONLY;
    RMAN> RECOVER DATABASE NOREDO;
    RMAN> restore archivelog all;
    SQL> startup mount
    SQL> alter database backup controlfile to trace;
    SQL> shut immediate
    SQL> startup nomount
    SQL> CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS ARCHIVELOG................;
    SQL> alter database open resetlogs
    ---Database altered.
    SQL> select * from TEST123;
    Not record found
    regards;
    Asim

    Dear Khurram;
    Kindly advise where i m worrg???????
    C:\>RMAN target=/
    RMAN> set DBID 1168995671
    executing command: SET DBID
    RMAN> RUN {
    2> SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'O:\rman\backup\Auto_Ctrl_weekly_%F';
    3> RESTORE CONTROLFILE from autobackup;
    4> }
    executing command: SET CONTROLFILE AUTOBACKUP FORMAT
    Starting restore at 27-DEC-07
    using channel ORA_DISK_1
    recovery area destination: O:\rman\backup
    database name (or database unique name) used for search: ORCL
    channel ORA_DISK_1: no autobackups found in the recovery area
    channel ORA_DISK_1: looking for autobackup on day: 20071227
    channel ORA_DISK_1: autobackup found: O:\rman\backup\Auto_Ctrl_weekly_c-11689956
    71-20071227-04
    channel ORA_DISK_1: control file restore from autobackup complete
    output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL01.CTL
    output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL02.CTL
    output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL03.CTL
    Finished restore at 27-DEC-07
    RMAN> ALTER DATABASE MOUNT;
    database mounted
    released channel: ORA_DISK_1
    RMAN> RESTORE DATABASE CHECK READONLY;
    Starting restore at 27-DEC-07
    Starting implicit crosscheck backup at 27-DEC-07
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=155 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=154 devtype=DISK
    Crosschecked 9 objects
    Finished implicit crosscheck backup at 27-DEC-07
    Starting implicit crosscheck copy at 27-DEC-07
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    Finished implicit crosscheck copy at 27-DEC-07
    searching for all files in the recovery area
    cataloging files...
    no files cataloged
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF
    restoring datafile 00002 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\UNDOTBS01.DBF
    restoring datafile 00003 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSAUX01.DBF
    restoring datafile 00004 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF
    restoring datafile 00005 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\TEST.DBF
    restoring datafile 00006 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\TEST2
    channel ORA_DISK_1: reading from backup piece O:\RMAN\BACKUP\FULL_WEEKLY_ORCL_3_
    1_642420573
    channel ORA_DISK_1: restored backup piece 1
    piece handle=O:\RMAN\BACKUP\FULL_WEEKLY_ORCL_3_1_642420573 tag=Test_WEEKLY_DATAB
    ASE
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:46
    Finished restore at 27-DEC-07
    RMAN> restore archivelog all;
    archive log thread 1 sequence 1 is already on disk as file O:\ARCHIVE\ARC00001_0642356125.001
    archive log thread 1 sequence 2 is already on disk as file O:\ARCHIVE\ARC00002_0642356125.001
    archive log thread 1 sequence 3 is already on disk as file O:\ARCHIVE\ARC00003_0642356125.001
    archive log thread 1 sequence 4 is already on disk as file O:\ARCHIVE\ARC00004_0642356125.001
    archive log thread 1 sequence 5 is already on disk as file O:\ARCHIVE\ARC00005_0642356125.001
    archive log thread 1 sequence 6 is already on disk as file O:\ARCHIVE\ARC00006_0642356125.001
    archive log thread 1 sequence 7 is already on disk as file O:\ARCHIVE\ARC00007_0642356125.001
    archive log thread 1 sequence 8 is already on disk as file O:\ARCHIVE\ARC00008_0642356125.001
    archive log thread 1 sequence 9 is already on disk as file O:\ARCHIVE\ARC00009_0642356125.001
    archive log thread 1 sequence 10 is already on disk as file O:\ARCHIVE\ARC00010_0642356125.001
    archive log thread 1 sequence 11 is already on disk as file O:\ARCHIVE\ARC00011_0642356125.001
    archive log thread 1 sequence 12 is already on disk as file O:\ARCHIVE\ARC00012_0642356125.001
    channel ORA_DISK_1: starting archive log restore to default destination
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=15
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=16
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=17
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=18
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=19
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=20
    channel ORA_DISK_1: reading from backup piece O:\RMAN\BACKUP\ARCHIVE_WEEKLY_ORCL_5_1_642420630
    channel ORA_DISK_1: restored backup piece 1
    piece handle=O:\RMAN\BACKUP\ARCHIVE_WEEKLY_ORCL_5_1_642420630 tag=Test_WEEKLY_ARCH
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:08
    Finished restore at 27-DEC-07
    RMAN> ALTER DATABASE OPEN;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of alter db command at 12/27/2007 10:27:10
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF'
    Regards;
    Asim

  • RMAN-20242: specification does not match any archive log in the recovery ca

    Hi,
    I'm working with an 9i Oracle RAC (yes, I know this version is out of support...). I'm launching my backup from node 1 with this script
    run {
    sql 'alter system switch logfile'
    sql 'alter system archive log current'
    allocate channel TSM1 type 'sbt_tape' connect *
    parms='ENV=(TDPO_OPTFILE=/home/adsmadm/rman_INF01T01/opt/tdpo.opt)'
    allocate channel TSM2 type 'sbt_tape' connect *
    parms='ENV=(TDPO_OPTFILE=/home/adsmadm/rman_INF01T01/opt/tdpo.opt)'
    backup
    format 'brman_arch_%s_%p'
    (archivelog like '/logs/bbdd/oracle/INF01T01/archiver/%' channel TSM1 delete input )
    (archivelog like '/logs/bbdd/oracle/INF01T03/archiver/%' channel TSM2 delete input )
    release channel TSM2
    release channel TSM1
    And fail with this error:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 08/13/2012 22:36:43
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archive log in the recovery catalog
    I've take a look to the archives directories and both nodes have archives:
    ora10g:/opt/ora10g > ls -lrt /logs/bbdd/oracle/INF01T01/archiver
    total 97896
    -rw-r----- 1 ora10g dba 2048 Aug 13 22:36 T0001S00000061440648489222.ARC
    -rw-rw---- 1 ora10g dba 38132224 Aug 13 22:36 T0001S00000061430648489222.ARC
    -rw-r----- 1 ora10g dba 11984896 Aug 13 22:36 T0002S00000044040648489222.ARC
    ora10g:/opt/ora10g > ls -lrt /logs/bbdd/oracle/INF01T03/archiver
    total 392984
    -rw-r----- 1 ora10g dba 49364992 Mar 24 2009 T0002S00000007020648489222.ARC
    -rw-r----- 1 ora10g dba 49364992 Mar 25 2009 T0002S00000007030648489222.ARC
    -rw-rw---- 1 ora10g dba 19314688 Mar 25 2009 T0002S00000007040648489222.ARC
    -rw-rw---- 1 ora10g dba 4733952 Mar 25 2009 T0002S00000007050648489222.ARC
    -rw-rw---- 1 ora10g dba 4608 Apr 09 2009 T0002S00000007440648489222.ARC
    -rw-rw---- 1 ora10g dba 2541056 Sep 26 2009 T0002S00000015420648489222.ARC
    -rw-rw---- 1 ora10g dba 49373184 Sep 28 2009 T0002S00000015430648489222.ARC
    -rw-rw---- 1 ora10g dba 3410432 Feb 11 2010 T0002S00000018680648489222.ARC
    -rw-rw---- 1 ora10g dba 599552 Feb 12 2010 T0002S00000018710648489222.ARC
    -rw-rw---- 1 ora10g dba 6574080 Mar 03 2010 T0002S00000019200648489222.ARC
    -rw-rw---- 1 ora10g dba 1663488 Mar 08 2010 T0002S00000019340648489222.ARC
    -rw-rw---- 1 ora10g dba 431104 Apr 07 2010 T0002S00000020160648489222.ARC
    -rw-rw---- 1 ora10g dba 13811712 Apr 19 2010 T0002S00000020460648489222.ARC
    I've tried to made a crosscheck but, only found node1 archives:
    RMAN> change archivelog all crosscheck;
    validation succeeded for archived log
    archive log filename=/logs/bbdd/oracle/INF01T01/archiver/T0001S00000061430648489222.ARC recid=10685 stamp=791246196
    validation succeeded for archived log
    archive log filename=/logs/bbdd/oracle/INF01T01/archiver/T0001S00000061440648489222.ARC recid=10686 stamp=791246196
    validation succeeded for archived log
    archive log filename=/logs/bbdd/oracle/INF01T01/archiver/T0002S00000044040648489222.ARC recid=10687 stamp=791246197
    Crosschecked 3 objects
    Any idea about the way to solve it?
    Thanks in advance!
    dbajug

    Hi,
    Connect to target through rman
    crosscheck archivelog all;
    Then re run the backup. This will work if those two locations provided are archive log destinations.
    In case the issue still persists then
    Connect to target through rman
    catalog start with '/logs/bbdd/oracle/INF01T01/archiver/';
    catalog start with '/logs/bbdd/oracle/INF01T03/archiver/';
    Then re run the backup.
    Thanks,
    Vivek
    Edited by: 952807 on Aug 16, 2012 5:21 PM

Maybe you are looking for