Resetlogs vs no resetlogs

Hi All,
DB: 10g
OS: windows
I am in a situation, i have a old controlfile trace and the latest controlfile is lost. The old controlfile doesnt have the new datafile entries.So i am mounting the database with the old trace with resetlog option and then i will be renaming the unamed datafiles. What i want to know here is why do i have to use
ALTER DATABASE OPEN RESETLOGS;as i have already specified the reset logs option in the creation of controlfile.
I am confused as in when to use the Reset log and the No reset logs option.
Kindly clarify the same.
BR
Sphinx

I am confused as in when to use the Reset log and the No reset logs option."An OPEN RESETLOGS operation is required after incomplete recovery or recovery with a backup control file."
http://docs.oracle.com/cd/B19306_01/backup.102/b14192/glossary.htm#sthref920
So,
1.Incomplete recovery
2.loss of active/current online redo logs
3.backup control file
4.rename the database
5.Flashback database (not just other options of flashback)
requires resetlogs.
1. Noresetlog is for manual recovery with cancel option used at the time of archive log apply.
2. Oracle uses noresetlogs when your database crashed and all files are available - this is automatic recover. You can also use noresetlogs when you restore a database using a backup controlfile from trace and all datafiles including online redologs are valid and the DB was shutdown properly (rare case).
Dude @ Re: resetlogs Vs noresetlogs
Truly speaking, I too was not known that when to use resetlog or noresetlog, i just searched in this forum ("why resetlog") and now this doubt too has removed for me.
Regards
Girish Sharma

Similar Messages

ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

Hello,
Yesterday i did a clean install of XE on my Windows 7 64bit laptop. The installation went well. Today when i tried to connect to the database i got ORA-01033 initialization or shutdown in progress.
So i started sqlplus as sysdba and executed
SQL> shutdown abort
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 1071333376 bytes
Fixed Size 1388352 bytes
Variable Size 620757184 bytes
Database Buffers 444596224 bytes
Redo Buffers 4591616 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
The alert log is showing the following output
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =19
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production.
Using parameter settings in server-side pfile C:\ORACLE\APP\ORACLE\PRODUCT\11.2.0\SERVER\DATABASE\INITXE.ORA
System parameters with non-default values:
sessions = 176
spfile = "C:\ORACLE\APP\ORACLE\PRODUCT\11.2.0\SERVER\DBS\SPFILEXE.ORA"
memory_target = 1G
control_files = "C:\ORACLE\APP\ORACLE\ORADATA\XE\CONTROL.DBF"
compatible = "11.2.0.0.0"
db_recovery_file_dest = "C:\oracle\app\oracle\fast_recovery_area"
db_recovery_file_dest_size= 10G
undo_management = "AUTO"
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
dispatchers = "(PROTOCOL=TCP) (SERVICE=XEXDB)"
shared_servers = 4
job_queue_processes = 4
audit_file_dest = "C:\ORACLE\APP\ORACLE\ADMIN\XE\ADUMP"
db_name = "XE"
open_cursors = 300
diagnostic_dest = "C:\ORACLE\APP\ORACLE"
Wed Sep 07 09:26:50 2011
PMON started with pid=2, OS id=4936
Wed Sep 07 09:26:50 2011
PSP0 started with pid=3, OS id=4756
OER 7451 in Load Indicator : Error Code = OSD-04500: illegal option specified !
Wed Sep 07 09:26:51 2011
VKTM started with pid=4, OS id=5772 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Wed Sep 07 09:26:51 2011
GEN0 started with pid=5, OS id=5424
Wed Sep 07 09:26:51 2011
DIAG started with pid=6, OS id=5928
Wed Sep 07 09:26:51 2011
DBRM started with pid=7, OS id=4000
Wed Sep 07 09:26:51 2011
DIA0 started with pid=8, OS id=3876
Wed Sep 07 09:26:51 2011
MMAN started with pid=9, OS id=6004
Wed Sep 07 09:26:51 2011
DBW0 started with pid=10, OS id=5252
Wed Sep 07 09:26:51 2011
LGWR started with pid=11, OS id=848
Wed Sep 07 09:26:51 2011
CKPT started with pid=12, OS id=2420
Wed Sep 07 09:26:51 2011
SMON started with pid=13, OS id=2424
Wed Sep 07 09:26:51 2011
RECO started with pid=14, OS id=2396
Wed Sep 07 09:26:51 2011
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Wed Sep 07 09:26:51 2011
MMON started with pid=15, OS id=2388
starting up 4 shared server(s) ...
ORACLE_BASE from environment = C:\oracle\app\oracle
Wed Sep 07 09:26:51 2011
ALTER DATABASE MOUNT
Wed Sep 07 09:26:51 2011
MMNL started with pid=16, OS id=1288
Successful mount of redo thread 1, with mount id 2642331547
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Wed Sep 07 09:26:56 2011
ALTER DATABASE OPEN
Errors in file C:\ORACLE\APP\ORACLE\diag\rdbms\xe\xe\trace\xe_ora_2212.trc:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
ORA-1589 signalled during: ALTER DATABASE OPEN...
Wed Sep 07 09:41:54 2011
db_recovery_file_dest_size of 10240 MB is 0.98% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Can anybody tell me what to do to solve this problem?
Kind Regards,
D.

