ARCHIVELOGS

Hi I have problem loading archivelogs on the standby database that i have created.
I created my standby database in accordance with oracles instruction but for the time being i am just implementing a non-managed standby database in which i copy the archivelogs from the primary server to the standby server.
On the primary server i issue the following command:
Alter system switch logfile;
then navigate to the location of the archivelogs and copy them to '/u01/archivelogs' on the standby server.
My standby server is already mounted i.e alter database mount standby database.
I then issue the command and the i type AUTO is this the correct way of applying archivelogs and how can i see if has been successful, thanks:
SQL> recover from '/u01/archivelogs' standby database;
ORA-00279: change 763058 generated at 06/07/2007 09:43:58 needed for thread 1
ORA-00289: suggestion : /u01/archivelogs/1_13_624107328.dbf
ORA-00280: change 763058 for thread 1 is in sequence #13
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00279: change 764866 generated at 06/07/2007 09:54:50 needed for thread 1
ORA-00289: suggestion : /u01/archivelogs/1_14_624107328.dbf
ORA-00280: change 764866 for thread 1 is in sequence #14
ORA-00278: log file '/u01/archivelogs/1_13_624107328.dbf' no longer needed for
this recovery
ORA-00279: change 765003 generated at 06/07/2007 09:56:42 needed for thread 1
ORA-00289: suggestion : /u01/archivelogs/1_15_624107328.dbf
ORA-00280: change 765003 for thread 1 is in sequence #15
ORA-00278: log file '/u01/archivelogs/1_14_624107328.dbf' no longer needed for
this recovery
ORA-00308: cannot open archived log '/u01/archivelogs/1_15_624107328.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3

Which archivelogs have you copied to the standby site? In case there were two of them (/u01/archivelogs/1_13_624107328.dbf, /u01/archivelogs/1_14_624107328.dbf
), then everything is fine.
The AUTO option of recover clause just applies the archivelogs in ascending order of sequence - the 13, then 14, then 15... As it never knows, which one is the last, it just tries the archivelog for next sequence number. When it doesn't exist, the auto recovery exits with ORA-308 together with "Linux Error: 2: No such file or directory". This is expected result.
The messages ORA-278 (log file no longer needed for recovery) inform, that the existing archivelogs (sequence 13 and 14) have been applied on standby database.
Best regards,
Martin

