Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
2. Create a backup
oslevel -sl 6100-07-04-1216 (this will show if there are any issues with the filesets
associated with the SP level, if there are any listed, then the present upgrade will fail
until these are resolved see below)
root@ca2appobitst02 # oslevel -sl 6100-07-04-1216
Fileset
Actual Level
Service Pack Level
----------------------------------------------------------------------------X11.fnt.ucs.ttf
6.1.7.1
6.1.7.15
X11.fnt.ucs.ttf_extb
6.1.7.1
6.1.7.15
bos.loc.com.utf
6.1.7.0
6.1.7.15
bos.loc.utf.EN_US
6.1.7.0
6.1.7.15
Page 1 of 4
c.
lppchk -v
Health check and gather server details:
e. Next, verify your boot image it can be successfully recreated using the hdisk#
from above and by using /dev/ipldevice.
bosboot -ad /dev/hdisk0
bosboot: Boot image is 35795 512 byte blocks.
Note: If either of these two commands fail for any reason, please call the IBM
support center for resolution before proceeding.
2. Create a backup
If something should go wrong, it is good to have a backup. The following backup is preformed
from a NIM master server, backing up the client (power2) that will be updated.
mksysb -i -e /oracle_patches/mksysb_den/server_name.mksysb.6.1.7
(where server_name is the system name)
Page 2 of 4
Create a standby BOS (Base Operating System) instance using the multibos command.
Initially you should run a preview operation:
multibos -Xsp
Return Status = SUCCESS
Now we actually run the command without preview mode. This may take a while even two.
multibos -Xs
We can actually now enter the secondary BOS instance like a chroot and check the oslevel:
multibos S
6100-07-04-1216
Page 3 of 4
Page 4 of 4