Frank,
We had other occurrences of same error during the checkinstall so I don't need your logs anymore. Here is the solution to this issue:
Error message:
8/3/15 12:52 PM (Target) Target "_output-log-info" started.
8/3/15 12:52 PM (XPath) java.lang.ArrayIndexOutOfBoundsException: 2048
What fails is actually the checkinstall tool that runs before and after upgrades.
The error happens in ant target _output-log-info which exists in another file called check-utils.xml, ending with this:
<target name="_output-log-info">
<if property="check.result.msg" isEmpty="false" >
<override name="result.message" value="${check.result.msg}" />
</if>
<trycatch>
<try>
<!-- CLRT-71023 : catch xerces parsing issue -->
<xpath file="${result.xml.file}">
<apply parent="/results" insert="true" after="true">
<element name="result" overwrite="false">
<attribute name="name" value="${script.name}" />
<attribute name="value" value="${check.result}" />
<element name="resultinfo" >
${result.message}
</element>
</element>
</apply>
</xpath>
</try>
<catch>
<fail>Error preparing the output log. Please run the utility again.</fail>
</catch>
</trycatch>
</target>
Here you’ll see the XPath task definition being called, in order to append some data to the logs. In this version of the check-utils, it’s wrapped with a try/catch block to try and stop the ‘xerces parsing issue’ from causing the upgrade to bail when reading and adding content to the results XML file of the check scripts. All it is trying to do in this case is add a line to that file to say that this script was skipped.
This is given as the ultimate root cause, stated as a rare and possibly freak occurring fault: https://issues.apache.org/jira/browse/XERCESJ-1275
I would suggest that perhaps the easiest way to work around this would be to ensure that the output going into that XML results file is different, so that it doesn’t end up on an exact boundary of 2048 bytes when re-parsing the content and tripping over.
Solution:
1. Open the file $install\checkinstall\scripts\imports\check-utils.xml
2. On line 250 modify the output from:
${result.message}
to
${result.message} ${result.message}
3. Save the file and re-run the upgrade. This should normally resolve the issue with the array output.
Hope this helps.
Kind Regards
Nika Hadzhikidi
CA Technologies
Principal Support Engineer