IBM InfoSphere Master Data Management, Version 11.3

Troubleshooting migration issues

Describes some common issues for troubleshooting that might come up during migration in IBM® InfoSphere® Master Data Management Collaboration Server.

Issue: Exporting access control groups

When you migrate to InfoSphere MDM Collaboration Server, you might see the following error that is related to exporting access control groups and roles:

AccessControlGroups

Exporting ACG and Roles for company: trigo 7/4/13 6:27 AM 
STARTED:Export 7/4/13 6:27 
AM STARTED:Export of AccessControlGroups 7/4/13 6:27 AM 
INFO:Skipping export of [Default] 7/4/13 6:27 AM 
FAILED:Export of AccessControlGroups

This error means that there was a failure in exporting the access control group (ACG). Check the logs under the $TOP/logs/default directory to find out the reason for the failure.

Issue: GDS migration questions are case-sensitive

All the GDS access control group migrations before InfoSphere MDM Collaboration Server version 9.1.0-FP011 are case-sensitive and y or n should be entered in lowercase. Before InfoSphere MDM Collaboration Server version 9.1.0-FP12 migrations, an uppercase Y or N should be used for GDS migration questions.

Issue: Missing indexes

When you migrate to InfoSphere MDM Collaboration Server, you might see missing indexes in the migration console report.

The following errors that are related to missing indexes might occur during migrating:

Missing indexes on the SCA table

Missing Indexes
|============================================================
|SCA_0_PK SCA_CATEGORY_IDSCA_SELECTION_IDSCA_COMPANY_IDSCA_
|CATALOG_IDSCA_CAT_TREE_ID

You can run this PERL script to resolve this issue. Choose directory db2 or oracle appropriately.

perl $PERL5LIB/runSQL.pl --sql_file=$TOP/src/db/schema
/dbscripts/<db2 or oracle>/sca_pk.sql

Missing indexes on the DBV table

Missing Indexes
|============================================================
|DBV_0_UK DBV_VERSION

You can run this PERL script to resolve this issue. Choose directory db2 or oracle appropriately.

perl $PERL5LIB/runSQL.pl --sql_file=$TOP/src/db/schema
/gen/<db2 or oracle>/ddl_ver_synchronize.sql
. $TOP/bin/compat.sh
$JAVA_RT com.ibm.ccd.synchronize.DBSchemaVersion --autoupd

Missing indexes on the DOA and CTG tables (DB2® only)

Missing Indexes
|==============================================
|  CTG_1_UK CTG_COMPANY_IDCTG_NAME
|  DOA_0_UK DOA_DOC_IDDOA_CMP_IDDOA_NAME

You can run this PERL script to resolve this issue:

perl $PERL5LIB/runSQL.pl 
--sql_command="alter table tctg_ctg_catalog drop constraint ctg_1_uk ;"
perl $PERL5LIB/runSQL.pl 
--sql_command="drop index ictg_ctg_2;"

perl $PERL5LIB/runSQL.pl 
--sql_command="alter table tctg_ctg_catalog
add constraint ctg_1_uk unique (ctg_company_id, ctg_name);"

perl $PERL5LIB/runSQL.pl 
--sql_command="create index ictg_ctg_2 on 
tctg_ctg_catalog ( ctg_name, ctg_company_id) 
ALLOW REVERSE SCANS;"

perl $PERL5LIB/runSQL.pl 
--sql_command="alter table TDOC_DOA_DOC_ATTRIBUTES 
drop constraint doa_0_uk ;"

perl $PERL5LIB/runSQL.pl 
--sql_command="drop index idoc_doa_0;"

perl $PERL5LIB/runSQL.pl 
--sql_command="alter table tdoc_doa_doc_attributes 
add constraint doa_0_uk unique (doa_doc_id, doa_cmp_id, doa_name);"

perl $PERL5LIB/runSQL.pl 
--sql_command="create index idoc_doa_0 
on tdoc_doa_doc_attributes ( doa_name, doa_doc_id, doa_cmp_id)
ALLOW REVERSE SCANS;"

Issue: Missing tables ITX and CAX

When you migrate to InfoSphere MDM Collaboration Server, you might see this error in the DB verification report:

___________________________________________________________
|Missing Tables
|===========================================================
| TCTG_CAX_CATEGORY_CONTENT 
| TCTG_ITX_ITEM_CONTENT

|Missing Indexes|
|  CAX_0_PK CAX_ENTRY_IDCAX_NEXT_VERSION_ID
|  ITX_0_PK ITX_ENTRY_IDITX_NEXT_VERSION_ID

This error indicates a problem with table space creation, XDB installation, or db parameters. Check in the errfile.log file in the $TOP/logs directory for the exact message. Ensure that database setup is done correctly and then run the migration script again.

Issue: Insufficient privileges error

When you run a migration script for migrating to InfoSphere MDM Collaboration Server, you might see an Insufficient privileges error in the console. Typical examples of the error are

Oracle database

When you use an Oracle database, the error might look like this error:

create index icnt_eem_2 on tcnt_eem_entry_entry_map (
                           *
ERROR at line 1:
ORA-01031: insufficient privileges

DB2 database

When you use a DB2 database, the error might look like this error:

SQL0551N  "USERNAME" does not have the privilege to perform operation
"CREATE INDEX" on object "USERNAME.TWFL_WFE_WORKFLOW_EVENT".  
SQLSTATE=42501

The database user does not have enough privileges to create an index in the database. You must grant "create index" privilege to the database user and then run the migration script again. You must also grant access to the user to be able to create and modify tables.

Issue: Migration script failure

When you run a migration script for migrating to InfoSphere MDM Collaboration Server, the script might fail. A typical scenario of script failure is

Failure in module data_maintenance_reports

-----------------------------------------------------------
Summary of the migration
-----------------------------------------------------------
Migration of the following modules failed:
data_maintenance_reports

The $TOP/logs/errfile.log file contains the following content:

net.sf.ehcache.distribution.
MulticastKeepaliveHeartbeatReceiver$MulticastReceiverThreadrun
SEVERE: Multicast receiver thread caught throwable. Cause was null. Continuing...

There is an issue with the cache configuration parameters, but the migration script ran and completed successfully. Check your cache configuration parameters. There is no need to rerun the migration script.

Last updated: 1 Aug 2014