This discussion is archived
1 2 3 Previous Next 30 Replies Latest reply: Nov 24, 2012 5:50 PM by 975524 RSS

Success on RESTORE but failed on RECOVER-- need help

975524 Newbie
Currently Being Moderated
I was able to execute "restore database" command and it went successfully.
But when I execute "recover database" it stops with error

RMAN-08187: WARNING: media recovery until SCN 1155620136 complete
archived log file name=/oracle/oradsk3/archivelogs/1_94646_700099109.dbf thread=1 sequence=94647
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/19/2012 05:55:32
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/oracle/oradsk3/archivelogs/1_94646_700099109.dbf'
ORA-00283: recovery session canceled due to errors
ORA-01112: media recovery not started
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 94647 and starting SCN of 1155620136


Although i have this error I can successfully startup my database without a problem. But on our ERP application, it encounters errors such as below
Error : SQLState QP99P: database error 376 (error 1376) (rcdset.readkastset() in object ....
Fatal error : Error 1376 (database error 376) on select

What should I be rectifying to fix this?
By the way, im a newbie to oracle database. Hope somebody could help me on this.

Below are the commands i did:
commands:
     1) rman --> enter
     2) connect target / --> enter
     3) delete expired backup; --> enter           # this will delete all the expired backup set on the controlfile
     4) catalog start with '/oracle/RMAN'; --> enter # this will catalog all files in directory
     5) restore database preview; --> enter          # this will test restore the backup sets on the database, no actual restoration, test only.
     6) restore database validate;
     7) restore archivelog all validate;
