Clarity

I have installed Clarity 13.2 (Windows, SQL Server) using an existing database from another environment.

After installing, configuring database tab in CSA (it did work), and also checking ODBC configuration (working properly as well),

Clarity application didn't work.

Checking CSA again, I found the message "Installation incomplete. (...) Database not connected." in CSA Installation overview page.

Checking app-ca log file, I found these errors:

SYS   2014-08-20 15:30:30,900 [localhost-startStop-1] niku.union (none:none:none:none) Clarity 13.2.0.472 initializing...

WARN  2014-08-20 15:30:31,353 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) [CA Clarity][SQLServer JDBC Driver][SQLServer]Invalid object name 'CMN_INSTALL_HISTORY'.

WARN  2014-08-20 15:30:31,353 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Could not verify database connection for Local TenantInstance with id = clarity marking as an invalid configuration.

SYS   2014-08-20 15:30:31,353 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) ==================================================================

SYS   2014-08-20 15:30:31,353 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) ==================================================================

SYS   2014-08-20 15:30:31,353 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) CLARITY

SYS   2014-08-20 15:30:31,353 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Tenants: TenantInstance: id: clarity

SYS   2014-08-20 15:30:31,353 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Tenants: TenantInstance: appId: app

SYS   2014-08-20 15:30:31,353 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Tenants: TenantInstance: bgId: bg

SYS   2014-08-20 15:30:31,353 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Tenants: TenantInstance: fileDirectory: tenantDirectory

SYS   2014-08-20 15:30:31,353 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Tenants: TenantInstance: status: invalid

SYS   2014-08-20 15:30:31,353 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Properties/Database: id: clarity

SYS   2014-08-20 15:30:31,353 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Properties/Database: serviceId: niku

SYS   2014-08-20 15:30:31,353 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Properties/Database: driver: com.ca.clarity.jdbc.sqlserver.SQLServerDriver

SYS   2014-08-20 15:30:31,353 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Properties/Database: url: jdbc:clarity:sqlserver://RSQLHM:1433;DatabaseName=niku;InsensitiveResultSetBufferSize=0;ProgramName=Clarity

SYS   2014-08-20 15:30:31,353 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Properties/Database: username: usrhmclarity

SYS   2014-08-20 15:30:31,368 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Properties/Database: schemaName: niku

SYS   2014-08-20 15:30:31,368 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Properties/Database: serviceName: niku

SYS   2014-08-20 15:30:31,368 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Properties/Database: vendor: mssql

SYS   2014-08-20 15:30:31,368 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Properties/Database: largeIndex: INDX_LARGE

SYS   2014-08-20 15:30:31,368 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Properties/Database: smallIndex: INDX_SMALL

SYS   2014-08-20 15:30:31,368 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Properties/Database: largeTables: USERS_LARGE

SYS   2014-08-20 15:30:31,368 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Properties/Database: smallTables: USERS_SMALL

SYS   2014-08-20 15:30:31,368 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) ==================================================================

SYS   2014-08-20 15:30:31,368 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Tenants for this Application with instance id = app :

SYS   2014-08-20 15:30:31,368 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) ==================================================================

SYS   2014-08-20 15:30:31,368 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) Active Tenants:

SYS   2014-08-20 15:30:31,368 [localhost-startStop-1] config.TenantConfigurationManager (none:none:none:none) ==================================================================

ERROR 2014-08-20 15:30:31,384 [localhost-startStop-1] niku.union (none:none:none:none) Clarity 13.2.0.472 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.verifyDatabaseConnections(ConfigurationManager.java:3838)

  at com.niku.union.config.ConfigurationManager.initAppServerIntern(ConfigurationManager.java:3382)

  at com.niku.union.config.ConfigurationManager.initAppServer(ConfigurationManager.java:3313)

  at com.niku.union.web.WebControlServlet.init(WebControlServlet.java:141)

  at javax.servlet.GenericServlet.init(GenericServlet.java:160)

  at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)

  at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)

  at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)

  at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)

  at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)

  at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)

  at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)

  at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)

  at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)

  at java.util.concurrent.FutureTask.run(FutureTask.java:166)

  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

  at java.lang.Thread.run(Thread.java:722)

ERROR 2014-08-20 16:30:06,564 [http-bio-82-exec-1] filter.RequestTenantIdExtractor (none:none:none:none)

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)

  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

  at org.apache.catalina.filters.AddDefaultCharsetFilter.doFilter(AddDefaultCharsetFilter.java:88)

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

  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

  at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)

  at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)

  at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)

  at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)

  at com.niku.union.web.valves.ErrorPageRedirectValve.invoke(ErrorPageRedirectValve.java:70)

  at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:931)

  at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)

  at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)

  at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)

  at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)

  at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)

  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

  at java.lang.Thread.run(Thread.java:722)

Could you help me with this issue?

Regards,

Pedro Cairo

Check this -

https://communities.ca.com/message/101908290#101908290

NJ

NJ,

I have read that post but, in my case, we are not upgrading and we don't have clusters.

Maybe changing multicast configuration could be the answer, although multicast addresses are all different for the 3 enviroments we have.

SQL Server user is connecting to the database, through ODBC or any other SQL Client.

Even CSA database configuration (in "Database" tab) is working properly.

But installation status in CSA says it is not complete because of an error in database connection.

I hope there's another answer to this problem.

Thank you,

Pedro Cairo

Hi Pedro,

The line in your log which says Invalid object name CMN_INSTALL_HISTORY denotes that its not able to find the table with that name, so it should be a schema issue. Try deleting and recreating the database user (first creating a temp user to assign the niku schema to) and also deleting and recreating the database login.

This is suggested in the thread - RE: Where is the NSA install history stored?

Regards,

Georgy

If you have

Could not verify database connection for Local TenantInstance with id = clarity marking as an invalid configuration.

You won't be able to find any objects in the database.

A work around would be to do the install with the database dump provided with the install files. Then after the successful install switch the database to the replica.

Good morning, everyone.

We discovered the problem with the database connection: database user we used to connect SQL Server did not have db_owner rights.

That's why the connection to the database failed. Once given db_onwer right to the user, everything started working well and properly.

Thank you all for helping me with this issue.

Regards,

Pedro Caetano Cairo