Feedback
Did this article resolve your question/issue?

   

Article

Shadow JDBC Driver returns wrong output when making metadata calls for DB2 Stored procedures

Information

 
TitleShadow JDBC Driver returns wrong output when making metadata calls for DB2 Stored procedures
URL NameProgress-7-3-JDBC-Driver-returning-wrong-output-when-making-metadata-calls-for-DB2-Sp
Article Number000147414
EnvironmentProduct: Shadow JDBC Driver
Version: 7.3.6725
OS: JAVA
Database: DB2
Application: All supported applications
Question/Problem Description
The Shadow 7.3 JDBC Driver returns wrong output when making metadata calls for DB2 Stored procedures.
When calling getProcedureColumns, the COLUMN_TYPE for output parameters is returned as COLUMN_TYPE = 3. The COLUMN_TYPE should be 4.
Steps to Reproduce
Clarifying Information
DDL used :
CREATE PROCEDURE SP_TEST1 (IN IN_PRM1 Char(1) , IN IN_PRM2 Char(1) , OUT PRM_OUT1 Char(1) , OUT PRM_OUT2 Char(1))
   p1:Begin
        
       SET PRM_OUT1 = IN_PRM1;
       SET PRM_OUT2 = IN_PRM2;
            
   END p1

Steps to repro :
  • Call DatabaseMetaData.getProcedureColumns(null, null, "SP_TEST1", null);
Error Message
Defect NumberDefect 26320
Enhancement Number
Cause
Resolution
Fixed in hot fix 7.3.6727.
Contact "SupportLink" to obtain this hot fix.
Workaround
Notes
Last Modified Date12/4/2015 3:10 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.