You can take corrective actions in response to error messages that occur while you use the Migration Manager application.
The following list of messages is not comprehensive but it contains the messages that you are most likely to encounter.
| Error code | Error message | Details in the Messages table | Explanation and response |
|---|---|---|---|
| BMXAA5198E | Could not create package package_name | Exception stack trace is written to the Message Details field | A package cannot be created. Check the associated stack trace to determine the cause of the error. |
| BMXAA5199E | Package distribution to target target_name failed | Exception stack trace is written to the Message Details field | A package cannot be distributed. The stack trace provides more details. Depending on the cause of the error, you can try to distribute the package again. |
| BMXAA5201E | Error checking distribution status in target environment for package package_name | Exception stack trace is written to the Message Details field | The database operations that determine the prior distribution status of the selected package failed . Check the associated stack trace to determine the cause of the error. |
| BMXAA5205E | Could not delete staging table records in target environment for incompletely dis-tributed package package_name | A package is not completely distributed to a target environment database and the Migration Manager application attempts to clean up committed records from the target database staging table. Depending on the cause of the error, you might have to remove records manually. | |
| BMXAA5206E | Could not read staging table records in source environment for package package_name | The Migration Manager application cannot extract the staging table records in the source environment of a package that is being distributed. Check the associated stack trace to determine the cause of the error. | |
| BMXAA5207E | Could not write staging table records in target environment for package package_name | The Migration Manager application cannot insert records into the staging table on the target environment database. Check the associated stack trace to determine the cause of the error. | |
| BMXAA5209E | Migration Manager root directory has not been configured using System Property system_property. The directory will default to default_directory. | No root folder has been configured for the mxe.dm.dmroot system property. If no root folder is configured, the Migration Manager application file operations are performed on the home folder of the application server. Use the System Properties application to specify the appropriate value for the mxe.dm.dmroot property. | |
| BMXAA5212E | Error creating XML document in manifest for package package_name | The XML document that represents the manifest of a package cannot be generated. Check the associated stack trace to determine the cause of the error and try the action again. | |
| BMXAA5214E | Could not create version header in manifest for package package_name | The application cannot retrieve and construct the version information of the package manifest that is being created or distributed. Check the associated stack trace to determine the cause of the error. | |
| BMXAA5220E | Could not get database name in source environment | The name of the source database cannot be retrieved from the database to generate the source information for a package definition. Check the associated stack trace to determine the cause of the error. You might have to work with a database administrator to correct the error. | |
| BMXAA5221E | Could not get database schema name in source environment | The schema name of the source database cannot be retrieved from the database to generate the source information for a package definition. Check the associated stack trace to determine the cause of the error. You might have to work with a database administrator to correct the error. | |
| BMXAA5227E | Could not register event listeners for package definitionpackage_definition_nameand source source_string | The application cannot register the event listeners for the active change packages. The error is recorded in the log file if the logger is configured. The associated stack trace indicates the cause of the error. | |
| BMXAA5228E | Could not register event listeners for all active Migration Manager change packages | The application cannot register the event listeners for the active change packages. The error might occur when the application server starts. The error is recorded in the log file if the logger is configured. The associated stack trace indicates the cause of the error. | |
| BMXAA5234E | Error in tracking events for package definition package_definition_name and source source_string | The application cannot capture event information and write it to the event tracking table. The error is recorded in the log file if the logger is configured. The associated stack trace indicates the cause of the error. | |
| BMXAA5244E | Cannot read manifest information from file file_name | Exception stack trace is written to the Message Details field | The manifest of a package cannot be read during deployment. The package file contents might be corrupted. You can test the file by copying it and extracting the manifest from the copy. If you cannot extract the manifest, re-create or redistribute the package. If the package file is not corrupted or if the manifest can be extracted, review the associated stack trace to identify the cause of the error. |
| BMXAA5252E | Error in checking entry in dmrestriction table | The application cannot check the restriction entries in the target database environment when distributing a package. The error is recorded in the log file if the logger is configured. The associated stack trace indicates the cause of the error. | |
| BMXAA5257E | Package redistribution to target target_name failed | Exception stack trace is written to the Message Details field | The stack trace provides details of the error. Depending on the cause of the error, you can try the redistribution again. |
| BMXAA5290E | Could not locate or create the folder folder_name | The application cannot locate the processed folder under DMROOT or cannot create the folder. Check if you have write permissions in the parent folder and if there is enough disk space. | |
| BMXAA5291E | Could not close package package_name to file file_name | The package file cannot be copied to the processed folder. Check if you have write permissions and if there is enough disk space | |
| BMXAA5309E | Could not export package configuration records to the staging table for package package_name | Exception stack trace is written to the Message Details field | The package metadata records cannot be exported from the source database. Check the associated stack trace to determine the cause of the error. |
| BMXAA5310E | Could not export configuration records to the staging table for package package_name | Exception stack trace is written to the Message Details field | Configuration data records cannot be exported from the source database. Check the associated stack trace to determine the cause of the error. |
| BMXAA5311E | Could not export data dictionary configuration records to the staging table for package package_name | Exception stack trace is written to the Message Details field | The data dictionary records cannot be exported from the source database. Check the associated stack trace to determine the cause of the error. |
| BMXAA5313E | Could not connect to the target database specified by URL database_URL | Exception stack trace is written to the Message Details field | The target database is not running at the time of distribution. Check with the target environment database administrator for database availability and the required connection parameters and update the target definition. |
| BMXAA5314E | Could not create staging table records in the target database specified by URL database_URL | Exception stack trace is written to the Message Details field | Database operations to insert package records fail. Check the associated stack trace to determine the cause of the error. The cause of the error might be a database issue related to table spaces or permissions. |
| BMXAA5315E | Could not create consolidated package file package_file_name into the folder target_folder_path | Exception stack trace is written to the Message Details field | The application cannot write the file to the outbound folder under the DMROOT folder on the application server or cannot copy the file from the DMROOT folder to the user-specified target folder. Check the write permissions on the folder and check for enough disk space. |
| BMXAA5316E | Could not stage selected package file package_name | Exception stack trace is written to the Message Details field | The contents of the package file cannot be extracted and written to the staging table. Check the associated stack trace to determine the cause of the error. Alternatively, obtain a new package from the source and deploy the new package. |
| BMXAA5317E | Could not import package metadata records for package package_name | Exception stack trace is written to the Message Details field | Package metadata records cannot be imported into the target database. Check the associated stack trace to determine the cause of the error. Alternatively, obtain a new package from the source and deploy the new package. |
| BMXAA5318E | Could not import data dictionary records for package package_name | Exception stack trace is written to the Message Details field | Data dictionary records cannot be imported into the target database. Check the associated stack trace to determine the cause of the error. Alternatively, obtain a new package from the source and deploy the new package. |
| BMXAA5319E | Could not import configuration records for package package_name | Exception stack trace is written to the Message Details field | Package configuration records cannot be imported into the target database. Check the associated stack trace to determine the cause of the error. |
| BMXAA5320E | Could not apply data dictionary changes into database using Database Configuration for package package_name. Please check configdb log file for more detail. | Exception stack trace is written to the Message Details field | The target database cannot be configured after the data dictionary records are imported from the package. Do not try to redeploy the package. Instead, check with the administrator of the source environment to determine whether the same data dictionary changes were successfully applied in the source. If necessary, obtain a new package. |
| BMXAA5324E | Could not extract or write XML document to staging table record for migration object migration_object_name for package package_name | The application cannot create the XML document that represents the migration object record or cannot write the XML document to the staging table in the source environment. Check the associated stack trace to determine the cause of the error. | |
| BMXAA5367E | Could not redistribute package metadata records for package package_name | Exception stack trace is written to the Message Details field | Metadata records that are regenerated for redistribution cannot be written to the staging table. Check the associated stack trace to determine the cause of the error. |
| BMXAA5648E | Could not distribute package package_name to target target_name. Source database is different than target database. | An attempt is made to distribute a package to a target database that is a different database management system than the source database. The Migration Manager application works only between databases of the same type. Distribute the package as a file instead. | |
| BMXAA5651E | Target environment base language language_name is different from source base language language_name. You must change target base language to match that for source base language before you can deploy the package. | The application requires that packages are deployed in the base language. The target environment base language also must match the source environment. When a new package is available for deployment, check its manifest and determine the base language of the package. If the base language of the target environment, change it to match the source environment. | |
| BMXAA6001E | Could not generate manifest for package package_name during redistribution | Exception stack trace is written to the Message Details field | The manifest of the package cannot be generated when a package is redistributed. Check the associated stack trace to determine the cause of the error. |