Recover Database after opening in Resetlog

Hi All,
Is it possible to recover datbase after opening it in resetlog.
Scenoria:
Due to some serious update exceuted on a particular table , I want to extract one table from previous day morning backup and apply archive still 4PM .
But after recovering the datbase still 2PM ..I opened the database with resretlog .
Now how can I apply archive generated after 2 clock.
Do I need to restore the database again?
Thanks

Do I need to restore the database again?Yes. You have to restore the database and proceed until applying archive logs upto 4pm.
RESETLOGS - Updates all current datafiles and online redo logs and all subsequent archived redo logs with a new RESETLOGS SCN and time stamp.Archives the current online redo logs (or up to the last redo record before redo corruption if corruption is found), clears the contents of the online redo logs, and resets the online redo logs to log sequence 1.

Similar Messages

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 after lossing system tablespace without backup

Hi
My database fail because of hardware failure and then system tablespace corrupted. other tablespaces and control files are OK. Can I recover my database without backup of system tablespace?

hi,
if you have not taken the physical backup (inconsistent or consistent) then you can not recocver it. you need to have some backup up strategy with RMAN or Manual. Do you have hardware (Disk) Mirroring to cover the media failure??
Atleast if you have the logical backups?? then create the database and import it..
Thanks
--Raman.

Can't recover database - ORA-0610

Oracle 11g
Win 2008
Can't recover database after db crashed last night.
Database dismounted.
ORACLE instance shut down.
SQL> connect sys/sys as sysdba
Connected to an idle instance.
SQL> startup;
ORACLE instance started.
Total System Global Area 6847938560 bytes
Fixed Size 2188768 bytes
Variable Size 4798286368 bytes
Database Buffers 2030043136 bytes
Redo Buffers 17420288 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open NORESETLOGS;
alter database open NORESETLOGS
ERROR at line 1:
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
When I try to create backup contriol file, I get os error:
SQL> alter database backup controlfile to '
2 F:\app\oradata\AHRPROD\control02.ctl';
alter database backup controlfile to '
ERROR at line 1:
ORA-01580: error creating control backup file
F:\app\oradata\AHRPROD\control02.ctl
ORA-27040: file create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 123) The filename, directory name, or volume label syntax is
incorrect.

