Databases Reference
In-Depth Information
Check the correct setting by issuing an
archive log list
command at the SQL prompt:
7.
SQL>archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 47
Next log sequence to archive 49
Current log sequence 49
Note the line
Archive destination USE_DB_RECOVERY_FILE_DEST
, which confirms that the archived redo log
destination is set to the fast recovery area.
8.
Check the operation by issuing a log switch that forces the generation of an archived
redo log:
alter system switch logfile;
9.
Execution of this command should come back with the message “System altered.” If you
see any other message, then you will get a clue for your next action from the message itself.
For instance, a common message is as follows:
ORA-00257: archiver error. Connect internal only, until freed.
10.
This message indicates that the location specified for archived redo logs is possibly full,
so you need to address that, as shown in Recipe 3-5.
11.
Confirm that an archived redo log was created in the fast recovery area. Oracle will
automatically create a directory called archivelog in the FRA and also a subdirectory under
that named as the day's date specified in the format YYYY-MM-DD. You can go to that
directory and check for the existence of a new, archived redo log file.
12.
Alternatively, or in addition to checking for the physical presence of the file, you can check
the database for the existence of the archivelog:
SQL>select name from v$archived_log
2 order by completion_time;
NAME
--------------------------------------------------------------------------------
... output truncated ...
+FRA/cdb1/archivelog/2012_08_01/thread_1_seq_128.342.790207235
+FRA/cdb1/archivelog/2012_08_01/thread_1_seq_129.343.790207281
+FRA/cdb1/archivelog/2012_08_01/thread_1_seq_130.344.790208967
+FRA/cdb1/archivelog/2012_08_02/thread_1_seq_131.345.790239647
+FRA/cdb1/archivelog/2012_08_02/thread_1_seq_132.346.790279237
13.
This shows the last archived redo log was created in the fast recovery area as an Oracle
managed file (note the long name).
14.
Now the archived redo log destination is set to the fast recovery area.
