IBM InfoSphere Master Data Management Reference Data Management Hub Version 11 Release 0. Upgrade Guide GI

Transcription

1 IBM InfoSphere Master Data Management Reference Data Management Hub Version 11 Release 0 Upgrade Guide GI

2

3 IBM InfoSphere Master Data Management Reference Data Management Hub Version 11 Release 0 Upgrade Guide GI

4 Note Before using this information and the product that it supports, read the information in Notices and trademarks on page 9. Edition Notice This edition applies to version 11.0 of IBM InfoSphere Master Data Management and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Tables v Figures vii Upgrading InfoSphere RDM Upgrading the InfoSphere RDM database Upgrading an existing InfoSphere RDM version 10.1 database on DB2 for UNIX or Linux Upgrading an existing InfoSphere RDM version 10.1 database on Oracle Adding RDM owners Handling corrupted data with similar base IDs... 7 Enabling trusted client mode Notices and trademarks Index Contacting IBM Copyright IBM Corp iii

6 iv Upgrade Guide

7 Tables 1. IBM resources Providing feedback to IBM Copyright IBM Corp v

8 vi Upgrade Guide

9 Figures Copyright IBM Corp vii

10 viii Upgrade Guide

11 Upgrading InfoSphere RDM You can upgrade to the current release of IBM InfoSphere Reference Data Management (RDM) from Version 10.1 to Version About this task You cannot currently upgrade to version 11.0 from a version prior to If you are running a version prior to 10.1, first upgrade your version to version 10.1, and then upgrade from 10.1 to See the upgrade instructions included with the Version 10.1 release. Before you upgrade RDM, ensure that you have completed all steps required for upgrading the IBM InfoSphere Custom Domain Hub (CDH). See the upgrade instructions for InfoSphere MDM CDH, which are currently delivered as a PDF file available from the same location where you obtained the PDF file for upgrading InfoSphere MDM RDM. Note: If you created any customizations or extensions for your Version 10.1 installation of RDM, redo the customizations and extensions for Version Upgrading the InfoSphere RDM database The upgrade applies to the original database structure and data. Any customizations or extensions might be deleted or changed by the upgrade. Adding RDM owners on page 6 RDM Version 11.0 uses a required Owners field for Folder and Data Type entities. Populate the Owners field after migration. Handling corrupted data with similar base IDs on page 7 After migration, run RDM migration scripts to identify corrupted records. Enabling trusted client mode on page 7 Trusted client mode determines whether the operational server processes the requested service using the identity that is specified in the requestername property of the DWLControl. Upgrading the InfoSphere RDM database The upgrade applies to the original database structure and data. Any customizations or extensions might be deleted or changed by the upgrade. Before you begin 1. Upgrade your application server and database server according to the instructions published with those applications. 2. Follow the instructions in the PDF file about upgrading IBM InfoSphere Master Data Management Custom Domain Hub. 1. Upgrading an existing InfoSphere RDM version 10.1 database on DB2 for UNIX or Linux on page 2 Follow the steps to upgrade your InfoSphere RDM database on DB2 for UNIX or Linux. 2. Upgrading an existing InfoSphere RDM version 10.1 database on Oracle on page 4 Follow the steps to upgrade your InfoSphere RDM database on Oracle. Copyright IBM Corp

12 Parent topic: Upgrading InfoSphere RDM, on page 1 Upgrading an existing InfoSphere RDM version 10.1 database on DB2 for UNIX or Linux Follow the steps to upgrade your InfoSphere RDM database on DB2 for UNIX or Linux. Before you begin The following steps assume that you have already upgraded the database for your IBM InfoSphere Custom Domain Hub installation. Be sure you have completed those steps before proceeding. Procedure 1. Connect to the Version 10.1 database using the same credentials that you used to connect to the Version 10.1 CDH/RDM instance. 2. Change the DB2 log file sizes to prevent transaction log buffer errors. Recommended settings: v LOGFILSIZ=3000 v LOGPRIMARY=30 v LOGSECOND=6 3. To check the sizes of log files and update files, run the following code: db2 get db cfg for <database_name> grep i LOGPRIMARY db2 update db cfg for <database_name> using LOGSECOND <new_value> To read and configure the primary log file, run the commands again, but replace logfilsiz with LOGPRIMARY. To read and configure the secondary log file, repeat the commands a third time, but replace logfilsiz with LOGSECOND. 4. To make sure the changes are saved, restart the DB2 database and the DB2 manager. 5. Navigate to the CDH_INSTALL_HOME/database/RDMScripts/UpgradeScipts/DB2 directory in your Version 11.0 installation. 6. If you are running on UNIX, run the dos2unix command on all the scripts in the directory to ensure the files are in UNIX format. 7. Roll back triggers and metadata for RDM version The default schema name in the.sql files are db2admin. If the schema name is different, replace the files accordingly in the following.sql files. Run the scripts in the order listed. a. db2 v td@ -f V10.1.0_Rollback_RDM_TRIGGERS_DB2.sql l <log_file_name> b. db2 tvf V10.1.0_Rollback_RDM_MetaData_DB2.sql -l <log_file_name> 8. Navigate to the CDH_INSTALL_HOME/database/RDMScripts/DB2 directory in your Version 11.0 installation. 9. If you are running on UNIX, run the dos2unix command on all the scripts in the directory to ensure the files are in UNIX format. 10. In the.sql files, replace <SCHEMA> with the appropriate schema name. 2 Upgrade Guide

