IBM Support

PM01518: JDBC PROVIDERS CREATED WRONG FOR EVENT/EVENT_CATALOG.

Fixes are available

7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The test connection operation failed for a data source event
    with the following exception: j
    ava.lang.ClassNotFoundException:
    DSRA8000E: No jar or zip files found in
    C:sqlserver_3.5_datadirectlib/sqljdbc.jar. View JVM logs for
    further details.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
    *                  who configure Common Event Infrastructure   *
    *                  with Microsoft SQL Server database and      *
    *                  want to use the DataDirect ConnectJDBC      *
    *                  driver type for Microsoft SQL Server.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: The automatic process of configuring    *
    *                      the Common Event Infrastructure with    *
    *                      Microsoft SQL Server database does      *
    *                      not support the WebSphere Application   *
    *                      Server data source based on the         *
    *                      DataDirect ConnectJDBC driver type      *
    *                      for Microsoft SQL Server. There is no   *
    *                      option for the users to specify the     *
    *                      fact that they want to create the       *
    *                      Data source for Common Event            *
    *                      Infrastructure based on the             *
    *                      DataDirect Connect JDBC provider type.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The automatic configuration process of Common Event
    Infrastructure with Microsoft SQL Server database does create
    the WebSphere Application Server data source based on the
    Microsoft SQL Server JDBC Driver (XA) driver version (if the
    parameter  ?jdbcClassPath is specified and value is provid
    Common Event Infrastructure configuration supports the data
    source to be configured with a provider based on DataDirect
    ConnectJDBC driver type for Microsoft SQL Server as well. If
    the users need to base their data source on the above option,
    they will be able to do so by using a manual procedure via
    the Administrative Console. The automatic configuration process
    for Common event Infrastructure should support this case as
    well.
    

Problem conclusion

  • The automatic configuration process with Microsoft SQL Server
    database has been changed by adding to the
    configEventServiceSQLServerDB configuration Admin Task a new
    optional parameter -jdbcProviderType that will accept the
    following possible/acceptable values microsoftjdbc /
    datadirectjdbc. By using the 'microsoftjdbc' value
    the configuration of the JDBC provider is made with 'Microsoft
    SQL Server JDBC Driver (XA). The usage of 'datadirectjdbc'
    value will determine the configuration of the JDBC provider to
    be based on the 'DataDirect ConnectJDBC to Microsoft SQL
    Server type 4' driver.
    
    The introduced behavior is:
    a. -jdbcProviderType not specified in the AdminTask - The
    configuration will be performed using 'Microsoft SQL Server
    JDBC Driver (XA)'.
    b. -jdbcProviderType specified but no value supplied - Will
    raise an exception as jdbcProviderType needs a value, that is
    if the user go so far as to use the parameter but does NOT
    supply a value, we give an error stating like in the following
    example "CEIIN0739E No value was specified for the
    jdbcProviderType parameter.
    c. -jdbcProviderType specified with the 'microsoftjdbc' value
    supplied - The configuration will be performed using
    'Microsoft SQL Server JDBC Driver (XA)'.
    d. -jdbcProviderType specified with the 'datadirectjdbc' value
    supplied - The configuration will be performed using
    'DataDirect ConnectJDBC to Microsoft SQL Server type 4 driver'.
    e. -jdbcProviderType specified with a value OTHER than
    microsoftjdbc or datadirectjdbc - Will raise an exception like
    in the following example: "CEIIN0701E The parameter
    jdbcProviderType contains the value <wrong_value>, which is
    not valid. Valid values are: microsoftjdbc datadirectjdbc."
    
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.9.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • ZE Fix Error, see PM11415 04/06/2010. There is a problem with
    the interim fix ONLY for this APAR. The interim fix is
    superceded by PM11415. The code for this APAR in any fix pack
    has no problem.
    

Comments

APAR Information

  • APAR number

    PM01518

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-11-17

  • Closed date

    2009-12-02

  • Last modified date

    2010-04-06

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021