Copy link to clipboard
Copied
Upgraded from CF10 to CF11 update 5 ( with hotfix hf1100-3971083.jar )
DB (DB2 v10.2)
getting an error on code that calls a stored proc.
Error Executing Database Query.
[Macromedia][DB2 JDBC Driver][DB2]ILLEGAL SYMBOL =;
The error occurred in ...: line 238
236 : <cfstoredproc datasource="#application.dsn#" procedure="LIVE.SP" >
237 : <cfprocparam type="In" cfsqltype="CF_SQL_BIGINT" dbvarname="STOPID" null="yes" />
238 : <cfprocparam type="In" cfsqltype="CF_SQL_INTEGER" dbvarname="POID" null="no" value="#val( qry.id )#" />
239 : </cfstoredproc>
The actual code looks like this - and works fine in CF10....
"qry" IS returning a value for "id"
<cfloop query="qry" >
<cfstoredproc datasource="#application.dsn#" procedure="LIVE.SP" >
<cfprocparam type="In" cfsqltype="CF_SQL_BIGINT" dbvarname="STOPID" null="yes" />
<cfprocparam type="In" cfsqltype="CF_SQL_INTEGER" dbvarname="POID" null="no" value="#val( qry.id )#" />
</cfstoredproc>
</cfloop>
This happens IF or NOT the 'debugging' is turned on (per hotfix hf1100-3971083.jar)
It seems there are others claiming cfprocparam issues - but the solutions to those issues are not fixing THIS issue.
Any Ideas?
Copy link to clipboard
Copied
Have you taken a look at this thread - Stored Procedures stop working after Coldfusion 11 install (OS X 10.10.1)
As you moved from CF10 to 11u5 it might apply to you.
Copy link to clipboard
Copied
Looking at this post -
I tried adding the "@" (which IBM docs say IS the param symbol - IBM Knowledge Center)
<cfstoredproc datasource="#application.dsn#" procedure="LIVE.SP" >
<cfprocparam type="In" cfsqltype="CF_SQL_BIGINT" dbvarname="@STOPID" null="true" >
<cfprocparam type="In" cfsqltype="CF_SQL_INTEGER" dbvarname="@POID" value="0" null="no" >
</cfstoredproc>
NO LUCK - SAME ERROR
I also tried hard coding the value being passed - NO LUCK - SAME ERROR
Copy link to clipboard
Copied
I assume the STOPID and POID vars are exactly correct as well? No misspelling at all?
On the DB2 server are you able to trace the request and get the full SQL that it thinks is being requested?