Hello, is there any issue transferring data from Oracle to BigQuery if one of the column is xml type? running replication with debug result, as you can see on the time, the process "hang" for like an hour https://cdn.discordapp.com/attachments/1210406123744796705/1460573559930884181/oracle_xml.log?ex=697934e0&is=6977e360&hm=0683757e4ef58a309a4c81ba5b32b4bb6e37f04a55697225c205bc12c902ebee&

Hey @paradiso this seems to be a 3rd party driver issue. The work-around to cast as CLOB using custom SQL (with

(XML_COL).getclobval()

). In the next release this will be done automatically.

hey, after changing to use custom sql with getClobVal, it resulted in another error. here is the log snippet with --debug https://cdn.discordapp.com/attachments/1460573560367222814/1460947772844015777/oracle_xml_2.log?ex=6968c524&is=696773a4&hm=c69dbf9f9b3bbdf32d52c30dbda1a04d8441c6a89f8fff3d70cea6bfbe2b84cc&

select RECID, (XMLRECORD).getClobVal() as XMLRECORD from table_name

? i think you need to put the correct table name in the query.

i just change the real table name to table_name in the log, the actual replication are run with the real table_name

ah ok, and if you run the query yourself in your db client,

select * from ( select RECID, (XMLRECORD).getClobVal() as XMLRECORD from table_name ) where rownum <= 0

it works?

yes, it does work with <=0 and <=2 https://cdn.discordapp.com/attachments/1460573560367222814/1460952690258350226/image.png?ex=6968c9b8&is=69677838&hm=342b9498b27d2fffb1d17f940c11d6e4eb1c884b3f02c96e96ae42c970952e1c&

can you fully qualify? put schema/owner name too

in the custom sql the replication yaml?