Troubleshooting
Problem
An issue similar to the following scenario might be experienced: the Maximo WOGEN table has more than 172 million records generated by 1pm on one Work Order record.
Symptom
Comments in the code say things like "wogen is a scratch pad" and "RUNDATE can be used to delete old runs that didn't get deleted when they should have."
This implies it can be truncated to clear debris when the crontask is not running.
The LONGDESCRIPTION table might also grow in size.
There are 27443757 records in WOGEN table.
Since the Description field for each record in WOGEN table is also stored in the LONGDESCRIPTION table, the WOGEN also has 27443757 records corresponding to WOGEN records
The SQL query below returns 27443757 records.
select COUNT (*) from LONGDESCRIPTION where LONGDESCRIPTION.ldownertable = 'WOGEN'
Cause
This could be caused by a data problem in the database. From the Assets application, Meters tab, if there is a negative value on the Average Units per Day, and this asset has been attached to a PM record, it may cause the PM to generate Work Orders non-stop.
Resolving The Problem
Stopping and starting the Maximo application server from the Websphere console will fix the problem.
It is safe to delete these unwanted records from the WOGEN table and WOGEN-related records from the LONGDESCRIPTION table:
select count(*) from WOGEN
select count(*) from LONGDESCRIPTION where LONGDESCRIPTION.ldownertable = 'WOGEN'
If it takes too long to delete hundreds of millions of records, then truncate the WOGEN table data via a database backend SQL script.
Turn on SQL logging to collect log files before bouncing the server. Then turn off SQL logging once the log files have been collected.
Was this topic helpful?
Document Information
More support for:
IBM Maximo Asset Management
Software version:
Version Independent
Operating system(s):
AIX, HP-UX, Linux, Solaris, Windows
Document number:
492127
Modified date:
17 June 2018
UID
swg21636637