#1 Production Mode and RPS/SDS Environments

[Jade Support]

In an RPS or SDS environment the production mode setting is inherited whenever the secondary database is established from the primary. Changes to the setting on the primary are not propagated through audit and replay.

If structural changes are made to classes on the primary database through a schema deployment, for example; when the changes are applied to the secondary database and production mode is enabled, in-memory meta data does not get updated. The mismatch between in-memory class descriptions and instances that have been reorged will result in applications encountering exceptions such as a 3039 database error (Schema to Database object size mismatch) when they access an instance of a changed class. In an RPS system the RPS data pump is likely to encounter an exception causing replication to halt.

In order to avoid this issue sites running RPS or native SDS secondaries with production mode enabled on the primary database will need to perform an extra step to turn off production mode on the secondary after cloning from the primary. This can be achieved by executing JDBUTILB with the following command line:

Code: Select all

JDBUTILB path=<path to secondary database> productionMode=false

Note: The issue could affect user applications in native secondaries as well as JADECare managed deployments.
A product resolution will be available in the next JADE 6.2 consolidated release, 6.2.15.