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.)
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 188.8.131.52, 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.