IBM Support

IJ18496: ORACLE ERRORS PRODUCED IF TYPE_SCROLL_SENSTIVE IS ENABLED. THE QUERIES RUN ON NETCOOL & DATA'S RETURNED BUT ERRORS ARE ANNOYING

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Oracle support team reported parse errors generated by queries
    run on the database by Netcool.
    Tried upgrading the Oracle Drivers to ojdbc6.jar. This did not
    solve the errors.
    The Oracle support team has recreated the issue with a script
    and found if TYPE_SCROLL_SENSTIVE is enabled, the parse errors
    are generated. But if it disabled and the same query is run, the
    parse errors stop.
    
    Setting log4j to capture log statements highlighting the usage:
    
    ? add the following line to impactserver.log4j.properties
    log4j.category.com.micromuse.common.datasource.JDBCVirtualStatem
    ent=DEBUG
    You should then see log statements which look like
    "creating scrollable statement"
    "jdbc statement options: <resultsettype> and
    <resultsetconcurrency>"
    
    And set the log threshold to DEBUG in
    $IMPACT_HOME/etc/impactserver.log4j.properties:
    
    log4j.appender.NETCOOL.threshold=DEBUG
    
    save it and recreate issue produces the log message:
    
    04 Jul 2019 12:39:31,997 DEBUG [JDBCVirtualStatement] creating
    scrollable statement
    04 Jul 2019 12:39:31,997 DEBUG [JDBCVirtualStatement] jdbc
    statement options : 1005 and 1008
    ...
    04 Jul 2019 12:39:32,012 DEBUG [JDBCVirtualStatement] Trying
    once more with type: TYPE_FORWARD_ONLY and concurrency:
    CONCUR_READ_ONLY
    
    1005 means TYPE_SCROLL_SENSITIVE
    1008 means CONCUR_UPDATABLE
    
    Impact will try TYPE_SCROLL_SENSITIVE and CONCUR_UPDATABLE
    first. If fails, then Impact tries once more with type:
    TYPE_FORWARD_ONLY and concurrency: CONCUR_READ_ONLY.
    
    The queries do run on Netcool and data is returned, however, the
    Oracle support team has requested we disable
    TYPE_SCROLL_SENSITIVE as this property is causing parse errors
    on the Database.
    
    So, yes, it is working but the double try method is causing the
    Oracle team a headache with these unwanted errors.  Yes, they
    can be ignored, but they'd rather not have them at all.  Is
    there a way of forcing one method rather than the other for this
    particular call to prevent the creation of these errors in the
    first place?
    

Local fix

  • A test fix has been produced and the README.txt describes how
    to set resultset type and/or resultset concurrency in Step 4.
    
    4. Set Integer stands for JDBC resultset type and/or resultset
    concurrency in etc/NCI_datasource.props
      impact.resultsettype=1003
      impact.resultsetconcurrency=1007
    
    Note: All valid values for step 4 are as following and accept
    Integer only.
    TYPE_FORWARD_ONLY=1003
    TYPE_SCROLL_INSENSITIVE=1004
    TYPE_SCROLL_SENSITIVE=1005
    CONCUR_READ_ONLY=1007
    CONCUR_UPDATABLE=1008
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Impact Users                                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * User need functionality which can set Oracle jdbc statement  *
    * option ResultSetType and ResultSetConcurrency.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Add support Oracle jdbc statement option ResultSetType and
    ResultSetConcurrency through property file.
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
    | Fix Pack | 7.1.0-TIV-NCI-FP0018
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ18496

  • Reported component name

    NETCOOL/IMPACT

  • Reported component ID

    5724O59IS

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-08-23

  • Closed date

    2019-10-30

  • Last modified date

    2019-10-30

  • 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

    NETCOOL/IMPACT

  • Fixed component ID

    5724O59IS

Applicable component levels

  • R710 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSHYH","label":"Tivoli Netcool\/Impact"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710"}]

Document Information

Modified date:
25 August 2021