[jira] [Created] (DERBY-6290) dblook fails on soft upgraded 10.3 database with ERROR 42X05: Table/View 'SYS.SYSROLES' does not exist.

["Kathey Marsden (JIRA)" <ji...@apache.org>]

Kathey Marsden created DERBY-6290:
-------------------------------------

             Summary: dblook fails on soft upgraded 10.3 database with  ERROR 42X05: Table/View 'SYS.SYSROLES' does not exist.
                 Key: DERBY-6290
                 URL: https://issues.apache.org/jira/browse/DERBY-6290
             Project: Derby
          Issue Type: Bug
          Components: Tools
    Affects Versions: 10.10.1.1
            Reporter: Kathey Marsden


With 10.10 and presumably earlier releases, dblook fails on a soft upgraded 10.3 database with 
ERROR 42X05: Table/View 'SYS.SYSROLES' does not exist.

To reproduce create a 10.3 database:
$java org.apache.derby.tools.ij
ij version 10.3
ij> connect 'jdbc:derby:tenthreedb;create=true';
ij> quit;

Then run dblook with 10.10.
$java org.apache.derby.tools.dblook -d jdbc:derby:tenthreedb
-- Timestamp: 2013-07-09 07:29:21.195
-- Source database is: tenthreedb
-- Connection URL is: jdbc:derby:tenthreedb
-- appendLogs: false

-- Note: At least one unexpected error/warning message was
-- encountered during DDL generation.  See dblook.log
-- to review the message(s).

The error is in dblook.log
java.sql.SQLSyntaxErrorException: Table/View 'SYS.SYSROLES' does not exist.
	at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:91)
	at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Util.java:327)
	at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(TransactionResourceImpl.java:424)
	at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(TransactionResourceImpl.java:353)
	at org.apache.derby.impl.jdbc.EmbedConnection.handleException(EmbedConnection.java:2400)
	at org.apache.derby.impl.jdbc.ConnectionChild.handleException(ConnectionChild.java:85)
	at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:700)
	at org.apache.derby.impl.jdbc.EmbedStatement.executeQuery(EmbedStatement.java:156)
	at org.apache.derby.impl.tools.dblook.DB_Roles.doRoles(DB_Roles.java:47)
	at org.apache.derby.tools.dblook.go(dblook.java:549)
	at org.apache.derby.tools.dblook.<init>(dblook.java:142)
	at org.apache.derby.tools.dblook.main(dblook.java:97)
Caused by: java.sql.SQLException: Table/View 'SYS.SYSROLES' does not exist.
	at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:42)
	at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(SQLExceptionFactory40.java:125)
	at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:71)
	... 11 more
Caused by: ERROR 42X05: Table/View 'SYS.SYSROLES' does not exist.
	at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:278)
	at org.apache.derby.impl.sql.compile.FromBaseTable.bindTableDescriptor(FromBaseTable.java:2652)
	at org.apache.derby.impl.sql.compile.FromBaseTable.bindNonVTITables(FromBaseTable.java:2264)
	at org.apache.derby.impl.sql.compile.FromList.bindTables(FromList.java:321)
	at org.apache.derby.impl.sql.compile.SelectNode.bindNonVTITables(SelectNode.java:511)
	at org.apache.derby.impl.sql.compile.DMLStatementNode.bindTables(DMLStatementNode.java:197)
	at org.apache.derby.impl.sql.compile.DMLStatementNode.bind(DMLStatementNode.java:135)
	at org.apache.derby.impl.sql.compile.CursorNode.bindStatement(CursorNode.java:268)
	at org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericStatement.java:400)
	at org.apache.derby.impl.sql.GenericStatement.prepare(GenericStatement.java:99)
	at org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(GenericLanguageConnectionContext.java:1111)
	at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:691)
	... 5 more
-- **--> DEBUG: Table/View 'SYS.SYSROLES' does not exist.





--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira