IBM Support

IV95206: WHEN RUNNING USER APPLICATION IMPORT, THE DB CURSOR KEEP OPENING

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Ø
    Environment:
    IBM WebSphere Application Server 8.5.5.9
    Tivoli's process automation engine 7.6.0.5-IFIX20160914-1206
    Build
    20160611-0100 DB Build V7605-45 HFDB Build HF7605-04
    IBM TPAE Integration Framework
    7.6.0.5-MIF_7605_IFIX.20160920-1010
    Build 20160610-2330 DB Build V7605-50 HFDB Build HF7605-03
    IBM Maximo Asset Management Work Centers 7.6.0.0 Build
    20160610-1318 DB Build V7600-38
    IBM Maximo Asset Management 7.6.0.5 Build 20160611-0100 DB
    Build  V7604-01
    Linux 2.6.32-573.el6.x86_64
    DB DB2/LINUXX8664 10.5 (SQL10057)
    
    Concerns/Problem:
    The customer try to import three files each has 500 records.
    When use the User application import the files, They get the
    below error :
    "BMXAA5804E -Import of data in file T1MXUSERINGROUP_500_3.dat
    was  unsuccessful.
    BMXAA5598E - Processing of an inbound transaction failed. The
    processing exception is identified in document  437.
    BMXAA4209E - Sequence GROUPUSERSEQ sequence does not exist. Use
    the database configuration application to check the
    configuration of this attribute and the sequence."
    
    This issue occurs with some specific object structure like
    Security Group and Location.
    It does not occur to every object structures.
    
    The customer set the DB2 CLIPKG is 3 as default.
    When running application import, the client check the number of
    open cursor by the following SQL.
          db2 select agent_id,open_loc_curs,open_rem_curs from
    sysibmadm.snapappl
    
    In some cases, cursors keep on opening and never closed.
    
    <Test Scenario>
    - DB2 CLIPKG=3
    
    - Using Application import with three files each has 500
    records.
    
    <Result>
    - For Security Group application import   The cursor keep on
    opening and never closed.
    
    Steps to reproduce the issue:
    1. Create an object structure:
    Parent  Child   Relationship:
    MAXUSER GROUPUSER  GROUPUSER
    
    Supprt Flat Structure.
    2. Added 100 users in Users application
    3. Import first file (500 records),No problem.
    4. Import second file (500 records),No problem.
    5. Import third file (500 records), get error:
    BMXAA5804E -Import of data in file T1MXUSERINGROUP_500_3.dat
    was unsuccessful.
    
    BMXAA5598E - Processing of an inbound transaction failed. The
    processing exception is identified in document  437.
    
    BMXAA4209E - Sequence GROUPUSERSEQ sequence does not exist. Use
    the database configuration application to check the
    configuration of this attribute and the sequence."
    
    "BMXAA6713E - MBO fetch operation failed in the mboset with the
    SQL error code -805. "
    
    If the customer sign out and sign in again, they can import the
    3rd file without any problem.
    
    Before and after import files, run the below queries to check
    cursors used in DB2.
    C:\IBM\SQLLIB\BIN>db2 select
    agent_id,open_loc_curs,open_rem_curs from sysibmadm.snapappl
    
    The client found the open cursor number is not changed after
    import files.
    
    Additional information:
    Level 3 expert checked the issue:
    The issue was whenever SqlFormat is used the mboset must be
    closed. There were numerous places in many classes where the
    mbosets were not being closed.
    
    Level 3 expert created a test-fix with below classes modified:
    GroupUser.class
    GroupUser_Stub.class
    GroupUserSet.class
    GroupUserSet_Stub.class
    LocAuth.class
    LocAuth_Stub.class
    MaxGroup.class
    MaxGroup_Stub.class
    MaxUser.class
    MaxUser_Stub.class
    
    After applied the test-fix, the cursor leaking issue is fixed.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Maximo Users                                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * WHEN RUNNING USER APPLICATION IMPORT, THE DB CURSOR KEEP     *
    * OPENING                                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to latest release                                    *
    ****************************************************************
    

Problem conclusion

  • WHEN RUNNING USER APPLICATION IMPORT, THE DB CURSOR ARE CLOSED
    PROPERLY
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV95206

  • Reported component name

    INTEGRATION

  • Reported component ID

    5724R46I1

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-17

  • Closed date

    2017-05-10

  • Last modified date

    2017-05-10

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • MAXIMO
    

Fix information

  • Fixed component name

    INTEGRATION

  • Fixed component ID

    5724R46I1

Applicable component levels

  • R760 PSY

       UP



Document information

More support for: Maximo Asset Management

Software version: 760

Reference #: IV95206

Modified date: 10 May 2017