13 11. Repopulate the triggers and metadata by running the following scripts in the order that they are listed: a. db2 v td@ -f RDM_TRIGGERS_DB2.sql l <log_file_name> b. db2 tvf RDM_MetaData_DB2.sql l <log_file_name> 12. Navigate to the CDH_INSTALL_HOME/database/RDMScripts/UpgradeScipts/DB2 directory in your Version 11.0 installation. 13. In the.sql files, replace <SCHEMA> with the appropriate schema name. 14. Run the following sql scripts in the order they are listed: a. db2 l <log_file_name> b. db2 l <log_file_name> c. db2 l <log_file_name> d. db2 l <log_file_name> e. db2 l <log_file_name> 15. Re-populate RDM metadata and code tables for non-english languages: db2 tvf RDM_MetaData_DB2_<language>.sql l <log_file_name> The list of non-english language scripts: v RDM_MetaData_DB2_de.sql v RDM_MetaData_DB2_es.sql v RDM_MetaData_DB2_fr.sql v RDM_MetaData_DB2_it.sql v RDM_MetaData_DB2_ja.sql v RDM_MetaData_DB2_ko.sql v RDM_MetaData_DB2_pt_BR.sql v RDM_MetaData_DB2_zh_CN.sql v RDM_MetaData_DB2_zh_TW.sql Note: Because RDM Version 10.1 already includes code tables for English, running the following script is not required: RDM_CODETABLES_DB2.sql. Upgrading InfoSphere RDM 3

14 16. Run the following code table scripts for non-english languages: db2 tvf RDM_CODETABLES_DB2_<language>.sql l <log_file_name> v RDM_CODETABLES_DB2_de.sql v RDM_CODETABLES_DB2_es.sql v RDM_CODETABLES_DB2_fr.sql v RDM_CODETABLES_DB2_it.sql v RDM_CODETABLES_DB2_ja.sql v RDM_CODETABLES_DB2_ko.sql v RDM_CODETABLES_DB2_pt_BR.sql v RDM_CODETABLES_DB2_zh_CN.sql v RDM_CODETABLES_DB2_zh_TW.sql Parent topic: Upgrading the InfoSphere RDM database on page 1 Next topic: Upgrading an existing InfoSphere RDM version 10.1 database on Oracle Upgrading an existing InfoSphere RDM version 10.1 database on Oracle Follow the steps to upgrade your InfoSphere RDM database on Oracle. Before you begin The following steps assume that you have already upgraded the database for your IBM InfoSphere Custom Domain Hub installation. Be sure you have completed those steps before proceeding. Procedure 1. Connect to the Version 10.1 database using the same credentials that you used to connect to the Version 10.1 CDH/RDM instance. 2. Navigate to the CDH_INSTALL_HOME/database/RDMScripts/UpgradeScipts/ Oracle directory in your Version 11.0 installation. 3. If you are running on UNIX, run the dos2unix command on all the scripts in the directory to ensure the files are in UNIX format. 4. Roll back triggers and metadata for RDM Version The default schema name in the.sql files are db2admin. If the schema name is different, replace the files accordingly in the following.sql files. Run the scripts in the order listed. a. sqlplus >> <log_file_name> b. sqlplus >> <log_file_name> 5. Navigate to the CDH_INSTALL_HOME/database/RDMScripts/Oracle directory in your Version 11.0 installation. 6. If you are running on UNIX, run the dos2unix command on all the scripts in the directory to ensure the files are in UNIX format. 7. In the.sql files, replace <SCHEMA> with the appropriate schema name. 4 Upgrade Guide

