Sybrand Bakker wrote:
>
> On Tue, 24 Jun 2003 13:02:48 +0100, Anthony Hogan
> <ahogan-nospam-_at_iespana.es> wrote:
>
> >I have the same problem on some of my W2K servers: The instance does not
> >open automatically on reboot. You can connect sys as sysdba and manually
> >startup the instance after reboot or create a script which opens the
> >instance. This script can then be associated with a scheduled task which
> >runs at system startup.
> >Beware of the script option if you have multiple instances on the server
> >as it may not always open all the instances.
> >
> >HTH
> >Anthony Hogan
>
> Is this a solution or just a workaround?
> You need to identify *why* your database doesn't start by verifying
> oradim.log and the alert log, instead of implementing and -even worse-
> recommending this crap workaround, which doesn't *solve* anything!
>
> Sybrand Bakker, Senior Oracle DBA
>
Sybrand,
Point taken. I know why the database doesn't start: it's a bug in
8.1.7.0.0 which (sometimes) manifests itself on W2K servers. The
permanent solution is to apply the patches.
Failing this, the workaround does solve the problem of unscheduled
server reboots not bringing up the instance.
Anthony Hogan
Received on Wed Jun 25 2003 - 03:07:04 CDT
