Page 1 of 1
Inserting a field of possible lenght 60K into DB2 CLOB
Posted: Mon Jul 12, 2010 11:40 am
by reachsam11
Hi, I have a requirement to load a huge text field (60K) in a text file into a DB2 CLOB field. I specified the fields in ODBC stage as LongVarChar. The job fails if i specify the LongVarChar lenght to be 60000. It accepts only 30000 as length. How can i handle 60K CLOB load.
Posted: Mon Jul 12, 2010 12:44 pm
by roydanlobo
You can specify the Longvarchar length '7463847'
Posted: Mon Jul 12, 2010 1:23 pm
by reachsam11
The job failed when i randomly specified as 60000 for lenght in LongVarChar.
Error 'APT_CombinedOperatorController,0: Fatal Error: Not bounded length.'
node_node1: ?? (13; SOL_SOCKET, SO_ERROR; 57; Socket operation on non-socket)
?? (15; SOL_SOCKET, SO_ERROR; 57; Socket operation on non-socket)
roydanlobo wrote:You can specify the Longvarchar length '7463847'
Posted: Wed Jul 14, 2010 8:56 am
by vivekgadwal
reachsam11 wrote:The job failed when i randomly specified as 60000 for lenght in LongVarChar.
Did you try having "LongVarChar" as unbounded? Meaning, no specification for length...
Posted: Wed Aug 11, 2010 3:18 pm
by reachsam11
How do i define LongVarChar field as unbounded. If i do not specify any length in ODBC stage to load into DB2 CLOB, the fatal error is "APT_CombinedOperatorController,0: Fatal Error: Not bounded length."
If i specify the length as 60000 or so, the job finished successfully, but only about 8K of data is loaded into CLOB field.
Posted: Mon Aug 23, 2010 3:01 pm
by reachsam11
I switched the ODBC stage to Dynamic RDBMS stage and loaded all the 60K data. Thanks!