Reviewing the generated manual clean script for WebSphere Application Server V5.0, 5.1 and 6.0 on AIX
 Technote (troubleshooting)
 
Problem(Abstract)
The "targeted cleanup" script discussed in technote 1191336, generateODMclean.sh, generates a script which will clean WebSphere-related entries from the AIX® ODM VPD. This technote explains how to check the integrity of the generated script.
 
Cause
The complete cleanup procedure described in technote 1191336 explains how to generate the cleanup script. That technote refers to the procedure described below.
 
Resolving the problem
The manualODMclean.sh script is divided into several sections:
  • inventory
  • lpp
  • product
  • vendor
  • history

The administrator should review each section according to the checklist below. Note that it is entirely possible for a section to be completely void of any deletion commands at all. If these items pass, then it is safe to run the script.
  • The header of the script should state the path of the product installation directory. Verify that this path is correct.

  • The inventory section might contain a large number of commands which delete entries from the inventory table. Each command should reference a path to a WebSphere-related file. Scroll through the list of files and check that all the files mentioned are within the product's installation directory. (In other words, be sure that no files are referenced outside of WebSphere®, such as in /lib, /usr/bin, or /bin) If any files are referenced outside of WebSphere, then do not run the manualODMclean.sh script.

    Note: the files mentioned might not actually exist in the file system. This is normal. Also, these commands will not delete these files from the file system if they do exist.

  • The product section might contain several entries which reference the product package identifiers. These identifiers typically begin with the strings WS or IHS, or might consist of 32-digit hexadecimal strings. If the identifiers clearly reference packages which belong to other products which should not be removed, or if the identifiers make any references to bos packages, then do not run the manualODMclean.sh script.

  • The lpp section might contain several entries which refer to lpp_id numbers. The meaning of these numbers is deep-rooted in the ODM tables, so human observers can only do a cursory check of these numbers. In general, the numbers should form a rough sequence, though there might be a small number of outliers. Also, the numbers should not be "low" numbers. Any lpp_id numbers less than 200 should arouse suspicion, since packages related to the initial installation of the operating system are in that range.

  • The vendor section might contain a small number of entries which reference the product installation directory and some of its subdirectories. There should be at least one entry listed in this section. If no entries are listed, it is not harmful, but it might indicate that the cleanup will be incomplete. (In that case, consider the "complete clean" solution referenced earlier in this technote.)

  • The history section might contain several entries using identifiers related to entries listed in other sections. There number of entries listed in the history section should not exceed the number of entries listed in the vendor section.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Install
Operating system(s): AIX
Software version: 6.0
Software edition:
Reference #: 1237362
IBM Group: Software Group
Modified date: Jun 14, 2006