Clarity MSSQL Installation Status shows Incomplete and Not Installed
search cancel

Clarity MSSQL Installation Status shows Incomplete and Not Installed

book

Article ID: 415951

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

In Clarity PPM 16.3.3 CSA there is mismatch of the installation status. The overall installation status appears as "Incomplete". Clicking on the incomplete status shows that Database Installation Status is "Not Installed" Despite having successful connection where Database tab is showing "available"

Noticed from SQL profiler it is queries 'niku' prefix on db queries and we are unable to run SQL statements without the 'niku' suffix. 

Environment

Clarity release 16.3.3

Database: Microsoft SQL Server 2019(Hosted on GCP)

Resolution

Re-ran the steps in Clarity with MSSQL Setup guide

Key point here is that DB name and login user was custom. Reviewed the SQL server DB options and values:


Database Schema Name = niku

The login name can be anything, but the default schema name for the login user must be 
niku. 


Database user roles= db_owner

The database user must be able to alter the Clarity -schema and otherwise own the database.

Validation:

Running the following select statements without the 'niku' prefix when logged in with the Clarity DB login:

select * from cmn_install_history;