We encounter this error when the archivelog destination (specified by DB_RECOVERY_FILE_DEST parameter ) is full.
Solution
1. When we have time and resource consider adding disks to the diskgroup upon which the archive log destination resides and then increase the parameter DB_RECOVERY_FILE_DEST_SIZE parameter.
ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE=XXXG SCOPE=BOTH;
2.If the above solution doesn't work, use rman to delete the archive log which have been backed up to make some space in the destination.
export ORACLE_SID=TESTDB
rman target /
RMAN> delete noprompt archivelog all completed before 'sysdate - 1';
The above command deletes archivelogs which have been completed 24 hours ago if you have archivelog backup in last 24 hours then you are good to go otherwise change the sysdate - to larger number of days.
3. Consider configuring rman archive log deletion and retention policies.
Solution
1. When we have time and resource consider adding disks to the diskgroup upon which the archive log destination resides and then increase the parameter DB_RECOVERY_FILE_DEST_SIZE parameter.
ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE=XXXG SCOPE=BOTH;
2.If the above solution doesn't work, use rman to delete the archive log which have been backed up to make some space in the destination.
export ORACLE_SID=TESTDB
rman target /
RMAN> delete noprompt archivelog all completed before 'sysdate - 1';
The above command deletes archivelogs which have been completed 24 hours ago if you have archivelog backup in last 24 hours then you are good to go otherwise change the sysdate - to larger number of days.
3. Consider configuring rman archive log deletion and retention policies.
No comments:
Post a Comment