DB2 Package Issues and solution

After the client has been upgraded from 10.1 to 11.1, and the server-side DB is version 10.1, the client executes an error when executing the SQL statement:

SELECT * from Ebcc.eol_item_info where eol_supp_no= ' E0085960901
sql0805n Package "Nullid. Sqlc2o26 0x4141414141664164 "was not found.
sqlstate=51002

Preliminary analysis: 

The package does not exist and should be caused by a large version upgrade of the database.

Workaround:

1. View the BND file that the corresponding package belongs to by using the following URL

2. There are two ways to resolve

2.1 Connect to database from client, perform bind operation

2.2 Upload the required BND packets to the server side and do the bind operation

DB2 "Select char (Authid, ten) as Authid,
Authidtype,
PRIVILEGE,
char (objectname,30) as OBJECTNAME
From Sysibmadm.privileges
where objectname= ' SYSLH205 ' "

DB2 Grant execute on the package nullid. Sqlc2o26 to Public
DB2 Connect to <database> user <username> using <password>
DB2 bind BINDFILE.BND Blocking all SQLError continue grant public
DB2 bind @db2cli. LST blocking all grant public SQLError continue clipkg 5

Reference:

DB2 Bind File and package Name List

DB2 Package Issues and solution