A huge FAGLFLEXA

[Former Member]

Hi,

We are running SAP ECC on Oracle Exadata in Oracle 11.2.0.4 database. The table FAGLFLEXA has reached a size of over 550 Gb and its 8 indexes reserve over 650 Gb.

Does anyone have experience with:

     1) a table partitioning in SAP

     2) SAP indexes on Exadata (are they all mandatory, are they any SAP rules and/or best practice for Exadata).

Many thanks for any hint!

[fidel_vales]

Hi,

partitioning without an analysis can cause performance issues.

We provide a "partitioning engine" that will partition some standard SAP tables but that one is not there.

Before checking partitioning I would check if the data can be archived/deleted/avoided as that usually is the case.

Depending on the activity it might be that the table is big (I saw that table reach several TB)