"Rman 에러"의 두 판 사이의 차이
DB CAFE
(새 문서: RMAN-08138: WARNING: archived log not deleted - must create more backups RMAN> delete archivelog all; RMAN-08138: WARNING: archived log not deleted - must create more backups archiv...) |
|||
| 49번째 줄: | 49번째 줄: | ||
RMAN> delete archivelog all; | RMAN> delete archivelog all; | ||
| + | |||
| + | [[category:oracle]] | ||
2020년 7월 19일 (일) 13:26 기준 최신판
- DBA { Oracle DBA 명령어 > DBA 초급 과정 > DBA 고급 과정 }
- 튜닝 { 오라클 튜닝 목록 }
- 모델링 { 데이터 모델링 가이드 }
RMAN-08138: WARNING: archived log not deleted - must create more backups RMAN> delete archivelog all;
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=/holding/testdb2/archive_logs/1_691_941163822.dbf thread=1 sequence=691
.
.
.
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=/holding/testdb2/archive_logs/1_694_941163822.dbf thread=1 sequence=694
Solution:
Archive log deletion failing because archive log deletion policy set must be backed up 1 times and there was no backup performed. To delete archive log without backup I have change the deletion policy.
RMAN> show ARCHIVELOG DELETION POLICY;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name TESTDB2 are:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY BACKED UP 1 TIMES TO DISK;
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
old RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY BACKED UP 1 TIMES TO DISK;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
new RMAN configuration parameters are successfully stored
RMAN> delete archivelog all;