Updating (patching) BCC 1.2.1 for OES 2 SP2 Linux assumes that you have installed BCC 1.2 on OES 2 SP1 Linux in an existing business continuity cluster.
Before you begin the update from OES 2 SP1 Linux to OES 2 SP2 Linux, you must apply the latest patches for BCC 1.2 and OES 2 SP1 Linux. For information about applying BCC 1.2.0 patches, see Section 6.0, Updating (Patching) BCC 1.2.0 on OES 2 SP1 Linux.
You must also prepare the cluster nodes for the OES 2 patch process as described in OES 2 SP3: Installation Guide. If BCC 1.2 is installed when you update a server from OES 2 SP1 Linux to OES 2 SP2 Linux, the BCC 1.2.1 patch files are pulled down from the OES 2 SP2 Linux patch channel in the maintenance patch for OES 2 SP2 Linux.
The following BCC 1.2.1 patch is available for OES 2 SP2 Linux:
OES2 SP2 January 2010 Scheduled Maintenance 20100130: The BCC 1.2.1 patch includes the following RPM files:
The features and changes included in the BCC1.2.1 patch are described in Section 2.2, BCC 1.2.1 Patch for OES 2 SP2 Linux (January 2010).
The patch includes a new BCC resource driver template for Identity Manager. The BCC resource driver template delivered in the BCC 1.2.1 patch for OES 2 SP2 Linux is functionally the same as the template delivered in the BCC 1.2.0 patch for OES 2 SP1 Linux, but it has a different version number. If you are already running Identity Manager 3.6.1 on OES 2 SP1 Linux and have deleted and re-created the Identity Manager drivers to use the new template for BCC 1.2.0, it is not necessary to delete and re-create the drivers again for BCC 1.2.1.