DennisV wrote:
Starting ORACLE instance (normal)What do you have in the alert.log above that line?
OER 7451 in Load Indicator : Error Code = OSD-04500: illegal option specified !This is one of the symptoms reported earlier when running on unsupported platform (x64) and maybe there's some connection with your issue.
See {thread:id=2278170}.
Errors in file C:\ORACLE\APP\ORACLE\diag\rdbms\xe\xe\trace\xe_ora_2212.trc:What errors does trace file reveal?

Open resetlogs is not working when creating clone db with online backup

Hi All,
I am trying to create a clone database using hot backup of a database .
STEPS THAT I FOLLOWED
LET ----- >CURRENT_DB NAME=DEV
CLONE DATABASE NAME=DEVCLONE
steps PERFORMED FORM DEV DB
- put the database in backup mode using 'alter database begin backup'
- copy all the data files to a different folder
- during copy i have performed some operations on the DB (creating users, tables, dmls etc...)
- in between copying i also performed log switch
- after completion of copy , "alter database end backup"
- created a backup control file in a human readable format (alter database backup controlfile to trace as ........)
steps performed for clone DB side ((DEVCLONE)
- created a parameter file for the database .
- modified the backup control file so that it will point to the location of copied destination of datafiles
- set the ORACLE_SID
- then 'sqlplus / as sysdba
- starup nomount
- run the modified control file ( created a control file for the clone database)
- recover the database using "recover database using backup controlfile"
I have provided the archive files that it was asking for (archive logs that has been generated in DEV DB)
then i canceled the recovery by typing "cancel"
- recover database using backup controlfile until cancel;
then typed "cancel"
- then try to open the database with open resetlogs but it showed below error
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: 'D:\DATA_GUARD\DEVHOT\SYSTEM01.DBF'
please help me on this ......
Thanks

Thanks , now i am able to open the DB in open reset logs mode .
Previously , when i had not taken the archive log after "alter database end backup" , i was not able to open the db with open resetlogs because the
fuzzy status of all the datafile headers were YES .
But after taking the archive log that got generated after "alter database end backup" and applying it on the clone db(Created with HOT backup ) the datafile_header status got changed from YES to NO .
So for that i am able to open the clone db with open resetlogs .
Can you please help me with a small description why this is happening ?
Thanks.......

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

Regarding RESETLOG and NORESETLOG option while creating a control file

Hi,
I dont understand the need for resetlogs option while creating a controlfile for a db in NOARCHIVELOGMODE. I assume that reset logs clears all the redo log contents.
While taking a cold backup what I did was:
1. Shutdown instance
2. Copy all the files
3. Startup
Now I tried recovering the same database on a new machine (with different path btw.) coz of which i had to create a new control file. My question is: while restoring the database, do I need to create the control file with NORESETLOG or RESETLOG option?
When I tried using the NORESETLOG (NOARCHIVELOG) option I was able to recover the instance without any hassles.
ie
1. STARTUP NOMOUNT
2. CREATE NEW CONTROL FILE USING NORESETLOG (NOARCHIVELOG)
3. RECOVER DATABASE
4. ALTER DATABASE OPEN;
While the same thing with NORESETLOG (NOARCHIVELOG) option:
1. STARTUP NOMOUNT
2. CREATE NEW CONTROL FILE USING RESETLOG (NOARCHIVELOG)
3. RECOVER DATABASE USING BACKUP CONTROLFILE
This step asked me for some archivelogs which were not generated since the db is in NOARCHIVELOG mode.
I wonder why we require the RESETLOG OPTION SINCE A NORMAL SHUTDOWN PERFORMED BEFORE COLD BACKUP would have ensured that there is no redo information left in the redo logs.
Please let me know if I am thinking the incorrect way.
Regards and Thanx in Advance,
Raj

If you had a db running in noarchivelog mode and had to clone the db and rename it, the create controlfile stmt:
create controlfile reuse <db_name> needs to be changed to: create controlfile SET <db_name>, in which case the db can only be opened with resetlogs. Hope this answers your question

Error during restore/recovery and 'open resetlogs'

Hello forum. I'm attempting to restore a database to a new host and have run into an error during the opening of the database (with resetlogs). The renaming of the datafiles, restore, switching of datafiles, and recovery are all done by an rman script, the contents of which are below:
# Restore production database to DR site using file system
# instead of ASM
run {
set newname for datafile 1 to '/opt/oracle/product/10gR2/oradata/DB01/system.dbf';
set newname for datafile 2 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf';
set newname for datafile 3 to '/opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf';
set newname for datafile 4 to '/opt/oracle/product/10gR2/oradata/DB01/users.dbf';
set newname for datafile 5 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf';
set newname for datafile 6 to '/opt/oracle/product/10gR2/oradata/DB01/file1.dbf';
set newname for datafile 7 to '/opt/oracle/product/10gR2/oradata/DB01/file2.dbf';
restore database;
switch datafile all;
recover database;
I get the following output:
RMAN> @/home/oracle/scripts/rman_dr.rman
RMAN> # Restore production database to DR site using file system
2> # instead of ASM
3> #
4> run {
5> set newname for datafile 1 to '/opt/oracle/product/10gR2/oradata/DB01/system.dbf';
6> set newname for datafile 2 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf';
7> set newname for datafile 3 to '/opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf';
8> set newname for datafile 4 to '/opt/oracle/product/10gR2/oradata/DB01/users.dbf';
9> set newname for datafile 5 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf';
10> set newname for datafile 6 to '/opt/oracle/product/10gR2/oradata/DB01/file1.dbf';
11> set newname for datafile 7 to '/opt/oracle/product/10gR2/oradata/DB01/file2.dbf';
12>
13> restore database;
14> switch datafile all;
15> recover database;
16> }
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 03-JAN-08
Starting implicit crosscheck backup at 03-JAN-08
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 651 objects
Finished implicit crosscheck backup at 03-JAN-08
Starting implicit crosscheck copy at 03-JAN-08
using channel ORA_DISK_1
Crosschecked 1 objects
Finished implicit crosscheck copy at 03-JAN-08
searching for all files in the recovery area
cataloging files...
no files cataloged
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/product/10gR2/oradata/DB01/system.dbf
restoring datafile 00002 to /opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf
restoring datafile 00003 to /opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf
restoring datafile 00004 to /opt/oracle/product/10gR2/oradata/DB01/users.dbf
restoring datafile 00005 to /opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf
restoring datafile 00006 to /opt/oracle/product/10gR2/oradata/DB01/file1.dbf
restoring datafile 00007 to /opt/oracle/product/10gR2/oradata/DB01/file2.dbfchannel ORA_DISK_1: reading from backup piece /ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642899284.1.1.bus
channel ORA_DISK_1: restored backup piece 1
piece handle=/ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642899284.1.1.bus tag=20080101_LV0_DB
channel ORA_DISK_1: restore complete, elapsed time: 01:22:28
Finished restore at 03-JAN-08
datafile 1 switched to datafile copy
input datafile copy recid=14 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/system.dbf
datafile 2 switched to datafile copy
input datafile copy recid=15 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf
datafile 3 switched to datafile copy
input datafile copy recid=16 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf
datafile 4 switched to datafile copy
input datafile copy recid=17 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/users.dbf
datafile 5 switched to datafile copy
input datafile copy recid=18 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf
datafile 6 switched to datafile copy
input datafile copy recid=19 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/file1.dbf
datafile 7 switched to datafile copy
input datafile copy recid=20 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/file2.dbf
Starting recover at 03-JAN-08
using channel ORA_DISK_1
starting media recovery
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=2 sequence=1005
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=1365
channel ORA_DISK_1: reading from backup piece /ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642900444.1.1.bus
channel ORA_DISK_1: restored backup piece 1
piece handle=/ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642900444.1.1.bus tag=20080101_LV0_DB
channel ORA_DISK_1: restore complete, elapsed time: 00:00:05
archive log filename=/opt/oracle/product/10gR2/db/flash_recovery_area/DB01/archivelog/2008_01_03/o1_mf_1_1365_3qtshnfv_.arc thread=1 sequence=1365
archive log filename=/opt/oracle/product/10gR2/db/flash_recovery_area/DB01/archivelog/2008_01_03/o1_mf_2_1005_3qtshncz_.arc thread=2 sequence=1005
channel default: deleting archive log(s)
archive log filename=/opt/oracle/product/10gR2/db/flash_recovery_area/DB01/archivelog/2008_01_03/o1_mf_1_1365_3qtshnfv_.arc recid=2418 stamp=643049236
unable to find archive log
archive log thread=1 sequence=1366
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/03/2008 16:47:22
RMAN-06054: media recovery requesting unknown log: thread 1 seq 1366 lowscn 181804603
RMAN> **end-of-file**
I searched for a decription of the 06054 error, and found that if the archive logs weren't available, then to run "alter database open resetlogs;", which I did. Here's the output:
RMAN> alter database open resetlogs;
database opened
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
ORACLE error from target database:
ORA-06553: PLS-801: internal error [56319]
I've done all of this twice now, with the same result. I've googled PLS-801 and found more than a few instances of people getting this code, but not during a database open after a restore. Can anyone shed some light on what might have gone wrong? In the interest of brevity, I left out the rest of the restore process prior to running the database restore, but other than setting "compatible" and "db_recovery_file_dest_size", it was all by the book.
Thanks in advance.

Thanks for the reply Pierre.
I am not using RMAN Duplicate. Yes, the source of the backup is an RAC. The destination is a single server, with the DB on the filesystem. Here's an overview of of the commands I ran and the procedure.
Copied tar'd backup controlfile and datafiles to destination machine. Untar'd. Install 10.2.0.1.0 on destination machine, patch to 10.2.0.2.0.
OS> sqlplus /nologin
SQL> alter system set compatible = '10.2.0.2.0' scope=spfile;
SQL> alter system set db_recovery_dest_file_size = '8g'; scope spfile;
SQL> shutdown immediate;
SQL> startup; (to verify changes took...)
SQL> shutdown immediate;
OS> Copy control file from untar'd dir and place in $ORACLE_HOME/dbs/, truncate name to c-DBID-date-00.
OS> rman target /
RMAN> startup nomount;
RMAN> set dbid <dbid from control file>;
RMAN> restore controlfile from autobackup; (finds control file with no problem...)
RMAN> alter database mount;
RMAN> @/home/oracle/rman_dr.rman (script cited in first post, to rename datafiles from ASM to filesystem, restore, switch files, and recover...)
RMAN> alter database open resetlogs; (as cited before...)
If I'm not using Duplicate and not specifying dates, the UNTIL/SET UNTIL commands aren't necessary, correct?

Need of resetlogs in recovery from controlfile backup...

Hi,
Suppose we are recovering with controlfile backup, we have all archivelogs and online redologs.
After restoring the controlfile and recovering the database why there is need of *"open with resetlogs"*, because when we have all archivelogs and redologs the DB should recover to the point of failure.
Plz help and clarify.
Ashutosh.

Suppose we are recovering with controlfile backup, we have all archivelogs and online redologs.
After restoring the controlfile and recovering the database why there is need of "open with resetlogs", because when we have all archivelogs and redologs the DB should recover to the point of failure.My understanding is when we were performing incomplete recovery we need to open with resetlogs is it true or not.. Can you please correct if I'm wrong.
http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10770/rcmsynta7a.htm
Thanks in advance for spending your valuable time. :)

ORA-27101: shared memory realm does not exist and ORA-01139: RESETLOGS

HI ALL,
After the oracle has installed on a solaries server successfully, i am unable to login into oracle database.
Below are the errors messages :
1) ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory
2) Media recovery complete.
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery.
and When i try to login into oracle as root .
this is the error :
sqlplus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Fri Feb 12 15:52:49 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
ld.so.1: oracle: fatal: libskgxp10.so: open failed: No such file or directory
ERROR:
ORA-12547: TNS:lost contact
my Operating system details :
SunOS Blade3-Chassis2 5.10 Generic_142900-03 sun4v sparc SUNW,Netra-CP3060
Anyone please help me here. waiting for your reply.
Below are the ORACLE_SID Details :
1) echo $ORACLE_SID ----- > ems
2)ps -eaf | grep smon -------> ora_smon_ems
do you need any data?
Edited by: user8959150 on Feb 11, 2010 7:19 PM

