I have to recover database.

Need quick help. I am refreshing a dev database from prod's backup. Using rman commands which is using control file. I have restored control file from tape backup. I have read I now I am supposed to do a alter database mount. When I did that I am getting the following errors :
SQL> alter database mount;
alter database mount
ERROR at line 1:
ORA-03113: end-of-file on communication channel
SQL> select * from v$instance;
ERROR:
ORA-03114: not connected to ORACLE
Can any one help what needs to be done.
Thanks
/Sh

ORA-03113 end-of-file on communication channel
Cause: An unexpected end-of-file was processed on the communication
channel. The problem could not be handled by the Net8 two-task software. This
message could occur if the shadow two-task process associated with a Net8
connect has terminated abnormally, or if there is a physical failure of the
interprocess communication vehicle, that is, the network or server machine
went down.
In addition, this message could occur when any of the following
statements/commands have been issued:
n ALTER SYSTEM KILL SESSION ... IMMEDIATE
n ALTER SYSTEM DISCONNECT SESSION ... IMMEDIATE
n SHUTDOWN ABORT/IMMEDIATE/TRANSACTIONAL
Action: If this message occurs during a connection attempt, check the setup
files for the appropriate Net8 driver and confirm Net8 software is correctly
installed on the server. If the message occurs after a connection is well
established, and the error is not due to a physical failure, check if a trace file
was generated on the server at failure time. Existence of a trace file may suggest
an Oracle internal error that requires the assistance of Oracle Support Services.
ORA-03114 not connected to ORACLE
Cause: A call to Oracle was attempted when no connection was established.
Usually this happens because a user-written program has not logged on. It may
happen if communication trouble causes a disconnection. In addition, this
message could occur when ALTER SYSTEM KILL SESSION or ALTER SYSTEM
DISCONNECT SESSION were issued with the IMMEDIATE qualifier because,
in those cases, the client’s connection to the database is terminated without
waiting for the client to issue a request.
Action: Try again. If the message recurs and the program is user written, check
the program.

