You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-user@db.apache.org by tom_ <to...@web.de> on 2007/12/31 20:17:40 UTC
Failed to start database
Without having a crash or something like that before, when trying to reopen
the database the error message is "Failed to start database". Is there a
possibility to start the database again?
The complete error trace is
java.sql.SQLException: Failed to start database '/mydatabase', see the next
exception for details.
at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection40.<init>(Unknown Source)
at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)
at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
at org.apache.derby.jdbc.EmbeddedDriver.connect(Unknown Source)
at
org.executequery.datasource.ConnectionDataSource.getConnection(ConnectionDataSource.java:290)
at
org.executequery.datasource.ConnectionDataSource.getConnection(ConnectionDataSource.java:267)
at
org.executequery.datasource.ConnectionPool.ensureCapacity(ConnectionPool.java:291)
at
org.executequery.datasource.ConnectionManager.createDataSource(ConnectionManager.java:90)
at
org.executequery.databasemediators.ConnectionBuilder.connect(ConnectionBuilder.java:133)
at
org.executequery.databasemediators.ConnectionBuilder.access$000(ConnectionBuilder.java:44)
at
org.executequery.databasemediators.ConnectionBuilder$1.construct(ConnectionBuilder.java:117)
at org.underworldlabs.swing.util.SwingWorker$2.run(SwingWorker.java:138)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.sql.SQLException: Failed to start database '/mydatabase',
see the next exception for details.
at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
Source)
... 19 more
Caused by: java.sql.SQLException: Java exception: ':
java.lang.NullPointerException'.
at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
Source)
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
Source)
at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
... 16 more
Caused by: java.lang.NullPointerException
at org.apache.derby.iapi.types.SQLChar.getCollationKey(Unknown Source)
at
org.apache.derby.iapi.types.WorkHorseForCollatorDatatypes.stringCompare(Unknown
Source)
at org.apache.derby.iapi.types.CollatorSQLVarchar.stringCompare(Unknown
Source)
at org.apache.derby.iapi.types.SQLChar.compare(Unknown Source)
at
org.apache.derby.impl.store.access.btree.ControlRow.compareIndexRowToKey(Unknown
Source)
at org.apache.derby.impl.store.access.btree.index.B2IUndo.findUndo(Unknown
Source)
at
org.apache.derby.impl.store.raw.data.LogicalPageOperation.findLogicalPage(Unknown
Source)
at
org.apache.derby.impl.store.raw.data.LogicalPageOperation.generateUndo(Unknown
Source)
at org.apache.derby.impl.store.raw.log.FileLogger.undo(Unknown Source)
at org.apache.derby.impl.store.raw.xact.Xact.abort(Unknown Source)
at
org.apache.derby.impl.store.raw.xact.XactFactory.rollbackAllTransactions(Unknown
Source)
at org.apache.derby.impl.store.raw.log.LogToFile.recover(Unknown Source)
at org.apache.derby.impl.store.raw.RawStore.boot(Unknown Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown Source)
at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown
Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown
Source)
at org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown
Source)
at org.apache.derby.impl.store.access.RAMAccessManager.boot(Unknown Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown Source)
at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown
Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown
Source)
at org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown
Source)
at org.apache.derby.impl.db.BasicDatabase.bootStore(Unknown Source)
at org.apache.derby.impl.db.BasicDatabase.boot(Unknown Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown Source)
at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown
Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(Unknown
Source)
at
org.apache.derby.impl.services.monitor.BaseMonitor.startProviderService(Unknown
Source)
at
org.apache.derby.impl.services.monitor.BaseMonitor.findProviderAndStartService(Unknown
Source)
at
org.apache.derby.impl.services.monitor.BaseMonitor.startPersistentService(Unknown
Source)
at
org.apache.derby.iapi.services.monitor.Monitor.startPersistentService(Unknown
Source)
... 16 more
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14561205.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: sql query using LIKE
Posted by tom_ <to...@web.de>.
Nik-31, thank you for putting this in my question. You should open your own
thread. I still can't re-open the database.
tom_
Nik-31 wrote:
>
> sweet, that fixed my next problem.. now i just have to get set the JTable
> properly...
> On Wed, 02 Jan 2008 17:38:46 +0900, Oystein Grovlen
> <Oy...@sun.com> wrote:
>
>> Nik wrote:
>>> I'm getting an SQL excpetion using LIKE to match a String.
>>> String query = "SELECT *" + "
>>> FROM "+ tableName +
>>> "WHERE DAY_OF_WEEK LIKE \""+
>>> searchTerms+"\"";
>>> is there some other way I should be doing this?
>>
>> You need to use single quotes for the search term, not double quotes.
>>
>> --
>> Øystein
>>
>>
>
>
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14579703.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: sql query using LIKE
Posted by Nik <ni...@gmail.com>.
sweet, that fixed my next problem.. now i just have to get set the JTable
properly...
On Wed, 02 Jan 2008 17:38:46 +0900, Oystein Grovlen
<Oy...@sun.com> wrote:
> Nik wrote:
>> I'm getting an SQL excpetion using LIKE to match a String.
>> String query = "SELECT *" + "
>> FROM "+ tableName +
>> "WHERE DAY_OF_WEEK LIKE \""+
>> searchTerms+"\"";
>> is there some other way I should be doing this?
>
> You need to use single quotes for the search term, not double quotes.
>
> --
> Øystein
>
>
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Re: sql query using LIKE
Posted by Oystein Grovlen <Oy...@Sun.COM>.
Nik wrote:
> I'm getting an SQL excpetion using LIKE to match a String.
> String query = "SELECT *" +
> " FROM "+ tableName +
> "WHERE DAY_OF_WEEK LIKE \""+
> searchTerms+"\"";
> is there some other way I should be doing this?
You need to use single quotes for the search term, not double quotes.
--
Øystein
sql query using LIKE
Posted by Nik <ni...@gmail.com>.
I'm getting an SQL excpetion using LIKE to match a String.
String query = "SELECT *" +
" FROM "+ tableName +
"WHERE DAY_OF_WEEK LIKE \""+
searchTerms+"\"";
is there some other way I should be doing this?
Nik
Re: Failed to start database
Posted by tom_ <to...@web.de>.
The database was created with the properties "territory=de_DE" and
"collation=TERRITORY_BASED". The connection string contains the same
properties.
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14567032.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by Suresh Thalamati <su...@gmail.com>.
I doubt it is related to db locking. Stacks has the following error
Caused by: java.lang.NullPointerException
at org.apache.derby.iapi.types.SQLChar.getCollationKey(Unknown Source)
at
on rollback of btree log records during recovery.
Problem may be related to collation information.
-suresh
On Dec 31, 2007 3:23 PM, Manjula Kutty <ma...@gmail.com> wrote:
> This may be due to the fact that the database is not shutdown properly.
> Please check if you have a db.lck file in your db directory. If it exists
> please delete that file manually and try booting the database again.
>
> Thanks
> Manjula
>
>
>
>
> On 12/31/07, tom_ <to...@web.de> wrote:
> >
> > Without having a crash or something like that before, when trying to
> reopen
> > the database the error message is "Failed to start database". Is there a
> > possibility to start the database again?
> >
> > The complete error trace is
> > java.sql.SQLException: Failed to start database '/mydatabase', see the
> next
> > exception for details.
> > at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException
> (Unknown
> > Source)
> > at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown
> Source)
> > at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> > at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase (Unknown
> Source)
> > at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown
> Source)
> > at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(Unknown
> Source)
> > at org.apache.derby.impl.jdbc.EmbedConnection40 .<init>(Unknown
> Source)
> > at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown
> Source)
> > at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
> > at org.apache.derby.jdbc.EmbeddedDriver.connect (Unknown Source)
> > at
> >
> org.executequery.datasource.ConnectionDataSource.getConnection(ConnectionDataSource.java:290)
> > at
> >
> org.executequery.datasource.ConnectionDataSource.getConnection(ConnectionDataSource.java
> :267)
> > at
> >
> org.executequery.datasource.ConnectionPool.ensureCapacity(ConnectionPool.java:291)
> > at
> >
> org.executequery.datasource.ConnectionManager.createDataSource(ConnectionManager.java:90)
> > at
> >
> org.executequery.databasemediators.ConnectionBuilder.connect(ConnectionBuilder.java:133)
> > at
> >
> org.executequery.databasemediators.ConnectionBuilder.access$000(ConnectionBuilder.java:44)
> > at
> > org.executequery.databasemediators.ConnectionBuilder$1.construct
> (ConnectionBuilder.java:117)
> > at
> org.underworldlabs.swing.util.SwingWorker$2.run(SwingWorker.java:138)
> > at java.lang.Thread.run(Thread.java:619)
> > Caused by: java.sql.SQLException: Failed to start database '/mydatabase',
> > see the next exception for details.
> > at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
> > Source)
> > at
> >
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA
> (Unknown
> > Source)
> > ... 19 more
> > Caused by: java.sql.SQLException: Java exception: ':
> > java.lang.NullPointerException'.
> > at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
> > Source)
> > at
> >
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
> > Source)
> > at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
> > Source)
> > at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown
> Source)
> > at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
> > ... 16 more
> > Caused by: java.lang.NullPointerException
> > at org.apache.derby.iapi.types.SQLChar.getCollationKey(Unknown
> Source)
> > at
> >
> org.apache.derby.iapi.types.WorkHorseForCollatorDatatypes.stringCompare(Unknown
> > Source)
> > at org.apache.derby.iapi.types.CollatorSQLVarchar.stringCompare
> (Unknown
> > Source)
> > at org.apache.derby.iapi.types.SQLChar.compare(Unknown Source)
> > at
> >
> org.apache.derby.impl.store.access.btree.ControlRow.compareIndexRowToKey(Unknown
> > Source)
> > at org.apache.derby.impl.store.access.btree.index.B2IUndo.findUndo
> (Unknown
> > Source)
> > at
> >
> org.apache.derby.impl.store.raw.data.LogicalPageOperation.findLogicalPage(Unknown
> > Source)
> > at
> >
> org.apache.derby.impl.store.raw.data.LogicalPageOperation.generateUndo(Unknown
> > Source)
> > at org.apache.derby.impl.store.raw.log.FileLogger.undo(Unknown
> Source)
> > at org.apache.derby.impl.store.raw.xact.Xact.abort(Unknown Source)
> > at
> > org.apache.derby.impl.store.raw.xact.XactFactory.rollbackAllTransactions
> (Unknown
> > Source)
> > at org.apache.derby.impl.store.raw.log.LogToFile.recover(Unknown
> Source)
> > at org.apache.derby.impl.store.raw.RawStore.boot(Unknown Source)
> > at org.apache.derby.impl.services.monitor.BaseMonitor.boot (Unknown
> Source)
> > at
> org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown
> > Source)
> > at
> org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown
> > Source)
> > at org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule
> (Unknown
> > Source)
> > at org.apache.derby.impl.store.access.RAMAccessManager.boot(Unknown
> Source)
> > at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
> Source)
> > at org.apache.derby.impl.services.monitor.TopService.bootModule
> (Unknown
> > Source)
> > at
> org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown
> > Source)
> > at
> org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown
> > Source)
> > at org.apache.derby.impl.db.BasicDatabase.bootStore(Unknown Source)
> > at org.apache.derby.impl.db.BasicDatabase.boot(Unknown Source)
> > at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
> Source)
> > at
> org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown
> > Source)
> > at
> org.apache.derby.impl.services.monitor.BaseMonitor.bootService(Unknown
> > Source)
> > at
> > org.apache.derby.impl.services.monitor.BaseMonitor.startProviderService
> (Unknown
> > Source)
> > at
> >
> org.apache.derby.impl.services.monitor.BaseMonitor.findProviderAndStartService(Unknown
> > Source)
> > at
> > org.apache.derby.impl.services.monitor.BaseMonitor.startPersistentService
> (Unknown
> > Source)
> > at
> >
> org.apache.derby.iapi.services.monitor.Monitor.startPersistentService(Unknown
> > Source)
> > ... 16 more
> >
> >
> > --
> > View this message in context:
> http://www.nabble.com/Failed-to-start-database-tp14561205p14561205.html
> > Sent from the Apache Derby Users mailing list archive at Nabble.com.
> >
> >
>
>
>
> --
> Thanks,
> Manjula.
Re: Failed to start database
Posted by Manjula Kutty <ma...@gmail.com>.
You are correct Suresh
-Manjula
On 12/31/07, tom_ <to...@web.de> wrote:
>
>
> I fear there is no db.lck file in the database directory
>
>
> Manjula Kutty wrote:
> >
> > This may be due to the fact that the database is not shutdown properly.
> > Please check if you have a db.lck file in your db directory. If it
> exists
> > please delete that file manually and try booting the database again.
> >
> > Thanks
> > Manjula
> >
> >
> > On 12/31/07, tom_ <to...@web.de> wrote:
> >>
> >>
> >> Without having a crash or something like that before, when trying to
> >> reopen
> >> the database the error message is "Failed to start database". Is there
> a
> >> possibility to start the database again?
> >>
> >> The complete error trace is
> >> java.sql.SQLException: Failed to start database '/mydatabase', see the
> >> next
> >> exception for details.
> >> at
> >> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException
> >> (Unknown
> >> Source)
> >> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown
> >> Source)
> >> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown
> >> Source)
> >> at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase
> (Unknown
> >> Source)
> >> at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown
> >> Source)
> >> at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(Unknown
> >> Source)
> >> at org.apache.derby.impl.jdbc.EmbedConnection40.<init>(Unknown
> >> Source)
> >> at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown
> >> Source)
> >> at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
> >> at org.apache.derby.jdbc.EmbeddedDriver.connect(Unknown Source)
> >> at
> >> org.executequery.datasource.ConnectionDataSource.getConnection(
> >> ConnectionDataSource.java:290)
> >> at
> >> org.executequery.datasource.ConnectionDataSource.getConnection(
> >> ConnectionDataSource.java:267)
> >> at
> >> org.executequery.datasource.ConnectionPool.ensureCapacity(
> >> ConnectionPool.java:291)
> >> at
> >> org.executequery.datasource.ConnectionManager.createDataSource(
> >> ConnectionManager.java:90)
> >> at
> >> org.executequery.databasemediators.ConnectionBuilder.connect(
> >> ConnectionBuilder.java:133)
> >> at
> >> org.executequery.databasemediators.ConnectionBuilder.access$000(
> >> ConnectionBuilder.java:44)
> >> at
> >> org.executequery.databasemediators.ConnectionBuilder$1.construct(
> >> ConnectionBuilder.java:117)
> >> at
> >> org.underworldlabs.swing.util.SwingWorker$2.run(SwingWorker.java
> >> :138)
> >> at java.lang.Thread.run(Thread.java:619)
> >> Caused by: java.sql.SQLException: Failed to start database
> '/mydatabase',
> >> see the next exception for details.
> >> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException
> >> (Unknown
> >> Source)
> >> at
> >>
> >>
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA
> >> (Unknown
> >> Source)
> >> ... 19 more
> >> Caused by: java.sql.SQLException: Java exception: ':
> >> java.lang.NullPointerException'.
> >> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException
> >> (Unknown
> >> Source)
> >> at
> >>
> >>
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA
> >> (Unknown
> >> Source)
> >> at
> >> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException
> >> (Unknown
> >> Source)
> >> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown
> >> Source)
> >> at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
> >> ... 16 more
> >> Caused by: java.lang.NullPointerException
> >> at org.apache.derby.iapi.types.SQLChar.getCollationKey(Unknown
> >> Source)
> >> at
> >> org.apache.derby.iapi.types.WorkHorseForCollatorDatatypes.stringCompare
> >> (Unknown
> >> Source)
> >> at org.apache.derby.iapi.types.CollatorSQLVarchar.stringCompare
> >> (Unknown
> >> Source)
> >> at org.apache.derby.iapi.types.SQLChar.compare(Unknown Source)
> >> at
> >>
> org.apache.derby.impl.store.access.btree.ControlRow.compareIndexRowToKey
> >> (Unknown
> >> Source)
> >> at
> org.apache.derby.impl.store.access.btree.index.B2IUndo.findUndo
> >> (Unknown
> >> Source)
> >> at
> >>
> org.apache.derby.impl.store.raw.data.LogicalPageOperation.findLogicalPage
> >> (Unknown
> >> Source)
> >> at
> >> org.apache.derby.impl.store.raw.data.LogicalPageOperation.generateUndo
> >> (Unknown
> >> Source)
> >> at org.apache.derby.impl.store.raw.log.FileLogger.undo(Unknown
> >> Source)
> >> at org.apache.derby.impl.store.raw.xact.Xact.abort(Unknown
> Source)
> >> at
> >>
> org.apache.derby.impl.store.raw.xact.XactFactory.rollbackAllTransactions
> >> (Unknown
> >> Source)
> >> at org.apache.derby.impl.store.raw.log.LogToFile.recover(Unknown
> >> Source)
> >> at org.apache.derby.impl.store.raw.RawStore.boot(Unknown Source)
> >> at org.apache.derby.impl.services.monitor.BaseMonitor.boot
> (Unknown
> >> Source)
> >> at org.apache.derby.impl.services.monitor.TopService.bootModule
> >> (Unknown
> >> Source)
> >> at
> org.apache.derby.impl.services.monitor.BaseMonitor.startModule
> >> (Unknown
> >> Source)
> >> at
> >> org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule
> >> (Unknown
> >> Source)
> >> at
> >> org.apache.derby.impl.store.access.RAMAccessManager.boot(Unknown
> >> Source)
> >> at org.apache.derby.impl.services.monitor.BaseMonitor.boot
> (Unknown
> >> Source)
> >> at org.apache.derby.impl.services.monitor.TopService.bootModule
> >> (Unknown
> >> Source)
> >> at
> org.apache.derby.impl.services.monitor.BaseMonitor.startModule
> >> (Unknown
> >> Source)
> >> at
> >> org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule
> >> (Unknown
> >> Source)
> >> at org.apache.derby.impl.db.BasicDatabase.bootStore(Unknown
> >> Source)
> >> at org.apache.derby.impl.db.BasicDatabase.boot(Unknown Source)
> >> at org.apache.derby.impl.services.monitor.BaseMonitor.boot
> (Unknown
> >> Source)
> >> at org.apache.derby.impl.services.monitor.TopService.bootModule
> >> (Unknown
> >> Source)
> >> at
> org.apache.derby.impl.services.monitor.BaseMonitor.bootService
> >> (Unknown
> >> Source)
> >> at
> >> org.apache.derby.impl.services.monitor.BaseMonitor.startProviderService
> >> (Unknown
> >> Source)
> >> at
> >>
> >>
> org.apache.derby.impl.services.monitor.BaseMonitor.findProviderAndStartService
> >> (Unknown
> >> Source)
> >> at
> >>
> org.apache.derby.impl.services.monitor.BaseMonitor.startPersistentService
> >> (Unknown
> >> Source)
> >> at
> >> org.apache.derby.iapi.services.monitor.Monitor.startPersistentService
> >> (Unknown
> >> Source)
> >> ... 16 more
> >>
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Failed-to-start-database-tp14561205p14561205.html
> >> Sent from the Apache Derby Users mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > --
> > Thanks,
> > Manjula.
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Failed-to-start-database-tp14561205p14563104.html
> Sent from the Apache Derby Users mailing list archive at Nabble.com.
>
>
--
Thanks,
Manjula.
Re: Failed to start database
Posted by tom_ <to...@web.de>.
I fear there is no db.lck file in the database directory
Manjula Kutty wrote:
>
> This may be due to the fact that the database is not shutdown properly.
> Please check if you have a db.lck file in your db directory. If it exists
> please delete that file manually and try booting the database again.
>
> Thanks
> Manjula
>
>
> On 12/31/07, tom_ <to...@web.de> wrote:
>>
>>
>> Without having a crash or something like that before, when trying to
>> reopen
>> the database the error message is "Failed to start database". Is there a
>> possibility to start the database again?
>>
>> The complete error trace is
>> java.sql.SQLException: Failed to start database '/mydatabase', see the
>> next
>> exception for details.
>> at
>> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException
>> (Unknown
>> Source)
>> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown
>> Source)
>> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown
>> Source)
>> at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown
>> Source)
>> at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown
>> Source)
>> at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(Unknown
>> Source)
>> at org.apache.derby.impl.jdbc.EmbedConnection40.<init>(Unknown
>> Source)
>> at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown
>> Source)
>> at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
>> at org.apache.derby.jdbc.EmbeddedDriver.connect(Unknown Source)
>> at
>> org.executequery.datasource.ConnectionDataSource.getConnection(
>> ConnectionDataSource.java:290)
>> at
>> org.executequery.datasource.ConnectionDataSource.getConnection(
>> ConnectionDataSource.java:267)
>> at
>> org.executequery.datasource.ConnectionPool.ensureCapacity(
>> ConnectionPool.java:291)
>> at
>> org.executequery.datasource.ConnectionManager.createDataSource(
>> ConnectionManager.java:90)
>> at
>> org.executequery.databasemediators.ConnectionBuilder.connect(
>> ConnectionBuilder.java:133)
>> at
>> org.executequery.databasemediators.ConnectionBuilder.access$000(
>> ConnectionBuilder.java:44)
>> at
>> org.executequery.databasemediators.ConnectionBuilder$1.construct(
>> ConnectionBuilder.java:117)
>> at
>> org.underworldlabs.swing.util.SwingWorker$2.run(SwingWorker.java
>> :138)
>> at java.lang.Thread.run(Thread.java:619)
>> Caused by: java.sql.SQLException: Failed to start database '/mydatabase',
>> see the next exception for details.
>> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException
>> (Unknown
>> Source)
>> at
>>
>> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA
>> (Unknown
>> Source)
>> ... 19 more
>> Caused by: java.sql.SQLException: Java exception: ':
>> java.lang.NullPointerException'.
>> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException
>> (Unknown
>> Source)
>> at
>>
>> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA
>> (Unknown
>> Source)
>> at
>> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException
>> (Unknown
>> Source)
>> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown
>> Source)
>> at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
>> ... 16 more
>> Caused by: java.lang.NullPointerException
>> at org.apache.derby.iapi.types.SQLChar.getCollationKey(Unknown
>> Source)
>> at
>> org.apache.derby.iapi.types.WorkHorseForCollatorDatatypes.stringCompare
>> (Unknown
>> Source)
>> at org.apache.derby.iapi.types.CollatorSQLVarchar.stringCompare
>> (Unknown
>> Source)
>> at org.apache.derby.iapi.types.SQLChar.compare(Unknown Source)
>> at
>> org.apache.derby.impl.store.access.btree.ControlRow.compareIndexRowToKey
>> (Unknown
>> Source)
>> at org.apache.derby.impl.store.access.btree.index.B2IUndo.findUndo
>> (Unknown
>> Source)
>> at
>> org.apache.derby.impl.store.raw.data.LogicalPageOperation.findLogicalPage
>> (Unknown
>> Source)
>> at
>> org.apache.derby.impl.store.raw.data.LogicalPageOperation.generateUndo
>> (Unknown
>> Source)
>> at org.apache.derby.impl.store.raw.log.FileLogger.undo(Unknown
>> Source)
>> at org.apache.derby.impl.store.raw.xact.Xact.abort(Unknown Source)
>> at
>> org.apache.derby.impl.store.raw.xact.XactFactory.rollbackAllTransactions
>> (Unknown
>> Source)
>> at org.apache.derby.impl.store.raw.log.LogToFile.recover(Unknown
>> Source)
>> at org.apache.derby.impl.store.raw.RawStore.boot(Unknown Source)
>> at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
>> Source)
>> at org.apache.derby.impl.services.monitor.TopService.bootModule
>> (Unknown
>> Source)
>> at org.apache.derby.impl.services.monitor.BaseMonitor.startModule
>> (Unknown
>> Source)
>> at
>> org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule
>> (Unknown
>> Source)
>> at
>> org.apache.derby.impl.store.access.RAMAccessManager.boot(Unknown
>> Source)
>> at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
>> Source)
>> at org.apache.derby.impl.services.monitor.TopService.bootModule
>> (Unknown
>> Source)
>> at org.apache.derby.impl.services.monitor.BaseMonitor.startModule
>> (Unknown
>> Source)
>> at
>> org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule
>> (Unknown
>> Source)
>> at org.apache.derby.impl.db.BasicDatabase.bootStore(Unknown
>> Source)
>> at org.apache.derby.impl.db.BasicDatabase.boot(Unknown Source)
>> at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
>> Source)
>> at org.apache.derby.impl.services.monitor.TopService.bootModule
>> (Unknown
>> Source)
>> at org.apache.derby.impl.services.monitor.BaseMonitor.bootService
>> (Unknown
>> Source)
>> at
>> org.apache.derby.impl.services.monitor.BaseMonitor.startProviderService
>> (Unknown
>> Source)
>> at
>>
>> org.apache.derby.impl.services.monitor.BaseMonitor.findProviderAndStartService
>> (Unknown
>> Source)
>> at
>> org.apache.derby.impl.services.monitor.BaseMonitor.startPersistentService
>> (Unknown
>> Source)
>> at
>> org.apache.derby.iapi.services.monitor.Monitor.startPersistentService
>> (Unknown
>> Source)
>> ... 16 more
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Failed-to-start-database-tp14561205p14561205.html
>> Sent from the Apache Derby Users mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Thanks,
> Manjula.
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14563104.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by Manjula Kutty <ma...@gmail.com>.
This may be due to the fact that the database is not shutdown properly.
Please check if you have a db.lck file in your db directory. If it exists
please delete that file manually and try booting the database again.
Thanks
Manjula
On 12/31/07, tom_ <to...@web.de> wrote:
>
>
> Without having a crash or something like that before, when trying to
> reopen
> the database the error message is "Failed to start database". Is there a
> possibility to start the database again?
>
> The complete error trace is
> java.sql.SQLException: Failed to start database '/mydatabase', see the
> next
> exception for details.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException
> (Unknown
> Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedConnection40.<init>(Unknown
> Source)
> at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown
> Source)
> at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
> at org.apache.derby.jdbc.EmbeddedDriver.connect(Unknown Source)
> at
> org.executequery.datasource.ConnectionDataSource.getConnection(
> ConnectionDataSource.java:290)
> at
> org.executequery.datasource.ConnectionDataSource.getConnection(
> ConnectionDataSource.java:267)
> at
> org.executequery.datasource.ConnectionPool.ensureCapacity(
> ConnectionPool.java:291)
> at
> org.executequery.datasource.ConnectionManager.createDataSource(
> ConnectionManager.java:90)
> at
> org.executequery.databasemediators.ConnectionBuilder.connect(
> ConnectionBuilder.java:133)
> at
> org.executequery.databasemediators.ConnectionBuilder.access$000(
> ConnectionBuilder.java:44)
> at
> org.executequery.databasemediators.ConnectionBuilder$1.construct(
> ConnectionBuilder.java:117)
> at org.underworldlabs.swing.util.SwingWorker$2.run(SwingWorker.java
> :138)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: java.sql.SQLException: Failed to start database '/mydatabase',
> see the next exception for details.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException
> (Unknown
> Source)
> at
>
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA
> (Unknown
> Source)
> ... 19 more
> Caused by: java.sql.SQLException: Java exception: ':
> java.lang.NullPointerException'.
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException
> (Unknown
> Source)
> at
>
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA
> (Unknown
> Source)
> at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException
> (Unknown
> Source)
> at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
> ... 16 more
> Caused by: java.lang.NullPointerException
> at org.apache.derby.iapi.types.SQLChar.getCollationKey(Unknown
> Source)
> at
> org.apache.derby.iapi.types.WorkHorseForCollatorDatatypes.stringCompare
> (Unknown
> Source)
> at org.apache.derby.iapi.types.CollatorSQLVarchar.stringCompare
> (Unknown
> Source)
> at org.apache.derby.iapi.types.SQLChar.compare(Unknown Source)
> at
> org.apache.derby.impl.store.access.btree.ControlRow.compareIndexRowToKey
> (Unknown
> Source)
> at org.apache.derby.impl.store.access.btree.index.B2IUndo.findUndo
> (Unknown
> Source)
> at
> org.apache.derby.impl.store.raw.data.LogicalPageOperation.findLogicalPage
> (Unknown
> Source)
> at
> org.apache.derby.impl.store.raw.data.LogicalPageOperation.generateUndo
> (Unknown
> Source)
> at org.apache.derby.impl.store.raw.log.FileLogger.undo(Unknown
> Source)
> at org.apache.derby.impl.store.raw.xact.Xact.abort(Unknown Source)
> at
> org.apache.derby.impl.store.raw.xact.XactFactory.rollbackAllTransactions
> (Unknown
> Source)
> at org.apache.derby.impl.store.raw.log.LogToFile.recover(Unknown
> Source)
> at org.apache.derby.impl.store.raw.RawStore.boot(Unknown Source)
> at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
> Source)
> at org.apache.derby.impl.services.monitor.TopService.bootModule
> (Unknown
> Source)
> at org.apache.derby.impl.services.monitor.BaseMonitor.startModule
> (Unknown
> Source)
> at org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule
> (Unknown
> Source)
> at org.apache.derby.impl.store.access.RAMAccessManager.boot(Unknown
> Source)
> at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
> Source)
> at org.apache.derby.impl.services.monitor.TopService.bootModule
> (Unknown
> Source)
> at org.apache.derby.impl.services.monitor.BaseMonitor.startModule
> (Unknown
> Source)
> at org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule
> (Unknown
> Source)
> at org.apache.derby.impl.db.BasicDatabase.bootStore(Unknown Source)
> at org.apache.derby.impl.db.BasicDatabase.boot(Unknown Source)
> at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown
> Source)
> at org.apache.derby.impl.services.monitor.TopService.bootModule
> (Unknown
> Source)
> at org.apache.derby.impl.services.monitor.BaseMonitor.bootService
> (Unknown
> Source)
> at
> org.apache.derby.impl.services.monitor.BaseMonitor.startProviderService
> (Unknown
> Source)
> at
>
> org.apache.derby.impl.services.monitor.BaseMonitor.findProviderAndStartService
> (Unknown
> Source)
> at
> org.apache.derby.impl.services.monitor.BaseMonitor.startPersistentService
> (Unknown
> Source)
> at
> org.apache.derby.iapi.services.monitor.Monitor.startPersistentService
> (Unknown
> Source)
> ... 16 more
>
>
> --
> View this message in context:
> http://www.nabble.com/Failed-to-start-database-tp14561205p14561205.html
> Sent from the Apache Derby Users mailing list archive at Nabble.com.
>
>
--
Thanks,
Manjula.
Re: Failed to start database
Posted by tom_ <to...@web.de>.
Yes, I'm shutting down the database with the shutdown attribute, I already
looked at the code, I will look at it again. What I know is that it happens
relative often that 2 applications try to open the database at the same
time, and one of them has to be stopped. I will have to look at the code for
this situation.
oysteing wrote:
>
> tom_ wrote:
>> Without having a crash or something like that before, when trying to
>> reopen
>> the database the error message is "Failed to start database". Is there a
>> possibility to start the database again?
>
> Just one more comment here: Make sure to explicitly shut down your
> database before exiting your application? If it is shut down properly,
> the database should not go into recovery at start-up. (I guess this
> will not solve your problem since your database will still be vulnerable
> to crashes until this bug is fixed, but normal startup will be quicker
> if you avoid recovery)
>
> --
> Øystein
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14736309.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by tom_ <to...@web.de>.
Hi Rick,
I was a day offline because of hardware issues, yes I will further have a
look at the described situation. There was a very fast fix for the collation
issue, I'm just checking if it can open the database.
Rick Hillegas-2 wrote:
>
> Hi Tom,
>
> The database shutdown attempt, by the second application, should simply
> raise an exception. It should not crash the database and cause recovery
> problems later on. That, at least, is how Derby is supposed to operate
> and I'm not aware of a bug in this area. However, if you can demonstrate
> such a bug, I am sure it will be regarded as a high priority issue and
> probably a blocker for the next release.
>
> Regards,
> -Rick
>
> tom_ wrote:
>> Yes, I agree, it doesn't need to and should not try a shutdown, and
>> that's
>> how the application's logic works. I have just found out that another
>> application by whatever reasons tries to make a shutdown in the described
>> situation. I wonder if this trial could result in a database crash -
>> eventually afterwards when the other application does the shutdown. It
>> would
>> explain why I am observing the recovery problem so often.
>>
>>
>> Rick Hillegas-2 wrote:
>>
>>> Hi Tom,
>>>
>>> The database is successfully booted in only one VM and can be shut down
>>> only in that VM. The second application, running in a different VM, can
>>> not get a connection to the database and can not shut down the database,
>>> either. The second application should abandon its trial and not attempt
>>> a shutdown.
>>>
>>> Hope this helps,
>>> -Rick
>>>
>>> tom_ wrote:
>>>
>>>> I have a question, if a program tries to access a database that is
>>>> already
>>>> opened by another one, how should the program proceed, should it just
>>>> stop
>>>> the trial without trying a shutdown of the database or try a shutdown?
>>>> If
>>>> it
>>>> would try a shutdown could this affect the state of the database?
>>>>
>>>>
>>>> oysteing wrote:
>>>>
>>>>
>>>>> tom_ wrote:
>>>>>
>>>>>
>>>>>> Without having a crash or something like that before, when trying to
>>>>>> reopen
>>>>>> the database the error message is "Failed to start database". Is
>>>>>> there
>>>>>> a
>>>>>> possibility to start the database again?
>>>>>>
>>>>>>
>>>>> Just one more comment here: Make sure to explicitly shut down your
>>>>> database before exiting your application? If it is shut down
>>>>> properly,
>>>>> the database should not go into recovery at start-up. (I guess this
>>>>> will not solve your problem since your database will still be
>>>>> vulnerable
>>>>> to crashes until this bug is fixed, but normal startup will be quicker
>>>>> if you avoid recovery)
>>>>>
>>>>> --
>>>>> Øystein
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14780011.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by tom_ <to...@web.de>.
The fix works fine, thanks a lot
Rick Hillegas-2 wrote:
>
> Hi Tom,
>
> The database shutdown attempt, by the second application, should simply
> raise an exception. It should not crash the database and cause recovery
> problems later on. That, at least, is how Derby is supposed to operate
> and I'm not aware of a bug in this area. However, if you can demonstrate
> such a bug, I am sure it will be regarded as a high priority issue and
> probably a blocker for the next release.
>
> Regards,
> -Rick
>
> tom_ wrote:
>> Yes, I agree, it doesn't need to and should not try a shutdown, and
>> that's
>> how the application's logic works. I have just found out that another
>> application by whatever reasons tries to make a shutdown in the described
>> situation. I wonder if this trial could result in a database crash -
>> eventually afterwards when the other application does the shutdown. It
>> would
>> explain why I am observing the recovery problem so often.
>>
>>
>> Rick Hillegas-2 wrote:
>>
>>> Hi Tom,
>>>
>>> The database is successfully booted in only one VM and can be shut down
>>> only in that VM. The second application, running in a different VM, can
>>> not get a connection to the database and can not shut down the database,
>>> either. The second application should abandon its trial and not attempt
>>> a shutdown.
>>>
>>> Hope this helps,
>>> -Rick
>>>
>>> tom_ wrote:
>>>
>>>> I have a question, if a program tries to access a database that is
>>>> already
>>>> opened by another one, how should the program proceed, should it just
>>>> stop
>>>> the trial without trying a shutdown of the database or try a shutdown?
>>>> If
>>>> it
>>>> would try a shutdown could this affect the state of the database?
>>>>
>>>>
>>>> oysteing wrote:
>>>>
>>>>
>>>>> tom_ wrote:
>>>>>
>>>>>
>>>>>> Without having a crash or something like that before, when trying to
>>>>>> reopen
>>>>>> the database the error message is "Failed to start database". Is
>>>>>> there
>>>>>> a
>>>>>> possibility to start the database again?
>>>>>>
>>>>>>
>>>>> Just one more comment here: Make sure to explicitly shut down your
>>>>> database before exiting your application? If it is shut down
>>>>> properly,
>>>>> the database should not go into recovery at start-up. (I guess this
>>>>> will not solve your problem since your database will still be
>>>>> vulnerable
>>>>> to crashes until this bug is fixed, but normal startup will be quicker
>>>>> if you avoid recovery)
>>>>>
>>>>> --
>>>>> Øystein
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14781471.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by Rick Hillegas <Ri...@Sun.COM>.
Hi Tom,
The database shutdown attempt, by the second application, should simply
raise an exception. It should not crash the database and cause recovery
problems later on. That, at least, is how Derby is supposed to operate
and I'm not aware of a bug in this area. However, if you can demonstrate
such a bug, I am sure it will be regarded as a high priority issue and
probably a blocker for the next release.
Regards,
-Rick
tom_ wrote:
> Yes, I agree, it doesn't need to and should not try a shutdown, and that's
> how the application's logic works. I have just found out that another
> application by whatever reasons tries to make a shutdown in the described
> situation. I wonder if this trial could result in a database crash -
> eventually afterwards when the other application does the shutdown. It would
> explain why I am observing the recovery problem so often.
>
>
> Rick Hillegas-2 wrote:
>
>> Hi Tom,
>>
>> The database is successfully booted in only one VM and can be shut down
>> only in that VM. The second application, running in a different VM, can
>> not get a connection to the database and can not shut down the database,
>> either. The second application should abandon its trial and not attempt
>> a shutdown.
>>
>> Hope this helps,
>> -Rick
>>
>> tom_ wrote:
>>
>>> I have a question, if a program tries to access a database that is
>>> already
>>> opened by another one, how should the program proceed, should it just
>>> stop
>>> the trial without trying a shutdown of the database or try a shutdown? If
>>> it
>>> would try a shutdown could this affect the state of the database?
>>>
>>>
>>> oysteing wrote:
>>>
>>>
>>>> tom_ wrote:
>>>>
>>>>
>>>>> Without having a crash or something like that before, when trying to
>>>>> reopen
>>>>> the database the error message is "Failed to start database". Is there
>>>>> a
>>>>> possibility to start the database again?
>>>>>
>>>>>
>>>> Just one more comment here: Make sure to explicitly shut down your
>>>> database before exiting your application? If it is shut down properly,
>>>> the database should not go into recovery at start-up. (I guess this
>>>> will not solve your problem since your database will still be vulnerable
>>>> to crashes until this bug is fixed, but normal startup will be quicker
>>>> if you avoid recovery)
>>>>
>>>> --
>>>> Øystein
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: Failed to start database
Posted by tom_ <to...@web.de>.
Yes, I agree, it doesn't need to and should not try a shutdown, and that's
how the application's logic works. I have just found out that another
application by whatever reasons tries to make a shutdown in the described
situation. I wonder if this trial could result in a database crash -
eventually afterwards when the other application does the shutdown. It would
explain why I am observing the recovery problem so often.
Rick Hillegas-2 wrote:
>
> Hi Tom,
>
> The database is successfully booted in only one VM and can be shut down
> only in that VM. The second application, running in a different VM, can
> not get a connection to the database and can not shut down the database,
> either. The second application should abandon its trial and not attempt
> a shutdown.
>
> Hope this helps,
> -Rick
>
> tom_ wrote:
>> I have a question, if a program tries to access a database that is
>> already
>> opened by another one, how should the program proceed, should it just
>> stop
>> the trial without trying a shutdown of the database or try a shutdown? If
>> it
>> would try a shutdown could this affect the state of the database?
>>
>>
>> oysteing wrote:
>>
>>> tom_ wrote:
>>>
>>>> Without having a crash or something like that before, when trying to
>>>> reopen
>>>> the database the error message is "Failed to start database". Is there
>>>> a
>>>> possibility to start the database again?
>>>>
>>> Just one more comment here: Make sure to explicitly shut down your
>>> database before exiting your application? If it is shut down properly,
>>> the database should not go into recovery at start-up. (I guess this
>>> will not solve your problem since your database will still be vulnerable
>>> to crashes until this bug is fixed, but normal startup will be quicker
>>> if you avoid recovery)
>>>
>>> --
>>> Øystein
>>>
>>>
>>>
>>
>>
>
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14738576.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by Rick Hillegas <Ri...@Sun.COM>.
Hi Tom,
The database is successfully booted in only one VM and can be shut down
only in that VM. The second application, running in a different VM, can
not get a connection to the database and can not shut down the database,
either. The second application should abandon its trial and not attempt
a shutdown.
Hope this helps,
-Rick
tom_ wrote:
> I have a question, if a program tries to access a database that is already
> opened by another one, how should the program proceed, should it just stop
> the trial without trying a shutdown of the database or try a shutdown? If it
> would try a shutdown could this affect the state of the database?
>
>
> oysteing wrote:
>
>> tom_ wrote:
>>
>>> Without having a crash or something like that before, when trying to
>>> reopen
>>> the database the error message is "Failed to start database". Is there a
>>> possibility to start the database again?
>>>
>> Just one more comment here: Make sure to explicitly shut down your
>> database before exiting your application? If it is shut down properly,
>> the database should not go into recovery at start-up. (I guess this
>> will not solve your problem since your database will still be vulnerable
>> to crashes until this bug is fixed, but normal startup will be quicker
>> if you avoid recovery)
>>
>> --
>> Øystein
>>
>>
>>
>
>
Re: Failed to start database
Posted by tom_ <to...@web.de>.
I have a question, if a program tries to access a database that is already
opened by another one, how should the program proceed, should it just stop
the trial without trying a shutdown of the database or try a shutdown? If it
would try a shutdown could this affect the state of the database?
oysteing wrote:
>
> tom_ wrote:
>> Without having a crash or something like that before, when trying to
>> reopen
>> the database the error message is "Failed to start database". Is there a
>> possibility to start the database again?
>
> Just one more comment here: Make sure to explicitly shut down your
> database before exiting your application? If it is shut down properly,
> the database should not go into recovery at start-up. (I guess this
> will not solve your problem since your database will still be vulnerable
> to crashes until this bug is fixed, but normal startup will be quicker
> if you avoid recovery)
>
> --
> Øystein
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14737909.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by Oystein Grovlen - Sun Norway <Oy...@Sun.COM>.
tom_ wrote:
> Without having a crash or something like that before, when trying to reopen
> the database the error message is "Failed to start database". Is there a
> possibility to start the database again?
Just one more comment here: Make sure to explicitly shut down your
database before exiting your application? If it is shut down properly,
the database should not go into recovery at start-up. (I guess this
will not solve your problem since your database will still be vulnerable
to crashes until this bug is fixed, but normal startup will be quicker
if you avoid recovery)
--
Øystein
Re: Failed to start database
Posted by tom_ <to...@web.de>.
I am using 10.3.1.4, I will have a try with 10.3.2 and tell you if it is able
to open the database.
oysteing wrote:
>
> Seems like this is a bug in recovery of collation-based databases.
> Which version of DERBY are you using? If not the newest (10.3.2), you
> could try to use a newer version of Derby to see whether the bug has
> been fixed. If not, I think a bug fix is needed before you will be able
> to start the database.
>
> --
> Øystein
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14580654.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by Mamta Satoor <ms...@gmail.com>.
I am one of the people who implemented collation in Derby and hence
curious to know what is going wrong here. I am not feeling well so
will take a look at it once I am better from the flu that I caught
today.
Mamta
On 1/2/08, tom_ <to...@web.de> wrote:
>
> On the downloads page I see only Official Releases.
>
>
>
> oysteing wrote:
> >
> > Kristian Waagan wrote:
> >> tom_ skrev:
> >>> 10.3.2 also can't open the database.
> >>>
> >>
> >> Hello Tom,
> >>
> >> The only thing left to do is then to try booting the database with the
> >> current devlopment version. Please backup your database first if you try
> >> that.
> >>
> >
> > Note that you will need to set the derby.database.allowPreReleaseUpgrade
> > property to true in order to be able to access your database with a
> > development version.
> >
> > --
> > Øystein
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14583058.html
> Sent from the Apache Derby Users mailing list archive at Nabble.com.
>
>
Re: Failed to start database
Posted by tom_ <to...@web.de>.
I have to change this, just a moment ...
oysteing wrote:
>
> tom_ wrote:
>> I have tried with the latest bits/trunk, here the problem is an exception
>> "upgrade from 10.3 to 10.4 is not supported".
>
> Have you followed my advice about setting the
> derby.database.allowPreReleaseUpgrade property?
>
> --
> Øystein
>
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14634908.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by Mamta Satoor <ms...@gmail.com>.
Thanks Knut, for the reproducible script. I will start looking at
DERBY-3302. I think the problem might be that database context is not
available at the time of recovery. The code uses the database context
to find the locale which gets used to get the collation.
Mamta
On 1/7/08, Knut Anders Hatlen <Kn...@sun.com> wrote:
> tom_ <to...@web.de> writes:
>
> > Here is the debug stack trace
> >
> [...]
> > Caused by: java.lang.NullPointerException
> > at org.apache.derby.iapi.types.SQLChar.getCollationKey(SQLChar.java:2516)
>
> Thanks! It seems like Mamta's guess was correct. The NPE was thrown by
> this line:
>
> RuleBasedCollator rbc = getLocaleFinder().getCollator();
>
> I managed to reproduce this bug with a small SQL script. I have logged a
> bug report (http://issues.apache.org/jira/browse/DERBY-3302) and
> attached the repro to it.
>
> --
> Knut Anders
>
Re: Failed to start database
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
tom_ <to...@web.de> writes:
> Here is the debug stack trace
>
[...]
> Caused by: java.lang.NullPointerException
> at org.apache.derby.iapi.types.SQLChar.getCollationKey(SQLChar.java:2516)
Thanks! It seems like Mamta's guess was correct. The NPE was thrown by
this line:
RuleBasedCollator rbc = getLocaleFinder().getCollator();
I managed to reproduce this bug with a small SQL script. I have logged a
bug report (http://issues.apache.org/jira/browse/DERBY-3302) and
attached the repro to it.
--
Knut Anders
Re: Failed to start database
Posted by tom_ <to...@web.de>.
Here is the debug stack trace
java.sql.SQLException: Failed to start database
'/Programme/Chemikalienverzeichnis-Einzelplatz/db/chev21', see the next
exception for details.
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:95)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java:88)
at org.apache.derby.impl.jdbc.Util.seeNextException(Util.java:224)
at
org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(EmbedConnection.java:1903)
at
org.apache.derby.impl.jdbc.EmbedConnection.<init>(EmbedConnection.java:255)
at
org.apache.derby.impl.jdbc.EmbedConnection30.<init>(EmbedConnection30.java:73)
at
org.apache.derby.impl.jdbc.EmbedConnection40.<init>(EmbedConnection40.java:54)
at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Driver40.java:68)
at org.apache.derby.jdbc.InternalDriver.connect(InternalDriver.java:209)
at org.apache.derby.jdbc.EmbeddedDriver.connect(EmbeddedDriver.java:128)
at
org.executequery.datasource.ConnectionDataSource.getConnection(ConnectionDataSource.java:290)
at
org.executequery.datasource.ConnectionDataSource.getConnection(ConnectionDataSource.java:267)
at
org.executequery.datasource.ConnectionPool.ensureCapacity(ConnectionPool.java:291)
at
org.executequery.datasource.ConnectionManager.createDataSource(ConnectionManager.java:90)
at
org.executequery.databasemediators.ConnectionBuilder.connect(ConnectionBuilder.java:133)
at
org.executequery.databasemediators.ConnectionBuilder.access$000(ConnectionBuilder.java:44)
at
org.executequery.databasemediators.ConnectionBuilder$1.construct(ConnectionBuilder.java:117)
at org.underworldlabs.swing.util.SwingWorker$2.run(SwingWorker.java:138)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.sql.SQLException: Failed to start database
'/Programme/Chemikalienverzeichnis-Einzelplatz/db/chev21', see the next
exception for details.
at
org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:45)
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(SQLExceptionFactory40.java:135)
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:70)
... 18 more
Caused by: java.sql.SQLException: Java exception: ':
java.lang.NullPointerException'.
at
org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:45)
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(SQLExceptionFactory40.java:135)
at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:70)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java:88)
at org.apache.derby.impl.jdbc.Util.javaException(Util.java:245)
at
org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(EmbedConnection.java:1899)
... 15 more
Caused by: java.lang.NullPointerException
at org.apache.derby.iapi.types.SQLChar.getCollationKey(SQLChar.java:2516)
at
org.apache.derby.iapi.types.WorkHorseForCollatorDatatypes.stringCompare(WorkHorseForCollatorDatatypes.java:88)
at
org.apache.derby.iapi.types.CollatorSQLVarchar.stringCompare(CollatorSQLVarchar.java:159)
at org.apache.derby.iapi.types.SQLChar.compare(SQLChar.java:902)
at
org.apache.derby.impl.store.access.btree.ControlRow.compareIndexRowToKey(ControlRow.java:1354)
at
org.apache.derby.impl.store.access.btree.index.B2IUndo.findUndo(B2IUndo.java:221)
at
org.apache.derby.impl.store.raw.data.LogicalPageOperation.findLogicalPage(LogicalPageOperation.java:358)
at
org.apache.derby.impl.store.raw.data.LogicalPageOperation.generateUndo(LogicalPageOperation.java:164)
at org.apache.derby.impl.store.raw.log.FileLogger.undo(FileLogger.java:991)
at org.apache.derby.impl.store.raw.xact.Xact.abort(Xact.java:933)
at
org.apache.derby.impl.store.raw.xact.XactFactory.rollbackAllTransactions(XactFactory.java:529)
at
org.apache.derby.impl.store.raw.log.LogToFile.recover(LogToFile.java:1100)
at org.apache.derby.impl.store.raw.RawStore.boot(RawStore.java:309)
at
org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java:1992)
at
org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:291)
at
org.apache.derby.impl.services.monitor.BaseMonitor.startModule(BaseMonitor.java:546)
at
org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Monitor.java:419)
at
org.apache.derby.impl.store.access.RAMAccessManager.boot(RAMAccessManager.java:985)
at
org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java:1992)
at
org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:291)
at
org.apache.derby.impl.services.monitor.BaseMonitor.startModule(BaseMonitor.java:546)
at
org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Monitor.java:419)
at org.apache.derby.impl.db.BasicDatabase.bootStore(BasicDatabase.java:759)
at org.apache.derby.impl.db.BasicDatabase.boot(BasicDatabase.java:190)
at
org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java:1992)
at
org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java:291)
at
org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java:1829)
at
org.apache.derby.impl.services.monitor.BaseMonitor.startProviderService(BaseMonitor.java:1695)
at
org.apache.derby.impl.services.monitor.BaseMonitor.findProviderAndStartService(BaseMonitor.java:1575)
at
org.apache.derby.impl.services.monitor.BaseMonitor.startPersistentService(BaseMonitor.java:994)
at
org.apache.derby.iapi.services.monitor.Monitor.startPersistentService(Monitor.java:542)
at
org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(EmbedConnection.java:1864)
... 15 more
Knut Anders Hatlen wrote:
>
> tom_ <to...@web.de> writes:
>
>> It has to be set in the file derby.properties which has to be created.
>> Now
>> the upgrade message has gone, but the exception with getCollationKey() is
>> shown again.
>
> Could you try to do the same with a debug build and post the stack trace
> you are seeing? You can find a debug build here:
> http://db.apache.org/derby/releases/release-10.3.2.1.cgi (pick one of
> the lib-debug downloads).
>
> --
> Knut Anders
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14663974.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
tom_ <to...@web.de> writes:
> It has to be set in the file derby.properties which has to be created. Now
> the upgrade message has gone, but the exception with getCollationKey() is
> shown again.
Could you try to do the same with a debug build and post the stack trace
you are seeing? You can find a debug build here:
http://db.apache.org/derby/releases/release-10.3.2.1.cgi (pick one of
the lib-debug downloads).
--
Knut Anders
Re: Failed to start database
Posted by tom_ <to...@web.de>.
I'm not allowed to send the database out. Maybe there is a further
possibility that could cause the error, if the database is not in a
consistent state, and the error only seems to be a collation problem. Is
there a way to check the consistency of the database?
Mamta Satoor wrote:
>
> Is there any way you can provide your database for me to debug the
> problem? The stack trace in your first mail says what method is
> causing NPE but it does not have the line number. I am thinking it
> might be caused by following code in SQLChar.getCollationKey but I am
> not certain why?
> RuleBasedCollator rbc = getLocaleFinder().getCollator();
>
> Mamta
>
> On 1/5/08, tom_ <to...@web.de> wrote:
>>
>> It has to be set in the file derby.properties which has to be created.
>> Now
>> the upgrade message has gone, but the exception with getCollationKey() is
>> shown again. I'm having a serious problem with this because I have to
>> create
>> a release and am lacking of a stable version.
>>
>>
>> tom_ wrote:
>> >
>> > Isn't the file service.properties in the database directory the right
>> > place for setting this property? I have also added "update=true" to the
>> > connection string.
>> >
>> >
>> > oysteing wrote:
>> >>
>> >> tom_ wrote:
>> >>> I have tried with the latest bits/trunk, here the problem is an
>> >>> exception
>> >>> "upgrade from 10.3 to 10.4 is not supported".
>> >>
>> >> Have you followed my advice about setting the
>> >> derby.database.allowPreReleaseUpgrade property?
>> >>
>> >> --
>> >> Øystein
>> >>
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Failed-to-start-database-tp14561205p14636492.html
>> Sent from the Apache Derby Users mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14660402.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by Mamta Satoor <ms...@gmail.com>.
Is there any way you can provide your database for me to debug the
problem? The stack trace in your first mail says what method is
causing NPE but it does not have the line number. I am thinking it
might be caused by following code in SQLChar.getCollationKey but I am
not certain why?
RuleBasedCollator rbc = getLocaleFinder().getCollator();
Mamta
On 1/5/08, tom_ <to...@web.de> wrote:
>
> It has to be set in the file derby.properties which has to be created. Now
> the upgrade message has gone, but the exception with getCollationKey() is
> shown again. I'm having a serious problem with this because I have to create
> a release and am lacking of a stable version.
>
>
> tom_ wrote:
> >
> > Isn't the file service.properties in the database directory the right
> > place for setting this property? I have also added "update=true" to the
> > connection string.
> >
> >
> > oysteing wrote:
> >>
> >> tom_ wrote:
> >>> I have tried with the latest bits/trunk, here the problem is an
> >>> exception
> >>> "upgrade from 10.3 to 10.4 is not supported".
> >>
> >> Have you followed my advice about setting the
> >> derby.database.allowPreReleaseUpgrade property?
> >>
> >> --
> >> Øystein
> >>
> >>
> >>
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14636492.html
> Sent from the Apache Derby Users mailing list archive at Nabble.com.
>
>
Re: Failed to start database
Posted by tom_ <to...@web.de>.
It has to be set in the file derby.properties which has to be created. Now
the upgrade message has gone, but the exception with getCollationKey() is
shown again. I'm having a serious problem with this because I have to create
a release and am lacking of a stable version.
tom_ wrote:
>
> Isn't the file service.properties in the database directory the right
> place for setting this property? I have also added "update=true" to the
> connection string.
>
>
> oysteing wrote:
>>
>> tom_ wrote:
>>> I have tried with the latest bits/trunk, here the problem is an
>>> exception
>>> "upgrade from 10.3 to 10.4 is not supported".
>>
>> Have you followed my advice about setting the
>> derby.database.allowPreReleaseUpgrade property?
>>
>> --
>> Øystein
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14636492.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by tom_ <to...@web.de>.
Isn't the file service.properties in the database directory the right place
for setting this property? I have also added "update=true" to the connection
string.
oysteing wrote:
>
> tom_ wrote:
>> I have tried with the latest bits/trunk, here the problem is an exception
>> "upgrade from 10.3 to 10.4 is not supported".
>
> Have you followed my advice about setting the
> derby.database.allowPreReleaseUpgrade property?
>
> --
> Øystein
>
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14635234.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by Øystein Grøvlen <Oy...@Sun.COM>.
tom_ wrote:
> I have tried with the latest bits/trunk, here the problem is an exception
> "upgrade from 10.3 to 10.4 is not supported".
Have you followed my advice about setting the
derby.database.allowPreReleaseUpgrade property?
--
Øystein
Re: Failed to start database
Posted by tom_ <to...@web.de>.
I have tried with the latest bits/trunk, here the problem is an exception
"upgrade from 10.3 to 10.4 is not supported".
John Embretsen wrote:
>
> tom_ wrote:
>> On the downloads page I see only Official Releases.
>
> You can check out the source and build the development trunk yourself [1],
> or
> use the most recent binaries available from
> http://dbtg.thresher.com/derby/bits/trunk/ (for
> testing purposes only).
>
>
> [1]: http://db.apache.org/derby/dev/derby_source.html
>
> --
> John
>
>
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14634619.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by John Embretsen <Jo...@Sun.COM>.
tom_ wrote:
> On the downloads page I see only Official Releases.
You can check out the source and build the development trunk yourself [1], or
use the most recent binaries available from
http://dbtg.thresher.com/derby/bits/trunk/ (for
testing purposes only).
[1]: http://db.apache.org/derby/dev/derby_source.html
--
John
Re: Failed to start database
Posted by tom_ <to...@web.de>.
On the downloads page I see only Official Releases.
oysteing wrote:
>
> Kristian Waagan wrote:
>> tom_ skrev:
>>> 10.3.2 also can't open the database.
>>>
>>
>> Hello Tom,
>>
>> The only thing left to do is then to try booting the database with the
>> current devlopment version. Please backup your database first if you try
>> that.
>>
>
> Note that you will need to set the derby.database.allowPreReleaseUpgrade
> property to true in order to be able to access your database with a
> development version.
>
> --
> Øystein
>
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14583058.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by Oystein Grovlen <Oy...@Sun.COM>.
Kristian Waagan wrote:
> tom_ skrev:
>> 10.3.2 also can't open the database.
>>
>
> Hello Tom,
>
> The only thing left to do is then to try booting the database with the
> current devlopment version. Please backup your database first if you try
> that.
>
Note that you will need to set the derby.database.allowPreReleaseUpgrade
property to true in order to be able to access your database with a
development version.
--
Øystein
Re: Failed to start database
Posted by Kristian Waagan <Kr...@Sun.COM>.
tom_ skrev:
> 10.3.2 also can't open the database.
>
Hello Tom,
The only thing left to do is then to try booting the database with the
current devlopment version. Please backup your database first if you try
that.
If that doesn't work, you should log a bug in Jira so the community can
fix the problem (https://issues.apache.org/jira/browse/DERBY).
If your data is public and the database isn't too big, it would be great
if you could attach it.
I agree with Øystein that this issue looks like a bug in Derby.
--
Kristian
>
>
> oysteing wrote:
>
>> tom_ wrote:
>>
>>> Without having a crash or something like that before, when trying to
>>> reopen
>>> the database the error message is "Failed to start database". Is there a
>>> possibility to start the database again?
>>>
>>>
>> Seems like this is a bug in recovery of collation-based databases.
>> Which version of DERBY are you using? If not the newest (10.3.2), you
>> could try to use a newer version of Derby to see whether the bug has
>> been fixed. If not, I think a bug fix is needed before you will be able
>> to start the database.
>>
>> --
>> Øystein
>>
>>
>>
>
>
Re: Failed to start database
Posted by tom_ <to...@web.de>.
10.3.2 also can't open the database.
oysteing wrote:
>
> tom_ wrote:
>> Without having a crash or something like that before, when trying to
>> reopen
>> the database the error message is "Failed to start database". Is there a
>> possibility to start the database again?
>>
>
> Seems like this is a bug in recovery of collation-based databases.
> Which version of DERBY are you using? If not the newest (10.3.2), you
> could try to use a newer version of Derby to see whether the bug has
> been fixed. If not, I think a bug fix is needed before you will be able
> to start the database.
>
> --
> Øystein
>
>
--
View this message in context: http://www.nabble.com/Failed-to-start-database-tp14561205p14581972.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Re: Failed to start database
Posted by Oystein Grovlen - Sun Norway <Oy...@Sun.COM>.
tom_ wrote:
> Without having a crash or something like that before, when trying to reopen
> the database the error message is "Failed to start database". Is there a
> possibility to start the database again?
>
Seems like this is a bug in recovery of collation-based databases.
Which version of DERBY are you using? If not the newest (10.3.2), you
could try to use a newer version of Derby to see whether the bug has
been fixed. If not, I think a bug fix is needed before you will be able
to start the database.
--
Øystein