Ethan,
Consider performing the clone in 2 distinct phases (my SOP). 1) Copying the
source database to the target machine w/ recovery if necessary, and 2)
Renaming/recreating the controlfile.
The recovery can be against a hot backup copy or cold w/ a controlfile
backup, and assures one of having
Did you recover the database using backup controlfile? Try that.
HTH,
Ruth
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Monday, July 29, 2002 12:48 PM
Having some trouble cloning a database. The database was shutdown with
the
immediate option
Digging into my own problem here, I did find this message from some years
back between Jonathen Lewis and Tom Kyte on Usenet, this probably explains
why I need to do a redo log switch before shutting down...
*
If
Yeah, went through the standard cloning process. My first line of trace
file looked like this...
CREATE CONTROLFILE SET DATABASE DM8 RESETLOGS NOARCHIVELOG
I am wondering if I should have stated NORESETLOGS here instead, that way
the data in the redo logs would be available and then the
Ethan,
Your first line of the trace file is the same as mine when I clone from cold
backups.
I also always do clean shutdown normal before cold backup but I think you
should be okay with shutdown immediate too (IMHO). I think if you are
renaming the cloned database then the RESETLOGS option is
Shutdown immediate always worked for me with 8.1.6 and 8.1.7.0.0 on HP-UX
11.0. Shutdown abort's another matter entirely.
-Original Message-
Sent: Monday, July 29, 2002 3:39 PM
To: Multiple recipients of list ORACLE-L
Ethan,
Your first line of the trace file is the same as mine when
Yeah Ed, your right, when renaming I think RESETLOGS is mandatory. If you
see my post referencing the stuff from Tom Kyte you will see the most likely
cause. I just wanted to be sure I wasn't losing my mind. I am sure of all
the things you mentioned. Another DBA did the copies and I trust him
I was looking in the docs :-)
In Recovery Manager Users Guide and Reference they have a script to shut
down the database for cold backup using RMAN.
It starts out something like this:
# Shut down the database cleanly using immediate priority. This type of
shutdown lets
# current calls to
From my understanding you do not need the on-line redo logs unless you
perform a shutdown abort. As a matter of fact the database will create the
logs if they do not exist when you issue the alter database open resetlogs
command.
-Original Message-
Sent: Monday, July 29, 2002 3:39 PM
Michael,
See previous post. It does appear that even during a shutdown immediate
(which does checkpoint) that instance recovery could be required. Thus we
need redo logs. Yes they will be recreated as you stated. However, there
is no way to both rename the database and perform instance
10 matches
Mail list logo
