Solved

AIX oslevel

Posted on 2014-02-14
5
532 Views
Last Modified: 2014-03-13
we have run into a major problem after increasing Oracle SGA from 60GB to 160GB at our prod server.

7.1
11g R2 oarcle
no large pages.

it was a sever memory issue,that caused us to revert changes.
now we are trying to reproduce the issue when we tried to reproduceon another server witha slightly higher OSLEVEL we were fine,but when tried at a very close oslevel we were able to reproduce.
prod=7100-00-02-1041

now have some confusion

why when we invoke nmon from both servers we get different results than oslevel -s
for instance
prod=
oslevel -s    7100-00-02-1041
although nmon home screen 7.1.0.2 TL00

while in the test box
oslevel -s   7100-00-02-1041
although nmon home screen  7.1.0.15 TL00

======================================
2nd Q how can we tell the difference in APAR's between 2 different oslevels,so we can tell what issues have caused the problem?
0
Comment
Question by:it-rex
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 68

Accepted Solution

by:
woolmilkporc earned 500 total points
ID: 39860639
nmon will display the version of the fileset bos.mp64 on its home screen (and with "r").

Could it be that you installed a service pack on one system , but not with all required filesets?

Run on both systems

lslpp -l bos.mp64

Any differences? Probably!

Run

lppchk -v

Any messages?

Next, run

oslevel -sq

to display all known service packs.

Is the highest known service pack the same of both systems? Probably not!

If it isn't then run on the machine which displays a higher known SP than reported by "oslevel -s":

oslevel -sl <highest known service pack>

means: display all fileset updates required  to reach the indicated level which are missing.

On the other machine you should run

oslevel -sg <highest known service pack>

means: display all fileset updates which are on a higher level than required to reach the indicated level.

This is also the clue how to list the difference between the highest and the second-to-highest service pack level (as obtained with "oslevel -sq")

oslevel -sg <second-to-highest SP>

means: display all filesets required to go from second-to-highest to highest service pack.

Note: some filesets will be on an even higher level than the highest SP. This is due to packaging.
The list of known levels/filesets is in bos.rte.install and it can happen that this fileset is packaged before the latest update to another fileset is published and packaged.

You can also run

instfix -ic | grep 71-00-021041_SP

to list all installed fileset updates contained in the specified service pack.

Note: No dash between the service pack number ("02") and the service pack date ("1041").
0
 
LVL 11

Author Comment

by:it-rex
ID: 39860823
lslpp -l bos.mp64
  Fileset                      Level  State      Description        
  ----------------------------------------------------------------------------
Path: /usr/lib/objrepos
  bos.mp64                   7.1.0.2  COMMITTED  Base Operating System 64-bit
                                                 Multiprocessor Runtime

Path: /etc/objrepos
  bos.mp64                   7.1.0.2  COMMITTED  Base Operating System 64-bit
                                                 Multiprocessor Runtime



lslpp -l bos.mp64
  Fileset                      Level  State      Description        
  ----------------------------------------------------------------------------
Path: /usr/lib/objrepos
  bos.mp64                  7.1.0.15  COMMITTED  Base Operating System 64-bit
                                                 Multiprocessor Runtime

Path: /etc/objrepos
  bos.mp64                  7.1.0.15  COMMITTED  Base Operating System 64-bit
                                                 Multiprocessor Runtime
=======================================================================
lppchk -v

no messages in both lpars
========================================================================
highest service pack
oslevel -sq

1st   7100-00-03-1115
2nd  7100-00-10-1334
========================================================================
0
 
LVL 11

Author Comment

by:it-rex
ID: 39860824
I am not sure what I am supposed to do here:


If it isn't then run on the machine which displays a higher known SP than reported by "oslevel -s":

oslevel -sl <highest known service pack>

means: display all fileset updates required  to reach the indicated level which are missing.

On the other machine you should run

oslevel -sg <highest known service pack>

means: display all fileset updates which are on a higher level than required to reach the indicated level.
0
 
LVL 68

Expert Comment

by:woolmilkporc
ID: 39861245
Both machines report a higher known service level than shown as "installed" by oslevel -s.

Run on 1st LPAR

oslevel -sl 7100-00-03-1115

and on 2nd LPAR

oslevel -sl 7100-00-10-1334

The filesets shown with these comands must be updated to reach the highest known service level.

It seems that you tried to update "1st" to SP 3, but some updates failed/were missing so you did just reach (or stay on) SP 2.

Similar is true for "2nd". You tried to update to SP 10, but many updates failed/were missing so you did just reach (or stay on) SP 2.

You should also run cleanup to to remove all incomplete pieces of the previous (interrupted?) installation:

installp -C

Any messages?

Anyway, you must decide which SP level you're willing to reach.
Service packs are cumulative, so you just have to make sure that you downloaded the complete desired SP package from Fix Central to then retry the upgrade.
Please record carefully all error messages from update_all, so in case the uprade might fail once more you can get some hints why.
0
 
LVL 11

Author Closing Comment

by:it-rex
ID: 39927642
thanks
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

When you do backups in the Solaris Operating System, the file system must be inactive. Otherwise, the output may be inconsistent. A file system is inactive when it's unmounted or it's write-locked by the operating system. Although the fssnap utility…
Java performance on Solaris - Managing CPUs There are various resource controls in operating system which directly/indirectly influence the performance of application. one of the most important resource controls is "CPU".   In a multithreaded…
Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…
In a previous video, we went over how to export a DynamoDB table into Amazon S3.  In this video, we show how to load the export from S3 into a DynamoDB table.

756 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question