eygle.com   eygle.com
eygle.com  
 

« Install MT plugins-Scode 1 | Blog首页 | How Many knowledge you do not Know from this Operation? »

Oracle Diagnostics:How to deal with ORA-19815

作者:eygle |【转载时请以超链接形式标明文章和作者信息及本声明
链接:

下班的时候,想不到又遇到了ORA-19815错误,这个10g的数据库最近数据量狂增,每天产生大约5~6个G的归档:

ORA-19815: WARNING: db_recovery_file_dest_size of 53687091200 bytes is 85.00% used, and has 8052259328 remaining bytes available.
*************************************************************
You have the following choices to free up space fromflash recovery area:1. Consider changing your RMAN retention policy. If you are using dataguard, then consider changing your RMAN archivelog deletion policy.2. Backup files to tertiary device such as tape using the RMAN command BACKUP RECOVERY AREA.3. Add disk space and increase the db_recovery_file_dest_size parameter to reflect the new space.4. Delete unncessary files using the RMAN DELETE command. If an OS command was used to delete files, then use RMAN CROSSCHECK and DELETE EXPIRED commands.

db_recovery_file_dest_size设置的是50G,在当前的备份策略下已经不足够.只好临时扩展一下恢复区:

 SQL> show parameter recov
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest                string      /msflsh
db_recovery_file_dest_size           big integer 50G
recovery_parallelism                 integer     0
SQL> alter system set db_recovery_file_dest_size=65G scope=both;
System altered.
SQL> show parameter recov
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest                string      /msflsh
db_recovery_file_dest_size           big integer 65G
recovery_parallelism                 integer     0

再修改下冗余策略,释放部分磁盘空间: 

$ rman target /                                                                  
Recovery Manager: Release 10.1.0.3.0 - 64bit Production                         
Copyright (c) 1995, 2004, Oracle.  All rights reserved.                         
connected to target database: MMSDB (DBID=799462343)                            
RMAN> show all;                                                                 
using target database controlfile instead of recovery catalog                   
RMAN configuration parameters are:                                              
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;                                     
....                                                                            
RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 1;                               
old RMAN configuration parameters:                                              
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;                                     
new RMAN configuration parameters:                                              
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;                                     
new RMAN configuration parameters are successfully stored                       
RMAN> delete obsolete;                                                          
RMAN retention policy will be applied to the command                            
RMAN retention policy is set to redundancy 1                                    
allocated channel: ORA_DISK_1                                                   
channel ORA_DISK_1: sid=127 devtype=DISK                                        
Deleting the following obsolete backups and copies:                             
Type                 Key    Completion Time    Filename/Handle                  
-------------------- ------ ------------------ --------------------             
Backup Set           672    27-NOV-05                                           
Backup Piece       672    27-NOV-05                                             
/msflsh/MMSDB/backupset/2005_11_27/o1_mf_annnn_TAG20051127T043004_1rkkggjh_.bkp 
Backup Set           673    27-NOV-05                                           
Backup Piece       673    27-NOV-05                                             
/msflsh/MMSDB/backupset/2005_11_27/o1_mf_annnn_TAG20051127T043004_1rkkh05d_.bkp 
Backup Set           674    27-NOV-05                                           
Backup Piece       674    27-NOV-05                                             
/msflsh/MMSDB/backupset/2005_11_27/o1_mf_annnn_TAG20051127T043004_1rkkhvtb_.bkp 
Backup Set           676    28-NOV-05                                           
Backup Piece       676    28-NOV-05                                             
/msflsh/MMSDB/backupset/2005_11_28/o1_mf_annnn_TAG20051128T043004_1rn5tfoo_.bkp 
Backup Set           718    03-DEC-05                                           
Backup Piece       718    03-DEC-05                                             
/msflsh/MMSDB/autobackup/2005_12_03/o1_mf_s_576045489_1s1d5kgd_.bkp             
Do you really want to delete the above objects (enter YES or NO)? yes           
deleted backup piece                                                            
backup piece handle=/msflsh/MMSDB/backupset/2005_11_27/                         
o1_mf_annnn_TAG20051127T043004_1rkkggjh_.bkp recid=672 stamp=575440206          
deleted backup piece                                                            
backup piece handle=/msflsh/MMSDB/backupset/2005_11_27/                         
o1_mf_annnn_TAG20051127T043004_1rkkh05d_.bkp recid=673 stamp=575440224          
deleted backup piece                                                            
backup piece handle=/msflsh/MMSDB/backupset/2005_11_27/                         
o1_mf_annnn_TAG20051127T043004_1rkkhvtb_.bkp recid=674 stamp=575440251          
deleted backup piece                                                            
backup piece handle=/msflsh/MMSDB/backupset/2005_11_28/                         
o1_mf_annnn_TAG20051128T043004_1rn5tfoo_.bkp recid=676 stamp=575526605          
deleted backup piece                                                            
backup piece handle=/msflsh/MMSDB/autobackup/2005_12_03/                        
o1_mf_s_576045489_1s1d5kgd_.bkp recid=718 stamp=576045489                       
Deleted 5 objects                                                               
RMAN> exit                                                                      
Recovery Manager complete.                                                      

赶快跑回家,北京冷的要命了,明天需要重新规划一下这个数据库了.以前的设计容量太小了.


历史上的今天...
      >> 2008-12-05文章:
             Oracle Developer Forum -开发者大会
      >> 2007-12-05文章:
             DBA需求旺盛 批量招聘DBA
      >> 2006-12-05文章:
             体验微软的 Office 2007 新版本
             关于版权的一点声明
------
这篇 【Oracle Diagnostics:How to deal with ORA-19815】来自 eygle.com | CSDN网摘| del.icio.us|Google订阅 | 鲜果订阅 | 抓虾订阅

By eygle on 2005-12-05 21:37 | Comments (5) | Posted to Backup&Recovery | Edit |

相关文章 随机文章
  • 断电故障导致 ASM DiskGroup 故障及恢复案例
  • 使用ora_rowscn识别误操作数据时间点
  • Oracle ASM的AU(Allocation units)分配
  • ASM的一张体系结构简图
  • Oracle Database 11g回滚段命名的变化
  • 北京天下亦有雪
    投资以及投资回报
    Oracle10g v$database视图SCN增强
    人民大会堂看电影记
    罗大佑的《美丽岛》
    搜索本站:

    留言 (5)

    不懂!

    Posted by: Julia at December 5, 2005 10:10 PM

    Flash RECOVERY AREA 似乎不是那么好

    Posted by: Fenng at December 5, 2005 11:29 PM

    我觉得还好吧,有利也有点弊.

    Posted by: eygle at December 6, 2005 9:17 AM

    大侠可以写一篇关于Flash RECOVERY AREA的文章吗?

    Posted by: kingheap at December 9, 2005 12:40 AM

    简单的写了一点:
    http://www.eygle.com/archives/2005/12/oracle10g_flash_recovery_area_space_management.html

    Posted by: eygle at December 9, 2005 10:50 AM

    发表留言:



    Remember Me?
    (输入验证码后方可评论,谢谢支持)



    CopyRight © 2004~2010 eygle.com, All rights reserved.