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 > XSR Registration with Stored Procedures

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-19-07, 12:37
Gandalf-mog Gandalf-mog is offline
Registered User
 
Join Date: Apr 2007
Posts: 4
XSR Registration with Stored Procedures

I am trying to register an XML Schema using ODBC interface. I am calling the Stored Procedure in the following way:

CALL SYSPROC.XSR_REGISTER ('USER', 'Address', 'C:\\Address.xsd',?, NULL)

I get the following error message:

42886(-469)[IBM][CLI Driver][DB2/NT] SQL0469N The parameter mode (IN, OUT, or INOUT) is not valid for a parameter in procedure "XSR_REGISTER" with specific name "XSR_REGISTER" (parameter number "0", name "RSCHEMA"). SQLSTATE=42886

I have also tried this with using the SQLBindParameters method which seems to work but at execution time I get the same message.

I am really out of clues what is going on here and my guess that it is now either a bug or an issue with how to call CLI methods.

I have of course in the SQLBindParameters method played around with the IN , OUT, INOUT modes, but this made no difference.

Any help here would be appreciated.

Regards,
Mohan
Reply With Quote
  #2 (permalink)  
Old 04-20-07, 10:50
n_i n_i is offline
:-)
 
Join Date: Jun 2003
Location: Toronto, Canada
Posts: 4,449
How'bout replacing NULL with CAST(NULL AS BLOB(5M))?
Reply With Quote
  #3 (permalink)  
Old 04-20-07, 11:58
Gandalf-mog Gandalf-mog is offline
Registered User
 
Join Date: Apr 2007
Posts: 4
No difference

I tried this but found no difference. The only hint that I have received is that this could be a DB2 bug fixed in the FixPack 2.

Internally I am using the ODBC methods, but i think its a problem of the database because other apps that use ODBC are returning to me the same message.

If you know anything about the issue would be much appreciated.

Thanks,
Mohan
Reply With Quote
  #4 (permalink)  
Old 04-21-07, 05:28
stolze stolze is offline
Registered User
 
Join Date: Jan 2007
Location: Jena, Germany
Posts: 2,662
The 2nd parameter of the procedure is an INOUT parameter (http://publib.boulder.ibm.com/infoce.../c0022710.htm). So have you tried to use SQLBindCol() to provide some storage for the output value?
__________________
Knut Stolze
IBM DB2 Analytics Accelerator
IBM Germany Research & Development
Reply With Quote
  #5 (permalink)  
Old 05-03-07, 12:25
Gandalf-mog Gandalf-mog is offline
Registered User
 
Join Date: Apr 2007
Posts: 4
Thanks... this was the trick!
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