Troubleshoot Web Content Management migration

Troubleshoot Web Content Management migration

+

Search Tips | Advanced Search

This topic details some ways to troubleshoot an unsuccessful migration. All errors, information and warnings are logged to the console as migration is performed. The message "command successful" is displayed after a successful migration. If the message "command failed" is displayed upon completion do the following:

Review any error messages displayed during the migration.

Review the migration log files located under...
portal_server_root/wcm/migration/log

Make sure you have copied the correct files and directories as described in the primary and secondary migration tasks.

Review the settings in...
portal_server_root/wcm/migration/config/migration.properties

Run individual wcmmigrate all-data commands
When you run the wcmmigrate all-data task, a set of commands are executed. To troubleshoot the wcmmigrate all-data task, we can run each of the commands separately. They should be run in the order shown below.

validate Validates the migration.properties file, network connectivity and user permissions. This requires a user-name and password.
estimate-data Provides an estimate of the time taken and space required for data migration.
export-data Exports items from the old system.
transform-data Transforms exported items so that they are ready to be imported into the new system.
import-data Imports the transformed items. This requires a user-name and password.

For example, to run the validate command, run the following command from...
portal_server_root/wcm/migration

Windows:
wcmmigrate.bat -user username -password password validate

UNIX:

./wcmmigrate.sh -user username -password password validate

i5/OS:
wcmmigrate.sh -user username -password password validate

The user specified in the command must be a WebSphere Portal administrator.

Resuming or restarting wcmmigrate commands

Once you have identified and fixed the issue that was causing a migration to fail, you have a choice of either restarting a wcmmigrate command, or resuming a wcmmigrate command from the point where a migration error occurred. For example, to restart the wcmmigrate all-data command, enter the following from...
portal_server_root/wcm/migration

Windows:
wcmmigrate.bat -user username -password password all-data -restart

UNIX:
./wcmmigrate.sh -user username -password password all-data -restart

i5/OS:
wcmmigrate.sh -user username -password password all-data -restart

The user specified in the command must be a WebSphere Portal administrator. To resume the wcmmigrate all-data command from the point where migration failed, enter the following from...
portal_server_root/wcm/migration

Windows:
wcmmigrate.bat -user username -password password all-data -resume

UNIX:
./wcmmigrate.sh -user username -password password all-data -resume

i5/OS:
wcmmigrate.sh -user username -password password all-data -resume

The user specified in the command must be a WebSphere Portal administrator.

Error messages

The following table contains a list of error messages you may see in the migration console:

Error Message Action
User specified on the command line must be the portal administrator user. Specify a valid WebSphere Portal administrator in the command line.
Could not connect to import servlet; check the import servlet url in the migration properties Check the import servlet URL in migration.properties. Ensure the import servlet is deployed and the WebSphere Portal server is started.
Unexpected http response code returned from the import servlet: {0} Check the import servlet URL in migration.properties. Ensure the import servlet is deployed and the WebSphere Portal server is started.
Resource {0} not found. Please ensure that the reference checker was run before export. The referenced resource was not found. Before migrating Web content data, run the following tools on the old system and resolve any problems:

Reference checker
Site checker
Resource checker
Member fixer

Refer to the WebSphere Portal 5.1 information center for details.
Could not create parameter: {0}; failed to find value for: {1} A portlet parameter could not be created as the new value was not available. Ensure migration.properties refers to the correct summary data from data migration.
Failed to update parameter: {0}; retaining old value: {1} A portlet parameter could not be updated as the new value was not available. Ensure migration.properties refers to the correct summary data from data migration.

Warning messages

If you see any of the following warning messages, review the migration log files located under...
portal_server_root/wcm/migration/log

A fatal error was encountered during the import step of data migration

Problem encountered encoding id of file: {0}

Problem encountered decoding id of file: {0}

Failed to read version properties file; empty labels will be used

Could not retrieve version date; using current date as the version date

Transform data problem encountered; skipping item and continuing

Transform system problem encountered; skipping item and continuing

Import system problem encountered; skipping item and continuing

Parent topic:
Migrating Web Content Management

validate	Validates the migration.properties file, network connectivity and user permissions. This requires a user-name and password.
estimate-data	Provides an estimate of the time taken and space required for data migration.
export-data	Exports items from the old system.
transform-data	Transforms exported items so that they are ready to be imported into the new system.
import-data	Imports the transformed items. This requires a user-name and password.

Error Message	Action
User specified on the command line must be the portal administrator user.	Specify a valid WebSphere Portal administrator in the command line.
Could not connect to import servlet; check the import servlet url in the migration properties	Check the import servlet URL in migration.properties. Ensure the import servlet is deployed and the WebSphere Portal server is started.
Unexpected http response code returned from the import servlet: {0}	Check the import servlet URL in migration.properties. Ensure the import servlet is deployed and the WebSphere Portal server is started.
Resource {0} not found. Please ensure that the reference checker was run before export.	The referenced resource was not found. Before migrating Web content data, run the following tools on the old system and resolve any problems: Reference checker Site checker Resource checker Member fixer Refer to the WebSphere Portal 5.1 information center for details.
Could not create parameter: {0}; failed to find value for: {1}	A portlet parameter could not be created as the new value was not available. Ensure migration.properties refers to the correct summary data from data migration.
Failed to update parameter: {0}; retaining old value: {1}	A portlet parameter could not be updated as the new value was not available. Ensure migration.properties refers to the correct summary data from data migration.