[
https://issues.apache.org/jira/browse/DERBY-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164683#comment-13164683
]
Kathey Marsden commented on DERBY-5315:
---------------------------------------
Mike mentioned to me also:
You may want to check that it is not a multiple user of single connection
commit issue. temp congloms can be affected by commits.
> "The conglomerate (-8) requested does not exist" during batch insert into
> temporary table
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-5315
> URL: https://issues.apache.org/jira/browse/DERBY-5315
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.8.1.2
> Environment: Embedded Derby, Oracle JDK 1.6.0_23
> Reporter: Thomas Brandl
>
> While executing this insert statement (TAG_VALUE_TEMP is a temporary table,
> inserts are done as batch inserts):
> INSERT INTO TAG_VALUE_TEMP (TAG_TYPE_ID, VALUE, CNT, ID) VALUES (?, ?, ?, ?)
> we got the following exception:
> Caused by: java.sql.SQLException: The conglomerate (-8) requested does not
> exist.
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeBatchElement(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeBatch(Unknown
> Source)
> at
> org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297)
> at
> org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297)
> at
> org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297)
> at
> com.dynatrace.diagnostics.repository.util.DefaultMeasureKeyCache$DynamicMeasureIDCallback.execute(DefaultMeasureKeyCache.java:863)
> at
> com.dynatrace.diagnostics.repository.statement.DefaultStatementExecutor.writeOnTransactionalConnection(DefaultStatementExecutor.java:73)
> ... 9 more
> Caused by: java.sql.SQLException: The conglomerate (-8) requested does not
> exist.
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
> Source)
> ... 23 more
> Caused by: ERROR XSAI2: The conglomerate (-8) requested does not exist.
> at org.apache.derby.iapi.error.StandardException.newException(Unknown
> Source)
> at
> org.apache.derby.impl.store.access.RAMTransaction.findExistingConglomerate(Unknown
> Source)
> at
> org.apache.derby.impl.store.access.RAMTransaction.getDynamicCompiledConglomInfo(Unknown
> Source)
> at org.apache.derby.impl.sql.execute.DMLWriteResultSet.<init>(Unknown
> Source)
> at org.apache.derby.impl.sql.execute.DMLWriteResultSet.<init>(Unknown
> Source)
> at org.apache.derby.impl.sql.execute.InsertResultSet.<init>(Unknown
> Source)
> at
> org.apache.derby.impl.sql.execute.GenericResultSetFactory.getInsertResultSet(Unknown
> Source)
> at
> org.apache.derby.exe.acd3394189x0130xad24x5036x00002df6f4087.fillResultSet(Unknown
> Source)
> at
> org.apache.derby.exe.acd3394189x0130xad24x5036x00002df6f4087.execute(Unknown
> Source)
> at org.apache.derby.impl.sql.GenericActivationHolder.execute(Unknown
> Source)
> at
> org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source)
> at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown
> Source)
> ... 17 more
> We only had this once in a pre-production-environment, reproducing it was not
> possible up to now.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
