Wednesday, November 23, 2011

IBM WCM 6 to 7 Migration - Commands - Unix


Hi Y'all

Please find attached the commands I used during migration form version 6.0.1.X  to 7.0.0.1


  • ./ConfigEngine.sh validate-database-connection -DTransferDomainList=jcr -DWasPassword=XXXXXX -DPortalAdminPwd=XXXXXX
  • ./ConfigEngine.sh connect-database-jcr-migration
  • ./ConfigEngine.sh create-wcm-persistence-tables
    • This is not part of the IBM listed steps...you will thank me later :-)
  • ./ConfigEngine.sh upgrade-jcr-datastore-601x-to-6100-jcr
  • ./ConfigEngine.sh configure-wcm-migration
  • ./ConfigEngine.sh configure-wcm-remote-admin
  • ./ConfigEngine.sh action-create-schema-applyMIG7000-wp.migration.jcr.db -DPreviousPortalVersion=XXX -DCurrentPortalVersion=7.0.0.x -DWasPassword=Password -DPortalAdminPwd=Password
    • Please add your Portal versions where the xx's are.
  • ./ConfigEngine.sh wcm-post-migration-data-update -DPortalAdminPwd=Password-DWasPassword=Password-DPreviousPortalVersion=6.1.0.x -DtransferDomainList=jcr
    • This step fails - Build Failed
The attached error can be found in your migration log.

Error: 
MigrationSQLExecutor: ERROR ->DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704, 
SQLERRMC: JCR.ICMSTJCRNODELOCKSX

Migration Log :

/WebSphere/WP_PROFILE/ConfigEngine/log/Migration.log

The Fix:

You can resolve the issue by binding the JCRDB, executing the following commands from a DB2 command line window:
==db2 terminate 
==db2 connect to jcrDB (this is the newly copied database from 6.0.x to 7.0)
==db2 bind PATH\db2schema.bnd blocking all grant public sqlerror continue db2 terminate 

Substitute "PATH" with the install path for your DB2, and make sure you find the db2schema.bnd in the path before running the command.

Also, verify that all the Datasource passwords are correct before running the next task. You can verify this in the security.xml at cell scope:
\config\cells\\security.xml:

Find this entry for the JCR datasource and make sure the encrypted password is the same as the other datasources; if not, set it to the clear text password, and it will be encrypted at the next restart:

authDataEntries xmi:id="JAASAuthData_1296387511109"
alias="jcrdbDSJAASAuth" userId="db2admin" password="setPasswordHere”
description="JAAS Alias for DataSource jcrdbDS"



Happy Trails and Yours in WebSphere


Jerome Slinger








IBM WCM 7 : Migrating from WCM 6.0 to 7 - Release Not Found


Error received during migration: Release not found

Error Example String:
/WebSphere/PortalServer/base/wp.db.impl/config/templates/updatedb/6.0.1.6-7.0.0.1/db2/release
 not found.

Solution:
The issue is caused by missing files for migration from 6.1.0.6 to  7.0.0.1. This happened, because fixpack 6.1.0.6 is newer and so not  known by current 7.0.0.1. An APAR is requested.

As there are no database changes in the affected area between 6.1.0.5  and 6.1.0.6, you could duplicate the files in
/base/wp.db.impl/config/templates/updatedb/6.1.0.5-7.0.0.1
to the new directory
/base/wp.db.impl/config/templates/updatedb/6.1.0.6-7.0.0.1
as a workaround.

This is obviously not ideal but will resolve your problem.

...so how does one end up with this problem.IBM recommends that clients/customers need to be at the most recent fix pack level and as 6.0.1.7 is the most latest users are running into problems.

I hope that this has helped.

Yours in WebSphere
Jerome Slinger