 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussion Groups Database Servers DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybaseDesktop Databases FileMakerFoxProMS AccessParadoxGeneral General DB TopicsDatabase TheoryRelated Topics Java Development.NET DevelopmentVB DevelopmentMore Topics ... |
Database Forum / DB2 Topics / January 2006Problem with package not found
Running Db2 8.1 w Fixpack 9. Recently upgraded to this level. An application attempting a load receives the following error Error Error 1 2005-12-29 14:55:26 SQLError: sqlstate 51002: [IBM][CLI Driver][DB2/6000] SQL0805N Package "NULLID.SYSLH103 0X5359534C564C3031" was not found. SQLSTATE=51002 Have done a rbind all, also db2 "bind @db2ubind.lst blocking all grant public" and db2 "bind @db2cli.lst blocking all grant public" In the /sqllib/bnd directory I've done a grep for SYSLH103 and anything close but its not there. Also no package coming back from a query to syscat.packages with that name. Any suggestions would be appreciated. Thanks in advance. > Running Db2 8.1 w Fixpack 9. > [quoted text clipped - 14 lines] > In the /sqllib/bnd directory I've done a grep for SYSLH103 and > anything close but its not there. You most likely also need to run the 'db2jdbcbind' command. Search the online docs at http://tinyurl.com/bslng for it. Check out this link for a possible solution: http://www-1.ibm.com/support/docview.wss?rs=71&uid=swg21208123&loc=en I ran the suggested command db2 bind @db2cli.lst blocking all grant public sqlerror continue CLIPKG 5 Now the job is failing looking for package nullid.SYSLH106 Is there anyway of determining how many packages this app will need? > I ran the suggested command > db2 bind @db2cli.lst blocking all grant public sqlerror continue CLIPKG [quoted text clipped - 3 lines] > > Is there anyway of determining how many packages this app will need? Count the number of needed handles, there's a description about CLI handles in the DB2 docs at http://tinyurl.com/7m9hc Thanks..this is very good information. It seems to be saying that I would need to know the number of packges the app is using in order to determine the best value to set CLIPKG value. Is that correct? > Thanks..this is very good information. It seems to be saying that I > would need to know the number of packges the app is using in order to > determine the best value to set CLIPKG value. Is that correct? As far as I understand you have to count the number of handles needed by your application. I'm not familiar with CLI programming but maybe the application allocates handles and doesn't release them when they are not needed anymore. > I ran the suggested command > db2 bind @db2cli.lst blocking all grant public sqlerror continue CLIPKG [quoted text clipped - 3 lines] > > Is there anyway of determining how many packages this app will need? This doesn't happen to be a perl application, does it? I ran into a situation using an older build ActivePerl with DBD::DB2 that had the same issue -- no matter how many CLI packages I bound I would eventually run out. The only way we could figure out how to release the handles was to disconnect and reconnect after X transactions. However, after we upgraded to the most current release of perl (but using the same DBI and DBD::DB2 modules) the problem was resolved. Thanks...not Its not perl. We've opened an SR with Siebel as this happened after a recent Siebel upgrade. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.