Home » RDBMS Server » Server Administration » Manual Clone DB
Manual Clone DB [message #256760] Mon, 06 August 2007 09:29 Go to next message
shaseeb
Messages: 113
Registered: April 2007
Location: Madison, WI
Senior Member
HI,

I am running Oracle10R2 on Windows and am required to clone that database to RHEL 4. I have done all the major steps for the clone but I cannot get the database to open. Here are the steps that I have done so far:

- took an offline (cold) backup of the source database - - it was not in Archivelog mode
- moved all the database files, controlfiles, pfile and logfiles to the clone db
- created a controlfile using the CREATE CONTROLFILE SET DATABASE... command which was generated by running the ALTER DATABASE BACKUP CONTROLFILE TO TRACE command on the source database
- then I tried to open the database


SYS@FPRCQA> alter database open resetlogs;
alter database open resetlogs

ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/u01/oradata/FPRCQA/SYSTEM01.DBF'

SYS@FPRCQA> recover database using backup controlfile until cancel;
ORA-00279: change 48879575 generated at 08/05/2007 01:36:47 needed for thread 1
ORA-00289: suggestion : /u05/oradata/FPRCQA/flash_recovery_area/FPRCQA/archivelog/2007_08_05/o1_mf_1_1_%u_.arc
ORA-00280: change 48879575 for thread 1 is in sequence #1

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/u04/oradata/FPRCQA/REDOG8L1_FPRCQA.LOG
Log applied.
Media recovery complete.
SYS@FPRCQA> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
Re: Manual Clone DB [message #256761 is a reply to message #256760] Mon, 06 August 2007 09:35 Go to previous messageGo to next message
BlackSwan
Messages: 25036
Registered: January 2009
Location: SoCal
Senior Member
Most likely the alert_SID.log file contains clues & points to a trace (*trc) file with more clues.

IIRC, similar can occur when Oracle s/w trees are NOT same version out to 4th decimal place.

>took an offline (cold) backup of the source database
If all was done properly, the database should have just been opened & NO recovery should have been necessary.

The cloned DB should have started just like the original DB.
The clone would NOT have known anything different from original DB.

[Updated on: Mon, 06 August 2007 10:23] by Moderator

Report message to a moderator

Re: Manual Clone DB [message #256774 is a reply to message #256760] Mon, 06 August 2007 10:43 Go to previous messageGo to next message
shaseeb
Messages: 113
Registered: April 2007
Location: Madison, WI
Senior Member
I checked the alert log and it said that I need to use the UPGRADE option. So here is what I did:

@> connect sys/ as sysdba
Connected to an idle instance.
SYS@FPRCQA> startup upgrade;
ORACLE instance started.

Total System Global Area 629145600 bytes
Fixed Size 2074856 bytes
Variable Size 406849304 bytes
Database Buffers 213909504 bytes
Redo Buffers 6311936 bytes
Database mounted.
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/u01/oradata/FPRCQA/SYSTEM01.DBF'

SYS@FPRCQA> SELECT member
FROM v$log l, v$logfile f
WHERE l.group# = f.group#
AND l.status = 'CURRENT';
2 3 4
MEMBER
------------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------
/u01/oradata/FPRCQA/REDOG1L1_FPRCQA.LOG
/u02/oradata/FPRCQA/REDOG1L2_FPRCQA.LOG

SYS@FPRCQA> recover database using backup controlfile;
ORA-00279: change 48879588 generated at 08/06/2007 10:28:19 needed for thread 1
ORA-00289: suggestion : /u05/oradata/FPRCQA/flash_recovery_area/FPRCQA/archivelog/2007_08_06/o1_mf_1_2_%u_.arc
ORA-00280: change 48879588 for thread 1 is in sequence #2


Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/u01/oradata/FPRCQA/REDOG1L1_FPRCQA.LOG
Log applied.
Media recovery complete.



Now should I shutdown the database and then open it again with the STARTUP UPGRADE command? I tried it without shutting down and it would give me the same errors. Or if I used the ALTER DATABASE OPEN RESETLOGS then it would say in the alertlog that I need to use the UPGARADE option.

Thanks

Re: Manual Clone DB [message #256775 is a reply to message #256760] Mon, 06 August 2007 10:48 Go to previous messageGo to next message
Mohammad Taj
Messages: 2412
Registered: September 2006
Location: Dubai, UAE
Senior Member

Hi,
it was not in Archivelog mode
Are you sure ?

If yes then go through below link
http://dbataj.blogspot.com/2007/03/shiftoracleserverfromonemachinetoanothe.html

Hope this helps
Taj
Re: Manual Clone DB [message #256780 is a reply to message #256775] Mon, 06 August 2007 11:18 Go to previous messageGo to next message
shaseeb
Messages: 113
Registered: April 2007
Location: Madison, WI
Senior Member
Thanks Taj, but your process is somewhat different and I am actually at the really end. I just can't get the database to open. And yes neither database was in archive log mode. I was actually following this:

http://orafaq.com/howto/clone-db.txt


Re: Manual Clone DB [message #256781 is a reply to message #256760] Mon, 06 August 2007 11:25 Go to previous messageGo to next message
BlackSwan
Messages: 25036
Registered: January 2009
Location: SoCal
Senior Member
IIRC, similar can occur when Oracle s/w trees are NOT same version out to 4th decimal place.
Please use sqlplus on both systems & post their banners here.
Re: Manual Clone DB [message #256782 is a reply to message #256760] Mon, 06 August 2007 11:28 Go to previous messageGo to next message
shaseeb
Messages: 113
Registered: April 2007
Location: Madison, WI
Senior Member
Here is the last part of my alert log:

Mon Aug 6 11:15:30 2007
ALTER DATABASE MOUNT
Mon Aug 6 11:15:34 2007
Setting recovery target incarnation to 7
Mon Aug 6 11:15:34 2007
Successful mount of redo thread 1, with mount id 2032071570
Mon Aug 6 11:15:34 2007
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Mon Aug 6 11:15:34 2007
ALTER DATABASE OPEN MIGRATE
ORA-1589 signalled during: ALTER DATABASE OPEN MIGRATE...
Mon Aug 6 11:15:52 2007
alter database open resetlogs
Mon Aug 6 11:15:52 2007
RESETLOGS after complete recovery through change 48879590
Resetting resetlogs activation ID 2032083008 (0x791f2040)
Online log /u02/oradata/FPRCQA/REDOG2L1_FPRCQA.LOG: Thread 1 Group 2 was previously cleared
Online log /u03/oradata/FPRCQA/REDOG2L2_FPRCQA.LOG: Thread 1 Group 2 was previously cleared
Online log /u03/oradata/FPRCQA/REDOG3L1_FPRCQA.LOG: Thread 1 Group 3 was previously cleared
Online log /u04/oradata/FPRCQA/REDOG3L2_FPRCQA.LOG: Thread 1 Group 3 was previously cleared
Online log /u04/oradata/FPRCQA/REDOG4L1_FPRCQA.LOG: Thread 1 Group 4 was previously cleared
Online log /u01/oradata/FPRCQA/REDOG4L2_FPRCQA.LOG: Thread 1 Group 4 was previously cleared
Online log /u01/oradata/FPRCQA/REDOG5L1_FPRCQA.LOG: Thread 1 Group 5 was previously cleared
Online log /u02/oradata/FPRCQA/REDOG5L2_FPRCQA.LOG: Thread 1 Group 5 was previously cleared
Online log /u02/oradata/FPRCQA/REDOG6L1_FPRCQA.LOG: Thread 1 Group 6 was previously cleared
Online log /u03/oradata/FPRCQA/REDOG6L2_FPRCQA.LOG: Thread 1 Group 6 was previously cleared
Online log /u03/oradata/FPRCQA/REDOG7L1_FPRCQA.LOG: Thread 1 Group 7 was previously cleared
Online log /u04/oradata/FPRCQA/REDOG7L2_FPRCQA.LOG: Thread 1 Group 7 was previously cleared
Mon Aug 6 11:15:57 2007
Setting recovery target incarnation to 8
Mon Aug 6 11:15:58 2007
Assigning activation ID 2032071570 (0x791ef392)
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: /u01/oradata/FPRCQA/REDOG1L1_FPRCQA.LOG
Current log# 1 seq# 1 mem# 1: /u02/oradata/FPRCQA/REDOG1L2_FPRCQA.LOG
Successful open of redo thread 1
Mon Aug 6 11:15:58 2007
MTTR advisory is disabled because either FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is set
Mon Aug 6 11:15:58 2007
SMON: enabling cache recovery
Mon Aug 6 11:15:58 2007
Errors in file /opt/app/oracle/admin/FPRCQA/udump/fprcqa_ora_32519.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Mon Aug 6 11:15:58 2007
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 32519
ORA-1092 signalled during: alter database open resetlogs...


When I use the STARTUP UPGRADE command it tells me:

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

And then when I use the alter database open resetlogs option it terminates.


ALSO, maybe this is the cause, the source database was 10.2.0.2 and the destination db is 10.2.0.3. Do i need to run any cat scripts maybe?

[Updated on: Mon, 06 August 2007 11:33]

Report message to a moderator

Re: Manual Clone DB [message #256874 is a reply to message #256782] Mon, 06 August 2007 23:45 Go to previous messageGo to next message
Mohammad Taj
Messages: 2412
Registered: September 2006
Location: Dubai, UAE
Senior Member

Hi,


you need to install latest patch set for 10.2.0.2 Version.

Go to metalink and download latest patch set.

www.metalink.com

NOte: you need valid CSI number for access metalink support.

Regards
Taj
Re: Manual Clone DB [message #257122 is a reply to message #256874] Tue, 07 August 2007 10:58 Go to previous messageGo to next message
DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland
Senior Member
Quote:
www.metalink.com


https://metalink.oracle.com/
Wink
Re: Manual Clone DB [message #260709 is a reply to message #256780] Mon, 20 August 2007 14:43 Go to previous message
Sanjay Bajracharya
Messages: 279
Registered: October 2001
Location: Florida
Senior Member
shaseeb wrote on Mon, 06 August 2007 12:18
Thanks Taj, but your process is somewhat different and I am actually at the really end. I just can't get the database to open. And yes neither database was in archive log mode. I was actually following this:

http://orafaq.com/howto/clone-db.txt





That document presumes that you are in the same OS between the source and target. I have done this numerous times (under same OS - UNIX like cloning production into Test/Dev).

In Oracle 10gR2, you CAN transport database between different OS as long as you are in the same endian. key word is "endian". I have never had chance to do this. You can read the doc here...

http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_PlatformMigrationTDB.pdf

Good luck.
--
Sanjay B.
Previous Topic: ORA-01031: insufficient privileges
Next Topic: db_cache_size
Goto Forum:
  


Current Time: Sun Dec 04 18:55:05 CST 2016

Total time taken to generate the page: 0.04200 seconds