An ORA-600 is received whenever a rule is edited or run.
- The aveksaServer.log shows:
06/18/2019 14:12:00.409 ERROR (default task-1) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] ORA-00600: internal error code, arguments: [qmtcolcb_nomatch], [ID], [annotation], [], [], [], [], [], [], [], [], []
- The Oracle database alert.log for the remote AIX database shows:
2019-06-20T00:00:02.225706-05:00 Errors in file /u01/app/oracle/diag/rdbms/iamq/iamq/trace/iamq_ora_9044396.trc (incident=159659): ORA-00600: internal error code, arguments: [qmtcolcb_nomatch], [ID], [annotation], [], [], [], [], [], [], [], [], [] Incident details in: /u01/app/oracle/diag/rdbms/iamq/iamq/incident/incdir_159659/iamq_ora_9044396_i159659.trc 2019-06-20T00:00:17.386575-05:00 Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. 2019-06-20T00:00:17.446175-05:00 Errors in file /u01/app/oracle/diag/rdbms/iamq/iamq/trace/iamq_ora_9044396.trc: ORA-00600: internal error code, arguments: [qmtcolcb_nomatch], [ID], [annotation], [], [], [], [], [], [], [], [], [] 2019-06-20T00:00:17.535870-05:00
- The incident trace files show primarily two SQL statements affected: (See Oracle reference to Note 411.1 at My Oracle Support in the above error message for instructions on how to package the incident.)
ORA-00600: internal error code, arguments: [qmtcolcb_nomatch], [ID], [annotation], [], [], [], [], [], [], [], [], [] ----- Current SQL Statement for this session (sql_id=0suk6qsvtusbp) ----- insert into T_DATA_RUN_TASKS ("TYPE", "STATUS", "SOURCE", "SOURCE_TYPE", "SOURCE_CONTAINER", "INPUT_DATA_REF", "START_TIME", "END_TIME", "XMLDATA", "IS_REPROCESS", "USER_ID", "PREVIOUS_EXECUTION_ID", "INT_1", "STR_1", RUN_ID, "ID") values (:1 , :2 , :3 , :4 , :5 , :6 , :7 , :8 , :9 , :10 , :11 , :12 , :13 , :14 , :15 , :16 ) and update T_AV_RULES set "IS_DELETED"=:1 , "NAME"=:2 , "CREATED_BY"=:3 , "OWNER_ID"=:4 , "CREATION_DATE"=:5 , "CURRENT_VERSION_ID"=:6 , "DESCRIPTION"=:7 , "CTRL_DESC"=:8 , "CTRL_URL"=:9 , "LAST_EXECUTION_DATE"=:10 , "DEFINITION"=:11 , "STATUS"=:12 , "STATUS_DISPLAY_NAME"=:13 , "RULE_TYPE"=:14 , "RULESET_ID"=:15 , "TYPE_DISPLAY_NAME"=:16 , "SCOPE"=:17 , "SCOPE_ID"=:18 , "COVERED_USERS"=:19 , "USERS_WITH_VIOLATIONS"=:20 , "COVERED_ENTS_B1"=:21 , "COVERED_ENTS_B2"=:22 , "VIOLATION_COUNT"=:23 , "EXCEPTION_COUNT"=:24 , "SCHEDULE_TYPE"=:25 , "REMEDIATION_PROC_REF"=:26 , "IMPLEMENTATION"=:27 , "CONDITION_TEXT"=:28 , "CONDITION_HTML"=:29 , "SCHEDULE"=:30 where "ID"=:31
Please refer to article 000030327 - Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the log files for your specific deployment.
This is an underlying issue on the AIX platform, which is home to the Oracle database.
There is a problem with the operating system which affects the functioning of the XDB/XML component of the Oracle product, and therefore any SQL statements that touch on tables with columns of type XMLTYPE.
This happens after an upgrade of the Oracle database to 12.2.0.1, and the move from RSA Identity Governance & Lifecycle 7.1.0 P01 to the RSA Identity Governance & Lifecycle OVA 7.1.1 platform and version.
The Oracle upgrade may have caused old Oracle modules to be left in the system.
RSA Identity Governance & Lifecycle Support suggests customers follow the instructions in this post on
Setting your environment for Oracle XML Database (XDB) from the Oracle website.
After re-installing the XDB component and running
/usr/sbin/slibclean per the instructions in the above Oracle post, rules can be run and edited without error.