Similar Messages

  • Recover Database vrs Recover Tablespace & Datafile

    Traditionally when I have been recovering a database either to point of failure or point in time I have issued
    RECOVER DATABASE AUTO;
    (or I have specified the point in time I wish to recover to ).
    I see now in 11gR2 there is also a RECOVER TABLESPACE and a RECOVER DATAFILE command
    Why would you use those instead of the RECOVER DATABASE ? You would have to be pretty sure it is only that tablespace or data file you wanted to apply archive logs to, otherwise would your recovery not risk putting the contents of that tablespace or datafile out of logical sync with the data in other tablespaces ( eg potentially viloating referential integrity etc ) ?
    I am presuming these commands also only apply the contents of archive logs that effect the specified tablespace or datafile ?
    thanks,
    Jim

    If I issue a RECOVER TABLESPACE or RECOVER DATAFILE for a Tablespace or Datafile that is current and does not need recovery, Oracle does nothing to the Tablespace / Datafile. It won't be out of logical sync with the rest of the database.
    >>>
    Can you recover the data file or the tablespace to a point in time before the current time ? If that is the case then surely it is possible that the recovered tablespace could have a table in it that has referential integrity to another table in a different ( unrecovered ) tablespace and that the referential integrity could then be compromised ?
    Jim

  • Recover database but don't have archive log file

    Hi
    I use old backup set in tape and restore all datafile completed but I cannot recover that show below errror in RMAN
    RMAN> recover database;
    Starting recover at 08-SEP-09
    using channel ORA_DISK_1
    starting media recovery
    unable to find archive log
    archive log thread=1 sequence=29166
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 09/08/2009 21:49:36
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 29166 lowscn 1648727512
    But in backup set and include archive log already that don't have seq 29166 that have last seg is 29165 when I tyr recover in sqlplus that show below error
    SQL> recover database using backup controlfile;
    ORA-00279: change 1648727512 generated at 09/05/2009 00:02:07 needed for thread
    1
    ORA-00289: suggestion : /oradata/archive/hrprd/1_29166_671345511.arc
    ORA-00280: change 1648727512 for thread 1 is in sequence #29166
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00308: cannot open archived log
    '/oradata/archive/hrprd/1_29166_671345511.arc'
    ORA-27037: unable to obtain file status
    IBM AIX RISC System/6000 Error: 2: No such file or directory
    Additional information: 3
    And I tried to open with reset log that show below error
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '/oradata/data/hrprd/system01.dbf'
    How can I do to open database?
    Taohiko.

    taohiko wrote:
    Hi Werner
    I tried and show below error
    SQL> recover database using backup controlfile until cancel;
    ORA-00279: change 1648727512 generated at 09/05/2009 00:02:07 needed for thread
    1
    ORA-00289: suggestion : /oradata/archive/hrprd/1_29166_671345511.arc
    ORA-00280: change 1648727512 for thread 1 is in sequence #29166
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    CANCEL
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/oradata/data/hrprd/system01.dbf'
    ORA-01112: media recovery not started
    How to do next step?
    TaohikoHi Taohiko
    Have you made backup of all archived redo log files? If so, why this one was disappeared?
    Have you applied all archived redo log files before that required archived redo log file?
    Please try to recover the database using the following command:
    RMAN> RESTORE DATABASE;
    RMAN> RECOVER DATABASE UNTIL SEQUENCE 29166;
    RMAN>ALTER DATABASE OPEN RESETLOGS;

  • Unable to recover database after rman recovery and database open resetlogs

    I am running Oracle 10.2.0.5 on OpenSUSE 9. I have been trying to upgrade the database to 11g, through dbua. I was getting stuck at one point during the Oracle Server install and the upgrade failed and I was forced to restore the database to an earlier backup.
    Below is the current place that I am stuck. As you can see I opened the database multiple times and reset the logs. Now I am afraid that my controlfile and redo log backups are out of sync and i can't get them back on track. Before when I actually got the database recovered RMAN would immediately throw:
    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
    OPA-00600: ORA-00600: internal error code, arguments: ...
    The database would open with ALTER DATABASE RESETLOGS but any query on non-system tables would fail and throw:
    ORA-04045: errors during recompilation/revalidation of LCRS_DEV1.FACILITY_REF
    ORA-00600: internal error code, arguments: [17069], [0x1158ED180], [], [], [],
    I hope I have not dug myself into too deep of a hole here.
    Here is the trace from my most recent attempt.
    RMAN> startup nomount;
    connected to target database (not started)
    Oracle instance started
    Total System Global Area 3070230528 bytes
    Fixed Size 2099424 bytes
    Variable Size 301991712 bytes
    Database Buffers 2751463424 bytes
    Redo Buffers 14675968 bytes
    RMAN> list incarnation of database;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of list command at 08/02/2011 15:49:04
    ORA-01507: database not mounted
    RMAN> restore controlfile from autobackup;
    Starting restore at 02-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    recovery area destination: /opt/oracle/flash_recovery_area
    database name (or database unique name) used for search: LCRSDEV
    channel ORA_DISK_1: autobackup found in the recovery area
    channel ORA_DISK_1: autobackup found: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
    channel ORA_DISK_1: control file restore from autobackup complete
    output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
    Finished restore at 02-AUG-11
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN> list incarnation of database;
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
    2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
    3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11
    4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11
    5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11
    6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11
    7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11
    8 8 LCRSDEV 756543625 CURRENT 95676701 02-AUG-11
    RMAN> restore database until scn 95676700;
    Starting restore at 02-AUG-11
    Starting implicit crosscheck backup at 02-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    Crosschecked 6 objects
    Finished implicit crosscheck backup at 02-AUG-11
    Starting implicit crosscheck copy at 02-AUG-11
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 02-AUG-11
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 08/02/2011 15:52:04
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    RMAN> restore database;
    Starting restore at 02-AUG-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /opt/oracle/oradata/LCRSDEV/system01.dbf
    restoring datafile 00002 to /opt/oracle/oradata/LCRSDEV/undotbs01.dbf
    restoring datafile 00003 to /opt/oracle/oradata/LCRSDEV/sysaux01.dbf
    restoring datafile 00004 to /opt/oracle/oradata/LCRSDEV/users01.dbf
    restoring datafile 00005 to /opt/oracle/oradata/LCRSDEV/LCRS_TBS.dbf
    channel ORA_DISK_1: reading from backup piece /opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp tag=TAG20110722T111922
    channel ORA_DISK_1: restore complete, elapsed time: 00:23:36
    Finished restore at 02-AUG-11
    RMAN> recover database until scn 95676700;
    Starting recover at 02-AUG-11
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/02/2011 16:16:28
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    RMAN> recover database;
    Starting recover at 02-AUG-11
    using channel ORA_DISK_1
    starting media recovery
    archive log thread 1 sequence 90 is already on disk as file /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
    archive log filename=/opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc thread=1 sequence=1
    unable to find archive log
    archive log thread=1 sequence=1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/02/2011 16:25:04
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 1 lowscn 95676701

    Thanks for the reply Hemant. I have reset the database for the controlfile that I am using as backup and now I am not able to recover until the correct SCN. I am thinking that my recovery catalog is bad. If I mount with the current controlfile I have this list of incarnations:
    List of Database Incarnations
    DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
    *1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05*
    *2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11*
    *3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11*
    *4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11*
    *5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11*
    *6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11*
    *7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11*
    *8 8 LCRSDEV 756543625 PARENT 95676701 02-AUG-11*
    *9 9 LCRSDEV 756543625 CURRENT 95676702 02-AUG-11*
    However if I restore the controlfile to the earlier version I am getting the following output from the process:
    RMAN> startup nomount;
    connected to target database (not started)
    Oracle instance started
    Total System Global Area 3070230528 bytes
    Fixed Size 2099424 bytes
    Variable Size 301991712 bytes
    Database Buffers 2751463424 bytes
    Redo Buffers 14675968 bytes
    RMAN> restore controlfile from '/opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp';
    Starting restore at 03-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
    output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
    Finished restore at 03-AUG-11
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN> list incarnation of database;
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
    2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
    3 3 LCRSDEV 756543625 CURRENT 92348137 18-JUL-11
    RMAN> restore database until scn 92348137;
    Starting restore at 03-AUG-11
    Starting implicit crosscheck backup at 03-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    Crosschecked 1 objects
    Finished implicit crosscheck backup at 03-AUG-11
    Starting implicit crosscheck copy at 03-AUG-11
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 03-AUG-11
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g3hn6o_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_2_73g3hnxq_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g0rts6_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_134_72v9gv4s_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_138_72v9p4b4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_120_72v8wwg0_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_121_72v8x5ty_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_131_72v9cnrv_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_139_72v9q5ok_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_137_72v9n4t5_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_136_72v9l88q_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_123_72v8ytm8_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_132_72v9dcxd_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_124_72v8zkg0_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_128_72v96qm1_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_135_72v9jqmx_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_129_72v98q3r_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_125_72v91g3b_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_118_72v8v8r4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_127_72v9626w_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_130_72v9bqtb_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_141_72vncy6g_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_122_72v8ycd4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_126_72v94cns_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_133_72v9fb17_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_140_72vn6wgo_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_119_72v8v9hf_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j3wo01_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73josgf1_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73jh223h_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73josflf_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jvqdqs_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_3_73josh91_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j91rh9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_91_72mqlnx9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_111_72mrdr5m_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_96_72mqx958_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_114_72mrgsf9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_94_72mqs6gj_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_102_72mr3893_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_99_72mr2h6c_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_104_72mr5hfm_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_109_72mrc83z_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_98_72mr080w_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_93_72mqq36m_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_97_72mqz0mm_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_116_72mrk268_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_101_72mr31yv_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_110_72mrddhg_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_95_72mqv3hp_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_105_72mr5vq4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_115_72mrjd2s_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_106_72mr7hnt_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_100_72mr2qfc_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_112_72mrfc5j_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_107_72mr909t_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_103_72mr4pol_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_113_72mrfsb9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_117_72mrl5mf_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_108_72mrb13l_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_92_72mqnxz1_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_143_72y6ww71_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_144_72ybybps_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_142_72xt10j7_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_145_72yccy5z_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758043324_73g3jfxx_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758035850_73fw6vrc_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758133684_73jvr5px_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758127608_73jot9x0_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758109276_73j3xfom_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 08/03/2011 12:53:19
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    Edited by: K Doyle on Aug 3, 2011 10:22 AM

  • Recover database on the other host

    I have to recover my database on the other host.
    In my source machine(redhat5,x86_64) I installed oracle 10g (10.2.0.1), sid=orapro, archive_mode=on, flash_area_recovery=default.
    RMAN - AUTOBACKUP=ON, CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
    In new host (zlinux) I install oracle 10g (10.2.0.2.0). I has used DBCA and create a new database, with the same SID=orapro, archive_mode=on, flash_area_recovery=default.
    RMAN - AUTOBACKUP=ON, CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
    Backup:
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    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 '/dados/db/oracle/product/10.2.0/db_1/dbs/snapcf_orapro.f'; # default
    RMAN> backup database;
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    6 Full 522.79M DISK 00:00:06 10-JUN-08
    BP Key: 6 Status: AVAILABLE Compressed: NO Tag: TAG20080610T112043
    Piece Name: /dados/db/oracle/flash_recovery_area/ORAPRO/backupset/2008_06_10/o1_mf_nnndf_TAG20080610T112043_44x6ycvx_.bkp
    List of Datafiles in backup set 6
    File LV Type Ckp SCN Ckp Time Name
    1 Full 608723 10-JUN-08 /dados/oradata/orapro/system01.dbf
    2 Full 608723 10-JUN-08 /dados/oradata/orapro/undotbs01.dbf
    3 Full 608723 10-JUN-08 /dados/oradata/orapro/sysaux01.dbf
    4 Full 608723 10-JUN-08 /dados/oradata/orapro/users01.dbf
    5 Full 608723 10-JUN-08 /dados/oradata/orapro/rman_ts
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    7 Full 6.80M DISK 00:00:01 10-JUN-08
    BP Key: 7 Status: AVAILABLE Compressed: NO Tag: TAG20080610T112050
    Piece Name: /dados/db/oracle/flash_recovery_area/ORAPRO/autobackup/2008_06_10/o1_mf_s_657026450_44x6ylyd_.bkp
    Control File Included: Ckp SCN: 608730 Ckp time: 10-JUN-08
    SPFILE Included: Modification time: 10-JUN-08
    I sent the backupset and autobackup files from source machine to new host.
    And alter the name of server parameter file 'spfileorapro.ora' on new host for 'spfileorapro-1.ora'.
    Recover:
    $rman target /
    RMAN> set dbid 'dbid_source_machine'
    RMAN> startup nomount
    LRM-00109: could not open parameter file '/dados/u01/app/oracle/product/10.2.0/db_1/dbs/initorapro.ora'
    RMAN> restore spfile to pfile '/dados/u01/app/oracle/product/10.2.0/db_1/dbs/initorapro.ora' from '/dados/u01/app/oracle/flash_recovery_area/ORAPRO/autobackup/2008_06_10/o1_mf_s_657026450_44x6ylyd_.bkp';
    Starting restore at 11-JUN-08
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=36 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 06/11/2008 09:10:01
    RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
    I get the error above.
    Can anybody help me?
    Thanks!

    I try now:
    RMAN> run{
    2> set controlfile autobackup format for device type disk to
    3> '/dados/u01/app/oracle/flash_recovery_area/%F';
    4> restore controlfile from autobackup;}
    executing command: SET CONTROLFILE AUTOBACKUP FORMAT
    Starting restore at 11-JUN-08
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 06/11/2008 15:51:04
    ORA-19625: erro ao identificar arquivo /dados/u01/app/oracle/flash_recovery_area/ORAPRO/autobackup/2008_06_11/o1_mf_s_657128589_450bvsnq_.bkp
    ORA-27047: UNABLE TO READ THE HEADER BLOCK OF FILE
    Additional information: 2
    Corrupt file? Version problem?
    Source machine 10.2.0.1 and new host 10.2.0.2.
    Compatibility?
    Marcos

  • Recover database from archive log: Time based recovery

    Hi,
    Could you pelase help regarding the following:
    I have power outage in my machine running oracle 9i on Solaris OS 9
    Oracle is mounted but failed to open
    Once it is started showing the error message
    SQL> startup;
    ORACLE instance started.
    Total System Global Area 9457089744 bytes
    Fixed Size 744656 bytes
    Variable Size 3154116608 bytes
    Database Buffers 6291456000 bytes
    Redo Buffers 10772480 bytes
    Database mounted.
    ORA-01113: file 4 needs media recovery
    ORA-01110: data file 4: '/opt/oracle/oradata/sysdb/indx/indx01.dbf'
    So I tried to recover the database
    SQL> recover database;
    ORA-00279: change 1652948240 generated at 12/03/2007 13:09:08 needed for thread
    1
    ORA-00289: suggestion : /opt/oracle/oradata/nobilldb/archive/1_183942.dbf
    ORA-00280: change 1652948240 for thread 1 is in sequence #183942
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00279: change 1652948816 generated at 12/03/2007 13:09:19 needed for thread
    1
    ORA-00289: suggestion : /opt/oracle/oradata/nobilldb/archive/1_183943.dbf
    ORA-00280: change 1652948816 for thread 1 is in sequence #183943
    ORA-00278: log file '/opt/oracle/oradata/nobilldb/archive/1_183942.dbf' no
    longer needed for this recovery
    The power outage at 16:00pm and the recovery archive log file '/opt/oracle/oradata/nobilldb/archive/1_183942.dbf' at 11 am
    Always I am applying the next sequence it is giving the same message and asking the next sequence. I have more than 900 archive log from 11am to 4pm and each of them having the size of 100mb and it take 1 minute to get back from each to provide this error message.
    How I can start my recovery from say 15:45 onwards until 16:15?
    I have all archive logs in the proper destination.
    Still my database is not opened and it is starts applying archive log since 5 hours back, please help me regarding this
    Thanks in advance

    Wrong forum. Post your question in the following forum:
    General Database Discussions

  • What order are Archive logs restored in when RMAN recover database issued

    Ok, you have a run block that has restored your level-0 RMAN backup.
    Your base datafiles are down on disc.
    You are about to start recovery to point in time, lets say until this morning at 07:00am.
    run {   set until time "TO_DATE('2010/06/08_07:00:00','YYYY/MM/DD_HH24:MI:SS')";
    allocate channel d1 type disk;
    allocate channel d2 type disk;
    allocate channel d3 type disk;
    allocate channel d4 type disk;
    recover database;
    So the above runs, it analyses the earlies SCN required for recovery, checks for incremental backups (none here), works out the archivelog range
    required and starts to restore the archive logs. All as expected and works.
    My question: Is there a particular order that RMAN will restore the archive logs and is the restore / recover process implemented as per the run block.
    i.e Will all required archive logs based on the run block be restored and then the database recovered forward. Or is there something in RMAN that says restore these archive logs, ok now roll forwards, restore some more.
    When we were doing this the order of the archive logs coming back seemed to be random but obviously constrained by the run block. Is this an area we need to tune to get recoveries faster for situations where incrementals are not available?
    Any inputs on experience welcome. I am now drilling into the documentation for any references there.
    Thanks

    Hi there, thanks for the response I checked this and here are the numbers / time stamps on an example:
    This is from interpreting the list backup of archivelog commands.
    Backupset = 122672
    ==============
    Archive log sequence 120688 low time: 25th May 15:53:07 next time: 25th May 15:57:54
    Piece1 pieceNumber=123368 9th June 04:10:38 <-- catalogued by us.
    Piece2 pieceNumber=122673 25th May 16:05:18 <-- Original backup on production.
    Backupset = 122677
    ==============
    Archive log sequence 120683 low time: 25th May 15:27:50 Next time 25th May 15:32:24 <-- lower sequence number restored after above.
    Piece1 PieceNumber=123372 9th June 04:11:34 <-- Catalogued by us.
    Piece2 PieceNumber=122678 25th May 16:08:45 <-- Orignial backup on Production.
    So the above would show that if catalogue command you could influence the Piece numbering. Therefore the restore order if like you say piece number is the key. I will need to review production as to why they were backed up in different order completed on production. Would think they would use the backupset numbering and then piece within the set / availability.
    Question: You mention archive logs are restored and applied and deleted in batches if the volume of archivelogs is large enough to be spread over multiple backup sets. What determines the batches in terms of size / number?
    Thanks for inputs. Answers some questions.

  • Recover database in NOarchivelog mode :)

    Hi all. How to recover a database wich is in noarchivelog mode? B-)
    Suppose,
    I have 3 redolog groups (with two members in each, the second members are located on another drive ). When first redo log group was 1/2 full I took a full backup. Then there were 2 switches from first to second and from second to third. Now the currnet redolog group - 3 (just started). At this point we faced media failer. How to roll forward changes using backup + online redologs?
    Edited by: Junior Oracle DBA on Oct 16, 2008 1:53 PM

    Restore your database cold backup (excluding redo logs).
    Then issue this command :
    RECOVER DATABASE USING BACKUP CONTROLFILE
    provide the names of the last ACTIVE / CURRENT Redo Logs in the database when Oracle prompts for an ArchiveLog.
    When Oracle has finished recovery to a consistent point in time, it will return to the command prompt without any error.
    Now issue this command :
    ALTER DATABASE OPEN RESETLOGS
    You would have a Complete Recovery.
    This is provided that Oracle had NOT cycled through all the Online Redo Logs since the time when the Cold Backup was taken. (If Oracle had cycled through all the Online Redo Logs, it would have overwrriten the oldest log because it wasn't in ArchiveLog mode).
    Hemant K Chitale
    http://hemantoracledba.blogspot.com

  • How to recover database without controlfile and redo files?

    Hi all,
    If I just have datafiles using hot backup saving in another machine, and all files in current database were lost including data files,control files and redo log files .
    How can I recover database just using hot backup datafiles? without control file, without redo files.
    Your help is greatly appreciated.

    alter database backup control file to trace
    SQL> alter database backup controlfile to trace;
    Go to udump folder in oracle home folder check the trace file copy these lines
    CREATE CONTROLFILE REUSE DATABASE "O10G1” NORESETLOGS NOARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 454
    LOGFILE
    GROUP 1 'E:\ORACLE2\PRODUCT\10.1.0\ORADATA\O10G1\REDO01.LOG' SIZE 10M,
    GROUP 2 'E:\ORACLE2\PRODUCT\10.1.0\ORADATA\O10G1\REDO02.LOG' SIZE 10M,
    GROUP 3 'E:\ORACLE2\PRODUCT\10.1.0\ORADATA\O10G1\REDO03.LOG' SIZE 10M
    -- STANDBY LOGFILE
    DATAFILE
    'E:\ORACLE2\PRODUCT\10.1.0\ORADATA\O10G1\SYSTEM01.DBF',
    'E:\ORACLE2\PRODUCT\10.1.0\ORADATA\O10G1\UNDOTBS01.DBF',
    'E:\ORACLE2\PRODUCT\10.1.0\ORADATA\O10G1\SYSAUX01.DBF',
    'E:\ORACLE2\PRODUCT\10.1.0\ORADATA\O10G1\USERS01.DBF'
    CHARACTER SET WE8MSWIN1252
    Change the new database name “abc
    ” and REUSE replaced by SET and NORESTLOGS replaced by RESTLOGS above lines.
    Save as C1.sql
    C:\ set oracle_sid=instance name
    C:\>sqlplus /nolog
    SQL*Plus: Release 10.1.0.2.0 - Production on Tue Apr
    11 06:44:28 2006
    Copyright (c) 1982, 2004, Oracle. All rights reserved.
    SQL> connect / as sysdba;
    Connected to an idle instance.
    SQL> startup nomount
    pfile='C:\oracle\product\10.1.0\admin\jeeno\pfile\jeenoinit.ora'
    ORACLE instance started.
    Total System Global Area 171966464 bytes
    Fixed Size 787988 bytes
    Variable Size 145750508 bytes
    Database Buffers 25165824 bytes
    Redo Buffers 262144 bytes
    SQL> @c1.sql
    Control file created.
    SQL> alter database open resetlogs;
    Database altered

  • How to recover database in this situation?

    My os is windows 2000 server, the oracle database version is 9.2.0.1
    And the database is in archivelog mode.
    first: I backup the controlfile to trace
    second: I added a new tablespace
    third: I shutdown immediate the database
    forth: I delete the controlfile and datafile of the new added database
    then: I tried to recover my database.
    But I meet troubles.
    I am a user from China. Appreciate your help!
    C:\>sqlplus
    SQL*Plus: Release 9.2.0.1.0 - Production on &#26143;&#26399;&#19968; 10&#26376; 24 21:05:24 2005
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    &#35831;&#36755;&#20837;&#29992;&#25143;&#21517;: sys/nolog as sysdba
    &#36830;&#25509;&#21040;:
    Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.1.0 - Production
    SQL> archive log list
    &#25968;&#25454;&#24211;&#26085;&#24535;&#27169;&#24335; &#23384;&#26723;&#27169;&#24335;
    &#33258;&#21160;&#23384;&#26723; &#21551;&#29992;
    &#23384;&#26723;&#32456;&#28857; D:\oracle\ora92\RDBMS
    &#26368;&#26089;&#30340;&#27010;&#35201;&#26085;&#24535;&#24207;&#21015; 0
    &#19979;&#19968;&#20010;&#23384;&#26723;&#26085;&#24535;&#24207;&#21015; 1
    &#24403;&#21069;&#26085;&#24535;&#24207;&#21015; 1
    SQL> select group#, sequence#, archived, status from v$log;
    GROUP# SEQUENCE# ARC STATUS
    1 0 YES UNUSED
    2 0 YES UNUSED
    3 1 NO CURRENT
    SQL> create tablespace user_data datafile
    2 'd:\oracle\oradata\wwfdb\user_data01.dbf' size 50m;
    &#34920;&#31354;&#38388;&#24050;&#21019;&#24314;&#12290;
    SQL> create table t(a number) tablespace user_data;
    &#34920;&#24050;&#21019;&#24314;&#12290;
    SQL> insert into t values(10);
    &#24050;&#21019;&#24314; 1 &#34892;&#12290;
    SQL> commit;
    SQL> shutdown immediate
    &#25968;&#25454;&#24211;&#24050;&#32463;&#20851;&#38381;&#12290;
    &#24050;&#32463;&#21368;&#36733;&#25968;&#25454;&#24211;&#12290;
    ORACLE &#20363;&#31243;&#24050;&#32463;&#20851;&#38381;&#12290;
    SQL> host del d:\oracle\oradata\wwfdb\*.CTL
    SQL> host del d:\oracle\oradata\wwfdb\user_data01.dbf
    SQL> startup nomount
    ORACLE &#20363;&#31243;&#24050;&#32463;&#21551;&#21160;&#12290;
    Total System Global Area 135338868 bytes
    Fixed Size 453492 bytes
    Variable Size 109051904 bytes
    Database Buffers 25165824 bytes
    Redo Buffers 667648 bytes
    SQL> CREATE CONTROLFILE REUSE DATABASE "WWFDB" NORESETLOGS ARCHIVELOG
    2 MAXLOGFILES 50
    3 MAXLOGMEMBERS 5
    4 MAXDATAFILES 100
    5 MAXINSTANCES 1
    6 MAXLOGHISTORY 226
    7 LOGFILE
    8 GROUP 1 'D:\ORACLE\ORADATA\WWFDB\REDO01.LOG' SIZE 100M,
    9 GROUP 2 'D:\ORACLE\ORADATA\WWFDB\REDO02.LOG' SIZE 100M,
    10 GROUP 3 'D:\ORACLE\ORADATA\WWFDB\REDO03.LOG' SIZE 100M
    11 DATAFILE
    12 'D:\ORACLE\ORADATA\WWFDB\SYSTEM01.DBF',
    13 'D:\ORACLE\ORADATA\WWFDB\UNDOTBS01.DBF',
    14 'D:\ORACLE\ORADATA\WWFDB\CWMLITE01.DBF',
    15 'D:\ORACLE\ORADATA\WWFDB\DRSYS01.DBF',
    16 'D:\ORACLE\ORADATA\WWFDB\EXAMPLE01.DBF',
    17 'D:\ORACLE\ORADATA\WWFDB\INDX01.DBF',
    18 'D:\ORACLE\ORADATA\WWFDB\ODM01.DBF',
    19 'D:\ORACLE\ORADATA\WWFDB\TOOLS01.DBF',
    20 'D:\ORACLE\ORADATA\WWFDB\USERS01.DBF',
    21 'D:\ORACLE\ORADATA\WWFDB\XDB01.DBF'
    22 CHARACTER SET ZHS16GBK;
    &#25511;&#21046;&#25991;&#20214;&#24050;&#21019;&#24314;
    SQL> recover database until time '2005-10-24 21:10:33';
    &#23436;&#25104;&#20171;&#36136;&#24674;&#22797;&#12290;
    SQL> alter database open;
    alter database open
    ERROR &#20301;&#20110;&#31532; 1 &#34892;:
    ORA-01589: ??????????? RESETLOGS ? NORESETLOGS ??
    SQL> alter database open noresetlogs;
    &#25968;&#25454;&#24211;&#24050;&#26356;&#25913;&#12290;
    SQL> select * from t;
    select * from t
    ERROR &#20301;&#20110;&#31532; 1 &#34892;:
    ORA-00376: ???????? 11
    ORA-01111: ???? 11 ???? - ?????????
    ORA-01110: ???? 11: 'D:\ORACLE\ORA92\DATABASE\MISSING00011'
    the above sql statement:
    recover database until time '2005-10-24 21:10:33'&#65292;the reason I choosed the time '2005-10-24 21:10:33'
    is based the contents of alert.log file:
    Mon Oct 24 21:10:20 2005
    create tablespace user_data datafile
    'd:\oracle\oradata\wwfdb\user_data01.dbf' size 50m
    Mon Oct 24 21:10:32 2005
    Completed: create tablespace user_data datafile
    'd:\oracle\or

    Hi,
    why you create trace file ? and if you did that then you must have trace your ctl file after adding the tablespace for your db.so your ctl file will have registered the name of newly created tablespace.and if you do not have backup of ctl file which dosent contain the name of newly created tablespace then how would you recover your tablespace ? if you want to achieve your disered thoughts then add the tablespace and then backup of your full db then shutdown your db and delete your ctl file and data file.now open your db in nomount mode then restore your ctl file and datafile.
    thanks
    Alok

  • Recovering database

    Hi,
    In our environment we sometimes copy "live" database from one disk volume to other. We use NetApp Snapmirror technology, but that is not important. That way, on the second volume we get a snapshot of that "live" database. What's obvious, the snapshot is inconsistent and before the copy database can be opened, needs recovery. We recover it using the "recover database" command. That solution we have been using for ages.
    The copied database usually performs recovery using redolog files. But yesterday, during recovery, the database asked us for archived redolog files (archived one day before). That was not a problem, we restored what was needed, but we couldn't deliver the "copy" database to users on time.
    I was asked to explain why the database needed the archived log files. My first explanation was "because the copy database was inconsistent as a result of long running transactions on the source database". But in my opinion undo data, to undo all uncommitted transactions is taken from undo tablespace. Nothing must have been redone. Can you explain me what the database had to redo? What could be the reason? Would you be so kind and give me advice how may I investigate the reason? In the future we have to deliver copied databases on time so there is a pressure put on me.
    Any help will be appreciated.
    Regards,
    Tim

    You don't mention a database version, but I presume you either do 'alter database begin backup' (if 10g) or 'alter tablespace ... begin backup' (if not 10g) before taking your mirror snapshot?
    If not, you're lucky to have had this thing working at all.
    If you issue those sorts of 'begin backup' commands, then there will be a database/tablespace checkpoint and the header blocks of the files involved will be updated with the latest checkpoint change number. During the recovery of your mirror, you will only need to roll those files forward from that point. The contents of the buffer cache for those files will be flushed to disk, and the copied files are therefore guaranteed to have contents no earlier than the header block's checkpoint change number.
    If you don't issue those sorts of commands, then Lord knows what state your datafile headers are in, and stuff in the buffer cache isn't necessarily flushed to disk in time. The copied file can therefore contain blocks from any checkpoint change number you care to think of onwards, and it's all pure chance what you get asked to supply by way of redo to rectify the situation.
    Recovery means rolling things forward as well as rolling them back: your comment about undo is a bit misguided therefore. You need undo and redo to be able to complete a recovery.

  • After a recover database, how can I find the time of the last transaction?

    After doing a restore and recovery. Is there something in the data dictionary that I can query to find the time of the last applied transaction that took place during the recover process?
    restore database ;
    recover database ;
    For example, if I restored from a full backup on 8/3/2008 with archive redologs, I know my last restored transaction is from sometime on that day, but I'd like a way to know the hour:minute:second of the last transaction included in the backup and redologs that was applied to my restore. Is that possible?
    The recover database applies all available redo logs for that day, but I want to know if that includes transaction up to 6PM, or 11:50PM, etc?
    Thanks,
    Jason

    If you did only a "recover database" that would have been a Complete Recovery to the last transaction -- ie the point when the database was shutdown.
    For an Incomplete Recovery, you would have to note the Sequence#, SCN or Timestamp of the recovery point.

  • Recover Database in RMAN vs SQL*PLUS

    Hello,
    Oracle 11.2.0.1, Oracle Linux 5.5 UEK.
    I recently did a "recover database" in sql*plus, but an attempt to open the database gave ORA-01113, complaining the system tablespace requried more recovery. Then I used RMAN (nocatalog) and after the same "recover database" command I was able to open the database.
    It seems there are differences between SQL*PLUS and RMAN "recover database" command. I have not been able to locate the chapter in the Oracle documentation that explains the difference. I have some ideas, but...
    Thanks.
    h3. Solution Summary:
    The recover command in RMAN compared to SQL*Plus implements a more user friendly processing logic based on the current detected scenario. For instance, a RMAN recover database command may actually perform a "recover database using backup controlfile until cancel" and automatically apply all archived and online redo logs if available. The same can be achieved with the recover command in SQL*plus, but will have to be done manually.
    Edited by: Dude on Jan 7, 2011 12:30 PM

    Dude wrote:
    I did not remove any datafiles or redo logs. it is the same restore operation as before, and again RMAN "recovery database" succeeds, whereas SQL recover has trouble. This tells me something is different between the two methods. For one, RMAN does not requrie to specify "using backup controlfile".
    Maybe someting about "resetlogs" that that RMAN recover can handle and SQL recover not?No,problem is there.If you using rman execute RECOVER DATABASE it also will apply online logs(if available) also and as result you will get complete recovery however you must open database with resetlogs option due to you recovered database using backup controlfile.So also you can recover and open database applying this online logs.After executing RECOVER DATABASE USING BACKUP CONTROLFILE you have to pass full path of online log then press ENTER so log will apply and you can open database with RESETLOGS.See below
    C:\Documents and Settings\chinar>rman target sys/sm
    Recovery Manager: Release 10.2.0.1.0 - Production on Fri Jan 7 17:47:49 2011
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    connected to target database (not started)
    RMAN> startup nomount;
    Oracle instance started
    Total System Global Area     138412032 bytes
    Fixed Size                     1247708 bytes
    Variable Size                 71304740 bytes
    Database Buffers              58720256 bytes
    Redo Buffers                   7139328 bytes
    RMAN> restore controlfile from 'D:\oracle\product\10.2.0\flash_recovery_area\T\B
    ACKUPSET\2011_01_07\O1_MF_NCSNF_TAG20110107T171001_6LG48JR5_.BKP'
    2> ;
    Starting restore at 07-JAN-11
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=157 devtype=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
    output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL01.CTL
    output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL02.CTL
    output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL03.CTL
    Finished restore at 07-JAN-11
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN> restore database;
    Starting restore at 07-JAN-11
    Starting implicit crosscheck backup at 07-JAN-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    Crosschecked 1 objects
    Finished implicit crosscheck backup at 07-JAN-11
    Starting implicit crosscheck copy at 07-JAN-11
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 07-JAN-11
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\T\BACKUPSET\2011_01_07\O
    1_MF_NCSNF_TAG20110107T171001_6LG48JR5_.BKP
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\SYSTEM01.DBF
    restoring datafile 00002 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\UNDOTBS01.DBF
    restoring datafile 00003 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\SYSAUX01.DBF
    restoring datafile 00004 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\USERS01.DBF
    channel ORA_DISK_1: reading from backup piece D:\ORACLE\PRODUCT\10.2.0\FLASH_REC
    OVERY_AREA\T\BACKUPSET\2011_01_07\O1_MF_NNNDF_TAG20110107T171001_6LG45BXS_.BKP
    channel ORA_DISK_1: restored backup piece 1
    piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\T\BACKUPSET\2011_01_07
    \O1_MF_NNNDF_TAG20110107T171001_6LG45BXS_.BKP tag=TAG20110107T171001
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:04
    Finished restore at 07-JAN-11
    RMAN> recover database;
    Starting recover at 07-JAN-11
    using channel ORA_DISK_1
    starting media recovery
    archive log thread 1 sequence 7 is already on disk as file D:\ORACLE\PRODUCT\10.
    2.0\ORADATA\T\REDO02.LOG
    archive log filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG thread=1 sequ
    ence=7
    media recovery complete, elapsed time: 00:00:03
    Finished recover at 07-JAN-11
    RMAN> exit
    Recovery Manager complete.
    C:\Documents and Settings\chinar>sqlplus sys/sm as sysdba
    SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jan 7 17:51:31 2011
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL> alter database open;
    alter database open
    ERROR at line 1:
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL> alter database open resetlogs;
    Database altered.
    SQL> And above you see lines as
    archive log thread 1 sequence 7 is already on disk as file D:\ORACLE\PRODUCT\10.
    *2.0\ORADATA\T\REDO02.LOG*
    archive log filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG thread=1 sequ
    ence=7
    It means RMAN apply these.So you can apply these using SQLPLUS ALSO.In additionally you can see that from alert log as
    alter database recover if needed
    start until cancel using backup controlfile
    Media Recovery Start
    parallel recovery started with 2 processes
    ORA-279 signalled during: alter database recover if needed
    start until cancel using backup controlfile
    Fri Jan 07 17:50:34 2011
    alter database recover logfile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG'
    Fri Jan 07 17:50:34 2011
    Media Recovery Log D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG
    Fri Jan 07 17:50:34 2011
    Incomplete recovery applied all redo ever generated.
    Recovery completed through change 665263
    Completed: alter database recover logfile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG'And finally you see clearly that even if you execute RECOVER DATABASE from RMAN it actually execute RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE (from alert.log start  until cancel using backup controlfile)
    And these is not any difference.
    Hope that help you and you got answer.

  • Recover database to last backup?

    I have a question about recovering a database in the cleanest way. I have a hot backup every day. If I need to restore from the hot backup (due to a logical corruption - i.e. a batch process messed up) I want to be able to continue as normal.
    I would like to be able to just shut down my database and copy my hot backup files and start it back up at the time of the night before.
    Can I do this without doing a resetlogs? What about the .arc files that were generated in the meantime? Can I just ignore them. Will oracle simply continue from the current sequence number?
    What about if I subsequently do another recovery tomorrow, from an even earlier time? I would not be able to roll forward through this last recovery since I did a file copy of the hot backup, right?
    Is my best option to just do a reset logs and go from there?

    If I need to restore from the hot backup (due to a logical corruption - i.e. a batch process messed up) I want to be able to continue as normal.
    I would like to be able to just shut down my database and copy my hot backup files and start it back up at the time of the night before.
    r.- If you have this case you have to have the archives generated from the moment when you began to carry out the backup last night in order to perform an incomplete recovery.
    I would like to be able to just shut down my database and copy my hot backup files and start it back up at the time of the night before.
    r.- To do this you have to perform a "RECOVERY DATABASE UNTIL <option>"
    Can I do this without doing a resetlogs?
    r.- Not, incomplete recovery needs this option to syncronyze the datafiles.
    What about the .arc files that were generated in the meantime? Can I just ignore them
    What about if I subsequently do another recovery tomorrow, from an even earlier time? I would not be able to roll forward through this last recovery since I did a file copy of the hot backup, right?
    r.- Yes, you can ignore them. The most important post-task after doing an incomplete recovery is to shutdown take a whole backup of the database in order to be able to recover the database to that point if it is needed.
    Is my best option to just do a reset logs and go from there?
    r.- Depending of what kind of corruption you have in the database.
    Joel Pèrez
    http://otn.oracle.com/experts

  • Error in Recover Database -  ORA-01547 , ORA-01194 and ORA-01110

    Hello folks,
    I am facing a problem when recovering a database..
    I made each tablespace in backup mode, then copied the datafile. I revert back the tablespace status to normal status.Once all datafiles are copied to target location, i created the control file from the source db.
    I started the target db by
    sqlplus "/ as sysdba"
    then i executed the control file
    SQL>@ctrlfile.sql
    Control file got created.
    SQL>recover database until cancel using backup controlfile;
    it asked for archives. I gave the path one by one until everything was done.Now i gave 'cancel' as below.
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 377 needs more recovery to be consistent
    ORA-01110: data file 377: '<path>/xxfndx01.dbf'
    ORA-01112: media recovery not started
    Could anyone please tell me where I went wrong and how can I move ahead from this stage???
    Later on, when I gave open resetlogs, it gave the same error(as below)
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 377 needs more recovery to be consistent
    ORA-01110: data file 377: '<path>/xxfndx01.dbf'
    Please let me know the mistake I made, how to avoid that and how to proceed now ???
    Thanks,
    Cherrish Vaidiyan
    [email protected]

    Hello Cherrish,
    A very good question you have asked. I hope you realize that you're doing an incomplete recovery. There is some amount of information that is still there in the online redo-log, that would not be applied on your target db. Moreover when you're using backup controlfile, you do not know till which point you need to apply archive logs.
    For incomplete recovery, Oracle for some reason has been very strict about the recover database command. i.e.
    recover database using backup controlfile
    recover database using backup controlfile until cancel
    Is not same. It also applies to the command that you had given. By giving the command 'recover database using backup controlfile until cancel', you're telling Oracle that incomplete recovery is in process, and you would do resetelogs, to make sure all files are in sync. This is required when you have lost the redo-logs
    In case you have just lost the control file. All latest redo-logs, archive-logs and datafiles are okay (or have been restored), then recover database using backup controlfile; would work perfectly okay. and resetlogs would not be required.. and that would be a complete recovery
    I hope this all makes sense to you
    Regards
    Sudhanshu

Maybe you are looking for

  • I recently purchased an iPad2 and can't synchronize it to iTunes.

    When I connect it to my PC (Windows 7, iTunes 10.3.1.55), I get a message stating that it could not read from my iPad2 and asking to restore it. I downloaded the most recent iTunes and restored the iPad over and over. After restoration, Ipad launches

  • DVD Slideshow Images Flickering

    I was a Window user. Now I am a new MAC user. I bought iMac mainly to do slideshows and video. I heard that MAC is great for slideshows and videos. iLife is great. But.. There is always a but. This is a big BUT and I sincerely hope that going to MAC

  • DLL destruction

    Hey FOlks. I have a DLL that is called from my Java app. I want to be able to tell the DLL when my app is closing so that the DLL can destruct and free its resources. My probelm is that I am using a finalizer in my class (I want to be able to do this

  • List of sap companies in hyderabad

    hi all, Can somebody send me the list of companies of sap in hyderabad to my mail id, i will be very thankful. my mail id is [email protected] thanx mallik

  • Coherence Management Pack questions

    Hi all, I'm attempting to setup the Coherence Management Pack for OEM12c integration but have a few questions on which I can seem to get clear answers. My understanding is that there needs to be a node setup as a JMX monitoring node for the Coherence