Trimming BI Apps ODI Repository

The ODI repository that is shipped by Oracle and deployed by customers contains all content supported by BI Applications. This repository can
be relatively large (relative to the database it is deployed on) which can impact database performance and ODI responsiveness. For example,
ODI Studio will be more responsive if it can populate navigation windows with fewer objects. Patches will be applied more quickly if there are
fewer objects that need to be patched.

Trimming content is not suggested as a best practice after deployment. This is just guidance for customers who may be experiencing issues due
to the large size of the ODI repository.

Oracle does not provide an automated mechanism to trim the ODI repository. Users must manually trim out content they are not using. There
are two ways to consider trimming the ODI repository - removing source adaptors that you do not use and trimming subject areas that you are not
using. Due to the deep inter-dependencies and overlaps between subjects areas, we do not provide guidance on how to trim ODI objects related
to offerings, functional areas or fact groups. However, there is no overlap between source specific objects so you can safely remove content
specific to a particular source system. By source system, we are referring to a particular product line version. For example, you can remove the
eBusiness Suite R12 content without impacting anything related to Siebel, PeopleSoft, JD Edwards, Fusion content as these are all completely
different product lines. You can also delete a different eBusiness Suite product line version such as R1211 or R122 - though part of the same
product line, these are separate versions within that product line and have no overlapping dependencies.

Once deleted, it is very difficult to bring a particular adaptor back. Deleting an adaptor can also cause errors in BIACM if you attempt to
register a source that has been removed from ODI.

Remove A Source Adaptor

Steps Object Name Screenshot

SDE_FUSION_V1_Adaptor
Delete Adaptor Folder SDE_JDEE1_90_Adaptor
SDE_JDEE1_91_Adaptor
Navigate to ODI Studio - Designer - Projects
SDE_ORA11510_Adaptor
- BI Apps Project - Mappings
SDE_ORAR1211_Adaptor
Select the Adaptor folder and either press SDE_ORAR1212_Adaptor
the 'Delete' or select the Delete option from SDE_ORAR1213_Adaptor
the right click menu SDE_ORAR122_Adaptor
SDE_ORAR12_Adaptor
SDE_PSFT_90_Adaptor
SDE_PSFT_91_Adaptor
SDE_PSFT_92_Adaptor
SDE_SBL_811_Adaptor
SDE_SBL_822_Adaptor
SDE_Universal_Adaptor

Delete Upgrade Adaptor

Most of the Source Adaptor folders have a
corresponding 'Upgrade' folder.

Delete this folder also. This ensures that

there should be no interfaces referencing a
source specific datastore

