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 > Problem executing stored procedure after transfer to different machine (PUT ROUTINE)

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 05-28-04, 02:56
antti antti is offline
Registered User
 
Join Date: May 2004
Posts: 11
Problem executing stored procedure after transfer to different machine (PUT ROUTINE)

Hi, first of all my skills with DB2 are quite low level so propably there is some simple solution to this that I havent just figured out

I have developed stored procedure in my own machine (Windows XP) and it's working just fine in my machine. Then I would like to transfer the compiled stored procedure to development server (Windows 2003), DB2 version is 8.1.4 on both machines. I have done the transfer using GET ROUTINE / PUT ROUTINE and apparently it went fine (no error messages FROM PUT routine command on development server).

But now when I try to execute the stored procedure in development server it gives the following error message (stored procedure name is SET_PARTNER_STATE):

[IBM][CLI Driver][DB2/NT] SQL0444N Routine "*ER_STATE" (specific name
"SQL040525082840954") is implemented with code in library or path
"...proc\DB_PROJECT\SCHEMA1\P6214173", function "pgsjmp" which
cannot be accessed. Reason code:"4".
SQLSTATE=42724

Any ideas how to get the stored procedure working in development server ?


Regards,
Antti
Reply With Quote
  #2 (permalink)  
Old 05-28-04, 03:58
sathyaram_s sathyaram_s is offline
Super Moderator
 
Join Date: Aug 2001
Location: UK
Posts: 4,534
hmmm ... I don't think you can develop on XP and transfer it to Windows 2003 ..
Have you tried deploying the extracted routines to another XP database and confirm that the extracted routines were indeed errorfree

Cheers
Sathyaram
__________________
Visit the new-look IDUG Website , register to gain access to the excellent content.
Reply With Quote
  #3 (permalink)  
Old 05-28-04, 06:32
Parijat Parijat is offline
Registered User
 
Join Date: May 2004
Posts: 6
GET ROUTINE and PUT ROUTINE works only when both the databases are on machines having same operating system thats why your procedure is not working
Reply With Quote
  #4 (permalink)  
Old 05-28-04, 06:57
antti antti is offline
Registered User
 
Join Date: May 2004
Posts: 11
So it's that strict about the operating system where the stored procedure has been compiled. I thinked first that the restriction is only like Windows<-->Unix<-->etc. not also like between different versions of Windows OS.

Well it seem's that I then should install the C compiler also in development server

Thanks for clarification.
Reply With Quote
  #5 (permalink)  
Old 03-04-05, 19:50
nnbinh nnbinh is offline
Registered User
 
Join Date: Mar 2005
Posts: 1
Lightbulb You need msvcr.dll or msvcr71.dll

I don't think so. You need copy msvcr.dll (if you built with MS VC++ 6) or msvcr70.dll (if you built with ms VC++ 7.0), msvcr71.dll (if you built with MS VC++ 7.1).

Cheers,
Ngoc Binh
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