Archive log file error

hi
i have take offline back. now i am taking archive log file backup
there is giving error
BR0002I BRARCHIVE 6.40 (34)
BR0006I Start of offline redo log processing: aechsfgv.sve 2010-01-08 15.26.53
BR0477I Oracle pfile D:\ORACLE\HOD\920\database\initHOD.ora created from spfile D:\ORACLE\HOD\920\database\spfi
leHOD.ora
BR0013W No offline redo log files found for processing
BR0007I End of offline redo log processing: aechsfgv.sve 2010-01-08 15.26.56
BR0280I BRARCHIVE time stamp: 2010-01-08 15.26.57
BR0004I BRARCHIVE completed successfully with warnings
BR0292I Execution of BRARCHIVE finished with return code 1
BR0668I Warnings or errors occurred - you can continue to ignore them or go back to repeat the last action
BR0280I BRTOOLS time stamp: 2010-01-08 15.26.57
BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:

Hello,
Have a look in oraarch if new archivelogs are correctly generated in the directory and if name look like other files.
C:\>SQLPLUS / AS SYSDBA
SQL>alter system switch logfile;
Regards

Similar Messages

  • Error after Restoring Datafiles in Archivelog but missing archive log files

    Hi all,
    I have taken backup yesterday monrning in Archive log mode but have lost all the archive log files. Yesterday night i have restored my DB .
    I m happy to have my datafile contents till yesterday morning.
    But after restoring when i try to open th DB, i m facing the following errors:
    SQL>          Startup open;
    Oracle instance started but in mounted stagell
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL>         alter database open resetlogs;
    Error: ORA-01113: file 1 needs media recovery
              ORA-01110: data file 1: 'E:\oracle\'<SID>\sapdata1\SYSTEM_1\SYSTEM.DATA1'
    SQL>         recover database using backup controlfile until cancel;
    ORA-00279 : change 26627919 generated at DATE TIMEneeded for thread 1
    ORA-00289 : Suggestion E:\ORACLE\<SID>\ORAARCH\<SID>ARCHARC03020_0683715008.001
    ORA-00280: change 266277189 for thread 1 is in sequence #3020
    ORA - 01112: media recovery not started
    SQL>   recover;
    ORA-00283: recovery session cancelled due to errors
    ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
    Alert Log File:
    Starting up ORACLE RDBMS Version: 10.2.0.2.0.
    System parameters with non-default values:
      processes                = 80
      sessions                 = 96
      event                    = 10191 trace name context forever, level 1
      sga_max_size             = 633339904
      shared_pool_size         = 301989888
      shared_pool_reserved_size= 30183260
      filesystemio_options     = setall
      control_files            = E:\ORACLE\IE6\ORIGLOGA\CNTRL\CNTRLIE6.DBF, E:\ORACLE\IE6\ORIGLOGB\CNTRL\CNTRLIE6.DBF, E:\ORACLE\IE6\SAPDATA1\CNTRL\CNTRLIE6.DBF
      control_file_record_keep_time= 30
      db_block_size            = 8192
      db_cache_size            = 301989888
      compatible               = 10.2.0
      log_archive_dest         = E:\oracle\IE6\oraarch\IE6arch
      log_buffer               = 2854912
      log_checkpoint_interval  = 0
      db_files                 = 254
      log_checkpoints_to_alert = TRUE
      dml_locks                = 4000
      undo_management          = AUTO
      undo_tablespace          = PSAPUNDO
      undo_retention           = 43200
      recyclebin               = off
      remote_os_authent        = TRUE
      remote_login_passwordfile= EXCLUSIVE
      job_queue_processes      = 1
      background_dump_dest     = E:\ORACLE\IE6\SAPTRACE\BACKGROUND
      user_dump_dest           = E:\ORACLE\IE6\SAPTRACE\USERTRACE
      core_dump_dest           = E:\ORACLE\IE6\SAPTRACE\BACKGROUND
      optimizer_features_enable= 10.2.0.1
      sort_area_size           = 2097152
      sort_area_retained_size  = 0
      db_name                  = IE6
      open_cursors             = 800
      optimpeek_user_binds   = FALSE
      pga_aggregate_target     = 402443468
      workarea_size_policy     = AUTO
      statistics_level         = typical
    PMON started with pid=2, OS id=804
    PSP0 started with pid=3, OS id=9580
    MMAN started with pid=4, OS id=5840
    DBW0 started with pid=5, OS id=8136
    LGWR started with pid=6, OS id=8712
    CKPT started with pid=7, OS id=1620
    SMON started with pid=8, OS id=7084
    RECO started with pid=9, OS id=9576
    CJQ0 started with pid=10, OS id=9156
    MMON started with pid=11, OS id=6000
    MMNL started with pid=12, OS id=2856
    Sat Apr 18 04:01:29 2009
    ALTER DATABASE   MOUNT
    Sat Apr 18 04:01:33 2009
    Setting recovery target incarnation to 1
    Sat Apr 18 04:01:33 2009
    Successful mount of redo thread 1, with mount id 1124466585
    Sat Apr 18 04:01:33 2009
    Database mounted in Exclusive Mode
    Completed: ALTER DATABASE   MOUNT
    Sat Apr 18 04:01:34 2009
    ALTER DATABASE OPEN
    ORA-1589 signalled during: ALTER DATABASE OPEN...
    Sat Apr 18 04:02:13 2009
    alter database open resetlogs
    Sat Apr 18 04:02:13 2009
    ORA-1245 signalled during: alter database open resetlogs...
    Sat Apr 18 04:11:05 2009
    ALTER DATABASE RECOVER DATABASE UNTIL CANCEL
    Sat Apr 18 04:11:05 2009
    Media Recovery Start
    Sat Apr 18 04:11:06 2009
    Media Recovery failed with error 1610
    ORA-283 signalled during: ALTER DATABASE RECOVER DATABASE UNTIL CANCEL...
    Sat Apr 18 04:11:28 2009
    ALTER DATABASE RECOVER DATABASE USING BACKUP CONTROLFILE
    Sat Apr 18 04:11:28 2009
    Media Recovery Start
    parallel recovery started with 3 processes
    ORA-279 signalled during: ALTER DATABASE RECOVER DATABASE USING BACKUP CONTROLFILE...
    Sat Apr 18 04:17:23 2009
    ALTER DATABASE RECOVER  database using backup controlfile until cancel 
    Sat Apr 18 04:17:23 2009
    Media Recovery Start
    ORA-275 signalled during: ALTER DATABASE RECOVER  database using backup controlfile until cancel  ...
    Any suggestions pls..............
    Thanks & Regards,
    Subbu

    Hello Subbu,
    > I have taken backup yesterday monrning in Archive log mode but have lost all the archive log files.
    You mean you have taken an online backup and lost all your archive log files after that online backup?
    SQL> alter database open resetlogs;
    Error: ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: 'E:\oracle\'<SID>\sapdata1\SYSTEM_1\SYSTEM.DATA1'
    SQL> recover database using backup controlfile until cancel;
    ORA-00279 : change 26627919 generated at DATE TIMEneeded for thread 1
    ORA-00289 : Suggestion E:\ORACLE\<SID>\ORAARCH\<SID>ARCHARC03020_0683715008.001
    ORA-00280: change 266277189 for thread 1 is in sequence #3020
    To perform a recovery with an online backup you will need all archive log files until the end of the online backup. If you have lost them you are not able to recover (or open) your database in a consistent state.
    So the only suggestion we can do is:
    You need the archive log files that were created during the online backup to perform an incomplete recovery ... if they are gone you can not restore your database.
    Regards
    Stefan

  • I have one problem with Data Guard. My archive log files are not applied.

    I have one problem with Data Guard. My archive log files are not applied. However I have received all archive log files to my physical Standby db
    I have created a Physical Standby database on Oracle 10gR2 (Windows XP professional). Primary database is on another computer.
    In Enterprise Manager on Primary database it looks ok. I get the following message “Data Guard status Normal”
    But as I wrote above ”the archive log files are not applied”
    After I created the Physical Standby database, I have also done:
    1. I connected to the Physical Standby database instance.
    CONNECT SYS/SYS@luda AS SYSDBA
    2. I started the Oracle instance at the Physical Standby database without mounting the database.
    STARTUP NOMOUNT PFILE=C:\oracle\product\10.2.0\db_1\database\initluda.ora
    3. I mounted the Physical Standby database:
    ALTER DATABASE MOUNT STANDBY DATABASE
    4. I started redo apply on Physical Standby database
    alter database recover managed standby database disconnect from session
    5. I switched the log files on Physical Standby database
    alter system switch logfile
    6. I verified the redo data was received and archived on Physical Standby database
    select sequence#, first_time, next_time from v$archived_log order by sequence#
    SEQUENCE# FIRST_TIME NEXT_TIME
    3 2006-06-27 2006-06-27
    4 2006-06-27 2006-06-27
    5 2006-06-27 2006-06-27
    6 2006-06-27 2006-06-27
    7 2006-06-27 2006-06-27
    8 2006-06-27 2006-06-27
    7. I verified the archived redo log files were applied on Physical Standby database
    select sequence#,applied from v$archived_log;
    SEQUENCE# APP
    4 NO
    3 NO
    5 NO
    6 NO
    7 NO
    8 NO
    8. on Physical Standby database
    select * from v$archive_gap;
    No rows
    9. on Physical Standby database
    SELECT MESSAGE FROM V$DATAGUARD_STATUS;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no SRL' ARCH
    ARC1: Becoming the heartbeat ARCH
    Attempt to start background Managed Standby Recovery process
    MRP0: Background Managed Standby Recovery process started
    Managed Standby Recovery not using Real Time Apply
    MRP0: Background Media Recovery terminated with error 1110
    MRP0: Background Media Recovery process shutdown
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[1]: Assigned to RFS process 2148
    RFS[1]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[2]: Assigned to RFS process 2384
    RFS[2]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[3]: Assigned to RFS process 3188
    RFS[3]: Identified database type as 'physical standby'
    Primary database is in MAXIMUM PERFORMANCE mode
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[3]: No standby redo logfiles created
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[4]: Assigned to RFS process 3168
    RFS[4]: Identified database type as 'physical standby'
    RFS[4]: No standby redo logfiles created
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[3]: No standby redo logfiles created
    10. on Physical Standby database
    SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
    PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    RFS IDLE 0 0 0 0
    RFS IDLE 0 0 0 0
    RFS IDLE 1 9 13664 2
    RFS IDLE 0 0 0 0
    10) on Primary database:
    select message from v$dataguard_status;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    ARCm: Becoming the 'no FAL' ARCH
    ARCm: Becoming the 'no SRL' ARCH
    ARCd: Becoming the heartbeat ARCH
    Error 1034 received logging on to the standby
    Error 1034 received logging on to the standby
    LGWR: Error 1034 creating archivelog file 'luda'
    LNS: Failed to archive log 3 thread 1 sequence 7 (1034)
    FAL[server, ARCh]: Error 1034 creating remote archivelog file 'luda'
    11)on primary db
    select name,sequence#,applied from v$archived_log;
    NAME SEQUENCE# APP
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00003_0594204176.001 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00004_0594204176.001 4 NO
    Luda 4 NO
    Luda 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00005_0594204176.001 5 NO
    Luda 5 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00006_0594204176.001 6 NO
    Luda 6 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00007_0594204176.001 7 NO
    Luda 7 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00008_0594204176.001 8 NO
    Luda 8 NO
    12) on standby db
    select name,sequence#,applied from v$archived_log;
    NAME SEQUENCE# APP
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00004_0594204176.001 4 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00003_0594204176.001 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00005_0594204176.001 5 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00006_0594204176.001 6 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00007_0594204176.001 7 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00008_0594204176.001 8 NO
    13) my init.ora files
    On standby db
    irina.__db_cache_size=79691776
    irina.__java_pool_size=4194304
    irina.__large_pool_size=4194304
    irina.__shared_pool_size=75497472
    irina.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0\admin\luda\adump'
    *.background_dump_dest='C:\oracle\product\10.2.0\admin\luda\bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\luda\luda.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0\admin\luda\cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_file_name_convert='luda','irina'
    *.db_name='irina'
    *.db_unique_name='luda'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
    *.fal_client='luda'
    *.fal_server='irina'
    *.job_queue_processes=10
    *.log_archive_config='DG_CONFIG=(irina,luda)'
    *.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/luda/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=luda'
    *.log_archive_dest_2='SERVICE=irina LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=irina'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=30
    *.log_file_name_convert='C:/oracle/product/10.2.0/oradata/irina/','C:/oracle/product/10.2.0/oradata/luda/'
    *.open_cursors=300
    *.pga_aggregate_target=16777216
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=167772160
    *.standby_file_management='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0\admin\luda\udump'
    On primary db
    irina.__db_cache_size=79691776
    irina.__java_pool_size=4194304
    irina.__large_pool_size=4194304
    irina.__shared_pool_size=75497472
    irina.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0/admin/irina/adump'
    *.background_dump_dest='C:\oracle\product\10.2.0/admin/irina/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\irina\control01.ctl','C:\oracle\product\10.2.0\oradata\irina\control02.ctl','C:\oracle\product\10.2.0\oradata\irina\control03.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0/admin/irina/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_file_name_convert='luda','irina'
    *.db_name='irina'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
    *.fal_client='irina'
    *.fal_server='luda'
    *.job_queue_processes=10
    *.log_archive_config='DG_CONFIG=(irina,luda)'
    *.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/irina/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=irina'
    *.log_archive_dest_2='SERVICE=luda LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=luda'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=30
    *.log_file_name_convert='C:/oracle/product/10.2.0/oradata/luda/','C:/oracle/product/10.2.0/oradata/irina/'
    *.open_cursors=300
    *.pga_aggregate_target=16777216
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=167772160
    *.standby_file_management='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0/admin/irina/udump'
    Please help me!!!!

    Hi,
    After several tries my redo logs are applied now. I think in my case it had to do with the tnsnames.ora. At this moment I have both database in both tnsnames.ora files using the SID and not the SERVICE_NAME.
    Now I want to use DGMGRL. Adding a configuration and a stand-by database is working fine, but when I try to enable the configuration DGMGRL gives no feedback and it looks like it is hanging. The log, although says that it succeeded.
    In another session 'show configuration' results in the following, confirming that the enable succeeded.
    DGMGRL> show configuration
    Configuration
    Name: avhtest
    Enabled: YES
    Protection Mode: MaxPerformance
    Fast-Start Failover: DISABLED
    Databases:
    avhtest - Primary database
    avhtestls53 - Physical standby database
    Current status for "avhtest":
    Warning: ORA-16610: command 'ENABLE CONFIGURATION' in progress
    It there anybody that experienced the same problem and/or knows the solution to this?
    With kind regards,
    Martin Schaap

  • How to recover the database when some of the archive log file get deleted.

    I am facing a problem with Oracle database, which is related to archivelogs.
    Our development database is running in archivelog mode, but we don't have backups scheduled and have no recovery catalog.
    When the database was in running condition, disk got full, so some archivelogs were deleted manually.
    After this they restarted the DB, and now DB is not coming up. Errors are as follows:
    SQL> startup
    ORACLE instance started.
    Total System Global Area 1444383504 bytes
    Fixed Size 731920 bytes
    Variable Size 486539264 bytes
    Database Buffers 956301312 bytes
    Redo Buffers 811008 bytes
    Database mounted.
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '/export/home/oracle/dev/ADVFRW/ADVFRW.system'
    SQL> recover datafile '/export/home/oracle/dev/ADVFRW/ADVFRW.system'
    ORA-00283: recovery session canceled due to errors
    ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
    SQL> recover database using backup controlfile;
    ORA-00279: change 215548705 generated at 09/02/2008 17:06:10 needed for thread
    1
    ORA-00289: suggestion :
    /export/home/oracle/dev/ADVFRW/ADVFRW.archivelog1/LOG_ADVFRW_1107_1.ARC
    ORA-00280: change 215548705 for thread 1 is in sequence #1107
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /export/home/oracle/dev/ADVFRW/ADVFRW.archivelog1/LOG_ADVFRW_1107_1.ARC
    ORA-00308: cannot open archived log
    '/export/home/oracle/dev/ADVFRW/ADVFRW.archivelog1/LOG_ADVFRW_1107_1.ARC'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    CANCEL
    Media recovery cancelled.
    SQL>
    1. How to recover the database and bring it online
    Any help will be highly appreciated.
    With Regards
    Hemant Joshi
    Edited by: hem_Kec on Sep 7, 2008 9:07 AM

    Hi,
    Archive log files are the copies of redolog files.As redo log files are circularly overwritten,oracle generates archive log file of the corresponding redo logfiles being overwritten.So if you have a backup that dates back to 10 am in the morning and if your database creashed at 3 pm,you cannot use the redo log files alone as they have incomplete information.To completely recover the database upto 3 pm,you need archive log files generated between 10 am to 3 pm. In your case since you are missing one archive log file,you cannot perform complete recovery and hence would suffer data loss.

  • Data Guard. My archive log files are not applied.

    I have one problem with Data Guard. My archive log files are not applied. However I have received all archive log files to my physical Standby db
    I have created a Physical Standby database on Oracle 10gR2 (Windows XP professional). Primary database is on another computer.
    In Enterprise Manager on Primary database it looks ok. I get the following message “Data Guard status Normal”
    But as I wrote above ”the archive log files are not applied”
    After I created the Physical Standby database, I have also done:
    1. I connected to the Physical Standby database instance.
    CONNECT SYS/SYS@luda AS SYSDBA
    2. I started the Oracle instance at the Physical Standby database without mounting the database.
    STARTUP NOMOUNT PFILE=C:\oracle\product\10.2.0\db_1\database\initluda.ora
    3. I mounted the Physical Standby database:
    ALTER DATABASE MOUNT STANDBY DATABASE
    4. I started redo apply on Physical Standby database
    alter database recover managed standby database disconnect from session
    5. I switched the log files on Physical Standby database
    alter system switch logfile
    6. I verified the redo data was received and archived on Physical Standby database
    select sequence#, first_time, next_time from v$archived_log order by sequence#
    SEQUENCE# FIRST_TIME NEXT_TIME
    3 2006-06-27 2006-06-27
    4 2006-06-27 2006-06-27
    5 2006-06-27 2006-06-27
    6 2006-06-27 2006-06-27
    7 2006-06-27 2006-06-27
    8 2006-06-27 2006-06-27
    7. I verified the archived redo log files were applied on Physical Standby database
    select sequence#,applied from v$archived_log;
    SEQUENCE# APP
    4 NO
    3 NO
    5 NO
    6 NO
    7 NO
    8 NO
    8. on Physical Standby database
    select * from v$archive_gap;
    No rows
    9. on Physical Standby database
    SELECT MESSAGE FROM V$DATAGUARD_STATUS;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no SRL' ARCH
    ARC1: Becoming the heartbeat ARCH
    Attempt to start background Managed Standby Recovery process
    MRP0: Background Managed Standby Recovery process started
    Managed Standby Recovery not using Real Time Apply
    MRP0: Background Media Recovery terminated with error 1110
    MRP0: Background Media Recovery process shutdown
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[1]: Assigned to RFS process 2148
    RFS[1]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[2]: Assigned to RFS process 2384
    RFS[2]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[3]: Assigned to RFS process 3188
    RFS[3]: Identified database type as 'physical standby'
    Primary database is in MAXIMUM PERFORMANCE mode
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[3]: No standby redo logfiles created
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[4]: Assigned to RFS process 3168
    RFS[4]: Identified database type as 'physical standby'
    RFS[4]: No standby redo logfiles created
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[3]: No standby redo logfiles created
    10. on Physical Standby database
    SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
    PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    RFS IDLE 0 0 0 0
    RFS IDLE 0 0 0 0
    RFS IDLE 1 9 13664 2
    RFS IDLE 0 0 0 0
    10) on Primary database:
    select message from v$dataguard_status;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    ARCm: Becoming the 'no FAL' ARCH
    ARCm: Becoming the 'no SRL' ARCH
    ARCd: Becoming the heartbeat ARCH
    Error 1034 received logging on to the standby
    Error 1034 received logging on to the standby
    LGWR: Error 1034 creating archivelog file 'luda'
    LNS: Failed to archive log 3 thread 1 sequence 7 (1034)
    FAL[server, ARCh]: Error 1034 creating remote archivelog file 'luda'
    11)on primary db
    select name,sequence#,applied from v$archived_log;
    NAME SEQUENCE# APP
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00003_0594204176.001 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00004_0594204176.001 4 NO
    Luda 4 NO
    Luda 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00005_0594204176.001 5 NO
    Luda 5 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00006_0594204176.001 6 NO
    Luda 6 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00007_0594204176.001 7 NO
    Luda 7 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00008_0594204176.001 8 NO
    Luda 8 NO
    12) on standby db
    select name,sequence#,applied from v$archived_log;
    NAME SEQUENCE# APP
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00004_0594204176.001 4 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00003_0594204176.001 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00005_0594204176.001 5 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00006_0594204176.001 6 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00007_0594204176.001 7 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00008_0594204176.001 8 NO
    13) my init.ora files
    On standby db
    irina.__db_cache_size=79691776
    irina.__java_pool_size=4194304
    irina.__large_pool_size=4194304
    irina.__shared_pool_size=75497472
    irina.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0\admin\luda\adump'
    *.background_dump_dest='C:\oracle\product\10.2.0\admin\luda\bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\luda\luda.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0\admin\luda\cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_file_name_convert='luda','irina'
    *.db_name='irina'
    *.db_unique_name='luda'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
    *.fal_client='luda'
    *.fal_server='irina'
    *.job_queue_processes=10
    *.log_archive_config='DG_CONFIG=(irina,luda)'
    *.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/luda/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=luda'
    *.log_archive_dest_2='SERVICE=irina LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=irina'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=30
    *.log_file_name_convert='C:/oracle/product/10.2.0/oradata/irina/','C:/oracle/product/10.2.0/oradata/luda/'
    *.open_cursors=300
    *.pga_aggregate_target=16777216
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=167772160
    *.standby_file_management='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0\admin\luda\udump'
    On primary db
    irina.__db_cache_size=79691776
    irina.__java_pool_size=4194304
    irina.__large_pool_size=4194304
    irina.__shared_pool_size=75497472
    irina.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0/admin/irina/adump'
    *.background_dump_dest='C:\oracle\product\10.2.0/admin/irina/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\irina\control01.ctl','C:\oracle\product\10.2.0\oradata\irina\control02.ctl','C:\oracle\product\10.2.0\oradata\irina\control03.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0/admin/irina/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_file_name_convert='luda','irina'
    *.db_name='irina'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
    *.fal_client='irina'
    *.fal_server='luda'
    *.job_queue_processes=10
    *.log_archive_config='DG_CONFIG=(irina,luda)'
    *.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/irina/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=irina'
    *.log_archive_dest_2='SERVICE=luda LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=luda'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=30
    *.log_file_name_convert='C:/oracle/product/10.2.0/oradata/luda/','C:/oracle/product/10.2.0/oradata/irina/'
    *.open_cursors=300
    *.pga_aggregate_target=16777216
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=167772160
    *.standby_file_management='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0/admin/irina/udump'
    Please help me!!!!

    Hi,
    After several tries my redo logs are applied now. I think in my case it had to do with the tnsnames.ora. At this moment I have both database in both tnsnames.ora files using the SID and not the SERVICE_NAME.
    Now I want to use DGMGRL. Adding a configuration and a stand-by database is working fine, but when I try to enable the configuration DGMGRL gives no feedback and it looks like it is hanging. The log, although says that it succeeded.
    In another session 'show configuration' results in the following, confirming that the enable succeeded.
    DGMGRL> show configuration
    Configuration
    Name: avhtest
    Enabled: YES
    Protection Mode: MaxPerformance
    Fast-Start Failover: DISABLED
    Databases:
    avhtest - Primary database
    avhtestls53 - Physical standby database
    Current status for "avhtest":
    Warning: ORA-16610: command 'ENABLE CONFIGURATION' in progress
    It there anybody that experienced the same problem and/or knows the solution to this?
    With kind regards,
    Martin Schaap

  • Oracle write archive log files continuosly

    Hi all,
    I don't know why my Oracle Database has this problem. Online log are writen to archive log file continuously(3 minutes period). My archive logfile is 300M. I have startup force my database. It work, but archive log files are writen so much. This is alert log:
    >
    Sat Jan 1 14:23:19 2011
    Successfully onlined Undo Tablespace 5.
    Sat Jan 1 14:23:19 2011
    SMON: enabling tx recovery
    Sat Jan 1 14:23:19 2011
    Database Characterset is AL32UTF8
    Opening with internal Resource Manager plan
    where NUMA PG = 1, CPUs = 16
    replication_dependency_tracking turned off (no async multimaster replication found)
    Sat Jan 1 14:23:40 2011
    WARNING: AQ_TM_PROCESSES is set to 0. System operation might be adversely affected.
    Sat Jan 1 14:24:32 2011
    db_recovery_file_dest_size of 204800 MB is 28.64% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Sat Jan 1 14:24:40 2011
    Completed: ALTER DATABASE OPEN
    Sat Jan 1 14:27:05 2011
    Warning: PROCESSES may be too low for current load
    shared servers=360, want 7 more but starting only 3 more
    Warning: PROCESSES may be too low for current load
    shared servers=363, want 9 more but starting only 0 more
    Sat Jan 1 14:27:39 2011
    Warning: PROCESSES may be too low for current load
    shared servers=363, want 9 more but starting only 1 more
    Warning: PROCESSES may be too low for current load
    shared servers=364, want 9 more but starting only 0 more
    Sat Jan 1 14:28:58 2011
    Thread 1 advanced to log sequence 9463 (LGWR switch)
    Current log# 3 seq# 9463 mem# 0: /u01/oradata/TNORA3/redo03a.log
    Current log# 3 seq# 9463 mem# 1: /u02/oradata/TNORA3/redo03b.log
    Sat Jan 1 14:30:20 2011
    Errors in file /opt/app/oracle/admin/TNORA3/bdump/tnora_j000_17762.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-00018: maximum number of sessions exceeded
    Sat Jan 1 14:39:47 2011
    Thread 1 advanced to log sequence 9464 (LGWR switch)
    Current log# 1 seq# 9464 mem# 0: /u01/oradata/TNORA3/redo01a.log
    Current log# 1 seq# 9464 mem# 1: /u02/oradata/TNORA3/redo01b.log
    Sat Jan 1 14:42:51 2011
    Errors in file /opt/app/oracle/admin/TNORA3/bdump/tnora_s008_17165.trc:
    ORA-07445: exception encountered: core dump [_intel_fast_memcpy.J()+80] [SIGSEGV] [Address not mapped to object] [0x2B8988CE2018] [] []
    Sat Jan 1 14:42:57 2011
    Thread 1 advanced to log sequence 9465 (LGWR switch)
    Current log# 2 seq# 9465 mem# 0: /u01/oradata/TNORA3/redo02a.log
    Current log# 2 seq# 9465 mem# 1: /u02/oradata/TNORA3/redo02b.log
    Sat Jan 1 14:43:11 2011
    found dead shared server 'S008', pid = (42, 1)
    Sat Jan 1 14:45:39 2011
    Thread 1 advanced to log sequence 9466 (LGWR switch)
    Current log# 3 seq# 9466 mem# 0: /u01/oradata/TNORA3/redo03a.log
    Current log# 3 seq# 9466 mem# 1: /u02/oradata/TNORA3/redo03b.log
    Sat Jan 1 14:48:47 2011
    Thread 1 cannot allocate new log, sequence 9467
    Checkpoint not complete
    Current log# 3 seq# 9466 mem# 0: /u01/oradata/TNORA3/redo03a.log
    Current log# 3 seq# 9466 mem# 1: /u02/oradata/TNORA3/redo03b.log
    Sat Jan 1 14:48:50 2011
    Thread 1 advanced to log sequence 9467 (LGWR switch)
    Current log# 1 seq# 9467 mem# 0: /u01/oradata/TNORA3/redo01a.log
    Current log# 1 seq# 9467 mem# 1: /u02/oradata/TNORA3/redo01b.log
    Sat Jan 1 14:52:11 2011
    Thread 1 advanced to log sequence 9468 (LGWR switch)
    Current log# 2 seq# 9468 mem# 0: /u01/oradata/TNORA3/redo02a.log
    Current log# 2 seq# 9468 mem# 1: /u02/oradata/TNORA3/redo02b.log
    Sat Jan 1 14:55:12 2011
    Thread 1 advanced to log sequence 9469 (LGWR switch)
    Current log# 3 seq# 9469 mem# 0: /u01/oradata/TNORA3/redo03a.log
    Current log# 3 seq# 9469 mem# 1: /u02/oradata/TNORA3/redo03b.log
    Sat Jan 1 14:58:12 2011
    Thread 1 advanced to log sequence 9470 (LGWR switch)
    Current log# 1 seq# 9470 mem# 0: /u01/oradata/TNORA3/redo01a.log
    Current log# 1 seq# 9470 mem# 1: /u02/oradata/TNORA3/redo01b.log
    Sat Jan 1 15:02:00 2011
    Thread 1 advanced to log sequence 9471 (LGWR switch)
    Current log# 2 seq# 9471 mem# 0: /u01/oradata/TNORA3/redo02a.log
    Current log# 2 seq# 9471 mem# 1: /u02/oradata/TNORA3/redo02b.log
    Sat Jan 1 15:05:16 2011
    Thread 1 advanced to log sequence 9472 (LGWR switch)
    Current log# 3 seq# 9472 mem# 0: /u01/oradata/TNORA3/redo03a.log
    Current log# 3 seq# 9472 mem# 1: /u02/oradata/TNORA3/redo03b.log
    Sat Jan 1 15:08:30 2011
    Thread 1 advanced to log sequence 9473 (LGWR switch)
    Current log# 1 seq# 9473 mem# 0: /u01/oradata/TNORA3/redo01a.log
    Current log# 1 seq# 9473 mem# 1: /u02/oradata/TNORA3/redo01b.log
    Sat Jan 1 15:11:12 2011
    Thread 1 cannot allocate new log, sequence 9474
    Checkpoint not complete
    Current log# 1 seq# 9473 mem# 0: /u01/oradata/TNORA3/redo01a.log
    Current log# 1 seq# 9473 mem# 1: /u02/oradata/TNORA3/redo01b.log
    Sat Jan 1 15:11:14 2011
    Thread 1 advanced to log sequence 9474 (LGWR switch)
    Current log# 2 seq# 9474 mem# 0: /u01/oradata/TNORA3/redo02a.log
    Current log# 2 seq# 9474 mem# 1: /u02/oradata/TNORA3/redo02b.log
    Sat Jan 1 15:14:15 2011
    Thread 1 advanced to log sequence 9475 (LGWR switch)
    Current log# 3 seq# 9475 mem# 0: /u01/oradata/TNORA3/redo03a.log
    Current log# 3 seq# 9475 mem# 1: /u02/oradata/TNORA3/redo03b.log
    >
    PLs, help me.

    This is the contait of tail -100 /opt/app/oracle/admin/TNORA3/bdump/tnora_s008_17165.trc | more
    KCBS: Tot bufs in set segwise
    KCBS: nbseg[0] is 1568
    KCBS: nbseg[1] is 1568
    KCBS: nbseg[2] is 1569
    KCBS: nbseg[3] is 1568
    KCBS: nbseg[4] is 1568
    KCBS: nbseg[5] is 1568
    KCBS: nbseg[6] is 1569
    KCBS: nbseg[7] is 1568
    KCBS: nbseg[8] is 1568
    KCBS: nbseg[9] is 1568
    KCBS: nbseg[10] is 1569
    KCBS: nbseg[11] is 1568
    KCBS: nbseg[12] is 1568
    KCBS: nbseg[13] is 1568
    KCBS: nbseg[14] is 1569
    KCBS: nbseg[15] is 1568
    KCBS: nbseg[16] is 1568
    KCBS: nbseg[17] is 1568
    KCBS: nbseg[18] is 1569
    KCBS: nbseg[19] is 1568
    KCBS: Act cnt = 15713
    KCBS: bufcnt = 31365, nb_kcbsds = 31365
    KCBS: fbufcnt = 445
    KCBS: Tot bufs in set segwise
    KCBS: nbseg[0] is 1568
    KCBS: nbseg[1] is 1568
    KCBS: nbseg[2] is 1569
    KCBS: nbseg[3] is 1568
    KCBS: nbseg[4] is 1568
    KCBS: nbseg[5] is 1568
    KCBS: nbseg[6] is 1569
    KCBS: nbseg[7] is 1568
    KCBS: nbseg[8] is 1568
    KCBS: nbseg[9] is 1568
    KCBS: nbseg[10] is 1569
    KCBS: nbseg[11] is 1568
    KCBS: nbseg[12] is 1568
    KCBS: nbseg[13] is 1568
    KCBS: nbseg[14] is 1569
    KCBS: nbseg[15] is 1568
    KCBS: nbseg[16] is 1568
    KCBS: nbseg[17] is 1568
    KCBS: nbseg[18] is 1569
    KCBS: nbseg[19] is 1568
    KCBS: Act cnt = 15713
    KCBS: bufcnt = 31365, nb_kcbsds = 31365
    KCBS: fbufcnt = 445
    KCBS: Tot bufs in set segwise
    KCBS: nbseg[0] is 1568
    KCBS: nbseg[1] is 1568
    KCBS: nbseg[2] is 1568
    KCBS: nbseg[3] is 1569
    KCBS: nbseg[4] is 1568
    KCBS: nbseg[5] is 1568
    KCBS: nbseg[6] is 1568
    KCBS: nbseg[7] is 1569
    KCBS: nbseg[8] is 1568
    KCBS: nbseg[9] is 1568
    KCBS: nbseg[10] is 1568
    KCBS: nbseg[11] is 1569
    KCBS: nbseg[12] is 1568
    KCBS: nbseg[13] is 1568
    KCBS: nbseg[14] is 1568
    KCBS: nbseg[15] is 1569
    KCBS: nbseg[16] is 1568
    KCBS: nbseg[17] is 1568
    KCBS: nbseg[18] is 1568
    KCBS: nbseg[19] is 1569
    KCBS: Act cnt = 15713
    KCBS: bufcnt = 31365, nb_kcbsds = 31365
    KCBS: fbufcnt = 444
    KCBS: Tot bufs in set segwise
    KCBS: nbseg[0] is 1568
    KCBS: nbseg[1] is 1568
    KCBS: nbseg[2] is 1568
    KCBS: nbseg[3] is 1569
    KCBS: nbseg[4] is 1568
    KCBS: nbseg[5] is 1568
    KCBS: nbseg[6] is 1568
    KCBS: nbseg[7] is 1569
    KCBS: nbseg[8] is 1568
    KCBS: nbseg[9] is 1568
    KCBS: nbseg[10] is 1568
    KCBS: nbseg[11] is 1569
    KCBS: nbseg[12] is 1568
    KCBS: nbseg[13] is 1568
    KCBS: nbseg[14] is 1568
    KCBS: nbseg[15] is 1569
    KCBS: nbseg[16] is 1568
    KCBS: nbseg[17] is 1568
    KCBS: nbseg[18] is 1568
    KCBS: nbseg[19] is 1569
    KCBS: Act cnt = 15713
    KSOLS: Begin dumping all object level stats elements
    KSOLS: Done dumping all elements. Exiting.
    Dump event group for SESSION
    Unable to dump event group - no SESSION state objectDump event group for SYSTEM
    ssexhd: crashing the process...
    Shadow_Core_Dump = partial

  • "recover database until cancel" asks for archive log file that do not exist

    Hello,
    Oracle Release : Oracle 10.2.0.2.0
    Last week we performed, a restore and then an Oracle recovery using the recover database until cancel command. (we didn't use backup control files) .It worked fine and we able to restart the SAP instances. However, I still have questions about Oracle behaviour using this command.
    First we restored, an online backup.
    We tried to restart the database, but got ORA-01113,ORA-01110 errors :
    sr3usr.data1 needed media recovery.
    Then we performed the recovery :
    According Oracel documentation, "recover database until cancel recovery" proceeds by prompting you with the suggested filenames of archived redo log files.
    The probleme is it  prompts for archive log file that do not exist.
    As you can see below, it asked for SMAarch1_10420_610186861.dbf that has never been created. Therefore, I cancelled manually the recovery, and restarted the database. We never got the message "media recovery complete"
    ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10417_61018686
    Fri Sep  7 14:09:45 2007
    ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf'
    Fri Sep  7 14:09:45 2007
    Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10418_610186861.dbf
    ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10418_61018686
    Fri Sep  7 14:10:03 2007
    ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf'
    Fri Sep  7 14:10:03 2007
    Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10419_610186861.dbf
    ORA-279 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10419_61018686
    Fri Sep  7 14:10:13 2007
    ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf'
    Fri Sep  7 14:10:13 2007
    Media Recovery Log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
    Errors with log /oracle/SMA/oraarch/SMAarch1_10420_610186861.dbf
    ORA-308 signalled during: ALTER DATABASE RECOVER    LOGFILE '/oracle/SMA/oraarch/SMAarch1_10420_61018686
    Fri Sep  7 14:15:19 2007
    ALTER DATABASE RECOVER CANCEL
    Fri Sep  7 14:15:20 2007
    ORA-1013 signalled during: ALTER DATABASE RECOVER CANCEL ...
    Fri Sep  7 14:15:40 2007
    Shutting down instance: further logons disabled
    When restaring the database we could see that, a recovery of online redo log has been performed automatically, is it the normal behaviour of a recovery using "recover database until cancel"  command ?
    Started redo application at
    Thread 1: logseq 10416, block 482
    Fri Sep  7 14:24:55 2007
    Recovery of Online Redo Log: Thread 1 Group 4 Seq 10416 Reading mem 0
      Mem# 0 errs 0: /oracle/SMA/origlogB/log_g14m1.dbf
      Mem# 1 errs 0: /oracle/SMA/mirrlogB/log_g14m2.dbf
    Fri Sep  7 14:24:55 2007
    Completed redo application
    Fri Sep  7 14:24:55 2007
    Completed crash recovery at
    Thread 1: logseq 10416, block 525, scn 105140074
    0 data blocks read, 0 data blocks written, 43 redo blocks read
    Thank you very much for your help.
    Frod.

    Hi,
    Let me answer your query.
    =======================
    Your question: While performing the recovery, is it possible to locate which online redolog is needed, and then to apply the changes in these logs
    1.   When you have current controlfile and need complete data (no data loss),
          then do not go for until cancel recovery.
    2.   Oracle will apply all the redologs (including current redolog) while recovery
         process is    on.
    3.  During the recovery you need to have all the redologs which are listed in the    view    V$RECOVERY_LOG and all the unarchived and current redolog. By querying  V$RECOVERY_LOG  you    can find out about the redologs required.
    4. If the required sequence is not there in the archive destination, and if recovery process    asks for that sequence you can query V$LOG to see whether requested sequence is part of the    online redologs. If yes you can mention the path of the online redolog to complete the recovery.
    Hope this information helps.
    Regards,
    Madhukar

  • How does one name an Archive Log file in ARC%S_%R.%T format

    Hallo!I have been trying to enable Archive Log mode for the Oracle 10g database.
    In OEM,I went via the links Maintenance->Recovery Settings->Media Recovery
    There,a text box by the name Log Archive Filename Format requires one to name the Archive Log file in ARC%S_%R.%T format.
    I have tried several times to name the Archive log e.g ARC001_001.001 but when I shutdown and restart the database instance,the error below appears
    ORA-19905: log_archive_format must contain %s, %t and %r.
    This error has proved impossible to rectify and I am forced to uninstall then re-install Oracle 10g.
    I would like to have back-ups in archive log mode.Please give me the best way to name the Archive Log file i.e with an example name so that I can have online back-ups.
    Thanks.

    Hi,
    If you try to change the LOG_ARCHIVE_FORMAT to something other than the default %s,%t,%r, it will fail
    Perform as the below steps in order to enable archive log mode
    SQL>create pfile from spfile
    SQL>create pfile='c:\temp\init.ora' from spfile;
    SQL>created;
    SQL>shutdown immediate;
    edit the init.ora file by adding the following information
    *.LOG_ARCHIVE_DEST_1='LOCATION=C:\db\archive1'
    *.LOG_ARCHIVE_FORMAT='%t_%s_%r.dbf'
    Start the DB with modified pfile.
    - Pavan Kumar N
    Edited by: Pavan Kumar on May 2, 2010 2:17 PM

  • How to Recover database from old backup and full archive log file

    Hi Oracle expert!
    I met problem when restore my oracle database.
    In my case:
    - My database version: 10.2.0.2
    - I have a database full backup (01-Nov)
    - I have all Archived log file from (01-Nov -> 05-Nov)
    - My database drop in 05-Nov with disk error (no datafile, no redo..).
    - I have no any RMAN backup from (01-Nov -> 05-Nov)
    How can i restore my database to 05-Nov?
    Thanks

    user10280724 wrote:
    Hi Chinar.
    When i used RMAN flow as your step, but i met the problem!
    - After recover database i select sequence#, applied from v$archived_log;
    --> it apply newest archived log that i had.
    - but when I select Data from table created between 01-Nov to 05-Nov, it not found!
    Not the same way the step:
    SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL?
    It apply newest the same archived log i had table created between 01-Nov to 05-Nov.
    How can i do with RMAN to recover my table?That is not possible,if your all available archive logs applied using rman or through sqlplus(recover database using backup controlfile until cancel) and one of these logs contain your table then there are not any problems.So there are not any difference between recovery using rman and user managed(using sqlplus),but there main matter is applying all archive logs.So first check through rman list copy of archivelog all or list backup of archivelog all and identify there in rman repository is any information or not about these logs.

  • RAC(OPS) 환경 하에서 ARCHIVED LOG FILE을 BACKUP 받는 방법

    제품 : RMAN
    작성날짜 : 2004-11-26
    RAC(OPS) 환경하에서 양쪽 Node의 archived log file을 RMAN을 사용하여 동시에 BACKUP 받는 방법
    ======================================================================================
    ORACLE 9i 이전 버전
    Oracle 8i까지는 다음과 같은 Script를 통하여 Backup을 받을 수 있었습니다.
    1) Script Name: arch_backup.rcv
    run{
    allocate channel node_1 type disk connect 'system/manager@v92hp1';
    allocate channel node_2 type disk connect 'system/manager@v92hp2';
    backup filesperset 1
    (archivelog until time 'SYSDATE' thread 1 channel node_1)
    (archivelog until time 'SYSDATE' thread 2 channel node_2);
    release channel node_1;
    release channel node_2;
    2) 수행 방법
    $ rman target=system/manager catalog=rman_user/rmanpw cmdfile='arch_backup.rcv' log='arch_backup.log'
    ORACLE 9i 이후 버전
    그러나 Oracle9i 이상부터는 Archived file backup전에 다음과 같은 설정을 먼저
    해 주셔야만 합니다.
    1) Configuration 설정
    $ rman target=system/manager catalog=rman_user/rmanpw
    RMAN> Show all;
    RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
    RMAN> configure default device type to disk;
    RMAN> configure channel 1 device type disk connect 'system/manager@v92hp1';
    RMAN> configure channel 2 device type disk connect 'system/manager@v92hp2';
    위 설정은 backup을 Disk에 받는 경우로 가정하고 device type을 모두 disk로 설정하였습니다.
    만일 backup solution을 사용하여 tape에 받는다면 device type을 'sbt_tape'으로 변경해 주시면 됩니다
    몇개의 Channel을 설정할 것인가에 따라 PARALLELISM의 값을 반드시맞춰 주어야 합니다.
    이것을 맞춰주지 않으면 다음과 같은 형태의 Error가 발생하면서 다른 Node의 archive file들을 인식하지
    못하게 됩니다.(실제로 Archived file들은 정상적으로 존재합니다)
    RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
    ORA-19625: error identifying file /u01/64bit/app/oracle/product/9.2.0/admin/V92HP/arch/arch1_146.dbf
    ORA-27037: unable to obtain file status
    HP-UX Error: 2: No such file or directory
    Additional information: 3
    위 설정은 한번만 수행해 주시면 됩니다.
    만일 CHANNEL을 잘못 설정하였으면 다음과 같은 명령으로 Clear 해 주시면 됩니다.
    RMAN> configure channel 1 device type disk clear;
    2)Archived file을 Backup 받습니다.
    RMAN> run { backup
    format='/u01/64bit/app/oracle/product/9.2.0/admin/V92HP/arch/%U'
    archivelog all delete input;
    ADDITIONAL INFORMATION(1)
    RAC 환경 하에서 일부 Archived file들이 OS에서 삭제 되었을 경우 다음과 같은 명령을 통하여
    validation check를 수행한 후에 backup을 수행하여 주십시요
    RMAN> allocate channel for maintenance type disk connect 'system/manager@v92hp1';
    RMAN> allocate channel for maintenance type disk connect 'system/manager@v92hp2';
    RMAN> crosscheck archivelog all;
    만약에 Configuration에서 이미 Channel을 설정해 주었다면
    Channel allocation 없이 바로 crosscheck명령어를 수행해 주시면 됩니다.
    ADDITIONAL INFORMATION(2)
    Channel Configuration 설정시에 Backup FORMAT을 함께 설정하려면 다음과 같은 형태로 수행합니다.
    RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
    RMAN> configure default device type to disk;
    RMAN> configure channel 1 device type disk connect 'system/manager@v92hp1' FORMAT '/arch/bkup%t_s%s_s%p';
    RMAN> configure channel 2 device type disk connect 'system/manager@v92hp2' FORMAT '/arch/bkup%t_s%s_s%p';
    ADDITIONAL INFORMATION(3)
    Tape device를 사용할 경우 device type은 'sbt_tape'을 사용합니다.
    RMAN> CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2;
    RMAN> configure default device type to 'sbt_tape';
    RMAN> configure channel 1 device type 'sbt_tape' connect 'system/manager@v92hp1' FORMAT 'bkup%t_s%s_s%p';
    RMAN> configure channel 2 device type 'sbt_tape' connect 'system/manager@v92hp2' FORMAT 'bkup%t_s%s_s%p';

  • (Forte-users) log file error

    Hi,
    We are getting this error in our log files, when we run our application.(We
    are running interpreted)
    Any help will be appreciated to solve this problem.
    Thanks
    Carole
    Attached to manager for node FORTE_DEV.
    aud Wed May 10 08:58:28 : Loading partition CSaver_cl169_Part1-router built
    on 08-May-2000 16:32:42.
    Attached to manager for node FORTE_DEV.
    aud Wed May 10 10:01:12 : Shutting down partition as requested.
    aud Wed May 10 10:01:13 : Unloaded partition CSaver_cl169_Part1-router.
    aud Wed May 10 10:01:15 : Loading partition CSaver_cl169_Part1-router built
    on 08-May-2000 16:32:42.
    Attached to manager for node FORTE_DEV.
    LbRouter::FindMembers - CAUGHT EXCEPTION attaching members from
    SYSTEM ERROR: Failed to connect or lost connection to the environment
    manager
    at FORTE_NS_ADDRESS = <Unknown>. Check that the environment manager is
    installed at that location. If it is, then check to be sure that there
    are
    enough system resources available to support this partition.
    Class: qqsp_SystemResourceException
    Error #: [601, 201]
    Detected at: qqdo_NsClient::FindObject at 1
    Error Time: Wed May 10 10:01:40
    Exception occurred (locally) on partition "CSaver_cl169_Part1-router",
    (partitionId = A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696:0x1, taskId
    =
    [A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696.9]) in application
    "CSaver_cl169", pid 698 on node FORTE_DEV in environment nbs_dev.
    SYSTEM ERROR: Attempt to send from a partition
    (A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696:0x1) that no longer
    exists.
    Class: qqsp_DistAccessException
    Error #: [601, 111]
    Detected at: qqdo_PartitionMgr::SendMsg at 1
    Error Time: Wed May 10 10:01:40
    Distributed method called: qqdo_NsServerProxy.FindObject (object
    name
    Unnamed) from partition "CSaver_cl169_Part1-router", (partitionId
    =
    A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696:0x1, taskId =
    [A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696.9]) in application
    "CSaver_cl169", pid 698 on node FORTE_DEV in environment nbs_dev
    Exception occurred (locally) on partition
    "CSaver_cl169_Part1-router",
    (partitionId = A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696:0x1,
    taskId
    = [A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696.9]) in application
    "CSaver_cl169", pid 698 on node FORTE_DEV in environment nbs_dev.
    LbRouter::FindMembers - CAUGHT EXCEPTION attaching members from
    SYSTEM ERROR: Failed to connect or lost connection to the environment
    manager
    at FORTE_NS_ADDRESS = <Unknown>. Check that the environment manager is
    installed at that location. If it is, then check to be sure that there
    are
    enough system resources available to support this partition.
    Class: qqsp_SystemResourceException
    Error #: [601, 201]
    Detected at: qqdo_NsClient::FindObject at 1
    Error Time: Wed May 10 10:01:40
    Exception occurred (locally) on partition "CSaver_cl169_Part1-router",
    (partitionId = A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696:0x1, taskId
    =
    [A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696.9]) in application
    "CSaver_cl169", pid 698 on node FORTE_DEV in environment nbs_dev.
    WARNING:
    Any unauthorised use or interception of this email is illegal. If this email
    is not intended for you, you may not copy, distribute nor disclose the
    contents to anyone. Save for bona fide company matters, the BoE Group does
    not accept any responsibility for the opinions expressed in this email.
    For further details please see: http://www.nbs.co.za/emaildisclaim.htm

    One thing to look at is this message: Check that the environment manager is
    installed at that location. If it is, then check to be sure that there are
    enough system resources available to support this partition.
    Particularly the enough systems resources part of it. I've seen this message
    before, but it's been awhile, & the problem was we didn't have enough
    virtual memory on the server & also we needed more tcp/ip connections. If I
    remember right our Unix guy had to change some of the configuration
    parameters in the kernel on the server.
    Hope this helps.
    -----Original Message-----
    From: MacDonald, Carole [mailto:CMacDonaldnbs.co.za]
    Sent: Thursday, May 11, 2000 3:53 AM
    To: forte-userslists.xpedior.com
    Subject: (Forte-users) log file error
    Hi,
    We are getting this error in our log files, when we run our application.(We
    are running interpreted)
    Any help will be appreciated to solve this problem.
    Thanks
    Carole
    Attached to manager for node FORTE_DEV.
    aud Wed May 10 08:58:28 : Loading partition CSaver_cl169_Part1-router built
    on 08-May-2000 16:32:42.
    Attached to manager for node FORTE_DEV.
    aud Wed May 10 10:01:12 : Shutting down partition as requested.
    aud Wed May 10 10:01:13 : Unloaded partition CSaver_cl169_Part1-router.
    aud Wed May 10 10:01:15 : Loading partition CSaver_cl169_Part1-router built
    on 08-May-2000 16:32:42.
    Attached to manager for node FORTE_DEV.
    LbRouter::FindMembers - CAUGHT EXCEPTION attaching members from
    SYSTEM ERROR: Failed to connect or lost connection to the environment
    manager
    at FORTE_NS_ADDRESS = <Unknown>. Check that the environment manager is
    installed at that location. If it is, then check to be sure that there
    are
    enough system resources available to support this partition.
    Class: qqsp_SystemResourceException
    Error #: [601, 201]
    Detected at: qqdo_NsClient::FindObject at 1
    Error Time: Wed May 10 10:01:40
    Exception occurred (locally) on partition "CSaver_cl169_Part1-router",
    (partitionId = A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696:0x1, taskId
    =
    [A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696.9]) in application
    "CSaver_cl169", pid 698 on node FORTE_DEV in environment nbs_dev.
    SYSTEM ERROR: Attempt to send from a partition
    (A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696:0x1) that no longer
    exists.
    Class: qqsp_DistAccessException
    Error #: [601, 111]
    Detected at: qqdo_PartitionMgr::SendMsg at 1
    Error Time: Wed May 10 10:01:40
    Distributed method called: qqdo_NsServerProxy.FindObject (object
    name
    Unnamed) from partition "CSaver_cl169_Part1-router", (partitionId
    =
    A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696:0x1, taskId =
    [A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696.9]) in application
    "CSaver_cl169", pid 698 on node FORTE_DEV in environment nbs_dev
    Exception occurred (locally) on partition
    "CSaver_cl169_Part1-router",
    (partitionId = A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696:0x1,
    taskId
    = [A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696.9]) in application
    "CSaver_cl169", pid 698 on node FORTE_DEV in environment nbs_dev.
    LbRouter::FindMembers - CAUGHT EXCEPTION attaching members from
    SYSTEM ERROR: Failed to connect or lost connection to the environment
    manager
    at FORTE_NS_ADDRESS = <Unknown>. Check that the environment manager is
    installed at that location. If it is, then check to be sure that there
    are
    enough system resources available to support this partition.
    Class: qqsp_SystemResourceException
    Error #: [601, 201]
    Detected at: qqdo_NsClient::FindObject at 1
    Error Time: Wed May 10 10:01:40
    Exception occurred (locally) on partition "CSaver_cl169_Part1-router",
    (partitionId = A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696:0x1, taskId
    =
    [A37D7E70-0024-11D3-9C6C-522EAE7DAA77:0xa696.9]) in application
    "CSaver_cl169", pid 698 on node FORTE_DEV in environment nbs_dev.
    WARNING:
    Any unauthorised use or interception of this email is illegal. If this email
    is not intended for you, you may not copy, distribute nor disclose the
    contents to anyone. Save for bona fide company matters, the BoE Group does
    not accept any responsibility for the opinions expressed in this email.
    For further details please see: http://www.nbs.co.za/emaildisclaim.htm
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

  • How do I setup RMAN not to delete archive log files on the source database so GoldenGate can process DDL/DML changes?

    I want to setup RMAN not to delete any archive log files that will be used by GoldenGate.   Once GoldenGate is completed with the archive log file, the archive log file can be backup and deleted by RMAN.   It's my understanding that I can issue the following command "REGISTER EXTRACT <ext_name>, LOGRETENTION" to enable to functionally.   Is this the only thing I need to do to execute to enable this functionally?

    Hello,
    Yes this is the rigth way  using clasic capture.
    Using the command : REGISTER EXTRACT Extract_name LOGRETENTION.
    Create a Oracle Streams Group Capture (Artificial)  that prevent RMAN archive deletion if these are pending to process for Golden Gate capture process.
    You can see this integration doing a SELECT * FROM DBA_CAPTURE; after execute the register command.
    Then, when RMAN try to delete a archive file pending to process for GG this warning appear AT RMAN logs:
    Error:     RMAN 8317 (RMAN-08317 RMAN-8317)
    Text:     WARNING: archived log not deleted, needed for standby or upstream capture process.
    Then , this is a good manageability feature. I think is a 11.1 GG new feature.
    Tip. To avoid RMAN backup multiples times a archive pending to process, there is a option called BACKUP archivelog not backed 1 times.
    If you remove a Capture process that is registered with the database you need to use this comand to remove the streams capture group:
    unREGISTER EXTRACT extract_name LOGRETENTION;
    Then if you query dba_capture, the artificial Streams group is deleted.
    I hope help.
    Regards
    Arturo

  • Are there any possible reason RMAN generates some corrupt archive log files

    Dear all,
    Are there any possible reason RMAN generates some corrupt archive log files?
    Best Regards,
    Amy

    Because I try to perform daily backup at lunch time and found out it takes more than 1 hour had no any progress. Normally we take around 40 minus. The following is the log file:
    RMAN> Run
    2> {
    3> CONFIGURE CONTROLFILE AUTOBACKUP ON;
    4> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/db/backup/RMAN/%F.bck';
    5> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
    6> allocate channel ch1 type disk format '/u03/db/backup/RMAN/backup_%d_%t_%s_%p_%U.bck';
    7> backup incremental level 1 cumulative database plus archivelog delete all input;
    8> backup current controlfile;
    9> backup spfile;
    10> release channel ch1;
    11> }
    12> allocate channel for maintenance type disk;
    13> delete noprompt obsolete;
    14> delete noprompt archivelog all backed up 2 times to disk;
    15>
    16>
    using target database controlfile instead of recovery catalog
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    new RMAN configuration parameters are successfully stored
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/db/backup/RMAN/%F.bck';
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/db/backup/RMAN/%F.bck';
    new RMAN configuration parameters are successfully stored
    old RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
    new RMAN configuration parameters are successfully stored
    allocated channel: ch1
    channel ch1: sid=99 devtype=DISK
    Starting backup at 31-MAR-09
    current log archived
    After that I go to archive log directory "/u02/oracle/uat/uatdb/9.2.0/dbs" and use ls -lt command to see how many archive logs and my screen just hang. After we found out that we cannot use ls -lt command to read arch1_171.dbf
    archive log, the rest of archive logs able to use ls -lt command.
    We cannot delete this file as well. We shutdown database abort and perform check disk...... and fix the disk error and then open database again. Everything seems back to normal and we can use ls -lt command to read arch1_171.dbf.
    The strange problem is we have the same problem in Development and Production..... one ore more archive logs seems to be corrupted under the same directories /u02/oracle/uat/uatdb/9.2.0/dbs.
    Does anyone encounter the same problem?
    Amy

  • How to delete the data in archived log files

    hi
    how can i delete the enteries in archived log files. and what is the disadvantage of deleting archived log enteries.

    There is no documented way to delete data stored in archived log files: you can only remove the archived log files if needed.

  • SQL Server 2012 Developer Edition will not install. Setup files don't even get copied completely. Win 8.1. ACT instance is loaded & can't be deleted. From log file: Error: Action "PreMsiTimingConfigAction" failed during execution.

    SQL Server 2012 Developer Edition will not install.  Setup files don't even get copied completely.  Win 8.1.  ACT instance is loaded & can't be deleted. From log file: Error: Action "PreMsiTimingConfigAction" failed during execution.

    Hello,
    I am glad it worked.
    Thank you for visiting MSDN forums!
    Regards,
    Alberto Morillo
    SQLCoffee.com

Maybe you are looking for