[
https://issues.apache.org/jira/browse/DERBY-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604957#action_12604957
]
sathish commented on DERBY-3721:
--------------------------------
Hi,
Thanks for the information.
The database was originally created with cloudscape 5.1.45. I very much agree
with your suggestion on upgradation support from IBM.
But what made me wonder is that the database is perfectly accessible and
working with Derby 10.1.x.
but not working with Derby 10.2.x and above, as you might have observed with
the attached test program and the database.
Now the application is working fine with Derby 10.1.x. though the database have
been created in cloudscape 5.x long time back.
If this glitch of migrating from 10.1.x to 10.2.x alone is simple to resolve,
it will really save a lot of pain in migrating the data.
Please let me know if it can be overcome by any simple means, as logically it
appears to be some difference across 10.1.x and 10.2.x.
Thanks.
> 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.
