Oracle-L: RE: re SHUTDOWN ABORT -- was RE: Debate on rc commands Solaris an

From: M Rafiq <rafiq9857_at_hotmail.com>
Date: Fri, 07 Feb 2003 09:29:50 -0800
Message-ID: <F001.005474CB.20030207092950@fatcity.com>

Dave

Just add one more line before to shutdown abort...

alter system checkpoint;
SHUTDOWN ABORT
STARTUP RESTRICT
SHUTDOWN IMMEDIATE Regards
Rafiq

Reply-To: ORACLE-L_at_fatcity.com
To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com> Date: Fri, 07 Feb 2003 07:28:43 -0800

I do my cold backups at a time when the system is not being used. In the future I want to learn RMAN for hot backups but for now I do the following;

SHUTDOWN ABORT
STARTUP RESTRICT
SHUTDOWN IMMEDIATE You mention about checkpointing, how can I do a checkpoint in my script before the SHUTDOWN ABORT?

Thanks,

Dave

-----Original Message-----
Sent: Thursday, February 06, 2003 10:54 PM To: Multiple recipients of list ORACLE-L 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.

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.
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!

-----Original Message-----
Rajendra
Sent: Monday, February 03, 2003 9:01 AM
To: Multiple recipients of list ORACLE-L an

When we do cold backups, our script issues 'shutdown immediate', if within 3 minutes the db is not shut down, we cancel and issue 'shutdown abort'. In either case, we (again issue) startup/shutdown to make it clean before taking backup.

We don't worry about users connecting, as during cold backup window, the listeners are shutdown. For us it is a circus (kind of) because our production DBs talk to each other, so we have to follow a specific seq of shutdown/startup.

So far we haven't encountered any major issues because of 'shutdown abort' ... (heavily knocking on the wood !!)
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!

Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail

--

Please see the official ORACLE-L FAQ: http://www.orafaq.net
--

Author: M Rafiq
INET: rafiq9857_at_hotmail.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Fri Feb 07 2003 - 11:29:50 CST