MDM Multidomain Edition (Version 9.0.1) Zero Downtime (ZDT) User Guide

Transcription

1 MDM Multidomain Edition (Version 9.0.1) Zero Downtime (ZDT) User Guide

2 Informatica MDM Multidomain Hub - Version September 2010 Copyright (c) 2010 Informatica. All rights reserved. This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software is be protected by U.S. andor international Patents and other Patents Pending. Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS (a) and (a) (1995), DFARS (1)(ii) (OCT 1988), FAR (a) (1995), FAR , or FAR (ALT III), as applicable. The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing. Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange, Informatica On Demand and Siperian are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Portions of this software andor documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights reserved. Copyright Sun Microsystems. All rights reserved. This product includes software developed by the Apache Software Foundation ( and other software which is licensed under the Apache License, Version 2.0 (the "License"). You may obtain a copy of the License at LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. This product includes software which is licensed under the GNU Lesser General Public License Agreement, which may be found at The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. This product includes software which is licensed under the CDDL (the "License"). You may obtain a copy of the License at The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. See the License for the specific language governing permissions and limitations under the License. This product includes software which is licensed under the BSD License (the "License"). You may obtain a copy of the License at The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. See the License for the specific language governing permissions and limitations under the License. This product includes software Copyright (c) , Terence Parr, all rights reserved which is licensed under the BSD License (the "License"). You may obtain a copy of the License at The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. See the License for the specific language governing permissions and limitations under the License. This product includes software Copyright (c) The Legion Of The Bouncy Castle ( which is licensed under a form of the MIT License (the "License"). You may obtain a copy of the License at The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. See the License for the specific language governing permissions and limitations under the License. DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice. NOTICES This Informatica product (the Software ) may include certain drivers (the DataDirect Drivers ) from DataDirect Technologies, an operating company of Progress Software Corporation ( DataDirect ) which are subject to the following terms and conditions: 1. THE DATADIRECT DRIVERS ARE PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. 2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS. Informatica MDM Hub Zero Downtime (ZDT) User Guide ii

3 Informatica Resources Informatica Customer Portal As an Informatica customer, you can access the Informatica Customer Portal site at The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library, the Informatica Knowledge Base, the Informatica Multimedia Knowledge Base, Informatica Documentation Center, and access to the Informatica user community. Informatica Documentation The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through at We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments. The Documentation team updates documentation as needed. To get the latest documentation for your product, navigate to the Informatica Documentation Center from Informatica Web Site You can access the Informatica corporate web site at The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services. Informatica How-To Library As an Informatica customer, you can access the Informatica How-To Library at The How-To Library is a collection of resources to help you learn more about Informatica products and features. It includes articles and interactive demonstrations that provide solutions to common problems, compare features and behaviors, and guide you through performing specific real-world tasks. Informatica Knowledge Base As an Informatica customer, you can access the Informatica Knowledge Base at Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team through at KB_Feedback@informatica.com. Informatica Multimedia Knowledge Base As an Informatica customer, you can access the Informatica Multimedia Knowledge Base at The Multimedia Knowledge Base is a collection of instructional multimedia files that help you learn about common concepts and guide you through performing specific tasks. If you have questions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Base team through at KB_Feedback@informatica.com. iii Informatica MDM Hub Zero Downtime (ZDT) User Guide

4 Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the WebSupport Service. WebSupport requires a user name and password. You can request a user name and password at Use the following telephone numbers to contact Informatica Global Customer Support: North AmericaSouth America Toll Free North America Brazil Mexico Standard Rate North America EuropeMiddle EastAfrica Toll Free United Kingdom or France Netherlands Germany Switzerland Israel Spain Portugal Italy AsiaAustralia Toll Free Australia New Zealand Singapore Standard Rate India Standard Rate Belgium France Germany Netherlands Switzerland Informatica MDM Hub Zero Downtime (ZDT) User Guide iv

5 Table of Contents Introduction... 1 Prerequisites 1 Related Information 1 Sample ZDT Upgrade Scenario... 2 Scenario 1: User Schema Upgrade Without Data Change 2 Scenario 2: User Schema Upgrade Requiring Data ChangeReload 2 Scenario 3: Internal Hub Upgrade 2 Scenario 4: Infrastructure Upgrade 2 Steps in the Upgrade Process... 3 Remaining Steps Invoked from Environment A 17 Tips and Troubleshooting Registered Backfill Tasks 20 Reset Matches on Target 20 New Message Type Enhancement 20 v Informatica MDM Hub Zero Downtime (ZDT) User Guide

6

7 Introduction The Zero Downtime functionality is also known as High Availability. This document refers to High Availability as Zero Downtime (ZDT). The ZDT functionality of the Informatica MDM Hub was designed to support upgrade processes on the Hub while allowing for uninterrupted access to the Hub by the various user processes (Batch and Online). ZDT makes use of a duplicated passive environment to perform the upgrade while letting the active environment provide for user processing. GoldenGate is the tool used to provide replication from the active to the passive environment. In order to provide a seamless swing from the active environment to the newly upgraded environment, a number of new interfaces are provided by ZDT to facilitate the switchover and to allow for communication between the new environments. As well, the Hub has been updated for ZDT to ensure that any changes made to the Hub on the upgrade do not impact the ability to replicate changes from the active environment. Also, any impact to the Hub metadata due to upgrade is handled by new backfill mechanisms. This guide demonstrates the use of ZDT functionality via sample upgrade scenarios. For the purposes of this document, we will refer to the active environment as environment A and the passive (upgrade) environment as environment B. Upgrades are always done on the passive environment (B), so that there is no impact to the active environment (A). There are numerous types of upgrade that can be performed on the Hub and ZDT is designed to accommodate all of these will providing for Zero Downtime. This document will discuss four typical upgrade scenarios that cover the majority of the upgrades that are performed with the Hub. These upgrades are provided for by ZDT with minimal customization. Prerequisites To use this functionality, you must have installed the following software: MDM Hub (9.0.1) GoldenGate 10.4 (see the Informatica MDM Hub Zero Downtime (ZDT) Install Guide for more details) Related Information For more information, see: GGS_WinUnix_Reference_10.0 GGS_WinUnix_Admin_ Informatica MDM Hub Zero Downtime (ZDT) User Guide

8 Sample ZDT Upgrade Scenario Below is a sample of the upgrade steps that could be used as part of a ZDT upgrade process. These steps would be executed from a command line interface (such as shell scripts) or a command-line job scheduler. A goal is to allow the upgrade to be executed from a single flow of control. This would allow for almost complete automation of the upgrade process. This process highlights how the messaging infrastructure will work, what we need for replication control, and how backfill is integrated. Typical upgrades will consist of one or more of the following change scenarios. In regular use it would be common for all scenarios to be combined into a single upgrade. Scenario 1: User Schema Upgrade Without Data Change This is the scenario, where the user schema is modified according to business requirements. This is the most common customer upgrade. Trust is added to one pre-existing base object column (DO_NOT_CALL_FLAG) on C_CUSTOMER. Also one column (GENDER_CODE) is removed from C_CUSTOMER. Both of these will require MET upgrades to the schema. Scenario 2: User Schema Upgrade Requiring Data ChangeReload This scenario would always involve a Scenario 1 upgrade as well. An additional base object C_AGREEMENT is going to be reloaded from the XREF so that they can re-consolidate the base object (BO). This is a separate BO in that there are no FK dependencies from C_AGREEMENT tofrom C_CUSTOMER. If other BOs have FK dependencies on C_AGREEMENT, they would have to be reloaded as part of the same process in order to manage the FK dependencies correctly. For simplicity of this example, we will assume that C_AGREEMENT is not a parent to other BOs. Scenario 3: Internal Hub Upgrade This is an upgrade due to changes in the Informatica Hub software (such as a hotfix, service pack, or new release). For this scenario, as an example, we add an LSC to populate new a repository table (C_REPOS_ SOME_INTERNAL_SETTINGS). Scenario 4: Infrastructure Upgrade For an infrastructure only upgrade, no additional steps are required. Informatica MDM Hub Zero Downtime (ZDT) User Guide 2

9 Steps in the Upgrade Process These sections are color coded to show the impact of each change above. The blue text sections are default processing that would always occur. A. Pre-upgrade Stage (this is done manually BEFORE you start the upgrade) Generate MET changelist (my_implementation_upgrade.xml) - this will contain trust addition for do_not_call_flag, plus removal of c_customer.gender_code. Dry run the changelist against environment B - this will not do any changes to B, but will detect potential problems. B. Automated Upgrade Stage Steps in the Upgrade Process 1. Disable read services to environment B (if currently enabled) 2. Set ACTIVE_UPGRADE_IND to 1 in environment B 3. Turn off replication replay on environment B 4. Run cleanup of obsolete objects in environment B 5. [Scenario 3 only] Run LSC scripts (SIP_ANT) 6. [Scenario 1 only] Run MET command line utility - Apply Changelist 7. [Scenario 1 only] Populate backfill table C_REPOS_ZDT_BACKFILL_TASK 8. [Scenarios 1 and 2] Run backfill scripts (all backfill) 9. [Scenario 2 only] Prepare to reload C_AGREEMENT 10. [Scenario 2 only] Start re-load of C_AGREEMENT 11. [Optional Step] Record SCN for later flashback and start Customer Acceptance Validation 12. [Optional Step] Completion of User Acceptance Validation, flashback to SCN from Step Turn replication replay back on 14. Detect completion of replication catch-up 15. Send message from B to A to disallow batch processes on A 16. Enable writeable SIF services on environment B 17. Synchronize sequences 18. Redirect services to environment B 19. Disable writeable SIF services on environment A 20. Complete replication processing in environment B 21. [Scenario 2 only] Delta processing of C_AGREEMENT 22. Run backfill tasks (for dirty data only) 23. Enable batch services on environment B 24. Remove backfill tasks now that all data is clean 25. Run Foreign Key validation (if user data FKs changed during upgrade) 26. Stop all GoldenGate processes on environment B and environment A 27. To setup for replication switch, mark environment B as the source 28. On environment B, remove history from ZDT event queue 29. Set ACTIVE_UPGRADE_IND to 0 in environment B 30. Configure sequences for environment B (the new source) to be even 31. Deploy and start event queue on environment B 32. Deploy new replication baseline parameter files from environment B to environment A 33. Start extract and pump on environment B (now the source) 34. Get current SCN from environment B 35. Export environment B using Data Pump with the SCN just recorded 36. Resume batch jobs in environment B 3 Informatica MDM Hub Zero Downtime (ZDT) User Guide

10 Remaining Steps Invoked from Environment A 37. (before import) Drop and create environment A 38. (after import) Re-compile the packages, stored procedures, and views 39. Restore ZDT status for environment A (the new target) 40. On environment A, clean C_REPOS_ZDT_ENV_STATE table and history info 41. Configure sequences on environment A to be odd now 42. Check environment specific settings on environment A 43. Deploy and start event queue on environment A (new target) 44. Deploy new replication baseline parameter files from environment A to environment B 45. Start replication replay on environment A Informatica MDM Hub Zero Downtime (ZDT) User Guide 4

11 Upgrade Steps Controlled from Environment B These steps are callable from command line. Note: Every step is dependent on the previous steps and will not execute until previous step is complete. Prior to the upgrade, replication is assumed to be currently active from environment A to environment B (the systems are in synch). 1. Disable read services to environment B (if currently enabled) 2. Set ACTIVE_UPGRADE_IND to 1 in environment B update C_REPOS_ZDT_STATUS set ACTIVE_UPGRADE_IND = 1; BEGIN cmxzdt.v_zdt_ind:= -1; END; commit; 3. Turn off replication replay on environment B begin cmxzdt.stop_replication_replay(out_error_message => out_error_msg, out_return_code => out_return_code); end; 4. Run cleanup of obsolete objects in environment B This step is done now for schema changes from a prior upgrade. begin cmxzdt.cleanup_obsolete_objects( out_error_message => out_error_msg, out_return_code => out_return_code); end; 5 Informatica MDM Hub Zero Downtime (ZDT) User Guide

12 Removes all columns and tables that were backward compatible removed from B during previous upgrade (based on C_REPOS_MET_VIRTUAL_CHANGE). 5. [Scenario 3 only] Run LSC scripts (SIP_ANT) This will upgrade any repository tables if an Informatica MDM (Siperian) upgrade has occurred. Specifically, this will make the change to environment B to add C_REPOS_SOME_INTERNAL_SETTINGS. At this step also any data fixesmigration to the user data should take place. These would be added as custom MIG scripts to the data_changes directory. An example is fixes to FK lookup data in the event that lookups will be added in the next step. 6. [Scenario 1 only] Run MET command line utility - Apply Changelist This will apply my_implementation_upgrade.xml (this removes the gender code and adds trust to the do_not_call_flag column) 7. [Scenario 1 only] Populate backfill table C_REPOS_ZDT_BACKFILL_TASK (this table is not replicated) to say that trust backfill is required for this upgrade on C_CUSTOMER Sample below: SQL> exec CMXZDT.add_backfill_task('TRUST_BACKFILL','C_CUSTOMER','B', 1); SQL> COMMIT; In the example above, trust backfill for customer affects (B)oth Write and Read activities, and the sequence is 1 Note: This data for this step can be automatically generated based on repository metadata. Informatica MDM Hub Zero Downtime (ZDT) User Guide 6

13 8. [Scenarios 1 and 2] Run backfill scripts (all backfill) declare in_dirty_only_ind INT; user_name varchar2(32); begin in_dirty_only_ind := 0; user_name := 'admin'; out_error_msg := NULL; out_return_code := NULL; cmxzdt.backfill_batch_all(in_dirty_only_ind,user_name,out_error_msg,out_return_code); end; commit; This proc will decide what backfill needs to be executed and for which tables based on the contents of C_REPOS_BACKFILL_TASK, 0 indicates for full table (not just dirty records). Also, backfill batch can be executed per base object from Batch View in MRM console. 9. [Scenario 2 only] Prepare to reload C_AGREEMENT Disable regular GG mapping for C_AGGREMENT and change the C_AGREEMENT_XREF mapping and make it replicate to the new table C_AGGREMENT_XREF_NEW_FROM_A. Done via the two steps below: 9.1. cmxzdt.disable_bo_replication ('C_AGREEMENT') - turns off mapping for the entire C_AGGREMENT base object and all related tables. Sample script: begin cmxzdt.disable_bo_replication ('C_AGREEMENT'); commit; end; 7 Informatica MDM Hub Zero Downtime (ZDT) User Guide

14 9.2. cmxzdt.remap_table_replication ('C_AGREEMENT_XREF',' C_AGREEMENT_XREF_NEW_FROM_A') - creates new mapping from C_AGREEMENT_XREF to C_AGREEMENT_XREF_NEW_FROM_A - source and target tables must be the same for this to work. The table C_AGREEMENT_XREF_NEW_FROM_A is automatically created by cmxzdt.remap_table_replication procedure, which fails if such table exists already. Sample script: begin cmxzdt.remap_table_replication ('C_AGREEMENT_XREF', 'C_AGREEMENT_XREF_NEW_FROM_A'); commit; end; 10. [Scenario 2 only] Start re-load of C_AGREEMENT Data will come from existing C_AGREEMENT_XREF- this is custom written by the implementation resources. Note: For this step we do not need to wait before proceeding to the next steps in the process. 11. [Optional Step] Record SCN for later flashback and start Customer Acceptance Validation This is an optional specific step for user acceptance testing. 12. [Optional Step] Completion of User Acceptance Validation, flashback to SCN from Step 10 This is an optional specific step for user acceptance testing. The time between these two steps can vary from hours to days. 13. Turn replication replay back on This is for environment B to process any data changes from environment A. Sample SQL below: begin cmxzdt.start_replication_replay(in_env_type => cmxzdt.zdt_local, out_error_message => out_error_msg, out_return_code => out_return_code); end; Informatica MDM Hub Zero Downtime (ZDT) User Guide 8

15 14. Detect completion of replication catch-up This is done on environment B. Depending on how much time was spent in Dark Pod validation and the transaction volume on A, this step may take some time to complete. Sample SQL below: BEGIN cmxzdt.wait_replay_catchup(in_timeout_minutes => 5, out_error_message => out_error_msg, out_return_code => out_return_code); END; 15. Send message from B to A to disallow batch processes on A BEGIN cmxzdt.disable_all_batch( in_affected_zdt_env => cmxzdt.zdt_source,in_timeout_minutes => 30, out_error_message => out_error_msg, out_return_code => out_return_code ); dbms_output.put_line('out_return_code => ' out_return_code ' out_error_msg => END; Changes would be required to the batch scheduling (ETL scripts) and batch control script to detect this condition and not attempt new jobs. This can be controlled based on the flag on environment A in C_REPOS_ZDT_STATUS.batch_disabled_ind. Any subsequent invocation of batch jobs from A will result in an error. The job scheduler should be updated accordingly. 9 Informatica MDM Hub Zero Downtime (ZDT) User Guide

16 16. Enable writeable SIF services on environment B BEGIN cmxzdt.enable_all_write_sif( in_affected_zdt_env => cmxzdt.zdt_target,in_timeout_minutes => 5,out_error_message => out_error_msg,out_return_code => out_return_code ); END; 17. Synchronize sequences This is done to ensure that the target environment has been updated from all sequence changes to the source. This resets the high water mark of all user sequences. This is done because the target sequences are not updated via replication. When replication is switched over between environments, the synch of sequences ensures that new sequence values on the target are higher than on the source. begin cmxzdt.synchronize_sequences( out_error_message => out_error_msg,out_return_code => out_return_code ); end; 18. Redirect services to environment B This is done via remote shell script command. Environment B is now live for read and write services. Informatica MDM Hub Zero Downtime (ZDT) User Guide 10

17 19. Disable writeable SIF services on environment A BEGIN cmxzdt.disable_all_write_sif( in_affected_zdt_env => cmxzdt.zdt_source,in_timeout_minutes => 5,out_error_message => out_error_msg,out_return_code => out_return_code); dbms_output.put_line('out_return_code => ' out_return_code ' out_error_msg => END; 20. Complete replication processing in environment B This call will return when all data is replicated to environment B (the target). begin cmxzdt.stop_replication(out_error_message => out_error_msg, out_return_code => out_return_code, in_timeout_minutes => 60); end; 21. [Scenario 2 only] Delta processing of C_AGREEMENT Catchup of services updates to Agreement taken from replicated C_AGREEMENT_XREF_NEW_FROM_A (assumes reload on B from Step 9 is complete) - this is custom written by the implementation resources to handle the data that came from A after reload on B. 11 Informatica MDM Hub Zero Downtime (ZDT) User Guide

18 22. Run backfill tasks (for dirty data only) declare in_dirty_only_ind INT; user_name varchar2(32); begin in_dirty_only_ind := 1; user_name := 'admin'; out_error_msg := NULL; out_return_code := NULL; cmxzdt.backfill_batch_all(in_dirty_only_ind,user_name,out_error_msg,out_return_code); end; commit; Note: JIT Backfill for services is active while this is running. The locks are batch row level locks. Also, backfill batch can be executed per base object from Batch View in MRM console. 23. Enable batch services on environment B BEGIN cmxzdt.enable_all_batch( in_affected_zdt_env => cmxzdt.zdt_target,in_timeout_minutes => 5,out_error_message => out_error_msg,out_return_code => out_return_code ); END; 24. Remove backfill tasks now that all data is clean This will ensure that no more backfill (batch or API) will run. Also, by removing the backfill tasks, other batch jobs are now free to execute. Delete from c_repos_zdt_backfill_task; commit; Informatica MDM Hub Zero Downtime (ZDT) User Guide 12

19 25. Run Foreign Key validation (if user data FKs changed during upgrade) This would have only occurred if new lookups were added as part of the upgrade (Scenario 2). This would catch any violations that came from environment A after the patches to the lookup data. Depending on the severity of the issues found, the upgrade can proceed and the fix can be done after the upgrade is complete. If there are widespread issues, then the upgrade should be aborted. IN_ROWID_TABLE CHAR(14); IN_USER_NAME VARCHAR2(50); OUT_ERROR_MESSAGE VARCHAR2(1024); OUT_RETURN_CODE NUMBER; IN_ROWID_JOB_GRP_CTRL CHAR(14); IN_ROWID_JOB_GRP_ITEM CHAR(14); IN_LIST_ROWID_COLUMN VARCHAR2(4000); IN_CASCADE_VALIDATE_IND NUMBER; BEGIN IN_ROWID_TABLE := 'SVR1.MY_BO'; IN_USER_NAME := 'UPGRADE_USER'; OUT_ERROR_MESSAGE := NULL; OUT_RETURN_CODE := NULL; IN_ROWID_JOB_GRP_CTRL := NULL; IN_ROWID_JOB_GRP_ITEM := NULL; IN_LIST_ROWID_COLUMN := NULL; IN_CASCADE_VALIDATE_IND := NULL; CMXUT.VALIDATE_BO_FKS ( IN_ROWID_TABLE, IN_USER_NAME, OUT_ERROR_MESSAGE, OUT_RETURN_CODE, IN_ROWID_JOB_GRP_CTRL, IN_ROWID_JOB_GRP_ITEM, IN_LIST_ROWID_COLUMN, IN_CASCADE_VALIDATE_IND ); DBMS_OUTPUT.Put_Line('OUT_ERROR_MESSAGE = ' OUT_ERROR_MESSAGE); DBMS_OUTPUT.Put_Line('OUT_RETURN_CODE = ' TO_CHAR(OUT_RETURN_CODE)); COMMIT; END; 13 Informatica MDM Hub Zero Downtime (ZDT) User Guide

20 26. Stop all GoldenGate processes on environment B and environment A From the GoldenGate command line, stop all GG processes on environment B (the target) and remove processes and trail files: Sample: GGSCI (hostname) 1> dblogin userid USER password "Password" GGSCI (hostname) 1> stop * GGSCI (hostname) 1> delete * -- hit 'y' when Prompted for ny GGSCI (hostname) 1> DELETE TRACETABLE [SCHEMA_NAME].GGS_EVENT_TRACE GGSCI (hostname) 1> DELETE CHECKPOINTTABLE [SCHEMA_NAME].GGS_EVENT_CHECKPOINT GGSCI (hostname) 1> DELETE CHECKPOINTTABLE [SCHEMA_NAME].GGS_CHECKPOINT GGSCI (hostname) 1> shell del <ggsdir>\dirprm\*env* <ggsdir>\dirprm\*def* <ggsdir>\dirrpt\* <ggsdir>\dirdat\enva\* <ggsdir>\dirdat\envb\* Remove all processes and trail files on environment A: Sample: GGSCI (hostname) 1> dblogin userid USER password "Password" GGSCI (hostname) 1> stop * GGSCI (hostname) 1> delete * -- hit 'y' when Prompted for ny GGSCI (hostname) 1> DELETE TRACETABLE [SCHEMA_NAME].GGS_EVENT_TRACE GGSCI (hostname) 1> DELETE CHECKPOINTTABLE [SCHEMA_NAME].GGS_EVENT_CHECKPOINT GGSCI (hostname) 1> shell del <ggsdir>\dirprm\*env* <ggsdir>\dirprm\*def* <ggsdir>\dirrpt\* <ggsdir>\dirdat\enva\* <ggsdir>\dirdat\envb\* 27. To setup for replication switch, mark environment B as the source update c_repos_zdt_status set REPLICATION_TARGET_IND = 0; commit; 28. On environment B, remove history from ZDT event queue delete from C_REPOS_ZDT_EVENT_QUEUE; delete from C_REPOS_ZDT_REPLICAT_EXCEPTION; update C_REPOS_ZDT_ENV_STATE set state = NULL, state_ts = NULL, state_desc = NULL, updated_by=null, update_date=null; drop table GGS_EVENT_CHECKPOINT; drop table GGS_EVENT_TRACE; drop table GGS_CHECKPOINT; commit; Informatica MDM Hub Zero Downtime (ZDT) User Guide 14

21 29. Set ACTIVE_UPGRADE_IND to 0 in environment B update C_REPOS_ZDT_STATUS set ACTIVE_UPGRADE_IND = 0; BEGIN cmxzdt.v_zdt_ind:= -1; END; commit; 30. Configure sequences for environment B (the new source) to be even exec cmxzdt.configure_sequences; 31. Deploy and start event queue on environment B BEGIN CMXZDT.CONFIGURE_GGS_EVENT_REPLICAT(CMXZDT.zdt_local); CMXZDT.CONFIGURE_GGS_EVENT_EXTRACT(CMXZDT.zdt_local); CMXZDT.START_EVENT_QUEUE(out_error_message => out_error_msg, out_return_code => out_return_code); END; 32. Deploy new replication baseline parameter files from environment B to environment A BEGIN CMXZDT.CONFIGURE_GGS_EXTRACT(CMXZDT.zdt_local); END; 15 Informatica MDM Hub Zero Downtime (ZDT) User Guide

22 33. Start extract and pump on environment B (now the source) begin cmxzdt.start_replication_extract(in_env_type => cmxzdt.zdt_local, out_error_message => out_error_msg, out_return_code => out_return_code); end; 34. Get current SCN from environment B SQL-CMX_ORS_B> select current_scn from v$database; CURRENT_SCN Export environment B using Data Pump with the SCN just recorded Sample: C:\> expdp ors_namepass@tnsname DIRECTORY=DUMP_DIR DUMPFILE=mrm_backup_envb_after_upgrade.dmp LOGFILE=mrm_backup_after_upgrade.log PARALLEL=8 job_name=export_after_upgrade flashback_scn= Note: In this step RMAN backup could be used as an alternative. 36. Resume batch jobs in environment B Informatica MDM Hub Zero Downtime (ZDT) User Guide 16

23 Remaining Steps Invoked from Environment A In order to prepare environment A as the new target, the following steps are initiated from environment A. 37. (before import) Drop and create environment A Close all the connections (sqlplus, toad, application server) connected to A and drop the schema A. Drop schema A - using system user (sqlplus systempassword@tnsname) SQL> drop user enva cascade; Create schema A - using system user (sqlplus systempassword@tnsname) -- supply the schema name as A Recreate ORS from the export of environment B Sample: C:\> impdp ors_namepass@tnsname DUMPFILE=export_dir: mrm_backup_envb_after_upgrade.dmp LOGFILE=export_dir: mrm_restore_from_envb.log CONTENT=ALL REMAP_SCHEMA=fromuser:touser PARALLEL=8 job_name=restore_envb Note: In this step RMAN duplicate could also be used as an alternative. After the database is duplicated, the SCN to be used to start replication can be obtained from the alert.log of the line: RESETLOGS after incomplete recovery UNTIL CHANGE (after import) Re-compile the packages, stored procedures, and views Sample calls: a) Using system user (sqlplus need to supply TNS name, schema name, schema password, GGS directory need to supply ORS name. b) Using cmx_ors user 17 Informatica MDM Hub Zero Downtime (ZDT) User Guide

24 39. Restore ZDT status for environment A (the new target) Initial settings use disable batch and disable writeable SIF API. delete from c_repos_zdt_status; insert into C_REPOS_ZDT_STATUS (REPLICATION_TARGET_IND, ACTIVE_UPGRADE_IND, CREATOR, CREATE_DATE, GGS_HOME_PATH, REPLICAT_NUMBER, TRAIL_FILE_SIZE, DISCARD_FILE_SIZE, ACCEPTABLE_LAG_MINUTES, LAG_DETECTION_TOKEN, LOCAL_ENVIRONMENT_NAME, LOCAL_SCHEMA_NAME, LOCAL_TRAIL_PATH, PUMP_RMTHOST, PUMP_MGRPORT, REMOTE_TRAIL_PATH, REMOTE_ENVIRONMENT_NAME, REMOTE_SCHEMA_NAME, REGULAR_STREAM_ID, EVENT_QUEUE_ID, EXTRACT_PREFIX, REPLICAT_PREFIX, BATCH_DISABLED_IND, DEFAULT_TIMEOUT_MINUTES, ROWID_ZDT_STATUS, WRITE_SIF_API_DISABLED_IND ) Values (1, 0, 'MRM Installer', sysdate, 'C:\GGS', 1, 10, 10, 5, 'LAG_TOKEN_SRC', 'ENVA', 'cmx_ors_a', 'C:\GGS\dirdat\enva\', 'enva_hostname', 9999, 'C:\GGS\dirdat\envb\', 'ENVB', 'cmx_ors_b', 'C', 'Q', 'E','R', 1, 40, '1 ', 1 ); COMMIT; 40. On environment A, clean C_REPOS_ZDT_ENV_STATE table and history info update C_REPOS_ZDT_ENV_STATE set state = NULL, state_ts = NULL, state_desc = NULL, updated_by=null, update_date=null; delete from C_REPOS_ZDT_EVENT_QUEUE; delete from C_REPOS_ZDT_REPLICAT_EXCEPTION; drop table GGS_EVENT_CHECKPOINT; drop table GGS_EVENT_TRACE; drop table GGS_CHECKPOINT; commit; Informatica MDM Hub Zero Downtime (ZDT) User Guide 18

25 41. Configure sequences on environment A to be odd now exec cmxzdt.configure_sequences; 42. Check environment specific settings on environment A Settings such app server, debug log etc. may need to be reset now that schema is residing on new environment A. 43. Deploy and start event queue on environment A (new target) BEGIN CMXZDT.CONFIGURE_GGS_EVENT_REPLICAT(CMXZDT.zdt_local); CMXZDT.CONFIGURE_GGS_EVENT_EXTRACT(CMXZDT.zdt_local); CMXZDT.START_EVENT_QUEUE(out_error_message => out_error_msg, out_return_code => out_return_code); END; 44. Deploy new replication baseline parameter files from environment A to environment B BEGIN CMXZDT.CONFIGURE_GGS_REPLICAT(CMXZDT.zdt_local); END; 45. Start replication replay on environment A begin cmxzdt.start_replication_replay(in_env_type => cmxzdt.zdt_local, out_error_message => out_error_msg, out_return_code => out_return_code,in_after_csn => SCN_FROM_STEP 34); end; The upgrade is now complete. 19 Informatica MDM Hub Zero Downtime (ZDT) User Guide

26 Tips and Troubleshooting The following are things to keep in mind when using ZDT in the MDM Hub environment. Registered Backfill Tasks The execution of batch jobs is not allowed in a target replication environment while backfill tasks are registered. This is enforced because of the high likelihood of locking conflicts when backfill batch jobs are running concurrently with regular batch jobs. Once the backfill has completed and the backfill tasks are de-registered, regular execution of batch jobs is enabled. If batch jobs are executed with backfill tasks enabled, the following error will be displayed for the job: "Failed due to existing backfill tasks on the same object. Please clear backfill tasks before proceeding with regular batch jobs for this object." Reset Matches on Target The Reset Match logic is not replicated to the target environment. MET migration will not reset the match table; this must be done via a script. Tokenize backfill does not impact the match table. After a match-related change list is applied, a change must be made to the target match rules in order to trigger Reset Match. New Message Type Enhancement Newly added message features are flexible and able to do GG setup and ZDT schema swing process from one environment to another (either from source or target, though target is preferable). These are the signatures to use the enhancements: Enhancement 1: Updating remote table - Remotely update the tables using this call. Example: Target C_REPOS_ZDT_STATUS.ACTIVE_UPGRADE_IND will set to 1 from source. begin end; cmxzdt.send_event_message(in_type=>cmxzdt.zdt_execute, in_parameters=>'update c_repos_zdt_status set active_upgrade_ind=1' ); Informatica MDM Hub Zero Downtime (ZDT) User Guide 20

27 Enhancement 2: Calling remote stored proc - Generate extract processes and prm files from target using this call. Example: begin end; cmxzdt.send_event_message( in_type=>cmxzdt.zdt_execute, in_parameters=>'begin CMXZDT.CONFIGURE_GGS_EXTRACT(CMXZDT.zdt_local); END;' ); Messaging cannot invoke any logic that uses the messaging recursively. 21 Informatica MDM Hub Zero Downtime (ZDT) User Guide