3.1.2 Post Upgrade Steps

This section describes post upgrade steps when you upgrade from CS 8.1.2.6.0 to CS 8.1.2.8.0.

Common for All Use Cases

Configure Conda Environment

To configure conda environment, see the Registering the Conda Environment section.

Graph Use Case

Post-installation Grants for Graph Schema

During the upgrade activity, make sure that the following grants are assigned to the graph schema.
  • Post-installation Grants for BD Graph
    GRANT EXECUTE ON <BD_ATOMIC_SCHEMA>.P_FCC_CS_BD_EXTERNAL_ENTITY TO
<GRAPH_SCHEMA>;
GRANT SELECT ON <BD_ATOMIC_SCHEMA>.FCC_CS_BD_EXTERNAL_ENTITY TO
<GRAPH_SCHEMA>;
GRANT SELECT ON <BD_ATOMIC_SCHEMA>.FCC_CS_BD_DERIVED_GROUP TO
<GRAPH_SCHEMA>;
  • Post-installation Grants for ECM Graph
    GRANT EXECUTE ON <ECM_ATOMIC_SCHEMA>.P_FCC_CS_CM_EXTERNAL_ENTITY TO
<GRAPH_SCHEMA>;
GRANT SELECT ON <ECM_ATOMIC_SCHEMA>.FCC_CS_CM_EXTERNAL_ENTITY TO
<GRAPH_SCHEMA>;
GRANT SELECT ON <ECM_ATOMIC_SCHEMA>.FCC_CS_CM_DERIVED_GROUP TO
<GRAPH_SCHEMA>;
GRANT DELETE ON <ECM_ATOMIC_SCHEMA>.FCC_GRAPH_M_TRXN_VIEWS TO
<GRAPH_SCHEMA>;
  • Post-installation Grants for both BD and ECM Graphs
    GRANT SELECT, INSERT, UPDATE, DELETE ON
<STUDIO_SCHEMA>.FCC_GRAPH_M_TRXN_VIEWS TO <GRAPH_SCHEMA>;
GRANT SELECT ON <STUDIO_SCHEMA>.FCC_M_TABLES TO <GRAPH_SCHEMA>;
GRANT SELECT ON <STUDIO_SCHEMA>.FCC_M_COLUMNS TO <GRAPH_SCHEMA>;
GRANT SELECT ON <STUDIO_SCHEMA>.FCC_M_ATTRIBUTE TO <GRAPH_SCHEMA>;
GRANT SELECT ON <STUDIO_SCHEMA>.FCC_M_ATTRIBUTE_COLUMN_MAP TO
<GRAPH_SCHEMA>;
GRANT SELECT ON <STUDIO_SCHEMA>.FCC_M_COLUMNS_DETAILS TO <GRAPH_SCHEMA>;
GRANT SELECT ON <STUDIO_SCHEMA>.FCC_M_MAP TO <GRAPH_SCHEMA>;
GRANT SELECT ON <STUDIO_SCHEMA>.MMG_GRAPH_SCHEMA TO <GRAPH_SCHEMA>;
GRANT EXECUTE ON SYS.DBMS_LOCK TO <GRAPH_SCHEMA>;
GRANT EXECUTE ON CTXSYS.CTX_DDL TO <GRAPH_SCHEMA>;
GRANT EXECUTE ON CTX_THES TO <GRAPH_SCHEMA>;

Perform Cleanup in the Manual Decisioning UI

To load graph in the Manual Decisioning UI after upgrade:
  1. Log in to Compliance Studio schema.
  2. Truncate the FCC_ER_PARAGRAPH_MANUAL table.

    This will delete all records which contains the paragraph IDs.

Start PGX Service

To start the PGX service:
  1. Navigate to the <PGX_INSTALLATION_PATH>/pgx/pgx-server/bin directory.
  2. Execute the command: ./pgx-server.sh -s.
    The PGX service is up and running.

    Note:

    To verify if PGX service is up, check the logs.

Reinitialize Graph Schema

To reinitialize the graph schema:
  1. Navigate to the <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/ficdb/graphmetadata/ bin directory.
  2. Execute the command: ./InitializeGraphSchema.sh -gw <graph_wallet_alias> -es <ecm_schema_name>.

Changes in Similarity Edges

After upgrade from CS 8.1.2.6.0 to CS 8.1.2.8.0, the following Similarity Edges are not available in the Compliance Studio graph.
  • Cust is similar to Cust
  • Cust is similar to Derived Entity
  • Derived Entity is similar to Derived Entity

Note:

If the above three similarity edge providers are utilized in CS 8.1.2.6.0 graph, these similarity edge providers should be added manually to the graph definition of CS 8.1.2.8.0.
To add Similarity Edge manually:
  1. Log in to Compliance Studio UI.
  2. In the Mega menu, click Modeling and select Graphs.
  3. Click FINANCIAL_CRIME_GLOBAL_GRAPH and click on the Node to create a relationship between them.

    The Edge Details pane is displayed.

  4. Enter Edge name in the Logical Name field.
  5. Enter Edge description in the Logical Description field.
  6. Enable Is Similarity Edge in the Edge Modeler Attributes section to add the pre-defined set of attributes available in the edge.
  7. In Manage Pipeline(s), click Attach drop-down list and select Match Rules.
  8. Click OK. The new edge will be created and added to the respective nodes.

Entity Resolution Use Case

