An error is reported when RMAN backs up the entire database and archives logs.
An error is reported when RMAN backs up the entire database and archives logs.
Hi.
I lost few previous archivelogs, and can't run "backup database plus archivelog ;".
That's what I got from rman:
RMAN> backup database plus archivelog;
Starting backup at 12-APR-09
Current log archived
Using channel ORA_DISK_1
RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================
RMAN-03002: failure of backup plus archivelog command at 04/12/2009 13:06:14
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file/u01/app/Oracle/backup/ORCL/archivelog/2008_08_04/o1_mf_1_11_49f37bn1 _. arc
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
How to fix it?
The error is reported because the expired and Lost Archive logs cannot be found. The solution is to run the following two commands to delete the expired archive logs.
Hi
Run commands:
RMAN> crosscheck archivelog all;
RMAN> delete noprompt expired archivelog all;
And then "backup database plus archivelog delete all input ;"
-------------------------------------- Recommended reading --------------------------------------
RMAN: Configure an archive log deletion policy
Basic Oracle tutorial-copying a database through RMAN
Reference for RMAN backup policy formulation
RMAN backup learning notes
Oracle Database Backup encryption RMAN Encryption
-------------------------------------- Split line --------------------------------------
Appendix
How to manually delete Oracle archive log files
Problem description
Oracle archive logs occupy full space, leading to abnormal database usage and backup errors.
Analyze problems
If the Oracle database does not have an archive log deletion policy or the daily log volume is too large, or the transaction log backup is not successful, the archive log cannot be deleted, you need to manually delete the archive log file.
Solution
I. For windows and linux
# Rman target username/password @ Instance name
Rman> delete archivelog until time 'sysdate-7'; DELETE all archived logs before 7.
Rman> crosscheck archivelog all;
Rman> delete noprompt expired archivelog all;
Rman> crosscheck archivelog all;
Rman> delete expired archivelog all;
2. for UNIX
# Rman target username/password @ Instance name
Rman> find./(archive Log Path)-xdev-mtime + 7-name "*. dbf"-exec rm-f {};