on 07-20-2013 4:31 AM
Hi,
You are not providing enough information to get some help...
I suppose you are building DR system from an online backup + archive log recovery ???
By the way Oracle 10g is not supported any more (except 10.2.0.5 with extra cost...)
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Online backup is supported, for system copy. It is the Oracle version 10.2 that is running out of extended support...
1110995 - Extended maintenance for Oracle Version 10.2
For a new installation or a copy with DB export you should definitely install version 12.2.0.3 on target.
For a copy with backup it is also possible but you'll need to open DB in upgrade mode and apply upgrade scripts.
I guess you already tried a simple "ALTER DATABASE OPEN" ?
I'm sorry i'l not using BRtools for that purpose, have you try a simple "RECOVER DATABASE UNTIL CANCEL"
If all archives are available (and uncompressed) it should run fine, then just issue a "ALTER DATABASE OPEN RESETLOGS" and you're done.
Hi Rosendo,
Please create a new control file for DR system and then copy the redo logs from Production to DR.
Start the database in mount state
SQL> recover database using backup controlfile until cancel;
Type "AUTO" -> This will automatically pick the redo logs from oraarch folder required for recovery
Once the recovery is completed, you may open the database using
SQL> alter database open resetlogs.
Hope this helps.
Regards,
Deepak Kori
Hi Rosendo,
You need to execute the below command on the source system
SQL> Alter database backup controlfile to trace;
Copy the trace file generated on the source system under saptrace folder to target system.
Modify the following points in this trace file
1) SID
2) Path of origlog, mirrlog
3) Path of datafiles ( if required)
4) Change command at startup nomount as
modify reuse -> set
Save this file at /oracle/SID on target server as CONTROL.SQL.
Login to target database
SQL> Startup mount
SQL> @/oracle/SID/CONTROL.SQL
This will generate the required control file on target server.
Hope this helps.
Regards,
Deepak Kori
Hi Rosendo,
pls, have a lock in your oraarch destination (F:\ORACLE\PRD\ORAARCH\PRDARCH\).
for the recovery you need the archivefile with naming convention ARC1_0821709246.001.
Does the names of archivefiles/offl.redologs meet these requirements?
If so, you need more archivefiles for the recovery, so that the db is consistent.
if they doesn't meet these naming convention, you have to adjust the names of the archivefiles.
instead the option RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL u can also try the option RECOVER DATABASE USING BACKUP CONTROLFILE until time 'yyyy-mm-dd:hh:mm:ss' (e.g. RECOVER DATABASE USING BACKUP CONTROLFILE until time '2013-07-26:06:00:00')
I retried your suggestion the "recover databse until cancel" worked but when i retried the "alter database open resetlogs" the oracle instance just got discconected.
Hi Rosendo,
so that is the reseaon for your problem.
simple said:
1. you defined a recovery with option until cancel + auto
--> all offlRedolog / archives in the oraarch-destination are used for the recovery, if they agree with the defined configuration / naming conventions in the pfile/spfile
2. there are no suitable archives --> the recovery is finished
3. the DB determine, if you try to open the DB, that the DB is not consistent --> not all needed transaction / archive are restored
there are a few possible solutions / ways. for example:
- one option is to rename manuell the archives like it is needed or defined in the pfile/spfile an to restared the recovey
- or to modify the configuration in the pfile/spfile for the archive-naming convention
eg.:
*.log_archive_dest --> this is the destination for your archivefiles
*.log_archive_format = %t_%s_%r.dbf --> this is the format/naming convention for archivefiles defined in PFILE (init<SID>.ora) or SPFILE
Hi Reagan,
This is the last line of the alert log
Mon Jul 29 13:39:05 2013
E:\oracle\PRD\102\bin\oradim.exe -startup -sid prd -usrpwd * -log oradim.log -nocheck 0
Mon Jul 29 13:39:27 2013
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
and the version of the oracle in the source system
oracle 10g. 10.2.0.2.0
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.