Aix version 4.3.0 not 4.3.3

[jie]

Question we just migrated our operating system from 4.21 to 4.3.3 unfortunately after migration we run oslevel and it gave us 4.3.0 not 4.3.3 . . .

what could be the cause of of this? Because we need to install our new apllication and our consultant told us that we need to be in the right oslevel ..

what could be a solution for this how can we correct this to the right oslevel ..

Thanks in advance ..

 

[victorv]

hi,

4.2.1 read

V.R.M : Version . Release . Modification

- To upgrade Version and/or Realease, 325->420 or 421->433
you have to boot from CDRom and perform
a "Migration Installation"

- To upgrade Modification ( 430->433 or 432->433 )
you have to insert CDROM with machine running and
perform a "smitty update_all"

- To change Maintenance Level ( another set of ptf
that don't change OS functions and feautures, but
correct bugs ( you can see them in 4.3.3.0 -> 4.3.3.5
giving a lslpp -L ) use again "smitty update_all"



how have you passed from 4.2.x to 4.3.x ?

bye

 

[usige]

oslevel just checks to see if certain files are at a specific level.

First run:

instfix -it p

If it says something like:

Not all filesets for 4.3.3.0_AIX_ML were found.

then you have some filesets that are down level. You should be able to find the down level file sets with the following command:

oslevel -l 4.3.3.0

Some times when you migrate there are left over lpp's that make the system appear downlevel. If there are only a few filesets that are downlevel you probably don't have to worry.

Try running:

lslpp -l bos.rte

if it shows 4.3.3.x you are probably close enough, but still try to resolve the downlevel filesets.

If all else fails you could grab the 4.3.0.0 to 4.3.3_ML11 fileset from IBM. Warning this fix is over 250mb. If you have unimpeded internet access from the 6000 you could also use fixdist.

Hope that helps.

 

[bi]

usige is right about your having a fileset that isn't at 4.3.3. However, I experienced this with a new system on which 4.3.3 came installed from the factory. There were some filesets (ifor_ls, if I remember correctly) that were all still at 4.2.x so OS level kept showing 4.2.whatever.

I would recommend checking an entire lslpp -l to check the fileset levels on all filesets. Keep in mind that some filesets will have completely different version numbers from 4.3.3.

 

[CrystalWizard]

you run the oslevel command to find out what filesets are not installed correctly. And then you either uninstall stuff you shouldn't have on there if it's causing you problems or you install what's missing. You also run lppchk -v and fix any filesets it says need to be fixed. You do not leave the machine showing 4.3.0, that's very bad.

 

[clifftayo]

right you must do a smitty_update_all. then check if al the ML patches are applied. (instfix -i |grep ML)