Upgrades/new install of clarity 16.0.3 fails when using JDBC URL under Database in CSA 
search cancel

Upgrades/new install of clarity 16.0.3 fails when using JDBC URL under Database in CSA 

book

Article ID: 247797

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

Upgrades/new install of clarity 16.03 fails to start when using JDBC URL under Database in CSA 
 
STEPS TO REPRODUCE: 

  • Upgrades  (The database connection in prior version setup must be using the JDBC URL) 
  1. Start an upgrade from any supported upgrade path of 16.0.3 

Expected Results: The upgrade should be successful 

Actual Results: The upgrades fails with below error in the install.log

(ExecTask) java.sql.SQLException: Driver:oracle.jdbc.driver.OracleDriver@151335cb returned null for URL:jdbc:clarity:oracle://example.com:1521;SID=CLARITY;

BatchPerformanceWorkaround=true;InsensitiveResultSetBufferSize=0;ServerType=dedicated;supportLinks=true;ConnectionRetryCount=400;ConnectionRetryDelay=3;

  • New Installation 
  1. Configure a database with service name/scan 
  2. Start the installation 
  3. Once the installation is complete Navigate to CSA and fill in the database details 
  4. Deploy and start the app services 

Expected Results: Clarity app services should start successfully 

Actual Results:  Clarity app services fails to start and below error is seen in app ca log 

SYS   2022-08-05 12:29:40,902 [WrapperStartStopAppMain] niku.union (none:none:none:none) Clarity 16.0.3.1009 initializing...
WARN  2022-08-05 12:29:41,016 [WrapperStartStopAppMain] config.TenantConfigurationManager (none:none:none:none) null
WARN  2022-08-05 12:29:41,016 [WrapperStartStopAppMain] config.TenantConfigurationManager (none:none:none:none) Could not verify database connection for Local TenantInstance with id = clarity marking as an invalid configuration.
SYS   2022-08-05 12:29:41,017 [WrapperStartStopAppMain] config.TenantConfigurationManager (none:none:none:none) ==================================================================
SYS   2022-08-05 12:29:41,017 [WrapperStartStopAppMain] config.TenantConfigurationManager (none:none:none:none) ==================================================================
SYS   2022-08-05 12:29:41,017 [WrapperStartStopAppMain] config.TenantConfigurationManager (none:none:none:none) CLARITY
SYS   2022-08-05 12:29:41,017 [WrapperStartStopAppMain] config.TenantConfigurationManager (none:none:none:none) Tenants: TenantInstance: id: clarity
SYS   2022-08-05 12:29:41,018 [WrapperStartStopAppMain] config.TenantConfigurationManager (none:none:none:none) Tenants: TenantInstance: appId: app
SYS   2022-08-05 12:29:41,018 [WrapperStartStopAppMain] config.TenantConfigurationManager (none:none:none:none) Tenants: TenantInstance: bgId: bg
SYS   2022-08-05 12:29:41,018 [WrapperStartStopAppMain] config.TenantConfigurationManager (none:none:none:none) Tenants: TenantInstance: fileDirectory: tenantDirectory
SYS   2022-08-05 12:29:41,018 [WrapperStartStopAppMain] config.TenantConfigurationManager (none:none:none:none) Tenants: TenantInstance: status: invalid
SYS   2022-08-05 12:29:41,029 [WrapperStartStopAppMain] config.TenantConfigurationManager (none:none:none:none) ==================================================================
SYS   2022-08-05 12:29:41,029 [WrapperStartStopAppMain] config.TenantConfigurationManager (none:none:none:none) Tenants for this Application with instance id = app :
SYS   2022-08-05 12:29:41,029 [WrapperStartStopAppMain] config.TenantConfigurationManager (none:none:none:none) ==================================================================
SYS   2022-08-05 12:29:41,029 [WrapperStartStopAppMain] config.TenantConfigurationManager (none:none:none:none) Active Tenants:
SYS   2022-08-05 12:29:41,029 [WrapperStartStopAppMain] config.TenantConfigurationManager (none:none:none:none) ==================================================================
ERROR 2022-08-05 12:29:41,030 [WrapperStartStopAppMain] niku.union (none:none:none:none) Clarity 16.0.3.1009 failed to initialize.
com.niku.union.config.ConfigurationException: The application failed to start because of a database configuration problem.  Please review the application log for specific error information.
        at com.niku.union.config.ConfigurationManager.initAppServerType(ConfigurationManager.java:4426)
        at com.niku.union.config.ConfigurationManager.initAppServerIntern(ConfigurationManager.java:4362)
        at com.niku.union.config.ConfigurationManager.initAppServer(ConfigurationManager.java:4343)
        at com.niku.union.web.WebControlServlet.init(WebControlServlet.java:154)
        at javax.servlet.GenericServlet.init(GenericServlet.java:158)

 

Environment

Release : 16.0.3

Component : Clarity Install and Upgrade

Cause

DE66146 & DE66171

Resolution

  • Updated ISO is updated on the support portal on 1st November, so download the new 16.0.3 ISO file 

 

 

 

 

Additional Information

URL Format for native drivers with different database vendors

  • Oracle: 
    • Oracle URL without Encryption - jdbc:oracle:thin:@//<hostname>:<port>/<service_name> 
    • Oracle URL with Encryption - jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=*****)(PORT=****))(CONNECT_DATA=(SERVICE_NAME=***)(SERVER=dedicated))(SECURITY=(ENCRYPTION_CLIENT=requested)(ENCRYPTION_TYPES_CLIENT=AES256)))
    • Oracle URL with SSL - jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCPS)(HOST=example.com)(PORT=XXXX))(CONNECT_DATA=(SERVICE_NAME=XXXX)(SERVER=dedicated))(CLARITY_PARAMETERS=(javax.net.ssl.trustStore=/opt/keystore)(javax.net.ssl.trustStorePassword=XXX)))
    • Oracle URL Load Balanced between multiple hosts - jdbc:oracle:thin:@(DESCRIPTION=(RETRY_COUNT=20)(RETRY_DELAY=10)(ADDRESS_LIST= (LOAD_BALANCE=ON) (ADDRESS=(PROTOCOL=tcp)(HOST=example.com)(PORT=XXXX)) (ADDRESS=(PROTOCOL=tcp)(HOST=example.com)(PORT=XXXX))) (CONNECT_DATA=(SERVICE_NAME=SERVICENAME)))

 

  • MS SQL Server
    • MSSQL with SSL & Encryption - jdbc:sqlserver://example:1433;DatabaseName=niku;trustServerCertificate=false;encrypt=true;trustStore=c:/foo;trustStorePassword=XXX

 

Important Information: For Customer using SSL in the database parameters 

  1. Before 16.0.3 Clarity used Data Direct Driver and trust store path can be \\ (double backslash) however during upgrade to 16.0.3 backslash are ignored and upgrade fails.
    Workaround: Changing trust store path from \\ (double backslash) to / forward slash in the CSA/Properties.xml can fix the issue. This step needs to be done prior to upgrade those using trust store parameter in the connection properties. 
  2. If the configuration of datasource is like Oracle URL Load Balanced between multiple hosts then Jaspersoft bean connections will not work as Jaspersoft doesn't support rather we recomend to use Oracle Scan to do load balancing 
Powered by Wolken Software