1. Installation Guide
  2. Known Issues - Resolutions

8 Known Issues - Resolutions

This topic describes about the known issues - resolutions.

Deployment issue oblm-integration-service

Problem

If deploying for oblm-integration-services-8.2.0 fails with below error.

Error

org.flywaydb.core.api.FlywayException: Validate failed: Detected failed migration to version 502.05.1.0.8.2.0.09.502005006.5.0 (LMX TM ACCOUNT VD BAL)

Solution

Check if there are existing records with same value for all the four parameters (ACCOUNT_NUMBER, BRANCH_CODE, CURRENCY_CODE, VALUE_DATE) in table LMX_TM_ACCOUNT_VD_BAL.

The following steps to be performed:
  1. Run the below query to check the existing records for the four parameters.
    SELECT ltavd.* FROM <LMX_SCHEMA>.LMX_TM_ACCOUNT_VD_BAL ltavd INNER 
        JOIN
        (   
          SELECT ACCOUNT_NUMBER, BRANCH_CODE, CURRENCY_CODE, VALUE_DATE   
          FROM OBLMLMX.LMX_TM_ACCOUNT_VD_BAL   
          GROUP BY ACCOUNT_NUMBER, BRANCH_CODE, CURRENCY_CODE, VALUE_DATE   
          HAVING COUNT(*) > 1 
        )t ON ltavd.ACCOUNT_NUMBER = t.ACCOUNT_NUMBER AND ltavd.BRANCH_CODE 
        = t.BRANCH_CODE AND ltavd.CURRENCY_CODE = t.CURRENCY_CODE AND 
        ltavd.VALUE_DATE = t.VALUE_DATE;
  2. Delete the existing records returned from the above query by using below query.
    DELETE FROM <LMX_SCHEMA>.LMX_TM_ACCOUNT_VD_BAL WHERE ID IN ('<Enter ID 1>', '<Enter ID 2>', '<Enter ID 3>', '<Enter ID 4>');
         COMMIT;
  3. Delete the script history instance in the “flyway_schema_history”
    DELETE FROM <LMX_SCHEMA>."flyway_schema_history" WHERE "success" = '0';
        COMMIT;
  4. Restart the server and deploy the oblm-integration services-8.2.0. again.

App Shell login issue – 8.2.0

Problem

If the app shell login fails during the deployment of 8.2.0 artifacts.

Solutions
  1. Check for the following parameters is set in all domains:

    Dspring.cloud.loadbalancer.ribbon.enabled=false

  2. Set the property if not found and restart the domain.

Deployment issue while installing the application using Installer

Datasource Properties Issue
Problem

While deploying the war file fails with below error:

Error

dataSource or dataSourceClassName or jdbcUrl is required

Solutions
  1. If the product and foundation setup are in 2 different VM's, ensure that the syncup between these 2 VM's are performed.
  2. Login to the plato schema and verify the entries for the respective warfile application are correct in the properties table like, jdbcURL, schema name, port etc..,
  3. Check the Hostname and plato related URL in setuserOverrides.sh of product.
  4. Restart the service.
JDBC Issue
Problem

While deploying the war file fails with below error:

Error

jdbc.<<SCHEMA_NAME>

Solutions
The JDBC Issue is encountered due to incorrect password in databag or incorrect entries in the properties table for the war file getting deployed.
  1. Verify the password of the respective schema of the war file being deployed in databag.
  2. In Plato schema, verify the entries of the war file being deployed in the properties table. Check jdbcurl, schema name and port no. are correct.
  3. If required update the same with correct values.
  4. Restart the service.