IZ86562: DATABASE SESSIONS GROW WITH ROUTES IN WORKORDER ON CLUSTERED ENV

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

  • Problem description:
    
    I could narrow the problem down to the following constellation:
    The idea
    is that we create a route and all workorders of the route stay
    in a
    workflow in a WAIT_NODE until we update them. The leaving of the
    WAIT_NODE causes the session problem.
    
    
    
    Steps to recreate provided by client:
    
    1) Create a workflow WOTESTDBS based on Workorder: START --->
    WAIT_NODE ----> END
       The WAIT_NODE waits for maximo.workorder.update
       Set Workflow to enabled and active
    2) Create an escalation WAKEUP that puts all workorders that
    have not been in workflow WOTESTDBS into it. The SQL is
    something like
       istask=0 and workorderid not in (select ownerid from
    wfinstance where ownertable='WORKORDER')
       Use REPORTDATE as escalation point and set REPEAT to false
       As escalation-action create an action that starts the
    workflow WOTESTDBS
    3) Create a route ROUTE-200 with 200 assets
    4) Create a workorder (I reference this workorder WO-MAIN) and
    apply ROUTE-200 => All 200 subworkflows are now in WAIT_NODE
    5) Create an action SET_DESC
       Object: WORKORDER
       Type: Set Value
       Value: 'Set by escalation'
       Parameter/Attribute: description
       Access by: ALL
    6) Create an escalation TOUCHWO
       Object: WORKORDER
       Where: parent = '<wonum of WO-MAIN>'
       Escalation Point: REPORTDATE
       Repeat: FALSE
       Action: SET_DESC
    
    Then let the escalation run.
    
    
    Reported Env.
    Maximo 7.1.1.4 with HF MBS_7114_LAFIX.20100212-0818.zip
    Language is German
    Win Server 2003 SP2 EE x64
    Oracle 10.2.0.4
    Websphere 6.1.0.27ND.
    clustered environment, eight servers, each hosting two nodes
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: all                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Problem description:                    *
    *                                                              *
    *                      I could narrow the problem down to the  *
    *                      following constellation:                *
    *                                                              *
    *                      The idea                                *
    *                                                              *
    *                      is that we create a route and all       *
    *                      workorders of the route stay            *
    *                                                              *
    *                      in a                                    *
    *                                                              *
    *                      workflow in a WAIT_NODE until we update *
    *                      them. The leaving of the                *
    *                                                              *
    *                      WAIT_NODE causes the session problem.   *
    *                                                              *
    *                      Steps to recreate provided by client:   *
    *                                                              *
    *                      1) Create a workflow WOTESTDBS based on *
    *                      Workorder: START --->                   *
    *                                                              *
    *                      WAIT_NODE ----> END                     *
    *                                                              *
    *                      The WAIT_NODE waits for                 *
    *                      maximo.workorder.update                 *
    *                                                              *
    *                      Set Workflow to enabled and active      *
    *                                                              *
    *                      2) Create an escalation WAKEUP that     *
    *                      puts all workorders that                *
    *                                                              *
    *                      have not been in workflow WOTESTDBS     *
    *                      into it. The SQL is                     *
    *                                                              *
    *                      something like                          *
    *                                                              *
    *                      istask=0 and workorderid not in (select *
    *                      ownerid from                            *
    *                                                              *
    *                      wfinstance where                        *
    *                      ownertable='WORKORDER')                 *
    *                                                              *
    *                      Use REPORTDATE as escalation point and  *
    *                      set REPEAT to false                     *
    *                                                              *
    *                      As escalation-action create an action   *
    *                      that starts the                         *
    *                                                              *
    *                      workflow WOTESTDBS                      *
    *                                                              *
    *                      3) Create a route ROUTE-200 with 200    *
    *                      assets                                  *
    *                                                              *
    *                      4) Create a workorder (I reference this *
    *                      workorder WO-MAIN) and                  *
    *                                                              *
    *                      apply ROUTE-200 => All 200 subworkflows *
    *                      are now in WAIT_NODE                    *
    *                                                              *
    *                      5) Create an action SET_DESC            *
    *                                                              *
    *                      Object: WORKORDER                       *
    *                                                              *
    *                      Type: Set Value                         *
    *                                                              *
    *                      Value: 'Set by escalation'              *
    *                                                              *
    *                      Parameter/Attribute: description        *
    *                                                              *
    *                      Access by: ALL                          *
    *                                                              *
    *                      6) Create an escalation TOUCHWO         *
    *                                                              *
    *                      Object: WORKORDER                       *
    *                                                              *
    *                      Where: parent = '<wonum of WO-MAIN>'    *
    *                                                              *
    *                      Escalation Point: REPORTDATE            *
    *                                                              *
    *                      Repeat: FALSE                           *
    *                                                              *
    *                      Action: SET_DESC                        *
    *                                                              *
    *                      Then let the escalation run.            *
    *                                                              *
    *                      Reported Env.                           *
    *                                                              *
    *                      Maximo 7.1.1.4 with HF                  *
    *                      MBS_7114_LAFIX.20100212-0818.zip        *
    *                                                              *
    *                      Language is German                      *
    *                                                              *
    *                      Win Server 2003 SP2 EE x64              *
    *                                                              *
    *                      Oracle 10.2.0.4                         *
    *                                                              *
    *                      Websphere 6.1.0.27ND.                   *
    *                                                              *
    *                      clustered environment, eight servers,   *
    *                      each hosting two nodes                  *
    *                                                              *
    *                      LOCAL FIX:                              *
    *                                                              *
    *                      None                                    *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    ****************************************************************
    DATABASE SESSIONS GROW WITH ROUTES IN WORKORDER ON CLUSTERED
    ENV
    

Problem conclusion

  • Database connection leak problem fixed.
    
    
    
    
    
    The fix for this APAR is contained in the following maintenance
    package:
    
      | release\fix pack | REL 7.1.1.8 - BS
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ86562

  • Reported component name

    MAXIMO SYS CONF

  • Reported component ID

    5724R46S1

  • Reported release

    711

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-10-12

  • Closed date

    2010-10-13

  • Last modified date

    2010-10-13

  • 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

    MAXIMO SYS CONF

  • Fixed component ID

    5724R46S1

Applicable component levels

  • R711 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Maximo Asset Management

Software version:

711

Reference #:

IZ86562

Modified date:

2010-10-13

Translate my page

Machine Translation

Content navigation