Hi
We mostly receive this error message ( ORA-27101: shared memory realm does not exist and ORA-01139)
When our SGA_MAX_SIZE is greater than 1.7 G.b on
You again configure your sga size
and sga_max_size paramete will not greater than 1.7 G.b
Hope your database will work correctly.
for test purpose you set all your init.ora parameter
db_cache_size=512m
db_keep_cache_size=64m
db_recycle_cache_size=16m
java_pool_size=8m
large_pool_size=16m
shared_pool_size=256m
shared_pool_reserved_size=64m
sga_max_size=1600m
sga_max_size will not be grater than combination of of db_cache_size db_keep_cache_size,db_recycle_cache_sizejava_pool_size+share_pool_size+share_pool_reserved_size
Hope it will work fine.
Regard
Abdul Hameed Malik
[email protected]

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.

View to check We Can Open Database with Resetlog Option

Hi Experts,
i need to know the view name that can tell us we can open the database in resetlog option during recovery process.
regards,
rizwan

Hi Rizwan;
i need to know the view name that can tell us we can open the database in resetlog option during recovery process.What is DB version?
Pelase check below link:
Troubleshooting Backups - V$ Recovery Views
http://www.toadworld.com/KNOWLEDGE/KnowledgeXpertforOracle/tabid/648/TopicID/TBT3/Default.aspx
Regard
Helios

