Detached Migration

When a migration needs to occur between two databases that do not share the same IVS, then a detached migration must be performed. A detached migration begins in much the same way as a typical migration. The configuration packages are created and marked ready to migrate. They are then added to migration sets.

 

When a release package is created, the first screen has a check box option to create files for detached migration. Clicking this box will allow the release package to migrate outside of the IVS environment of the source environment. After the release package is created, it is built and promoted exactly as it is in a typical migration.

The Rules Palette has a tool that manages the deployment of a detached migration. This tool can only be used in the target environment, after a release package has been built and marked ready to promote. A Detached Migration wizard walks you through the steps to complete the deployment of the release package. When the deployment is initiated, OIPA performs conflict validations on each rule prior to writing the rule to the database. If a conflict occurs, you will be presented with a warning message, along with action buttons to support user overrides or a cancel button to abort the detached migration.

 

Once the deployment is successfully completed, a confirmation message is presented.

Trouble Shooting the Detached Migration

The IVSRELEASEPACKAGE table has a column called DETACHEDFLAG. A value of Y indicates that the package was marked for detached migration.

 

The location of the detached migration files can be found by referencing the <BuildLocation> tags in the RELEASEPACKAGEMANIFEST column of the IVSRELEASEPACKAGE table.

 

The ReleaseManifest.xml file contains a list of all items included in the detached migration. Items are grouped by type and are separated by start and end tags that reflect the item type.

 

 

 

 

 

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us