805758 wrote:
Here is the original error I got this morning:
Status Failed
Details ORA-01033: ORACLE initialization or shutdown in progress (DBD ERROR: OCISessionBeginsqlplus
/ as sysdba
shutdown abort
startup
exit
COPY commands (above) & results then PASTE all back here

Is there a way to apply archive logs, standby DB is opened with 'resetlogs'

Hi All,
I have setup a standby database (Oracle 10g SE). I applied hot backup and archive logs to the standby database till yesterday. I have opened the standby database using 'alter database open resetlogs;" and validated the application functionality using the standby database.
Now I want to regularly apply logs from the Primary database to the standby database, but today I have opened the standby database using 'alter database open resetlogs;"
Need assistance to know the way to apply archive logs, once the standby database is opened with 'resetlogs' option to keep it in sync with the Primary database.
Thanks
Kunal

Welcome to OTN,
I have setup a standby database (Oracle 10g SE). I applied hot backup and archive logs to the standby database till yesterday. I have opened the standby database using 'alter database open resetlogs;" and validated the application functionality using the standby database.Standby opened with *resetlogs* ? What you did? have you performed failover of standby database?
Now I want to regularly apply logs from the Primary database to the standby database, but today I have opened the standby database using 'alter database open resetlogs;"
Need assistance to know the way to apply archive logs, once the standby database is opened with 'resetlogs' option to keep it in sync with the Primary database.Have you enabled Flashback & created Restore point? If so you can do it.. If not rebuild standby again.
Check this scenario How To Open Physical Standby For Read Write Testing and Flashback [ID 805438.1]

Simplify recovery after opening the database with the RESETLOGS option

Hi All,
I just have doubt ,regarding the topic which is given in Oracle 11g Exam Syllabus for upgrading from 9i to 11g OCP.The opic is
*"Simplify recovery after opening the database with the RESETLOGS option"* in this topic what one need to study.
As i am little bit confuse related to "Recovery through RESETLOGS and reset of the incarnation of the database".
Kindly correct me if i am wrong
Thanks in advance

vk82 wrote:
Hi All,
I just have doubt ,regarding the topic which is given in Oracle 11g Exam Syllabus for upgrading from 9i to 11g OCP.The opic is
*"Simplify recovery after opening the database with the RESETLOGS option"* in this topic what one need to study.
As i am little bit confuse related to "Recovery through RESETLOGS and reset of the incarnation of the database".
Kindly correct me if i am wrong
Thanks in advanceyou are correct so you can mark this thread as answered
Handle:     vk82
Status Level:     Newbie (35)
Registered:     Nov 21, 2010
Total Posts:     733
Total Questions:     180 (115 unresolved)

Instance scrash whenever database open with resetlogs

I have a Oracle 10.1.0.4 on Linux 2.6.9-34.ELsmp. Whenever I open database with resetlogs (after database cloning or recover database with backup control file), instance crash with 7445 error. Can anybody give a help? Thanks in advance.
Errors in file /oracle/admin/q004/bdump/q004_smon_8075.trc:
ORA-07445: exception encountered: core dump [ksqdeli()+95] [SIGSEGV] [Address not mapped to object] [0x000000008] [] []
ORA-25153: Temporary Tablespace is Empty
Threshold validation cannot be done before catproc is loaded.
Thu Apr 13 14:10:48 2006
Errors in file /oracle/admin/q004/bdump/q004_pmon_8065.trc:
ORA-00474: SMON process terminated with error
Thu Apr 13 14:10:48 2006
PMON: terminating instance due to error 474
Instance terminated by PMON, pid = 8065

Hi,
Did you have any backups running on the database?
Or did you take a backup of datafiles and control files before trying to create a control file?
It seems that as the database shutdown was not a normal shutdown, all the files are not "synchronized".
If you have a backup of the files after the crash, then you can try starting the instance without the control file which is out of sync(user1/genisys/sys/cntrlINS02.dbf).
Is it a production DB?
Regards,
Badri.

How to recover my database after lose some archivelogs?

How to recover my database after lose some archivelogs?
What should I do next?
When I make a point-in-time recovery, I get the following message:
Oracle Error:
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: '/u01/app/oracle/oradata/rcatalog/system01.dbf'
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/25/2008 16:41:19
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 17 lowscn 798237 found to restore
RMAN-06025: no backup of log thread 1 seq 16 lowscn 796977 found to restore
RMAN-06025: no backup of log thread 1 seq 15 lowscn 781378 found to restore
RMAN-06025: no backup of log thread 1 seq 14 lowscn 759019 found to restore
RMAN-06025: no backup of log thread 1 seq 13 lowscn 709039 found to restore
RMAN-06025: no backup of log thread 1 seq 12 lowscn 708479 found to restore
RMAN-06025: no backup of log thread 1 seq 11 lowscn 676234 found to restore
RMAN-06025: no backup of log thread 1 seq 10 lowscn 646686 found to restore
RMAN-06025: no backup of log thread 1 seq 9 lowscn 645207 found to restore
RMAN-06025: no backup of log thread 1 seq 8 lowscn 645199 found to restore
RMAN-06025: no backup of log thread 1 seq 7 lowscn 595363 found to restore
RMAN-06025: no backup of log thread 1 seq 6 lowscn 557197 found to restore
RMAN-06025: no backup of log thread 1 seq 5 lowscn 519102 found to restore
RMAN-06025: no backup of log thread 1 seq 4 lowscn 519053 found to restore
RMAN-06025: no backup of log thread 1 seq 3 lowscn 492824 found to restore
RMAN-06025: no backup of log thread 1 seq 2 lowscn 476888 found to restore

Mixing thread
yours recovery asking a lot of archivelog ,you are in the situation now like you are in no archive mode recovery..which requires last cold backup.
What you can do is restore yours old backup with its old controlfile and then recover till before that miissing log by using recover database using backup controlfile.
Khurram

Can not open database after restore...

Hi,
I am doing a system copy from a online backup of our production system to our qas system. It is AIX and Oracle 10.2.0.2.0 on both systems.
I have done the restore using the backup log file from the production system. I have run the control.sql script, applied 4 archive log files using "recover database using backup controlfile until cancel;". Last I run "alter database open resetlogs;", but here my problems start....
Here is what happends...
I apply the archive logs:
ORA-00279: change 65129304 generated at 01/22/2008 19:50:35 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8210_632565567.dbf
ORA-00280: change 65129304 for thread 1 is in sequence #8210
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8209_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
From the alert log:
ALTER SYSTEM ARCHIVE LOG ALL USING BACKUP CONTROLFILE start
Database is not in archivelog mode
ALTER SYSTEM ARCHIVE LOG ALL USING BACKUP CONTROLFILE complete
2008-02-23 01:00:23.810
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Have somebody had this problem? Hope you can help me :-).
Best regards Henrik