Customization in Entity Resolution

If any customization is applied before the upgrade, then re-check and evaluate whether these changes are still in place after the upgrade. If changes are not available, re-apply the customization wherever required.

Out-of-the-box rules should not be edited for customizations. If there are any customizations, create a copy of out-of-the-box pipeline definitions to apply any customizations otherwise the customizations will not persist when upgraded.

If out-of-the-box pipeline definitions are modified for any customizations, follow these steps to preserve the customizations:
  1. Before upgrade, create a copy of the modified/customized pipeline definitions.
  2. Merge the customizations into upgraded out-of-the-box pipeline definitions appropriately after the successful upgrade of Compliance Studio 8.1.2.8.0.

    For any clarifications, contact My Oracle Support (MOS).

Upload Data Model

To upload the data model, see the Uploading FSDF section.

Upgrade Steps for Entity Resolution

Note:

  • This section is applicable only when Entity Resolution batches are executed in the previous version of the Compliance Studio and upgrading from MATCHING_MECHANISM = OS in CS 8.1.2.6.0 to MATCHING_MECHANISM = OS in CS 8.1.2.8.0.
  • If you are upgrading from MATCHING_MECHANISM = OS in CS 8.1.2.6.0 to MATCHING_MECHANISM = OT in CS 8.1.2.8.0, then contact My Oracle Support (MOS).

Upgrade Metadata from CS 8.1.2.7.0

To update metadata schema:
  1. Navigate to <COMPLIANCE_STUDIO_INSTALLATION_PATH>/ficdb/upgrade/8.1.2.7.0/ UpgradeMetaSchema.
  2. Log in to metadata schema.

    Note:

    Add the customized columns in C_CREATE_FULL_TABLE_QUERY.sql before executing the script as per the match rule.
  3. Execute the C_CREATE_FULL_TABLE_QUERY.sql script.

    This script will create the full table in the C_CREATE_FULL_TABLE_QUERY column in the FCC_STUDIO_ER_QUERIES table.

  4. Add the following scripts in the V_MAKE_TABLE_QUERIES column in the FCC_STUDIO_ER_QUERIES table. 
    DECLARE V_EXISTS NUMBER;
BEGIN
SELECT COUNT (1) INTO V_EXISTS FROM USER_INDEXES WHERE
TABLE_NAME = 'FCC_ER_FULL' AND INDEX_NAME =
'FCC_ER_FULL_CONCAT_NAME_IND';
IF V_EXISTS >0 THEN
EXECUTE IMMEDIATE 'DROP INDEX FCC_ER_FULL_CONCAT_NAME_IND ';
END IF;
END;
&&
DECLARE V_EXISTS NUMBER;
BEGIN
SELECT COUNT (1) INTO V_EXISTS FROM USER_INDEXES WHERE
TABLE_NAME = 'FCC_ER_FULL' AND INDEX_NAME = 'IND_UI_SEARCH';
IF V_EXISTS = 0 THEN
EXECUTE IMMEDIATE 'create index IND_UI_SEARCH on
fcc_er_full(CONCAT_NAME)
indextype is ctxsys.context
parameters (''datastore CTXSYS.DEFAULT_DATASTORE LEXER mylex
wordlist kgram SYNC( ON COMMIT)'') parallel 8';
END IF;
END;

    Note:

    Add the customized columns in UPDATE_QUERIES.sql before executing the script as per the match rule.
  5. Execute the UPDATE_QUERIES.sql script.

    This script will create an idx view table in the QUERIES column in the FCC_STUDIO_ER_QUERIES table.

Upgrade ER/FSDF from CS 8.1.2.7.0

To update ER/FSDF schema:
  1. Navigate to <COMPLIANCE_STUDIO_INSTALLATION_PATH>/ficdb/upgrade/8.1.2.7.0/ UpgradeFSDFSchema.
  2. Log in to ER/FSDF schema.
  3. Execute the PGRADE_ER_SCHEMA.sql script.

    This script will add additional text columns for incorporating the date and dob columns in FCC_ER_FULL table.

  4. Execute the DROP_FCC_ER_FULL_CONCAT_NAME_IND.sql script.

    This script will drop FCC_ER_FULL_CONCAT_NAME_IND index from the FCC_ER_FULL table.

    Note:

    • Manual action cannot be performed from Merge and Split Global Entities UI after performing steps mentioned in the <COMPLIANCE_STUDIO_INSTALLATION_PATH>/ficdb/ upgrade/8.1.2.7.0 directory.
    • Manual action can be performed after execution of ER jobs on the next day.

Upgrade ER/FSDF from CS 8.1.2.8.0

To update ER/FSDF schema:
  1. Navigate to <COMPLIANCE_STUDIO_INSTALLATION_PATH>/ficdb/upgrade/8.1.2.8.0/ UpgradeFSDFSchema.
  2. Log in to ER/FSDF schema.
  3. Execute the Update_created_runskey_for_GId.sql script.

    This script will add created runskey value for existing global parties in n_created_run_skey column in the FCC_ER_MAPPING table.

Interpreters

After upgrade, you can download the supported version for spark and pyspark interpreters.

Note:

The supported version for spark and pyspark interpreters is 3.0.3 and above.

Upgrade Steps for Scenario Conversion Utility

For upgrade steps, see the Using Scenario Conversion Utility for ASC section in the OFS Compliance Studio Administration and Configuration Guide.