*Cause: The archiver process received an error while trying to archive
a redo log. If the problem is not resolved soon, the database
will stop executing transactions. The most likely cause of this
message is the destination device is out of space to store the
redo log file.
*Action: Check archiver trace file for a detailed description
of the problem. Also verify that the
device specified in the initialization parameter
ARCHIVE_LOG_DEST is set up properly for archiving.
Explanation:-
The archiver process received an error while trying to archive a log.
The database will stop executing transactions.
The cause of this error is the archive destination device is out of space.
This will stop the system from working allowing only internal to connect.
solution:-
1)
Sql> conn / as sysdba
sql> archive log list;
---see the Archive Destination and
---increase the size of that location
suppose if archive destination is USE_DB_RECOVERY_FILE_DEST
then increase the size with following command.
SQL> alter system set db_recovery_file_dest_size=3G ;
2) backup your database and archive logs to somewhere else then delete archive log file via Rman
RMAN> connect target sys/sys@orcl as sysdba
RMAN> delete archivelog all ;
3) also you can configure
set the following parameters so that when the dest1 is full, archiving is automatically performed to the alternate dest2 :
log_archive_dest_1='LOCATION=use_db_recovery_file_dest NOREOPEN ALTERNATE=LOG_ARCHIVE_DEST_2'
log_archive_dest_2='LOCATION=/other_dest_for_archiving'
log_archive_dest_state_1='enable'
log_archive_dest_state_2='alternate'
db_recovery_file_dest='/u01/app/oracle/product/10.1.0/db_1/flash_recovery_area'
db_recovery_file_dest_size=2G
Windows Recall : How to disable spy mode
2 days ago
No comments:
Post a Comment