I entered cancel when the log files had been restored and then I did "alter database open resetlogs;"
Here is what I did:
orasrq> sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.2.0 - Production on Fri Feb 22 13:01:38 2008
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 4714397696 bytes
Fixed Size                  2077560 bytes
Variable Size            2365590664 bytes
Database Buffers         2332033024 bytes
Redo Buffers               14696448 bytes
SQL> @controlSRQ.sql
Control file created.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/SRQ/sapdata1/system_1/system.data1'
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 65088663 generated at 01/22/2008 18:30:19 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8203_632565567.dbf
ORA-00280: change 65088663 for thread 1 is in sequence #8203
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65091816 generated at 01/22/2008 18:35:25 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8204_632565567.dbf
ORA-00280: change 65091816 for thread 1 is in sequence #8204
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8203_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65094835 generated at 01/22/2008 18:39:16 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8205_632565567.dbf
ORA-00280: change 65094835 for thread 1 is in sequence #8205
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8204_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65101797 generated at 01/22/2008 18:56:03 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8206_632565567.dbf
ORA-00280: change 65101797 for thread 1 is in sequence #8206
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8205_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65108888 generated at 01/22/2008 19:05:31 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8207_632565567.dbf
ORA-00280: change 65108888 for thread 1 is in sequence #8207
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8206_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 65108888 generated at 01/22/2008 19:05:31 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8207_632565567.dbf
ORA-00280: change 65108888 for thread 1 is in sequence #8207
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65115833 generated at 01/22/2008 19:20:32 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8208_632565567.dbf
ORA-00280: change 65115833 for thread 1 is in sequence #8208
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8207_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 65115833 generated at 01/22/2008 19:20:32 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8208_632565567.dbf
ORA-00280: change 65115833 for thread 1 is in sequence #8208
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65122618 generated at 01/22/2008 19:35:37 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8209_632565567.dbf
ORA-00280: change 65122618 for thread 1 is in sequence #8209
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8208_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65129304 generated at 01/22/2008 19:50:35 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8210_632565567.dbf
ORA-00280: change 65129304 for thread 1 is in sequence #8210
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8209_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cn
ORA-00308: cannot open archived log 'cn'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection force

Is it possible to restore a datafile after opening the db using resetlogs?

Hi Experts,
We have cloned the db and after opening the db with resetlog option we came to know that one of the user db file is not part of the db and is showing the below error while checking the status and attempting to online it. When checking the size and availability of the dbfile it shows everything without errors.
SQL> alter database datafile 50 online;
alter database datafile 50 online
ERROR at line 1:
ORA-01122: database file 50 failed verification check
ORA-01110: data file 50:
'+DATA/orcl/orcldata.291.730828357.dbf'
ORA-01251: Unknown File Header Version read for file number 50
Thanks,
Newbie

user7490278 wrote:
Hi Experts,
We have cloned the db and after opening the db with resetlog option we came to know that one of the user db file is not part of the db and is showing the below error while checking the status and attempting to online it. When checking the size and availability of the dbfile it shows everything without errors.
SQL> alter database datafile 50 online;
alter database datafile 50 online
ERROR at line 1:
ORA-01122: database file 50 failed verification check
ORA-01110: data file 50:
'+DATA/orcl/orcldata.291.730828357.dbf'
ORA-01251: Unknown File Header Version read for file number 50
Thanks,
NewbieI suggest you review what was done, determine where the mistake was made,
then clone the DB again; but this time don't make any mistakes.

Getting ora-01113 error while opening Database after recovery

HI all,
we have a test database. I lost my entire database including DBFs, controlfiles, Archived logs, redo log files.
But I have a hot backup copy of the lost database.
I tried to recover database using backup copy
I restored my control files and all dbfs and then when i tried to recover database I got the following message
RMAN-00571: ==============================
RMAN-00569: =ERROR MESSAGE STACK FOLLOWS =
RMAN-00571: ===============================
RMAN-03002: failure of recover command at 04/01/2005 14:14:43
RMAN-06054: media recovery requesting unknown log: thread 1 scn 32230460
still i tried to open database resetlogs but i got following eror
RMAN> alter database open resetlogs:
ORA-01113: file 5 needs media recovery
ORA-01110: data file 5: C:\DB11\ORADATA\DB11\system01.dbf
I dont have any redo logs and archivelogs. Can anyone help me how to open the database
thanks and regards
VENKAT

