Search Blog Post

Wednesday, December 11, 2013

ORA-00001: unique constraint (SYS.I_STMT_AUDIT_OPTION_MAP) violated

Problem:

While upgrading my 11.1.0.7 database to 11.2.0.2 (RHEL platform), I see that utlu112s shows violated constraints:

SQL> @utlu112s.sql
.
Oracle Database 11.2 Post-Upgrade Status Tool        12-11-2013 04:40:42
.
Component                Current      Version     Elapsed Time
Name                    Status         Number     HH:MM:SS
.
Oracle Server
.   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
.   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
.   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
.   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
.   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
.   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_SYSTEM_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
.   ORA-01408: such column list already indexed
.                      VALID      11.2.0.3.0  00:10:27
JServer JAVA Virtual Machine
.                      VALID      11.2.0.3.0  00:00:00
Oracle Real Application Clusters
.                    INVALID      11.2.0.3.0  00:00:00
OLAP Analytic Workspace
.                      VALID      11.2.0.3.0  00:00:00
OLAP Catalog
.                      VALID      11.2.0.3.0  00:00:00
Oracle OLAP API
.                      VALID      11.2.0.3.0  00:00:00
Oracle XDK
.                      VALID      11.2.0.3.0  00:00:00
Oracle Text
.                      VALID      11.2.0.3.0  00:00:00
Oracle XML Database
.                      VALID      11.2.0.3.0  00:00:00
Oracle Database Java Packages
.                      VALID      11.2.0.3.0  00:00:00
Oracle Multimedia
.                      VALID      11.2.0.3.0  00:00:00
Spatial
.                      VALID      11.2.0.3.0  00:00:00
Gathering Statistics
.                                 00:03:12
Total Upgrade Time: 00:13:46

PL/SQL procedure successfully completed.

 Cause:
I followed the note "*Complete Checklist for Manual Upgrades to 11gR2 [ID 837570.1]*"
. I ran the script catupgrd.sql 2 times because the first time it failed due to some bad OS parameters. After modifying OS parameter I relaunched the catupgrd.sql and the upgrade completed successfully.

It seems we can ignore the error as it is just an unique constraint error (trying to insert the rows already existing since I ran the upgrade script twice)..

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.

No comments:

Post a Comment