Writing CLOB Data to a File in an ODI 11.1.1.7 Procedure Using The Bind Mechanism Results in Incorrect oracle.sql.CLOB@<VALUE> Data (Doc ID 1625893.1)

Last updated on JUNE 16, 2022

Applies to:

Symptoms

When using the bind mechanism in an ODI 11.1.1.7 procedure to write CLOB data into a file having:

• A select clob..  SQL instruction on the Command on source tab
• An odiOutfile on the Command on target tab

Using the following setup :

Steps:

1. In an Oracle database (in a schema you have already configured in your topology, so you have a logical model associated with it), create the following table:

   Then, execute it.

   The resulting file contains data as oracle.sql.CLOB@<VALUE> instead of the data stored in the CLOB database column.

   Changes

    

   Cause

   Sign In	To view full details, sign in with your My Oracle Support account.
   Register	Don't have a My Oracle Support account? Click to get started!

   ---

   In this Document
   

   Symptoms

   Changes

   Cause

   Solution

   References

   ---

   
   My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.