IBM Support

Rolling back the last Global Configuration Database (GCD) modification for FileNet Content Platform Engine

Question & Answer


Question

How do you undo the last Global Configuration Database (GCD) modification?

Cause

Some changes to the FileNet Content Platform Engine domain can prevent the users from logging back into ACCE to undo the changes. This procedure returns the GCD to a state before the one where the mistake occurred.

Answer

Note: Take a backup of the GCD before performing any operations on the Database.

Every update to the GCD is stored as a new row in the FNGCD table in the GCD database. The FNGCD table holds the history of the last 100 changes made to the GCD. Using the procedure documented in this technote makes it easy for an administrator to roll back the unwanted updates.

The FNGCD table consists of four columns: epoch_id, gcd_blob, last_modified_date, and last_epoch_id.

The last_epoch_id of the 0th epoch_id row identifies the last gcd_blob that was loaded. In Figure 1, the 0th epoch_id has a last_epoch_id of 15. When the Content Platform Engine server starts, the gcd_blob where epoch_id = 15 is loaded as the current GCD.

Figure 1: FNGCD table with a value of 15 for the last_epoch_id in the row with 0 (zero) as the epoch_id

To undo the last modification in the FNGCD table shown in Figure 1
  1. Change the value of the last_epoch_id in the 0th row to 14.
  2. Change the value of epoch_id 15 to a negative number. For instance, change the value to -15.
Figure 2 shows the FNGCD table after these two updates have been made.

Best Practice
Multiply the epoch_id of the change that is to be rolled back by -1.  All negative-valued epoch_ids are ignored, and this enables you to track changes that have been undone. Note that the next GCD update produces a row with an epoch_id matching the one previously rolled back. In the example shown in this technote, the new row is assigned an epoch_id of 15.


Figure 2: FNGCD table with a value of 14 for the last_epoch_id in the row with 0 (zero) as the epoch_id

Steps to undo the last GCD update
Use the following procedure to undo a GCD update:
  1. Stop the Content Platform Engine server.
  2. Back up the GCD.
  3. Update the FNGCD table as described to change the epoch_id of the last row in the table to a negative number. And, update the last_epoch_id of the 0th row to match the epoch_id of the row with the last good update.
  4. Restart the Content Platform Engine server.
  5. Verify the logon to ACCE is successful.
If needed, repeat the procedure working back to the last GCD update that enables you to log on to ACCE.

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVNV","label":"FileNet Content Manager"},"ARM Category":[{"code":"a8m0z0000004D40AAE","label":"Content Engine"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.5.0;and future releases"}]

Document Information

Modified date:
22 February 2023

UID

swg21318059