Re: Derby database started in READ ONLY mode Ram T Tue Feb 07 00:00:22 2012
Hi All, Finally i could able to reproduce the issue with below steps. I have filled all the memory on the disk with placing temporary files. And restarted the derby, then some of the databases are started normally, and some of the databases are started in READ ONLY mode. I have performed drop command with connecting to the derby using ij command. i got the same error DDL is not permitted. Then i have free the memory on disk and restarted the derby. Now i have verified with performing the same command on the same db. Now the table got deleted as expected without any issues. Thanks for you response. Bryan Pendleton-3 wrote: > >>>> =========== java.io.IOException: No space left on device at >>>> sun.nio.ch.FileDispatcher.pwrite0(Native Method) at > > Also check if your database is located on a FAT-32 filesystem or > similar, where database files are limited by the filesystem to > a max 2GB size. > > Similar things can happen with operating system quotas; the > operating system can refuse you from writing any more data to > the filesystem even though the overall filesystem itself may > not be full, if you have reached your quota. > > thanks, > > bryan > > -- View this message in context: http://old.nabble.com/Derby-database-started-suddenly-in-READ-ONLY-mode-tp33271488p33276887.html Sent from the Apache Derby Users mailing list archive at Nabble.com.
- Derby database started in READ ONLY mode Ram T 2012/02/06