Upgrade to CA Spectrm R10++ from R9.3/R9.4 will result in broken OC-server install

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

When upgrading a CA Spectrum R9.3.* (or R9.4.*) Installation to CA Spectrum R10(or R10.1) this fails (unsuccessful) and appears to be not recoverable anymore. This was seen for CA Spectrum upgrade on Windows platform. Postinstall logs is showing mysql failure/error.

Environment:
CA Spectrum R9.3.* or R9.4.* upgade on Windows server hosts by apply CA Spectrum R10 or R10.1
Cause:

CA Spectrum OneClick Server memory configuration customization parameter is affecting the CA Spectrum upgrade processing causing the OneClick-Tomcat server start to fail loading Java runtime. Subsequential upgrade-processing steps then fail. 

One symptom of this is, that the CA Spectrum Mysql Database server - service entry - under Windows Services is not present anymore. But you may find a "mysqld" only service which is located in the CA Spectrum install directory. 

Resolution:

Background for this problem appears to be a failure to save the re-configured OneClick-Server Webserver memory setting. This is saved to file $SPECROOT/custom/common/config/tomcat-server-config.xml - and may NOT cover a trailing "M" for the -Xmx memory setting. 

Here Samples with value "6144" (once you had enabled 64bit Java operation for the CA Spectrum Oneclick server):

  -Xmx6144    (is incorrect)

  -Xmx6144M    (is correct)

The -Xmx parameter will be passed to the loaded Java runtime - to specify the available memory. Doing this with 6144 only results in 6144k of memory which does not allow Java being loaded within Tomcat. The java runtime logfile (jvm.log) will claim about too less memory. For the Windows OC-server implementation the startup file is ./tomcat/bin/OneClickService.conf - which is looking fine covering the "M". 

The upgrade processing will not take the OneClickService.conf file/content - as this file is rebuild per each OC-server reconfiguration step. So the processing will take Xmx parameter from tomcat-server-config.xml - which is incorrect. 

Editing tomcat-server-config.xml parameter to correct "-Xmx6144M" will allow successful upgrade processing.

Additional Information:

In case the upgrade was already done and had failed the broken context does not allow to re-apply the same release again to correct this symptom. You have to restore the original installation files and then to correct the ./custom/common/config/tomcat-server-config.xml file - or to fully remove this file.