[
https://issues.apache.org/jira/browse/DERBY-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604792#action_12604792
]
sathish edited comment on DERBY-3721 at 6/13/08 3:35 AM:
---------------------------------------------------------
A CORRECTION - The problem is observed in database created in cloudscape and
not with database created with any of derby versions. The database created in
cloudscape is attached.
Details of attachement:
The database attached is created in cloudscape. The test program is also
attached.
service.properties in the above database is replaced with the one for derby.
On testing:
1) The database is accessible without any issues for all derby versions 10.1.x
2) The mentioned exception is getting thrown and database is not accessible for
all derby versions 10.2.x and above.
Requirement: The attached database created in cloudscape needs to be accessed
and usable for all and latest versions of derby.
was (Author: sathish):
The database attached is created in cloudscape. The test program is also
attached.
service.properties in the above database is replaced with the one for derby.
On testing:
1) The database is accessible without any issues for all derby versions 10.1.x
2) The mentioned exception is getting thrown and database is not accessible for
all derby versions 10.2.x and above.
Requirement: The attached database created in cloudscape needs to be accessed
and usable for all and latest versions of derby.
> Derby Database created in 10.1x is not compatibile when tried to access with
> 10.2x - Throws error
> -------------------------------------------------------------------------------------------------
>
> Key: DERBY-3721
> URL: https://issues.apache.org/jira/browse/DERBY-3721
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.2.1.6
> Environment: OS - Windows XP Professional
> Reporter: sathish
> Priority: Critical
> Attachments: derbymigration.zip
>
>
> An application uses cloudscape database. It requires migration to latest
> version of derby.
> While checking the binary compatibility of the database with different
> versions of derby, I observed the following.
> Cloudscape and Derby Database created before and in 10.1x versions are
> compatible across versions - All versoins are able to connect to and operate
> on the application's DB.
> When the same database is accessed with derby versions 10.2.x and above,
> following exception is getting thrown.
> java.sql.SQLException: Failed to start database 'dbelec', see the next
> exception for details.
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.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.jdbc.Driver30.getNewEmbedConnection(Unknown Source)
> at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
> at org.apache.derby.jdbc.EmbeddedDataSource.getConnection(Unknown
> Source)
> at org.apache.derby.jdbc.EmbeddedDataSource.getConnection(Unknown
> Source)
> at
> com.gesmallworld.javatest.SimpleDerbyAppNew.go(SimpleDerbyAppNew.java:189)
> at
> com.gesmallworld.javatest.SimpleDerbyAppNew.main(SimpleDerbyAppNew.java:102)
> 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.Util.newEmbedSQLException(Unknown Source)
> at org.apache.derby.impl.jdbc.Util.javaException(Unknown Source)
> ... 9 more
> Caused by: java.lang.NullPointerException
> at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.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.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)
> Can you please update me on if there is a known compatibility issue and if
> there is a workaround for the same. Or is it something that i might be
> overlooking.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