no there is no other way allowresetlogs_corruption is one of the last resort unless oracle dont recommend,usually you got this error when restored datafile is far behind then others datafile CKPT SCN+COntrolfile CKPT SCN header.
SQL> select controlfile_change#,checkpoint_change#
2    from v$database
3 /
CONTROLFILE_CHANGE# CHECKPOINT_CHANGE#
             675632             675775
SQL> select substr(name,1,51) fname,checkpoint_change#
2    from v$datafile_header
3 /
FNAME                                               CHECKPOINT_CHANGE#
F:\ORACLE\PRODUCT\10.1.0\ORADATA\PROD\SYSTEM01.DBF              675775
F:\ORACLE\PRODUCT\10.1.0\ORADATA\PROD\UNDOTBS01.DBF             675775
F:\ORACLE\PRODUCT\10.1.0\ORADATA\PROD\SYSAUX01.DBF              675775
F:\ORACLE\PRODUCT\10.1.0\ORADATA\PROD\USERS01.DBF               675775
F:\ORACLE\PRODUCT\10.1.0\ORADATA\PROD\USERS02.DBF[b]               675418user02.dbf CKPT SCN header 675418 is earlier/oldest CKPT SCN header to others datafile as well to controilfile CKPT SCN header.
You will have to apply enough redo to that datafile either from archivelog or from online redo log file,if you cant then no way you can open the database except using allowresetlogs_corruption with the oracle recommendation.
Think why archivelog backup ,database backup and online redo log file, controlfile redundency is recommended.
Khurram

Newbie ? - Error Opening Database After Recovery

Hi All-
I'm new to Oracle and am using 9i - I'm working on cloning our Production db for a Test db.
I shutdown the Production db and copied all the files from that db into my Test db - I then started my Test db and recovered it. I am now trying to OPEN it, but am getting an error. I am hoping that someone out there with a little more experience and knowledge can help me with this issue.
Here is what I've done and the error that I'm getting:
SQL> @/ubc/test/clone.sql
ORACLE instance started.
Total System Global Area 1502242576 bytes
Fixed Size 743184 bytes
Variable Size 452984832 bytes
Database Buffers 1048207360 bytes
Redo Buffers 307200 bytes
Control file created.
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 1411222426 generated at 05/01/2007 18:31:02 needed for thread
1
ORA-00289: suggestion : /ubc/oracle/OraHome1/dbs/arch1_61111.dbf
ORA-00280: change 1411222426 for thread 1 is in sequence #61111
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/ubc/test/redo/redo03.log
Log applied.
Media recovery complete.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
SQL>
Then, when I go to my '.trc' file to see the error, the following is in there:
/ubc/oracle/dprtest/dumps/udump/dprtest_ora_1179688.trc
Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
ORACLE_HOME = /ubc/oracle/OraHome1
System name:     AIX
Node name:     p650
Release:     2
Version:     5
Machine:     0001875A4C00
Instance name: dprtest
Redo thread mounted by this instance: 1
Oracle process number: 12
Unix process pid: 1179688, image: oracle@p650 (TNS V1-V3)
*** SESSION ID:(9.1) 2007-05-02 08:31:05.436
Start recovery at thread 1 ckpt scn 1411222426 logseq 61111 block 188745
*** 2007-05-02 08:31:20.370
Media Recovery Log /ubc/test/redo/redo03.log
File 1 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 2 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 3 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 4 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 5 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 6 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 7 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 8 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 9 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 10 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 11 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 12 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 13 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 14 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 15 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 16 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 17 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 18 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
File 19 (stop scn 1411222427) completed recovery at checkpoint scn 1411222427
*** 2007-05-02 08:31:31.238
ORA-30012: undo tablespace 'UNDOTBS01' does not exist or of wrong type
Any input or thoughts on how to address this issue would be greatly appreciated! Thanks in advance for your time and assistance!!
-JG
Message was edited by:
J.G.

