Wayne Carmichael
Member
When we installed SP23_U1 in May, we discovered that Oracle has changed the "default" DB2 connection model to "SQL Server". This caused problems with batch processing where a job stream uses both UBE and non-UBE (SQL) database access ... the UBE would fail because two different DB2 connection methods and conflicts arose on the SQL CONNECT processing order. For job streams where there were just UBEs, there were performance problems because the database workload was going to a different subsystem than was expected.
Note: We use IBMs advanced job scheduler for our batch processing.
The workaround recommended by Oracle was to add sqlServerMode=0 to the [DB SYSTEM SETTINGS] section in the iSeries JDE.INI. This restores the connection method back to what we were experiencing in SP23_J1.
Apparently, Oracle introduced the new database connection model to support new features in Vertex 3.x and higher. We're only on 2.9, so we would not have looked at the 3.x release notes.
Note: We use IBMs advanced job scheduler for our batch processing.
The workaround recommended by Oracle was to add sqlServerMode=0 to the [DB SYSTEM SETTINGS] section in the iSeries JDE.INI. This restores the connection method back to what we were experiencing in SP23_J1.
Apparently, Oracle introduced the new database connection model to support new features in Vertex 3.x and higher. We're only on 2.9, so we would not have looked at the 3.x release notes.
