IBM Support

IV91129: SYSTEM GENERATES LESS PM WORK ORDERS THAN IT SHOULD

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Steps to replicate the issue:
    
    1) Go to Assets application
    
    2) Create an Asset record associated to the ODOM-KM Meter
    
    3) Change the Assets Status to OPERATING
    
    4) Go to Preventive Maintenance application
    
    5) Create and activate multiple Meter-Based PM records against
    the Asset above as the following:
    
    Use Last Work Order's Start Date to Calculate Next Due Date? =
    No
    Generate Work Order Based on Meter Readings (Do Not Estimate)? =
    Yes
    Generate Work Order When Meter Frequency is Reached? = Yes
    
    16 PM records with:
    Frequency = 6,400
    
    04 PM records with:
    Frequency = 12,800
    
    02 PM records with:
    Frequency = 32,000
    
    02 PM records with:
    Frequency = 38,400
    
    02 PM records with:
    Frequency = 51,200
    
    05 PM records with:
    Frequency = 76,800
    
    01 PM record with:
    Frequency = 102,400
    
    01 PM record with:
    Frequency = 115,200
    
    01 PM record with:
    Frequency = 120,000
    
    6) Go to Assets application
    
    7) Bring up the Asset above and enter a Meter Reading whose
    Delta is 6,400
    
    The expect result is: 16 PM Work Orders should be generated.
    
    The issue is: system randomly creates less PM Work Orders than
    it should. The logs shows up the following error:
    
    [17/11/16 09:48:40:666 COT] 0045c8b8 SystemOut     O 17 nov 2016
    09:48:40:666 [INFO] [MAXIMO] [] BMXAA6719I - USER = (MAXADMIN)
    SPID = (96) app (null) object (ASSETTRANS) : select * from
    assettrans
    
     where assetid = 1304 and datemoved <= { ts '2016-11-17
    09:47:59.172' } and (toparent is not null or fromparent is not
    null) order by datemoved desc OPTION (FAST 1000)
    [17/11/16 09:48:40:682 COT] 0045c8b8 SystemOut     O 17 nov 2016
    09:48:40:682 [ERROR] [MAXIMO] [] BMXAA6713E - The MBO fetch
    operation failed in the mboset with the SQL error code 3989. The
    record
    
    could not be retrieved from the database. See the log file for
    more details about the error.
    com.microsoft.sqlserver.jdbc.SQLServerException: New request is
    not allowed to start because it should come with valid
    transaction descriptor.
     at
    com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabase
    Error(SQLServerException.java:216)
     at
    com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.jav
    a:254)
     at
    com.microsoft.sqlserver.jdbc.SQLServerResultSet$FetchBuffer$Fetc
    hBufferTokenHandler.onEOF(SQLServerResultSet.java:4783)
     at
    com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:84)
     at
    com.microsoft.sqlserver.jdbc.SQLServerResultSet$FetchBuffer.next
    Row(SQLServerResultSet.java:4849)
     at
    com.microsoft.sqlserver.jdbc.SQLServerResultSet.fetchBufferNext(
    SQLServerResultSet.java:1781)
     at
    com.microsoft.sqlserver.jdbc.SQLServerResultSet.next(SQLServerRe
    sultSet.java:1062)
     at psdi.mbo.MboSet.getNextRecordData(MboSet.java:3304)
     at psdi.mbo.MboSet.fetchMbosActual(MboSet.java:2846)
     at psdi.mbo.MboSet.fetchMbos(MboSet.java:2803)
     at psdi.mbo.MboSet.getMbo(MboSet.java:2050)
     at
    psdi.plust.app.contract.PlusTContractService.getParentAsset(Plus
    TContractService.java:2006)
     at
    psdi.plust.app.contract.PlusTContractService.checkIterAssetFllCv
    r(PlusTContractService.java:2028)
     at
    psdi.plust.app.contract.PlusTContractService.findOneWOFullCovera
    ge(PlusTContractService.java:1628)
     at
    psdi.plust.app.workorder.PlusTWO.warrantyWOValidation(PlusTWO.ja
    va:1409)
     at
    psdi.plust.app.workorder.PlusTWO.performWarrantyLogicValidation(
    PlusTWO.java:1344)
     at
    psdi.plust.app.workorder.PlusTWO.setAttrFromWoGen(PlusTWO.java:2
    804)
     at psdi.app.pm.PM.generateWorkOrderInformation(PM.java:2478)
     at psdi.app.pm.PM.wogen(PM.java:2022)
     at psdi.app.pm.PM.generateWork(PM.java:1674)
     at psdi.plust.app.pm.PlusTPM.generateWork(PlusTPM.java:299)
     at
    psdi.app.pm.PMService$BackGroundWogen.run(PMService.java:455)
     at java.lang.Thread.run(Thread.java:853)
    

Local fix

  • No workaround has been found.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * SYSTEM GENERATES LESS PM WORK ORDERS THAN IT SHOULD          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:
    	 | release\fix pack | Interim Fix for Release 7.6.0.8 Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV91129

  • Reported component name

    PREVENTIVE MAIN

  • Reported component ID

    5724R46PM

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-11-30

  • Closed date

    2016-12-13

  • Last modified date

    2016-12-13

  • 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

    PREVENTIVE MAIN

  • Fixed component ID

    5724R46PM

Applicable component levels

  • R760 PSY

       UP



Document information

More support for: Maximo Asset Management
Prev Maint

Software version: 760

Reference #: IV91129

Modified date: 13 December 2016