Start of change

-992   PACKAGE package-name CANNOT BE EXECUTED OR DEPLOYED ON LOCATION location-name

Explanation

A mismatch in DB2® code levels prevents the package from being executed or deployed.

package-name
The name of the package.
location-name
The DB2 system where the deployment or execution was attempted.

One of the following conditions has occurred:

  • The package cannot be executed or deployed because of a mismatch in the level of the DB2 code between the system identified by location-name and the current server. The current server and the system identified by location-name might be the same system.
  • The representation of an SQL routine cannot be executed on the system. The package was bound at a different release or maintenance level than the system can support.

Deployment is the process of establishing an SQL routine at a remote location without regenerating the representation of that routine. The deployment requires that the remote server be able to understand the structures generated by the current server for the identified package. The difference in code level between the current server and the remote location makes this impossible. The difference might be in release levels or maintenance levels, but it is large enough that the package cannot be deployed from the current server to the remote location.

This condition might be specific to this particular package. Other packages might successfully be executed on this system or deployed from the current server to the remote location.

System action

The statement cannot be processed.

Programmer response

If this condition occurs when deploying a SQL routine, try again after DB2 at location-name is updated to the release or maintenance level that can support the package that is being deployed.

If this condition occurs in contexts other than deployment (for example, a package that was created prior to application of a PTF is no longer supported by the level of DB2 after the application of that PTF), then execute the ALTER PROCEDURE or ALTER FUNCTION statement with the REGENERATE clause for that version of the SQL routine at the current server to regenerate the package using the current maintenance level. The ALTER PROCEDURE or ALTER FUNCTION statement with the REGENERATE clause will cause a rebind of the package at the local server.

If the SQL routine required package replication at different servers, the process must be repeated for the regenerated SQL routine.

If variations of the package have been created locally with different collection IDs, those additional packages should also be explicitly rebound.

SQLSTATE

51008

End of change