Looking on how to delete archive logs in Oracle database? The R12 Applications will show funny error when the archive log is full in the database.
When We login to R12 Applications, it will redirect us to the error “Unable to generate forwarding URL. Exception: oracle.apps.fnd.common.PoolException: Exception creating new Poolable object.”
When we login to the Oracle Database via TOAD, the error message “ORA-00257: archiver error. Connect internal only, until freed” will pop up and denying our login.
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.
The only way to solve this issue is by login to the RMAN and remove the expired archive logs.
Recovery Manager: Release 10.1.0.2.0 - Production
Copyright (c) 1995, 2004, Oracle. ALL rights reserved.
RMAN> CONNECT target /
connected TO target DATABASE: INSTANT (DBID=1234567890)
RMAN> crosscheck archivelog ALL;
Note: You can schedule this command once a week.
The crosscheck command does NOT DELETE the information about the logs that it
could NOT find ON disk, it just updates their STATUS IN the repository AS 'EXPIRED'.
TO obtain a list OF logs marked AS 'EXPIRED' USE the following command:
RMAN> list expired archivelog ALL;
IF it IS NOT necessary TO keep the information about these
logs IN the repository, DELETE them WITH command:
RMAN> DELETE expired archivelog ALL;
Recovery Manager complete.
Next» Long Running Concurrent Request In Oracle