Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / January 2006

Tip: Looking for answers? Try searching our database.

SQL0444N Reason Code 4 SQLSTATE=42724

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
GarthVader - 24 Jan 2006 21:20 GMT
I'm new to DB2 and am trying to execute a parameterized stored
procedure from within a VB 6.0 application.  We're using DB2 WSE
version 8.2 with fixpack 10 running on a Windows Small Business Server
2003.  I created the stored procedure on the DB2 server.  When I call
the sp from within my VB code, it uses a DSN to connect to the
database.  The DSN uses the IBM DB2 ODBC Driver.  I get the following
error message:

Error: [IBM][CLI Driver][DB2/NT] SQL0444N Routine "*PATIENTS" (specific
name "SQL060124151726030") is implemented with code in library or path
"...ISITS_PATIENT", function "p_INS_VISITS_PATIENTS" which cannot be
accessed.  Reason code: "4". SQLSTATE=42724

Security is set up on the database and I have ensured that the proper
groups have permissions to execute the stored procedure in question as
well as to perform SELECT and INSERT operations on the underlying
table.

All other stored procedures seem to function correctly when called from
the application.  It is only with this newly created sp that I receive
the error message.  All other sp's were created by the previous
developers.  This is the only sp I have created and I used the
Development Center to create it.

Does anyone know what might be causing this error?
Serge Rielau - 24 Jan 2006 22:46 GMT
> I'm new to DB2 and am trying to execute a parameterized stored
> procedure from within a VB 6.0 application.  We're using DB2 WSE
[quoted text clipped - 21 lines]
>
> Does anyone know what might be causing this error?

Take a look at the definition of the stored procedure.
Verify that the EXTERNAL library is indeed where it's supposed to be.
Also verify that DB2 has permissions to access the directory.
Is this a CLR procedure, Java, C?
One thing is for sure: The error has nothing to do with your VB app.

Cheers
Serge
Signature

Serge Rielau
DB2 Solutions Development
DB2 UDB for Linux, Unix, Windows
IBM Toronto Lab

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.