| CMCICU Standard Cost Update Poor Performance or not Completing (文档 ID 234023.1) |  转到底部 |  |
APPLIES TO:Oracle Cost Management - Version 11.5 and laterInformation in this document applies to any platform. Standard Cost Update - CMCICU *** Checked on Relevance on 02-AUG-2018 *** PURPOSEThe update standard cost process is perhaps one of the most used processes within Oracle Cost Management. 1) CST_STD_COST_ADJ_TEMP TROUBLESHOOTING STEPSPerformance issues may arise due to the amount of data being passed through the tables and indexes. Proactive performance fixes (Doc ID 117129.1) (Doc ID:117129.1) Oracle provides several processes to improve performance of the update standard cost process. 1) Purge Standard Cost History (CSTCSPCH).
(Doc ID:117129.1) 2) Purge Cost Type Information (CSTCSPCT).
(Doc ID 117129.1)
3. Checklist for update standard cost performance.
a. Purge the cost types that you do not need.
b. Delete the negative cost_type_id from the cst_item_costs and cst_item_cost_details tables. The negative cost_type_id is created whenever a cost update
is aborted, so you may want to periodically check for negative cost_type_id records and delete them.
c. Periodically purge the cost update history. This clears out some of the tables and benefits the performance. Obtain a count on tables where the trace
file indicates a performance issue. Performance issues arise when tables have large amounts of records.
d. Truncate temporary tables, i.e., cst_std_cost_adj_temp. These tables grow if cost update is run with the CST debug profile set to Full.
The following tables can be truncated for performance. Be sure there are no cost processes running when truncating these tables:
CST_LOW_LEVEL_CODES e. Verify that you have the latest versions of the following files:
cmliru.lpc f. For 11i and R12, Run Gather Schema Stats for the CST_ITEM_COSTS and CST_ITEM_COST_DETAILS tables.
g. Use the cost update option "item cost only" as opposed to the update options that include resource and overhead activity.
h. When using the Resource and Overhead activity parameter for the cost update, performance can be impacted if there are a large number of unclosed discrete
jobs. Because the cost update process impacts open jobs, the number of open jobs directly impacts performance. Performance can be degraded with a large number
of discrete jobs and using the item cost only option. Performance degradation will be impacted even more with a large number of open discrete jobs and using the
resource and overhead parameter for the update process.
For Release 11i, please review Note 467719.1 For R12, please review <Doc ID 750331.1>.
If the action plan above does not solve your performance issue, please perform the following action plan
SOLUTION
EBS 11.5.10.2 1. Download and review the readme and pre-requisites for Patch 17450072, now superseded use Replacement Patch 19666156. 2. Ensure that you have taken a backup of your system before applying the recommended patch. 3. Apply the patch in a test environment. 4. Confirm the following file versions or higher exist after patch applications: cmlwru.lpc 115.32.115100.34 You can use the commands like the following: 5. Retest the process 6. Migrate the solution as appropriate to other environments.
EBS 12.0.X 1. Download and review the readme and pre-requisites for Patch 8442125:R12.BOM.A, now superseded, use Replacement Patch 11729160:R12.BOM.A. 2. Ensure that you have taken a backup of your system before applying the recommended patch. 3. Apply the patch in a test environment. 4. Confirm the following file versions or higher exist after patch applications: cmlicu.lpc 120.6.12000000.7 You can use the commands like the following: 5. Retest the process 6. Migrate the solution as appropriate to other environments.
EBS 12.1.X To implement the solution, please execute the following steps: 1. Download and review the readme and pre-requisites for Patch 22053665:R12.BOM.C. 2. Ensure that you have taken a backup of your system before applying the recommended patch. 3. Apply the patch in a test environment. 4. Confirm the following file versions or higher exist after patch applications: cmlwru.lpc 120.9.12010000.8 You can use the commands like the following: 5. Retest the process 6. Migrate the solution as appropriate to other environments.
EBS 12.2.X To implement the solution, please execute the following steps: 1. Download and review the readme and pre-requisites for Patch 25792415:R12.BOM.D. 2. Ensure that you have taken a backup of your system before applying the recommended patch. 3. Apply the patch in a test environment. 4. Confirm the following file versions or higher exist after patch applications: cmlwru.lpc 120.11.12020000.10 You can use the commands like the following: 5. Retest the process 6. Migrate the solution as appropriate to other environments.
Other Actions to be Considered In case patch does not resolve the performance issue, we may be facing a new situation. In this case please log a Service Request providing the following required information:
ACTION PLAN Please answer/upload/read/proceed with the following: 1. Please read <Doc ID 378348.1> Data Collection Scripts for Cost Management. (For R11 and R12). Upload the output of the following costing diagnostic script: CstCheck.sql (Cost Collector Script, shows cost setup by organization, File versions, invalid objects. Customer name is a required input and can be any name and is used for the name of the report. The output will be spooled as file name CstDiag115.txt) 2. Upload Standard Cost Update log file for the process with performance issue. 3. Generate TKPROF Trace File and upload RAW and TKPROF Trace files. For more information about generating trace files review the following document.
REFERENCESNOTE:117129.1 - How to get a Trace first And Begin to Analyze a E-Business Applications Performance IssueNOTE:1665376.1 - How to Resolve Performance Issues in Cost Management NOTE:1588583.1 - CMCICU: Update Standard Cost Process having performance issue or not completing |
扫一扫
1581
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
