CLOB created which is empty cannot be selected by the LWJDBC and placed into BP as a primary document.

Technote (troubleshooting)


Problem(Abstract)

CLOB created which is empty cannot be selected by the LWJDBC and placed
into BP as a primary document.

Cause

Code fix required.

Diagnosing the problem

Simulation Steps

1. Create Table

CREATE TABLE "SI522"."EMPTY_CLOB" ( "ID_DATA" NUMBER(10), "DATA" CLOB,
CONSTRAINT "id_dataclob_pk" PRIMARY KEY ("ID_DATA") VALIDATE )

2. Insert empty clob

INSERT INTO EMPTY_CLOB (ID_DATA,DATA) VALUES (1,EMPTY_CLOB())

3. Create LWJDBC adapter SEELightweightJDBCAdapter using oraclePool

4. Run bp :-

<process name = "TEST_EMPTY_BLOB">
<sequence name="Start Empty_CLOB">
<operation name="Retrieve empty clob">
<participant name="SEELightweightJDBCAdapter"/>
<output message="LightweightJDBCAdapterTypeInputMessage">
<assign to="result_name">data_file</assign>
<assign to="sql">SELECT DATA FROM EMPTY_CLOB WHERE ID_DATA = 1</assign>
<assign to="row_name">RowResult</assign>
<assign to="query_type">SELECT</assign>
<assign to="result_name">QueryResult</assign>
<assign to="." from="*"></assign>
</output>
<input message="inmsg">
<assign to="PrimaryDocument" from="doc-1/@SCIObjectID"></assign>
<assign to="."
from="DocToDOM(PrimaryDocument,&apos;false&apos;)"></assign>
</input>
</operation>
</sequence>
</process>


5. See results. No PrimaryDocument is created as the CLOB is not
retrived because doc-1/@SCIObjectID is not created.

Resolving the problem

Please apply IBM B2B Sterling Integrator patch 502040

Historical Number

23349
999
706

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Sterling B2B Integrator
Adapters

Software version:

5.2

Operating system(s):

All

Software edition:

All Editions

Reference #:

1590372

Modified date:

2013-04-26

Translate my page

Machine Translation

Content navigation