HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations نسخه متنی

18.5 DATABASE STARTUP AND SHUTDOWN

The database startup and shutdown scripts are located in the standard system location for startup at system boot time. If it becomes necessary to stop or restart the database after system bootutilize execute the scripts or commands at the command line.

18.5.1 Automatic Database Startup and Shutdown

At system boot time, the database startup is controlled by two configuration variables (ORACLE and LISTENER) located in the file /etc/rc.config.d/ovoracle. If the variable is equal to 1 (one), the database will startup. If the variable is equal to 0 (zero), the database will not startup. The script that executes the database startup commands is /sbin/init.d/ovoracle (/etc/init.d/ovoracle on Solaris). The database startup occurs in sequence based on the sequence numbers assigned to the ovoracle link files in the directories /sbin/rc3.d for startup sequence and /sbin/rc1.d for the shutdown/sequence. Also, the file /etc/oratab can start or prevent database startup.

Depending on user response to the automatic database startup question during the OVO server installation, the value of the Oracle database and listener process startup variables will be set to 0 or 1. If the database does not start automatically, you must make sure that it is started using some other mechanism before starting the OVO server.

18.5.2 Manual Database Startup and Shutdown

Manual database stop or restart sometimes becomes necessary. One reason for this would be to configure the database for archive log mode or after making changes to the parameter (initialization) file. The commands to stop the database are executed by the privileged user oracle. The following example demonstrates the commands to login to the database and perform a manual shutdown:

# su oracle
$ sqlplus
SQL*Plus: Release 9.2.0.2.0 - Production on Sat Jan 10 12:34:53 2004
Copyright © 1982, 2002, Oracle Corporation. All rights reserved.
Enter user-name: system
Enter password:
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.2.0 - 64bit Production
JServer Release 9.2.0.2.0 - Production
SQL> connect sys/<password> as sysdba
Connected.
SQL> shutdown
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 267479512 bytes
Fixed Size 735704 bytes
Variable Size 184549376 bytes
Database Buffers 81920000 bytes
Redo Buffers 274432 bytes
Database mounted.
Database opened.

18.5.2.1 Database Shutdown Command Line Options

• Shutdown (no options)
  The execution of the

  shutdown command stops the database, provided that there are no processes connected to the database and or outstanding transactions. If executed with processes connected the command will hang indefinitely.

• Shutdown normal
  Same as shutdown; wait for all users to disconnect. During shutdown, no new user connections are accepted. The database and redo log buffers are flushed to disk. Physical files are synchronized. The normal shutdown does not require instance recovery when the database restarts.

• Shutdown transactional
  Same as shutdown normal, except all users are disconnected after their current transactions complete.

• Shutdown immediate
  Current sessions are terminated and all users are logged off, current transactions are rolled back. No new user login sessions are accepted. The database and redo log buffers are flushed to disk. The physical files are synchronized. No instance recovery is required when the database restarts.

• Shutdown abort
  Terminate current sessions and log off all users. Accept no new request for login. Buffer cache is not flushed to disk. Physical files are not synchronized. Active transactions are not rolled back. Instance recovery is required when the database restarts. This may become necessary if the database is deadlocked and the shutdown immediate does not work. If this becomes necessary, you need to perform the following steps to bring the database back to a consistent state: shutdown abort, startup, and shutdown.