My Oracle Support Banner

Oracle VM Manager Database Corrupted with Error ' Duplicate entry '1506903609965' for key 'PRIMARY'" (Doc ID 2327898.1)

Last updated on FEBRUARY 02, 2019

Applies to:

Oracle VM - Version 3.4.3 to 3.4.4 [Release OVM34]
Oracle Cloud Infrastructure - Version N/A and later
Linux x86-64

Symptoms

Oracle VM manager database was found to be corrupted. Error messages are show as below in Oracle VM Manager logs:

 

<26/10/2017 3:29:08 PM AWST> <Warning> <oracle.adf.share.http.ServletADFContext> <BEA-000000> <Found wrong applicationScope sticking to oldContext for ovm_console, while the current one is ovm_help>
[EL Warning]: 2017-10-26 15:43:31.133--UnitOfWork(17257065)--Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '1506903609965' for key 'PRIMARY'
Error Code: 1062
Call: INSERT INTO OVM_JOB (ID, ABORTEDBYUSER, DEBUGTRANSCRIPT, DESCRIPTION, ENDTIME, ERRORMESSAGE, ERRORTYPE, JOBGROUP, NAME, PARENTJOB, RESULTCLASS, RESULTID, RUNSTATE, STARTTIME, SUMMARYSTATE, USERNAME) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) bind => [16 parameters bound] Query: InsertObjectQuery(com.oracle.ovm.mgr.api.job.JobEntity@44becf4c)

 

 Also resource limitation is found below:


<2017-10-02T08:15:48.170+0800> <Warning> <JDBC> <BEA-001153> <Forcibly releasing inactive/harvested connection "weblogic.jdbc.wrapper.PoolConnection_com_mysql_jdbc_JDBC4Connection@1d7d89f0" back into the data source connection pool "ovm-qrtz-ds", currently reserved by: reclaimed because of init failure before user access. Not because of inactivity..>
<2017-10-02T08:15:48.172+0800> <Error> <com.oracle.appfw.common.tasks.SchedulerImpl> <BEA-000000> <Unable to shutdown Scheduler. Failed to obtain DB connection from data source 'ovm-qrtz-ds': java.sql.SQLException: Could not retrieve datasource via JNDI url 'ovm-qrtz-ds' java.sql.SQLException: Failed to setAutoCommit to true for pool connection: First we got No operations allowed after connection closed., then we got No operations allowed after connection closed.>

 

 

 

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
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.