Saturday, 3 January 2009

My Database Has an Archiver Error Whatever Shall I Do?

When the database is complaining that the disk is full due to an archiver error, and there is no-one to get to do the work for you then you can follow the following steps to clear the problem down.

1. df -h
This shows you the mount points and their sizes and usage.

2. rman target /
This connects you to the rman (Recovery MANager) repository - in this case the database controlfile.

3. For a quick win try....
- crosscheck backup;
- crosscheck archivelog all;
- delete noprompt expired;
- delete noprompt obsolete recovery window of 1 days;

4. list archivelog all;
This shows you a list of all the remaining archivelogs on the system. If this list continues beyond a couple of screenfuls or the dates are for more that two days ago then you have candidates for deletion.

5. delete noprompt archivelog until time 'sysdate-2';
Removes archivelogs older than two days.

6. delete noprompt expired;
Removes any exired objects;

7. exit;
Leaves rman.

In enterprise manager the same commands are available in point and click in the maintenance tab under the maintain current backups entry.

No comments: