2.8.5.6 Configuring Transliteration

This section describes how to configure Transliteration.

Note:

• This section is applicable only when APPLY_TRANSLITERATION flag is set to True and MATCHING_MECHANISM is set to OT.
• There is no additional configuration required for OpenSearch.

Prerequisites: Make sure that JAVAVM is added before loading the jar, class, or any java-related files.

To add JAVAVM:

1. Login to Sys/Admin.
2. Execute the following SQL script.

   SELECT status FROM DBA_REGISTRY
   WHERE comp_id = 'JAVAVM';
   ---O/P
   --- Status
   --- Valid
   SELECT dbms_java.get_jdk_version
   FROM DUAL;
   ---O/P
   ---JDK Version
   ---1.8.0_351

   You can go once you get the corresponding O/P showing JAVAVM is installed.

3. If you are not getting the corresponding O/P, then execute the following SQL script.

   BEGIN
   DBMS_CLOUD_ADMIN.ENABLE_FEATURE(
   feature_name => 'JAVAVM' );
   END;

4. Provide the create procedure permission grant and execute the following grant to the user/ schema(AMLDD).

   GRANT CREATE PROCEDURE TO <DATA_SCHEMA_NAME>

5. To configure transliteration:

   Note:

   Users should execute the following steps in a separate terminal.
   1. Download the Oracle Client zip file.
   2. Unzip the Oracle client zip in a separate folder.

      Note:

      The path where the LINUX.X64_193000_client_home.zip file is unzipped and it is referred to as “ORACLE_CLIENT_PATH”.
   3. Set the ORACLE_HOME.

      Note:

      ORACLE_HOME refers to the path where oracle database client is unzipped.
   4. Navigate to the ORACLE_CLIENT_PATH directory and modify the load java by executing the following command:

      sed -i -e "s|/scratch/app/user/product/19.0.0/ clienthome_1|##ORACLE_CLIENT_PATH##|g" bin/loadjava

   5. To compile the java class with the icu4j plugin, execute the following command:

      ##ORACLE_CLIENT_PATH##/jdk/bin/javac -cp ##ICU4j_PATH##
      ##TRANSLATOR_JAVA_PATH##

      Note:

      ##ICU4j_PATH## refers to path where icu4j jar is placed and ##TRANSLATOR_JAVA_PATH## refers to the path where Translator.java file is placed.

      These files are available in the <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/candidate-selection/utility/transliteration directory.

   6. Navigate to the ORACLE_CLIENT_PATH/bin directory and perform loadjava operation by executing the following command:

      ./loadjava -thin -user <Username>/
      <Password>@<Hostname>:<Port>:<ServiceName> -resolve -verbose -force
      ##ICU4j_PATH## ##TRANSLATOR_CLASS_PATH##

      Note:

      Replace the following placeholder:

      • <Username> specifies the username of the data schema. For example, username of the ER schema or Graph schema.
      • <Username> specifies the username of the data schema. For example: username of the ER schema or Graph schema.
      • <Password> specifies the password of the ER schema or graph schema.
      • <Hostname> specifies the database server’s hostname of the data schema.
      • <Port> specifies the database port.
      • <ServiceName> specifies the service parameter of the database.
      • ##ICU4j_PATH## refers to this <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/ candidate-selection/utility/transliteration/icu4j-72.1.jar path.
      • ##TRANSLATOR_CLASS_PATH## refers to this <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/ candidate-selection/utility/transliteration/Translator.java path.
   7. If you use a Data Schema wallet from the ORACLE_CLIENT_PATH/bin directory, perform loadjava operation by executing the following command.

      ./loadjava -thin -user <Username>/<Password>@##WALLET_ALIAS## -resolve -
      verbose -force ##ICU4j_PATH## ##TRANSLATOR_CLASS_PATH##

      Note:

      This step is optional and Set export TNS_ADMIN=##WALLET_ALIAS_PATH##.