Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Auto startup of db after reboot...

RE: Auto startup of db after reboot...

From: Maser, Donna (SEA) <>
Date: Wed, 6 Dec 2000 14:43:24 -0800
Message-Id: <>

Hi Rocky,
  I copied this from metalink, in case you can not gain access:

Doc ID: Note:98418.1
Subject: WARNING: "dbstart" does not work with 8.1.6 Instances Type: PROBLEM
 Content Type: TEXT/PLAIN
Creation Date: 07-FEB-2000
Last Revision Date: 13-JUL-2000
Language: USAENG  

Problem Description

  "dbstart" is a shellscript used on Unix platforms to start databases   listed in the "oratab" file. It is often called from system startup   scripts.

  The "dbstart" script shipped with all versions of Oracle up to and   including 8.1.6 does not start any 8.1.6 instances if they are down.   "dbstart" will report "Database <SID> warm started" rather than starting   the instance. This problem only affects 8.1.6 (or later) instances.

  The change in the banner may affect users custom startup / shutdown   scripts.    

  "dbshut" has no problem.

  Please note there are 2 related issues which should be born in mind   when changing any startup / shutdown scripts:

     Advance notification of Server Manager desupport      [NOTE:74943.1]
     Advance notification of CONNECT INTERNAL desupport    [NOTE:50508.1]

Solution Description


  Enterprise Edition Workaround

  The workaround is to change the dbstart script to look for the string   "Oracle8i Enterprise Edition" instead of "PL/SQL" by making the following   changes:
  1. Save a copy of the 8.1.6 $ORACLE_HOME/bin/dbstart script
  2. Edit the script and change the 'awk' lines from: VERSION=`$ORACLE_HOME/bin/svrmgrl command=exit | awk '
    /PL\/SQL (Release|Version)/ {substr($3,1,3) ;
    print substr($3,1,3)}'` to: VERSION=`$ORACLE_HOME/bin/svrmgrl command=exit | awk '
    /PL\/SQL (Release|Version)/ { print substr($3,1,3); exit }
    /Oracle7 Server (Release|Version)/ { print substr($4,1,3); exit }
    /Oracle8i Enterprise Edition (Release|Version)/ { print
    substr($5,1,3); exit }
    /Oracle8i (Release|Version)/ { print substr($3,1,3); exit }'`
      Additionally for platforms which set LD_LIBRARY_PATH in the dbstart
      script you should change the following:
            export LD_LIBRARY_PATH
            export LD_LIBRARY_PATH

   3. Copy the updated "dbstart" to any location it is expected to reside.
      Eg: system startup scripts often run /usr/local/bin/dbstart.

      IMPORTANT: Do not overwrite existing scripts without taking a backup
                 copy first as the script you are overwriting may have
                 been modified.

   NOTE: This workaround will only work for Oracle8 Enterprise Editions 
         Similar workarounds may be used for other editions.


  The problem is caused by a change in the Oracle banner which is output   by Oracle version 8.1.6. The banner no longer includes a PL/SQL line   and so the test in "dbstart" for a PL/SQL version returns a blank string   which in turn causes the step to startup the instance to be skipped.   


  The problem is reported in [BUG:1154931]

  The "oratab" file typically exists in either /etc/oratab or   /var/opt/oracle/oratab

  [NOTE:50508.1] - Advance notification of CONNECT INTERNAL desupport   [NOTE:74943.1] - Advance notification of Server Manager desupport

-----Original Message-----
Sent: Wednesday, December 06, 2000 7:23 PM To: Multiple recipients of list ORACLE-L

Hi gang,
The dbstart script on my 8.1.6 database on Solaris 8/Sun 450 doesn't seem to work. If I issue the dbstart command it returns:

OEM01 warm started

Whether the database is down or up. It doesn't start the database at all. I have the proper entry in my /var/opt/oracle/oratab file but no luck.

Any suggestions?


Rocky Welch
Senior Consultant - Internet Services Group Arthur Andersen

The information contained in this email is intended for the personal and confidential use of the addressee only. It may also be privileged information. If you are not the intended recipient then you are hereby notified that you have received this document in error and that any review, distribution or copying of this document is strictly prohibited. If you have received this communication in error, please notify Celltech Group immediately on:

+44 (0)1753 534655, or email '' Received on Wed Dec 06 2000 - 16:43:24 CST

Original text of this message