We have a JDBC application INSERT or UPDATING a LOB/XML column. Currently this can cause transaction slowness as the INSERT or UPDATE has to wait for the uncompressed LOB to travel across network.
|Who would benefit from this IDEA?||All JDBC Db2 apps having INSERT or UPDATE of LOB/XML columns|
How should it work?
1) It would be better if the JDBC driver had a configuration parameter that allowed compression of the LOB/XML subject of INSERT or UPDATE prior to transmission across the network and for Db2 for z/OS (or Db2 for LUW) to understand and decompress the LOB/XML at the other end.
Refer to case TS003549649 for example.
I note that other JDBC drivers have this functionality.
2) This would lead to reduced transaction elapsed times. In particular, "TCP/IP LOB XML MATERILIZATION WAIT" will be reduced.
3) One workaround would be for the application could compress LOB/XML column prior to INSERT or UPDATE. This may not be possible for some applications or packages.
|Priority Justification||There are a lot of JDBC Db2 apps having INSERT or UPDATE of LOB/XML columns.|
|Customer Name||Frank McEwen, Westpac Banking Group|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions