RMAN-03009&ORA-04030备份失败

于 2010-01-27 10:51:18 发布
阅读量386 收藏
点赞数

Recovery Manager: Release 11.1.0.6.0 - Production on Tue Jan 26 01:00:34 2010

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

connected to target database: gjj (DBID=2083925150)
using target database control file instead of recovery catalog

RMAN> run 
2> {
3> allocate channel t1 type 'sbt_tape' connect * parms 
4> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
5> 
6> allocate channel t2 type 'sbt_tape' connect * parms 
7> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
8> 
9> backup incremental level=0 tag "level0_BACKUP" format "DB_%d_%s_%I_%T_%t_%U.bak" database include current controlfile spfile;
10> 
11> sql "alter system archive log current";
12> 
13> backup tag "LOG_BACKUP" format "LOG_%d_%s_%I_%T_%t_%U.bak" archivelog all delete input skip inaccessible;
14> 
15> release channel t1;
16> release channel t2;
17> }
18> 
19> 
allocated channel: t1
channel t1: SID=900 instance=gjj1 device type=SBT_TAPE
channel t1: Data Protection for Oracle: version 5.5.1.0

allocated channel: t2
channel t2: SID=885 instance=gjj2 device type=SBT_TAPE
channel t2: Data Protection for Oracle: version 5.5.1.0

Starting backup at 26-JAN-10
channel t1: starting incremental level 0 datafile backup set
channel t1: specifying datafile(s) in backup set
input datafile file number=00001 name=/dev/rgjj_system
input datafile file number=00003 name=/dev/rgjj_undotbs1
input datafile file number=00005 name=/dev/rgjj_undotbs2
input datafile file number=00007 name=/dev/rgjj_data_02
channel t1: starting piece 1 at 26-JAN-10
channel t2: starting incremental level 0 datafile backup set
channel t2: specifying datafile(s) in backup set
input datafile file number=00002 name=/dev/rgjj_sysaux
input datafile file number=00004 name=/dev/rgjj_users
input datafile file number=00006 name=/dev/rgjj_data_01
channel t2: starting piece 1 at 26-JAN-10
channel t1: finished piece 1 at 26-JAN-10
piece handle=DB_gjj_866_2083925150_20100126_709261264_r2l4ctug_1_1.bak tag=LEVEL0_BACKUP comment=API Version 2.0,MMS Version 5.5.1.0
channel t1: backup set complete, elapsed time: 00:08:46
channel t1: starting incremental level 0 datafile backup set
channel t1: specifying datafile(s) in backup set
including current control file in backup set
channel t1: starting piece 1 at 26-JAN-10
channel t2: finished piece 1 at 26-JAN-10
piece handle=DB_gjj_867_2083925150_20100126_709261248_r3l4ctu0_1_1.bak tag=LEVEL0_BACKUP comment=API Version 2.0,MMS Version 5.5.1.0
channel t2: backup set complete, elapsed time: 00:16:42
channel t2: starting incremental level 0 datafile backup set
channel t2: specifying datafile(s) in backup set
including current SPFILE in backup set
channel t2: starting piece 1 at 26-JAN-10
channel t1: finished piece 1 at 26-JAN-10
piece handle=DB_gjj_868_2083925150_20100126_709261800_r4l4cuf8_1_1.bak tag=LEVEL0_BACKUP comment=API Version 2.0,MMS Version 5.5.1.0
channel t1: backup set complete, elapsed time: 00:10:52
channel t1: starting incremental level 0 datafile backup set
channel t1: specifying datafile(s) in backup set
including current SPFILE in backup set
channel t1: starting piece 1 at 26-JAN-10
channel t2: finished piece 1 at 26-JAN-10
piece handle=DB_gjj_869_2083925150_20100126_709262250_r5l4cuta_1_1.bak tag=LEVEL0_BACKUP comment=API Version 2.0,MMS Version 5.5.1.0
channel t2: backup set complete, elapsed time: 00:06:10
RMAN-03009: failure of backup command on t1 channel at 01/26/2010 01:26:47
ORA-04030: out of process memory when trying to allocate 86040 bytes (pga heap,control file i/o buffer)
channel t1 disabled, job failed on it will be run on another channel
channel t2: starting incremental level 0 datafile backup set
channel t2: specifying datafile(s) in backup set
including current SPFILE in backup set
channel t2: starting piece 1 at 26-JAN-10
channel t2: finished piece 1 at 26-JAN-10
piece handle=DB_gjj_871_2083925150_20100126_709262807_r7l4cven_1_1.bak tag=LEVEL0_BACKUP comment=API Version 2.0,MMS Version 5.5.1.0
channel t2: backup set complete, elapsed time: 00:03:25
Finished backup at 26-JAN-10

