IBM Support

Error: Discovery Task Failed: Problem writing BLOB/CLOB in Oracle Adapter.

Troubleshooting


Problem

A Discovery task fails with error messages similar to the following: 

Symptom

Error: Error generating map Map_7_DO_STAGE_CMBS_MBS_LOAN_To_DO_ASSET_976048214 for source tables STAGE_CMBS_MBS_LOAN(STAGE_CMBS_MBS_LOAN), STAGE_CMBS_COMMITMENT(STAGE_CMBS_COMMITMENT) and target table LOAN(LOAN) based on parent map Map_6_DO_STAGE_CMBS_MBS_LOAN_To_DO_ASSET_976048214: Problem writing BLOB/CLOB in Oracle Adapter. Object information: Map:fb0548ba1d35f57a024a5229d80a884a(Map_7_DO_STAGE_CMBS_MBS_LOAN_To_DO_ASSET_976048214)-Project:ef6b12d4ec263dfe01b7b3f4981c3820.  Completed Map Generation for Data Object Map DOMap1_DO_STAGE_CMBS_MBS_LOAN_to_DO_ASSET, Target Table LOAN. 1 table maps were generated. 0 redundant table maps were removed.  8 modified objects saved. Error: Discovery Task Failed: Problem writing BLOB/CLOB in Oracle Adapter. Object information: Map:fafb4d061d35f57a0037dbdbb21b4f3d(Map_6_DO_STAGE_CMBS_MBS_LOAN_To_DO_ASSET_976048214)-Project:ef6b12d4ec263dfe01b7b3f4981c3820. 

Resolving The Problem

This error message (Problem writing BLOB/CLOB in Oracle Adapter) often appears when the actual problem does not involve writing BLOB/CLOB. The real error is often due to deadlock or tablespace issues on the repository or staging database. 
To view the real error message, display the server log by selecting Start>Programs>InfoSphere Disovery>Discovery>Discovery Server>Discovery Server Log Viewer. 
When the error is due to tablespace issues on the repository database, entries similar to the following appear in the server log: 
2007-09-12 14:27:57,304 INFO [STDOUT] OracleAdapter problem 
2007-09-12 14:27:57,304 INFO [STDOUT] Connection: 128:oracle.jdbc.driver.T4CConnection@6506cd 
2007-09-12 14:27:57,304 INFO [STDOUT] java.io.IOException: ORA-01691: unable to extend lob segment AEU9IEOR.SYS_LOB0000096500C00008$$ by 32 in tablespace SH_USER_01 
To resolve this problem increase the tablespace and re-run the task. 
When the error is due to deadlock issues on the repository database, entries similar to the following appear in the server log: oracle.jdbc.driver.DatabaseError.SQLToIOException(DatabaseError.java:556) at 'oracle.jdbc.driver.OracleBlobOutputStream.flushBuffer(OracleBlobOutputStream.java:215) at oracle.jdbc.driver.OracleBlobOutputStream.flush(OracleBlobOutputStream.java:171) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:124)'

To resolve this issue simply add more table space and re-run the task and the error message will disappear 

[{"Product":{"code":"SSC6AW","label":"InfoSphere Discovery"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF033","label":"Windows"}],"Version":"4.1.1;4.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Product Synonym

Information in this article applies to: 
- Discovery 3.2.1
- Discovery 4.0.1 

Document Information

More support for:
InfoSphere Discovery

Software version:
4.1.1, 4.0

Operating system(s):
Windows

Document number:
128577

Modified date:
23 June 2018

UID

swg21406620

Manage My Notification Subscriptions