What is the Best Practice Approach to the Order of Columns in the FEM_BALANCES_P?
Last updated on OCTOBER 04, 2016
Applies to:Oracle Enterprise Performance Foundation - Version: 11.5.10
Oracle Profitability Manager - Version: 11.5.10 to 12.0.0
Information in this document applies to any platform.
Need guidance on best approach to the order of columns on FEM_BALANCES_P, the primary, unique processing key index.
Built the index as:
drop INDEX FEM.FEM_BALANCES_P;
CREATE UNIQUE INDEX FEM.FEM_BALANCES_P
PCTFREE 10 INITRANS 11 MAXTRANS 255
STORAGE(INITIAL 32768 FREELISTS 4 FREELIST GROUPS 4)
TABLESPACE APPS_TS_TX_IDX LOGGING ;
During operations of Oracle Profitability Manager (PFT) , found a series of statements that caused over 38 million disk reads. Examination of the columns showed that there is a lot of low selective columns at the start.
Q1: Can you change the ORDER of the Unique Index/Processing Key for FEM_BALANCES without invalidating existing Mapping Rules?
Q2: What is the best practice approach to the order of columns in the FEM_BALANCES_P index.?
Q3: During some operations we observed executions that caused huge I/O reads and high CPU?
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