- 운영 DB의 Backup ==> 신규 서버로 Restore/Recovery
2. ORA-010567 Error 발생
...
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3020], [4263064082], [1], [445534], [1024879], [468], [], []
ORA-10567: Redo is inconsistent with data block (file# 1016, block# 1651218)
ORA-10564: tablespace TS_DATA_10M
ORA-01110: data file 1016: '/com_stg41/oradata/ts_data_10m_94.dbf'
ORA-10560: block type 'FIRST LEVEL BITMAP BLOCK'
Recovery interrupted.
Recovered data files restored to a consistent state at change 13156165013519
...
2-1. Recovery 하기
SQL> recover database allow 1 corruption;
SQL> recover database allow 1 corruption;
We need to repeat this command until the recovery completes.
SQL> recover database allow 1 corruption;
Starting recover at 03-OCT-12
using channel ORA_DISK_1
starting media recovery
media recovery complete, elapsed time: 00:00:02
Finished recover at 03-OCT-12
3. ORA-01194 Error 발생
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 1687171004 generated at 01/07/2010 10:58:26 needed for thread
1
Media Recovery Log /MALLDB_arch/ARCH/arch_1_445534.arc
ORA-00280: change 1687171004 for thread 1 is in sequence #445534
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 430 needs more recovery to be consistent
ORA-01110: data file 1: '/com_stage55/oradata/ts_wrk_430.dbf'
3-1. Recovery 하기
SQL> shutdown immediate
# init<SID>.ora
_allow_resetlog_corruption=true
SQL> startup mount
SQL> recover database using backup controlfile until cancel;
cancel
SQL> alter database open resetlogs;
-- raw-device Redolog Size 부족 :: smitty lvm 에서 Size 증가
-- Temp raw-device 추가 !!