15 8. Repopulate the triggers and metadata by running the following scripts in the order that they are listed: a. >> <log_file_name> b. >> <log_file_name> 9. Navigate to the CDH_INSTALL_HOME/database/RDMScripts/UpgradeScipts/ Oracle directory in your Version 11.0 installation. 10. If you are running on UNIX, run the dos2unix command on all the scripts in the directory to ensure the files are in UNIX format. 11. In the.sql files, replace <SCHEMA> with the appropriate schema name. 12. Run the following sql scripts in the order they are listed: a. l <log_file_name> b. sqlplus >> <log_file_name> c. sqlplus >> <log_file_name> d. sqlplus >> <log_file_name> e. sqlplus >> <log_file_name> 13. Re-populate RDM metadata and code tables for non-english languages: sqlplus userid/password@host RDM_MetaData_ORACLE_<language>.sql >> <log_file_name> The list of non-english language scripts: v RDM_MetaData_ORACLE_de.sql v RDM_MetaData_ORACLE_es.sql v RDM_MetaData_ORACLE_fr.sql v RDM_MetaData_ORACLE_it.sql v RDM_MetaData_ORACLE_ja.sql v RDM_MetaData_ORACLE_ko.sql v RDM_MetaData_ORACLE_pt_BR.sql v RDM_MetaData_ORACLE_zh_CN.sql v RDM_MetaData_ORACLE_zh_TW.sql Upgrading InfoSphere RDM 5

16 Adding RDM owners Note: Because RDM Version 10.1 already includes code tables for English, running the following script is not required: RDM_CODETABLES_ORACLE.sql. 14. Run the following code table scripts for non-english languages: sqlplus RDM_CODETABLES_ORACLE_<language>.sql >> <log_file_name> The list of non-english language scripts: v RDM_CODETABLES_ORACLE_de.sql v RDM_CODETABLES_ORACLE_es.sql v RDM_CODETABLES_ORACLE_fr.sql v RDM_CODETABLES_ORACLE_it.sql v RDM_CODETABLES_ORACLE_ja.sql v RDM_CODETABLES_ORACLE_ko.sql v RDM_CODETABLES_ORACLE_pt_BR.sql v RDM_CODETABLES_ORACLE_zh_CN.sql v RDM_CODETABLES_ORACLE_zh_TW.sql Parent topic: Upgrading the InfoSphere RDM database on page 1 Previous topic: Upgrading an existing InfoSphere RDM version 10.1 database on DB2 for UNIX or Linux on page 2 RDM Version 11.0 uses a required Owners field for Folder and Data Type entities. Populate the Owners field after migration. About this task Owner fields control access and authorization for various RDM entities like sets, mappings, and so on. Do not confuse these entities with roles like Administrator, Steward, and so on, which offer broader access and authorization control on entity actions like create, delete, and change state of entity. Owner fields use user-defined groups to limit how entities can be edited. Only a user who belongs to one or more groups in the Owners field for the entity is able to edit the entity. A user who does not belong to any group in the Owners field is able to view the entity, but all other actions are disabled. RDM Version 11.0 adds Owner fields functionality to Folders and Data Types. Previously the Owner field was only available with Sets and Mappings. After migration, all Owner fields for entities Folder and Data Types are empty. The field is a custom combo-box. Populate the Owners field appropriately from the groups available in the combo-box. Because the Owner field is a required entity property, you must populate the Owner field before you can save and switch to any other entity. The following steps describe how to populate the fields for all Folder and Data Type entities. After Owners have been selected and saved, the appropriate security is automatically applied to the entity. 6 Upgrade Guide

17 Procedure 1. Click on the Owners button associated with the Owner field. 2. Select and add appropriate available groups from the combo-box. 3. Save the entity. Results If the user belongs to any groups added to the Owner field, the entity is now editable. If not, the entity is read-only for the user. Parent topic: Upgrading InfoSphere RDM, on page 1 Handling corrupted data with similar base IDs After migration, run RDM migration scripts to identify corrupted records. About this task Enabling trusted client mode Because of a bug, records that are different might share the same BaseId. Such records are considered corrupted. The BaseId for a record is not visible to the user, but RDM scripts can identify the corrupted records so that administrators can fix the records manually. Procedure 1. Depending on your database, run one of the following scripts. The scripts include a select statement that identifies corrupted records in the log files: SELECT R1.RD_VALUE_SET_ID, R1.RD_VALUE_ID, R1.RD_VALUE_NAME... v DB2: V10.1.0_TO_V11.0.0_RELEASE_MIGRATION_DML_DB2.sql v Oracle: V10.1.0_TO_V11.0.0_RELEASE_MIGRATION_DML_ORACLE.sql 2. View the log file for the script you ran and identify the Set entities that need to be fixed manually. 3. Manually fix the Set entities by deleting and recreating the 'RDM Value entities' for each Set entity. Parent topic: Upgrading InfoSphere RDM, on page 1 Trusted client mode determines whether the operational server processes the requested service using the identity that is specified in the requestername property of the DWLControl. About this task InfoSphere RDM requires that trusted client mode is enabled. When it is enabled, the operational server does not retrieve the user group information; instead, it trusts the client to put the roles into any message requests. The parameter is provided to enable backward compatibility because, prior to InfoSphere MDM version 11.0, the user name set in the requestername property of the DWLControl was always used. By default, the mode is disabled, which indicates that the InfoSphere MDM operational server processes a requested transaction using the identity of the user who calls the service (for example, the user who is authenticated by the container). Upgrading InfoSphere RDM 7

