Files and assets that cannot be migrated to InfoSphere Information Server, V.11.5

Certain files and assets cannot be migrated by using istool and there are some files and assets that cannot be migrated at all. Some of the files that cannot be moved by using istool can be manually migrated by using other migration methods.

Contents

InfoSphere Business Glossary

The following data either cannot be migrated by using istool, or cannot be migrated at all:

Data that cannot be migrated by using istool, but can be manually migrated
  • Viewing permissions
  • Permissions for terms and categories
You can manually reconfigure the items listed above on your new computer from the Administration tab in Information Governance Catalog. However, you cannot export this information to a file and then re-import it. When you export permissions for terms and categories, the permissions information is not included in the exported file. You can manually define it again on your target computer.
Data that cannot be migrated
Term history

InfoSphere Data Quality Console

InfoSphere Data Quality Console is not supported at Version 11.5. The functionality has been replaced by the Data Quality Exception Console. You cannot migrate InfoSphere Data Quality Console assets to Version 11.5.

InfoSphere DataStage and QualityStage

The following data either cannot be migrated by using istool, or cannot be migrated at all:

Data that cannot be migrated by using istool, but can be manually migrated
  • DSParams settings, which are per-project. Export and import the settings by using the Administrator client
  • FTP (file transfer protocol) and send mail templates in the Project directory. You copy this to the target computer
  • The uvodbc.config file in the Project directory. You copy this to the target computer.
  • Message handlers, which are under the Server directory. You copy this to the target computer.
  • DSEngine configuration, which is in the uvconfig file. You copy this to the target computer.
    Note: If you are migrating to a target computer that has a different operating system than your source computer, edit the uvconfig file and then issue the uvregen command.
  • User-defined entries in the dsenv file. For more information about setting up the dsenv file, see Configuring the dsenv file. Manually merge the changes you made for your environment into the new dsenv file.
  • odbc.ini file. For all versions before Version 9.1, manually merge the changes in the file. For Version 9.1 and later, you should be able to copy the file from your source computers and move it to your target computers. You copy this to the target computer.
    Note: If you are migrating to a target computer that has a different operating system than your source computer, the migration of the odbc.ini file is unsupported. You will have to edit the new file on your target computer.
  • Parallel job configuration files. You copy this to the target computer.
  • Non-administrator roles for the projects
  • Project files like hash files, data sets, run-time log files, and job schedules. The best practice is for jobs to recreate data sets on every invocation. If you are using data sets for persistent data, the best practice is to create jobs to export and import the data into a exportable format, such as a database table or file set. Run-time log files can be printed from the InfoSphere® DataStage® and QualityStage® Director.
  • Operational metadata. If you retain the original operational metadata import files, you can import the files onto your new computer.
  • apt_config_files. If you are migrating to the same host names and paths, you can back up and restore the files. Otherwise, you have to manually edit them to match the current environment.
  • Data sets. For information on migrating data sets, see http://www.ibm.com/support/docview.wss?uid=swg21392477.
  • Files that are referenced by jobs that are not in the project directories. You must save the files and manually move them to the target installation.
  • The exceptions database. You must back up the database on the source computer and restore it on the target computer by using back-up and restore documentation for the database you are using as your exceptions database.
  • The Standardization Rules Designer database. You use asset interchange or the InfoSphere DataStage and QualityStage Designer to import and export the actual standardization rule sets to the new system, rather than migrating the whole Standardization Rules Designer database.
  • The Match Designer database. You must back it up on the source computer and restore it on the target computer or recreate the database on the target computer.
  • Modules and reference files. You download and install compatible versions of the modules and reference files on the target computer and edit InfoSphere QualityStage jobs to point to the location of the reference files or to use the updated modules.
Note: You cannot migrate the assets listed above by using istool or the InfoSphere DataStage Designer.
Data that cannot be migrated
  • InfoSphere QualityStage postal validation reference files. You must install new reference files on your new system.
  • InfoSphere QualityStage geocoding reference files. You must install new reference files on your new system.

IBM® InfoSphere DataStage and QualityStage Operations Console

The following data cannot be migrated:

Data that cannot be migrated
The operations database. The migration of the operations database is not supported, and not recommended. The operations database contains data that is specific to InfoSphere DataStage jobs that were run on your old computer. That data is not required on your new computer. You should start with a new operations database on your new computer.

