Build date failure updating from 6100-07-07 to 6100-08-02

no comments

Problem:

When attempting to update from 6100-07-07 to 6100-08-02 results in build date errors for the following filesets.

  • devices.pciex.df1020e214103c04.rte
  • devices.pciex.df1020e214103c04.diag
  • devices.pciex.df1020e214100f04.rte
  • devices.pciex.df1020e214100f04.diag

Solution:

To resolve this issue, download the fix for APAR IV42218, and include the images into the same directory as the 6100-08-02 Service Pack prior to updating.

This issue only occurs when updating from the 6100-07-07 Service Pack.

 

How many virtual processors are active in my AIX LPARs?

no comments

Question:

 

How many virtual processors are active in my AIX LPARs?

 

Solution:

 

You can use kdb command and the sub-command vpm:

As you see, the number of active virtual processors is 4.

# echo vpm | kdb
 START END <name>
0000000000001000 0000000004090000 start+000FD8
F00000002FF47600 F00000002FFDF9C0 __ublock+000000
000000002FF22FF4 000000002FF22FF8 environ+000000
000000002FF22FF8 000000002FF22FFC errno+000000
F1000F0A00000000 F1000F0A10000000 pvproc+000000
F1000F0A10000000 F1000F0A18000000 pvthread+000000
read vscsi_scsi_ptrs OK, ptr = 0x0
(0)> vpm
VPM Tunables
vpm_interval............... 000003E8 schedp.vpm_fold_threshold.. 00000031
vpm_fold_limit............. 00000008 vpm_unfold_limit........... 00000002
vpm_be_threshold........... 0000000A
VPM Data
.........................vpm_mgmt :01
........................vpm_flags :01 USE_BEST_ENERGY
....................vpm_prev_time :1368736952449027431 ns
.....................vpm_interval :1001004500 ns
....................vpm_prev_intr :20125205922335 ns
.........................vpm_intr :11899421 ns
VPM Core Buckets
INDX ID TYPE SR CORE LAST ACTI HEAD UTIL STATE
 0 0 SRAD 1 1 1 0 0 51844765
VPM Core State
 POS CORE NEXT PRIO BEST C STATE
 0 0 NONE 0 0 0 GP ACTIVE
VPM Sleep Data.
........................vsd_state :03
..............vsd_sleep_specifier :00000002
................vsd_sleep_latency :0000000000000000 sec 00989680 nsec
....................vsd_min_sleep :0000000000000000 sec 1DCD6500 nsec
....................vsd_prod_lock :@F100010021622400
....................vsd_prod_head :0000000000000000
VSD Thread State.
 CPU VP_STATE SLEEP_STATE PROD_TIME: SECS NSECS CEDE_LAT
0 ACTIVE AWAKE 0000000000000000 00000000 00
 1 ACTIVE AWAKE 0000000000000000 00000000 00
 2 ACTIVE AWAKE 0000000000000000 00000000 00
 3 ACTIVE AWAKE 0000000000000000 00000000 00
(0)>

In case your WebShpere Administrator is away.

no comments

After reading this attached PDF, you may probably step up while your WAS administrator is away and your company is looking after a person knows a little about WebShere.

PDF download:

WebSphere Application Server – Being the Back-Up Administrator