If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > .Net SQL0444N sql routine cannot be accessed

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-29-04, 11:56
gar34 gar34 is offline
Registered User
 
Join Date: May 2003
Posts: 1
Question .Net SQL0444N sql routine cannot be accessed

Hi,
I'm calling a procedure from .Net and I get the following error
System.Data.Odbc.OdbcException Error [42724][IBM][CLI Driver][DB2/NT] SQL0444N Routine "*OLIST_D" [sepcific name "Portfoliolist_D"] is implemented with code in library or path qlproc\calib01\db2admin\P0533754", function "pgsjmp" which cannot be accessed reason code 4 SQLState=42724.

This is a really strange error. I have 2 databases one live and one staging both running on the same machine.

Calib01 = Staging and Calib02=Live

The procedures work before I rebuild the database in both instances of the application. When I rebuild it fails on the live but the error message I get indicates that the code is on the staging database.

a. I don't know why this is failing in the first place
b. Does db2 look through it's catalogue and for any procedures with a specific name on a machine, or why do I get an error message with another database name in my error.

Any help greatly appreciated.
Slán
Gar
Reply With Quote
  #2 (permalink)  
Old 04-29-04, 14:13
J Petruk J Petruk is offline
Registered User
 
Join Date: Mar 2004
Location: Toronto, ON, Canada
Posts: 513
Quote:
Originally Posted by gar34
Hi,
I'm calling a procedure from .Net and I get the following error
System.Data.Odbc.OdbcException Error [42724][IBM][CLI Driver][DB2/NT] SQL0444N Routine "*OLIST_D" [sepcific name "Portfoliolist_D"] is implemented with code in library or path qlproc\calib01\db2admin\P0533754", function "pgsjmp" which cannot be accessed reason code 4 SQLState=42724.

This is a really strange error. I have 2 databases one live and one staging both running on the same machine.

Calib01 = Staging and Calib02=Live

The procedures work before I rebuild the database in both instances of the application. When I rebuild it fails on the live but the error message I get indicates that the code is on the staging database.

a. I don't know why this is failing in the first place
b. Does db2 look through it's catalogue and for any procedures with a specific name on a machine, or why do I get an error message with another database name in my error.

Any help greatly appreciated.
Slán
Gar
The PATH would have been provided with the CREATE PROCEDURE command, the NAME option, that's where db2 is getting the path from.

Try:
select IMPLEMENTATION from syscat.procedures where SPECIFICNAME = 'Portfoliolist_D'

You should be able to use "ALTER PROCEDURE <procname> EXTERNAL NAME '<newname>'" to fix it, although I'm not clear on exactly what you've done to get into this situation!
__________________
--
Jonathan Petruk
DB2 Database Consultant
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On