sql statement: alter system archive log current

Starting backup at 26-JAN-10
current log archived
archived log /arch/1_459_700774689.dbf not found or out of sync with catalog
skipping inaccessible file /arch/1_459_700774689.dbf
archived log /arch/1_460_700774689.dbf not found or out of sync with catalog
skipping inaccessible file /arch/1_460_700774689.dbf
archived log /arch/1_461_700774689.dbf not found or out of sync with catalog
skipping inaccessible file /arch/1_461_700774689.dbf
RMAN-06061: WARNING: skipping archived log compromises recoverability
channel t2: starting archived log backup set
channel t2: specifying archived log(s) in backup set
input archived log thread=2 sequence=333 RECID=795 STAMP=709263015
input archived log thread=2 sequence=334 RECID=797 STAMP=709263023
channel t2: starting piece 1 at 26-JAN-10
channel t2: finished piece 1 at 26-JAN-10
piece handle=LOG_gjj_872_2083925150_20100126_709263033_r8l4cvlp_1_1.bak tag=LOG_BACKUP comment=API Version 2.0,MMS Version 5.5.1.0
channel t2: backup set complete, elapsed time: 00:00:45
channel t2: deleting archived log(s)
archived log file name=/arch/2_333_700774689.dbf RECID=795 STAMP=709263015
archived log file name=/arch/2_334_700774689.dbf RECID=797 STAMP=709263023
Finished backup at 26-JAN-10

released channel: t1
released channel: t2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of release command at 01/26/2010 01:31:18
RMAN-06012: channel: t1 not allocated

Recovery Manager complete.



RMAN-03009: failure of backup command on t1 channel at 01/26/2010 01:26:47
ORA-04030: out of process memory when trying to allocate 86040 bytes (pga heap,control file i/o buffer)
channel t1 disabled, job failed on it will be run on another channel
奇怪备份一直正常为什么会报内存不足呢。



http://blog.youkuaiyun.com/newchengse/archive/2005/03/10/316543.aspx

ORA-4030意味着什么？

    这个错误意味着oracle服务器进程不能从操作系统获得更多的内存。这里的内存指的是PGA(程序全局区)以及由配置决定的它的子项。对于专用的服务器进程，内存包括堆栈区、UGA（用户全局区）。UGA包括用户会话数据、游标信息和排序区。在多线程配置中（共享服务器），UGA处于SGA（系统全局区）中，它不会造成ora-4030错误。

    因此，ora-4030意味着进程需要更多的内存（堆栈、UGA或者PGA）来执行它的工作。

是什么引起了这个错误？

这个错误表示操作系统不能分配足够的内存。这个错误可能是你的进程本身引起的，例如你的进程需要太多的内存，或者其它的原因引起操作系统内存枯竭，例如SGA区分得太大或者太多的进程竞争系统虚拟内存（物理内存＋交换分区）。许多操作系统会限制某个进程获得的内存以保证系统稳定。

请按以下步骤检查你的系统：

·       是否仍有足够的内存供分配？

·       操作系统是否有限制？

·       Oracle数据库是否有限制？

·       哪一个进程需要过多的内存？

·       如何收集那个（需要过多内存的）进程正在做什么的信息？

这些将在下一节里讨论。

进一步讨论主题：

·       避免此类错误的一般建议



# su - oracle
$ ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited
stack(kbytes)        unlimited
memory(kbytes)       unlimited
coredump(blocks)     unlimited
nofiles(descriptors) unlimited
threads(per process) unlimited
processes(per user)  unlimited


# ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         262144
stack(kbytes)        262144
memory(kbytes)       262144
coredump(blocks)     2097151
nofiles(descriptors) 2000
threads(per process) unlimited
processes(per user)  unlimited



来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/11134849/viewspace-626124/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/11134849/viewspace-626124/

cite7656271
关注
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值