AnsweredAssumed Answered

Upgrade to 13.1 fails - invalid database connection for local tenant

Question asked by another_martink on Jun 16, 2013
Latest reply on Jul 9, 2013 by Nika_Hadzhikidi
I've been trying to upgrade v12.1.1 to 13.1 without success.

The First three attemps were fresh upgrades from a working v.12.1.1 .
I had both jdk 6 and 7, Tomcat folder given in install to version 7.

Then I made an upgrade to v13.0 which did not go smoothly, but eventually I got upgraded v13.0 working as I should expect.
No customization that I know of to the java libs and no classpath environmental variable set.
Note that the jdk and Tomcat were the same versions for v13.0 and v12.1.3

Tried to upgrade to v13.1 and that failed.

When running the install jdk 7 was installed and java_home was pointing to that and Tomcat 7 was unziped and its folder was given when the installer asked.

The Build finished but the update failed.
Going in to CSA the Install status was in incomplete and the preupgrade was Installed but db and from there on needed upgrade.

Installing database from the Install and Overview resulted in error in admin log

6/16/13 12:18 PM (admin) Command: install database schema from driver file
6/16/13 12:18 PM (admin) To URL: jdbc:clarity:sqlserver://W2008:1433;DatabaseName=clarity;InsensitiveResultSetBufferSize=0;ProgramName=Clarity
6/16/13 12:18 PM (admin) As user: niku
6/16/13 12:18 PM (admin) For vendor: mssql
6/16/13 12:18 PM (admin) Previous schema directory: D:\Clarity\upgrade\infrastructure\previousSchema
6/16/13 12:18 PM (admin) Option: filtering on type "^((?!(?:pre|post)-upgrade).)*$"
6/16/13 12:18 PM (admin) Option: -updateHistory=false - update history will not be recorded for this session.
6/16/13 12:18 PM (admin) Loading DBDriver file: D:\Clarity\upgrade\projmgr\schema\driver.xml
6/16/13 12:18 PM (admin) Loading DBDriver file: D:\Clarity\upgrade\projmgr\schema\driver.xml
6/16/13 12:18 PM (admin) Current database version is projmgr_20120817_0528
6/16/13 12:18 PM (admin) DBDriver for projmgr_20120817_0528
6/16/13 12:18 PM (admin) Resume installation of DBDriver ...
6/16/13 12:18 PM (admin) Current database version is projmgr_20111204_1616
6/16/13 12:18 PM (admin) Note: Foreign Keys have been disabled
6/16/13 12:18 PM (admin) Note: Foreign Keys and Triggers have been enabled
6/16/13 12:18 PM (admin) DBDriver successfully installed!
6/16/13 12:18 PM (admin) Total time: 0H:0M:2S
6/16/13 12:18 PM (admin) Updating schema for component = calendar
6/16/13 12:18 PM (admin) Updating schema for component = uif
6/16/13 12:18 PM (admin) Updating schema for component = nsa
6/16/13 12:18 PM (admin) Calling auditTrailReEnableUpgrade
6/16/13 12:18 PM (admin) Component = database i18n resource files are applied during the schema update
6/16/13 12:18 PM (admin) No i18n resource files found for component = infrastructure
6/16/13 12:18 PM (admin) Component = ppm i18n resource files are applied during the schema update
6/16/13 12:18 PM (admin) No i18n resource files found for component = nmc
6/16/13 12:18 PM (admin) No i18n resource files found for component = njs
6/16/13 12:18 PM (admin) No i18n resource files found for component = revmgr
6/16/13 12:18 PM (admin) No i18n resource files found for component = reporting
6/16/13 12:18 PM (admin) No i18n resource files found for component = projmgr
6/16/13 12:18 PM (admin) No i18n resource files found for component = calendar
6/16/13 12:18 PM (admin) No i18n resource files found for component = uif
6/16/13 12:18 PM (admin) No i18n resource files found for component = nsa
6/16/13 12:18 PM (admin) Updating xogseeddata for component = database
6/16/13 12:18 PM (admin)
Applying lookup_autosuggest_corrections.xml
6/16/13 12:18 PM (admin)
Applying OBJECT_ACTION_MENU_ITEM_LOOKUPS.xml
6/16/13 12:18 PM (admin)
Applying platform_lookups.xml
6/16/13 12:19 PM (admin)
Applying XOG_ACCESS_RIGHTS.xml
6/16/13 12:19 PM (admin) Error Applying XOG: null
6/16/13 12:19 PM (admin) java.lang.NullPointerException
6/16/13 12:19 PM (admin)
at com.niku.security.service.AuthenticationService.removeSessionCaches(AuthenticationService.java:960)
6/16/13 12:19 PM (admin)
at com.niku.security.service.AuthenticationService.delete(AuthenticationService.java:231)
6/16/13 12:19 PM (admin)
at com.niku.xog.client.XOGAdminClient.processFileDescriptors(XOGAdminClient.java:793)
6/16/13 12:19 PM (admin)
at com.niku.xog.client.XOGAdminClient.execute(XOGAdminClient.java:437)
6/16/13 12:19 PM (admin)
at com.niku.xog.client.XOGAdminClient.main(XOGAdminClient.java:221)
6/16/13 12:19 PM (admin) ERROR: Upgrade failed for tenant
6/16/13 12:19 PM (admin) ==========================================
6/16/13 12:19 PM (admin) DBTools Log - Sun Jun 16 12:19:53 EEST 2013
6/16/13 12:19 PM (admin) ==========================================
6/16/13 12:19 PM (admin) Command: extract row count
6/16/13 12:19 PM (admin) To URL: jdbc:clarity:sqlserver://W2008:1433;DatabaseName=clarity;InsensitiveResultSetBufferSize=0;ProgramName=Clarity
6/16/13 12:19 PM (admin) As user: niku
6/16/13 12:19 PM (admin) For vendor: mssql
6/16/13 12:20 PM (admin) Total time: 0H:0M:49S
6/16/13 12:20 PM (admin) -----------------------------------------------------
6/16/13 12:20 PM (admin) 2013-06-16 12:20:42: Finished updating database
6/16/13 12:20 PM (admin) -----------------------------------------------------
Jun 16, 2013 12:20:42 PM Error executing command: db -javaHome D:\jdk7\jre core-upgrade
D:\Clarity\.setup\scripts\db.xml:1662: The following error occurred while executing this line:
D:\Clarity\.setup\scripts\db.xml:1595: The following error occurred while executing this line:
D:\Clarity\.setup\scripts\db.xml:1608: The following error occurred while executing this line:
D:\Clarity\.setup\scripts\db.xml:1689: The following error occurred while executing this line:

at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:551)
D:\Clarity\.setup\scripts\db.xml:1895: ERROR: Upgrade failed. Please review the upgrade logs for details.

The same error was in install.log earlier

nsa-ca.log has
WARN 2013-06-16 19:06:53,844 [Config Monitor] config.TenantConfigurationManager (none:none:none:none) Found invalid database connection for local tenant clarity

The connection details were not changed since v13.0 and the database shows as available in CSA. Though the healthcheck gives all the details of the database but says valid=false

In other threads the solutions for the problems with the new v13.1 installed have been pointed to memory parameters and tomcat.

I did not change the memory parameters for install and tomcat was unzipped as before and I am not sure if those or anything java related to to the database connection though it is a java command that failed.

What might be wrong?

Martti K.

Outcomes