8) shutdown;
9) startup nomount;
10) mount database;
11) list incarnation;
12) reset database to incarnation 1; - chnage to the old incarnation.
13) restore database;
14) recover database;
15) Alter database open resetlogs;
  • 1. Re: Success on RESTORE but failed on RECOVER-- need help
    mseberg Guru
    Currently Being Moderated
    Hello;

    I think I would try :

    set until sequence = <archivelog seq#>;
    restore database;
    recover database;

    Instead of until SCN 1155620136

    Cannot remember off the top of my head, but RMAN converts one to the other behind the scene.

    In any event this is the root of your issue :
    unknown archived log for thread 1 with sequence 94647
    Best Regards

    mseberg
  • 2. Re: Success on RESTORE but failed on RECOVER-- need help
    975524 Newbie
    Currently Being Moderated
    Hi mseberg,
    im glad somebody replied immediately.

    I run what you stated and got the message below...

    RMAN> run {
    2> set until sequence = 94646;
    3> restore database;
    4> recover database;
    5> }

    executing command: SET until clause
    using target database control file instead of recovery catalog

    Starting restore at 22-NOV-12
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=2170 device type=DISK

    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 11/22/2012 08:53:09
    RMAN-06085: must use SET NEWNAME command to restore datafile /oracle/Ora11g/dbs/ MISSING00126

    RMAN>


    Why did it look at "/oracle/Ora11g/dbs " directory? what datafile should i a rename? as i look at the directory there are no datafiles in there.
    $ pwd
    /oracle/Ora11g/dbs
    $ ls -l
    total 72
    -rw-r--r-- 1 oracle dba 0 Sep 08 2011 core
    -rw-rw-rw- 1 oracle dba 1544 Nov 22 09:01 hc_ERPLN.dat
    -rw-r--r-- 1 oracle dba 2774 Sep 11 2007 init.ora
    -rw-r--r-- 1 oracle dba 12920 May 03 2001 initdw.ora
    -rw-r--r-- 1 oracle dba 24 Oct 14 2009 lkERPLN
    -rw-r----- 1 oracle dba 1536 Aug 22 2011 orapwERPLN
    -rw-r--r-- 1 oracle dba 3584 Nov 21 22:44 spfileERPLN.ora
    $

    please help

    Edited by: 972521 on Nov 21, 2012 5:02 PM
  • 3. Re: Success on RESTORE but failed on RECOVER-- need help
    975524 Newbie
    Currently Being Moderated
    I also run this query and got this..how do i solve this? Its kinda a related to the problem?

    SQL> select file#, name, status from v$datafile where status = 'RECOVER';

    FILE#
    ----------
    NAME
    --------------------------------------------------------------------------------
    STATUS
    -------
    126
    /oracle/Ora11g/dbs/MISSING00126
    RECOVER

    127
    /oracle/Ora11g/dbs/MISSING00127
    RECOVER

    FILE#
    ----------
    NAME
    --------------------------------------------------------------------------------
    STATUS
    -------

    128
    /oracle/Ora11g/dbs/MISSING00128
    RECOVER

    129
    /oracle/Ora11g/dbs/MISSING00129

    FILE#
    ----------
    NAME
    --------------------------------------------------------------------------------
    STATUS
    -------
    RECOVER


    SQL>
  • 4. Re: Success on RESTORE but failed on RECOVER-- need help
    975524 Newbie
    Currently Being Moderated
    I tried this to resolve the ' set newname ' message. but no luck. (see below)

    Hello Experts!! need you help!!!

    RMAN> run {
    2> set newname for datafile '/oracle/Ora11g/dbs/MISSING00126' to '/oracle/oradsk3/ERPLN/system01.dbf';
    3> }

    executing command: SET NEWNAME

    RMAN> run {
    2> set until sequence = 94646;
    3> restore database;
    4> recover database;
    5> }

    executing command: SET until clause

    Starting restore at 22-NOV-12
    using channel ORA_DISK_1

    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 11/22/2012 14:08:16
    RMAN-06085: must use SET NEWNAME command to restore datafile /oracle/Ora11g/dbs/MISSING00126

    RMAN>
  • 5. Re: Success on RESTORE but failed on RECOVER-- need help
    975524 Newbie
    Currently Being Moderated
    hello anybody out there who can help me?
  • 6. Re: Success on RESTORE but failed on RECOVER-- need help
    Hemant K Chitale Oracle ACE
    Currently Being Moderated
    You have 4 datafiles (FILE_IDs 126 to 129) which were either not restored or, more likely, were not in the backup that was used for the restore.


    Hemant K Chitale
  • 7. Re: Success on RESTORE but failed on RECOVER-- need help
    Hemant K Chitale Oracle ACE
    Currently Being Moderated
    set newname for datafile '/oracle/Ora11g/dbs/MISSING00126' to '/oracle/oradsk3/ERPLN/system01.dbf';
    Are you sure that FILE_ID 126 was system01.dbf ?

    set until sequence = 94646;
    should be UNTIL SEQUENCE = 94647 (i.e. the last archivelog to be applied plus 1)
    recover database;
    The set until clause should be in the same curly brackets as the RESTORE and RECOVER


    Hemant K Chitale
  • 8. Re: Success on RESTORE but failed on RECOVER-- need help
    975524 Newbie
    Currently Being Moderated
    set newname for datafile '/oracle/Ora11g/dbs/MISSING00126' to '/oracle/oradsk3/ERPLN/system01.dbf'; -- no and i dont know. and how do i know? i thought i could just name the file i want. Anyway,
    I think i screw things up more because of what i did now. im sorry but im a newbie.

    i did a RMAN > list backup; then get the last sequence it displayed on the list.
    then i did this command
    RMAN > restore database until sequence 94645; then it runned for awhile telling it has restoring datafiles but suddenly it stops with this error. see below (not the complete output but it is up to the last message)

    channel ORA_DISK_1: restore complete, elapsed time: 00:13:55
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00026 to /oracle/oradsk2/ERPLN/appsidx100_06.dbf
    channel ORA_DISK_1: restoring datafile 00051 to /oracle/oradsk3/ERPLN/bigtablesdat17.dbf
    channel ORA_DISK_1: restoring datafile 00076 to /oracle/oradsk4/ERPLN/bigtablesidx02.dbf
    channel ORA_DISK_1: restoring datafile 00101 to /oracle/oradsk4/ERPLN/appsidx101_11.dbf
    channel ORA_DISK_1: restoring datafile 00126 to /oracle/Ora11g/dbs/MISSING00126
    channel ORA_DISK_1: reading from backup piece /oracle/RMAN/ERPLN_full_datafiles_797914296_20670_1
    channel ORA_DISK_1: ORA-19870: error while restoring backup piece /oracle/RMAN/ERPLN_full_datafiles_797914296_20670_1
    ORA-19502: write error on file "/oracle/Ora11g/dbs/MISSING00126", block number 397185 (block size=8192)
    ORA-27063: number of bytes read/written is incorrect
    IBM AIX RISC System/6000 Error: 28: No space left on device
    Additional information: -1
    Additional information: 131072

    RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
    RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
    ORACLE error from target database:
    ORA-09817: Write to audit file failed.
    IBM AIX RISC System/6000 Error: 28: No space left on device

    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00027 to /oracle/oradsk3/ERPLN/appsidx100_07.dbf
    channel ORA_DISK_1: restoring datafile 00052 to /oracle/oradsk4/ERPLN/bigtablesdat18.dbf
    channel ORA_DISK_1: restoring datafile 00077 to /oracle/oradsk1/ERPLN/bigtablesidx03.dbf
    channel ORA_DISK_1: restoring datafile 00102 to /oracle/oradsk1/ERPLN/appsidx100_12.dbf
    channel ORA_DISK_1: restoring datafile 00127 to /oracle/Ora11g/dbs/MISSING00127
    channel ORA_DISK_1: reading from backup piece /oracle/RMAN/ERPLN_full_datafiles_797914602_20671_1
    channel ORA_DISK_1: ORA-19870: error while restoring backup piece /oracle/RMAN/ERPLN_full_datafiles_797914602_20671_1
    ORA-19502: write error on file "/oracle/Ora11g/dbs/MISSING00127", block number 397169 (block size=8192)
    ORA-27063: number of bytes read/written is incorrect
    IBM AIX RISC System/6000 Error: 28: No space left on device
    Additional information: -1
    Additional information: 131072

    c. dbms_backup_restore.restoreCancel() failed
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: fatal error during execution of command
    RMAN-10006: error running SQL statement: select sofar, context, start_time from v$session_longops where (start_time >vl(:1, sysdate-100) or start_time = nvl(:2, sysdate+100)) and sid = :3 and serial# = :4 and opname like 'RMAN:%' order by start_time desc, context desc
    RMAN-10002: ORACLE error: ORA-09817: Write to audit file failed.
    IBM AIX RISC System/6000 Error: 28: No space left on device
    ORA-19502: write error on file "/oracle/Ora11g/dbs/MISSING00127", block number 397153 (block size=8192)
    ORA-27063: number of bytes read/written is incorrect
    IBM AIX RISC System/6000 Error: 28: No space left on device
    Additional information: -1
    Additional information: 131072
    $

    What should i do now? my problem was only the "recovery" part but now even on the "restore" part its having a problem.
    Although this is just a on a test server but its important to get it back online. I dont care if i dont restore up to the last point in time. i just want it to run the database again with no problem.
    i dont want to do anytihing right now on the database, fearing i could screw it up more and complicate things.
    i will just wait for any body who can post a suggestion and help me all the way until i get this up and running.

    Hoping for somebody to guide me step by step.

    Thanks in advance whoever you will be...
  • 9. Re: Success on RESTORE but failed on RECOVER-- need help
    Hemant K Chitale Oracle ACE
    Currently Being Moderated
    The error :
    IBM AIX RISC System/6000 Error: 28: No space left on device
    is on the filesystem /oracle/Ora11g/dbs

    Your bigger problem is the 4 MISSING files. You need to identify whether they did get included in the backup, why they are MISSING.

    Hemant K Chitale
  • 10. Re: Success on RESTORE but failed on RECOVER-- need help
    975524 Newbie
    Currently Being Moderated
    I guess the 4 files missing where not restored.
    I found out from the backup script these lines and thought maybe these are the missing files.

    ##### BACKUP OF ERPLN DATABASE IS FINISHED OTHER SCRIPTS WILL NOW PROCEED. #####

    ############ BACKUP OF CONTROLFILE WILL BEGIN ############
    rm /oracle/RMAN/files/spfileERPLN.ora
    rm /oracle/RMAN/files/orapwERPLN
    rm /oracle/RMAN/files/hc_ERPLN.dat
    sqlplus /nolog << EOF
    connect / as sysdba;
    alter database backup controlfile to '/oracle/RMAN/files/erpln_bkp_$(date +%d%m%Y-%H%M%S)_ctrl_file.ctl';
    quit;
    EOF
    ############ BACKUP OF CONTROLFILE IS FINISHED ############


    ######### COPY OF IMPORTANT FILES TO BACKUP DIRECTORY WILL NOW BEGIN ##########
    cp $ORACLE_HOME/dbs/spfileERPLN.ora /oracle/RMAN/files/. >> $BKP_LOGFILE
    cp $ORACLE_HOME/dbs/orapwERPLN /oracle/RMAN/files/. >> $BKP_LOGFILE
    cp $ORACLE_HOME/dbs/hc_ERPLN.dat /oracle/RMAN/files/. >> $BKP_LOGFILE
    ############ COPY OF IMPORTANT FILES TO BACKUP DIRECTORY IS FINISHED ###########

    So i was able to extract it from tape.
    Then i catalog them again with the new files "/oracle/RMAN"
    Then it prompts if i want to include files in "/oracle/RMAN/files" to catalog then i answered "YES"
    But i got the message that the "erpln_bkp_xxxxxxxx_ctrl_file.ctl" was cataloged
    But the 3 files has bad headers error.
  • 11. Re: Success on RESTORE but failed on RECOVER-- need help
    975524 Newbie
    Currently Being Moderated
    I was able to restore successfully by doing the following:

    run {
    set newname for datafile 126 to '/oracle/oradsk2/ERPLN/appsidx100_20.dbf';
    set newname for datafile 127 to '/oracle/oradsk2/ERPLN/bigtablesdat55.dbf';
    set newname for datafile 128 to '/oracle/oradsk4/ERPLN/appdat100_16.dbf';
    set newname for datafile 129 to '/oracle/oradsk2/ERPLN/bigtablesidex18.dbf';
    restore database;
    switch datafile all;
    recover database;
    }

    But on recover i got this error below...whats next?

    Starting recover at 24-NOV-12
    using channel ORA_DISK_1

    starting media recovery
    media recovery failed
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 11/24/2012 21:53:33
    ORA-00283: recovery session canceled due to errors
    RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
    start until cancel
    ORA-00283: recovery session canceled due to errors
    ORA-01122: database file 1 failed verification check
    ORA-01110: data file 1: '/oracle/oradsk2/ERPLN/system01.dbf'
    ORA-01207: file is more recent than control file - old control file
  • 12. Re: Success on RESTORE but failed on RECOVER-- need help
    975524 Newbie
    Currently Being Moderated
    I also tried this and came with another message below;

    RMAN> shutdown immediate;

    database dismounted
    Oracle instance shut down

    RMAN> startup

    connected to target database (not started)
    Oracle instance started
    database mounted
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of startup command at 11/24/2012 22:36:06
    ORA-01190: control file or data file 1 is from before the last RESETLOGS
    ORA-01110: data file 1: '/oracle/oradsk2/ERPLN/system01.dbf'

    RMAN>
  • 13. Re: Success on RESTORE but failed on RECOVER-- need help
    975524 Newbie
    Currently Being Moderated
    i tried this and got this message below. Any experts that can help me ?

    RMAN> startup

    database is already started
    database mounted
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of startup command at 11/24/2012 23:09:10
    ORA-01190: control file or data file 1 is from before the last RESETLOGS
    ORA-01110: data file 1: '/oracle/oradsk2/ERPLN/system01.dbf'

    RMAN>
  • 14. Re: Success on RESTORE but failed on RECOVER-- need help
    975524 Newbie
    Currently Being Moderated
    Based on the forums i need to re-create the controlfile
    and im following these steps:

    sql> alter database backup controlfile to trace as ‘/tmp/create_controlf.sql’; -- create trace file of controlfile
    sql> startup nomount -- start with nomount

    (i stopped here)

    next is to recreate the controlfile using the trace file. This is the part where im afraid of.

    Because of the tracefile is soo long i dont know where to stop copying on what command from the file. Should i be copying them all throughout? Need Experts to help me... please

    pasting the content of the file. see below:



    ***********************************
    -- The following are current System-scope REDO Log Archival related
    -- parameters and can be included in the database initialization file.
    --
    -- LOG_ARCHIVE_DEST=''
    -- LOG_ARCHIVE_DUPLEX_DEST=''
    --
    -- LOG_ARCHIVE_FORMAT=%t_%s_%r.dbf
    --
    -- DB_UNIQUE_NAME="ERPLN"
    --
    -- LOG_ARCHIVE_CONFIG='SEND, RECEIVE, NODG_CONFIG'
    -- LOG_ARCHIVE_MAX_PROCESSES=4
    -- STANDBY_FILE_MANAGEMENT=MANUAL
    -- STANDBY_ARCHIVE_DEST=?/dbs/arch
    -- FAL_CLIENT=''
    -- FAL_SERVER=''
    --
    -- LOG_ARCHIVE_DEST_1='LOCATION=/oracle/oradsk3/archivelogs'
    -- LOG_ARCHIVE_DEST_1='MANDATORY NOREOPEN NODELAY'
    -- LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM EXPEDITE NOVERIFY SYNC'
    -- LOG_ARCHIVE_DEST_1='NOREGISTER NOALTERNATE NODEPENDENCY'
    -- LOG_ARCHIVE_DEST_1='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED NODB_UNIQUE_NAME'
    -- LOG_ARCHIVE_DEST_1='VALID_FOR=(PRIMARY_ROLE,ONLINE_LOGFILES)'
    -- LOG_ARCHIVE_DEST_STATE_1=ENABLE

    --
    -- Below are two sets of SQL statements, each of which creates a new
    -- control file and uses it to open the database. The first set opens
    -- the database with the NORESETLOGS option and should be used only if
    -- the current versions of all online logs are available. The second
    -- set opens the database with the RESETLOGS option and should be used
    -- if online logs are unavailable.
    -- The appropriate set of statements can be copied from the trace into
    -- a script file, edited as necessary, and executed when there is a
    -- need to re-create the control file.
    --
    -- Set #1. NORESETLOGS case
    --
    -- The following commands will create a new control file and use it
    -- to open the database.
    -- Data used by Recovery Manager will be lost.
    -- Additional logs may be required for media recovery of offline
    -- Use this only if the current versions of all online logs are
    -- available.

    -- After mounting the created controlfile, the following SQL
    -- statement will place the database in the appropriate
    -- protection mode:
    -- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE

    STARTUP NOMOUNT
    CREATE CONTROLFILE REUSE DATABASE "ERPLN" NORESETLOGS NOARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 200
    MAXINSTANCES 8
    MAXLOGHISTORY 17584
    LOGFILE
    GROUP 1 '/oracle/oradsk1/ERPLN/redo01.log' SIZE 50M,
    GROUP 2 '/oracle/oradsk2/ERPLN/redo02.log' SIZE 50M,
    GROUP 3 '/oracle/oradsk3/ERPLN/redo03.log' SIZE 50M
    -- STANDBY LOGFILE

    DATAFILE
    '/oracle/oradsk2/ERPLN/system01.dbf',
    '/oracle/oradsk1/ERPLN/sysaux01.dbf',
    '/oracle/oradsk4/ERPLN/undotbs01.dbf',
    '/oracle/oradsk1/ERPLN/users01.dbf',
    '/oracle/oradsk1/ERPLN/toolsdat01.dbf',
    '/oracle/oradsk2/ERPLN/toolsidx01.dbf',
    '/oracle/oradsk3/ERPLN/appsdat100_01.dbf',
    '/oracle/oradsk4/ERPLN/appsdat100_02.dbf',
    '/oracle/oradsk1/ERPLN/appsdat100_03.dbf',
    '/oracle/oradsk2/ERPLN/appsdat100_04.dbf',
    '/oracle/oradsk3/ERPLN/appsdat100_05.dbf',
    '/oracle/oradsk4/ERPLN/appsdat100_06.dbf',
    '/oracle/oradsk1/ERPLN/appsdat100_07.dbf',
    '/oracle/oradsk2/ERPLN/appsdat100_08.dbf',
    '/oracle/oradsk3/ERPLN/appsdat100_08.dbf',
    '/oracle/oradsk4/ERPLN/appsdat100_10.dbf',
    '/oracle/oradsk1/ERPLN/appsdat101_01.dbf',
    '/oracle/oradsk2/ERPLN/appsdat101_02.dbf',
    '/oracle/oradsk3/ERPLN/appsdat101_03.dbf',
    '/oracle/oradsk4/ERPLN/appsdat101_04.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_01.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_02.dbf',
    '/oracle/oradsk3/ERPLN/appsidx100_03.dbf',
    '/oracle/oradsk4/ERPLN/appsidx100_04.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_05.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_06.dbf',
    '/oracle/oradsk3/ERPLN/appsidx100_07.dbf',
    '/oracle/oradsk4/ERPLN/appsidx100_08.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_09.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_10.dbf',
    '/oracle/oradsk3/ERPLN/appsidx100_01.dbf',
    '/oracle/oradsk4/ERPLN/appsidx100_02.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_03.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_04.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat01.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat02.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat03.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat04.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat05.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat06.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat07.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat08.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat09.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat10.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat11.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat12.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat13.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat14.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat15.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat16.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat17.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat18.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat19.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat20.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat21.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat22.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat23.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat24.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat25.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat26.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat27.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat28.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat29.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat30.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat31.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat32.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat33.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat34.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat35.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat36.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat37.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat38.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat39.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat40.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesidx01.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesidx02.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesidx03.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesidx04.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesidx05.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesidx06.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesidx07.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesidx08.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesidx09.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesidx10.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesidx11.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesidx12.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat41.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat42.dbf',
    '/oracle/oradsk3/ERPLN/appsdat101_05.dbf',
    '/oracle/oradsk4/ERPLN/appsdat101_06.dbf',
    '/oracle/oradsk1/ERPLN/appsdat101_07.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat43.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat44.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat45.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat46.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat47.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat48.dbf',
    '/oracle/oradsk1/ERPLN/appsdat100_11.dbf',
    '/oracle/oradsk2/ERPLN/appsdat100_11.dbf',
    '/oracle/oradsk3/ERPLN/appsdat100_12.dbf',
    '/oracle/oradsk4/ERPLN/appsidx101_11.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_12.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_13.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesidex13.dbf',
    '/oracle/oradsk2/ERPLN/appsdat100_13.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat49.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_14.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_15.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat50.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_06.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_16.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_17.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat51.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesidex14.dbf',
    '/oracle/oradsk4/ERPLN/appsdat100_14.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat52.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_18.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_19.dbf',
    '/oracle/oradsk3/ERPLN/appsdat100_15.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat53.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat54.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesidx15.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesidx16.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesidx17.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_07.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_20.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat55.dbf',
    '/oracle/oradsk4/ERPLN/appdat100_16.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesidex18.dbf'
    CHARACTER SET WE8ISO8859P1
    ;

    -- Take files offline to match current control file.
    ALTER DATABASE DATAFILE '/oracle/oradsk2/ERPLN/appsidx100_20.dbf' OFFLINE DROP;
    ALTER DATABASE DATAFILE '/oracle/oradsk2/ERPLN/bigtablesdat55.dbf' OFFLINE DROP;
    ALTER DATABASE DATAFILE '/oracle/oradsk4/ERPLN/appdat100_16.dbf' OFFLINE DROP;
    ALTER DATABASE DATAFILE '/oracle/oradsk2/ERPLN/bigtablesidex18.dbf' OFFLINE DROP;

    -- Configure RMAN configuration record 1
    VARIABLE RECNO NUMBER;
    EXECUTE :RECNO := SYS.DBMS_BACKUP_RESTORE.SETCONFIG('DEVICE TYPE','DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1');
    -- Configure RMAN configuration record 2
    VARIABLE RECNO NUMBER;
    EXECUTE :RECNO := SYS.DBMS_BACKUP_RESTORE.SETCONFIG('RETENTION POLICY','TO REDUNDANCY 2');
    -- Commands to re-create incarnation table
    -- Below log names MUST be changed to existing filenames on
    -- disk. Any one log file from each branch can be used to
    -- re-create incarnation records.
    -- ALTER DATABASE REGISTER LOGFILE '/oracle/oradsk3/archivelogs/1_1_700099109.dbf';
    -- ALTER DATABASE REGISTER LOGFILE '/oracle/oradsk3/archivelogs/1_1_784819699.dbf';
    -- ALTER DATABASE REGISTER LOGFILE '/oracle/oradsk3/archivelogs/1_1_799740911.dbf';
    -- ALTER DATABASE REGISTER LOGFILE '/oracle/oradsk3/archivelogs/1_1_800034519.dbf';
    -- Recovery is required if any of the datafiles are restored backups,
    -- or if the last shutdown was not normal or immediate.
    RECOVER DATABASE

    -- Database can now be opened normally.
    ALTER DATABASE OPEN;

    -- Commands to add tempfiles to temporary tablespaces.
    -- Online tempfiles have complete space information.
    -- Other tempfiles may require adjustment.
    ALTER TABLESPACE TEMP ADD TEMPFILE '/oracle/oradsk3/ERPLN/temp01.dbf' REUSE;
    -- End of tempfile additions.
    --
    -- Set #2. RESETLOGS case
    --
    -- The following commands will create a new control file and use it
    -- to open the database.
    -- Data used by Recovery Manager will be lost.
    -- The contents of online logs will be lost and all backups will
    -- be invalidated. Use this only if online logs are damaged.

    -- After mounting the created controlfile, the following SQL
    -- statement will place the database in the appropriate
    -- protection mode:
    -- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE

    STARTUP NOMOUNT
    CREATE CONTROLFILE REUSE DATABASE "ERPLN" RESETLOGS NOARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 200
    MAXINSTANCES 8
    MAXLOGHISTORY 17584
    LOGFILE
    GROUP 1 '/oracle/oradsk1/ERPLN/redo01.log' SIZE 50M,
    GROUP 2 '/oracle/oradsk2/ERPLN/redo02.log' SIZE 50M,
    GROUP 3 '/oracle/oradsk3/ERPLN/redo03.log' SIZE 50M
    -- STANDBY LOGFILE

    DATAFILE
    '/oracle/oradsk2/ERPLN/system01.dbf',
    '/oracle/oradsk1/ERPLN/sysaux01.dbf',
    '/oracle/oradsk4/ERPLN/undotbs01.dbf',
    '/oracle/oradsk1/ERPLN/users01.dbf',
    '/oracle/oradsk1/ERPLN/toolsdat01.dbf',
    '/oracle/oradsk2/ERPLN/toolsidx01.dbf',
    '/oracle/oradsk3/ERPLN/appsdat100_01.dbf',
    '/oracle/oradsk4/ERPLN/appsdat100_02.dbf',
    '/oracle/oradsk1/ERPLN/appsdat100_03.dbf',
    '/oracle/oradsk2/ERPLN/appsdat100_04.dbf',
    '/oracle/oradsk3/ERPLN/appsdat100_05.dbf',
    '/oracle/oradsk4/ERPLN/appsdat100_06.dbf',
    '/oracle/oradsk1/ERPLN/appsdat100_07.dbf',
    '/oracle/oradsk2/ERPLN/appsdat100_08.dbf',
    '/oracle/oradsk3/ERPLN/appsdat100_08.dbf',
    '/oracle/oradsk4/ERPLN/appsdat100_10.dbf',
    '/oracle/oradsk1/ERPLN/appsdat101_01.dbf',
    '/oracle/oradsk2/ERPLN/appsdat101_02.dbf',
    '/oracle/oradsk3/ERPLN/appsdat101_03.dbf',
    '/oracle/oradsk4/ERPLN/appsdat101_04.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_01.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_02.dbf',
    '/oracle/oradsk3/ERPLN/appsidx100_03.dbf',
    '/oracle/oradsk4/ERPLN/appsidx100_04.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_05.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_06.dbf',
    '/oracle/oradsk3/ERPLN/appsidx100_07.dbf',
    '/oracle/oradsk4/ERPLN/appsidx100_08.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_09.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_10.dbf',
    '/oracle/oradsk3/ERPLN/appsidx100_01.dbf',
    '/oracle/oradsk4/ERPLN/appsidx100_02.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_03.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_04.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat01.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat02.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat03.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat04.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat05.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat06.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat07.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat08.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat09.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat10.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat11.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat12.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat13.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat14.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat15.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat16.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat17.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat18.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat19.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat20.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat21.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat22.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat23.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat24.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat25.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat26.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat27.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat28.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat29.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat30.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat31.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat32.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat33.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat34.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat35.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat36.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat37.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat38.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat39.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat40.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesidx01.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesidx02.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesidx03.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesidx04.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesidx05.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesidx06.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesidx07.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesidx08.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesidx09.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesidx10.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesidx11.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesidx12.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat41.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat42.dbf',
    '/oracle/oradsk3/ERPLN/appsdat101_05.dbf',
    '/oracle/oradsk4/ERPLN/appsdat101_06.dbf',
    '/oracle/oradsk1/ERPLN/appsdat101_07.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat43.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat44.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat45.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat46.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat47.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat48.dbf',
    '/oracle/oradsk1/ERPLN/appsdat100_11.dbf',
    '/oracle/oradsk2/ERPLN/appsdat100_11.dbf',
    '/oracle/oradsk3/ERPLN/appsdat100_12.dbf',
    '/oracle/oradsk4/ERPLN/appsidx101_11.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_12.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_13.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesidex13.dbf',
    '/oracle/oradsk2/ERPLN/appsdat100_13.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat49.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_14.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_15.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat50.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_06.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_16.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_17.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat51.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesidex14.dbf',
    '/oracle/oradsk4/ERPLN/appsdat100_14.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesdat52.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_18.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_19.dbf',
    '/oracle/oradsk3/ERPLN/appsdat100_15.dbf',
    '/oracle/oradsk4/ERPLN/bigtablesdat53.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesdat54.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesidx15.dbf',
    '/oracle/oradsk3/ERPLN/bigtablesidx16.dbf',
    '/oracle/oradsk1/ERPLN/bigtablesidx17.dbf',
    '/oracle/oradsk1/ERPLN/appsidx100_07.dbf',
    '/oracle/oradsk2/ERPLN/appsidx100_20.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesdat55.dbf',
    '/oracle/oradsk4/ERPLN/appdat100_16.dbf',
    '/oracle/oradsk2/ERPLN/bigtablesidex18.dbf'
    CHARACTER SET WE8ISO8859P1
    ;

    -- Configure RMAN configuration record 1
    VARIABLE RECNO NUMBER;
    EXECUTE :RECNO := SYS.DBMS_BACKUP_RESTORE.SETCONFIG('DEVICE TYPE','DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1');
    -- Configure RMAN configuration record 2
    VARIABLE RECNO NUMBER;
    EXECUTE :RECNO := SYS.DBMS_BACKUP_RESTORE.SETCONFIG('RETENTION POLICY','TO REDUNDANCY 2');
    -- Commands to re-create incarnation table
    -- Below log names MUST be changed to existing filenames on
    -- disk. Any one log file from each branch can be used to
    -- re-create incarnation records.
    -- ALTER DATABASE REGISTER LOGFILE '/oracle/oradsk3/archivelogs/1_1_700099109.dbf';
    -- ALTER DATABASE REGISTER LOGFILE '/oracle/oradsk3/archivelogs/1_1_784819699.dbf';
    -- ALTER DATABASE REGISTER LOGFILE '/oracle/oradsk3/archivelogs/1_1_799740911.dbf';
    -- ALTER DATABASE REGISTER LOGFILE '/oracle/oradsk3/archivelogs/1_1_800034519.dbf';
    -- Recovery is required if any of the datafiles are restored backups,
    -- or if the last shutdown was not normal or immediate.
    RECOVER DATABASE USING BACKUP CONTROLFILE

    -- Database can now be opened zeroing the online logs.
    ALTER DATABASE OPEN RESETLOGS;

    -- Commands to add tempfiles to temporary tablespaces.
    -- Online tempfiles have complete space information.
    -- Other tempfiles may require adjustment.
    ALTER TABLESPACE TEMP ADD TEMPFILE '/oracle/oradsk3/ERPLN/temp01.dbf' REUSE;
    -- End of tempfile additions.
    --
    ************************************************
1 2 3 Previous Next

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points