Oracle Financial Services Financial Crime and Compliance Management 6.1 Patch/Hotfix Readme File This document provides late-breaking or other information that supplements the Oracle Financial Services Financial Crime and Compliance Management 6.1 documentation. For information about Oracle Financial Services Software, Inc., visit http://www.oracle.com/industries/financial_services/index.html. --------------------------------------------------------------- Patch 6.1.3.0.0BD Applicable Releases: Oracle Financial Services Financial Crime and Compliance Management 6.1 --------------------------------------------------------------- 1.0 Resolved Issues/Enhancements in Patch 6.1.3.0.0BD --------------------------------------------------------------- 17438694 - UI DISPLAY ISSUES WITH UNUSED WHITE SPACE AND MISSING SCROLL BARS. 13667449 - Updated scenario Reg S Sales to bind and display Account Position records 17444147 - HISTORICAL DATACOPY JOB IS USING A DEPRECATED ANALYZE FOR ANALYZING TABLes --------------------------------------------------------------- 1.1 Known Issues/Enhancements in Patch 6.1.3.0.0BD --------------------------------------------------------------- 17336160 - RUNUTILITY.SH REGISTEREDREPRESENTATIVEPROFILE TAKES A LONG TIME TO RUN NOTE: This Intermediate Release(IR) is cumulative and contains of all BD patches for ECM 6.1 (including 6.1.2.0.0BD) released before this patch. NOTE: This hotfix requires the prior installation of fcm_hotfix_20120504.01 and fccm_20120726.01. NOTE: If the hotfix 6.1.0.1.5(PR_14810694.mantas.sql) has been applied in this environment, please comment the entry of "PR_14810694.mantas.sql" in the 6.1.3.0.0BD.cfg file before running the run_dbbuilder_utility. PATCH CONTENTS The following files are included with this patch/hotfix: 6.1.3.0.0BD.tar.gz (this readme file) The following subsystems are affected by this patch/hotfix: Database Ingestion Manager Patch Installer Services Behavior Detection UPGRADE INSTRUCTIONS The upgrade instructions refer to the following directories: Name Description --------------------------- -------------------------------- Directory containing installed Oracle Behavior Detection Platform components Directory containing the patch tar.gz file To apply this patch/hotfix, follow these instructions: On the Database Server: ------------------------ 1. Change to the /patch_installer directory. 2. Type "patchUtil.sh install" to install the patch. 3. When prompted, provide the complete directory path where the hotfix tar.gz file is located: /6.1.3.0.0BD.tar.gz 4. Edit the db_variables.cfg file located at /database/db_tools/mantas_cfg folder a. Locate the following line in the db_variables.cfg file: patch_util_user=@PATCH_SCHEMA_OWNER@ -- (where @PATCH_SCHEMA_OWNER@ token will be configured with the apppropriate value as per your environment) Add the following sections relevant to ECM Stage 3 installation, if it is not there: -Added for CR 16016443 fatca_user=@FATCA_USER@ ctr_user=@CTR_USER@ kyc_user=@KYC_USER@ rev_user=@REV_USER@ -- Infodom names added for CR 15989064 AMINFODOM=@AM_INFODOM@ CMINFODOM=@CM_INFODOM@ KYCINFODOM=@KYC_INFODOM@ CTRINFODOM=@CTR_INFODOM@ FATCAINFODOM=@FATCA_INFODOM@ -- Segment names added for CR 16016443 AMSEGMENT=@AM_SEGMENT@ CMSEGMENT=@CM_SEGMENT@ KYCSEGMENT=@KYC_SEGMENT@ CTRSEGMENT=@CTR_SEGMENT@ FATCASEGMENT=@FATCA_SEGMENT@ -- new token added for CR 16016443 CONTEXT_NM=@CONTEXT_NAME@ Please subsistute the tokens with the appropriate values relevant to your ECM installation. @FATCA_USER@ - Provide the FATCA user if you have installed FATCA product. @CTR_USER@ - Provide the CTR user if you have installed FATCA product. @KYC_USER@ - Provide the KYC user if you hvae installed KYC product. @REV_USER@ - Provide the config schema user for OFSAAI database. @AM_INFODOM@ - Provide the Alert Management Infodom name as configured in the ECM Stage 3 installation. @CM_INFODOM@ - Provide the Case Management Infodom name as configured in the ECM Stage 3 installation. @KYC_INFODOM@ - Provide the KYC Infodom name as configured for KYC installation. @CTR_INFODOM@ - Provide the CTR Infodom name as configured for CTR installation. @FATCA_INFODOM@ - Provide the FATCA Infodom name as configured for FATCA installation. @AM_SEGMENT@ - Provide the Alert Management Segment name as configured in the ECM Stage 3 installation. @CM_SEGMENT@ - Provide the Case Management Segment name as configured in the ECM Stage 3 installation. @KYC_SEGMENT@ - Provide the KYC Segment name as configured for KYC product @CTR_SEGMENT@ - Provide the CTR Segment name as configured for CTR product. @FATCA_SEGMENT@ - Provide the FATCA Segment name as configured for FATCA product. @CONTEXT_NAME@ - Provide the Context Name for the ECM application. If the above products are not applicable in your installation you can leave the token values as is. Save the above changes to the db_variables.cfg Add the following lines: purge_util_user=@PURGE_USER@ Substitute the @PURGE_USER@ token with the purge utility user name. For example: purge_util_user=purge_util_usr 5. Edit the install.cfg file located at /database/db_tools/mantas_cfg folder a. Locate the following line in the install.cfg file: dbscript.execution.users=(system|business|mantas|market|miner|ingest|report|kdd_altio|kdd|algorithms|case) Replace it with the below line if it is not present already: dbscript.execution.users=(system|business|mantas|market|miner|ingest|report|kdd_altio|kdd|algorithms|case|config|fatca|ctr|kyc) Save the changes. b. Add the following lines in the "ALERT PURGE CONFIGURATION" section:(consult the Purge Utility addendum for more details on what values to set for the below parameters) purge.database.user=@PURGE_DB_USER@ purge.database.password= purge_alert_flag=Y purge_case_flag=Y purge_test_flag=N purge_default_rule_set= purge_threads_no=10 purge_batch_size=5000 purge_limit_matches=Y purge_report_directory= purge_product_version=6.1 If you have already applied ECM 6.1.2.0.0BD, please edit the line below: purge_product_verion=6.1 and replace it with: purge_product_version=6.1 c. Remove the following lines in the "ALERT PURGE CONFIGURATION" section: limit_matches=N purge=Y batch_size=5000 job=null scenario=null # enter dates, with quotes in the following format: # 'DD-MON-YYYY HH24:MI:SS' start_date=null end_date=null alert_status=NW 6. Go to the /database directory and create the following directory structures if the directories are not there: 1. mkdir -p ficdb/script/Config 2. mkdir -p ficdb/script/Atomic 7. To execute the database patch scripts against the business schema, do the following: a. Verify that the variables in the db_variables.cfg file located at /database/db_tools/mantas_cfg are up to date. b. Change to the /database/bus_mkt_schema/delta/oracle subdirectory. c. Run the command ../../../db_tools/bin/run_dbbuilder_utility.sh 6.1.3.0.0BD.cfg d. Provide the business schema and alert management schema password when prompted. Please provide the Case schema for 'AS_CM_USER' , Mantas schema for 'AS_AM_USER' when prompted. e. "Database Builder Utility run successfully" should be displayed at the end of the run. f. Check the /database/db_tools/logs/db_builder.log file for any errors. 8. Run the following commands to encrypt the Purge Utility schema password introduced in this patch. a. Confirm the JAVA_HOME and MANTAS_EXT_DIR properties for the /changePasswords.sh script are set correctly in the backup file for changePasswords.sh script as per the manual Instructions mentioned in the beginning. b. Run /changePasswords.sh purge.database.password and provide the Patch Schema Database password to encrypt the clear text password provided earlier in the installation steps. 9. Please run patchUtil.sh info and patchUtil.sh hist to view the installed patch information as well as the patch installation history. 10. Keep a record of the builds and patches applied to each Mantas server, and the date/time they were applied. 11. Send an email message to mantas_support_us_grp@oracle.com indicating that the patch/hotfix has been applied. On the Ingestion Server: ------------------------ 1. Change to the /patch_installer directory. 2. Type "patchUtil.sh install" to install the patch. 3. When prompted, provide the complete directory path where the hotfix tar.gz file is located: /6.1.3.0.0BD.tar.gz 4. Take a backup of the DataIngest.xml file located at : /ingestion_manager/config directory and make the following changes to the section: a. Locate the following section: Replace the above section with the following: b. Locate the following section in the DataIngest.xml file: Replace it with: c. Locate the following section in the DataIngest.xml file: Replace it with: d. Locate the following section in the DataIngest.xml file: Replace it with: e. Locate the following section in the DataIngest.xml file: Replace it with: f. Locate the following section in the DataIngest.xml file: Replace it with: 5. Edit the DataIngest.xml file (or DataIngestCustom.xml whichever is applicable) in the /ingestion_manager/config folder and add the following lines in the DBUtility section: Please run the runUtility jobs in the following order after applying this patch: runUtility.sh AccountProfileTransaction runUtility.sh AccountProfileBalance runUtility.sh AccountProfileTrade (there is no need to execute runDL.sh) 6. Take a backup of the DataIngestCustom.xml file located at : /ingestion_manager/config directory and make the following changes: Locate the .. tag section. If the section exists add the following line: If the tag does not exist, please add the following section: Save the changes. 7. Edit the DataIngest.xml file in the /ingestion_manager/config folder and add the following lines in the DBUtility section: 8. Take a backup of the DataIngestCustom.xml file located at : /ingestion_manager/config directory and make the following changes: The "UseTaxIDForUnrelatedParty" flag should be set to "true" in the section below if the preprocessor job should mark the back office transactions UNRLTD_PARTY_CD=NULL (as related) if the Tax Identifier is the same and it meet the other conditions as well. This is the default ebhavior of 5.9.0.1. The "UseTaxIDForUnrelatedParty" flag should be set to "false" if the preprocessor job should not set the UNRLTD_PARTY_CD flag based on Tax Identifier. The following step shows how to set the flag to true. Locate the .. tag section. Add the following property: Save the changes. If this property flag is not set in the above section, the flag is taken as true by default. 9a. Upload the following XML files to your PC from the directory /ingestion_manager/informatica/exports: a. m_p3207_ASMS_to_CL_I.XML 9b. To import the updated mapping:m_p3207_ASMS_to_CL_I.XML, follow these steps: a.Open the Informatica Designer and log on to the Informatica repository to be updated. b.Double-click on the MLM_Brokerage_Production folder c. Select Main menu -> repository -> import objects d.Locate the m_p3207_ASMS_to_CL_I.XML mappping file in the directory to which you uploaded it. e.Click on the mappping name, then click on "Add >>" to move the file to the right side of the screen and click on Next. f. If the Conflict Resolution Wizard prompts you to resolve conflicts, check on "Retain Persistant Mapping variables values" as well as "Retain Sequence Generator" options and click Next. Choose "Replace" for each conflict. g. Select Main menu -> repository -> Save 10. Please run patchUtil.sh info and patchUtil.sh hist to view the installed patch information as well as the patch installation history. Refer to the Admin Guide under Chapter 8 - Administrative Utilities for details. 11. Keep a record of the builds and patches applied to each Mantas server, and t e date/time they were applied. 12. Send an email message to mantas_support_us_grp@oracle.com indicating that the patch/hotfix has been applied. If the below said changes are not updated yet, please proceed with the following steps: On the Patch Installer Server: ------------------------------ 1. Change to the /patch_installer directory. 3. When prompted, provide the complete directory path where the hotfix tar.gz file is located: /6.1.3.0.0BD.tar.gz 4. Edit the install.cfg file located at /patch_installer/mantas_cfg and replace the following line: product.subsystem.FCCM=ficweb,ficapp,ficdb,ftpshare Replace it with: product.subsystem.FCCM=ficweb,ficapp,ficdb,ftpshare,OBIEE,AM,alert_management 5 a. Take a backup of the /lib/kddcore.jar file which will be replaced in the next step. 5 b. Copy the kddcore.jar located at patch_installer/temp to / patch_installer/lib directory. 6. Keep a record of the builds and patches applied to each application server, and the date/time they were applied. 7. Send an email message to mantas_support_us_grp@oracle.com indicating that the patch/hotfix has been applied. On the Behavior Detection Server: --------------------------------- 1. Change to the directory. 2. Type "patchUtil.sh install" to install the patch. 3. When prompted, provide the complete directory path where the hotfix tar.gz file is located: /6.1.3.0.0BD.tar.gz 4. Keep a record of the builds and patches applied to each Oracle Mantas server, and the date/time they were applied. 5. Send an email message to mantas_support_us_grp@oracle.com indicating that the patch/hotfix has been applied. On the Services Server: ----------------------- 1. Change to the directory. 2. Type "patchUtil.sh install" to install the patch. 3. When prompted, provide the complete directory path where the hotfix tar.gz file is located: /6.1.3.0.0BD.tar.gz 4. Keep a record of the builds and patches applied to each Oracle Mantas server,and the date/time they were applied. 5. Send an email message to mantas_support_us_grp@oracle.com indicating that the patch/hotfix has been applied. NOTE: This hotfix includes updates to the following files: 6.1.3.0.0BD.xml kddcore.jar 16387388.sql 16511979.business.sql 6.1.3.0.0BD.cfg branch_ctr_updates.business.sql branch_ctr_updates.mantas.sql CR_14702867.business.sql CR_14702867.mantas.sql CR_16430438.market.sql CR_16430438.system.sql CR_16442668.case.sql CR_6.1.2.1.0_metadata.mantas.sql CR_6.1.3_metadata.mantas.sql ctr_updates.business.sql ctr_updates.ingest.sql ctr_updates.mantas.sql delta_mts6.1.2_metadata_b01.sql mi_updates.business.sql mi_updates.mantas.sql mts_ctr_code_translations.sql pfm6.1.2_b01.17202438.mantas.sql pfm6.1.2_b01.17261108.case.sql pfm6.1.2_b01.17263834.mantas.sql plat6.1.2_b01.17263834.business.sql plat6.1.2_b01.17263834.ingest.sql plat6.1.2_b01.17263834.miner.sql PR_13691234.sql PR_13743716.business.sql PR_14810694.mantas.sql PR_16366315.mantas.sql PR_16635984.business.sql PR_17034702.case.sql PR_6.1.2.1.0_17484024.miner.sql PR_6.1.3_17618735.case.sql dbtools.jar kddcore.jar categories.cfg mantas_database_message_lib_en.dat PurgeRules.xsd PurgeRules.xml Account.xml AccountAddress.xml AccountBalance.xml AccountChangeLogSummary.xml AccountPhone.xml AccountProfileBalance.xml AccountProfileTrade.xml AccountProfileTransaction.xml BranchCTRConductor.xml BranchCTRSummary.xml BranchCTRTransaction.xml CTRTransaction.xml CurrencyTransaction.xml Customer.xml CustomerAddress.xml CustomerChangeLogSummary.xml CustomerPhone.xml InvestmentAdvisor.xml InvestmentAdvisorProfile.xml Organization.xml m_p3207_ASMS_to_CL_I.XML dbutility.jar kddcore.jar preprocessor.jar util.jar kddcore.jar ============================== (c) 2013 by Oracle Financial Services Software, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise without the prior written permission of Oracle Financial Services Software, Inc.