Fix (APAR):  PM00901

Status:  Fix

Release:  6.1.0.5

Operating System:  AIX,HP-UX,Linux,Solaris,Windows,z/OS

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  227282

Date: 2009-11-20

Abstract:  An InvalidIndexKeyExceptions exception is displayed in the SystemOut.log file.

Description/symptom of problem:  
PM00901 resolves the following problem:

ERROR DESCRIPTION:                                              
The following exception is displayed multiple times in the      
SystemOut.log file of the deployment manager:                   
                                                                
00000064 DataAggregato E WVCS1001E: Exception occurred while    
trying to access the cache service. Exception was               
com.ibm.ws.xd.visualizationengine.cacheservice.exceptions.      
                                                                
Previously we just added 1 new index into the                   
SIPServerStatsCache to fix the previous issue.   Looking through
the cache no indices were added to SIPServerStatsCache related  
to multi-cell changes that went into 6.1.0.5.                   
                                                                
With this fix, we will be adding all the necessary indices which
will be 8 additional indices.  This should clear up all these   
kinds of issues.                                                
  indices.add(SIPSTATCACHE_INDEX_CELLNODEGROUP_ARRAY);          
  indices.add(SIPSTATCACHE_INDEX_CELLNODE_ARRAY);               
  indices.add(SIPSTATCACHE_INDEX_CELLNODESERVER_ARRAY);         
  indices.add(SIPSTATCACHE_INDEX_CELLSC_ARRAY);                 
  indices.add(SIPSTATCACHE_INDEX_CELLTC_ARRAY);                 
  indices.add(SIPSTATCACHE_INDEX_CELLAPP_ARRAY);                
  indices.add(SIPSTATCACHE_INDEX_CELLAPPMODULE_ARRAY);          
  indices.add(SIPSTATCACHE_INDEX_CELLNODESERVAPPMOD_ARRAY);     

LOCAL FIX:                                                      
None                                                            

PROBLEM SUMMARY

USERS AFFECTED:
 All users of WebSphere Extended Deployment

PROBLEM DESCRIPTION:
An InvalidIndexKeyExceptions exception
is displayed in the SystemOut.log file.

RECOMMENDATION:
None

Indices are missing in one of the caches used in charting. As
a result, an InvalidIndexKeyExceptions exception is displayed
in the SystemOut.log file of the deployment manager.

PROBLEM CONCLUSION:                                             
The missing indices are added to the cache.                     
                                                                
Refer to the Recommended Updates page for delivery information: 
http://www.ibm.com/support/docview.wss?rs=3023&uid=swg27005709  


Directions to apply fix:  
Install Fix to:
__ Application Server Nodes
_x_ Deployment Manager Nodes
__ Both

NOTE:
The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. Also, you should be logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
The Fix Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

The Update Installer for V5.0 does not have a maintenance directory. It uses fixpacks and fixes as the location of the unpacked files.

Customers must be at V6.1.0.17 or newer of the Update Installer.  This can be checked by reviewing the level of the Update Installer in file <was_root>/updateinstaller/version.txt.

1) Copy 6.1.0.5-WS-WXDOP-IFPM00901.pak file directly to the maintenance directory

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (6.1.0.5-WS-WXDOP-IFPM00901.pak file which was copied in the maintenance directory).  The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes directory.

7) Install the maintenance package.

8) Restart WebSphere

Directions to remove fix:  
NOTE:  The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.

NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.
DO NOT REMOVE A FIX UNLESS
ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.
YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (6.1.0.5-WS-WXDOP-IFPM00901.pak).

6) UnInstall maintenance package.

7) Restart WebSphere

Directions to re-apply fix:  
1) Shutdown WebSphere

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere

Additional Information: