Results 1 to 2 of 2
  1. #1
    Join Date
    Oct 2005

    Unanswered: Package not found.


    When I am trying to execute one of the shell script at unix box, which in turn calls a set of compiled stored procedures at DB2 database.
    I am getting the following error message in the dbmsg log: DB2 SQL error: SQLCODE: -805, SQLSTATE: 51002, SQLERRMC: NULLID.SYSLH203 0X5359534C564C3031

    Although the corresponding package for the Stored Procedure exists at the Database.

    What can be the reason for getting the 'package not found' error inspite of it being present at database.


  2. #2
    Join Date
    May 2003
    SQL0805N error when performing a DML statement on database.
    Technote (FAQ)

    SQL0805N error, Package.Nullid.SYSLH203 was not found. SQLSTATE=51002, returned when attempting to perform a DML statement on the database server from a remote client application.

    The package, SYSLH203, doesn't exist on the database server.

    Depending on the type of statement you are executing, DB2 will use a particular package on the server. By default DB2 creates three packages for each type of package. In this case NULLID.SYSLH2yy is reserved for statements with CURSORHOLD on and isolation level Cursor Stability. The package SYSLH203 means that DB2 is looking for the 4th package (200 is first, 201 is second, etc) of this type, but it does not exist. You can create more packages on the server by connecting to the database and issuing the following bind command from the /sqllib/bnd directory:

    db2 bind @db2cli.lst blocking all grant public sqlerror continue CLIPKG 5

    Note: CLIPKG 5 will create 5 large packages, and will give you the package that your application is looking for, as well as one more in this case.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts