IV30041: CHANGING THE ORACLE LDAP DATA SOURCE TO USE A JDBC LDAP URL TO OBTAIN A CONNECTION TO ORACLE

6.1.0-TIV-BSM-FP0004-zlinux
6.1.0-TIV-BSM-FP0004-windows
6.1.0-TIV-BSM-FP0004-solaris
6.1.0-TIV-BSM-FP0004-linux
6.1.0-TIV-BSM-FP0004-aix
6.1.0-TIV-NCI-FP0004-zlinux
6.1.0-TIV-NCI-FP0004-windows
6.1.0-TIV-NCI-FP0004-solaris
6.1.0-TIV-NCI-FP0004-aix
6.1.0-TIV-NCI-FP0004-linux
6.1.0-TIV-NCI-FP0003-zlinux
6.1.0-TIV-NCI-FP0003-windows
6.1.0-TIV-NCI-FP0003-solaris
6.1.0-TIV-NCI-FP0003-linux
6.1.0-TIV-NCI-FP0003-aix
6.1.0-TIV-BSM-FP0003-solaris
6.1.0-TIV-BSM-FP0003-aix
6.1.0-TIV-BSM-FP0003-zlinux
6.1.0-TIV-BSM-FP0003-windows
6.1.0-TIV-BSM-FP0003-linux
5.1.1-TIV-NCI-FP0003-Linux
5.1.1-TIV-NCI-FP0003-HPUX
5.1.1-TIV-NCI-FP0003-win
5.1.1-TIV-NCI-FP0003-Solaris
5.1.1-TIV-NCI-FP0003-Linuxs390
5.1.1-TIV-NCI-FP0003-aix
IBM Tivoli Netcool/Impact V5.1.1 Fix Pack 2 (5.1.1-TIV-NCI-FP0002)
IBM Tivoli Business Service Manager V6.1.0 Fix Pack 2(6.1.0-TIV-BSM-FP0002)
IBM Tivoli Netcool/Impact V6.1.0 Fix Pack 2(6.1.0-TIV-NCI-FP0002)
IBM Tivoli Netcool/Impact V5.1.1 Fix Pack 3 (5.1.1-TIV-NCI-FP0003)
IBM Tivoli Netcool/Impact V6.1.0 Fix Pack 4(6.1.0-TIV-NCI-FP0004)
IBM Tivoli Business Service Manager V6.1.0 Fix Pack 4(6.1.0-TIV-BSM-FP0004)
IBM Tivoli Netcool/Impact V6.1.0 Fix Pack 4(6.1.0-TIV-NCI-FP0004)

APAR status

• Closed as program error.

Error description

• Changing the Oracle LDAP data source to use a jdbc ldap URL to
  obtain a connection to Oracle
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Impact Users                                             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Configuring Oracle data source via LDAP was very difficult   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * NONE                                                         *
  ****************************************************************
  Impact required a special sql.Datasource object to exist in the
  LDAP jndi registry in order to obtain an oracle connection
  through ldap. This approach does not make sense given the url
  available to make an oracle ldap connection, and in the case of
  Active  DIrectory this approach was not feasible to implement.
  

Problem conclusion

• Customer now configures the data source in Impact with the url
  to connect to Oracle via LDAP.
  The fix for this apar is in 511FP2
  

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:

Modules/Macros

• UNKNOWN
  

Fix information

• Fixed component name

  NC/IMPACT DSA O

• Fixed component ID

  5724O66OR

Applicable component levels

• R511 PSY

     UP