[
https://issues.apache.org/jira/browse/DERBY-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314463#comment-14314463
]
Myrna van Lunteren commented on DERBY-6792:
-------------------------------------------
If there is no space issue then this is likely related to the other report we
had of a similar error.
So it is possible this started due to a bug, but we don't know for sure
until/unless we can have an idea of what the sequence of events is that trigger
this. There is no fix, nor a way to fix it.
Even if we had a fix for the possible bug, it would not fix the database.
I can see the following choices for you/your customer:
a. continue to limp with the database as is. It will not get better.
b. attempt to use the off line compress routine as I described before. There is
a possibility this would repair the database, but that is not guaranteed.
c. use a back-up.
d. create a new database.
at d: You *might* be able to salvage data from the old database by exporting
data from the database, or manually (e.g. using ij, or by writing a program)
selecting data from each table.
> Could not execute JDBC batch update
> -----------------------------------
>
> Key: DERBY-6792
> URL: https://issues.apache.org/jira/browse/DERBY-6792
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.8.3.3
> Environment: Derby 10.8.3.3, IBM JAVA 7 SR7, Linux
> Reporter: Raja
> Priority: Critical
> Attachments: Derby_error.txt, derby.log, derbyserver.out
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> We are using Derby v10.8.3.3 for our product CastIron. Our customer is
> getting the following error in their production environment.
> SEVERE [T-84] [job:96CC8CC6085B45D13583E180C1014E82]
> [com.approuter.maestro.vm.Task] Internal error:
> org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch
> update
> org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch
> update
> at
> org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)
> at
> org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)
> at
> org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
> at
> org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:253)
> at
> org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:92)
> at
> org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:87)
> at
> org.hibernate.jdbc.AbstractBatcher.prepareBatchStatement(AbstractBatcher.java:222)
> at
> org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2354)
> at
> org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2307)
> at
> org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2607)
> at
> org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:92)
> at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:250)
> at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:234)
> at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:142)
> at
> org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
> at
> org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
> at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
> at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338)
> at
> org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106)
> at
> com.approuter.maestro.opera.rdbms.RdbmsSession.commit(RdbmsSession.java:363)
> at com.approuter.maestro.vm.Task.commit(Task.java:1136)
> at com.approuter.maestro.activities.Invoke.persist(Invoke.java:280)
> at sun.reflect.GeneratedMethodAccessor278.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
> at java.lang.reflect.Method.invoke(Method.java:611)
> at
> com.approuter.maestro.activities.Instruction.call(Instruction.java:45)
> at com.approuter.maestro.vm.Program.call(Program.java:596)
> at com.approuter.maestro.vm.Task.run(Task.java:692)
> at com.approuter.maestro.vm.Task.run(Task.java:631)
> at
> com.approuter.maestro.vm.Program$RunnableWrapper.run(Program.java:2207)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:450)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
> at java.util.concurrent.FutureTask.run(FutureTask.java:149)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:109)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:217)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:761)
> ------------------------------
> Need quick analysis and solution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
