Thank you Mark - I'll give it a try on our test systems. Robyn On 2/27/06, Bobak, Mark <Mark.Bobak@xxxxxxxxxxxxxxx> wrote: > > My preferred solution is: > > STARTUP FORCE RESTRICT <--- equivalent of shutdown abort followed by > startup restrict > SHUTDOWN IMMEDIATE > > -Mark > > *--* > *Mark J. Bobak* > *Senior Oracle Architect* > *ProQuest Information & Learning* > > "Exception: Some dividends may be reported as qualified dividends but are > not qualified dividends. These include: > > • Dividends you received on any share of stock that you held for less than > 61 days during the 121-day period that began 60 days before the ex-dividend > date. The ex-dividend date is the first date following the declaration of a > dividend on which the purchaser of a stock is not entitled to receive the > next dividend payment. When counting the number of days you held the stock, > include the day you disposed of the stock but not the day you acquired it. > See the examples below. Also, when counting the number of days you held the > stock, you cannot count certain days during which your risk of loss was > diminished. See Pub. 550 for more details." > > --IRS, Form 1040-A Instruction Booklet, Line 9b: Qualified Dividends > > > ------------------------------ > *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto: > oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Robyn > *Sent:* Monday, February 27, 2006 11:37 AM > *To:* Oracle-L@Freelists > *Subject:* hanging shutdowns > > Hello all, > > I have a small dilemma I need to resolve. We have several large databases > that do not shutdown quickly due to active processes (usually AQ stuff but > not always) and this has caused problems with cold backups in the past. > (I'd prefer to stop the colds entirely, but have not yet won that debate.) > > Another dba wrote a script which first kills all unix processes connecting > to the database, connects to the database to kill all sessions except the > sys connections and then issues a shutdown immediate. We now have another > instance on the server so I need to modify the scripts for the new instance > but I'm not comfortable with the current approach. > > Given that I need to have something that works by next Sunday morning, > what is the best way to structure these scripts? Continue to kill > everything? Issue a shutdown, find the remaining active transactions and > kill only them? Issue a shutdown abort, restart, shutdown cleanly and then > run the backups? I've seen discussions on this subject in the past, I'm > just wondering if there's any new solutions or concerns on the subject. > > Databases are Oracle 9.2.0.6 on HP-UX approximately a TB in size. (some > slightly bigger, some slightly smaller) > > recommendations appreciated ... > > Robyn > > -- Robyn Anderson Sands email: Robyn.Sands@xxxxxxxxxx