RE: hanging shutdowns, excellent case for a standby recovery database and associated frozen rename target

Something in there just sparked this: if that level of DB recovery is necessary, then wouldn't that have to extend to the DB server's OS as well? There's no guarantee that at the time of the cold backup that the oracle s/w wouldn't have had extraneous suids set or be owned by root or was running with this particular Oracle patch that required a particular OS patch or whatever. Ewwwwwww!!!! I think that's on the 6th level of hell...

Rich

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Powell, Mark D
Sent: Tuesday, February 28, 2006 2:55 PM To: Oracle-L_at_Freelists
Subject: RE: hanging shutdowns, excellent case for a standby recovery database and associated frozen rename target

I have a minor issue with one point in Mark Farnham's response. I think Mark has confused the ability of the Oracle rdbms to open and accept connections prior to performing all rollbacks after a crash with the shutdown process. If you do a shutdowm immediate all current transactions are rolled back. The cold backup will not contain any "pending" rollbacks. Delayed block cleanout may have to be done, but all transaction rollbacks are complete. I do not consider delayed block cleanout an issue though I guess it is possible legal was told they could extract the time of the last checkpoint from the file header. I would expect the OS file timestamp to match the time the file was created from the backup tape.

[snip]

--
http://www.freelists.org/webpage/oracle-l