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.

In article <1136315671.991456.196240@z14g2000cwz.googlegroups .com>,
datapro01@yahoo.com (datapro01@yahoo.com) says...
> 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.
>

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...1208123&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?

In article <1136396553.024146.136060@o13g2000cwo.googlegroups .com>,
datapro01@yahoo.com (datapro01@yahoo.com) says...
> 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?
>

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?

In article <1136400707.216427.164530@f14g2000cwb.googlegroups .com>,
datapro01@yahoo.com (datapro01@yahoo.com) says...
> 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.

datapro01@yahoo.com wrote:
> 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?
>

This doesn't happen to be a perl application, does it? I ran into a
situation using an older build ActivePerl with DBD:B2 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:B2 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.