ORA-19583/ORA-27206/ORA-06512

发表于 2012 年 2 月 2 日 由 惜分飞

联系：手机/微信(+86 17813235971) QQ(107644445)QQ咨询惜分飞

标题：ORA-19583/ORA-27206/ORA-06512

作者：惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

检查alert日志发现近期数据库出现了ORA-19583/ORA-27206/ORA-06512错误

Fri Dec 30 12:22:36 2011
Errors in file /oracle9/app/admin/ykcdb/udump/ykcdb_ora_5390564.trc:
ORA-19583: conversation terminated due to error
ORA-27206: requested file not found in media management catalog
ORA-06512: at "SYS.DBMS_BACKUP_RESTORE", line 625

进一步查看trace文件发现

Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
With the Partitioning option
JServer Release 9.2.0.7.0 - Production
ORACLE_HOME = /oracle9/app/product/9.2.0
System name:    AIX
Node name:      OFFON2
Release:        3
Version:        5
Machine:        000A36B8D600
Instance name: ykcdb
Redo thread mounted by this instance: 1
Oracle process number: 79
Unix process pid: 5390564, image: oracle@OFFON2 (TNS V1-V3)

*** 2011-12-30 12:22:36.051
*** SESSION ID:(32.62184) 2011-12-30 12:22:36.023
FATAL ERROR IN TWO-TASK SERVER: error = 12152
*** 2011-12-30 12:22:36.051
ksedmp: internal or fatal error
ORA-19583: conversation terminated due to error
ORA-27206: requested file not found in media management catalog
ORA-06512: at "SYS.DBMS_BACKUP_RESTORE", line 625
----- Call Stack Trace -----
calling              call     entry                argument values in hex      
location             type     point                (? means dubious value)     
-------------------- -------- -------------------- ----------------------------
ksedmp+0148          bl       ksedst               1025AE55C ?
opitsk+0968          bl       ksedmp               20289E71C ?
opiino+0798          bl       opitsk               000000000 ? 000000000 ?
opiodr+08c8          bl       _ptrgl               
opidrv+032c          bl       opiodr               3C00000018 ? 4101C7F40 ?
                                                   FFFFFFFFFFFF810 ? 0A03547C8 ?
sou2o+0028           bl       opidrv               3C0C000000 ? 4A039C2D0

查看mos发现[ID 558993.1]提供了错误原因和解决方案
错误原因：RMAN backup to tape using veritas netbackup，The MML parameters like NB_ORA_CLIENT and NB_ORA_SERV were not given in proper case while configuring channel in RMAN backup.
解决方法：The NB_ORA_CLIENT and NB_ORA_SERV MML parameters are case sensitive. So make sure to give these parameters in same case while allocating or configuring RMAN channel as it is configure in Veritas server.

此条目发表在 ORA-xxxxx 分类目录，贴了 , , 标签。将固定链接加入收藏夹。

《ORA-19583/ORA-27206/ORA-06512》有 1 条评论

  1. 惜 分飞 说：
    2012 年 2 月 2 日19:20

    Applies to

    Oracle Server - Enterprise Edition - Version: 9.2.0.7 and later [Release: 9.2 and later ]
Information in this document applies to any platform.
***Checked for relevance on 27-Dec-2011***

    Symptoms

    RMAN backup of database using Veritas MML failed with below errors:

released channel: T1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on T1 channel at 02/24/2008 09:26:47
RMAN-10032: unhandled exception during execution of job step 1:
ORA-19583: conversation terminated due to error
ORA-27206: requested file not found in media management catalog
ORA-06512: at "SYS.DBMS_BACKUP_RESTORE", line 625
ORA-06512: at line 579
RMAN-10035: exception raised in RPC:
ORA-19583: conversation terminated due to error
ORA-27206: requested file not found in media management catalog
ORA-06512: at "SYS.DBMS_BACKUP_RESTORE", line 625
RMAN-10031: RPC Error: ORA-19583 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE

    Cause

    The MML parameters like NB_ORA_CLIENT and NB_ORA_SERV were not given 
in proper case while configuring channel in RMAN backup. These parameters are case sensitive.
RMAN>ALLOCATE CHANNEL ch00 TYPE sbt_tape;
send 'NB_ORA_CLIENT=<NetBackup_client> NB_ORA_SERV=<NetBackup_master_server>';

    Solution

    The NB_ORA_CLIENT and NB_ORA_SERV MML parameters are case sensitive. 
So make sure to give these parameters in same case while allocating or configuring RMAN channel as it is configure in Veritas server.