catalog.sql failing due to ORA-03135 or ORA-03113

刘泽宇

现象：
Catalog is failing due to below error

Grant succeeded.

create or replace package dbms_standard is
*
ERROR at line 1:
ORA-03135: connection lost contact
Process ID: 17078
Session ID: 1071 Serial number: 119


ERROR:
ORA-03114: not connected to ORACLE


ERROR:
ORA-03114: not connected to ORACLE
From 10046 trace we can see below error

WAIT #18446744071522704512: nam='SQL*Net break/reset to client' ela= 1 driver id=1650815232 break?=1 p3=0 obj#=-1 tim=34030812262970
WAIT #18446744071522704512: nam='SQL*Net break/reset to client' ela= 12 driver id=1650815232 break?=0 p3=0 obj#=-1 tim=34030812263033
WAIT #18446744071522704512: nam='SQL*Net break/reset to client' ela= 0 driver id=1650815232 break?=1 p3=0 obj#=-1 tim=34030812263089
WAIT #18446744071522704512: nam='SQL*Net break/reset to client' ela= 11 driver id=1650815232 break?=0 p3=0 obj#=-1 tim=34030812263152
WAIT #18446744071522704512: nam='SQL*Net break/reset to client' ela= 1 driver id=1650815232 break?=1 p3=0 obj#=-1 tim=34030812263207
WAIT #18446744071522704512: nam='SQL*Net break/reset to client' ela= 12 driver id=1650815232 break?=0 p3=0 obj#=-1 tim=34030812263270
opitsk: network error occurred while two-task server trying tosend break; error code = 12571    <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
CLOSE #18446744071522704512:c=3,e=3,dep=0,type=0,tim=34030812263602
CLOSE #18446744071522707688:c=4,e=5,dep=0,type=0,tim=34030812263669


原因
Database server has a security third party software called Guardium installed which had rules that did not allow some operations with the sys user
This behaviour is also discussed in Bug 33757864 - [NODP] OPITSK: NETWORK ERROR OCCURRED WHILE TWO-TASK SERVER TRYING TOSEND BREAK; ERROR CODE = 12571 WHILE RUNNING CATALOG SCRIPT
数据库服务器安装了名为Guardium的安全第三方软件，该软件的规则不允许与sys用户进行某些操作
Bug 33757864-[NODP]观点中也讨论了这种行为：当双任务服务器尝试终止时发生网络错误；运行目录脚本时错误代码=12571


处理方法：
Customer excluded the rules from third party tool with the help of their security team and issue was fixed.
客户在其安全团队的帮助下从第三方工具中排除了这些规则，问题得到了解决。