AIX not showing the correct oslevel after patching

After patching AIX to 5.3 TL11 SP3 oslevel -r still showed the OS at TL 09 :-

# oslevel -r
# 5300-09

To check what filesets are below the TL you patched to first find all TL levels you have installed :-

# oslevel -r -q
Known Recommended Maintenance Levels
————————————
5300-11
5300-10
5300-09
5300-08
5300-07
5300-06
5300-05
5300-04
5300-03
5300-02
5300-01
5300-00

Next check what filesets are below our highest level e.g. TL11

# oslevel -r -l 5300-11
Fileset                                 Actual Level           Recommended ML
—————————————————————————–
Java5.sdk                               5.0.0.1                5.0.0.235
ifor_ls.html.en_US.base.cli             5.3.7.0                5.3.8.0
#

Here you can see two filesets are at the wrong level. So we need to fix this. Java is a seperate download for AIX you can get it here http://www.ibm.com/developerworks/java/jdk/aix/service.html

Check if you have the 32 or 64 bit version with lslpp -l | grep -i java and download the latest fix – select your highest TL level you have installed when you download. Install using the usual  installp / smiity method.

Re run oslevel -r -l 5300-11
Fileset                                 Actual Level           Recommended ML
—————————————————————————–
ifor_ls.html.en_US.base.cli             5.3.7.0                5.3.8.0

Now only one fileset is below level. A Google shows that there is a bug with the update process for this fileset – simply run the patch process again and it will update to the correct level.

Now oslevel is correct :-

# oslevel -r
5300-11
#

2 thoughts on “AIX not showing the correct oslevel after patching”

  1. I just installed TL11 SP5 on a Dev Server. I had never seen let alone done a TL upgrade before and my oslevel was coming back incorrectly. I figured there was some magic step that I didn’t know about but the google I did found this page and the info about the bug with file ifor_ls.html.en_US.base.cli

    Thank You Very Much my oslevel is now correct. 🙂

  2. I’m glad it sorted you out. It is frustrating when you think it is something you have done and it turns out it was a bug all along.

Leave a Reply

Your email address will not be published. Required fields are marked *