IBM Support

IJ35290: CREATING NEW ADHOC REPORT IN OPERATOR LOG (OIL) DETAILS CAUSES "THERE WAS AN EXCEPTION ON THE SERVER"

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • RROB DESCRIPTION:
    
    PROBLEM:
    When user accesses Operator Log(Oil) and creates detail qbr
    report using "RECORDKEY", it causes a generic err msg, instead
    of a qbr/ad-hoc report output with DB2 database.
    
    PERFORMANCE ISSUE:
    
    STEPS TO REPRODUCE:
    -from Operator Log(oil) application>run reports>create
    report>detail>Operator Log (Oil) Details >click on
    PLUSGSHFTLOGENTRY>add just "RECORDKEY">run and save
    -err is reproduced instead of the ad-hoc report: "There was an
    exception on the server. Check your report parameter values, or
    contact your system administrator, who can find additional
    details in the server log."
    
    
    CURRENT ERRONEOUS RESULT:
    err is reproduced instead of the ad-hoc report: "There was an
    exception on the server. Check your report parameter values, or
    contact your system administrator, who can find additional
    details in the server log."
    
    EXPECTED RESULT:
    Qbr report should be generated and displayed on the screen, as
    per client?s previous selections.
    
    ADDITIONAL INFO:
    n/a
    ENVIRONMENT (SYSTEM INFO):
    Tivoli's process automation engine 7.6.0.9-IFIX20190718-1538
    Build 20171127-0100 DB Build V7609-45 HFDB Build HF7609-14, IBM
    Maximo for Nuclear Power 7.6.1.0-20200727-1124 Build
    20171110-1308 DB Build V7610-45 HFDB Build HF7610-74, IBM TPAE
    Integration Framework 7.6.0.9-MIF_7609_IFIX.20190806-1734 Build
    20171127-2230 DB Build V7609-32, IBM Maximo Calibration 7.6.0.0
    Build 20171127-0100 DB Build V7600-06, IBM Maximo Linear
    Management 7.6.0.2 Build 20171127-0100 DB Build V7602-03, IBM
    Maximo Asset Management Scheduler 7.6.7.0 Build 20171127-0100 DB
    Build V7670-56 HFDB Build HF7670-28, IBM Maximo Health, Safety
    and Environment Manager 7.6.1.0 Build 20161020-0816 DB Build
    V7610-01, IBM Maximo for Service Providers 7.6.3.1-20201017-0754
    Build 20170905-1206 DB Build V7631-17 HFDB Build HF7631-21, IBM
    Maximo Spatial Asset Management 7.6.0.3-20190729-1053 Build
    20171130-1339 DB Build V7603-10 HFDB Build HF7603-02, IBM Maximo
    Enterprise Adapter for SAP Applications 7.6.0.0 Build
    201508100537 DB Build V7600-01, IBM Maximo Asset Management Work
    Centers 7.6.0.3 Build 20171121-0723 DB Build V7603-175, IBM
    Maximo for Utilities 7.6.0.1-20200713-1016 Build 20170518-1923
    DB Build V7601-08 HFDB Build HF7601-09, IBM Maximo Asset
    Management 7.6.0.9 Build 20171127-0100 DB Build V7604-01
    
    LOCAL FIX:n/a
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Creating a detail adhoc report fails when the database is    *
    * DB2, and the child object structure relationship "where      *
    * clause" has :AAA=''                                          *
    ****************************************************************
    

Problem conclusion

  • _The fix for this APAR is contained in the following maintenance
    package: release\fix pack for Release 7.6.1.3 Product_
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ35290

  • Reported component name

    MAXIMO REPORTIN

  • Reported component ID

    TIVOREPTS

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-10-01

  • Closed date

    2021-11-01

  • Last modified date

    2021-11-01

  • 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

    MAXIMO REPORTIN

  • Fixed component ID

    TIVOREPTS

Applicable component levels

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761"}]

Document Information

Modified date:
02 November 2021