I'd found that out, too, and ended up adding error catching in the PL/SQL to
always make sure that I opened the ref cursor and passed it back, even if it
was empty.

----- Original Message -----
From: "Adrocknaphobia"

> ** this is a response to a post from 3/9/2004 which never seemed to be
> resolved **
>
> Explanation of CFMX Oracle JDBC database error "Unsupported Data
Conversion"
>
> This issue occurs when using RefCursors to return queries from oracle
> via a stored procedure.
>
> When you declare a RefCursor it is NULL until it is populated with the
> OPEN ... FOR syntax.
>
> If any sort of error or premature return from the stored procedure
> occurs, Oracle still passes the RefCursor to CFMX. CFMX cannot convert
> the NULL RefCursor to an empty query. Now, if oracle performed and
> OPEN...FOR on the cursor and no rows were returned, then the RefCursor
> is successfully passed back to CFMX as it is no longer considered
> NULL.
>
> This one can be a little tricky to debug, especially you have good
> exception handling. In my case I was catching and returning an error
> before it got to populate the RefCursor. But CFMX threw it's
> "Unsupported Data Conversion" before it threw the actual error.
>
> This is def a driver/cfmx issue as you will not see this error in any
> form in SQL*Plus.
>
> Adam
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to