IT Tutorial IT Tutorial | Oracle DBA | SQL Server, Goldengate, Exadata, Big Data, Data ScienceTutorial
I got ” RMAN-06059 expected archived log not found, loss of archived log compromises recoverability ” error in Oracle database.
RMAN-06059 expected archived log not found, loss of archived log compromises recoverability
Details of error are as follows.
RMAN-06059 expected archived log not found, loss of archived log compromises recoverability Cause: The archived log was not found. The repository thinks it does exist. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable across the point in time covered by the archived log. This may occur because the archived log was removed by an outside utility without updating the repository. Action: If the archived log has been removed with an outside utility and the archivelog has already been backed up, then you can synchronize the repository by running CROSSCHECK ARCHIVELOG ALL. If the archivelog has not been previously backed up, then you should take a full backup of the database and archivelogs to preserve recoverability. Previous backups are not fully recoverable.
RMAN-03002: failure of backup command at 04/16/2021 19:01:40 RMAN-06059: expected archived log not found, lost of archived log recoverability ORA-19625: error identifying file /var/opt/arch_oltp28_1_744738.arc ORA-27037: unable to obtain file status
expected archived log not found, loss of archived log compromises recoverability
This RMAN-06059 error is related with the archived log was not found. The repository thinks it does exist. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable
across the point in time covered by the archived log.
This may occur because the archived log was removed by an outside utility without updating the repository.
CROSSCHECK ARCHIVELOG ALL
If the archived log has been removed with an outside utility and the archivelog has already been backed up, then you can synchronize the repository by running CROSSCHECK ARCHIVELOG ALL.
If the archivelog has not been previously backed up, then you should take a full backup of the database and archivelogs to preserve recoverability. Previous backups are not fully recoverable.
The error still persist after the following commands have been tried :-
RMAN> crosscheck copy of archivelog all RMAN> crosscheck archivelog all RMAN> resync catalog RMAN> delete force obsolete; RMAN> delete expired archivelog all ;
From the above command ‘delete force obsolete’ and ‘delete expired archivelog all’ fails with segmentation errors
Files were deleted at OS level. Archive log files were deleted at OS level.
To solve this error, Run the following commands.
RMAN> Change archivelog '<Archive log which was deleted>' UNCATALOG ;
Please note the first archive log name would be present in the error message ORA-19625:
For example :
RMAN-06059: expected archived log not found, lost of archived log ORA-19625: error identifying file /var/opt/arch_oltp28_1_744738.arc ORA-27037: unable to obtain file status RMAN> Change archivelog '/var/opt/arch_oltp28_1_744738.arc' uncatalog;
Run the archive log backup command check if you still get the error
Keeping specify the archive log file name reported in ORA-19625 till backup of archive log goes fine
Or
RMAN> Change Archivelog all Uncatalog ;
Please note the above command will uncatalog the information about the Archive log from catalog database.
Do you want to learn Oracle Database for Beginners, then read the following articles.
Oracle Tutorial | Oracle Database Tutorials for Beginners ( Junior Oracle DBA )
