Troubleshoot WCM migration

Troubleshoot WCM 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...

Review any error messages displayed during the migration.
Review the migration log files in...
was_profile_root/PortalServer/wcm/config/migration/log

Verify you have copied the correct files and directories as described in the primary and secondary migration tasks.
Review the settings in...
was_profile_root/PortalServer/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, you can run each of the commands separately. They should be run in the order shown below.

validate Validate...

migration.properties file
network connectivity
user permissions

estimate-data Estimate time taken and space required for data migration.
export-data Export items from the old system.
transform-data Transform exported items so that they are ready to be imported into the new system.
import-data Import the transformed items. This requires a user-name and password.

For example, to run the validate command...
cd was_profile_root/PortalServer/wcm/config/migration/
./wcmmigrate.sh -user username -password password validate

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

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...
cd was_profile_root/PortalServer/wcm/config/migration/
./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...
cd was_profile_root/PortalServer/wcm/config/migration/
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
The 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 under...
was_profile_root/PortalServer/wcm/config/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

Log tracing levels

By default, the migration log trace level is set to "fine". This is set in...
was_profile_root/PortalServer/wcm/migration/config/migration.properties

If you change this setting to "finer" or "finest", data migration may slow or fail. If migration is still slow with a trace level of "fine", you should change the trace-level to "info".

Tuning data migration for large data sets

There are a set of parameters in the "Advanced Properties" section of the migration.properties file that can be used to tune migration performance. These should only be changed when migrating large amounts of data. See migration.properties for details.

Parent topic
Migrating version 5.1 Web content

validate	Validate... migration.properties file network connectivity user permissions
estimate-data	Estimate time taken and space required for data migration.
export-data	Export items from the old system.
transform-data	Transform exported items so that they are ready to be imported into the new system.
import-data	Import the transformed items. This requires a user-name and password.

Error Message	Action
The 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.