Slow/Poor Performance of PFT Allocation Processes on Exadata Machine
Last updated on MAY 18, 2017
Applies to:Oracle Financial Services Profitability Management - Version 6.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
For Oracle Financial Services Profitability Management (PFT) 6.x, after migrating to an Exadata machine, when running a batch of Allocations for a processing cycle, the Allocations are running much slower than they ran previously. Allocations that ran in seconds now take minutes. Allocations that ran in minutes now take hours.
In the AWR Report, the following two SQL are the longest running:
INSERT INTO FSI_M_DATA_IDENTITY_DETAIL (identity_code, as_of_date, src_drv_as_of_date, src_drv_type , row_count, balance , parent_identity_code, balance_type_cd ) SELECT :"SYS_B_00" , :"SYS_B_01" , :"SYS_B_02" , :"SYS_B_03" , TT.* , :"SYS_B_04" from ( select count( a.identity_code ), SUM(NVL(AVG_ASSET_BAL, :"SYS_B_05")), NVL( a.identity_code_chg , :"SYS_B_06" ) from ACCT_COST a where (((a.PRODUCT_ID < :"SYS_B_07" or a.PRODUCT_ID > :"SYS_B_08") and (a.PRODUCT_ID < :"SYS_B_09" or a.PRODUCT_ID > :"SYS_B_10"))) and a.as_of_date=:"SYS_B_11" group by NVL( a.identity_code_chg , :"SYS_B_12" ) ) TT
MERGE INTO LEDGER_STAT TARGET USING (SELECT * FROM (SELECT (SUM (IVW_SOURCE.IVWSRC_AMOUNT) * 1 ) BALANCE_AMOUNT, BOOK_CODE_ID,ORG_UNIT_ID, COMMON_COA_ID, PRODUCT_ID, USER_DIM1_D, USER_DIM2_ID, USER_DIM3_ID FROM ......
You do not understand why performance is so slow after moving to Exadata.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms