This content has been marked as final. Show 4 replies
WLS properly wraps all vendor-specific types when using a connection pool. What you can do is to check the connection you are using to call the stored proc, and if it is a WL connection, call getVendorConnection() on it to get the oracle connection which is being wrapped.1 person found this helpful
Thanks for the response. How do I get the WLConnection to get the getVendorConnection method available? I have the DBTransaction class from my AM, but I can't cast it to a WLConnection class to use that method. Any ideas how to do this?
In the connection pool uncheck the property "Wrap Data Types".
By default, data type objects for Array, Blob, Clob, NClob, Ref, SQLXML, and Struct, plus ParameterMetaData and ResultSetMetaData objects are wrapped with a WebLogic wrapper. This allows for features like debugging and connection usage to be done by the server.
The wrapping can be turned off by setting this value to false. This improves performance, in some cases significantly, and allows for the application to use the native driver objects directly.
I am using Weblogic 10.3.0. I am also getting the same exception. But I don,'t see the option of unchecking Wrap Data Types under Connection Pool , Adavanced settings.
Could you please tell me how do I disable this option in weblogic 10.3.0.