Db2- SQL Error -805 Resolution

Here are four SQL queries that will give an idea on reason for -805 error:

Query 1: Display the DBRMs in the member list for the plan.

SELECT PLCREATOR, PLNAME, NAME, VERSIONF
ROM SYSIBM.SYSDBRM
WHERE PLNAME = 'plan-name';

If no rows are returned, then the plan was bound without a member list.

Query 2: Display the entries in the package list for the plan.

SELECT LOCATION, COLLID, NAME
FROM SYSIBM.SYSPACKLIST
WHERE PLANNAME = 'plan-name';

If no rows are returned, then the plan was bound without a package list.

Query 3: Display the CURRENTSERVER value specified on the BIND subcommand for the plan.

SELECT NAME, CURRENTSERVER
FROM SYSIBM.SYSPLAN
WHERE NAME = 'plan-name';

Query 4: Determine if there is a matching package in SYSPACKAGE

If the package is remote, put the location name in the FROM clause. If the collection-id value in the message is blank, use this version of the query:

SELECT COLLID, NAME, HEX(CONTOKEN),VERSION
FROM location-name.SYSIBM.SYSPACKAGE
WHERE NAME = 'dbrm-name'AND HEX(CONTOKEN) = 'consistency-token';

If the collection-id value in the message is not blank, use this version of the query:

SELECT COLLID, NAME, HEX(CONTOKEN),VERSION
FROM location-name.SYSIBM.SYSPACKAGE
WHERE NAME = 'dbrm-name'AND HEX(CONTOKEN) = 'consistency-token';AND COLLID = 'collection-id';

If no rows are returned, the correct version of the package was not bound.

Srini

Data Engineer with deep AI and Generative AI expertise, crafting high-performance data pipelines in PySpark, Databricks, and SQL. Skilled in Python, AWS, and Linux—building scalable, cloud-native solutions for smart applications.