My Oracle Support Banner

"java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint " while Creating any Model or Glossary in OEMM (Doc ID 2525820.1)

Last updated on SEPTEMBER 10, 2021

Applies to:

Oracle Enterprise Metadata Management - Version 12.2.1.2 and later
Information in this document applies to any platform.

Symptoms

When trying to create any type of Model or Glossary in Oracle Enterprise Metadata Management (OEMM) the following error is seen:


[5455/[SasBiImport, MetaIntegrationMul] 2019-03-26 13:07:17 BLIB_I0118 MITI component(s) with build version '10.0.0 - 2018-10-10': MIMBWebServices.jar, MIMBWebServices.jar, MIMBWebServices.jar, MIMBWebServices.jar, MIMBWebServices.jar, MIMBWebServices.jar

[5455/Import model version] 2019-03-26 13:07:19 DBUTL_E0008 A Fatal database exception occured. Please contact technical support with the following information and server logs. Database error code: 1, Message: ORA-00001: unique constraint (<OEMM_SCHEMA_NAME>.PK_CLASS) violated
.
java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (<OEMM_SCHEMA_NAME>.PK_CLASS) violated

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1059)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:522)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:257)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:587)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:225)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:53)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:943)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1150)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:4798)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:4875)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1361)
at MITI.util.database.Update.executeStatement(Update.java:39)
at MITI.util.database.Statement.execute(Statement.java:53)
at MITI.util.database.Transaction.executeStatement(Transaction.java:53)
at MITI.util.database.CommonDataSource.executeStatement(CommonDataSource.java:35)
at MITI.server.services.repository.impl.RepositoryImpl$1.run(RepositoryImpl.java:1159)
at MITI.server.services.repository.impl.RepositoryImpl$1.run(RepositoryImpl.java:1104)
at MITI.util.database.Transaction.execute(Transaction.java:87)
at MITI.util.database.CommonDataSource.executeTransaction(CommonDataSource.java:69)
at MITI.server.services.repository.impl.RepositoryImpl.createInternal(RepositoryImpl.java:1179)
at MITI.server.services.repository.impl.RepositoryImpl.createInternal(RepositoryImpl.java:1083)
at MITI.server.services.repository.impl.RepositoryImpl.createVersion(RepositoryImpl.java:1058)
at MITI.server.services.operation.impl.thread.StoreModel.createVersion(StoreModel.java:327)
at MITI.server.services.operation.impl.thread.StoreModel.execute(StoreModel.java:213)
at MITI.server.services.operation.impl.thread.ImportModel.execute(ImportModel.java:122)
at MITI.server.services.operation.internal.OperationThread.run(OperationThread.java:93)


Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.