ORA-0257 archiver error 처리 방향

3075 단어 error

1. 먼저 oerr가 제시한 간략한 설명을 찾아라

oerr ora 257
00257, 00000, "archiver error. Connect internal only, until freed."
// *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.

2. 조회 V$RECOVERY_AREA_USAGE 정보:

SQL> select * from V$RECOVERY_AREA_USAGE;

FILE_TYPE            PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
-------------------- ------------------ ------------------------- ---------------
CONTROL FILE                          0                         0               1
REDO LOG                              0                         0               0
ARCHIVED LOG                      79.36                         0              58
BACKUP PIECE                      18.98                         0               8
IMAGE COPY                            0                         0               0
FLASHBACK LOG                         0                         0               0
FOREIGN ARCHIVED LOG                  0                         0               0

7 rows selected.

SQL> select sum(percent_space_used) from v$recovery_area_usage;

SUM(PERCENT_SPACE_USED)
-----------------------
                  98.34

아카이브 위치 확인:
SQL> archive log list
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     1412
Next log sequence to archive   1417
Current log sequence           1417

SQL> show parameter db_recovery

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest                string      +DATA
db_recovery_file_dest_size           big integer 350G

3. 실제 공간 잉여 상황에 따라 압축 파일 디렉터리의 크기를 적당히 늘려 업무 회복을 보장한다.

SQL> select NAME, TOTAL_MB, FREE_MB from v$asm_diskgroup;

NAME                             TOTAL_MB    FREE_MB
------------------------------ ---------- ----------
DATA                              3068928    2418353
alter system set db_recovery_file_dest_size = 600G;

4. 백업에 문제가 있는지 확인합니다.


① 백업 정책, 예를 들어 백업 후 삭제 메커니즘이 있는지 확인하고,
crosscheck backup;
crosscheck archivelog all;
delete expired archivelog all;
delete archivelog until time 'sysdate-1'; 
backup archivelog all delete input fromat '';
delete noprompt obsolete;

② 백업 로그 vi 찾기ORA- 문자의 분석 원인을 확인합니다.

좋은 웹페이지 즐겨찾기