Package deployment errors
Deployment errors occur primarily when the configuration data in the package cannot be validated. If you cannot correct the errors that are displayed in the Deployment Data Errors tab, you can take further action.
Error determination
During a deployment, the Migration Manager application creates progress messages that show the steps that succeeded. This information can help you to determine the cause of the error. The messages are stored in the product log file, if it is configured, and persist in the messages table.
To discover where an error is occurring, you can create package definitions with smaller sets of data. This step helps to determine which set of data deployed correctly and which set of data created an error.
Types of errors
An incomplete configuration might occur if the related configuration data is not in the package and if the data is not in the target environment. An incorrect configuration might occur if the configuration is created by using SQL scripts without validations.
If an error is caused by bad configuration data in a package, restore the target database from the database backup. Then, correct the configuration data in the source environment and re-create the package. For example, an incorrectly defined database index must be recreated in the source environment.
If an error occurs because the data in the target database must change, you can modify the data in the target database and redeploy the package. You do not have to re-create the package in the source environment. For example, if a workflow process revision is active and enabled in the target environment, the package that contains updates to this revision fails to deploy. You can deactivate and disable the workflow process in the target environment and deploy the package again.
If the application server stops running while a package is being deployed, the package remains in the DEPLOY_INPROGRESS status. You might be able to restart the deployment by clicking Continue Deployment. Depending on the stage of deployment, the structural integrity of the database might be compromised and a database restore operation might be necessary.
Integration framework errors
By default, a validation mechanism listens for data dictionary changes, identifies the changes to the integration framework integration components, and requests that the configurations be updated.
To ensure the deployment of packages that contain database updates that affect integration framework configurations, you can set the system property mxe.int.validatemmpackage to 1.
If this property is enabled, during a deployment the validation process identifies whether any business object changes affect the configuration of the components and which migration groups must be updated.