ORACLE的备份与恢复.ppt

Enabling Automatic Archiving at Instance Startup If the database is in ARCHIVELOG mode, then archiver processes can be started every time the database instance is started by setting the parameter: LOG_ARCHIVE_START = boolean where: TRUE automatically starts n ARCn processes upon instance startup, where n is determined by the value of LOG_ARCHIVE_MAX_PROCESSES. FALSE inhibits ARCn from starting upon instance startup. After the initialization parameter is set, the ARCn processes automatically start upon instance startup, eliminating the need for you to start automatic archiving manually. Enabling Automatic Archiving After Instance Startup You can enable automatic archiving by using the ALTER SYSTEM command. You can optionally specify the archiving destination with the TO option on the ALTER SYSTEM ARCHIVE LOG START command. Step Explanation 1 Check the status of the ARC n process: SQL ARCHIVE LOG LIST 2 Enable the archiver processes (ARC n ): UNIX : SQL ALTER SYSTEM ARCHIVE LOG START TO ‘/ORADATA/ARCHIVE1‘; Windows NT : SQL ALTER SYSTEM ARCHIVE LOG START TO ‘c: \ u04 \ Oracle \ TES T \ log‘; 3 The ARC n processes automatically archive log files as they are filled. Disabling Automatic Archiving You can always stop archive processes regardless of how you started them by using the ALTER SYSTEM command in SQL*Plus or Oracle Enterprise Manager. Note: Stopping ARCn processes does not set the database in NOARCHIVELOG mode. When all groups of redo logs are used and not archived, the database will stall if it is in ARCHIVELOG mode. Manual Archiving of Redo Log Files If your database is in ARCHIVELOG mode and you have not enabled automatic archiving, you must manually archive online redo log files. In addition, you can use manual archiving when automatic archiving is enabled to re-archive an inactive group to another destination. You must connect with administrator privileges to issue the ALTER SYSTEM ARCHIVE LOG co