'alter database open resetlogs' didn't reset one of the datafiles

I've spent the last three and a half weeks recovering an oracle database (11g 64-bit linux) because of a corrupt block in an online redo log (which I thought was being written to multiple locations). I restored the files, moving some of them around in the process; recovered to the latest possible point; moved files back to their proper location; ran 'alter database open resetlogs'; and one of the datafiles (from a bigfile tablespace) didn't get reset. I checked afterward, and it was marked offline. I do not remember placing the file offline, and cannot find such a statement in my last 300 sqlplus commands, which includes commands well before I renamed this file and the commands surrounding the rename.
Restoring/recovering the database again will take too long, and is a remarkably poor option. Even if the database had opened correctly, the affected tablespace would not have been touched in the two or three minutes the database was open. Is there any way to force oracle to reset the logs again or otherwise fix this one file to mark it with the same date? Only allowing the resetlogs option after an incomplete recovery seems a poor restriction, especially, if files can slip through like this. I'm suspecting there is someway to just fix the checkpoint values for the tablespace, but I don't know where to begin. This particular file is <5% of the database, so if I have to do some sort of backup/restore with just it, that is probably doable.

0: 11.1.0.6.0 on SUSE Linux Enterprise Server 10 SP2
1: rman
backup format '/opt/oracle/backup/mydatabase_%Y-%M-%D_%s_datafiles_%p' (database);
backup format '/opt/oracle/backup/mydatabase_%Y-%M-%D_%s_archivelogs_%p' archivelog all delete input;
backup format '/opt/oracle/backup/mydatabase_%Y-%M-%D_%s_control_%p' current controlfile spfile;
2:
restore database; --not sure what datafiles were restored with this
restore datafile X; --several files were restored individually
recover database until scn 1137554504; -- I verified that all datafiles were on the same checkpoint after this finished. Not having placed any files offline, I didn't bother checking that.
3:
SQL> alter database open resetlogs;
Database altered.
Elapsed: 00:04:20.34
SQL> quit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
4: Nothing in the tablespace has been touched since I ran 'alter database open resetlogs;'. It also appears that oracle placed the file offline (without me telling it to do so) and left it that way through the resetlogs, leaving the tablespace unusable during the time it was opened. The only things that would be out of date are the 'RESETLOGS_CHANGE#', the 'CHECKPOINT_CHANGE#', and associated values. It's still at the last scn before the resetlogs, and the system has been in archivelog mode the entire time. This is all information that Oracle could be tracking, and from a program logic standpoint there is no reason why Oracle cannot tie together the changes before the resetlogs, the resetlogs command and the changes after the resetlogs into a new, continuous string of changes. I assume there is some such feature in a high-caliber program because I'm actually a programmer (who would have included such advanced tracking features), and I've become a DBA out of necessity. I admit to not knowing all of the oracle DBA commands, hence me posting here before doing the work of submitting a request to metalink.
5: I consider it a poor restriction because it doesn't always reset the logs on all files, and as far as my knowledge goes it has rendered my 3.5 week recovery process WORTHLESS. I suppose it could cause numerous errors, especially if the database wasn't cleanly shut down, but having the ability to do something equivalent to datafiles that oracle skipped the process on seems quite useful in my situation. I guess the more fundamental problem to complain about is that it would apply such changes to only some of the files, while leaving others unusable, instead of just giving me an error that some files weren't going to be reset, but I think I'm done venting my Oracle frustrations for now.
Am I stuck with a tablespace that I cannot bring online with the database open, or is there some sort of 'alter database datafile' command (or anything else) that I know nothing of that will fix the straggling file?
Edited by: jbo5112 on Oct 5, 2009 3:33 PM -- obfuscated some file names to secure identity.

