Stupid question. RMAN - apply new archive logs

I have following scenario:
I have backup from last night + archived logs.
And have a lot of new archivelogs.
And I've lost main server.
Now I can restore this database on another host. And this database will have state of the previous database from last backup. Can I somehow apply new archivelogs to this database? (We have all archivelogs after backup).
Thank you.

Hi,
after restoring the backup on new server( on there exact same location).issue
startup mount;
recover database until cancel;<-- this cmd will apply are available archivelog.
alter database open resetlogs;
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a97202/toc.htm
Thanks
Kuljeet

Similar Messages

  • Question about only new archive logs backed up in backup

    Hi,
    We are taking daily two online backup. We are running database in ARCHIVELOG mode. We configure database in PRIMARY and PHYSICAL STANDBY mode. Till now, we were taking all archive logs in backup. But it was causing problem of lot of space utilization of disk.
    So based on search in this forum, I am planning to take only new archive logs generated since last backed up using following command.
    BACKUP ARCHIVELOG all not backed up 1 times format '$dir/archivelogs_%s_%t' FORCE;
    I am not sure about how it impact during restore and recovery when we take only new archivelogs in backup.
    We restore database and then after perform always incomplete recovery till latest SCN capture in backup using following commands.
    RESTORE DATABASE;
    RECOVER DATABASE UNTIL SCN $BACKUP_LAST_SCN;
    Do you see any problem/risk of implementing this solution going ahead?
    Please let me provide your thoughts/inputs for this.
    Thanks.
    Shardul

    Hi,
    We are not deleting archive logs from actual location after backup. We keep latest 6 days archive logs at actual location. But here we are planning to put only new archive logs in backup image which were not backed up due to disk size problem.
    For your reference below is our datbase backup RMAN commands. We are taking full database backup.
    run {
    ALLOCATE CHANNEL C1 TYPE DISK;
    delete noprompt archivelog all completed before 'sysdate-5';
    SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT';
    BACKUP INCREMENTAL LEVEL=0 CUMULATIVE format '$dir/level0_%u' DATABASE include current controlfile
    for standby force;
    SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT';
    BACKUP ARCHIVELOG all not backed up 1 times format '$dir/archivelogs_%s_%t' FORCE;
    BACKUP CURRENT CONTROLFILE format '$dir/control_primary' FORCE;
    Then in this polich do you see any problem when we restore database as PRIMARY or PHYSICAL STANDBY on server. We are using Oracle 10.2.0.3.

  • RMAN-08120: WARNING: archived log not deleted, not yet applied by standby

    i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary
    but when i run below query i get the same result from primary and standby
    SQL> select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
    44051
    SQL>
    standby is one log switch behind only!

    i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary You already have answer by post of Mseberg.
    but when i run below query i get the same result from primary and standby
    SQL> select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
    44051
    SQL>
    standby is one log switch behind only!this is wrong query used on primary & standby. even if any one of archive gap available lets suppose sequence *44020* , this archive not transported to standby due to some network problem and so on. later if archives from *44021* all the archives transported on standby upto *44051* , then it shows the maximum sequence transferred to standby, It wont shows applied sequence.
    Check the below queries.
    Primary:-
    SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
    Standby:-
    SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
    HTH.

  • RMAN BACKUPS AND ARCHIVED LOG ISSUES

    제품 : RMAN
    작성날짜 : 2004-02-17
    RMAN BACKUPS AND ARCHIVED LOG ISSUES
    =====================================
    Scenario #1:
    1)RMAN이 모든 archived log들을 삭제할 때 실패하는 경우.
    database는 두 개의 archive destination에 archive file을 생성한다.
    다음과 같은 스크립트를 수행하여 백업후에 archived redo logfile을 삭제한다.
    run {
    allocate channel c1 type 'sbt_tape';
    backup database;
    backup archivelog all delete input;
    Archived redo logfile 삭제 유무를 확인하기 위해 CROSSCHECK 수행시 다음과
    같은 메시지가 발생함.
    RMAN> change archivelog all crosscheck;
    RMAN-03022: compiling command: change
    RMAN-06158: validation succeeded for archived log
    RMAN-08514: archivelog filename=
    /oracle/arch/dest2/arcr_1_964.arc recid=19 stamp=368726072
    2) 원인분석
    이 문제는 에러가 아니다. RMAN은 여러 개의 arhive directory중 하나의
    directoy안에 있는 archived file들만 삭제한다. 그래서 나머지 directory안의
    archived log file들은 삭제되지 않고 남게 되는 것이다.
    3) 해결책
    RMAN이 강제로 모든 directory안의 archived log file들을 삭제하게 하기 위해서는
    여러 개의 채널을 할당하여 각 채널이 각 archive destination안의 archived file을
    백업하고 삭제하도록 해야 한다.
    이것은 아래와 같이 구현될 수 있다.
    run {
    allocate channel t1 type 'sbt_tape';
    allocate channel t2 type 'sbt_tape';
    backup
    archivelog like '/oracle/arch/dest1/%' channel t1 delete input
    archivelog like '/oracle/arch/dest2/%' channel t2 delete input;
    Scenario #2:
    1)RMAN이 archived log를 찾을 수 없어 백업이 실패하는 경우.
    이 시나리오에서 database를 incremental backup한다고 가정한다.
    이 경우 RMAN은 recover시 archived redo log대신에 incremental backup을 사용할
    수 있기 때문에 백업 후 모든 archived redo log를 삭제하기 위해 OS utility를 사용한다.
    그러나 다음 번 backup시 다음과 같은 Error를 만나게 된다.
    RMAN-6089: archive log NAME not found or out of sync with catalog
    2) 원인분석
    이 문제는 OS 명령을 사용하여 archived log를 삭제하였을 경우 발생한다. 이때 RMAN은
    archived log가 삭제되었다는 것을 알지 못한다. RMAN-6089는 RMAN이 OS 명령에 의해
    삭제된 archived log가 여전히 존재하다고 생각하고 백업하려고 시도하였을 때 발생하게 된다.
    3) 해결책
    가장 쉬운 해결책은 archived log를 백업할 때 DELETE INPUT option을 사용하는 것이다.
    예를 들면
    run {
    allocate channel c1 type 'sbt_tape';
    backup archivelog all delete input;
    두 번째로 가장 쉬운 해결책은 OS utility를 사용하여 archived log를 삭제한 후에
    다음과 같은 명령어를 RMAN prompt상에서 수행하는 것이다.
    RMAN>allocate channel for maintenance type disk;
    RMAN>change archivelog all crosscheck;
    Oracle 8.0:
         RMAN> change archivelog '/disk/path/archivelog_name' validate;
    Oracle 8i:
    RMAN> change archivelog all crosscheck ;
    Oracle 9i:
    RMAN> crosscheck archivelog all ;
    catalog의 COMPATIBLE 파라미터가 8.1.5이하로 설정되어 있으면 RMAN은 찾을 수 없는
    모든 archived log의 status를 "DELETED" 로 셋팅한다. 만약에 COMPATIBLE이 8.1.6이상으로
    설정되어 있으면 RMAN은 Repository에서 record를 삭제한다.

    Very strange, I issue following command in RMAN on both primary and standby machine, but it they don't delete the 1_55_758646076.dbf, I find in v$archived_log, this "/home/oracle/app/oracle/dataguard/1_55_758646076.dbf" had already been applied.
    RMAN> connect target /
    RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    old RMAN configuration parameters:
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    new RMAN configuration parameters:
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    new RMAN configuration parameters are successfully stored
    RMAN>
    ----------------------------------------------------------------------------------

  • Data guard real time apply vs archived log apply on physical standby

    Dear DBA's,
    last week i configuared DR , now the phyiscal stanby database is archive apply mode,
    i want to confirm is it better to apply the archived log or should i cahnge it to real time apply .
    give me sugesstions.
    Thanks and Regards
    Raja...

    One question are you using ARCH transport to move the redo? or have you configured standby redo logs and logwr transport (either async or syncronous), if you are using the archiver to transport the logs then you can not use real time apply.
    If you are using log writer to transpor the redo the realtime apply reduces the recovery time required if you need to failover as trher should be less redo to apply to bring the standby up to date, which mode you use to transport redo will depend on what is acceptable in terms of data loss and the impact on performance.

  • New Archived log entry in alert log after cpu patch 19 applied

    Has anyone applied October critical patch for 11.1.0.7? I applied the cpu Patch 19 (8892977) for 11.1.0.7 on several windows2008 servers and after the patch the alert log displays a new message everytime a redo log transfers. This only happens on servers that have archivelog on. It looks like there is some kind of trace set. Anyone know know what the message is?
    Thanks,
    Kathie
    Archived Log entry 10937 added for thread 1 sequence 10938 ID 0xa96e3908 dest 10:

    Hi Mark!
    Yes, Oracle informed me that this message is normal and is only used for formational purposes. I should just ignore it.
    Did you apply patch19? I have also found issues with a high amount of "waits" of type of "other". Some jobs are running slightly slower also. Also, if you check your "database health link" on dbconsole home page you will see consistant "non-critical" alerts. I don't have these alerts on servers not yet patched. This alerts appear to be caused by wait events of "other".
    Kathie

  • RMAN backup of archive logs

    I am sort of new to RMAN, I've been playing with it for a while but that's about as far as I've taken it. My question is does RMAN automatically backup any archive logs needed for recovery when I run "backup database" command or do I have to issue "backup database plus archive log" in order to insure recovery.

    Backup database also backups archivelogs.No,it does not. From documentation:
    backup database;
    Creates a backup set (AS BACKUPSET) or group of image copies (AS COPY) for all datafiles in the database. If generating a backup set, then RMAN can include only datafiles and control files: it cannot include archived redo logs.
    Werner

  • RMAN never deletes archive log backups

    Hi all,
    I have same problem as some of you have already faced.
    I have some instances 10.2.0.4 running un archive log mode.
    I take full hot backup daily.
    I setup a rman script to backup and delete obsolete backups according to the following policy:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    and then:
    run {
    ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
    BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/mnt/rman_202/pnetpres/db_pres_%U';
    CROSSCHECK ARCHIVELOG ALL;
    BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/mnt/rman_202/pnetpres/al_pres_%U';
    CROSSCHECK BACKUP;
    DELETE NOPROMPT OBSOLETE;
    DELETE NOPROMPT EXPIRED BACKUP;
    RELEASE CHANNEL RMAN_BACK_CH01;
    crosscheck archivelog all;
    delete noprompt archivelog all completed before 'sysdate -2';
    DB full backups are being deleted, however archive logs backups are not deleted.
    There are no tablespaces in backup or offline mode.
    How can I know the reason why some archive log backups are kept ?
    Even I clear the policy and perform a crosscheck and delete, those are not marked as obsolete neither deleted from disk.
    Thanks in advance.

    Hi Fernando,
    This are the ouputpus of the commands:
    RMAN> REPORT OBSOLETE;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    no obsolete backups found
    RMAN> LIST BACKUP OF ARCHIVELOG ALL;
    List of Backup Sets
    ===================
    BS Key Size Device Type Elapsed Time Completion Time
    1090 69.65M DISK 00:00:16 23-FEB-11
    BP Key: 1093 Status: AVAILABLE Compressed: YES Tag: TAG20110223T061511
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0jm5c6bf_1_1
    List of Archived Logs in backup set 1090
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 13 2173025156 21-FEB-11 2173028010 21-FEB-11
    1 14 2173028010 21-FEB-11 2173041730 21-FEB-11
    1 15 2173041730 21-FEB-11 2173041813 21-FEB-11
    1 16 2173041813 21-FEB-11 2173106066 22-FEB-11
    1 17 2173106066 22-FEB-11 2173108831 22-FEB-11
    1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
    1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
    1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
    1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
    1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
    1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    1411 125.43M DISK 00:00:28 24-FEB-11
    BP Key: 1414 Status: AVAILABLE Compressed: YES Tag: TAG20110224T061643
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0mm5eqqb_1_1
    List of Archived Logs in backup set 1411
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
    1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
    1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
    1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
    1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
    1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
    1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
    1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
    1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    1600 164.40M DISK 00:00:37 25-FEB-11
    BP Key: 1603 Status: AVAILABLE Compressed: YES Tag: TAG20110225T061643
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0pm5hf6b_1_1
    List of Archived Logs in backup set 1600
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
    1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
    1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
    1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
    1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
    1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
    1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    1829 132.24M DISK 00:00:30 26-FEB-11
    BP Key: 1832 Status: AVAILABLE Compressed: YES Tag: TAG20110226T061627
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0sm5k3hr_1_1
    List of Archived Logs in backup set 1829
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
    1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
    1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
    1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
    1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
    1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    2058 218.03M DISK 00:00:48 27-FEB-11
    BP Key: 2061 Status: AVAILABLE Compressed: YES Tag: TAG20110227T061628
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0vm5mnts_1_1
    List of Archived Logs in backup set 2058
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
    1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
    1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
    1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
    1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
    1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
    1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    2298 205.39M DISK 00:00:45 28-FEB-11
    BP Key: 2301 Status: AVAILABLE Compressed: YES Tag: TAG20110228T061620
    Piece Name: /mnt/rman_202/pnetproy/al_pres_12m5pc9l_1_1
    List of Archived Logs in backup set 2298
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
    1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
    1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
    1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
    1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
    1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
    1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    2546 180.29M DISK 00:00:39 01-MAR-11
    BP Key: 2549 Status: AVAILABLE Compressed: YES Tag: TAG20110301T061533
    Piece Name: /mnt/rman_202/pnetproy/al_pres_15m63to5_1_1
    List of Archived Logs in backup set 2546
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
    1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
    1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
    1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
    1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
    1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
    1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    2801 85.40M DISK 00:00:19 02-MAR-11
    BP Key: 2804 Status: AVAILABLE Compressed: YES Tag: TAG20110302T061613
    Piece Name: /mnt/rman_202/pnetproy/al_pres_18m66i5d_1_1
    List of Archived Logs in backup set 2801
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
    1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
    1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
    1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
    1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3058 137.93M DISK 00:00:30 03-MAR-11
    BP Key: 3061 Status: AVAILABLE Compressed: YES Tag: TAG20110303T061548
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1bm696gk_1_1
    List of Archived Logs in backup set 3058
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
    1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
    1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
    1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
    1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
    1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3324 138.96M DISK 00:00:31 04-MAR-11
    BP Key: 3327 Status: AVAILABLE Compressed: YES Tag: TAG20110304T061559
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1em6bqsv_1_1
    List of Archived Logs in backup set 3324
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
    1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
    1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
    1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
    1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
    1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3597 178.07M DISK 00:00:39 05-MAR-11
    BP Key: 3600 Status: AVAILABLE Compressed: YES Tag: TAG20110305T061543
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1hm6ef8f_1_1
    List of Archived Logs in backup set 3597
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
    1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
    1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
    1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
    1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
    1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
    1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3835 198.44M DISK 00:00:43 06-MAR-11
    BP Key: 3838 Status: AVAILABLE Compressed: YES Tag: TAG20110306T061548
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1km6h3kk_1_1
    List of Archived Logs in backup set 3835
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
    1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
    1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
    1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
    1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
    1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
    1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    4131 185.94M DISK 00:00:40 07-MAR-11
    BP Key: 4134 Status: AVAILABLE Compressed: YES Tag: TAG20110307T061546
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1nm6jo0i_1_1
    List of Archived Logs in backup set 4131
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
    1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
    1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
    1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
    1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
    1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
    1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    4435 161.37M DISK 00:00:35 08-MAR-11
    BP Key: 4438 Status: AVAILABLE Compressed: YES Tag: TAG20110308T061540
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1qm6mccc_1_1
    List of Archived Logs in backup set 4435
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
    1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
    1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
    1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
    1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
    1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
    1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    4745 79.24M DISK 00:00:18 09-MAR-11
    BP Key: 4748 Status: AVAILABLE Compressed: YES Tag: TAG20110309T061555
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1tm6p0os_1_1
    List of Archived Logs in backup set 4745
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
    1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
    1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
    1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
    1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    5270 135.13M DISK 00:00:31 10-MAR-11
    BP Key: 5273 Status: AVAILABLE Compressed: YES Tag: TAG20110310T061603
    Piece Name: /mnt/rman_202/pnetproy/al_proy_20m6rl53_1_1
    List of Archived Logs in backup set 5270
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
    1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
    1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
    1 58 2174307679 09-MAR-11 2174353241 09-MAR-11
    1 59 2174353241 09-MAR-11 2174384330 10-MAR-11
    1 60 2174384330 10-MAR-11 2174387259 10-MAR-11
    RMAN>
    For example the backups of archivelog from Feb 21st will never be deleted unless I force the delete.
    I'd like to understand why it happens :-)
    Thanks a lot,
    Regards,
    Diego.

  • Question about import in archive log mode

    Hello.
    I am a developer, I have ordered to write a script that makes the import of a schema of a database (release 9.2.0.7). That import will be done once a day. I have seen that in my development environment the import creates 54 archivers files (10M aprox. each), that means more that half a Gb a day, it seems too much to me.
    I cannot see why all those archivers can be useful. Would a good way of proceeding the following?
    1. Forcing an archiver just before the import (I do not know how to do that) so that a backup could be done to the state before the import.
    2. Disabling archive log mode during the import and enabling it just after the import (I do not know how to do that).
    3. Forcing a new archiver just after the import (I do not know how to do that).
    Thanks in advance.

    540M is not that much.
    One would question why you need to import every day,
    there must be better ways to do this.
    The three steps you propose look like an awful
    scenario, as it would require the database to switch
    from archivelog to noarchivelog and vice versa.
    This would require the database to close twice a
    day.
    The scenario is also incomplete as one would need to
    take a backup after the import
    If you can convince your DBA to close the database
    twice a day, he should write the script, which he can
    easily derive from the docs.
    But likely he will visit Billy Verreynne to borrow
    his lead pipe, and rightly so ;)
    Sybrand Bakker
    Senior Oracle DBAThanks for the answer.
    A few things:
    - Sorry for my ignorance, I have no experience in database backups, I do not understand why I need to backup just after the import.
    - That database is not critical, it is just for a team who will test on that database several applications, so the database will only need to be open during the office schedule.
    - I have no dba. The client has a dba for several databases but I have no contact with him/her nor my boss has.

  • How to control RMAN backup of archive logs in FRA

    Setup:
    11.2.0.2 GI
    ASM Diskgroup for Fast Recovery Area
    10.2.0.4 Enterprise Database
    Without Catalog Database
    To get familiar with Flashback Database we set up RMAN Backups
    without deleting the archive logs,
    as published in Oracle10g / 11g - Getting Started with Recovery Manager (RMAN) (Doc ID 360416.1)
    "These deletions are managed by Oracle when space is required."
    We observed that RMAN takes backups of all archive logs every time,
    here we go with backing up archive logs every 30 minutes.
    So the question is:
    Is this (backing up all archive logs every time) the expected behavior or
    the result of not using a catalog database or
    any other mismatch?
    thanx for any hint
    Michael

    Hi Michael,
    In Note 360416.1 it refers to two archivelog backup commands.
    BACKUP ARCHIVELOG ALL;and
    BACKUP ARCHIVELOG FROM TIME 'SYSDATE-30' UNTIL TIME 'SYSDATE-7';Your question:
    Is this (backing up all archive logs every time) the expected behavior or the result of not using a catalog database or any other mismatch?If you used the first script you will backup alle archivelogs everytime.
    If you use the second one it will do a subset (probably not the range you want to backup...)
    You could implement another script
    BACKUP ARCHIVELOG NOT BACKED UP 2 TIMES;So every archivelog is only backed up twice.
    Check
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#i78895
    for more information.
    Regards,
    Tycho

  • 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

  • RMAN Backups for archive logs

    Hi,
    We are taking daily backups using BCV's and archive backup to tapes using RMAN. Please note we are using RMAN only for archive backups.
    We are changing our backup strategy and I need below information on RMAN.
    1) Is there any benefit I will be getting if I use RMAN for archive backups ( like finding the courruption in the logs,health of the archive) etc? Any reference note for this would be great.
    2) If I use multiplexing of archives using LOG_ ARCHIVE_DEST & LOG_ ARCHIVE_DUPLEX_DEST with this I want RMAN to take the backup of archives and delete from one location only ( Say from LOG_ ARCHIVE_DEST ). And I want the archives in LOG_ ARCHIVE_DUPLEX_DEST to maintain on my own ( Like different purge strategy to zip and keep for 7 days in this location.
    If I use command "backup archivelog all delete input" it is picking and removing radomly from either of these locations. Is there a way I can configure RMAN so that it will not touch my secondary locaton?
    Thanks in advance.
    Thanks,
    Varma

    >
    1) Is there any benefit I will be getting if I use RMAN for archive backups ( like finding the courruption in the logs,health of the archive) etc? Any reference note for this would be great.
    You can use validate backupset command to check the health of backup.
    2) If I use multiplexing of archives using LOG_ ARCHIVE_DEST & LOG_ ARCHIVE_DUPLEX_DEST with this I want RMAN to take the backup of archives and delete from one location only ( Say from LOG_ ARCHIVE_DEST ). And I want the archives in LOG_ ARCHIVE_DUPLEX_DEST to maintain on my own ( Like different purge strategy to zip and keep for 7 days in this location.
    Yes, you can do that.
    If I use command "backup archivelog all delete input" it is picking and removing radomly from either of these locations. Is there a way I can configure RMAN so that it will not touch my secondary locaton?
    You can allocate channels for that.
    regards

  • 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....

  • RMAN-08137: WARNING: archived log not deleted as it is still needed

    I am trying to delete archive logs older than 7 days in streams environment.
    1) we dont have a standby database
    2) checkpoint_retention_time = 7
    Please help me with this.
    Regards,
    Mike

    SQL> set serveroutput on
    DECLARE
    hScn number := 0;
    lScn number := 0;
    sScn number;
    ascn number;
    alog varchar2(1000);
    begin
    select min(start_scn), min(applied_scn) into sScn, ascn
    from dba_capture;
    DBMS_OUTPUT.ENABLE(2000);
    for cr in (select distinct(a.ckpt_scn)
    from system.logmnr_restart_ckpt$ a
    where a.ckpt_scn <= ascn and a.valid = 1
    and exists (select * from system.logmnr_log$ l
    where a.ckpt_scn between l.first_change# and l.next_change#)
    order by a.ckpt_scn desc)
    loop
    if (hScn = 0) then
    hScn := cr.ckpt_scn;
    else
    lScn := cr.ckpt_scn;
    exit;
    end if;
    end loop;
    if lScn = 0 then
    lScn := sScn;
    end if;
    dbms_output.put_line('Capture will restart from SCN ' || lScn ||' in the following file:');
    for cr in (select name, first_time
    from DBA_REGISTERED_ARCHIVED_LOG
    where lScn between first_scn and next_scn order by thread#)
    loop
    dbms_output.put_line(cr.name||' ('||cr.first_time||')');
    end loop;
    end;
    After i ran the above script from metalink i got the below output.
    When I have run the above code that is given in metalink to check the minimum archive logs required to restart streams i got the below ouput.
    Capture will restart from SCN 55313283790in the following file:
    +FLASH/ORCL/archivelog/2011_02_22/thread_1_seq_842.346.443519740 (11-MAR-11)*
    +FLASH/ORCL/archivelog/2011_02_22/thread_2_seq_832.189.440690538 (11-MAR-11)*
    Does this mean that I will not be able to delete the archive logs from 11-mar-11 ?
    Regards,
    Mike

  • RMAN copies of archived logs view

    When I backup the archivelogs with this statement:
    backup as copy archivelog all;
    Why are these copies not shown in the RC_BACKUP_ARCHIVELOG_DETAILS view?
    The Description says:
    BTYPE      CHAR(9)      The backup type container, which can be BACKUPSET, IMAGECOPY or PROXYCOPY.
    In which view or table are this files represented?
    Thanks!
    Edited by: 916796 on 24.02.2012 04:15
    Edited by: 916796 on 24.02.2012 06:29

    OK
    I think V$BACKUP_REDOLOG is the one.
    http://docs.oracle.com/cd/E11882_01/server.112/e25513/dynviews_1060.htm#REFRN30024
      SELECT * FROM V$BACKUP_REDOLOG ;
    set linesize 200
    SELECT THREAD#, SEQUENCE#, FIRST_TIME, NEXT_CHANGE#, NEXT_TIME, BLOCKS FROM V$BACKUP_REDOLOG;
    -- archive logs backed up
    select
      THREAD#,
       MAX(SEQUENCE#)
    FROM 
      V$BACKUP_REDOLOG
    GROUP BY
      THREAD#;Best Regards
    mseberg
    Edited by: mseberg on Feb 24, 2012 7:37 AM
    Later
    I did a test on one of my test databases
    SQL> SELECT DBID  FROM V$DATABASE;
          DBID
    1612176986And then
    SELECT
      DB_KEY
    FROM
      RMANCAT.RC_DATABASE
    WHERE
      DBID = 1612176986;  Once I have this I can query the "RC" tables
    SELECT
    FROM
      RMANCAT.RC_ARCHIVED_LOG
    WHERE DB_KEY = 2511344 ;   -- 72It returns 72 rows so I did a log switch and ran the query again, the count remained 72.
    Next I tried this :
    SELECT
    FROM
      RMANCAT.RC_BACKUP_ARCHIVELOG_DETAILS
        WHERE DB_KEY = 2511344;  I expected another 72, but got 66. I did another log switch and it remained 66.
    So I think you are right about the RC_ tables. And they seem to only hold backup info.
    RC_ARCHIVED_LOG shows the most promise. The query should probably include a AND IS_STANDBY = 'NO'
    Having a difficult time finding exactly what you want.
    Edited by: mseberg on Feb 24, 2012 2:46 PM

Maybe you are looking for

  • Please help me to get out of this nightmare and mi...

    Hi I need to unlink my microsoft account (old live ID) from my skype account. I am getting an error: This account has been suspended. Please contact Skype Customer Support to resolve this issue before unlinking this account. Filled out the useless fo

  • TS1424 I am having trouble getting Itunes to open

    I am having trouble getting ITUNES to work I have deleted itunes and everything associated with it and reinstalled and I still get the same errors, The application has failed to start because of MSVCR80.DLL INTUNES WAS NOT INSTALLED CORRECTLY  ERROR

  • Sorting files for distributed systems for Documaker

    Hello, I've been asked to research tools that will assist with fast sorting of files for the distributed systems for Documaker. Unfortunately, I have not had any exposure to Documaker so I'm starting from scratch. Anyone have any experience with this

  • Diagnosing a Kernel Panic (Macbook Pro 6,2)

    I'm hoping that someone can diagnose this kernel panic for me. Thanks! Sun Jun 16 20:23:17 2013 panic(cpu 1 caller 0xffffff80002c4794): Kernel trap at 0xffffff80002121dc, type 13=general protection, registers: CR0: 0x000000008001003b, CR2: 0x00000001

  • Hey :) Need some help from someone a bit more tech...

    Would anyone please check if my cabinet will get Infinity please? Apparently its coming on the 31st March I know about 100 metres down the road gets Virgin Media but we dont! Its a new build estate. My postcode is LN1 1AW.  Thanks in advance J