Oracle数据库维护培训华为.pptVIP

Shutdown Options Shutdown Abort If the normal and immediate shutdown options do not work, you can abort the current database instance. Aborting an instance proceeds with the following conditions: Current SQL statements being processed by the Oracle server are immediately terminated. Oracle does not wait for users currently connected to the database to disconnect. Database and redo buffers are not written to disk. Uncommitted transactions are not rolled back. The instance is terminated without closing the files. The database is not closed or dismounted. The next startup requires instance recovery, which occurs automatically. Shutdown Options (continued) How to Use the Console to Start Up or Shut Down Launch the Console: % oemapp console Choose Launch Standalone Expand your working database from the Databases folder Expand Instance folder and click Configuration From the General tab, select an Instance State, and click Apply. Note: You should be connected to the database with SYSDBA privileges to perform startup or shutdown. You can also launch the Console from Windows NT Start menu User Trace Files User trace files contain statistics for traced SQL statements, which are useful for SQL tuning. In addition, user trace files contain user error messages. Naming convention for user trace file: sid_ora_PID.trc (db01_ora_23845.trc) on Unix. Its location is defined by the USER_DUMP_DEST initialization parameter. The default location on Unix is $ORACLE_HOME/rdbms/log. Practice 3: Managing an Oracle Instance 1 Connect to the database as user SYS AS SYSDBA and shutdown the database. 2 With the database shutdown, create an SPFILE from the PFILE. Place the SPFILE in directory $HOME/ADMIN/PFILE with the file name format spfileSID.ora, use your instance name in place of SID. Create the SPFILE from the PFILE located in $HOME/ADMIN/PFILE. 3 From the operating system, view the SPFILE. 4 Connect as user SYS AS SYSDBA, and start the database using the SPFILE. 5 S