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_ <[EMAIL PROTECTED]> 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.
