You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "sathish (JIRA)" <ji...@apache.org> on 2008/06/12 18:50:46 UTC
[jira] Created: (DERBY-3721) Derby Database created in 10.1x is not
compatibile when tried to access with 10.2x - Throws error
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
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.
[jira] Issue Comment Edited: (DERBY-3721) Derby Database created in
10.1x is not compatibile when tried to access with 10.2x - Throws error
Posted by "sathish (JIRA)" <ji...@apache.org>.
[ 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:38 AM:
---------------------------------------------------------
A CORRECTION - The problem is observed in database created in cloudscape and not with database created with any of derby versions. sorry for the miscommunication. 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):
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.
> 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.
[jira] Issue Comment Edited: (DERBY-3721) Derby Database created in
10.1x is not compatibile when tried to access with 10.2x - Throws error
Posted by "sathish (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-3721) Derby Database created in 10.1x is not
compatibile when tried to access with 10.2x - Throws error
Posted by "sathish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
sathish updated DERBY-3721:
---------------------------
Attachment: derbymigration.zip
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.
[jira] Commented: (DERBY-3721) Derby Database created in 10.1x is
not compatibile when tried to access with 10.2x - Throws error
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604894#action_12604894 ]
Myrna van Lunteren commented on DERBY-3721:
-------------------------------------------
If I'm understanding the sequence of events, the database was created with Cloudscape 5.1 or earlier?
And then you created a database with Derby 10.1 and replaced the service.properties in the cloudscape database with the one in the empty derby.database? And that worked with derby 10.1?
Cloudscape (versions 5.1.60 and earlier) and Derby (versions 10.0 and higher) are not compatible. IBM has migration tools from 5.1 to 10. There's not much we can do as Derby developers.
The service.properties file does says explicitly 'do not edit'. You can't just replace it either, that's worse. If I misunderstood, apologies, please clarify.
If I understood correctly, you should contact IBM to see what your options are.
> 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.
[jira] Commented: (DERBY-3721) Derby Database created in 10.1x is
not compatibile when tried to access with 10.2x - Throws error
Posted by "sathish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605231#action_12605231 ]
sathish commented on DERBY-3721:
--------------------------------
Thanks very much for your inputs. I will use clouscape migration tool.
> 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
>
> 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.
[jira] Updated: (DERBY-3721) Derby Database created in 10.1x is not
compatibile when tried to access with 10.2x - Throws error
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-3721:
----------------------------------
I agree with myrna, if you are attempting to use a cloudscape 5.X database with derby it is not going to work, and we should mark
this JIRA entry as invalid.
Cloudscape was a closed source db, and thus the derby developers can't do anything to help with an automatic upgrade.
There may be generic jdbc level tools that will allow you to unload from one db and put the data into another db.
Derby only supports soft and hard upgrading among the various derby versions. There are some deep
storage level differences between the format of the underlying files between the two versions (even if the naming and location
of the files look similar), really the only upgrade path is to
export the data using your cloudscape software and reload it into a new derby db.
> 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.
[jira] Commented: (DERBY-3721) Derby Database created in 10.1x is
not compatibile when tried to access with 10.2x - Throws error
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604942#action_12604942 ]
Kathey Marsden commented on DERBY-3721:
---------------------------------------
That said Cloudscape 10.x *is* Derby. If you originally created your database with Cloudscape 10.1 then it should upgrade, but definitely you shouldn't be changing service.properties. The question is, did you start with Cloudscape 5.x or Cloudscape 10.x?
> 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.
[jira] Updated: (DERBY-3721) Derby Database created in 10.1x is not
compatibile when tried to access with 10.2x - Throws error
Posted by "sathish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
sathish updated DERBY-3721:
---------------------------
Attachment: (was: derbymigration.zip)
> 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
>
> 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.
[jira] Commented: (DERBY-3721) Derby Database created in 10.1x is
not compatibile when tried to access with 10.2x - Throws error
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604587#action_12604587 ]
Kathey Marsden commented on DERBY-3721:
---------------------------------------
Are you able to post your database? I am not able to reproduce with a simple 10.1 database
> 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
>
> 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.
[jira] Commented: (DERBY-3721) Derby Database created in 10.1x is
not compatibile when tried to access with 10.2x - Throws error
Posted by "sathish (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (DERBY-3721) Derby Database created in 10.1x is
not compatibile when tried to access with 10.2x - Throws error
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-3721.
-----------------------------------
Resolution: Invalid
Resolving as invalid. Database from 5.1 should never have been used with 10.x. It's pretty amazing it ever worked at all. As Mike said, there were incompatible store changes that should have caused trouble with 10.1.
> 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.