Queries on DATABASE OPEN RESETLOGS and lost Control Files

Hi I have some queries on RESETLOGS I would be keen to hear some answers on
Q1. If I am doing a PITR and I end in ALTER DATABASE OPEN RESETLOGS, what happens about any Archived Redo Log files ( still in situ ) that were from the original source database but were at a future point in time ? Are they just ignored by any future restore ( since their log sequence number will be different ? ) and eventually over written or purged out ?
Q2. When you create a new incarnation using RESETLOGS can you Flashback Database to before this ?
Q3. If I have lost all my Control Files and have not created a backup control file or done a backup to trace of the control file, can I simply restore one of the actual control files from my last backup and use RECOVER DATABASE USING BACKUP CONTROLFILE AUTO; or will this only work with a bonafide backup control file ( i.e. one created via ALTER DATABASE BACKUP CONTROLFILE TO ‘<file spec>’; )
Q4. When I issue RECOVER DATABASE USING BACKUP CONTROLFILE AUTO;
Do I have to ALTER DATABASE OPEN RESETLOGS at the end of the recovery ? I have seen this documented but I am not sure why I would need to reset the redo logs and instead simply open the database ?
Q5. If I am running the CREATE CONTROL FILE command from an ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
Do I need to use the NORESETLOGS or RESETLOGS ? How do I know which to use ?
thanks,
Jim

