Thanks Robert,
I wasn't aware of that issue. Plus now that we have all instances on 9202, we hope it won't bite us. As for adding tablespaces dynamically, no chance. We *require* that development team request space at-least 7 business days before they actually need it. This gives us enough time to create raw including backups)) and make sure that hot backups go on fine before we make it available to them for actual use.
Thanks again ..
Raj
______________________________________________________
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't reflect that of ESPN Inc.
QOTD: Any clod can have facts, but having an opinion is an art!
-----Original Message-----
From: Robert Freeman [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 06, 2003 11:54 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: re SHUTDOWN ABORT -- was RE: Debate on rc commands Solaris an
Let me throw in my 2 cents worth on this topic. There are two problems with SHUTDOWN ABORT that I have experienced in the past.
1. Before 9i (it appears to be fixed in 9i) if you inserted data in a table, then did a shutdown abort, if after restarting the database, you tried to truncate the table while the database was performing recovery on that table, the database would crash.
2. Assume that you have applications that are dynamically doing things like adding and dropping tablespaces. WHat happens if the app is in the middle of such an operation and it's in the middle of writing new records to the control file. What is the result if you shutdown abort in the middle of this write, before it's complete. We experienced a situation like this earlier this week.
I've always been opposed to shutdown abort unless you are certain that you have checkpointed and that there are no user sessions operating on the database.
Cheers!
RF
********************************************************************This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you.*********************************************************************2
