Last updated on JANUARY 04, 2016
Applies to:Oracle Cost Management - Version 188.8.131.52 and later
Information in this document applies to any platform.
On : 184.108.40.206 version, Performance
Ran Cost Rollup - No Report for a category that contains ~110,000 items. After ~30 hours, it encountered a snapshot too old error and rolled back its changes.
Rescheduled same Cost Rollup - No Report ensuring that no big jobs would be running to contend for undo--It's still running (~39 hours), and hasn't even advanced past where the original run hit the snapshot too old error.
Portion of long-running statement is: INSERT INTO CST_ITEM_COST_DETAILS (INVENTORY_ITEM_ID, COST_TYPE_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, ORGANIZATION_ID, OPERATION_SEQ_NUM, LEVEL_TYPE, ACTIVITY_ID, RESOURCE_ID, RESOURCE_RATE, USAGE_RATE_OR_AMOUNT, BASIS_TYPE, BASIS_FACTOR, NET_YIELD_OR_SHRINKAGE_FACTOR, ITEM_COST, COST_ELEMENT_ID, ROLLUP_SOURCE_TYPE, REQUEST_ID, PROGRAM_APPLICATION_ID,...
The rollup to have better performance and complete
The issue can be reproduced at will with the following steps:
1. Launch the Cost Rollup
2. Monitor for the request to complete
3. The request does not complete and is stopped
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms