Automatically roll back changes from a RealTime database (RTDB) changeset installation failure

An automatic rollback reverses all the changes that have been applied to the RealTime database (RTDB) during the installation of a package (i.e., the RTDB will be brought back to the state it was in prior to the start of the package install process).

Rollback of a RTDB changeset is automatically triggered when a failure occurs during the installation of RTDB changesets from a package.

If a package installation times out and subsequently fails, the changeset that was being installed will be rolled back. However, any previously installed changesets in the same package will not be rolled back.

Install operations from a changeset will fail and trigger a rollback in any of the following partial list of scenarios:

• a record being inserted already exists in the RTDB (duplicate key)

• a record being deleted is missing from the RTDB (nonexistent key)

• a field being updated does not have the expected value prior to the update

These errors can occur if a user attempts to install the same package more than once or if manual modifications have been made to the same RTDB tables that a changeset is modifying.

If an automatic rollback has occurred, the end package status will depend on the success or failure of the rollback as follows:

• The package status will be Install Failed - Rollback Successful in the Management of Change (MoC) zone if the rollback was successful.

• The package status will be Install Failed - Rollback Failed if the package failed to roll back.

For more information on package status, refer to Understanding the status of an MoC package.