Rman一直卡住。无法执行，请求帮助。

dexter

今天碰到了一个奇怪的现象
三节点 AIX+CFS+OracleDatabase11.1.0.6 RAC

使用rman测试备份一个控制文件的时候
卡在这里一直没有反应
Starting backup at 08-JAN-13
using channel ORA_DISK_1

看v$session_wait视图
只有 db file sequential read 并且 wait_time=-1


不知道下一步应该怎样监控

Maclean Liu(刘相兵

run
{
debug on
YOUR SCRIPT;
debug off;}



or  


10046 trace your rman session


or

v$session_longops

wind

挺好，再复习一遍

dexter

Maclean Liu(刘相兵 发表于 2013-1-8 19:19
run
{
debug on

第一个节点执行，使用debug方式：

1. bash-3.00$ rman target / trace rman.trc debug
   
2. 
   
3. Recovery Manager: Release 11.1.0.6.0 - Production on Tue Jan 8 19:50:12 2013
   
4. 
   
5. Copyright (c) 1982, 2007, Oracle.  All rights reserved.
   
6. 
   
7. RMAN-06005: connected to target database: LANDDB (DBID=3198567539)
   
8. 
   
9. RMAN> run{
   
10. 2> debug on
    
11. 3> backup current controlfile format '/ysysdata/ctl_test.bkp' ;
    
12. 4> debug off
    
13. 5> }
    
14. 
    
15. RMAN-03036: Debugging set to level=9, types=ALL
    
16. 
    
17. RMAN-03090: Starting backup at 08-JAN-13
    
18. RMAN-06009: using target database control file instead of recovery catalog
    
19. RMAN-08030: allocated channel: ORA_DISK_1
    
20. RMAN-08605: channel ORA_DISK_1: SID=283 instance=landdb1 device type=DISK
    

复制代码

第二个使用10046事件监控：

1. bash-3.2$ rman target / trace rman46.trc debug
   
2. 
   
3. Recovery Manager: Release 11.1.0.6.0 - Production on Tue Jan 8 20:13:41 2013
   
4. 
   
5. Copyright (c) 1982, 2007, Oracle.  All rights reserved.
   
6. 
   
7. RMAN-06005: connected to target database: LANDDB (DBID=3198567539)
   
8. 
   
9. RMAN> run{
   
10. 2> sql "alter session set events ''10046 trace name context forever , level 12 ''" ;
    
11. 3> set command id to 'rman' ;
    
12. 4> backup current controlfile format '/home/oracle/ctltest.bkp' ;
    
13. 5> }
    
14. 
    
15. RMAN-06009: using target database control file instead of recovery catalog
    
16. RMAN-06162: sql statement: alter session set events ''10046 trace name context forever , level 12 ''
    
17. 
    
18. RMAN-03023: executing command: SET COMMAND ID
    
19. 
    
20. RMAN-03090: Starting backup at 08-JAN-13
    
21. RMAN-08030: allocated channel: ORA_DISK_1
    
22. RMAN-08605: channel ORA_DISK_1: SID=285 instance=landdb2 device type=DISK

复制代码

详细trace文件见附件
rman_trace.rar (39.48 KB, 下载次数: 2068)

2013-1-9 10:37 上传

点击文件名下载附件

请帮忙分析。

dexter

请求帮助

Maclean Liu(刘相兵

这个问题可能与你相关：

RMAN BACKUPS CAN TAKE A LONG TIME IN 11.1.0.6 [ID 605557.1]




                RMAN BACKUPS CAN TAKE A LONG TIME IN 11.1.0.6 [ID 605557.1]        To Bottom       
Modified:27-Dec-2011Type:PROBLEMStatus:PUBLISHEDPriority:3       
Comments (0)                               

In this Document
  Symptoms
  Cause
  Solution
  References

Applies to:

Oracle Server - Enterprise Edition - Version: 11.1.0.6 to 11.1.0.6 - Release: 11.1 to 11.1
Information in this document applies to any platform.
***Checked for relevance on 27-Dec-2011***
Symptoms

RMAN backups can take a long time in 11.1.0.6.

An increase in memory used by logminer may also be noticed. In once case, the ORA-4030 errors were reported, and lead to a database crash

This problem can affect all platforms. Additionally, 3 of the reports have been for customers with PeopleSoft installed.
Cause

This is caused by bug <<6412947>>.
Solution

To workaround the problem, switch off the logminer setup for DRA by setting:

  _dra_enable_offline_dictionary = FALSE


建议你升级到11.1.0.7

dexter

Maclean Liu(刘相兵 发表于 2013-1-9 21:13
这个问题可能与你相关：

RMAN BACKUPS CAN TAKE A LONG TIME IN 11.1.0.6

正是这个问题，感谢maclean！