Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
upgrade maintenance level 1
- Thread starter aix43
- Start date
-
1
- #4
Well just my two cents
IBM calls them recommended maintenance upgrades........It feels that the bugs
fixed in the patches could save you grief down the road. If something does not work correctly on your system...the first words out of IBM are, do you have the
maintenance patches applied? Yes they can break stuff as well, but ......some of the patches are significant as in system hangs, poor performance on ethernet, etc etc...
I guess you have to make up your own mind. If you have a relatively simple application running on the machine, and it doesn't use many of the aix features, you can probably get by on just 4.3.3.0.........I would at least put the update cd on the system though...that was shipped with the original operating system.
IBM calls them recommended maintenance upgrades........It feels that the bugs
fixed in the patches could save you grief down the road. If something does not work correctly on your system...the first words out of IBM are, do you have the
maintenance patches applied? Yes they can break stuff as well, but ......some of the patches are significant as in system hangs, poor performance on ethernet, etc etc...
I guess you have to make up your own mind. If you have a relatively simple application running on the machine, and it doesn't use many of the aix features, you can probably get by on just 4.3.3.0.........I would at least put the update cd on the system though...that was shipped with the original operating system.
And yet another thought....
We make it a practice to have a MKSYSB (two of them) prior to applying the O/S patches. Also note we apply not commit. This makes it easier to rip out if a problem should occur. When the next set of patches come out we commit the previous set prior to applying the new set.
We make it a practice to have a MKSYSB (two of them) prior to applying the O/S patches. Also note we apply not commit. This makes it easier to rip out if a problem should occur. When the next set of patches come out we commit the previous set prior to applying the new set.
how do we see the maintainence level of a machine
"oslevel" gives level like 4.3.3...but if we want to see the whole version..how do we see it.....sorry a stupid question but just curious...!! Thief................
(In a confrontation between a rock and stream, the stream always wins, not because of strength but persistence.)
"oslevel" gives level like 4.3.3...but if we want to see the whole version..how do we see it.....sorry a stupid question but just curious...!! Thief................
(In a confrontation between a rock and stream, the stream always wins, not because of strength but persistence.)
it gave me this output...
> instfix -i|grep ML
All filesets for AIX43ML were found.
All filesets for 4.3.1.0_AIX_ML were found.
All filesets for AIX43ML were found.
All filesets for 4.3.2.0_AIX_ML were found.
All filesets for 4320-01_AIX_ML were found.
All filesets for 4320-02_AIX_ML were found.
All filesets for 4.3.3.0_AIX_ML were found.
All filesets for 4330-02_AIX_ML were found.
All filesets for 4330-03_AIX_ML were found.
Not all filesets for 4330-04_AIX_ML were found.
Not all filesets for 4330-05_AIX_ML were found.
All filesets for 4330-01_AIX_ML were found.
Not all filesets for 4330-06_AIX_ML were found.
Not all filesets for 4330-07_AIX_ML were found.
Not all filesets for 4330-08_AIX_ML were found.
Not all filesets for 4330-09_AIX_ML were found.
what do i conclude out of it Thief................
(In a confrontation between a rock and stream, the stream always wins, not because of strength but persistence.)
> instfix -i|grep ML
All filesets for AIX43ML were found.
All filesets for 4.3.1.0_AIX_ML were found.
All filesets for AIX43ML were found.
All filesets for 4.3.2.0_AIX_ML were found.
All filesets for 4320-01_AIX_ML were found.
All filesets for 4320-02_AIX_ML were found.
All filesets for 4.3.3.0_AIX_ML were found.
All filesets for 4330-02_AIX_ML were found.
All filesets for 4330-03_AIX_ML were found.
Not all filesets for 4330-04_AIX_ML were found.
Not all filesets for 4330-05_AIX_ML were found.
All filesets for 4330-01_AIX_ML were found.
Not all filesets for 4330-06_AIX_ML were found.
Not all filesets for 4330-07_AIX_ML were found.
Not all filesets for 4330-08_AIX_ML were found.
Not all filesets for 4330-09_AIX_ML were found.
what do i conclude out of it Thief................
(In a confrontation between a rock and stream, the stream always wins, not because of strength but persistence.)
It appears that you have some patches applied...
You look at where they are all found the latest and that is the level you are at...
4330_03 were all found...so you have the third maintenance level applied.
Some patches for the other levels are applied...but not a complete maintenance level...
To see what needs to be installed to bring you up to a particular, complete
maintenance level:
# instfix -ivk 4330-04_AIX_ML|grep not | grep ':'
#instfix -ivk 4330-05_AIX_ML|grep not | grep ':'
etc....
You can apply these filesets from an update cd or downloaded individually
off the web if you wish..
or
If the output indicates that not all filesets are found, you can also
determine which filesets are not updated using the command:
instfix -ciqk 4330-04_AIX_ML | grep ":-:"
You look at where they are all found the latest and that is the level you are at...
4330_03 were all found...so you have the third maintenance level applied.
Some patches for the other levels are applied...but not a complete maintenance level...
To see what needs to be installed to bring you up to a particular, complete
maintenance level:
# instfix -ivk 4330-04_AIX_ML|grep not | grep ':'
#instfix -ivk 4330-05_AIX_ML|grep not | grep ':'
etc....
You can apply these filesets from an update cd or downloaded individually
off the web if you wish..
or
If the output indicates that not all filesets are found, you can also
determine which filesets are not updated using the command:
instfix -ciqk 4330-04_AIX_ML | grep ":-:"
thanx for the input aixqueen & ffritzon...i recently upgraded my system using a CD...but while running the command the final output was "failed"...but at the same time it was showing that the patches added were all succesfully commited. only some fixes that were required for HA, java and other applications i dont use, gave error . so i interpretted that maybe coz of this patches the command failed. will it be a problem at a later stage coz of this.... Thief................
(In a confrontation between a rock and stream, the stream always wins, not because of strength but persistence.)
(In a confrontation between a rock and stream, the stream always wins, not because of strength but persistence.)
Einstein47
Programmer
This info was also very helpful to me as well. I have one of my systems reporting oslevel 4.3.2.0, and I have been frustrated as to why. I know that it WAS at 4.3.3.0 before. Now I can at least find the correct filesets on the IBM site to get all my boxes at the same level.
Thanks again!
Thanks again!
Even one fileset at a lower level will make it say 4.3.2 instead of 4.3.3
--------------------------------------------------
On migrations to 4.3.3...the most common were...
The oslevel command may not correctly output 4.3.3.0 on systems installed or updated from the AIX 4.3.3 product media for the following reasons.
The level of the ifor_ls.compat.cli fileset on the AIX product media is at the 4.3.2.0 level. This problem can be corrected by installing the
ifor_ls.compat.cli 4.3.3.0 update (PTF U466561), which is available from
FixDist. This problem does not occur when updating from the 4.3.3.0 Maintenance
Level.
The bos.perf.pmr fileset is down level after updating from the AIX 4.3.3
product media. This occurs only when updating AIX 4.3.0 and 4.3.1 systems,
which already have the bos.perf.pmr fileset installed. The
bos.perf.pmr fileset is obsolete in AIX 4.3.3 and should be removed.
The bos.crypto* and sysmgt.security* filesets are not included in the
AIX 4.3.3.0 Maintenance Level since they contain encryption code that is
subject to export restrictions. Updates to these filesets are available only
on the AIX 4.3.3 Bonus Pack that is shipped with AIX 4.3.3.
Hope this helps narrow it down for you...........
--------------------------------------------------
On migrations to 4.3.3...the most common were...
The oslevel command may not correctly output 4.3.3.0 on systems installed or updated from the AIX 4.3.3 product media for the following reasons.
The level of the ifor_ls.compat.cli fileset on the AIX product media is at the 4.3.2.0 level. This problem can be corrected by installing the
ifor_ls.compat.cli 4.3.3.0 update (PTF U466561), which is available from
FixDist. This problem does not occur when updating from the 4.3.3.0 Maintenance
Level.
The bos.perf.pmr fileset is down level after updating from the AIX 4.3.3
product media. This occurs only when updating AIX 4.3.0 and 4.3.1 systems,
which already have the bos.perf.pmr fileset installed. The
bos.perf.pmr fileset is obsolete in AIX 4.3.3 and should be removed.
The bos.crypto* and sysmgt.security* filesets are not included in the
AIX 4.3.3.0 Maintenance Level since they contain encryption code that is
subject to export restrictions. Updates to these filesets are available only
on the AIX 4.3.3 Bonus Pack that is shipped with AIX 4.3.3.
Hope this helps narrow it down for you...........
gurus,
i tried to upgrade my machine to 4.3.3.09 from 4.3.3.01... then i when i test my lppchk -v, i got this bos.rte.control error..... it say that its not there. however, when i key in to check the list of my installed lpp, its already there and committed? how does this thing happened? when i look at the list of my new RML , because i did not apply, so im hoping i could the upgrade/applied patch for this one, there is no list of bos.rte.control 4.3.3.75 either..hmmmm..
i know that this bos.rte.control needs patch due to slowdown of shutting down system... but it seems that i've got this error strange..
can somebody explain to me, when things like this likely to occur after applying patches? the patch is there and the commited fils set is installed yet the lppchk can't recognize the commited lower level one.
Thanks a lot!
i tried to upgrade my machine to 4.3.3.09 from 4.3.3.01... then i when i test my lppchk -v, i got this bos.rte.control error..... it say that its not there. however, when i key in to check the list of my installed lpp, its already there and committed? how does this thing happened? when i look at the list of my new RML , because i did not apply, so im hoping i could the upgrade/applied patch for this one, there is no list of bos.rte.control 4.3.3.75 either..hmmmm..
i know that this bos.rte.control needs patch due to slowdown of shutting down system... but it seems that i've got this error strange..
can somebody explain to me, when things like this likely to occur after applying patches? the patch is there and the commited fils set is installed yet the lppchk can't recognize the commited lower level one.
Thanks a lot!
- Status