InfoSphere Information Server

The following data either cannot be migrated by using istool, or cannot be migrated at all:

Data that cannot be migrated by using istool, but can be manually migrated
  • Owner and group read, write, and execute permissions for file systems. The user ownership, as well as the read, write, and execute permissions, cannot be migrated by using istool. You must manually update these permissions on your target computer.
  • Permissions related to who can access reports. After you move the reports to your target system by using istool, you must open each report on the Reporting tab in the Administration Console and click Open Access Control. You can specify who can read, update, delete, modify, and run each report.
  • Credential mapping information. Manually create the operating system users on your target computer to match the credential mapping information that you exported.
  • WebSphere® registry configuration for the operating system and LDAP. Manually configure WebSphere when you set up WebSphere on your target computer.
  • WebSphere registry configuration for SSL LDAP user registries. Manually configure WebSphere when you set up WebSphere on your target computer.
  • WebSphere registry configuration for federated user registries. Manually configure WebSphere when you set up WebSphere on your target computer.
Data that cannot be migrated
  • Mainframe assets. You cannot migrate mainframe assets to Version 11.5. They are no longer supported by all products in the InfoSphere Information Server suite. Also, you cannot migrate from InfoSphere Information Server on a mainframe to InfoSphere Information Server, Version 11.5 on a mainframe, because the mainframe is longer supported by InfoSphere Information Server.
  • Logging reports and logging views are no longer supported. These include logs such as:
    • CAS+Log.log
    • iasHandler-server1.log
    • iasServer-server1.log
    • SystemErr.log
    • SystemOut.log
  • DHTML reports are no longer supported
  • Reporting schedules. Recreate the schedules on your target computer.

InfoSphere Information Services Director

The following data cannot be migrated:

Data that cannot be migrated
The InfoSphere Information Services Director connections cannot be migrated and must be manually entered on the target computer. This should be done before importing any applications from the source computer.

InfoSphere FastTrack

The following data cannot be migrated:

Data that cannot be migrated
Aggregate and switch mapping elements in Versions 8.0.1, 8.1, and 8.1.1.

InfoSphere Information Governance Catalog

The following data either cannot be migrated by using istool, or cannot be migrated at all:

Data that cannot be migrated by using istool, but can be manually migrated
  • Viewing permissions
  • Permissions for terms and categories

You can manually reconfigure the items listed above on your new computer from the Administration tab in Information Governance Catalog. However, you cannot export this information to a file and then re-import it. When you export permissions for terms and categories, the permissions information is not included in the exported file. You can manually define it again on your target computer.

  • Registered asset type bundles

You must manually register the asset type bundles on the target computer. For more information, see the topic "Registration of asset type bundles" in the PDF attachment to this technote.

Data that cannot be migrated
Term history
Workflow
Collections
Lineage administration and configuration settings, including manual bindings
Custom view configuration
Language setting configuration
Event notification and Subscription Manager settings

InfoSphere Information Analyzer

The following data cannot be migrated:

Data that cannot be migrated and that must be reconfigured
You must reconfigure the following settings in the newly installed version of InfoSphere Information Analyzer:
  • Analysis database configuration settings
  • Analysis settings such as thresholds
Data that cannot be migrated and must be regenerated:
Primary key analysis results cannot be migrated. You must rerun all primary key, foreign key and natural key analyses.

InfoSphere Metadata Asset Manager

You can move metadata that has been shared to the metadata repository, but you cannot move any assets in the staging area that have not been shared.

InfoSphere Metadata Workbench

The following data either cannot be migrated by using istool, or cannot be migrated at all:

Data that cannot be migrated by using istool, but can be manually migrated
  • Database alias mappings must be manually recreated on the new computer.
  • Manual bindings, data item bindings and stage bindings must be manually recreated on the new computer.
  • Data source identities must be re-mapped manually on the new computer.
  • Extended data sources that you migrate will lose steward and term assignments, however you can export these attributes by using InfoSphere Business Glossary or Information Governance Catalog.
  • Custom attribute definitions. You can migrate custom attribute definitions by exporting them to an XML file and then reimporting them.
Data that cannot be migrated
  • Operational metadata. If you do not have the original operational metadata XML files to import, you cannot migrate the metadata.
  • Extension mapping documents will lose the type, description, term and steward assignments.
Parent topic: Performing a migration