Professional Documents
Culture Documents
aspx
Advanced Search
Table of Contents
Introduction
Errors faced while installing updates
1. Permission denied
i. In UNIX:
ii. In NT:
7. <<update name>> version <<XX>> is the same or lower than the installed
9. Dependency error
i. SUBROUTINE_CALL_FAIL
iii. Update failed: Failed to get a return code from child process
13. <<ComponentName>> branch <<BranchInfo>> does not match <<product>> branch <<BranchInfo>>
Conclusion:
Introduction:
The purpose of this document is to troubleshoot the errors faced while installing updates using T24Updater tool.
1. Permission denied
i. In UNIX:
Error Message
To resolve this
Error Message
To resolve this
1 of 14 3/28/2015 10:46 AM
How to Troubleshoot Updates installation errors? https://tcsp.temenos.com/HowTo/TroubleshootUpdates.aspx
Error Message
This error message occurs when the JAVA_HOME path is not pointing to jdk's bin.
To resolve this
Set the JAVA_HOME path pointing to jdk\bin's path and run the updater again.
To resolve this
Error message
To resolve this
This error message occurs when the downloaded .zip file is not present inside $HOME/updater/updates directory
To resolve this
Place the downloaded zip file inside $HOME/updater/updates and then execute updater from sh prompt.
To resolve this
and check for the working of gtar using the below command
jsh-->gtar
To resolve this
/storage/JB/temprel/temp.release
2 of 14 3/28/2015 10:46 AM
How to Troubleshoot Updates installation errors? https://tcsp.temenos.com/HowTo/TroubleshootUpdates.aspx
To resolve this
Note: gtar is used by T24Updater tool in UNIX and it is replaced by tar for NT
To resolve this
This problem occurs when the variables JAVA_HOME and T24_HOME is not set in both UNIX and WINDOWS environment.
Also the path of $HOME/updater/bin should be appended to PATH variable (of remote.cmd or .profile).
Note: The JAVA_HOME should point to the standalone java and not the one inside TAFC directory
R09_AC_Overridecodes_2_LINUX_ELF_AS5.tar
R09_AC_Errorcodes_1_LINUX_ELF_AS5.tar
Output Summary:
1 files processed.
Errors/Warnings:
Exiting Updater...
To resolve this
a) a) Need to check for the presence of TEMP.RELEASE record and temp.release directory
TEMP.RELEASE
001 D
002 /glohd/HDareas/INfareas/intstj4/mbdemo/mbdemo.run/temp.release
total 392
/glohd/HDareas/INfareas/intstj4/mbdemo/mbdemo.run/temp.release
3 of 14 3/28/2015 10:46 AM
How to Troubleshoot Updates installation errors? https://tcsp.temenos.com/HowTo/TroubleshootUpdates.aspx
Output Summary:
0 files processed.
Errors/Warnings:
machine.
Exiting Updater...
To resolve this
Set the field T24.SERVER to YES in EB_Browser of EB.COMPONENT application and authorise it as shown below
Output Summary:
0 files processed.
Errors/Warnings:
Exiting Updater...
Error message says that R09_EB_BrowserVersion_11 is already installed in the environment and the same
To resolve this
Since re-installation of same update version is not possible. Hence we should re-generate SysDef.xml file and download updates.
Reason:
To resolve this:
9. Dependency error
Error Message
4 of 14 3/28/2015 10:46 AM
How to Troubleshoot Updates installation errors? https://tcsp.temenos.com/HowTo/TroubleshootUpdates.aspx
To resolve this
Since dependency check is made by the updater tool based on the update.xml file present inside the tar file,
the tool will not install the update if dependency check fails. Hence we should re-generate SysDef.xml file and download updates.
This problem could occur when the .tar pack present inside the .zip file is removed or renamed.
To resolve this
Set the below variable in your .profile (or remote.cmd), and execute the updater command again
export T24_HOME=$HOME
Error Message:
Solution:
Un-comment the corresponding tag in updater.xml file. In this case, as T24 updates are installed, uncomment the below lines
Note: similarly when Browser / ARC IB, TAFC, TAG updates are installed, their corresponding tag should be
for the exact error message. It could be either SUBROUTINE_CALL_FAIL error message or TOO MANY CHARACTERS.
i. SUBROUTINE_CALL_FAIL
Error Message
R09_CHQ_PaymentStop_1_LINUX_ELF_AS5.tar
R09_CHQ_Issue_1_LINUX_ELF_AS5.tar
R09_AI_ModelBank_1_LINUX_ELF_AS5.tar
R09_ACM_AccountClosure_1_LINUX_ELF_AS5.tar
R09_AC_Overridecodes_2_LINUX_ELF_AS5.tar
R09_AC_Errorcodes_1_LINUX_ELF_AS5.tar
5 of 14 3/28/2015 10:46 AM
How to Troubleshoot Updates installation errors? https://tcsp.temenos.com/HowTo/TroubleshootUpdates.aspx
Output Summary:
1 files processed.
Errors/Warnings:
Exiting Updater...
032
034
038
This error message occurs because the t24lib and t24bin used by T24Updater tool is replaced by itself
To resolve this
Point JBASE_PATH and JBCOBJECTLIST in .profile (or remote.cmd) to a different location other than
Error Message
To resolve this:
Procedure to be followed:
b) Now take a copy of the t24lib and t24bin from bnk.run and place them in run1
c) Edit your .profile/remote.cmd and ensure that JBASE_PATH and JBCOBJECTLIST is pointed to the run1 directory
d) Ensure that VOC and SAVEDLISTS& are created as UD type directory in run1 (to resolve the problem #1 “Unable to open & file“)
6 of 14 3/28/2015 10:46 AM
How to Troubleshoot Updates installation errors? https://tcsp.temenos.com/HowTo/TroubleshootUpdates.aspx
a) Take unzip the downloaded T24Updates<<YYYY-MM-DD-X-nn>>.zip and take the tar file - R09_EB_Upgrade_X_OS.tar
iii. Update failed: Failed to get a return code from child process
Error Screenshot:
&COMO& record
Transferring F.BATCH>LTD/SC.SYS.END.OF.DAY
[24;2H
7 of 14 3/28/2015 10:46 AM
How to Troubleshoot Updates installation errors? https://tcsp.temenos.com/HowTo/TroubleshootUpdates.aspx
EB.RTN.DATE-132
No Records selected
Solution:
The problem occurs when the updater tool transfers SC.SYS.END.OF.DAY record of BATCH application.
This problem is fixed in R09_EB_Updates_1. Hence, install R09_EB_Updates_1 before installing R09_SC_ModelBank_4.
After successful installation of R09_EB_Updates_1, please copy t24lib and t24bin of R09_EB_Updates_1 to
respective folder inside run1 directory, this is because when executing T24Updater tool, the variable JBCOBJECTLIST
points to run1/t24lib, hence the fixed libraries should be copied to run1 directory.
Subroutine: D:\Localhost\r9test\bnk\bnk.run\run1\t24lib\eb_updates\lib0.dll
Executable: D:\Localhost\r9test\bnk\bnk.run\run1\t24bin\eb_updates\T24Version.dll
13. <<ComponentName>> branch <<BranchInfo>> does not match <<product>> branch <<BranchInfo>>
Error message
Input Summary:
T24Updates-2011-7-25-635.zip
R10_FC_libTAFCjbase_6_HPUX_IA64.tar
R10_FC_libTAFCjcf_4_HPUX_IA64.tar
R10_FC_libTAFCjql_4_HPUX_IA64.tar
R10_FC_libTAFCmonitor_1_HPUX_IA64.tar
R10_FC_libTAFCfrmwrk_6_HPUX_IA64.tar
R10_FC_libTAFCjee_2_HPUX_IA64.tar
R10_FC_libTAFCsql_1_HPUX_IA64.tar
R10_FC_libTAFCutil_5_HPUX_IA64.tar
Output Summary:
0 files processed.
Errors/Warnings:
PB201011_HPUX_IA64
Exiting Updater...
$ exit
While trying to install non compatible version of TAFC updates, system will result in “does not match XX branch” error.
To resolve this
This problem will happen when “branch” in versionxml_jbase output and the “major” in jdiag output does not
<ivy-module version="1.0">
<dependencies>
8 of 14 3/28/2015 10:46 AM
How to Troubleshoot Updates installation errors? https://tcsp.temenos.com/HowTo/TroubleshootUpdates.aspx
</dependencies>
</ivy-module>
JEDIFILEPATH : '/t24/cbalive/bnk/bnk.run'
JEDIFILENAME_MD : '/t24/cbalive/bnk/bnk.run/VOC'
JEDIFILENAME_SYSTEM : '/t24/cbalive/bnk/bnk.run/src/SYSTEM'
JBCEMULATE : 'prime'
This does not match with the name of the update (R10_FC_libTAFCutil_5_HPUX_IA64.tar)
Hence need to make sure that non-compatible TAFC updates are not installed in the environment
and the updates are downloaded from TCSP website using the latest SysDef.xml file.
<path>[T24_HOME]/t24bin/eb_updatesrun/T24Version</path>
<installpath>[T24_HOME]</installpath>
<installprogram>[T24_HOME]/t24bin/eb_updates/T24.UPDATE.INSTALLER</installprogram>
</service>
To resolve this
When the updater tool hangs, need to check the presence of T24.UPDATE.INSTALLER binary file
<path>[T24_HOME]/t24bin/eb_updatesrun/T24Version</path>
<installpath>[T24_HOME]</installpath>
<installprogram>[T24_HOME]/t24bin/eb_updatesrun/T24.UPDATE.INSTALLER</installprogram>
</service>
9 of 14 3/28/2015 10:46 AM
How to Troubleshoot Updates installation errors? https://tcsp.temenos.com/HowTo/TroubleshootUpdates.aspx
4) Extract R09_EB_Updates_1_AIX_5.tar
5) Extract R09_EB_Upgrade_6_AIX_5.tar
10 of 14 3/28/2015 10:46 AM
How to Troubleshoot Updates installation errors? https://tcsp.temenos.com/HowTo/TroubleshootUpdates.aspx
8) Modify JBASE_PATH and JBCOBJECTLIST variable in .profile to point $HOME/run1/t24bin and $HOME/run1/t24lib
(where VOC and &SAVEDLISTS& exist with full permission as UD type directory)
11) Uncomment (only) the below tags in updater.xml file (present inside $HOME/updater/config directory,
..
11 of 14 3/28/2015 10:46 AM
How to Troubleshoot Updates installation errors? https://tcsp.temenos.com/HowTo/TroubleshootUpdates.aspx
From the above screenshot it is shown that on following the above procedure,
13) 13) After successful installation of updates, run1 directory can be deleted from bnk.run
Note:
R09_ST_RateParameters_4_SUN_X86.tar
java.lang.NullPointerException
at java.io.FileInputStream.<init>(FileInputStream.java:103)
at com.temenos.upgrader.Upgrader.processDir(Upgrader.java:1150)
at com.temenos.upgrader.Upgrader.loadUpdateXML(Upgrader.java:1025)
at com.temenos.upgrader.Upgrader.doIt(Upgrader.java:299)
at com.temenos.upgrader.Upgrader.main(Upgrader.java:157)
Solution:
This problem would occur if a tar file in the pack does not contain update.xml file.
The java logging should be enabled and the updater should be executed.
Ensure the below modifications are done in the logging.properties file which is found in
*********
handlers= java.util.logging.ConsoleHandler
.level= FINE
java.util.logging.ConsoleHandler.level = FINE
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
*******
After making the above setup, start a new jshell session to enable the changes
On executing the updater with the java logging enabled, the execution would throw NULL POINTER exception
when installing a problematic update. The corresponding problematic update should be recompiled and given to the client.
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.handleEvent(UnmarshallingContext.java:523)
Solution:
The update.xml file of the corresponding update (in this case: R09_FC_libTAFCjbase_3_HPUX_ IA64.tar) is improper.
import java.io.*;
12 of 14 3/28/2015 10:46 AM
How to Troubleshoot Updates installation errors? https://tcsp.temenos.com/HowTo/TroubleshootUpdates.aspx
String s = null;
System.out.println(Variable);
try {
Process p = Runtime.getRuntime().exec("/glotam1/Bankareas/cib-test/bnk/bnk.run/t24bin/eb_updates
/T24Version");
System.out.println(s);
System.out.println(s);
System.exit(0);
catch (IOException e) {
e.printStackTrace();
System.exit(-1);
Note: highlighted line in the java code should be modified to a valid T24Version path.
Solution:
This is bug in java 1.6. This is fixed in java version 1.6 SR6 (and above)
13 of 14 3/28/2015 10:46 AM
How to Troubleshoot Updates installation errors? https://tcsp.temenos.com/HowTo/TroubleshootUpdates.aspx
http://www.ibm.com/developerworks/java/jdk/aix/j664/Java6_64.fixes.html
153743 IZ55981 620700127 600 13/08/2009 N/A /USR/LIB IS PREPENDED TO THE LIBPATH
Output Summary:
28 files processed.
Exiting Updater...
Solution:
Need to append $JAVA_HOME/bin to PATH variable of .profile as shown in the below example
Example:
export
PATH=/DEV2_02/r10test/bnk.run/updater/bin:/usr/vac/bin:$JBCRELEASEDIR/bin:$JAVA_HOME/
bin:$JBCRELEASEDIR/config:$PATH:.:/usr/local/bin:$HOME/globuspatchbin:$HOME/bin:$HOME
/t24bin:/usr/ccs/bin:/usr/ucb:/usr/aix/bin:$HOME/t24/eb_interface:/usr/bin/gtar
javax.xml.bind.UnmarshalException
at
javax.xml.bind.helpers.AbstractUnmarshallerImpl.createUnmarshalException(AbstractUnmarshallerImpl.java:315)
at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.createUnmarshalException(UnmarshallerImpl.java:476)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:198)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:167)
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:137)
There could be a special character (non UTF8 character) present inside update.xml file of the corresponding tar file. In this case,
Conclusion:
The procedures suggested in the document will ensure that the errors mentioned in the document will be resolved.
After installation of updates, all the INAU files, which are released in updates installation should be authorised.
If CONVERSION.DETAILS records are released, it should be authorised and verified, so that the corresponding data conversion is done.
14 of 14 3/28/2015 10:46 AM