Jimbo wrote:
Hi I have some queries on RESETLOGS I would be keen to hear some answers on
Q1. If I am doing a PITR and I end in ALTER DATABASE OPEN RESETLOGS, what happens about any Archived Redo Log files ( still in situ ) that were from the original source database but were at a future point in time ? Are they just ignored by any future restore ( since their log sequence number will be different ? ) and eventually over written or purged out ?
what happens when you try it?
Q2. When you create a new incarnation using RESETLOGS can you Flashback Database to before this ?
what happens when you try it?
Q3. If I have lost all my Control Files and have not created a backup control file or done a backup to trace of the control file, can I simply restore one of the actual control files from my last backup and use RECOVER DATABASE USING BACKUP CONTROLFILE AUTO; or will this only work with a bonafide backup control file ( i.e. one created via ALTER DATABASE BACKUP CONTROLFILE TO ‘<file spec>’; )
what happens when you try it?
Q4. When I issue RECOVER DATABASE USING BACKUP CONTROLFILE AUTO;
Do I have to ALTER DATABASE OPEN RESETLOGS at the end of the recovery ? I have seen this documented but I am not sure why I would need to reset the redo logs and instead simply open the database ?
what happens when you try it?
Q5. If I am running the CREATE CONTROL FILE command from an ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
Do I need to use the NORESETLOGS or RESETLOGS ? How do I know which to use ?
what happens when you try it?

