Links may not function; however, this content may be relevant to outdated versions of the product.
Troubleshooting: ‘Save failed: problem encountered when reading ruleset versions: code: -4470’ after DB2 Connect upgrade on DB2 for z/OS
You have deployed IBM DB2 for z/OS Version 9.1 on WebSphere Application Server Version 6.1 for z/Linux. You are using application server JDBC connection pools. After you upgrade to DB2 Connect 9.5, you cannot save certain types of records, for example, access groups and application rules. Here's an example of the error message:
** Save failed: problem encountered when reading ruleset versions from the database: code: -4470 SQLState: <none> Message: [jcc][3.53.95] Invalid operation: Lob is closed. ERRORCODE=-4470, SQLSTATE=null
Certain custom properties for the JDBC Providers of the PegaRULES data sources need to be specified in the application server administrative console.
- In the WebSphere Application Server administrative console, go to JDBC Providers > Pega - UDB JDBC Driver > Data sources > PegaRULES > Custom properties > New.
- Specify the following custom properties for the DB2 UDB Connection Pool:
- Restart the application server.
What custom properties are required for the DB2 UDB Connection Pool in the z/OS mainframe environment?