Menu

#69 SqlException returned if no schema matches

closed
5
2008-10-07
2008-09-17
No

Running schemaSpy with either no schema defined or an invalid schema definition results in SqlException.

For example:

<java jar="${lib}/schemaSpy_3.1.1.jar"
fork="true">
<arg line="-t udbt4"/>
<arg line="-host ${db.host}"/>
<arg line="-port ${db.port}"/>
<arg line="-db ${database}"/>
<arg line="-u ${db.userid}"/>
<arg line="-p ${db.password}"/>
<arg line="-s NONEXISTENT"/>
<arg line="-cp ${DB2_LIB}/db2jcc.jar:${DB2_LIB}/db2jcc_license_cu.jar"/>
<arg line="-o ${reports.data.model.dir}"/>
</java>

results in:

[java] Using database properties:
[java] [/local/work/seascape/primhd_app/lib/schemaSpy_3.1.1.jar]/net/sourceforge/schemaspy/dbTypes/udbt4.properties
[java] Connected to DB2/LINUXX8664 - SQL09050
[java]
[java]
[java] com.ibm.db2.jcc.b.SqlException: [jcc][t4][10120][10898][3.50.152] Invalid operation: result set is closed. ERRORCODE=-4470, SQLSTATE=null
[java] at com.ibm.db2.jcc.b.wc.a(wc.java:55)
[java] at com.ibm.db2.jcc.b.wc.a(wc.java:102)
[java] at com.ibm.db2.jcc.b.jk.Bb(jk.java:3987)
[java] at com.ibm.db2.jcc.b.jk.c(jk.java:273)
[java] at com.ibm.db2.jcc.b.jk.next(jk.java:258)
[java] at net.sourceforge.schemaspy.model.Database.initTables(Database.java:122)
[java] at net.sourceforge.schemaspy.model.Database.<init>(Database.java:27)
[java] at net.sourceforge.schemaspy.SchemaSpy.<init>(SchemaSpy.java:12)
[java] at net.sourceforge.schemaspy.Main.main(Main.java:180)
[java] Gathering schema details

Also occurs with schemaSpy.jar from trunk.

Discussion

  • John Currier

    John Currier - 2008-09-17

    SVN revision 465 will make that exception go away, resulting in a message about not finding any tables.

     
  • John Currier

    John Currier - 2008-09-23

    Resolved in release 4.0.0.

     
  • John Currier

    John Currier - 2008-09-23
    • status: open --> pending
     
  • SourceForge Robot

    • status: pending --> closed
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     

Log in to post a comment.