Instructions 18802097 Gatherstats Recon FS SIL 11.1.1.7.1
Instructions 18802097 Gatherstats Recon FS SIL 11.1.1.7.1
Instructions 18802097 Gatherstats Recon FS SIL 11.1.1.7.1
Solution:
DiffManLoad mappings are sourced from the reconciliation staging tables
(RECON_FS tables mentioned below) which are populated by the
DiffManDerive mappings for each module. Once the DiffManDerive mappings
are complete in the LP, the statistics are not gathered for the RECON_FS
tables thus causing the optimizer to use the last available stats on the
RECON_FS tables which could be from a previous run and hence the optimizer
chooses a wrong path which leads to performance issues.
So, as a solution we will add a step to gather stats on RECON_FS table before
the actual DiffManLoad mappings run.
Steps: ODI Changes
1) Login to ODI Designer tab.
2) Open Load Plans and Scenarios and then expand BIAPPS Load
Plan and find Load Plan Dev Components
3) Expand SIL option inside Load Plan Dev Components
4) This tech note explains the steps by considering AP module as an
example. Please follow the same steps for each module. All the necessary
information for each module is given in the table in step 9 below.
5) Find the load plan component 3 SIL Fact APTRANS_FG for AP. Open this
load plan component to edit it.
6) You will have to add the EXEC_TABLE_MAINT_PROC scenario just before
the DiffManLoad scenario.
9) Repeat the steps from 5 through 8 for each module mentioned in the table
below. The necessary information for each module is present in the same
table.
MODU
LE
AP
AR
GLREV
N
GLCOG
S
Load Plan
Components
3 SIL Fact
APTRANS_FG
3 SIL Fact
ARTRANS_FG
3 SIL Fact GLREVN_FG
3 SIL Fact GLCOGS_FG
RECON_FS table
for each module
W_AP_XACT_RECON
_FS
W_AR_XACT_RECO
N_FS
W_GL_REVN_RECO
N_FS
W_GL_COGS_RECO
N_FS
Name of DiffManLoad
Scenario in LP
SIL_APTRANSACTIONFACT_DIFFMA
NLOAD
SIL_ARTRANSACTIONFACT_DIFFMA
NLOAD
SIL_GLREVENUEFACT_DIFFMANLO
AD
SIL_GLCOGSFACT_DIFFMANLOAD
10)
Generate a new load plan after making these changes and carry out
incremental load.