Following my previous post, I did hit a problem whereby TDI v7 didn't appear to update correctly.
During the update process, which I performed using the command: -
cd /opt/IBM/TDI/V7.0/bin
./applyUpdates.sh -update /tmp/TDI/7.0.0-TIV-TDI-FP0005/Fixpack.zip
I did see an exception: -
CTGDKO023I Applying fix 'TDI-7.0-FP0001' using backup directory '/opt/IBM/TDI/V7.0/maintenance/BACKUP/TDI-7.0-FP0001'.
CTGDKO027I Updating SERVER.
CTGDKO009E Error while executing an operating system command. An exception occurred: /opt/IBM/TDI/V7.0/bin/tdimiggbl.sh: not found
CTGDKO027I Updating CE.
which, at the time, I ignored.
This was a bad move :-)
What I should have done is read this Technote (1391717): -
applyUpdates process fails
which directs one to replace this JAR file: -
/opt/IBM/TDI/V7.0/maintenance/UpdateInstaller.jar
and then re-run the fix pack installation: -
./applyUpdates.sh -update /tmp/TDI/7.0.0-TIV-TDI-FP0005/TDI-7.0-FP0005.zip
However, I then hit another issue;
CTGDKO032E The level of the current installation is '7.0.0.5'. The level must be between '7.0.0.0' and '7.0.0.4' to apply this fix.
Therefore, I realised that I had to first roll back from 7.0.0.5 to 7.0.0.0 before re-applying the fixpack: -
./applyUpdates.sh -rollback
./applyUpdates.sh -update /tmp/TDI/7.0.0-TIV-TDI-FP0005/TDI-7.0-FP0005.zip
Having done this, the updates installed as expected.
Geeking in technology since 1985, with IBM Development, focused upon Docker and Kubernetes on the IBM Z LinuxONE platform In the words of Dr Cathy Ryan, "If you don't write it down, it never happened". To paraphrase one of my clients, "Every day is a school day". I do, I learn, I share. The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions. Remember, YMMV
Subscribe to:
Post Comments (Atom)
TIL - read-only variables in Linux
A co-worker was seeing an exception: - line 8: TMOUT: readonly variable when trying to SCP a file from a remote Linux box. I did some digg...
-
After an unscheduled reboot of the VMs that host my K8s cluster, I was struggling to work out why the kubelet wasn't starting properly...
-
I hit a wee snag earlier today, whilst attempting to unpack some IBM software on my NAS. Being a command-line junkie, I'd SSH'd into...
-
I've just spent ~1 hour trying to get a pair of Powerline adapters to .... pair. This involved pressing a "Pair" button on one...
No comments:
Post a Comment