Potential database issues

Depending on which database you use; there some potential issues that you should be aware of.

IBM Db2

When attempting to cache a node in a stream which reads data from a Db2 database, you may see the following error message:

A default table space could not be found with a pagesize of at least 4096 that authorization
 ID TEST is authorized to use

To configure Db2 to enable in-database caching to work properly in SPSS® Modeler, the database administrator should create a "user temporary" tablespace and grant access to this tablespace to the relevant Db2 accounts.

We recommend using a pagesize of 32768 in the new tablespace, as this will increase the limit on the number of fields that can be successfully cached.

IBM Db2 for z/OS

Scoring a subset of algorithms, with confidences enabled, using generated SQL can return an error on execution. The issue is specific to Db2 for z/OS; to fix this, use the SPSS Modeler Server Scoring Adapter for Db2 on z/OS.
When running streams against Db2 for z/OS, you may experience database errors if the timeout for idle database connections is enabled and set too low. In Db2 for z/OS version 8, the default changed from no timeout to 2 minutes. The solution is to increase the value of the Db2 system parameter IDLE THREAD TIMEOUT (IDTHTOIN), or reset the value to 0.

Oracle

When you run a stream that contains an Aggregate node, the values returned for the 1st and 3rd Quartiles, when pushing back SQL to an Oracle database, may differ from those that are returned in native mode.