- 最后登录
- 2023-8-16
- 在线时间
- 1686 小时
- 威望
- 2135
- 金钱
- 50532
- 注册时间
- 2011-10-12
- 阅读权限
- 200
- 帖子
- 5207
- 精华
- 39
- 积分
- 2135
- UID
- 2
|
3#
发表于 2014-2-22 21:39:54
MORE FINDING:
During an Oracle RDBMS Upgrade from 10.2.0.4 to 11.2.0.3, got a number of errors from the “catupgrd” command.
ORA-00001: unique constraint (SYS.I_AUDIT_ACTIONS) violated
ORA-00001: unique constraint (SYS.I_SMB$CONFIG_PKEY) violated
ORA-00001: unique constraint (SYS.I_STMT_AUDIT_OPTION_MAP) violated
ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
ORA-00001: unique constraint (SYS.I_TABLE_PRIVILEGE_MAP) violated
ORA-00001: unique constraint (SYS.WRM$_BASELINE_PK) violated
ORA-04063: package body "SYS.DBMS_SESSION" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_SESSION"
ORA-06512: at line 1
ORA-06512: at line 23
CAUSE OF ISSUE
-----------------------------
This is the expected behavior as confirmed by development in the unpublished bugs
Bug 5501515 TST&PERF VIOLATED SOME TABLE'S UNIQUE CONSTRAINT WHILE UPGRADING TO 11G
Bug 8834797 APPSST GSI 11G UNIQUE CONSTRAINT VIOLATED WHILE RUNNING CATUPGRD
There are 11g specific configuration rows to be inserted in the dictionary tables during the upgrade. When running multiple times the post upgrade step, the same rows are inserted again, therefore the unique constraint keys are violated.
Solution
SOLUTION
----------------------------------
Unique constraint errors are expected and acceptable on re-run of catupgrd.sql or utlu111s.sql. These ORA-1 errors can be safely ignored and should not impact the upgrade process in anyway.
If still having issues with DBMS_SESSION then request CT to run dbmsutil.sql prvtutil.plb SYS
|
|