IC80420: TPC UPGRADE FAILS AT LDAP CONFIGURATION SCREEN

4.2.2 Fix Pack 7 (July 2014) for Tivoli Storage Productivity Center
4.2.2 Interim Fix 2 (December 2012) for Tivoli Storage Productivity Center
4.2.2 Fix Pack 8 (March 2015) for Tivoli Storage Productivity Center
4.2.2 Fix Pack 9 (May 2015) for Tivoli Storage Productivity Center
4.2.2 Fix Pack 10 (August 2015) for Tivoli Storage Productivity Center
4.2.2 Fix Pack 3 (October 2012) for Tivoli Storage Productivity Center

APAR status

• Closed as program error.

Error description

• During TPC upgrade when installer comes to the LDAP
  configuration screen
  LDAP TPC Administrator user and group is specified
  Upgrade fails producing error message:
  LDAP TPC user Administrator username  <userid> was not found in
  the LDAP server under the o=defaultWIMFileBasedrealm relative
  distinguished name
  Enter an existing LDAP userid and try again
  Initial Impact: Medium
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All TPC users performing an upgrade          *
  ****************************************************************
  * PROBLEM DESCRIPTION: Unable to upgrade TPC after changing    *
  *                      authentication method from OS to LDAP:  *
  *                                                              *
  *                      The specified LDAP Relative             *
  *                      distinguished Name (RDN),               *
  *                      o=defaultWIMFileBasedRealm, was not     *
  *                      found on the LDAP server. Enter an      *
  *                      existing RDN and try again.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  -
  

Problem conclusion

• To workaround the issue, connect to TIP and configure
  Federated Repositories. Click on "Supported entity types" link,
  then change  "Base entry for the default parent" for each
  record (Group, OrgContainer, PersonAccount) from
  "o=defaultWIMFileBasedRealm" to "ou=tpc,o=ibm,c=us".
  
  The fix for this APAR is targeted for the following
  maintenance package:
  
  | fix pack | 4.2.2-TIV-TPC-FP0002 - target April 2012
  
  http://www-01.ibm.com/support/docview.wss?&uid=swg21320822
  
  The target dates for future fix packs do not represent a formal
  commitment by IBM. The dates are subject to change without
  notice.
  
  There is also a documentation correction.
  
  For TPC users performing an upgrade from a version older than
  4.2.2.97, after changing authentication method from OS to LDAP
  this workaround is necessary:
  For the following file:
  For Windows: c:\Program
  Files\IBM\TPC\config\InstallVariable.properties
  For UNIX or Linux:
  /opt/IBM/TPC/config/InstallVariable.properties
  
  Modify the value of varTPCSUGrp property with the name of the
  group from LDAP that was mapped by TPC to superuser role.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TPC FOR FABRIC

• Fixed component ID

  5608TC100

Applicable component levels

• R42A PSY

     UP

• R42L PSY

     UP

• R42W PSY

     UP