tracker issue : CF-4198596

select a category, or use search below
(searches all categories and all time range)
Title:

cfStoredProcedure won't work

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Workaround

Reporter/Name(from Bugbase): Jerome Lepage / Jerome Lepage ()

Created: 05/05/2017

Components: Database, Oracle

Versions: 2016

Failure Type: Others

Found In Build/Fixed In Build: 2016,0,04,302561 / 5.1.4 (Build 0001) /

Priority/Frequency: Normal /

Locale/System: / Linux

Vote Count: 0

Problem Description:

We want to migrate our application from CF9 to CF2016.
When we try to call a stored procedure, we have an error.
Apparently, the value of argument is not passed to the procedure.

Steps to Reproduce:

<CFSTOREDPROC PROCEDURE="SIPTRA.MAJ_CASCADETARIFFAIRE" DATASOURCE="#Application.DSN#">
<cfprocparam type="In" cfsqltype="CF_SQL_VARCHAR" dbvarname="idOrdre" value="JPG-000384B" null="No">
</CFSTOREDPROC>

Actual Result:
(part of cfcatch)

[Macromedia][Oracle JDBC Driver][Oracle] ORA-20920: MAJ_CASCADETARIFFAIRE( value="idOrdre=:v0" ) - RECHERCHE BRUT FACTURATION : 100 ORA-06512: at "SIPTRA.MAJ_CASCADETARIFFAIRE", line 44 ORA-06512: at line 1  
where (param 1) = [type='IN', class='java.lang.String', value='JPG-000384-02', sqltype='CF_SQL_VARCHAR']  

(param 1) = [type='IN', class='java.lang.String', value='JPG-000384-02', sqltype='CF_SQL_VARCHAR'] 

See that value passed is "JPG-000384-02" and called procedure recieived value "idOrdre=:v0"

Expected Result:

No error

Any Workarounds:

Attachments:

  1. May 05, 2017 00:00:00: error.PNG

Comments:

Jerome, DBvarname attribute was not honored in ColdFusion 9. It was enabled by default in ColdFusion 11 Update 3. Here's a bug you can refer: https://tracker.adobe.com/#/view/CF-3808734 In order to fix this issue for Oracle database, you have to prefix the dbvarname value with a colon ":". For example: dbvarname=":idOrdre" Please let me know if it does not work for you. Thanks, Nimit
Comment by Nimit S.
801 | June 02, 2017 05:29:34 AM GMT
Jerome, Please try the suggestion given the previous comment. It should resolve your issue. We are closing this issue. Please let us know if you face any challenge after following the suggestion.
Comment by Nimit S.
802 | July 07, 2017 12:29:33 PM GMT