Data Guard setup after resetlogs on Primary

Hello,
On our primary database we had to perform an incomplete recovery and afterwards had to perform the command "ALTER DATABASE OPEN RESETLOGS". The problem I have is that after switching the Logical and Physical Standby databases back on they are still looking for archive log number 16133 when the log sequences have been reset back to 1.
The error message in the alert log is ....
ORA-16069: Archive Log standby database activation identifier mismatch
So the question is do I need to re-create my Logical and Physical standby databases or is there another may around this?
Thanks.

It depends on the database version, and the configuration in the databases, if the database version is 9i, it's mandatory to re-create the standby database. If the version is 10g, and the flashback database is used, it is possible that automatically the database continue the redo application.

How to fix RMAN-20207: UNTIL TIME is before RESETLOGS time

Early this morning, in my haste to get a point in time restore and recovery started, I forgot to restore the controlfile as the 1st step.
I used the current database control file, and now I have "RMAN-06004: ORACLE error from recovery catalog database: RMAN-20207: UNTIL TIME is before RESETLOGS time". I have a recovery catalog database. This is Oracle 8.1.7.4.
Here was my script syntax:
export ORACLE_SID=myname
export ORACLE_HOME=/x01/oracle/product/8.1.7
export LOG=/x01/admin/recover/point_in_time_${ORACLE_SID}_${TimeStamp}.log
echo "Starting Time: `date`" > $LOG
/x01/oracle/product/8.1.7/bin/rman <<! | tee -a ${LOG}
set echo on;
connect target
connect catalog myuser/mypass@mycatalog
startup nomount pfile='/x01/admin/myname/pfile/initmyname.ora';
alter database mount;
run {
set until time "to_date('2006-12-02:03:00:00','yyyy-mm-dd:hh24:mi:ss')";
allocate channel t1 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
allocate channel t2 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
restore database;
recover database;
release channel t1;
release channel t2;
Alter Database Open Resetlogs;
sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_01.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 2097217536";
sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_02.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 2097217536";
exit
echo "Finished Time: `date`" >> ${LOG}
Can I do the following to try to restore the controlfile? First, I would shutdown my database.
export ORACLE_SID=myname
export ORACLE_HOME=/x01/oracle/product/8.1.7
export LOG=/x01/admin/rman/recover/db_point_in_time_8i_${ORACLE_SID}_${TimeStamp}.log
echo "Starting Time: `date`" > $LOG
/x01/oracle/product/8.1.7/bin/rman <<! | tee -a ${LOG}
set echo on;
connect target
connect catalog myuser/mypass@mycatalog
startup nomount pfile='/x01/admin/myname/pfile/initmyname.ora';
alter database mount;
run {
set until time "to_date('2006-12-02:03:00:00','yyyy-mm-dd:hh24:mi:ss')";
allocate channel t1 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
allocate channel t2 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
restore controlfile to '/x01/disk/control01.ctl';
replicate controlfile from '/x01/disk/control01.ctl';
recover database;
release channel t1;
release channel t2;
Alter Database Open Resetlogs;
sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_01.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 2097217536";
sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_02.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 2097217536";
exit
echo "Finished Time: `date`" >> ${LOG}
I have a new incarnation of the database too -
List of Database Incarnations
DB Key Inc Key DB Name DB ID CUR Reset SCN Reset Time
1 2 MYNAME 1849293826 NO 1 06-AUG-03
1 25874 MYNAME 1849293826 NO 750748990 26-SEP-03
1 143681 MYNAME 1849293826 NO 6610874669464 12-AUG-05
1 265345 MYNAME 1849293826 YES 6611455777113 14-DEC-06
What is the fastest way to fix this situation without having to restore the entire database?
Thanks,
Message was edited by:
user521040

Here is the "revised" script - I have not run this again on the Production system, but I might get a chance - finding corruption on the disk. I will test out later on a development database:
#!/usr/bin/ksh
TimeStamp=`date +%Y%m%d_%H%M%S`
export ORACLE_SID=myname
export ORACLE_HOME=/x01/oracle/product/8.1.7
export LOG=/x01/admin/rman/recover/8i_${ORACLE_SID}_${TimeStamp}.log
echo "Starting Time: `date`" > $LOG
/x01/oracle/product/8.1.7/bin/rman <<! | tee -a ${LOG}
set echo on;
connect target
connect catalog myuser/mypass@mycat1
startup nomount pfile='/x01/admin/myname/pfile/initmyname.ora';
run {
set until time "to_date('2006-11-25:18:08:00','yyyy-mm-dd:hh24:mi:ss')";
allocate channel t1 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
allocate channel t2 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
allocate channel t3 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
allocate channel t4 type 'SBT_TAPE' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin/tdpo.opt)';
restore controlfile to '/x01/disk/control01.ctl';
replicate controlfile from '/x01/disk/control01.ctl';
alter database mount;
restore database;
recover database;
Alter Database Open Resetlogs;
sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_01.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 20
97217536";
sql "alter tablespace temp01 add tempfile ''/x01/myname/temp1/temp01_02.tmp'' SIZE 5308416 REUSE AUTOEXTEND ON NEXT 5242880 MAXSIZE 20
97217536";
release channel t1;
release channel t2;
release channel t3;
release channel t4;
exit
echo "Finished Time: `date`" >> ${LOG}
Message was edited by:
user521040

When is resetlogs option used in alter database

Hi
Could anybody explain when
alter database open resetlogs
statement is used?
Thanks in advance

[incomplete recovery or recovery with a backup control file|http://download.oracle.com/docs/cd/B10501_01/server.920/a96572/performingreco.htm]

What are all scenarios we will open the database in open resetlog mode

what are all scenarios we will open the database in open resetlog mode..please advise

Another situation I could think of is that when the active/current online redo logs are lost.
Regards,
Jaffar

Resetlogs vs no resetlogs

Similar Messages

Maybe you are looking for