The following is in my init file:
# System Managed Undo and Rollback Segments
undo_management=AUTO
undo_retention=10800
undo_tablespace=UNDOTBS01
And this is my startup script ("clone.sql"):
STARTUP NOMOUNT
CREATE CONTROLFILE SET DATABASE "DPRTEST" RESETLOGS NOARCHIVELOG
-- SET STANDBY TO MAXIMIZE PERFORMANCE
MAXLOGFILES 5
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 1
MAXLOGHISTORY 1588
LOGFILE
GROUP 1 '/ubc/test/redo/redo01.log' SIZE 500M,
GROUP 2 '/ubc/test/redo/redo02.log' SIZE 500M,
GROUP 3 '/ubc/test/redo/redo03.log' SIZE 500M
-- STANDBY LOGFILE
DATAFILE
'/ubc/test/other_sysadmin/xdb01.dbf',
'/ubc/test/other_sysadmin/users01.dbf',
'/ubc/test/other_sysadmin/undotbs01.dbf',
'/ubc/test/other_sysadmin/tools01.dbf',
'/ubc/test/other_sysadmin/system01.dbf',
'/ubc/test/other_sysadmin/odm01.dbf',
'/ubc/test/other_sysadmin/example01.dbf',
'/ubc/test/other_sysadmin/drsys01.dbf',
'/ubc/test/other_sysadmin/cwmlite01.dbf',
'/ubc/test/data/OLTP.dbf',
'/ubc/test/data/STAGING.DBF',
'/ubc/test/indexes/indx01.dbf',
'/ubc/test/indexes/STAGINGINDEX.DBF',
'/ubc/test/indexes/OLTPINDEX.DBF',
'/ubc/test/other_notused/STATSPACK.DBF',
'/ubc/test/other_notused/SPOTLIGHT.DBF',
'/ubc/test/other_notused/DATACAPTUREINDEX.DBF',
'/ubc/test/other_notused/DATACAPTURE.DBF',
'/ubc/test/other_notused/ARCHIVE.DBF'
CHARACTER SET WE8ISO8859P1
HTH
-JG

ORA-01547 :warning recover succeeded but open resetlogs......

Hai All,
In a standby database I put a command
sql> recover standby database
auto
then error comes...
ORA-01547 :warning recover succeeded but open resetlogs......
ora-01152 : file1 was not restored from a sufficiently old bcakup
ora-01110 : datafile 1: d:\sfms\system01.dbf'
when the database open read only .. also this error comes...
How can I resolve....
Shiju

See Note:1070049.6

ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error be

Hi,
I am trying rman duplicate from RAC to NON-RAC and getting below error. Restore is successfull, but while recover i am getting below issue.
I referred tech note RMAN-06102 DURING DUPLICATE OR RESTORE [ID 436637.1]
I have tried until cancel using controlfile;
To Implement solution " I restored controlfie from the backup peice of contrll file" , Any pointers appreciated.
contents of Memory Script:
   set until scn 5968419799614;
   recover
   clone database
    delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 19-FEB-11
