IBM Systems Director installation or uninstallation fails and requires cleanup

This problem affects systems on which installation or the removal of an installation failed for a
component of IBM? Systems
Director.

Problem

You attempted to install IBM Systems Director or uninstall a component of
IBM Systems Director, but it failed
and left behind files, data, or registry settings that might cause problems for
later installations.

Explanation

A failed IBM Systems
Director installation or uninstallation can
leave items that require cleanup.

Resolution

Use the following information to
clean up after a failed IBM Systems
Director installation or uninstallation:

For AIX? :
If the installation or uninstallation of one
or more of the IBM Systems
Director file sets fails, take the following
actions to clean up your system:

• Run installp -C to clean up
  any interrupted installation processes.
  
• Use the following commands to determine if there are any file sets
  related to IBM Systems Director that
  are still on the system:
  

  * lslpp -l | grep -i fspproxy
  * lslpp -l | grep -i director
  * lslpp -l | grep -i cas
  * lslpp -l | grep -i sysmgt.cim * lslpp -l | grep -i tivguid

  
  If any of the following
  file sets are returned by the lslpp
  command, use the installp -u
  command to uninstall them in the order in which they
  are listed here:
  
  
  
  • Director.Server.ext.FSPProxy.rte
    
  • DirectorServer
    
  • DirectorCommonAgent
    
    
  • cas.agent^*
    
  • Director.DirectorCimCore
    
  • DirectorPlatformAgent
    
  • Director.CimExtension
    
  • Director.CimCore
    
  • sysmgt.cim.smisproviders.hba_hdr^*
    
  • sysmgt.cim.smisproviders.hhr^*
    
  • sysmgt.cim.smisproviders.vblksrv^*
    
  • sysmgt.cim.providers.smash^*
    
  • sysmgt.cim.providers.osbase^*
    
  • sysmgt.cim.providers.metrics^*
    
  • sysmgt.cim.providers.scc^*
    
  • sysmgt.cimserver.pegasus.rte^*
    
  • tivoli.tivguid^*
  ^* Other applications might use these file sets, so remove
  them with caution.
  
• After uninstallation, complete the following steps to check for
  unnecessary remaining processes and end them if they are found:
  
  
  
  1. Check for CIMprocesses by running the following commands:
     

     # ps -ef | grep cimserver
         root 491660 499862   0   Oct 15   -  0:00 
           /opt/freeware/cimom/pegasus/bin/cimservera
     # ps -ef | grep cimlistener
         root 454814      1   0   Oct 15   -  0:00 
           /usr/bin/cimlistener
     # ps -ef | grep -i diag
         root 487444      1   0   Oct 15   -  0:00 
           /opt/freeware/cimom/pegasus/bin/CIM_diagd

     
     
     
  2. Check for SLP and SNMP processes by running the following commands:
     

     # ps -ef | grep tier1slp
     root 442594      1   0   Oct 15  -  0:00 /opt/ibm/director/cimom
        /bin/tier1slp
     # ps -ef | grep dirsnmp
     root 303210      1   0   Oct 15  -  0:00 
        /opt/ibm/icc/cimom/bin/dirsnmpd

     
     
     
  3. Check for server Java processes by running the following commands:
     

     # ps -ef | grep java | grep -i /opt/ibm/director/jre
     root 372942      1   0 00:45:28  pts/3  4:12 
        /opt/ibm/director/jre/bin/java -Xms512m -Xmx1024m 
        -Dtio.home=/opt/ibm/director/tpm -Dtc.home=/opt/ibm/director/tpm 
        -Djava.net.preferIPv4Stack=true -Xms512m -Xmx1024m 
        -Dtio.home=/opt/ibm/director/tpm -Dtc.home=/opt/ibm/director/tpm 
        -DPCL_BASEDIR=/opt/ibm/director/data/base 
        -Xbootclasspath/a:/opt/ibm/director/lwi/runtime/core/rcp/eclipse
        /plugins/com.ibm.rcp.base_6.1.2.200801281200/rcpbootcp.jar:/opt/ibm
        /director/lwi/lib/ISCJaasModule.jar:/opt/ibm/director/lwi/lib
        /UsmiJaasModule.jar:/opt/ibm/director/lwi/lib/icl.jar:/opt/ibm
        /director/lwi/lib/jaas2zos.jar:/opt/ibm/director/lwi/lib
        /jaasmodule.jar:/opt/ibm/director/lwi/lib/lwinative.jar:/opt/ibm
        /director/lwi/lib/lwirolemap.jar:/opt/ibm/director/lwi/lib
        /passutils.jar -Xverify:none -cp eclipse/launch.jar:eclipse
        /startup.jar:/opt/ibm/director/lwi/runtime/core/rcp/eclipse/plugins
        /com.ibm.rcp.base_6.1.2.200801281200/launcher.jar 
        com.ibm.lwi.LaunchLWI

     
     
     
  4. If a common agent file set was uninstalled, check for agent Java
     processes by running the following commands:
     

     # ps -ef | grep nonstop
     root 532710      1   0 10:02:02      -  0:00 bin/nonstop_aix @config
        /nonstop.properties
     # ps -ef | grep /var/opt/tivoli/ep
     root 491666 532710   0 10:02:03      -  1:12 /var/opt/tivoli/ep/_jvm
        /jre/bin/java -Xmx384m -Xminf0.01 -Xmaxf0.4 -Xbootclasspath/a:/var
        /opt/tivoli/ep/runtime/core/rcp/eclipse/plugins
        /com.ibm.rcp.base_6.1.2.200801281200/rcpbootcp.jar:/var/opt/tivoli
        /ep/lib/icl.jar:/var/opt/tivoli/ep/lib/jaas2zos.jar:/var/opt/tivoli
        /ep/lib/jaasmodule.jar:/var/opt/tivoli/ep/lib/lwinative.jar:/var
        /opt/tivoli/ep/lib/lwirolemap.jar:/var/opt/tivoli/ep/lib
        /passutils.jar:../../runtime/agent/lib/cas-bootcp.jar -Xverify:none 
        -cp eclipse/launch.jar:eclipse/startup.jar:/var/opt/tivoli/ep/runtime
        /core/rcp/eclipse/plugins/com.ibm.rcp.base_6.1.2.200801281200
        /launcher.jar com.ibm.lwi.LaunchLWI

     
     
  
  
