DB2 Stored Procedures

Posted on 2005-03-10
Medium Priority
Last Modified: 2010-05-18
Our DBAs recently upgraded our AIX based DB2 database to version 8.2.  Due to business limitations, we are accessing the system using V6 clients.  All stored procedures built prior to the ugrade function perfectly under this arrangement, but new procedures built using either the V7 client or the V8.2 client fail to run producing the following error message:

Error: SQL0444N  Routine "*nQualSum" (specific name "SQL050217160054980") is implemented with code in library or path "...nQualSum", function "DBAWD001.SP0600AdminQualSum" which cannot be accessed.  Reason code: "4".  SQLSTATE=42724
 (State:42724, Native Code: FFFFFE44)

If we build and run the SP using only V8.2 clients the work, but if we build on V8.2 the will not run for V7 and V6, and if we build using V7 client they will not run on any of the clients.  If cannot upgrade the clients to V8.2, does anybody have a solution for this?
Question by:speke
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 13

Accepted Solution

ghp7000 earned 2000 total points
ID: 13511761
Generally speaking, SQL0444n return code 4 is equivalent to the blue screen of death in Windows, very difficult to diagnose and correct. It relates to the compiler settings, more specifically the export path of the stored procedure, or the fact that prior to the upgrade, the stored procedure relied upon certain MS dll's to be present in the system in order to function and perhaps those clients are expecting those function calls to be resolved.
Since V8.2 no longer requires the external MS compiler, I would ask this question directly to IBM support, as there are just way too many variables involved with stored procedures.

You may get a clue as to what is wrong exactly by looking at the db2diag log, if there is an internal return code there, it can be deciphered for help in solving this problem.
I would also try setting the dbset parameters for the compiler settings that were used prior to the upgrade.
Another way perhaps is to distribute the SP with the put command.


Expert Comment

ID: 13519674
Were the binds run for each of the different client versions against the UDB?


Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

November 2009 Recently, a question came up in the DB2 forum regarding the date format in DB2 UDB for AS/400.  Apparently in UDB LUW (Linux/Unix/Windows), the date format is a system-wide setting, and is not controlled at the session level.  I'm n…
Recursive SQL in UDB/LUW (it really isn't that hard to do) Recursive SQL is most often used to convert columns to rows or rows to columns.  A previous article described the process of converting rows to columns.  This article will build off of th…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
Have you created a query with information for a calendar? ... and then, abra-cadabra, the calendar is done?! I am going to show you how to make that happen. Visualize your data!  ... really see it To use the code to create a calendar from a q…
Suggested Courses

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question