2.2 Installing this Maintenance Level Release

To install this ML release, follow these steps:

Note:

On Oracle Database 19.3, SQL MERGE statements will fail with the error ORA-01792 (maximum number of columns in a table or view is 1000).

To resolve this issue, upgrade the database to Oracle 19c Release Update (RU) 19.18 or later versions.

  1. Login to My Oracle Support (MOS) and download the OFS LRS 8.1.2.11.0 release patches.
    Use the following patch numbers:
    • 39490886 - Liquidity Risk Solution Application Pack Release 8.1.2.11.0
    • 39491028 - Liquidity Risk Solution Data Model Release 8.1.2.11.0
  2. Download the OFS_LRS_8.1.2.11.0_LINUX.zip archive file and copy it to your OFSAA server in Binary mode.
  3. Stop all the OFSAAI services. For more information, see the Stopping Infrastructure Services section in the Oracle Financial Services Liquidity Risk Solution Installation Guide.
  4. Login to the OFSAA server as a non-root user, navigate to the $FIC_HOME directory, and execute the command: chmod -R 775 *
  5. Extract the contents of the 8.1.2.11.0 ML archive file using the following command:

    unzip -a <name of the file to be unzipped>

  6. Update the configuration file params.conf available in the directory: /OFS_LRS_PACK/appsLibConfig/conf/params.conf.
    Following are the input parameters for params.conf file:
    UPLOAD_MODEL= 1
    MODEL_TYPE= 0
  7. Update the params.conf file available in the following directory:

    /OFS_LRS_PACK/params.conf.

    Set the following values:

    WEBSERVER_TYPE=TOMCAT
    WEBSERVER_VERSION=<version of Tomcat>
  8. Navigate to the OFS_LRS_PACK directory and provide execute permission to the ML patch installer script:
    chmod 755 OFSAAIUpdate.sh
  9. Run the installer:
    ./OFSAAIUpdate.sh
  10. Verify that the ML is applied successfully by reviewing the generated log files.
  11. After successful installation of the ML, perform the following steps:
    1. Clear the application cache. Navigate to the following directory depending on the configured web application server and delete the files.
      • Tomcat: <Tomcat installation folder>/work/Catalina/localhost/<Application name>/org/apache/jsp
      • WebLogic: <WebLogic installation location>/domains/<Domain name>/servers/<Server name>/tmp/_WL_user/<Application name>
      • WebSphere: <WebSphere installation directory>/AppServer/profiles/<Profile name>/temp/<Node name>/server1/<Application name>/<.war file name>
    2. Deploy the RPD and Web Catalog file(s)
      1. Take a backup of deployed RPD and catalog files from the OBIEE environment.
      2. Navigate to the $FIC_HOME/OFS_LRM_DASHBOARDS/12.2.1.4.0/datamodel directory which contains the following catalog files:
        • Liquidity_Risk_Management_pack.catalog: $FIC_HOME/OFS_LRM_DASHBOARDS/12.2.1.4.0/content/catalog
        • BNM.catalog: $FIC_HOME/OFS_LRM_LCR_BNM/OFS_LRM_DASHBOARDS/12.2.1.4.0/content/catalog
        • Bank of Thailand.catalog: $FIC_HOME/OFS_LRM_LCR_BOT/OFS_LRM_DASHBOARDS/12.2.1.4.0/content/catalog
        • HKMA.catalog: $FIC_HOME/OFS_LRM_LCR_HKMA/OFS_LRM_DASHBOARDS/12.2.1.4.0/content/catalog
        • RBI.catalog: $FIC_HOME/OFS_LRM_LCR_RBI/OFS_LRM_DASHBOARDS/12.2.1.4.0/content/catalog
        • USFED.catalog: $FIC_HOME/OFS_LRM_LCR_USFED/OFS_LRM_DASHBOARDS/12.2.1.4.0/content/catalog
        • Deposit Insurance.catalog: $FIC_HOME/OFS_LRM_DIC_USFED/OFS_LRM_DASHBOARDS/12.2.1.4.0/content/catalog

          Note:

          Ignore the existing files in $FIC_HOME/OFS_LRM_DASHBOARDS/12.2.1.4.0/content/catalog folder:
          • BNM.catalog
          • Bank of Thailand.catalog
          • HKMA.catalog
          • Deposit Insurance.catalog
          • RBI.catalog
          • USFED.catalog
      3. Modify the connection pool and set the properties.
      4. Any customization performed on the older RPD and Web Catalog files requires to be manually carried over to the newer ones post-deployment.
      5. Clear OBIEE cache, if enabled.

        For more information on deploying RPD and Web Catalog files, see Deploying the application section in Oracle Financial Services Liquidity Risk Solution Installation Guide

  12. Delete the existing EAR or WAR file available in the folder $FIC_HOME/ficweb.
  13. Add umask 0027 in the .profile of the UNIX account which manages web server to ensure restricted access permissions.
  14. Navigate to the web component deployed area. If you are deploying on a fresh environment, then delete the generated .war file. If you are installing in an existing environment, then delete the generated .war file and the folder created along with it.
  15. Generate the application EAR or WAR file and redeploy the application onto your configured web application server. For more information on generating and deploying the EAR or WAR file, see the Post Installation Configurations section in the Oracle Financial Services Liquidity Risk Solution Installation Guide.
  16. Restart all the OFSAAI services. For more information, see the Starting Infrastructure Services section in the Oracle Financial Services Liquidity Risk Solution Installation Guide.