My Oracle Support Banner

Calculation on Calendar Preventive Maintenance (Doc ID 2731471.1)

Last updated on NOVEMBER 24, 2020

Applies to:

Oracle Utilities Work and Asset Management Enterprise Edition - Version 2.2.0.6.0 and later
Information in this document applies to any platform.

Goal

On : 2.2.0.6.0
We noticed that whenever Batch W1-MNTTR (Maintenance Trigger Periodic Monitor Process) is running, it is locking up the CI_SEQ table. When it does that, no one can create any transactions which uses CI_SEQ table to get the next sequence number. For now, we had to kill the Threadpool to stop this Batch and release the lock on the Sequence table.

WAM v2.2.0.6.0.096 000
Framework v4.4.0.2.0 007 000
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 Trigger Type: Calendar Anniversary, Template Work Order Type: General, Allow Multiple Flag: False
 Trigger Type: Calendar Anniversary, Template Work Order Type: General, Allow Multiple Flag: True
 Trigger Type: Calendar Anniversary, Template Work Order Type: Asset Location Specific, Allow Multiple Flag: False
 Trigger Type: Calendar Anniversary, Template Work Order Type: Asset Location Specific, Allow Multiple Flag: True
 Trigger Type: Calendar Interval, Template Work Order Type: General
 Trigger Type: Calendar Interval, Template Work Order Type: Asset Location Specific


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.