Solution : https://service.sap.com/sap/support/notes/784568 (SAP Service marketplace login required)
Summary :
During the execution of a JDBC-based application on DB2, a `DisconnectException` error may occur due to attempts to fully materialize large LOB (Large Object) data, exceeding the Java VM’s capacity. The default configuration of the DB2 JDBC driver, type 4, materializes LOB data during the fetch process. This can be modified by setting "fullyMaterializeLobData=false" to manage LOBs with locators, saving memory. Applications might face reentrant calls issues, but versions post-DB2 V8 SP10 have a setting to circumvent this. However, complete materialization is recommended to avoid larger memory consumption during batch operations with LOBs.
Key words :
version db2 version 8 support package 10, 0100e04ce76bdrda application server sqljsdrdaascbputlobdata probe, disable data source property, fully materialize lob data, driver materializes lob objects, locator-basedlob implementation, -based lob accesses, jbdc-based application, sap open sql, memory required depends
Related Notes :
| 1283141 | Add. info.: Upgrade to SAP NetWeaver 7.0 EHP1 SR1 Java |
| 1267573 | Central Note: Upgrade to Systems on SAP NW 7.0 EHP2 Java |
| 1160166 | DB6: Add. Information - SAP Enhancement Package Installer |
| 1156186 | Add. info.: Upgrade to SAP NetWeaver 7.0 including EHP1 Java |
| 1102065 | Add. info. on upgrading to SAP NetWeaver 7.0 SR3 Java |
| 866725 | SAPJup: Engine startup failed due to DB6 JDBC driver issue |
| 836198 | Add. info. on upgrading to SAP NW 7.0 Java |
| 819876 | DB6: Additional info about upgrade (based) on SAP NW AS 7.0 |
| 784903 | Export and other DTR operations fail on DB2 with Status 500 |
| 781644 | DB6: SAP Web AS 6.40 SR1 - Installation on Windows |
| 781643 | DB6: SAP Web AS 6.40 SR1 - Installation on UNIX |