Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Strange Problems OE 7.3.4 / NT4 SP3

Re: Strange Problems OE 7.3.4 / NT4 SP3

From: Alan Campbell <ajc_at_cgocable.net>
Date: Sun, 27 Jun 1999 20:23:26 -0400
Message-ID: <3776C07D.F96F4BA9@cgocable.net>


Where did you learn that stopping the service will first do a shutdown. If it does, what type of shutdown: immediate or Normal? And if so, how do you change the setting?
I do not know of such a facility. You have a common misconception that stopping the service first shuts down the instance. In my experience this is not the case. To avoid possible corruption, You must do a shutdown, or shutdown immediate, and wait for this to complete before stopping the service. Stopping the service is required to get a good cold backup because the service does not seem to let go of some of the datafiles even though the instance has been shutdown.

Gerhard Eickenhorst wrote:

> Hi all
>
> I've got a strange problem.
> Oracle Enterprise Edition 7.3.4 on a Compaq ProLiant 1500 NT4 SP3.
> Sometimes when I shut down the Oracle service, the DB hangs in a
> undefined mode. The service shuts faster than the DB.
>
> Sometimes it works fine; first Oracle then the service...
> We use this to do cold backups at night.The stop service command is
> issued by the ADSM preschedule procedure command. ADSM works fine. After
>
> the backup ADSM issues the start service command. Because the shutdown
> hasn't completed, the start command doesn't work.
> I don't always want to start using the startup force command. It's like
> using a hammer... ;)
>
> Any comments are welcome.
>
> Gerhard
Received on Sun Jun 27 1999 - 19:23:26 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US