Similar Messages

  • Problem with archivelogs in a phy stb

    Hi every body!
    I want ask you about my problem with the archivelogs in a physical standby.
    this standby works perfectly, but every time it recives a archivelog from the primary database, it generates another archivelog bigger than the it recives.
    -rw-r----- 1 oracle dba 43314176 Mar 13 16:06 1_1794.dbf
    -rw-r----- 1 oracle dba 52429824 Mar 13 16:06 1_1795.dbf
    Those files are archivelogs. 1794 is recived from the primary database, and 1795 is generated by the standby, as you can see the 1795 is bigger than 1794.
    when i generate another archivelog this is the result:
    -rw-r----- 1 oracle dba 4290560 Mar 13 16:40 1_1795_637513013.dbf
    -rw-r----- 1 oracle dba 52429824 Mar 13 16:40 1_1796_637513013.dbf
    i generate 1795 in primary database, and physical standby generated 1796...
    Doy you know the solution to my problem....
    Thanks a lot for your time.

    Yep you do have to down the standby database I'm afraid, do a shutdown immediate then a startup nomount then issue the alter database mount standby database; command. Once this is done run the below statements to recreate the relevant standby redo logs. See the below SQL for a syntax example.
    ALTER DATABASE DROP STANDBY LOGFILE GROUP 4;
    ALTER DATABASE DROP STANDBY LOGFILE GROUP 5;
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 ('D:\somepath\STBYREDO_GRP4_A.LOG','D:\somepath\STBYREDO_GRP4_B.LOG') SIZE 100M;
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 5 ('D:\somepath\STBYREDO_GRP5_A.LOG','D:\somepath\STBYREDO_GRP5_B.LOG') SIZE 100M;

  • How to delete the foreign archivelogs in a Logical Standby database

    How do I remove the foreign archive logs that are being sent to my logical standby database. I have files in the FRA of ASM going back weeks ago. I thought RMAN would delete them.
    I am doing hot backups of the databases to FRA for both databases. Using ASM, FRA, in a Data Guard environment.
    I am not backing up anything to tape yet.
    The ASM FRA foreign_archivelog directory on the logical standby FRA keeps growing and nothing is get deleted when
    I run the following command every day.
    delete expired backup;
    delete noprompt force obsolete;
    Primary database RMAN settings (Not all of them)
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE DB_UNIQUE_NAME 'WMRTPRD' CONNECT IDENTIFIER 'WMRTPRD_CWY';
    CONFIGURE DB_UNIQUE_NAME 'WMRTPRD2' CONNECT IDENTIFIER 'WMRTPRD2_CWY';
    CONFIGURE DB_UNIQUE_NAME 'WMRTPRD3' CONNECT IDENTIFIER 'WMRTPRD3_DG';
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    Logical standby database RMAN setting (not all of them)
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    How do I cleanup/delete the old ASM foreign_archivelog files?

    OK, the default is TRUE which is what it is now
    from DBA_LOGSTDBY_PARAMETERS
    LOG_AUTO_DELETE     TRUE          SYSTEM     YES
    I am not talking about deleting the Archive logs files for the Logical database that it is creating, but the Standby archive log files being sent to the Logical Database after they have been applied.
    They are in the alert log as follows under RFS LogMiner: Registered logfile
    RFS[1]: Selected log 4 for thread 1 sequence 159 dbid -86802306 branch 763744382
    Thu Jan 12 15:44:57 2012
    *RFS LogMiner: Registered logfile [+FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297] to LogM*
    iner session id [1]
    Thu Jan 12 15:44:58 2012
    LOGMINER: Alternate logfile found. Transition to mining archived logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/
    foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297
    LOGMINER: End mining logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/threa
    d_1_seq_158.322.772386297
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 159, +DG1/wmrtprd2/onlinelog/group_4.284.771760923                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • How to delete archivelog with RMAN in the Primary and Standby database?

    Hello,
    I am working on Oracle 10gR2.
    My question is :
    How could I implement a automatized and secure way of:
    1) Delete archivelogs on my PRIMARY server only when these logs are successfully TRANSFERED to all my standby databases?
    2) Delete archivelogs on my STANDBY server only when these logs are sucessfully APPLIED to the database?
    Thanks a lot for your help!

    on 10G
    CONFIGURE ARCHIVELOG DELETION POLICY TO [CLEAR | NONE | APPLIED ON STANDBY];
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm#CHDBEICE
    Coskan Gundogar
    http://coskan.wordpress.com

  • How to find out the reasion that database have a lot of archivelog files?

    Hi All
    Yesterday and Today , my database have a lot of archivelog files. So much so that I set remove archive every 2 hours in crontab. I don't know the reason.
    I just set audit the user but I set noaudit this user later.
    I made the AWR for 2 days but I didn't find any unsual things.
    Somebody please help me because my database is a production
    Thanks

    924728 wrote:
    Hi All
    Yesterday and Today , my database have a lot of archivelog files. So much so that I set remove archive every 2 hours in crontab. I don't know the reason.I hope you backed them up before removing!
    >
    I just set audit the user but I set noaudit this user later.Which user? If you know which, you can investigate what he is doing
    >
    I made the AWR for 2 days but I didn't find any unsual things.The AWR report will tell you at the top the redo generated per second, and lower in the body of the report the redo generated throughout the entire period. Have these figures changed from what is "usual"?
    >
    Somebody please help me because my database is a productionDo you actually have a problem? Have any users complained about anything?
    >
    Thanks

  • Flash recovery area: archivelog file directory modification time

    Using Oracle Database 10g Release 10.2.0.3.0 - 64bit (Standard Edition) on Solaris 10, SunOS 5.10 Generic_118833-33, archivelog files in the Flash Recovery Area are still present, after the time that they should have been made redundant and therefore deleted::
    bvsmdb01-oracle10g $ date
    Thu Jan 24 16:04:46 GMT 2008
    bvsmdb01-oracle10g $ ls -lt archivelog
    total 20
    drwxr-x--- 2 oracle10g oinstall 1024 Jan 24 16:00 2008_01_24
    drwxr-x--- 2 oracle10g oinstall 512 Jan 23 23:30 2008_01_19
    drwxr-x--- 2 oracle10g oinstall 1536 Jan 23 23:04 2008_01_23
    drwxr-x--- 2 oracle10g oinstall 1536 Jan 22 23:30 2008_01_18
    drwxr-x--- 2 oracle10g oinstall 1536 Jan 22 22:53 2008_01_22
    drwxr-x--- 2 oracle10g oinstall 1024 Jan 21 23:07 2008_01_21
    drwxr-x--- 2 oracle10g oinstall 512 Jan 20 22:20 2008_01_20
    bvsmdb01-oracle10g $
    The archivelog directory for 2008_01_19 has a modification time of Jan 23 23:30 - this is almost 4 days after it was last written to.
    The current redundancy setting in RMAN is shown in the output of show all:
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/dbs/snapcf_kierli.f'; # default
    So, the current retention policy is three days. It is 24/1 today - the archivelog directory from 19/1 should have been deleted by now, but it has not been.
    The modification time for the archivelog directory 2008_01_19 has a modification time of Jan 23 23:30 2008.
    Why is this? How can this be investigated? Does anyone have any suggestions?
    Thanks
    Jerry Mander

    From 2 Day DBA:
    Even after files in the flash recovery area are obsolete, they are generally not deleted from the flash recovery area until space is needed to store new files. As long as space permits, files recently moved to tape will remain on disk as well, so that they will not have to be retrieved from tape in the event of a recovery.
    What is the current space used in the FRA and what is the FRA disk limit ?

  • Retention Policy to delete both backup sets and archivelogs automatically

    I configured the Recovery Window-Based Retention Policy for my database for the window=14 days. I also set up a crontab to do a full backup every Monday. So say in a month, there will be 30 archive logs and 4 full DB backup sets.
    Now that I understand if the FRA gets filled up, older archive logs that are not needed for the 14 days recoverable window will be automatically deleted. My questions is what happen to the old backup sets? Will they get deleted automatically too if there is no space left in FRA? Or I need to use "DELETE OBSOLETE" to delete them?
    Thanks.

    One of the advantages of the FRA is, in case of space pressure obsolete objects (obsolete due to the defined retention policy) are deleted automatically. That's true for backups and archivelogs. The objects are NOT deleted automatically after the retention policy expires, but only when additional space is needed. That does not mean you don't have to care about FRA space consumption. You may have unusual amounts of archivelogs, additional backups and flashback logs (if flashback database is configured), which fill up the FRA.
    Werner

  • Retention policy vs. Archivelog deletion policy

    Environment:
    Oracle EE 11.2.0.3 on Solaris 10.5
    Which policy takes precedence?
    My Retention Policy is set to 'Recovery window of 8 days' and my Archivelog deletion policy is set to 'backed up 2 times to disk'.
    My DAILY full backup happens at 03:00am and uses the following commands:
    backup incremental level 0 cumulative database tag 'full_daily' plus archivelog tag 'full_daily';
    DELETE NOPROMPT OBSOLETE;I also have an archivelog backup that runs every 4 hours at 02:00, 06:00, 10:00, 14:00, 18:00 and 22:00 and looks like this:
    backup archivelog all tag '&1';
    delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';With the archivelog backup running every 4 hours the logs are getting backed up to disk the required 2 times very quickly. Much sooner than 8 days! :-)
    I have a problem where the archivelog backup that runs immediately AFTER the full database backup fails due to not being able to find some older archivelog files.
    In looking at V$ARCHIVED_LOG the files were dated (COMPLETION_DATE) just outside the 8 day retention window but they had a status of 'A' (Archived) instead of the 'D' (Deleted) I was expecting. When I ran a 'Crosscheck archivelog all' it changed the statuses to 'D' and the next archivelog backup ran successfully.
    What am I missing?
    Should I change the archivelog deletion policy to something else? If so, what and why (just trying to understand!) ?
    I am not using an FRA and have controlfile autobackup turned on.
    Please let me know if you need more information. I have been scouring the docs and the 11g RMAN Oracle Press book but haven't found the trick yet!
    Thanks for any assistance!
    -gary

    Hemant K Chitale wrote:
    The Retention Policy applies to Backups. It does not apply to ArchiveLogs.
    The ArchiveLog Deletion Policy applies to ArchiveLogs. It does not apply to Backups.
    Since you have 2 copies of ArchiveLogs in the backups and these are retained for 8 days, a "delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';" is overkill. Why retain 8 days of archivelogs on disk if there are 2 copies already backed up ?
    Does your full backup that begins at 3am complete before 6am ? If it goes beyond 6am, it will be deleting some files after 6am but the "backup archivelog all" at 6am will expect some archivelogs (8 days old) to be present.
    Hemant K Chitale
    RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/oracle/oracle/.Autobackup_CTRL/%F.ctl_bkp';    
    Starting backup at 22-MAY-12
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00001 name=/oracle/oracle/oradata/orcl/system01.dbf
    output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_system_7vpg432v_.dbf tag=TAG20120522T122602 RECID=1 STAMP=783951999
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:46
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00002 name=/oracle/oracle/oradata/orcl/sysaux01.dbf
    output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_sysaux_7vpg5l1n_.dbf tag=TAG20120522T122602 RECID=2 STAMP=783952038
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:35
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00003 name=/oracle/oracle/oradata/orcl/undotbs01.dbf
    output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_undotbs1_7vpg6ms0_.dbf tag=TAG20120522T122602 RECID=3 STAMP=783952046
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
    channel ORA_DISK_1: starting datafile copy
    input datafile file number=00004 name=/oracle/oracle/oradata/orcl/users01.dbf
    output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_users_7vpg6ptn_.dbf tag=TAG20120522T122602 RECID=4 STAMP=783952047
    channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
    Finished backup at 22-MAY-12
    Starting Control File and SPFILE Autobackup at 22-MAY-12
    piece handle=/oracle/oracle/product/11.2.0/dbhome_1/dbs/controlfile_c-1309370544-20120522-02 comment=NONE
    Finished Control File and SPFILE Autobackup at 22-MAY-12
    ORA-00604: error occurred at recursive SQL level 1
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    RMAN-08132: WARNING: cannot update recovery area reclaimable file list
    old RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
    new RMAN configuration parameters:
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/oracle/oracle/.Autobackup_CTRL/%F.ctl_bkp';
    new RMAN configuration parameters are successfully stored
    RMAN> delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';
    released channel: ORA_DISK_1
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=196 device type=DISK
    RMAN-08138: WARNING: archived log not deleted - must create more backups
    archived log file name=/oracle/oracle/flash_recovery_area/ORCL/archivelog/2012_04_28/o1_mf_1_2_7sq8tf5p_.arc thread=1 sequence=2
    RMAN-08138: WARNING: archived log not deleted - must create more backups
    archived log file name=/oracle/oracle/flash_recovery_area/ORCL/archivelog/2012_05_22/o1_mf_1_3_7vpdcjjm_.arc thread=1 sequence=3
    ORA-00604: error occurred at recursive SQL level 1
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    RMAN-08132: WARNING: cannot update recovery area reclaimable file list
    RMAN> having problem with Archivelog backup.

  • Rman errors on restore archivelog

    Hi all,
    I am running scripts to back up database every day , but after while 7 days it start to give me errors like:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 12/16/2003 04:06:04
    RMAN-06026: some targets not found - aborting restore
    RMAN-06025: no backup of log thread 1 seq 43 scn 3924903 found to restore ...........
    that is script:
    $ORACLE_HOME/bin/rman target / << EOF
    configure retention policy to redundancy 3;
    configure retention policy to recovery window of 3 days;
    configure backup optimization on;
    configure controlfile autobackup off;
    configure default device type to Disk;
    configure device type Disk parallelism 1;
    configure datafile backup copies for device type Disk to 1;
    configure channel device type Disk format '/backup/%d_datafile_%s_%p.bak';
    configure maxsetsize to unlimited;
    configure snapshot controlfile name to '/backup/prod_snapcf.f';
    set controlfile autobackup format for device type Disk to '/backup/prod_controlfile_%F';
    show all;
    run {
    allocate channel ch1 type Disk maxpiecesize = 1900M;
    backup full database noexclude
    include current controlfile
    format '/backup/%d_datafile_%s_%p.bak'
    tag 'prod_datafile_daily';
    run {
    allocate channel ch1 type Disk maxpiecesize = 1900M;
    backup archivelog all
    delete all input
    format '/backup/%d_archivelog_%s_%p.bak'
    tag 'prod_archivelog_daily';
    run {
    allocate channel ch1 type Disk maxpiecesize = 1900M;
    backup format '/backup/%d_controlfile_%s.bak' current controlfile;
    crosscheck backup;
    restore controlfile to '/backup' validate;
    restore tablespace SYSTEM validate;
    restore archivelog all validate;
    list backup of database;
    report unrecoverable;
    report schema;
    report need backup;
    report obsolete;
    delete noprompt expired backup of database;
    delete noprompt expired backup of controlfile;
    quit
    I can resetlogs and that error disapeire
    Does anybody know that wrong with that script?
    Thanks

    Really the error is very strange realizing that if functions well for about 6 days or something like that.
    this is a notable line in the error.
    some targets not found - aborting restore
    I recommend you to check very well your targets path
    to be restore. I think that is the cause of the failure.
    Joel P�rez

  • How do I clone a database but still apply old archivelogs? Getting ORA-1223

    Hi,
    I'm doing a clone from PROD to DEV in 9.2.0.6 for 11.5.10.2 on Solaris 9. I worked through many issues, such as copying the files, changing the init<SID>.ora to the new DEV values, re-editing all of the env files with the new SID on the new (target) machine name, etc.
    The data is about 2 weeks old and so I was hoping to not only recover this database during the clone, but ALSO roll forward, applying all of the old archive logs to date. (Nothing changed in the middle tier save for a few
    paramaters in the xml file which I've already edited).
    Normally when I'm cloning -- I do it with fresh/recent data files so I don't care about reseting the archivelogs, I just reset them and say si-a-nerra!
    But.... now I am trying to both change the database name (SID) and apply a bunch of archvie logs (about 2 weeks worth). Note: I also recreate the control file as part of my whole process too.
    Here's the problem I am having -- after doing a startup nomount in the new location (with my new environment files, data files, etc all in place) and
    then doing @recreate.sql (which is the edited control file script from the 'backup controlfile to trace' on prod) I am getting this message:
    SQL> @recreate.sql
    CREATE CONTROLFILE SET DATABASE "DEV11i" NORESETLOGS
    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01223: RESETLOGS must be specified to set a new database name
    - well OK this message makes sense to me - yes I could easily just keep the new name and say RESETLOGS, but I don't want to do this !!! I want to set the new name for the clone, and keep the logs unset so that I can then recover until cancel, applying my 2 weeks worth of logs.
    - What is the solution? Do I have to just bite the bullet and do RESETLOGS instead? (and in effect make my recovery practice seperate from my current cloning tasks)
    - Or should I change everything back to the old (original name) LIVE11i (for Prod), including the env files, data files etc .. on the new (target) machine.., recover the database completely (maybe even disconnect it from the network and rename the (target) machine to the old prod server name), and then do another whole procedure (which I'd have to find - but I know it's similar) for changing the SID...
    Please help. Thanks in advance! Marvin.
    Message was edited by:
    umfan866

    Oviwan,
    Because of getting the error message, the recreate controlfile has not
    gone through, thus I have not yet reset the logs.
    What I'm going to do for now is in fact change the script to SET
    the new name for DEV11i and RESET the logs, just to test my clone. The
    data will be 2 weeks out of date, but I'll have verified that my files from tape
    work (these files had come of the tape, and are now 2 weeks old).
    To make the DB fresher, I can just re-clone with RESET using last night's
    hot backup from PROD. That'll freshen DEV's files up no problem.
    I had wanted to test all these archive logs and see if they apply nicely,
    but I'll just have do that on a separate box (disconnected from the network)
    where I keep the DB name and machine name the same as prod.
    Thanks for your help! Marvin.

  • How to check for archivelog backup on a particular date or time?

    Dear All,
    We have RMAN full database, cumulative and archivelog backup(eg location: Diskgroup A) scheduled on a regular period basis. Assume archivelog location is Diskgroup B. The diskgroup B became full and unable to archive further, since no space. Unable to connect to database, connect internal only until freed error. alert log also shows that archiver error. So the solution for this to clear some space in diskgroup B by removing some old archive logs. In our environment, everyday the archive logs are stored in a separated folder arranged in date wise.  I can do that . But before clearing some space, i need to make sure that the folder( or any date folder what im going to delete) is backed up or not. How to check that? Any idea please?
    eg: i have archivelogs like this in folders
    01_11_2013/
    02_11_2013/
    03_11_2013/
    04_11_2013/
    05_11_2013/
    06_11_2013/
    If i want to remove the folder 01_11_2013/( and its contents ie archivelogs) , how to check whether the archivelogs in this folder 01_11_2013/ is backed up or not?
    Regards,

    Pradeepcmst wrote:
    Dear All,
    We have RMAN full database, cumulative and archivelog backup(eg location: Diskgroup A) scheduled on a regular period basis. Assume archivelog location is Diskgroup B. The diskgroup B became full and unable to archive further, since no space. Unable to connect to database, connect internal only until freed error. alert log also shows that archiver error. So the solution for this to clear some space in diskgroup B by removing some old archive logs. In our environment, everyday the archive logs are stored in a separated folder arranged in date wise.  I can do that . But before clearing some space, i need to make sure that the folder( or any date folder what im going to delete) is backed up or not. How to check that? Any idea please?
    eg: i have archivelogs like this in folders
    01_11_2013/
    02_11_2013/
    03_11_2013/
    04_11_2013/
    05_11_2013/
    06_11_2013/
    If i want to remove the folder 01_11_2013/( and its contents ie archivelogs) , how to check whether the archivelogs in this folder 01_11_2013/ is backed up or not?
    Regards,
    rman> list backup;
    Which begs the question .. why is the FRA getting filled in the first place?  Is it seriously undersized?  Are you not doing regular housekeeping with rman 'delete obsolete' and 'backup archivelog delete input'

  • How to restore archivelogs on RAC ?

    Hello !
    I need to restore archivelogs for 2 hours: to_date('04/08/2010 23:00:00','dd/mm/yyyy HH24:mi:ss')" until time "to_date('05/08/2010 01:00:00','dd/mm/yyyy hh24:mi:ss'). I have this files on tape:
    RMAN> list backup of archivelog from time "to_date('04/08/2010 23:00:00','dd/mm/yyyy HH24:mi:ss')" until time "to_date('05/08/2010 01:00:00','dd/mm/yyyy hh24:mi:ss')";
    List of Backup Sets
    ===================
    BS Key  Size
    1359667 19.00M
      List of Archived Logs in backup set 1359667
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      3    24686   68236434950 04/08/2010 22:54:47 68243156430 04/08/2010 23:46:12
      Backup Set Copy #1 of backup set 1359667
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:03:50     04/08/2010 23:51:06 NO         TAG20100804T234715
        List of Backup Pieces for backup set 1359667 Copy #1
        BP Key  Pc# Status      Media                   Piece Name
        1359674 1   AVAILABLE   NN0876L3                /ORACLE:SVPRD1B:REDO:153543_726191236_1/
      Backup Set Copy #2 of backup set 1359667
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:03:50     04/08/2010 23:51:06 NO         TAG20100804T234715
        List of Backup Pieces for backup set 1359667 Copy #2
        BP Key  Pc# Status      Media                   Piece Name
        1359675 1   AVAILABLE   NN0261L3                /ORACLE:SVPRD1B:REDO:153543_726191236_2/
    BS Key  Size
    1359668 19.96G
      List of Archived Logs in backup set 1359668
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      1    33810   68236430016 04/08/2010 22:54:44 68240656570 04/08/2010 23:25:13
      Backup Set Copy #1 of backup set 1359668
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:22:24     05/08/2010 00:09:39 NO         TAG20100804T234715
        List of Backup Pieces for backup set 1359668 Copy #1
        BP Key  Pc# Status      Media                   Piece Name
        1359676 1   AVAILABLE   NN0876L3                /ORACLE:SVPRD1B:REDO:153541_726191236_1/
      Backup Set Copy #2 of backup set 1359668
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:22:24     05/08/2010 00:09:39 NO         TAG20100804T234715
        List of Backup Pieces for backup set 1359668 Copy #2
        BP Key  Pc# Status      Media                   Piece Name
        1359677 1   AVAILABLE   NN0261L3                /ORACLE:SVPRD1B:REDO:153541_726191236_2/
    BS Key  Size
    1359669 2.56G
      List of Archived Logs in backup set 1359669
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      1    33811   68240656570 04/08/2010 23:25:13 68243156997 04/08/2010 23:46:13
      Backup Set Copy #1 of backup set 1359669
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:02:38     05/08/2010 00:12:20 NO         TAG20100804T234715
        List of Backup Pieces for backup set 1359669 Copy #1
        BP Key  Pc# Status      Media                   Piece Name
        1359678 1   AVAILABLE   NN0876L3                /ORACLE:SVPRD1B:REDO:153544_726192582_1/
      Backup Set Copy #2 of backup set 1359669
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:02:38     05/08/2010 00:12:20 NO         TAG20100804T234715
        List of Backup Pieces for backup set 1359669 Copy #2
        BP Key  Pc# Status      Media                   Piece Name
        1359679 1   AVAILABLE   NN0261L3                /ORACLE:SVPRD1B:REDO:153544_726192582_2/
    BS Key  Size
    1359670 19.95G
      List of Archived Logs in backup set 1359670
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      2    33578   68236472935 04/08/2010 22:55:03 68240747010 04/08/2010 23:26:01
      Backup Set Copy #1 of backup set 1359670
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:26:38     05/08/2010 00:13:54 NO         TAG20100804T234715
        List of Backup Pieces for backup set 1359670 Copy #1
        BP Key  Pc# Status      Media                   Piece Name
        1359680 1   AVAILABLE   NN0876L3                /ORACLE:SVPRD1B:REDO:153542_726191236_1/
      Backup Set Copy #2 of backup set 1359670
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:26:38     05/08/2010 00:13:54 NO         TAG20100804T234715
        List of Backup Pieces for backup set 1359670 Copy #2
        BP Key  Pc# Status      Media                   Piece Name
        1359681 1   AVAILABLE   NN0261L3                /ORACLE:SVPRD1B:REDO:153542_726191236_2/
    BS Key  Size
    1359671 2.48G
      List of Archived Logs in backup set 1359671
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      2    33579   68240747010 04/08/2010 23:26:01 68243160092 04/08/2010 23:46:14
      Backup Set Copy #1 of backup set 1359671
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:02:46     05/08/2010 00:16:48 NO         TAG20100804T234715
        List of Backup Pieces for backup set 1359671 Copy #1
        BP Key  Pc# Status      Media                   Piece Name
        1359682 1   AVAILABLE   NN0876L3                /ORACLE:SVPRD1B:REDO:153545_726192843_1/
      Backup Set Copy #2 of backup set 1359671
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:02:46     05/08/2010 00:16:48 NO         TAG20100804T234715
        List of Backup Pieces for backup set 1359671 Copy #2
        BP Key  Pc# Status      Media                   Piece Name
        1359683 1   AVAILABLE   NN0261L3                /ORACLE:SVPRD1B:REDO:153545_726192843_2/
    BS Key  Size
    1359733 17.25M
      List of Archived Logs in backup set 1359733
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      3    24687   68243156430 04/08/2010 23:46:12 68260260710 05/08/2010 01:41:22
      Backup Set Copy #1 of backup set 1359733
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:02:48     05/08/2010 01:51:01 NO         TAG20100805T014812
        List of Backup Pieces for backup set 1359733 Copy #1
        BP Key  Pc# Status      Media                   Piece Name
        1359743 1   AVAILABLE   NN0821L3                /ORACLE:SVPRD1B:REDO:153560_726198493_1/
      Backup Set Copy #2 of backup set 1359733
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:02:48     05/08/2010 01:51:01 NO         TAG20100805T014812
        List of Backup Pieces for backup set 1359733 Copy #2
        BP Key  Pc# Status      Media                   Piece Name
        1359744 1   AVAILABLE   NN0833L3                /ORACLE:SVPRD1B:REDO:153560_726198493_2/
    BS Key  Size
    1359739 9.97G
      List of Archived Logs in backup set 1359739
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      1    33812   68243156997 04/08/2010 23:46:13 68253559461 05/08/2010 00:55:07
      1    33813   68253559461 05/08/2010 00:55:07 68260254831 05/08/2010 01:41:19
      Backup Set Copy #1 of backup set 1359739
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:11:44     05/08/2010 01:59:57 NO         TAG20100805T014812
        List of Backup Pieces for backup set 1359739 Copy #1
        BP Key  Pc# Status      Media                   Piece Name
        1359750 1   AVAILABLE   NN0821L3                /ORACLE:SVPRD1B:REDO:153558_726198493_1/
      Backup Set Copy #2 of backup set 1359739
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:11:44     05/08/2010 01:59:57 NO         TAG20100805T014812
        List of Backup Pieces for backup set 1359739 Copy #2
        BP Key  Pc# Status      Media                   Piece Name
        1359751 1   AVAILABLE   NN0833L3                /ORACLE:SVPRD1B:REDO:153558_726198493_2/
    BS Key  Size
    1359740 9.84G
      List of Archived Logs in backup set 1359740
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      2    33580   68243160092 04/08/2010 23:46:14 68253672744 05/08/2010 00:56:10
      2    33581   68253672744 05/08/2010 00:56:10 68260864567 05/08/2010 01:46:16
      Backup Set Copy #1 of backup set 1359740
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:12:20     05/08/2010 02:00:33 NO         TAG20100805T014812
        List of Backup Pieces for backup set 1359740 Copy #1
        BP Key  Pc# Status      Media                   Piece Name
        1359752 1   AVAILABLE   NN0821L3                /ORACLE:SVPRD1B:REDO:153559_726198493_1/
      Backup Set Copy #2 of backup set 1359740
      Device Type Elapsed Time Completion Time     Compressed Tag
      SBT_TAPE    00:12:20     05/08/2010 02:00:33 NO         TAG20100805T014812
        List of Backup Pieces for backup set 1359740 Copy #2
        BP Key  Pc# Status      Media                   Piece Name
        1359753 1   AVAILABLE   NN0833L3                /ORACLE:SVPRD1B:REDO:153559_726198493_2/but when I am trying to restore them I receive an error:
    RMAN> run {
    allocate channel t1 type 'sbt_tape';
    2>  set archivelog destination to '/oracle/archive/svprd1b1/20100817_arch_rest';
    restore (archivelog from time "to_date('04/08/2010 23:00:00','dd/mm/yyyy HH24:mi:ss')" until time "to_date('05/08/2010 01:00:00','dd/mm/yyyy hh24:mi:ss')" );
    release channel t1;
    3> 4> 5> 6>
    allocated channel: t1
    channel t1: sid=1725 instance=SVPRD1B1 devtype=SBT_TAPE
    channel t1: NMO v4.2.0.0
    executing command: SET ARCHIVELOG DESTINATION
    Starting restore at 23/08/2010 13:05:15
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=3 sequence=24686
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153543_726191236_1/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153543_726191236_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153543_726191236_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=1 sequence=33810
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153541_726191236_1/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153541_726191236_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153541_726191236_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=1 sequence=33811
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153544_726192582_1/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153544_726192582_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153544_726192582_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=2 sequence=33578
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153542_726191236_1/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153542_726191236_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153542_726191236_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=2 sequence=33579
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153545_726192843_1/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153545_726192843_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153545_726192843_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=3 sequence=24687
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153560_726198493_1/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153560_726198493_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153560_726198493_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=1 sequence=33812
    channel t1: restoring archive log
    archive log thread=1 sequence=33813
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153558_726198493_1/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153558_726198493_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153558_726198493_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=2 sequence=33580
    channel t1: restoring archive log
    archive log thread=2 sequence=33581
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153559_726198493_1/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153559_726198493_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153559_726198493_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    failover to previous backup
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=3 sequence=24686
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153543_726191236_2/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153543_726191236_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153543_726191236_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=1 sequence=33810
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153541_726191236_2/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153541_726191236_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153541_726191236_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=1 sequence=33811
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153544_726192582_2/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153544_726192582_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153544_726192582_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=2 sequence=33578
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153542_726191236_2/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153542_726191236_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153542_726191236_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=2 sequence=33579
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153545_726192843_2/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153545_726192843_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153545_726192843_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=3 sequence=24687
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153560_726198493_2/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153560_726198493_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153560_726198493_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=1 sequence=33812
    channel t1: restoring archive log
    archive log thread=1 sequence=33813
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153558_726198493_2/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153558_726198493_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153558_726198493_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    channel t1: starting archive log restore to user-specified destination
    archive log destination=/oracle/archive/svprd1b1/20100817_arch_rest
    channel t1: restoring archive log
    archive log thread=2 sequence=33580
    channel t1: restoring archive log
    archive log thread=2 sequence=33581
    channel t1: reading from backup piece /ORACLE:SVPRD1B:REDO:153559_726198493_2/
    ORA-19870: error reading backup piece /ORACLE:SVPRD1B:REDO:153559_726198493_2/
    ORA-19507: failed to retrieve sequential file, handle="/ORACLE:SVPRD1B:REDO:153559_726198493_2/", parms=""
    ORA-27029: skgfrtrv: sbtrestore returned error
    ORA-19511: Error received from media manager layer, error text:
       A backup or restore session is already in progress. (100:17:0)
    failover to previous backup
    released channel: t1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 08/23/2010 13:08:50
    RMAN-06026: some targets not found - aborting restore
    RMAN-06025: no backup of log thread 3 seq 24687 lowscn 68243156430 found to restore
    RMAN-06025: no backup of log thread 3 seq 24686 lowscn 68236434950 found to restore
    RMAN-06025: no backup of log thread 2 seq 33581 lowscn 68253672744 found to restore
    RMAN-06025: no backup of log thread 2 seq 33580 lowscn 68243160092 found to restore
    RMAN-06025: no backup of log thread 2 seq 33579 lowscn 68240747010 found to restore
    RMAN-06025: no backup of log thread 2 seq 33578 lowscn 68236472935 found to restore
    RMAN-06025: no backup of log thread 1 seq 33813 lowscn 68253559461 found to restore
    RMAN-06025: no backup of log thread 1 seq 33812 lowscn 68243156997 found to restore
    RMAN-06025: no backup of log thread 1 seq 33811 lowscn 68240656570 found to restore
    RMAN-06025: no backup of log thread 1 seq 33810 lowscn 68236430016 found to restoreWhat am I doing wrong ?
    Database 10.2.0.4 @HP-UX 11.23 Itanium
    Thanks in advance.

    The error "A backup or restore session is already in progress. (100:17:0)" comes from the MML -- the Tape Management software. It prevents you from running a RESTORE.
    Hemant K Chitale

  • Using archivelog and control file from other Oracle server

    I am still bothered with my backup process.
    I have 2 AIX boxes (same model, say A and B); both have BAAN 5 and Oracle 10g R2 on. Right now my colleague insists to use the export pump (cold backup) from Prod Oracle server (A) to restore the Oracle server on Box B. The Prod server has the archivelog mode turn on. But it will miss any transaction data from import pump till the crash point of Box A. So this is my confusion.
    Can I pass the control files and archivelog files form Box A (prod server) to Box B and use them to restore the Box B as the latest Prod server? How?
    I tried to convince them to use the RMAN backup? But not successful?
    I think the best way is probably to use the Oracle Data guard. However, there is always one concern to my manager and colleague, that such process will cause the data on the restored server (failover, Box B) not recognizable by the BAAN, which define the objects (tables).
    Thanks

    Performing a logical backup is not useful to restore to the point of failure. The only valid and available option is a hot backup/archivelog mode. Your recovery manager backup perform a controlfile and redologfile backup, so those can be restored at the destination. You must take care of the way you perform the backup, and ensure the paths where your backup is being deposited are visible by the second node. A shared storage with same mount points is suitable in this case. A tape robot configured at both nodes is also a suitable solution.
    Recovery manager perfoms a controlfile and spfile restore, too. This rman command perform the action:
    SET DBID <DBID of the database,for which you want to restore the controlfile>;
    RESTORE CONTROLFILE FROM <name_of_backupiece_which_contains_the_controlfile backup>';
    I don't see any problem on the recovery manager side, and technically speaking, on the Oracle side it is perfectly possible to restore your database at a remote location. I don't know what happens on the BAAN side, if you are required to have it configured to be operative on the target node. You could try to clone your database at the node B, configure BAAN and prepare the proceduere in case of failure.
    Configuring a dataguard is also a recomended action. So it is to think about Cold Failed Over clusters. I have recently performed a CFC configuration with BAAN. No problem it works smoothly.
    ~ Madrid.

  • Problem running oracle 9i database in archivelog mode - database freezes

    Greetings,
    I recently needed to change a (test) database to archivelog mode to make online back-ups of this database. This posed no real problem although I seem to be unable to set the database to automatic archiving eventhough I edited the init.ora file (translation of the "archive log list" output between square brackets):
    SQL> archive log list
    Databaselogmodus Archiveermodus [Databaselogmode: Archivemode]
    Automatisch archiveren Gedeactiveerd [Automatic archiving: Deactivated]
    Archiveerbestemming O:\oracle\ora92\RDBMS [Archivedestionation: O:\oracle\ora92\RDBMS]
    Oudste on-line logreeks 12306
    Volgende logreeks voor archivering 12306
    Huidige logreeks 12308
    I added this to my init.ora file:
    # Archvie Log Destinations
    log_archive_start=TRUE
    log_archive_dest_1=%ORACLE_HOME%\database\archive
    log_archive_format="%%ORACLE_SID%%t_%s.arc"
    However, this is not the real problem (maybe it has something to do with it, which is why I mention it aswell), the real problem is that my database freezes when the archive log file is "full". When the archive file reaches ~102.400Kb it just freezes up and I need to restart the database.
    The following error is written to the alert_sid.log file:
    Thu Apr 17 09:19:55 2008
    Thread 1 cannot allocate new log, sequence 12309
    All online logs needed archiving
    Current log# 2 seq# 12308 mem# 0: O:\ORACLE\ORADATA\O\REDO02.LOG
    The problem seems to be that the oracle service can't start a new logfile when the previous one is full. Does anybody know how I could fix this?
    Thanks in advance,
    Bram

    Hello Maran, thanks for your quick response.
    I added the output of archivelog list in the original post, but it's in dutch so here's the (loose) translation of the output:
    SQL> archive log list
    Databaselog mode Archive mode
    Automatic archiving Deactivated
    Archive destionation O:\oracle\ora92\RDBMS
    Oldest on-line logsequence 12307
    Next logsequence for archiving 12307
    Current logsequence 12309
    Maybe something that can help with the troubleshooting:
    The archivelog file is written to O:\oracle\ora92\RDBMS but only AFTER the reboot, I've checked SYSTEM rights to the folder and it has full control.
    Babu, thanks aswell for your quick response.
    The location exists and space is available but the database doesn't seem to load (that part of) the ora.init file because the output of archive log list still refers to %ORACLE_HOME%\rdbms instead of %ORACLE_HOME%\database\archive.
    I've now executed alter system archive log all; and am executing the import where the database usually freezes to see if it still happens. So far I already had this written to the alert_sid.log file after executing the command:
    Completed: alter database open
    Thu Apr 17 10:00:11 2008
    ARCH: Evaluating archive log 1 thread 1 sequence 12307
    ARCH: Beginning to archive log 1 thread 1 sequence 12307
    Creating archive destination LOG_ARCHIVE_DEST_1: 'O:\ORACLE\ORA92\RDBMS\ARC12307.001'
    ARCH: Completed archiving log 1 thread 1 sequence 12307
    ARCH: Evaluating archive log 2 thread 1 sequence 12308
    ARCH: Beginning to archive log 2 thread 1 sequence 12308
    Creating archive destination LOG_ARCHIVE_DEST_1: 'O:\ORACLE\ORA92\RDBMS\ARC12308.001'
    ARCH: Completed archiving log 2 thread 1 sequence 12308
    And new log files were written to the directory (O:\oracle\ora92\RDBMS) and this time I didn't have to reboot for it to happen. Both were 100mb files without the database actually doing all that much though.
    Message was edited by:
    user616266

  • Difference in o/p in CROSSCHECK & RESTORE ARCHIVELOG VALIDATE

    hi,
    i m planning to restore and recovery from a backup(full hot Level 0) taken between '24.05.2012 11:41:00' AND '24.05.2012 12:03:07'; But when i run the crosscheck and restore archivelog validate there seems to be an extra archivelog backup piece reported in restore archivelog validate command.
    Also there was 2 backups taken on same day but different time
    LEVEL 0 ======> between '24.05.2012 11:41:00' AND '24.05.2012 12:03:07'
    LEVEL 1 CUMMULATIVE =======> between '24.05.2012 12:29:46' AND '24.05.2012 12:35:59'
    below the difference in o/p when i run the crosscheck and restore archivelog validate
    CROSSCHECK BACKUP OF ARCHIVELOG ALL command :
    RMAN> ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE sbt;
    allocated channel: ORA_MAINT_SBT_TAPE_1
    channel ORA_MAINT_SBT_TAPE_1: sid=1859 devtype=SBT_TAPE
    channel ORA_MAINT_SBT_TAPE_1: Veritas NetBackup for Oracle - Release 7.0 (2010010419)
    RMAN> sql "alter session set nls_date_format = ''dd.mm.yyyy hh24:mi:ss''";
    sql statement: alter session set nls_date_format = ''dd.mm.yyyy hh24:mi:ss''
    RMAN> CROSSCHECK BACKUP OF ARCHIVELOG ALL DEVICE TYPE sbt completed between '24.05.2012 11:41:00' AND '24.05.2012 12:03:07';
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=PRTUXDB_al_0dnbphae_1_1 RECID=10 STAMP=784123214
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=PRTUXDB_al_0cnbphae_1_1 RECID=11 STAMP=784123214
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=PRTUXDB_al_0fnbphae_1_1 RECID=12 STAMP=784123214
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=PRTUXDB_al_0enbphae_1_1 RECID=13 STAMP=784123214
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=PRTUXDB_al_0bnbphae_1_1 RECID=14 STAMP=784123214
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=PRTUXDB_al_0anbphae_1_1 RECID=15 STAMP=784123214
    Crosschecked 6 objectsRestore archive log validate command :
    [oratux@DMXCK5 ~]$ rman target / nocatalog
    Recovery Manager: Release 11.2.0.3.0 - Production on Fri May 25 08:16:08 2012
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: PRTUXDB (DBID=329945109)
    using target database control file instead of recovery catalog
    RMAN> run {
    allocate channel t1 type 'SBT_TAPE';
    restore archivelog UNTIL TIME "TO_DATE('24.05.2012 12:03:07','dd.mm.yyyy hh24:mi:ss')" validate;
    release channel t1;
    2> 3> 4> 5>
    allocated channel: t1
    channel t1: SID=35 device type=SBT_TAPE
    channel t1: Veritas NetBackup for Oracle - Release 7.0 (2010010419)
    Starting restore at 25-MAY-12
    channel t1: starting validation of archived log backup set
    channel t1: reading from backup piece PRTUXDB_al_0dnbphae_1_1
    channel t1: piece handle=PRTUXDB_al_0dnbphae_1_1 tag=PRIMARY_HOT_DB_BK_LEVEL0
    channel t1: restored backup piece 1
    channel t1: validation complete, elapsed time: 00:01:15
    channel t1: starting validation of archived log backup set
    channel t1: reading from backup piece PRTUXDB_al_0cnbphae_1_1
    channel t1: piece handle=PRTUXDB_al_0cnbphae_1_1 tag=PRIMARY_HOT_DB_BK_LEVEL0
    channel t1: restored backup piece 1
    channel t1: validation complete, elapsed time: 00:01:15
    channel t1: starting validation of archived log backup set
    channel t1: reading from backup piece PRTUXDB_al_0fnbphae_1_1
    channel t1: piece handle=PRTUXDB_al_0fnbphae_1_1 tag=PRIMARY_HOT_DB_BK_LEVEL0
    channel t1: restored backup piece 1
    channel t1: validation complete, elapsed time: 00:01:15
    channel t1: starting validation of archived log backup set
    channel t1: reading from backup piece PRTUXDB_al_0enbphae_1_1
    channel t1: piece handle=PRTUXDB_al_0enbphae_1_1 tag=PRIMARY_HOT_DB_BK_LEVEL0
    channel t1: restored backup piece 1
    channel t1: validation complete, elapsed time: 00:01:15
    channel t1: starting validation of archived log backup set
    channel t1: reading from backup piece PRTUXDB_al_0bnbphae_1_1
    channel t1: piece handle=PRTUXDB_al_0bnbphae_1_1 tag=PRIMARY_HOT_DB_BK_LEVEL0
    channel t1: restored backup piece 1
    channel t1: validation complete, elapsed time: 00:01:25
    channel t1: starting validation of archived log backup set
    channel t1: reading from backup piece PRTUXDB_al_0anbphae_1_1
    channel t1: piece handle=PRTUXDB_al_0anbphae_1_1 tag=PRIMARY_HOT_DB_BK_LEVEL0
    channel t1: restored backup piece 1
    channel t1: validation complete, elapsed time: 00:01:15
    channel t1: starting validation of archived log backup set
    channel t1: reading from backup piece PRTUXDB_al_0qnbpj8c_1_1
    channel t1: piece handle=PRTUXDB_al_0qnbpj8c_1_1 tag=HOT_DB_BK_LEVEL1
    channel t1: restored backup piece 1
    channel t1: validation complete, elapsed time: 00:01:05
    Finished restore at 25-MAY-12
    released channel: t1As you can see one extra archivelog backup piece is reported and that too from HOT_DB_BK_LEVEL1(LEVEL 1 CUMMULATIVE BACKUP) which was between '24.05.2012 12:29:46' AND '24.05.2012 12:35:59'.
    I m afraid if i execute the real restore command it will apply this extra archivelog from LEVEL 1 CUMMULATIVE BACKUP

    Yes that is true,but my question is when i run crosscheck i have all the required archivelogs availiable (6 archivelogs) but when i execute restore archivelog validate why it give (6+1) archivelogs why not only those 6 from LEVEL 0 hot backup
    i have clearly specified UNTIL TIME "TO_DATE('24.05.2012 12:03:07','dd.mm.yyyy hh24:mi:ss')" in restore archivelog validate but still it also give me extra archive log backup piece from LEVEL 1 backup taken way after TO_DATE('24.05.2012 12:03:07','dd.mm.yyyy hh24:mi:ss').

  • Restore database in archivelog mode

    Hello everyone.
    I've been looking on google, how to restore my database on archivelog mode, but i did not succeed.
    I made my backup using this mode, and now i need to know what is the command need to use to restore this.
    Somebody can write the command here please ?
    Thanks for help.
    Regards,
    Dan
    ps: Using Oracle 10g XE on Win XP.

    user8973191 wrote:
    Oh, ok Vijayaraghavan K.
    Thx for u help.
    And about the users ?
    i need to create the "same" user in another machine ?
    For example:
    In this machine i using the "system" user, where i have my tables.
    Another machine, when i restore, my tables will go to the "system" user too? or i can choice? or i need to create one?A true backup is a copy of the data files at the file/block level. The restore is therefore a restore of the data files/blocks. Applying the redo (archive logs) is also done at the block level. None of that knows or cares (or needs to know or care) about logical objects (such as users, tablespaces, tables, rows, etc) within the database. so if you do a proper restore, you are restoring files to a consistent state and thus everything that was defined within those files will be there when restored.

Maybe you are looking for

  • Html5 video player won't work with slider script??

    Hi - I'm new to html5 and Dreamweaver, but I've worked with html in the past, so most things aspects aren't foreign to me. My question is this: I'm working with an existing html5 template and it had a slider graphics bar near the top. It works fine a

  • Error while doing multiple object updation from EP ! object lock error

    HI all, I am doing multiple  object updation using a standard RFC(BAPI_PROJECT_MAINTAIN). The RFC i am calling from Enterprise portal. I am sending data to RFC one by one. But the error i am getting is object is locked by user so data can't be save.

  • How do I deploy dependent jars in a standalone soa server?

    Hi, I have deployed a webservice on a standalone SOA server. When I try to execute it I see the following message: faultstring>JBO-25002: Definition oracle.apps.cdm.tcaModel.parties.core.model.publicEntity.PartyPEO of type Entity Definition not found

  • Consolidate tracks into one album

    I have the latest version of itunes and I ripped one of my cd's last night.  It's a 2 disc album and it ripped disc 2 fine as one album, but disc one is all separate tracks. I have selected all the tracks and clicked "get into", changed all the info

  • Need help in date conversion(it's Urgent)

    I am reading data from the text file... and inserting that data into the oracle table(using bpel process) I have following problem with the date field. In the XSD file if i specify the date format as nxsd:dateFormat="ddMMyyyy" and when i pass null va