• After uninstallation, the following directories should be empty or
  nonexistent. Remove them if they still exist.
  
  
  
  • /opt/ibm/director/* (except for /opt/ibm/director/classes - see the
    next bullet)
    
  • /opt/ibm/icc
    
  • /opt/freeware/cimom/pegasus (only if sysmgt.cim* file sets were
    removed)
    
  • /etc/ibm/director
    
  • /etc/ibm/tivoli
    
  • /usr/tivoli/guid (only if tivoli.tivguid was removed)
    
  • /usr/pegasus (only if sysmgt.cim* file sets were removed)
    
  • /var/opt/tivoli/ep (only if cas.agent file set was removed)
    
  
  
  Note: Removing these files
  can produce related SWVPD error messages when you try a new installation.
  However, you can usually ignore these error messages because the SWVPD inventory
  is corrected as part of the new installation process.
  
  
• After uninstallation, remove the following files only if you are
  running a version of AIX that is
  earlier than 6.1:
  
  
  
  • /opt/ibm/director/classes/pConsoleLaunch.jar
    
  • /opt/ibm/director/classes/extensions/pConsole.TWGExt
    
  • /opt/ibm/director/classes/extensions/pConsole.TWGSubagent
    

For more information about cleaning up a failed installation, see
in the IBM System
p? and AIX Information Center.

For IBM i:
If IBM Systems Director
uninstallation fails on IBM i
because an object is locked, see the job log for details about the object that
caused the failure. Commands such as WRKOBJLCK and DLCOBJ can be used to work with object locks. If
a different server has a lock on an IBM Systems
Director object, the uninstallation might be completed
successfully but the locked IBM Systems
Director object might still exist after the uninstallation. If you
want to clean up the locked objects, you first might need to end that server to
release the locks. Use the normal documented method of ending that server, for
example, use ENDTCPSVR instead of ENDJOB.
For Linux and VMware:
The IBM Systems
Director uninstallation script checks for any RPM dependencies. If
dependencies are detected, the script lists the dependencies found and then
exits. To remove the dependencies, type the following command for each
dependency listed:

rpm -ef rpm_name

where
rpm_name is the dependency.

Note: Occasionally this
command might fail. If it does, type rpm -ef rpm_name --noscripts where rpm_name is the
dependency.

After removing all of the dependencies, run the IBM Systems Director uninstallation script again.

For Windows:
Contact the IBM Technical Support Center for
assistance. You must have an IBM Support Line contract.