What I did to the tables is like below. I tried to delete tables several times consecutively, because the tables still remained undeleted. And, before trying to delete the table, I had tried to upload data into the tables through the function "SYSCS_UTIL.SYSCS_IMPORT_TABLE" and failed because the table attributes and data were not corresponded, so I tried several times to do the same uploading work as I corrected the problems.
Now, the tables are locked as you said. I can find the lock file in the database directory. And, my derby.log file reads like below. ======== begin of derby.log Server is ready to accept connections on port 1527. Connection number: 1. ---------------------------------------------------------------- 2007-05-15 18:30:33.937 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.1.3.1 - (417277): instance c013800d-0112-9101-7aa7-00003e7c6227 on database directory C:\Documents and Settings\Hyunki Chung\.netbeans-derby\NetBlockFlixster Database Class Loader started - derby.database.classpath='' ======== end of derby.log Francois Orsini wrote: > > The lock is to prevent more than 1 Derby instance to access the same > database on Disk - You cannot have 2 Derby engine instances accessing the > same database at the same time. Since you're running in client-server > mode, > you should be good unless you may have attempted to access the database in > embedded mode as well, but the database lock should have prevented > this...Have you noticed any stack traces related to this reported error in > the derby.log file? > > On 5/15/07, hk <[EMAIL PROTECTED]> wrote: >> >> >> Thank for your intest in my problem. >> >> I'm accessing derby through Client-Server mode. >> If lock is the cause of the problem, how can I release the lock? >> >> >> >> Francois Orsini wrote: >> > >> > How are you accessing Netbeans from Netbeans? in Embedded or >> Client-Server >> > mode? You might want to check derby.log file to see if there is any >> > stacktrace(s) relevant to this error...Also, are you by any chance >> > accessing >> > the same database from some other Derby instance? there should be a >> lock >> > file preventing this but I have issues with this, especially with a >> > database >> > opened and accessed from different classloaders...Just food for >> > thoughts.... >> > >> > On 5/14/07, hk <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> While I was trying to delete tables through "Execute command screen" >> of >> >> Netbeans, I got an error message saying >> >> "The coglomerate (27265) requested does not exist." >> >> >> >> -- >> >> View this message in context: >> >> http://www.nabble.com/can%27t-delete-table-tf3754439.html#a10610657 >> >> Sent from the Apache Derby Users mailing list archive at Nabble.com. >> >> >> >> >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/can%27t-delete-table-tf3754439.html#a10617690 >> Sent from the Apache Derby Users mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/can%27t-delete-table-tf3754439.html#a10628755 Sent from the Apache Derby Users mailing list archive at Nabble.com.
