Feedback
Did this article resolve your question/issue?

   

Article

"Unexpected Network Error" occurs when accessing CLOB data from Oracle 12cR2 using Connect64 for ODBC v8.0.1 Oracle Wire Protocol driver

Information

 
Title"Unexpected Network Error" occurs when accessing CLOB data from Oracle 12cR2 using Connect64 for ODBC v8.0.1 Oracle Wire Protocol driver
URL Nameunexpected-network-error-occurs-when-accessing-data-from-oracle-12cr2-using-connect64-for-odbc-v8-0-1-oracle-wire-protocol-driver
Article Number000118590
EnvironmentProduct: Connect/Connect64 for ODBC Oracle Wire Protocol driver
Version: 08.01.2064 (B0250, U0166)
OS: All supported platforms
Database: Oracle 12cR2 (12.2)
Application: All supported applications
Question/Problem Description
Using Oracle 12c Release 2, DataDirect Oracle Wire Protocol drivers V8.0.1, when trying to fetch CLOB data that is 4130 characters long, the following error message occurs.
Steps to ReproduceDDL to reproduce problem:

DROP TABLE ODBCTest;
CREATE TABLE ODBCTest (QueryDefID NUMBER, QueryText CLOB);
DECLARE
v_val CLOB;
i NUMBER;
BEGIN
i:=0;
v_val := '';
WHILE(i<4130) LOOP
v_val := v_val||'x';
i:=i+1;
END LOOP;
INSERT INTO ODBCTest(QueryDefID,QueryText) VALUES(597,v_val);
COMMIT;
END;

Steps to reproduce problem:

You can find the ODBCTester.exe file in directory ODBCTester\x64\Debug
Run the program from a command line:
ODBCTester <datasource name> <uid> <password>

Observed results: (give a short description of the failure and then the exact program output)

Connecting to data source '80_ora_siem' as user 'scott'.

Executing: SELECT QueryDefID, QueryText FROM ODBCTest WHERE QueryDefID>595 ORDER BY QueryDefID
SQLSTATE = HY000
NATIVE ERROR = -5
MSG = DataDirectODBC Oracle Wire Protocol driverOracleUnexpected Network Error.


Example complete.

Press any key to continue . . .


Expected results:

There should not be any error
Clarifying Information
Error Message"[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]Unexpected Network Error."
Defect NumberDefect 81327
Enhancement Number
Cause
The driver had trouble parsing the reply from a LOB READ operation. The reply to the LOB READ request included the requested data but that the data was NOT contained within a normal protocol packet. 
Resolution
Fixed in hot fix 08.01.2073
Refer to Connect and Connect64 for ODBC hot fix download and install instructions for instructions on how to download and install the hot fix.
Workaround
Notes
Last Modified Date11/9/2017 6:48 PM
Files 1. ODBCTester.zip
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.