Clarity: External Connection for Dynamic query causes the application to become unstable

Document ID : KB000048547
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

A local Clarity application connected to Oracle DB. Configuring the Clarity System Administration (CSA) with an external Microsoft SQL Server (MSSQL) connection and using this reference in a custom lookup definition, the system throws "Unable to process request - Server error" error within the Clarity application and then onwards, doesn't respond to any of the requests given to the server.

The following exception errors are found in the logs:

com.niku.union.config.ConfigurationException: Could not retrieve a valid tenant

at com.niku.union.config.TenantConfigurationManager.getValidLocalTenant(TenantConfigurationManager.java:313)

at com.niku.union.web.filter.RequestTenantIdExtractor.getTenantIdForRequest(RequestTenantIdExtractor.java:211)

at com.niku.union.web.filter.CharsetFilter.doFilter(CharsetFilter.java:55)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)

Additionally -

The system is fetching the values from the external database if it is the same database vendor (ie. Oracle/Oracle). Locally, I'm running Oracle DB for Clarity, and I tried using another Oracle DB as an external database. The system was able to run the NSQL query from the external DB to fetch data and the Clarity application continues to work.

Steps to Reproduce:

  1. Create an external MSSQL Server Connection in Clarity System Administration (CSA) for Clarity v13.2
  2. Create a user-defined table within this MSSQL Server Database Instance
  3. Perform a XOG write action to create a new Clarity user-defined dynamic query lookup definition that references this external database table
  4. Restart Clarity Application and Background Services
  5. Login to Clarity as an administrator user
  6. Administration, Data Administration: Lookups - search for the new dynamic query lookup created through XOG write action
  7. Open the lookup definition and navigate to the 'Browse Window' tab
  8. Click 'Preview' button

Expected Result: A successful connection is established ; no error is generated and application continues to work as expected.

Actual Result: An error message is generated on the page and the system becomes unstable and is not working as expected in other areas.

Solution:

WORKAROUND:

If you want to use an external database connection, use the same database vendor type used for Clarity or add the data into Clarity.

STATUS/RESOLUTION:

Resolved in Clarity 13.2.0 Generic Patch. Reference TEC599354

Resolved in Clarity 13.3.0

Keywords: CLARITYKB, CLRT-72846, clarity13resolved, clarity133resolved