10.2upgrade to11.2在运行catupgrd后，发现ORA-00001

qhd2004

os:rhel5.4
db：从10.2.0.5 升级到11.2.0.4

运行catupgrd.sql时出现情况：
第一次是没运行utlu112i.sql （我故意的，想看1722报错）
第二次运行时报错：sga小于240m（我在虚机做的测试，没改参数）
第三次运行时空间占满（归档模式，我想看产生归档数量是不是很多）

第四次是：运行utlu112i.sql、加大sga、非归档模式下运行，完成后，检查日志发现很多ora-00001，如下：
ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated
ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_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.I_TABLE_PRIVILEGE_MAP) violated
ORA-00001: unique constraint (SYS.I_STMT_AUDIT_OPTION_MAP) violated
ORA-00001: unique constraint (SYS.I_STMT_AUDIT_OPTION_MAP) violated
ORA-00001: unique constraint (SYS.I_STMT_AUDIT_OPTION_MAP) violated

根据文档：
11gr2 Upgrade, Re-Running catupgrd.sql Causes Ora-00001 Errors (文档 ID 1100828.1)
说这个可以忽略

我想问的是：
1.如果在生产上，正常升级（不看上面想看的那些），如果出现ora-00001，那升级后的库是否可用？
2.出现ora-00001后我该如何入手解决呢？？

Maclean Liu(刘相兵

就现有的SR 反馈来看 确实可以被忽略，也没有用户反映这个有什么后续影响。

Maclean Liu(刘相兵

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

Maclean Liu(刘相兵

ODM FINDING:
No need to execute the post upgrade script ( utlu112s.sql) ,it will be executed as part of upgrade process (during catupgrd.sql execution)

ORA-00001: unique constraint (SYS.I_SYSTEM_PRIVILEGE_MAP) violated is ignorable

if you find ORDIM INVALID ,execute utlrp.sql multiple times