starting media recovery
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/u01/oracle/PROD/db/clonedata/system01.dbf'
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 02/19/2011 14:39:27
RMAN-03015: error occurred in stored script Memory Script
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 2 seq 184399 lowscn 5968419794646 found to restore
RMAN-06025: no backup of log thread 2 seq 184398 lowscn 5968419759510 found to restore
RMAN-06025: no backup of log thread 2 seq 184397 lowscn 5968419736368 found to restore
RMAN-06025: no backup of log thread 2 seq 184396 lowscn 5968419726043 found to restore
RMAN-06025: no backup of log thread 2 seq 184395 lowscn 5968419705565 found to restore
RMAN-06025: no backup of log thread 2 seq 184394 lowscn 5968419678283 found to restore
RMAN-06025: no backup of log thread 2 seq 184393 lowscn 5968419665940 found to restore
RMAN-06025: no backup of log thread 2 seq 184392 lowscn 5968419647797 found to restore
RMAN-06025: no backup of log thread 2 seq 184391 lowscn 5968419630414 found to restore
RMAN-06025: no backup of log thread 2 seq 184390 lowscn 5968419626580 found to restore
RMAN-06025: no backup of log thread 2 seq 184389 lowscn 5968419593858 found to restore
RMAN-06025: no backup of log thread 2 seq 184388 lowscn 5968419527543 found to restore
RMAN-06025: no backup of log thread 2 seq 184387 lowscn 5968419501163 found to restore
RMAN-06025: no backup of log thread 2 seq 184386 lowscn 5968419485951 found to restore
RMAN-06025: no backup of log thread 2 seq 184385 lowscn 5968419469937 found to restore
RMAN-06025: no backup of log thread 2 seq 184384 lowscn 5968419440393 found to restore
RMAN-06025: no backup of log thread 2 seq 184383 lowscn 5968419422292 found to restore
RMAN-06025: no backup of log thread 2 seq 184382 lowscn 5968419397028 found to restore
RMAN-06025: no backup of log thread 2 seq 184381 lowscn 5968419366574 found to restore
RMAN-06025: no backup of log thread 2 seq 184380 lowscn 5968419352992 found to restore
RMAN-06025: no backup of log thread 2 seq 184379 lowscn 5968419338522 found to restore
RMAN-06025: no backup of log thread 2 seq 184378 lowscn 5968419326774 found to restore
RMAN-06025: no backup of log thread 2 seq 184377 lowscn 5968419313956 found to restore
RMAN-06025: no backup of log thread 2 seq 184376 lowscn 5968419300847 found to restore
RMAN-06025: no backup of log thread 2 seq 184375 lowscn 5968419282136 found to restore
RMAN-06025: no backup of log thread 2 seq 184374 lowscn 5968419265656 found to restore
RMAN-06025: no backup of log thread 2 seq 184373 lowscn 5968419254578 found to restore
RMAN-06025: no backup of log thread 2 seq 184372 lowscn 5968419229337 found to restore
RMAN-06025: no backup of log thread 2 seq 184371 lowscn 5968419218373 found to restore
RMAN-06025: no backup of log thread 2 seq 184370 lowscn 5968419178539 found to restore
RMAN-06025: no backup of log thread 2 seq 184369 lowscn 5968419167027 found to restore
RMAN-06025: no backup of log thread 2 seq 184368 lowscn 5968419143802 found to restore
RMAN-06025: no backup of log thread 2 seq 184367 lowscn 5968419139461 found to restore
RMAN-06025: no backup of log thread 2 seq 184366 lowscn 5968419133683 found to restore
RMAN-06025: no backup of log thread 2 seq 184365 lowscn 5968419099514 found to restore
RMAN-06025: no backup of log thread 2 seq 184364 lowscn 5968419094146 found to restore
RMAN-06025: no backup of log thread 2 seq 184363 lowscn 5968419072193 found to restore
RMAN-06025: no backup of log thread 2 seq 184362 lowscn 5968419055733 found to restore
RMAN-06025: no backup of log thread 2 seq 184361 lowscn 5968419047459 found to restore
RMAN-06025: no backup of log thread 2 seq 184360 lowscn 5968419005913 found to restore
RMAN-06025: no backup of log thread 2 seq 184359 lowscn 5968419001578 found to restore
RMAN-06025: no backup of log thread 2 seq 184358 lowscn 5968418983975 found to restore
RMAN-06025: no backup of log thread 2 seq 184357 lowscn 5968418950115 found to restore
RMAN-06025: no backup of log thread 2 seq 184356 lowscn 5968418945661 found to restore
RMAN-06025: no backup of log thread 2 seq 184355 lowscn 5968418909994 found to restore
RMAN-06025: no backup of log thread 2 seq 184354 lowscn 5968418891366 found to restore
RMAN-06025: no backup of log thread 2 seq 184353 lowscn 5968418884733 found to restore
RMAN-06025: no backup of log thread 1 seq 217710 lowscn 5968419793223 found to restore
RMAN-06025: no backup of log thread 1 seq 217709 lowscn 5968419779424 found to restore
RMAN-06025: no backup of log thread 1 seq 217708 lowscn 5968419776035 found to restore
RMAN-06025: no backup of log thread 1 seq 217707 lowscn 5968419775408 found to restore
RMAN-06025: no backup of log thread 1 seq 217706 lowscn 5968419774817 found to restore
MAN-06025: no backup of log thread 1 seq 217705 lowscn 5968419758
RMAN>thanks in advance.

Hello,
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistentFrom the error ORA-01547 and ORA-01194 you got, it seems that the Database is still inconsistent and, you have to apply more Archived logs .
Then, you have the following error:
RMAN-06053: unable to perform media recovery because of missing logWhich says that some logs are missing. The error messages RMAN-06025 below give you the list of missing logs:
RMAN-06025: no backup of log thread 2 seq 184399 lowscn 5968419794646 found to restore
...Are you sure to have a Backup of all the needed Archived logs ?
You may execute this statement to check the contents of the RMAN Backup:
list backup of archivelog all;Hope this help.
Best regards,
Jean-Valentin

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 after opening in Resetlog

Similar Messages

Maybe you are looking for