Oracle数据库日常维护手册(国外英文资料).doc

Oracle数据库日常维护手册(国外英文资料) During the operation of the Oracle database, the DBA should monitor the running log of database and table space, find the problems existing in the database as soon as possible. A warning, Oracle log file monitoring Oracle in the operation process, will be in the alert log file (alert_SID.log) operation records in the database: The database startup shutdown, non default startup parameters; Redo log - switching database, record each switching time, and if the checkpoint (checkpoint) operation was not completed due to reasons can not switch, record cannot switch; Some operations - the database, such as creating or deleting a table space, increase the data file; The database error occurred, such as a table space is not enough, the internal bad block, database error (ORA-600) DBA should regularly check the log file and processed in a timely manner according to the problems found in the log. Handling problems: Dont check the startup parameters initialization parameter file Because the checkpoint file or the operation did not complete due to the redo log cannot be switched if such a situation occurs frequently, can consider increasing the redo log file group; to find ways to improve the efficiency of the checkpoint or archive operation; Someone without authorization to delete the security check database table space, if the password is too simple; if necessary, some user permissions revocation system There is a bad block check is a hardware problem (such as disk the bad block), if not, check the database objects appear bad blocks, the reconstruction of the object Table space is not enough increase the data file to the corresponding table space ORA-600 view the TRC file according to the contents of the log file, if it is Oracle bug, a timely hit the corresponding patch Two, the database table space usage monitoring (Dictionary managed tablespaces) The database is running after a period of time, due to the constant in the table space to create and del