IBM Support

IJ02928: MAXIMO ERRORS OUT WHEN TRYING TO DOWNLOAD ASSETS TO SPREADSHEET.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Environment :
    
    App Server  IBM WebSphere Application Server 8.5.5.3
    
    Version  Tivoli's process automation engine 7.6.0.6 Build
    20161019-0100
    DB Build V7606-50IBM TPAE Integration Framework 7.6.0.6 Build
    20161014-
    1504 DB Build V7606-24IBM Maximo Asset Management Scheduler
    7.6.4.0
    Build 20161019-0100 DB Build V7640-51IBM Maximo Asset
    Management Work
    Centers 7.6.0.1 Build 20161014-1326 DB Build V7601-41IBM Maximo
    Asset
    Management 7.6.0.6 Build 20161019-0100 DB Build V7604-01
    
    Server OS  Windows Server 2012 6.2
    Server DB  DB2/NT64 10.5 (SQL10054)
    
    
    Replication Steps:
    
    1. Login to Maximo
    2. Go to Assets application and get a list of all assets.
    3. Click on the Download button to download the assets to an
    excel spreadsheet,
    
    Error occurs in logs:
    ===
    SRVE0014E: Uncaught service()exception root cause
    /webclient/common/tabledownload.jsp;com.ibm.websphere.servlet.er
    ror.Serv
    letErrorReport: psdi.util.MXSystemException: BMXAA4210E -
    Database
    error number -805 has occurred. Invalid SQL queries are logged
    in the
    log file. Check the SQL query to identify the error.
    ===
    
    Current Erroneous Result :
    - Asset records not getting completely downloaded in the excel
    spreadsheet (Only 2224 out of 20426 records
    were downloaded before the error.)
    
    Expected Result :
    
    - All asset records should be downloaded without an error.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO users                                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * On the List tab of any application that uses dot notation to *
    * display values from related objects, the following error may *
    * be encountered if there are a large number of records being  *
    * downloaded due to consumption of all database package (db2)  *
    * or cursor (Oracle) resources:                                *
    *                                                              *
    * BMXAA6714E - The data for the next record in the mboset      *
    * could not be retrieved for the SQL query select * from       *
    * locancestor  where location = 'PUMPROOM'  and systemid = (   *
    * select systemid from locsystem where primarysystem = 1 and   *
    * siteid = 'BEDFORD' ) and siteid= 'BEDFORD' for read only.    *
    * See the log file for more details about the error.           *
    *                                                              *
    * com.ibm.db2.jcc.am.SqlException: DB2 SQL Error:              *
    * SQLCODE=-805, SQLSTATE=51002, SQLERRMC=NULLID.SYSLH203       *
    * 0X5359534C564C3031, DRIVER=3.71.22                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Replication Steps:
    
    * This example uses the Assets application but this problem will
    occur in any application.
    1. Login to Maximo
    2. Modify the Assets List tab to include data from another
    object, for example, add the following to the
    results_showlist_tablebody control in the List tab asset.xml and
    reimport:
    
    <tablecol dataattribute="PRIMARYSYSLOCASSET.ANCESTOR"
    id="results_showlist_tablebody_3XYZ"/>
    
    3. On the List tab, query for all assets. The problem will not
    happen if there are not a large number of assets. I used 25,000
    but this number will differ based on your database's package or
    cursor configuration. The more resources you have allocated for
    these, the more records you will need.
    4. Click on the Download button to download the assets to an
    excel spreadsheet. The following error will occur:
    
    *********************************************
    26 Jan 2018 14:05:30:298 [ERROR] [MXServer] [] BMXAA6714E - The
    data for the next record in the mboset could not be retrieved
    for the SQL query select * from lo
    cancestor  where location = 'PUMPROOM'  and systemid = ( select
    systemid from locsystem where primarysystem = 1 and siteid =
    'BEDFORD' ) and siteid= 'BEDFORD' f
    or read only. See the log file for more details about the error.
    com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-805,
    SQLSTATE=51002, SQLERRMC=NULLID.SYSLH203 0X5359534C564C3031,
    DRIVER=3.71.22
            at com.ibm.db2.jcc.am.gd.a(gd.java:816)
            at com.ibm.db2.jcc.am.gd.a(gd.java:66)
            at com.ibm.db2.jcc.am.gd.a(gd.java:140)
            at com.ibm.db2.jcc.am.gp.c(gp.java:2788)
            at com.ibm.db2.jcc.t4.bb.r(bb.java:964)
            at com.ibm.db2.jcc.t4.bb.i(bb.java:151)
            at com.ibm.db2.jcc.t4.bb.b(bb.java:41)
            at com.ibm.db2.jcc.t4.p.a(p.java:32)
            at com.ibm.db2.jcc.t4.vb.i(vb.java:145)
            at com.ibm.db2.jcc.am.gp.ib(gp.java:2189)
            at com.ibm.db2.jcc.am.gp.a(gp.java:3286)
            at com.ibm.db2.jcc.am.gp.a(gp.java:711)
            at com.ibm.db2.jcc.am.gp.executeQuery(gp.java:690)
            at psdi.mbo.MboSet.getNextRecordData(MboSet.java:3333)
            at psdi.mbo.MboSet.fetchMbosActual(MboSet.java:2941)
            at psdi.mbo.MboSet.fetchMbos(MboSet.java:2898)
            at psdi.mbo.MboSet.getMbo(MboSet.java:2114)
            at psdi.mbo.Mbo.getMboForAttribute(Mbo.java:1630)
            at psdi.mbo.Mbo.getMboValueData(Mbo.java:1398)
            at psdi.mbo.Mbo.getMboValueData(Mbo.java:1471)
            at
    jsp_servlet._webclient._common.__tabledownload._jspService(__tab
    ledownload.java:273)
            at weblogic.servlet.jsp.JspBase.service(JspBase.java:35)
            at
    weblogic.servlet.internal.StubSecurityHelper$ServletServiceActio
    n.run(StubSecurityHelper.java:286)
            at
    weblogic.servlet.internal.StubSecurityHelper$ServletServiceActio
    n.run(StubSecurityHelper.java:260)
            at
    weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubS
    ecurityHelper.java:137)
            at
    weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImp
    l.java:350)
            at
    weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImp
    l.java:247)
            at
    weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(Re
    questDispatcherImpl.java:612)
            at
    weblogic.servlet.internal.RequestDispatcherImpl.include(RequestD
    ispatcherImpl.java:483)
            at
    psdi.webclient.system.controller.RequestManager.manageRequest(Re
    questManager.java:161)
            at
    psdi.webclient.servlet.WebClientServlet.handleRequest(WebClientS
    ervlet.java:141)
            at
    psdi.webclient.servlet.WebClientServlet.doGet(WebClientServlet.j
    ava:93)
    
    Logged a message at:
    psdi.webclient.system.controller.RequestManager.manageRequest(Re
    questManager.java:244)
    Exception processed request: psdi.util.MXSystemException:
    BMXAA4210E - Database error number -805 has occurred. Invalid
    SQL queries are logged in the log file.
    Check the SQL query to identify the error.
    *********************************************
    
    Impact of this error:
    The complete set of asset records is not downloaded into the
    spreadsheet when this error occurs. Also, the database needs to
    be restarted or the package/cursor consumption otherwise
    released in order to continue working in the application.
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:
    	| release\fix pack\interim fix for Release 7.6.1.0
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ02928

  • Reported component name

    ASSETS

  • Reported component ID

    5724R46AS

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-04

  • Closed date

    2018-01-26

  • Last modified date

    2018-01-26

  • 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

    ASSETS

  • Fixed component ID

    5724R46AS

Applicable component levels

  • R760 PSY

       UP



Document information

More support for: Maximo Asset Management
Assets

Software version: 760

Reference #: IJ02928

Modified date: 26 January 2018