18 Procedure 1. Connect to the database. 2. Run the following query: update configelement set value = true, LAST_UPDATE_DT=CURRENT_TIMESTAMP, LAST_UPDATE_USER= admin where name= /IBM/DWLCommonServices/Security/TrustedClientMode/enabled Parent topic: Upgrading InfoSphere RDM, on page 1 Related tasks: Managing users Elements in the Configuration and Management component 8 Upgrade Guide

19 Notices and trademarks This information was developed for products and services offered in the U.S.A. Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd , Shimotsuruma, Yamato-shi Kanagawa Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Copyright IBM Corp

20 Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J46A/G4 555 Bailey Avenue San Jose, CA U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: 10 Upgrade Guide

21 This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. Copyright IBM Corp. _enter the year or years_. All rights reserved. If you are viewing this information softcopy, the photographs and color illustrations may not appear. Privacy Policy Considerations IBM Software products, including software as a service solutions, ("Software Offerings") may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering s use of cookies is set forth below. Depending upon the configurations deployed, this Software Offering may use session and persistent cookies that collect each user s name, user name, password, profile name, or other personally identifiable information for purposes of session management, authentication, enhanced user usability, single sign-on configuration, or web page identification that the user tried to load prior to login. These cookies can be disabled, but disabling them will also likely eliminate the functionality they enable. If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent. For more information about the use of various technologies, including cookies, for these purposes, see IBM s Privacy Policy at and IBM s Online Privacy Statement at the section entitled "Cookies, Web Beacons and Other Technologies" and the "IBM Software Products and Software-as-a-Service Privacy Statement" at product-privacy. Notices and trademarks 11

22 Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at The following terms are trademarks or registered trademarks of other companies: Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of The Minister for the Cabinet Office, and is registered in the U.S. Patent and Trademark Office. UNIX is a registered trademark of The Open Group in the United States and other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo are trademarks of HP, IBM Corp. and Quantum in the U.S. and other countries. 12 Upgrade Guide

23 Index C customer support contacting 15 L legal notices 9 S software services contacting 15 support customer 15 T trademarks list of 9 Copyright IBM Corp

24 14 Upgrade Guide

25 Contacting IBM You can contact IBM for customer support, software services, product information, and general information. You also can provide feedback to IBM about products and documentation. The following table lists resources for customer support, software services, training, and product and solutions information. Table 1. IBM resources Resource Description and location Product documentation for InfoSphere MDM You can search and browse across all the InfoSphere MDM documents at v11r0/index.jsp. Product documentation for InfoSphere MDM Custom Domain Hub, including InfoSphere MDM Reference Data Management IBM Support Portal Software services My IBM Training and certification IBM representatives You can search and browse across all the InfoSphere MDM Custom Domain Hub documents at infocenter/mih/v11r0/index.jsp. You can customize support information by choosing the products and the topics that interest you at You can find information about software, IT, and business consulting services, on the solutions site at businesssolutions/. You can manage links to IBM web sites and information that meet your specific technical support needs by creating an account on the My IBM site at You can learn about technical training and education services designed for individuals, companies, and public organizations to acquire, maintain, and optimize their IT skills at You can contact an IBM representative to learn about solutions at Providing feedback The following table describes how to provide feedback to IBM about products and product documentation. Table 2. Providing feedback to IBM Type of feedback Product feedback Action You can provide general product feedback through the Consumability Survey at consumability/. Copyright IBM Corp

26 Table 2. Providing feedback to IBM (continued) Type of feedback Action Documentation feedback To comment on the information center, click the Feedback link on the top right side of any topic in the information center. You can also send comments about PDF file books, the information center, or any other documentation in the following ways: v Online reader comment form: v comments@us.ibm.com 16 Upgrade Guide

27

28 Printed in USA GI