My Oracle Support Banner

Heavy Processing And Slow Response Time Of Delete Statement In EAMFOGEN (Generate EAM Forecast) (Doc ID 1477424.1)

Last updated on FEBRUARY 10, 2021

Applies to:

Oracle Enterprise Asset Management - Version 12.1.3 and later
Information in this document applies to any platform.


On : 12.1.3 version, PERF

When attempt to run the Generate eAM Forecast concurrent job (EAMFOGEN), the process is creating blocking locks on CST_EAM_ASSET_PER_BALANCES and the delete statement on that table is taking up a lot of processing. It was found that putting an index on the table has resolved the issue with this table and the blocking locks.
Customer would like Dev to provide a patch that puts this index on the table.
Customer would also like Dev to review the processing time this job uses as there are no major queries running for a long time but the job takes a lot of CPU when it runs.
We are specifically running it for a forecast of future material and labor requirements, not a look at the past.

There is no performance issue in running the Generate eAM Forecast concurrent job (EAMFOGEN)

The issue can be reproduced at will with the following steps:
1. Responsibility: Enterprise Asset Management
2. Create forecast and generate it.
   Customer are creating a forecast for Forecasted Work for a year date range in the future.

The issue has the following business impact:
Due to this issue, users cannot get decent performance to run Generate eAM Forecast.


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

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