AnsweredAssumed Answered

Upgrade 12.1 to 13.1 fails after 13.0

Question asked by another_martink on Jun 20, 2013
Latest reply on Feb 10, 2014 by another_martink
Upgrade 12.1 to 13.1 fails after 13.0
What do I do differently to get upgrade fro m13.0 to 13.1 also done?

I've been trying to upgrade 12.1 to 13.1 for some timeand have not got there yet.
I posted in another thread how upgrade first from 12.1 to 13.0 was successful and then failed in 13.0 to 13.1, see
101225418
Nika pointed out that it was due to a bug and showed the workaround.

Now I am back to the problem in running the 13.1 upgrade directly on 12.1

The starting point is

Folders


Clarity - 12.1 installation
Clarity_13 - to be given as the target folder for upgrade
jdk - jdk 6
jdk7 - jdk 7
Old Tomcat - Tomcat 6.026 for 12.1
Tomcat - Tomcat 7.026


When I gave the Clarity folder as the target for the upgrade the install failed in a few minutes.
Therefore I had to Create Clarity_13 for the upgrade.


The install folder only contains the clients and the install.jar because in the upgrade the database already exists,
jdk 7 and Tomcat 7 are alredy installed.

Environmental variables

CLARITY_HOME=D:\Clarity_13
JAVA_HOME=D:\jdk7
NIKU_HOME=D:\Clarity_13

PATH
Path=D:\jdk7\bin;D:\Clarity_13\bin;C:\Windows\system32;...

caches.xml in %NIKU_HOME%\.setup\templates\config

v12.1.1 was dated 6/28/2012
v13.0 was dated 3/22/2011 (from the 13.0 - 13.1 upgrade)

So I copied the older file to ..\Clarity\config

Start the upgrade
jar -xvf install.jar and after unjarring delete install.jar to save space.
Answer all questions
Eg current install Clarity
Target upgrade Clarity_13

The installation in the command window finishes with




[color=#2c95ff][size=4]-----------------------------------------------------
2013-06-19 00:41:04: Finished updating database
-----------------------------------------------------

Trying to override old definition of task java

init:

postupgrade:
Installation Successful - 19-June-2013 00:41:08

BUILD SUCCESSFUL
Total time: 27 minutes 27 seconds
Trying to override old definition of task java

init:

_stop-services:
Trying to override old definition of task java

_stop-service:
service id = beacon
servicecmd = service.bat
No registered service(s) found.
Trying to override old definition of task java

_stop-service:
service id = app
servicecmd = service.bat
[-] Niku Server [app] is already stopped
Trying to override old definition of task java

_stop-service:
service id = nsa
servicecmd = service.bat
[-] Niku System Admin Server [nsa] is already stopped
Trying to override old definition of task java

_stop-service:
service id = bg
servicecmd = service.bat
[-] Niku Background Server [bg] is already stopped
release.exec.result = Result: 1

BUILD FAILED
D:\131_u\gateway.xml:35: The following error occurred while executing this line:

D:\131_u\install.xml:209: The following error occurred while executing this line
:
D:\131_u\install.xml:370: The following error occurred while executing this line
:
D:\131_u\install.xml:396: The following error occurred while executing this line
:
D:\131_u\install.xml:418: The following error occurred while executing this line
:
D:\131_u\install.xml:732: The upgrade step for 13.0.0 failed. Please consult the

D:\131_u\install-packages\13.0.0\upgrade-repack.13.0.0.7032a/in
stall.log for that release package."

Total time: 28 minutes 47 seconds
[size]
[color]

The lines referenced are
[color=#2c95ff][size=4]
gateway.xml:35

<ant antfile="${target.ant.file}" target="${install_target}"/>

install.xml:209

<antcall target="_upgrade"/>


install.xml:370

<if property="proceedWithCaution" value="y" target="_proceed-upgrade"/>


install.xml:396

<foreach list="${release.list}" param="release.package" target="_process-release" inheritAll="true"/>


install.xml:418

<antcall target="_install-release">


install.xml:732

<fail>The upgrade step for ${release.package} failed. Please consult the
${release.package.path}/install.log for that release package."
</fail>
[size]
[color]
which don't really help at all

The end of
D:\131_u\install-packages\13.0.0\upgrade-repack.13.0.0.7032a/install.log
is
[color=#2c95ff][size=4]
6/19/13 12:40 AM (ExecTask) ==========================================
6/19/13 12:40 AM (ExecTask) DBTools Log - Wed Jun 19 00:40:21 EEST 2013
6/19/13 12:40 AM (ExecTask) ==========================================
6/19/13 12:40 AM (ExecTask)
6/19/13 12:40 AM (ExecTask) Command: extract row count
6/19/13 12:40 AM (ExecTask) To URL: jdbc:clarity:sqlserver://W2008:1433;DatabaseName=clarity;InsensitiveResultSetBufferSize=0;ProgramName=Clarity
6/19/13 12:40 AM (ExecTask) As user: niku
6/19/13 12:40 AM (ExecTask) For vendor: mssql
6/19/13 12:41 AM (ExecTask)
6/19/13 12:41 AM (ExecTask) Total time: 0H:0M:42S
6/19/13 12:41 AM (ExecTask)
6/19/13 12:41 AM (ExecTask) -----------------------------------------------------
6/19/13 12:41 AM (ExecTask) 2013-06-19 00:41:04: Finished updating database
6/19/13 12:41 AM (ExecTask) -----------------------------------------------------
6/19/13 12:41 AM (ExecTask)
6/19/13 12:41 AM (Target) Target "installsteps" finished.
6/19/13 12:41 AM (Project) Trying to override old definition of task java
6/19/13 12:41 AM (Target) Target "init" started.
6/19/13 12:41 AM (Target) Target "init" finished.
6/19/13 12:41 AM (Target) Target "postupgrade" started.
6/19/13 12:41 AM (Target) Target "postupgrade" finished.
6/19/13 12:41 AM (Echo) Installation Successful - 19-June-2013 00:41:08
6/19/13 12:41 AM (Target) Target "_install" finished.
6/19/13 12:41 AM (Target) Target "_upgrade" finished.
6/19/13 12:41 AM (Target) Target "install" finished.
[size]
[color]
which is not in line with what was displayed in the command window.


If I look at cmn_install_history in the database



that looks like the db was updated to v.13.0

When I look at the service the niku services are there, no CA Clarity PPM services.

Why did the install stop after an apparently successfull upgrade to 13.0 ?

Manually I would continue by removing the niku services, create new services from the current Clarity folder
and then go to to the newly created ..\131\install-packages\13.1.0
and run the install from there.




Martti K.

Outcomes