Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Stored procedures fail with a CURRENT PATH issue (DB2)

Updated on September 13, 2021

Called stored procedures can fail if the path to the schema is undefined. This error can appear at system startup or when you run an upgrade script.

For example, this message is generated on system startup when a call to SPPR_AGGREGATE_USAGE fails while trying to add licensing information to the database:

Daemon problem while running the procedure in License Database-General
There was a problem getting a list -444 42724 Routine "*_SECONDS" (specific name "MIDNIGHT_SECONDS2") is implemented with code in library or path "...n/db2clifn.a", function "CLI_udfMIDNIGHT_SECONDS2" which cannot be accessed. Reason code: "4".
From: (B381190ABEFC51C0297DBB54D26A6D625:(License Daemon))
      SQL: {call sppr_aggregate_usage}
      SQL Inserts:
Caused by SQL Problems.
Problem #1, SQLState 42724, Error code -444: Routine "*_SECONDS" (specific name "MIDNIGHT_SECONDS2") is implemented with code in library or path "...n/db2clifn.a", function "CLI_udfMIDNIGHT_SECONDS2" which cannot be accessed. Reason code: "4".


Both the DB2 CurrentFunctionPath property and the DB2 environment variable CURRENT_PATH specify the SQL path used to resolve unqualified data types and function names in SQL statements. CURRENT_PATH overrides CurrentFunctionPath.

To resolve the issue, set the value of CURRENT_PATH even if CurrentFunctionPath is already defined:

  1. Have your database administrator use the IBM DB2 command-line processor (CLP) to set CURRENT_PATH to include SYSIBM, SYSFUN, SYSPROC, and the data schema name. The data type is string, and the value is a comma-separated list of schema names. All values must be in quotes. For example:


    where schema is the name of your data schema.

  2. Re-create the SPPR_AGGREGATE_USAGE stored procedure.

  • Previous topic Issue: Update DB2 z/OS stored procedures sppc_data_uniqueid and UNIQID to prevent infinite loop and improve performance
  • Next topic System won't start when using DB2 version 9.5

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us