IV16582: SQL ERROR 17011 : EXHAUSTED RESULTSET APPROVING WORK ORDER IN TRANSPORTATION

APAR status

• Closed as program error.

Error description

• This case was already sent to Carey Clarke before, who sent some
  
  suggestions to the client, and according to client, here are the
  issues:
  
  This are two issues when approving a workorder through the
  Workorder
  Tracking (Tr) in the maximo demo application.
  a. Maximo sometimes gives sql error 17011 : Exhausted Resultset.
  b. When this issue happens, maximo session is stuck. The only
  choice is
  to close the browser and open a new one.
  
  
  Following are the steps to reproduce the issue. (attached
  screenshots on
  this location:
  https://ecurep.mainz.de.ibm.com/aexfiles/pmr/0/8/08112%2C499%2C0
  00/0-all
  _data/08112.499.000.issueReport.docx)
  
  1. The following is the demo installation version
  2. Open Workorder Tracking (Tr) and create a new workorder.
  Simply enter
  the required fields.
  3. Create 4 or more new tasks. Enter the basic required
  information.
  4. Approve the top level workorder. Make sure to hit OK right
  after
  changing the status in the status change dialog box.
  5. Sometimes Maximo gives the following pop up error message.
  6. The exception in the backend is as follows. The complete log
  file is
  attached with this report.
  
  The mboset has been closed. Check the log files in the home
  directory to
  determine the source and cause of the error.
  [2/22/12 9:13:47:113 EST] 00000ca4 SystemOut     O 22 Feb 2012
  09:13:47:113 [ERROR] [mx7dmo] [CID-UIASYNC-1104650] BMXAA6713E -
  The MBO
  fetch operation failed in the mboset with the SQL error code 1
  7011. The record could not be retrieved from the database. See
  the log
  file for more details about the error.
  java.sql.SQLException: Exhausted Resultset
          at
  oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMappi
  ng.java:
  70)
          at
  oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.j
  ava:131)
          at
  oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError
  .java:19
  7)
          at
  oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError
  .java:26
  1)
          at
  oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError
  .java:26
  9)
          at
  oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError
  .java:49
  0)
          at
  oracle.jdbc.driver.OracleResultSetImpl.getObject(OracleResultSet
  Impl.jav
  a:755)
          at
  oracle.jdbc.driver.OracleResultSet.getObject(OracleResultSet.jav
  a)
          at psdi.mbo.MboSet.getNextRecordData(MboSet.java:3095)
          at psdi.mbo.MboSet.fetchMbosActual(MboSet.java:2636)
          at psdi.mbo.MboSet.fetchMbos(MboSet.java:2602)
          at psdi.mbo.MboSet.getMbo(MboSet.java:1887)
          at
  psdi.webclient.system.beans.DataBean.getMbo(DataBean.java:4141)
          at
  psdi.webclient.beans.workorder.WOChangeStatusBean.execute(WOChan
  geStatus
  Bean.java:368)
          at
  psdi.plust.webclient.beans.plustwo.PlusTWOChangeStatusBean.execu
  te(PlusT
  WOChangeStatusBean.java:195)
          at sun.reflect.GeneratedMethodAccessor180.invoke(Unknown
  Source)
          at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
  Accessor
  Impl.java:37)
          at java.lang.reflect.Method.invoke(Method.java:611)
          at
  psdi.webclient.system.beans.DataBean.callBeanMethod(DataBean.jav
  a:6431)
          at
  psdi.webclient.system.beans.DataBean.callMethod(DataBean.java:62
  33)
          at
  psdi.webclient.system.beans.DataBean.callMethod(DataBean.java:62
  09)
          at
  psdi.webclient.system.session.AsyncProcess.run(AsyncProcess.java
  :138)
          at java.lang.Thread.run(Thread.java:736)
  [2/22/12 9:13:47:113 EST] 00000ca4 SystemOut     O 22 Feb 2012
  09:13:47:113 [INFO] [mx7dmo] [CID-UIASYNC-1104650] Correlated
  data:
  BEGIN UIClientIP:10.11.64.153 UserId:maxadmin AppName:plustwo
  UISes
  sionId:42 ElapsedTime:679 ms  END
  [2/22/12 9:13:47:418 EST] 00000038 SystemOut     O 22 Feb 2012
  09:13:47:418 [INFO] [mx7dmo] [CID-CRON-1104652] Correlation
  started.
  
  
  7. If the error doesn?t happen on the first try, change the
  status back
  to WAPPR and approve it again.
  8. Open the Workorder Tracking (OOB, non-Tr) application.
  9. Open the same workorder and approve. It goes through fine.
  
  https://ecurep.mainz.de.ibm.com/aexfiles/pmr/0/8/08112%2C499%2C0
  00/0-all
  _data/08112.499.000.issueReport.docx
  
  
  
  VERSION OF MAXIMO: 7.5 + Transportation
  

Local fix

• na
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Maximo Transportation 7.5                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Approving a work order with four or     *
  *                      more tasks on the Work Ordar Tracking   *
  *                      for Transportation application          *
  *                      sometimes results in a SQL ERROR 17011: *
  *                      Exhausted resultset                     *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  *                                                              *
  *                                                              *
  *                                                              *
  ****************************************************************
  SQL ERROR 17011 : EXHAUSTED RESULTSET APPROVING WORK ORDER IN
  TRANSPORTATION
  

Problem conclusion

• The problem cannot be reproduced with the latest transportation
  hot fix or with TPAE 7.5.0.2
  
  
  
  
  
  The fix for this APAR is contained in the following maintenance
  package:
  
    | release\fix pack | REL 7.5.0.0 TR HF
  

Temporary fix

Comments

APAR Information

• 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

  MX TRANSPORTATI

• Fixed component ID

  5724R5500

Applicable component levels

• R750 PSY

     UP