13 HSA Patch Installation

An RPAS HSA system comprises of one or more integrated domains and the RPAS Data Mart (RDM). The integrated domains are upgraded and patched the same way as an independent domain. The RDM is upgraded and patched separately. All the domains do not need to be on the same version of RPAS, as long as these RPAS versions support the same schema version. RDM should be upgraded to the highest version among these RPAS versions and any RDM utilities must run on that version.

Note: For information on installing HSA, see Installing and Building the RPAS HSA Environment. For more information about upgrading or patching RDM, refer to the Classic Client or Fusion Client version of the Oracle Retail Predictive Application Server Administration Guide.

Upgrading RDM

The RDM maintains a numeric schema version number which is independent of the RPAS version. This schema version number is incremented whenever there is a schema change making the schema incompatible with existing RPAS releases.

The upgradeRdm utility is used to upgrade the RDM schema and the RDM repository. This utility is responsible for updating the RDM with any RPAS revisions to the schema tables, PL/SQL procedures or the RDM repository directory structure. This utility must be run on the RDM each time a new version of RPAS is deployed. However, it will only increment the schema version when the changes are incompatible with existing versions of RPAS. This allows the integrated domains to run on different versions of RPAS as long as they support the same schema version.

Patching RDM

Similar to patching a domain when its configuration has been modified, in an HSA environment, the RDM can also be patched. The patchRdm utility applies a changed integration configuration to the RDM. The shared hierarchies, facts, and integration map components of an integration configuration can be patched.

The patchRdm utility takes the modified integration configuration as input and compares it against the existing integration configuration (a copy of the current integration configuration is always maintained in the RDM Repository directory area). If any differences are found, it updates the RDM schema. Once the patchRdm completes successfully, the integration configuration stored in the RDM Repository is replaced with the new one. Note that most of the components of the integration configuration are patchable. However, removing a hierarchy and removing a dimension are not supported.