EWA Files with AUTOEXTEND increment > 100 M in BI system

[willi_eimler]

Hi,

my EWA states an alert because of the Oracle mini checks for our BI-system. It is the

"Files with AUTOEXTEND increment > 100 M"-alert. It raises, because all extent-sizes of the DB-files are 2GB. Our BI-team does not want to Archive data or compress fact tables so our DB grows and grows.

My question is:

Why should I reduce the AUTOEXTENT increment size to 100M? This would cause a lot of extent operations during data load in the night. The tablespaces are LTMS and so the high water mark is no reason for reducing the increment size. I don't see a benefit in reducing the increment size.

Please tell me your opinion!

Best regardsWilli Eimler

[willi_eimler]

Hi James,

thanx for your reply, but what's your opinion? Are my considerations right or not? Should I change the increment size anyway or not?

Best regards

Willi Eimler

[JamesZ]

Hi Willi,

As long as you are not suffering from performance, you can keep your current setting.

Best regards,
James

[JamesZ]

Hi,

The check is from SAP note 1615380 point 12. Please note this is a general recommendation for most of customers, but you can consider not to use based on your business scenario.

Best regards,
James