Oracle automatically activated problems Environment : 3 update3 redhat enterprise Linux server, oracle9ir6 (9.2.0.6) According to the Oracle document, create the following file dbora start on the following /etc/init.d #!/bin/sh # Set ORA_HOME to be equivalent to the $ORACLE_HOME # From which you wish to execute dbstart and dbshut; # # Set ORA_OWNER to the user id of the owner of the # Oracle database in ORA_HOME. ORA_HOME=/opt/ora9/product/9.2 ORA_OWNER=oracle If [!] - F $ORA_HOME/bin/dbstart Then Echo "can not start : Oracle startup" Exit Fi Case "$ 1" in 'Start') # Start the Oracle databases : # The following command assumes that the oracle Login # Will not prompt the user for any values Su-carotene $ORA_HOME/bin/dbstart & $ORA_OWNER ;; 'Stop') # Stop the Oracle databases : # The following command assumes that the oracle Login # Will not prompt the user for any values Su-carotene $ORA_HOME/bin/dbshut & $ORA_OWNER ;; Esac Oracle should not be switched automatically activated when found. But logging operation can start corresponding script database, using either direct or root to start Oracle posted operating /etc/rc.d/init.d/dbora dbstart operation can be posted. Later, plus countless words echo dbstart script to find start-up following the implementation of the order is no longer in operation : *) $SQLDBA "" EOF Connect / as sysdba Startup EOF 100 baffling. Then amend dbora script, su-su $ORA_OWNER-c $ORA_HOME/bin/dbstart & re-carotene $ORA_HOME/bin/dbstart $ORA_OWNER that prevent its implementation in the background. automatically switched on when the system was activated in the realization of Oracle. Although served its purpose, but still do not know why. Why not smooth implementation dbstart script in the background? Please shell experts advise. [ Closed window ]