The stack in derby.log is interesting , I do see a run() method in
RafContainer.java.
1) Are u running under security manager ?
2) What JVM & OS are u using ?
3) Are u able to reproduce this problem with a simple set of SQL
statements not the whole application ?
Could u please post the output of the following command :
java org.apache.derby.tools.sysinfo
Thanks
-suresht
Peart, David E. wrote:
find attached the derby.log I don't know if this will offer any
additional insight.
------------------------------------------------------------------------
*From:* Satheesh Bandaram [mailto:[EMAIL PROTECTED]
*Sent:* Tuesday, August 16, 2005 1:19 PM
*To:* Derby Discussion
*Subject:* Re: Error when running a delete all a 2nd time
I think Army has already answered this question...Since there is a
primary key on the column, Derby would have created an unique index on
it, so attempting to create another unique index on the same column
would raise the warning. Why it is a warning and not an error, I don't
know :-) (since it doesn't actually create the second index...)
So your first problem is not related to this one...
Satheesh
Peart, David E. wrote:
Satheesh
when you say a complete reproduction you mean all code, etc?
Anyway, I'm also getting this error on creating indexes, may be it is
related. So I'd like to see if this was resolved then see if the
other problem goes away.
The problem is:
WARNING 01504: The new index is a duplicate of an existing index:
SQL050816084652910.
But its not a duplicate. It creates this warning on the 2nd index
PARGRP.X2FTNRC2
Additionally, although its a warning it does not create the 2nd index
!!!!! I checked the system tables for which indexes are created.
Let me know if you need the ddl on the table again, and may be you can
try creating the table with the three indexes and see if you get the
same error.
Note: we are loading the tables onto DB2 and have no issues there.
Here is the ddl script for creating the indexes
CREATE UNIQUE
INDEX PARGRP.X1FTNRC2
ON PARGRP.FTNREC2_CATCTRL
(CARRIER_CD ASC
,TARIFF_CD ASC
,FOOTNOTE_CD ASC
,CATEGORY_NO ASC
,SEQUENCE_NO ASC
,CREATE_TS ASC
);
CREATE UNIQUE
INDEX PARGRP.X2FTNRC2
ON PARGRP.FTNREC2_CATCTRL
(FTNREC2_SG ASC
);
CREATE
INDEX PARGRP.X3FTNRC2
ON PARGRP.FTNREC2_CATCTRL
(BATCH_CI ASC
,BATCH_NO ASC
);
David
------------------------------------------------------------------------
*From:* Satheesh Bandaram [mailto:[EMAIL PROTECTED]
*Sent:* Friday, August 12, 2005 3:20 PM
*To:* Derby Discussion
*Subject:* Re: Error when running a delete all a 2nd time
Hi Peart,
The error is really strange... I can't spot what could be causing the
problem here. Would it be possible for you to make a complete
reproduction?
Satheesh
Peart, David E. wrote:
I'm getting the following internalError when I try and delete from a
table after I have populated it. Has anybody seen this error or know
whats causing it. It only happens with this table (find the ddl
attached), other tables are fine
I've using this to do some TDD.
a) So I delete the contents of the table in a class setup
b) load the data
c) after all tests have run, delete the contents of the table
It's during the 'c' step this occurs, and after I get this any
attempt to delete from the table produces this error.
Any help would be appreciated as this is driving me crazy.
MessageID = "XJ001.U"
SQLState = "XJ001"
net.atpco.common.dataaccess.errors.DataAccessApplicationException:
unexpected error occurred in attempt to execute SQL: Java exception:
'No run method: java.lang.InternalError'.;
Caused by -->
java.lang.InternalError: No run method
at
org.apache.derby.impl.sql.execute.DeleteCascadeResultSet.open(DeleteCascadeResultSet.java)
at
org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java)
at
org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java)
at
org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(EmbedPreparedStatement.java)
at
org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(EmbedPreparedStatement.java)
at
net.atpco.rules.footnotes.server.dataaccess.MockJDBCDAO.createUpdateDelete(MockJDBCDAO.java:393)
at
net.atpco.rules.footnotes.server.dataaccess.MockJDBCDAO.delete(MockJDBCDAO.java:442)
at
net.atpco.rules.footnotes.server.dataaccess.FootNotesJDBCDAOFake.delete(FootNotesJDBCDAOFake.java:93)
at
net.atpco.rules.footnotes.server.dataaccess.GenericFootNotesJDBCDAO.delete(GenericFootNotesJDBCDAO.java:208)
at
net.atpco.rules.footnotes.server.dataaccess.GenericFootNotesDaSvc.delete(GenericFootNotesDaSvc.java:148)
at
net.atpco.rules.footnotes.server.dataaccess.GenericFootNotesDaSvc.delete(GenericFootNotesDaSvc.java:152)
at
net.atpco.rules.footnotes.server.dataaccess.FootNotesDaSvcTest.deleteSeedData(FootNotesDaSvcTest.java:207)
at
net.atpco.rules.footnotes.server.dataaccess.FootNotesDaSvcTest$1.setUp(FootNotesDaSvcTest.java:41)
at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:329)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:218)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:151)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:151)
