NULLID.SYSSN300
in [DB2]
|
Prev: SQL0818N after V7 -> V8 migration.
Next: SQL1224N - A database agent could not be started to service a request
From: chrisg on 23 Mar 2006 19:29 Can anyone please help me and explain: [24/03/06 11:22:28:212 EST] 3e70982f WSRdbDataSour I DSRA8203I: Database product name : OS2 [24/03/06 11:22:28:332 EST] 3e70982f WSRdbDataSour I DSRA8204I: Database product version : DB2 UDB 6.1 [24/03/06 11:22:28:332 EST] 3e70982f WSRdbDataSour I DSRA8205I: JDBC driver name : IBM DB2 JDBC Universal Driver Architecture [24/03/06 11:22:28:342 EST] 3e70982f WSRdbDataSour I DSRA8206I: JDBC driver version : 2.8.46 [2006.03.24-11:22:28] (DEBUG ) [Thread-2] Database.executeQuery( sql = SELECT 1 FROM SYSIBM.SYSDUMMY1 ) [2006.03.24-11:22:29] (ERROR ) [Thread-2] WarpSQLException: au.com.warpspeed.database.exception.WarpSQLException: NULLID.SYSSN300 SQL : SELECT 1 FROM SYSIBM.SYSDUMMY1 SQL Message : NULLID.SYSSN300 SQL State : 51002 SQL Error Code: -805 Original Exception: com.ibm.db2.jcc.a.SqlException: NULLID.SYSSN300 How far back does backwards compatibility go anyway? Can 8.1/8.2 connect to a V7.1/7.2 database? Back to V6.1? Thanks, -Chris
From: Knut Stolze on 24 Mar 2006 04:47 chrisg(a)warpspeed.com.au wrote: > Can anyone please help me and explain: > > [24/03/06 11:22:28:212 EST] 3e70982f WSRdbDataSour I DSRA8203I: > Database product name : OS2 > > [24/03/06 11:22:28:332 EST] 3e70982f WSRdbDataSour I DSRA8204I: > Database product version : DB2 UDB 6.1 > > [24/03/06 11:22:28:332 EST] 3e70982f WSRdbDataSour I DSRA8205I: JDBC > driver name : IBM DB2 JDBC Universal Driver Architecture > > [24/03/06 11:22:28:342 EST] 3e70982f WSRdbDataSour I DSRA8206I: JDBC > driver version : 2.8.46 > [2006.03.24-11:22:28] (DEBUG ) [Thread-2] Database.executeQuery( sql = > SELECT 1 FROM SYSIBM.SYSDUMMY1 ) > [2006.03.24-11:22:29] (ERROR ) [Thread-2] WarpSQLException: > au.com.warpspeed.database.exception.WarpSQLException: NULLID.SYSSN300 > SQL : SELECT 1 FROM SYSIBM.SYSDUMMY1 > SQL Message : NULLID.SYSSN300 > SQL State : 51002 > SQL Error Code: -805 -805 = SQL0805 $ db2 "? sql805" SQL0805N Package "<package-name>" was not found. [snip] Try to bind the packages db2ubind.lst, db2schema.lst and db2cli.lst. $ cd sqllib/bnd $ db2 bind @db2ubind.lst $ db2 bind @db2schema.lst $ db2 bind @db2cli.lst -- Knut Stolze DB2 Information Integration Development IBM Germany
From: chrisg on 26 Mar 2006 19:23
Knut Stolze wrote: > chrisg(a)warpspeed.com.au wrote: > > > Can anyone please help me and explain: > > > > [24/03/06 11:22:28:212 EST] 3e70982f WSRdbDataSour I DSRA8203I: > > Database product name : OS2 > > > > [24/03/06 11:22:28:332 EST] 3e70982f WSRdbDataSour I DSRA8204I: > > Database product version : DB2 UDB 6.1 > > > > [24/03/06 11:22:28:332 EST] 3e70982f WSRdbDataSour I DSRA8205I: JDBC > > driver name : IBM DB2 JDBC Universal Driver Architecture > > > > [24/03/06 11:22:28:342 EST] 3e70982f WSRdbDataSour I DSRA8206I: JDBC > > driver version : 2.8.46 > > [2006.03.24-11:22:28] (DEBUG ) [Thread-2] Database.executeQuery( sql = > > SELECT 1 FROM SYSIBM.SYSDUMMY1 ) > > [2006.03.24-11:22:29] (ERROR ) [Thread-2] WarpSQLException: > > au.com.warpspeed.database.exception.WarpSQLException: NULLID.SYSSN300 > > SQL : SELECT 1 FROM SYSIBM.SYSDUMMY1 > > SQL Message : NULLID.SYSSN300 > > SQL State : 51002 > > SQL Error Code: -805 > > -805 = SQL0805 > > $ db2 "? sql805" > > SQL0805N Package "<package-name>" was not found. > > [snip] > > Try to bind the packages db2ubind.lst, db2schema.lst and db2cli.lst. > > $ cd sqllib/bnd > $ db2 bind @db2ubind.lst > $ db2 bind @db2schema.lst > $ db2 bind @db2cli.lst Did the first and last, but not the middle. I'll give it a go. Thanks. Can V8 connect back to a V6 database? -Chris |