To tylko jedna z 2 stron tej notatki. Zaloguj się aby zobaczyć ten dokument.
Zobacz
całą notatkę
Enabling Archiving of Redo Log Files
To back up the database while it is open, or to be able to perform complete or
point-in-time media recovery, you must enable the archiving of redo log files. To do
so, you place the database in ARCHIVELOG mode. You can determine if archiving of
redo logs is enabled for the target database using the following query:
SELECT LOG_MODE FROM V$DATABASE;
If you do not specify a destination to which the database should write archived log
files, the database writes them to the fast recovery area. You can specify a different
destination, or you can specify that multiple copies of each archived log file be written,
each to a different destination. Redundant copies help ensure that archived log files
are always available in the event of a failure at one of the destinations.
The following procedure assumes that you want to place archived log files in the
directory /u02/oracle/logfiles, and redundant copies of archived log file in the
directory /u03/oracle/logfiles. The redundant copies are optional.
To enable archiving of redo log files:
1. Connect RMAN to the target database as described in "Connecting to the Target
Database" on page 9-9.
2. Shut down the database.
SHUTDOWN IMMEDIATE;
3. Back up the database.
It is recommended that you always back up a database before making any major
change to the database.
See "Performing a Whole Database Backup" on page 9-18.
4. Start the instance and mount the database (do not open the database). To enable
archiving, the database must be mounted but not open.
STARTUP MOUNT;
5. Enter the following command to set the first archived log file destination:
ALTER SYSTEM SET LOG_ARCHIVE_DEST_1 = 'LOCATION=/u02/oracle/logfiles';
See Also:
■ "Fast Recovery Area" on page 9-5
■ "About the Fast Recovery Area Size" on page 9-7
WARNING: You must ensure that there is sufficient disk space at
all times for archived log file destinations. If the database
encounters a disk full error as it attempts to archive a log file, a fatal
error occurs and the database stops responding. You can check the
alert log for a disk full message.
... zobacz całą notatkę
Komentarze użytkowników (0)