TOracleObject: Invalid handle error w/ NULL XMLType in query

[Martin B]

Hi Marco,

Just observed some curious behavior in DOA v. 4.1.1. When we execute an query (or dataset) that has an XMLType column that is NULL we get an TOracleObject: Invalid handle when the corresponding Oracle session is freed.

(Looks like DOA may be trying to free something that has a null pointer. -- This sounds similar to the behavior described in the post #43172: TOracleObject: Invalid handle under PL/SQL Developer)

As a temporary work around we're using a view on the DB and converting the XMLType to a CLOB using the getClobVal() method of the XMLtype.

Oracle version: 10.2.0.4
OCI version: 11.2.0.1.0
DOA version: 4.1.1

 

[Marco Kalter]

Null columns are quite common, so I can't imagine this is a general null-xmltype issue. We'll try to reproduce and fix this.

 

[Martin B]

Only other thing to note is that this particular application uses pesistent fields in the datamodule (i.e. when TOracleQuery is executed in design mode and the fields are stored in the DM)