First, LONG VARCHAR and LONG VARGRAPHIC have been deprecated (
LONG VARCHAR and LONG VARGRAPHIC data types have been deprecated) for a long time already (since December 2006). As a consequence, any new features and performance improvements in DB2 are not likely to work at all or as good for those data types.
But back to your performance issue: LONG VARCHAR and LONG VARGRAPHIC are stored separately and won't benefit from the buffer pool. So all access to such values incurs disk I/O, which is simply... slow.
You can use VARCHAR instead of LONG VARCHAR. The difference of the maximum length is 32672 vs. 32700 bytes. Similar for VARGRAPHIC and LONG VARGRAPHIC, where you can store a mere 14 double-byte characters more in a LONG VARGRAPHIC. (
SQL and XML limits) If you have longer strings than that, CLOB and DBCLOB are the way to go. But those values of those types won't benefit from the caching in the DB2 buffer pool either (except for inlined portions) - which means it will be slower to fetch them!