It figures. As soon as I spend the time to compose a diatribe to oracle-l, I
figure out the problem...
The trick is this:
SQL > recover database until cancel using backup controlfile;
Instead of this:
SQL > recover database using backup controlfile until cancel;
If I enter CANCEL in the first case, I can then open the target with reset
logs. If I enter CANCEL in the second case, Oracle continues to expect redo
logs indefinitely.... why Oracle doesn 't give me an error in the second case I
don 't know.
Thanks for the suggestions everyone sent in the meantime!
Rich
--
Rich Holland (913) 645-1950 SAP Technical Consultant
print unpack( "u ", "92G5S\=\ "!A;F]T:&5R(\ '!E <FP\@:&%C:V5R\ "\@\`\` ");
> -- --Original Message-- --
> From: Rich Holland [mailto:holland@(protected)]
> Sent: Tuesday, May 18, 2004 12:38 PM
> To: oracle-l@(protected)
> Subject: help "cloning " a database
>
> I 'm trying to make a copy of a database (running SAP, Oracle 9.2.0.4 64-bit,
> AIX 5.1) and running into some difficulty with the system tablespace. It
> doesn 't seem to matter if I shut the database down before the copy (offline)
[...]
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