Delete Model
Navigate to ODI Studio - Designer - Models
Expand the Model Folder to expose the
Models. Most sources have a separate
'Source Files' model.
Edit each Model in the Folder and make a
note of the 'Logical Schema' attribute. We
will be deleting these later.
Close the Model.
Delete the Model Folder using the Delete key
or the Delete option from the pop up menu.
Fusion 1.0
Oracle Fusion 1.0 CRM
Oracle Fusion 1.0 FSCM
Oracle Fusion 1.0 HCM
Oracle Fusion 1.0 Source Files
JD Edwards 9.0
JD Edwards EnterpriseOne 9.0 Control
JD Edwards EnterpriseOne 9.0 Data
JD Edwards EnterpriseOne 9.0 Data
Dictionary
JD Edwards EnterpriseOne 9.0 Source Files
JD Edwards EnterpriseOne 9.0 System
JD Edwards 9.1
JD Edwards EnterpriseOne 9.1 Control
JD Edwards EnterpriseOne 9.1 Data
JD Edwards EnterpriseOne 9.1 Data
Dictionary
JD Edwards EnterpriseOne 9.1 Source Files
JD Edwards EnterpriseOne 9.1 System
Oracle E-Business Suite 11.5.10
Oracle E-Business Suite 11.5.10
Oracle E-Business Suite 11.5.10 Source
Files
Oracle E-Business Suite R12
Oracle E-Business Suite R12
Oracle E-Business Suite R12 Source Files
Oracle E-Business Suite R12.1.1
Oracle E-Business Suite R12.1.1
Oracle E-Business Suite R12.1.1 Source
Files
Oracle E-Business Suite R12.1.2
Oracle E-Business Suite R12.1.2
Oracle E-Business Suite R12.1.2 Source
Files
Oracle E-Business Suite R12.1.3
Oracle E-Business Suite R12.1.3
Oracle E-Business Suite R12.1.3 Source
Files
Oracle E-Business Suite R12.2
Oracle E-Business Suite R12.2
Oracle E-Business Suite R12.2 Source Files
PeopleSoft 9.0/PeopleSoft 9.0 CS
PeopleSoft 9.0 CS
PeopleSoft 9.0/PeopleSoft 9.0 FNSCM
PeopleSoft 9.0 FNSCM
PeopleSoft 9.0 FNSCM Source Files
PeopleSoft 9.0/PeopleSoft 9.0 HCM
PeopleSoft 9.0 HCM
PeopleSoft 9.0/PeopleSoft 9.0 LM
PeopleSoft 9.0 LM
PeopleSoft 9.1/PeopleSoft 9.1 CS
PeopleSoft 9.1 CS
PeopleSoft 9.1/PeopleSoft 9.1 FNSCM
PeopleSoft 9.1 FNSCM
PeopleSoft 9.1 FNSCM Source Files
PeopleSoft 9.1/PeopleSoft 9.1 HCM
PeopleSoft 9.1 HCM
 PeopleSoft 9.1/PeopleSoft 9.1 LM
PeopleSoft 9.1 LM

PeopleSoft 9.2/PeopleSoft 9.2 CS

PeopleSoft 9.2 CS

PeopleSoft 9.2/PeopleSoft 9.2 FNSCM

PeopleSoft 9.2 FNSCM
PeopleSoft 9.2 FNSCM Source Files

PeopleSoft 9.2/PeopleSoft 9.2 HCM

PeopleSoft 9.2 HCM

PeopleSoft 9.2/PeopleSoft 9.2 LM

PeopleSoft 9.2 LM

Siebel 8.1.1
Siebel 8.1.1
Siebel 8.1.1 Source Files

Siebel 8.2.2
Siebel 8.2.2
Siebel 8.2.2 Source Files

Universal
Universal Source Files

AGILE_PLM_9_3_1
Delete Load Plan
Components AGILE_PLM_9_3_2

AGILE_PLM_PROC_6_1
Navigate to ODI Studio - Designer - Load
Plans And Scenarios EBS_11_5_10
Expand BIAPPS Load Plan - Load Plan EBS_12_0
Components - SDE
EBS_12_1_1
Delete the Load Plan folder that corresponds
to the adaptor you are removing. EBS_12_1_2

EBS_12_1_3

EBS_12_2

FUSION_1_0

JDE_9_0

JDE_9_1

PSFT_9_0

PSFT_9_1

PSFT_9_2

SEBL_8_1_1

SEBL_8_2_2

UNIVERSAL
Delete Logical Schema
Navigate to ODI Studio - Topology -
Technologies

Under the appropriate technology ('Oracle'

for relational based sources, 'File' for file
based sources and 'Oracle BI' for Fusion
sources), locate the logical schema
associated with the adaptor you noted in the
'Delete Model' step. Select it and delete it
using the Delete key or 'Delete' pop up menu
option.

The Adaptor specific logical schemas have

'DS_' as a prefix. Do not delete any other
logical schema.

Potential Gotcha
You can delete multiple adaptors by selecting multiple Adaptor folders, models or load plan component folders at the same time. Some
users have encountered issues when deleting a very large number of objects. Deleting more than one source adaptor or model at the
same time may not result in issues, especially for some of the adaptors with less content. However, be aware when deleting source
adaptors that have a lot of associated content.