Symptom

To use IBM DB2 version 9.5 or 9.7, you must add two settings to the connection URL for your database. If these settings are not used, Process Commander systems fail to start.

DB2 can be used with either of two drivers: 

• Type 2 – thick client
• Type 4 – pure Java

NOTE: Pegasystems does not test the Type 2 driver for any version of DB2; instead, the Type 4 driver is tested.  Pegasystems does not support or document using Type 2 drivers.

In Version 9.5 of DB2, IBM introduced a new feature:  Progressive Streaming.  Based on the database server perspective, Progressive Streaming tries to determine the best way to present the LOB data to the application server:  by storing it in the database server memory, or by directly streaming it. 

The default behavior is incompatible with Process Commander’s use of LOB (Large Objects) data, and prevents the PRPC system from starting. 

Solution

To prevent DB2 from using Progressive Streaming and to use the LOB Locator functionality instead, add two settings to the connnection URL for your database:

progressiveStreaming=2
progressiveLocators=2

The connection URL is specified in the data source definition in your application server, or in the database element of the prconfig.xml file. These settings take integer values.  If they are not specified, the internal value of the settings is set to zero.  A value of “1” enables the  Progressive Streaming functionality, and “2”disables it. 

For example, the full entry in the prconfig.xml file for the connection URL for a DB2 9.5 or 9.7 database  is as follows (without the link break):

<env name="database/databases/PegaRULES/url" value="jdbc:db2://10.60.151.210:50000/SLABDB95:
driverType=4;progressiveStreaming=2;progressiveLocators=2;" />