以前的一个关于恢复区常见错误的处理过程
现象:
告警日志,内容如下:
alert.log:
host_id='M1HFData' host_addr='::1' module='MMON_SLAVE'
pid='25261'>
ORA-19815: WARNING: db_recovery_file_dest_size of 322122547200 bytes is 85.01% used, and has 48299640832 remaining
bytes available.
查看OS存储信息如下:
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root
50G 12G 36G 25% /
tmpfs 7.5G 276K 7.5G 1% /dev/shm
/dev/sda1 485M 33M 427M 8% /boot
/dev/mapper/VolGroup-lv_home
392G 213M 372G 1% /home
/dev/sdb 9.9T 5.8T 3.6T 62% /opt/M1HFData
查看参数设置:
NAME TYPE
------------------------------------ --------------------
VALUE
------------------------------
db_recovery_file_dest string
/opt/M1HFData
db_recovery_file_dest_size big integer
300G
查看相关文件分布情况:
FILE_TYPE USED RECLAIMABLE number
-------------------- ---------- ----------- ----------
CONTROL FILE 0 0 0
REDO LOG 0 0 0
ARCHIVED LOG 32.95 0 216
BACKUP PIECE .01 0 1
IMAGE COPY 0 0 0
FLASHBACK LOG 53.59 .03 1915
FOREIGN ARCHIVED LOG 0 0 0
查看闪回最早时间点:
OLDEST_FLASHBACK_SCN OLD_TIME
-------------------- ------------------------------
547836755 2011/11/09 11:16:38
经过分析,此原因的产生是由于昨天晚上跑的一个脚本(此脚本于03::00左右正确执行完成),产生大量归档日志信息,以至于相关目录空间集聚增长,达到相关参数的报警临界值。
处理方案:
为保证闪回的最早时间点(即快速恢复可用性),故不对闪回相关文档进行操作,于是决定将归档日志备份以释放相关空间。
处理后相关文件分布百分比如下:
FILE_TYPE USED RECLAIMABLE number
-------------------- ---------- ----------- ----------
CONTROL FILE 0 0 0
REDO LOG 0 0 0
ARCHIVED LOG 0 0 0
BACKUP PIECE .01 .01 2
IMAGE COPY 0 0 0
FLASHBACK LOG 53.59 .24 1915
FOREIGN ARCHIVED LOG 0 0 0
后续继续观测相关告警信息以及相关目录状态。
附metalink相关处理
Action: One of the following:
1.Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE.
2.Backup files to tertiary device using RMAN.
3.Consider changing RMAN retention policy.
4.Consider changing RMAN archivelog deletion policy.
5.Delete files from recovery area using RMAN.
来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/26143577/viewspace-715748/ ,如需转载,请注明出处,否则将追究法律责任。