Cannot Insert On Database After Installing Patch OHMPI 2.0.11 (Doc ID 2165331.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Healthcare Master Person Index - Version 2.0.9 and later
Information in this document applies to any platform.

Symptoms

OHMPI 2.0.11

After applying the OHMPI 2.0.11 patch, can no longer insert data on OHMPI DB using web services and MIDM. The problem is associated with the primary key that starts over 0, ignoring the records already saved.

The log displays the following error:

SEVERE: MDM-MI-MSC582: MasterControllerImpl encountered a ProcessingException: name=com.sun.mdm.index.audit.AuditException, message=MDM-MI-AUD500: Audit Log record could not be inserted: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DBCADSUSMPI.PK_SBYN_AUDIT) violated
, stack trace=
com.sun.mdm.index.audit.AuditManager.insertAuditLog(AuditManager.java:101)
com.sun.mdm.index.ejb.master.MasterControllerCoreImpl.insertAuditLog(MasterControllerCoreImpl.java:2040)
com.sun.mdm.index.ejb.master.MasterControllerEJB.insertAuditLog(MasterControllerEJB.java:3599)

It reproduces with any operation that triggers a insert operation. Example: Audit operation when open details from "record details" search in MIDM. For example:

1) The MIDM can not perform any operation which triggers auditing.
2) The web service can not insert data. Only MIDM operations can generate audit logs, the web service does not create audit logs. The unique constraint violation on PK_SBYN_AUDIT could be only resulted from MIDM operations.

Changes

 This issue started after applying new patch 2.0.11.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms