database statistics not re-calculated

[former_member204746]

Hi,

I am using:

R/3 4.7 ext.200

Windows 2003 SP2

Oracle 10.2.0.2

BRTOOLS 7.00 (patch 24)

I noticed that some tables such as EKPO did not have updated statistics since January 2007. After investigation, it seems that initSID.sap uses a default value: stats_change_threshold = 50

What are you using as a value for this parameter, I am planning to use 10.

Thanks to all in advance for replies.

[Former Member · Accepted solution]

That's normal with the Cost-Based Optimizer for Statistics.

SAP knows what tables need statistics or not.

Have you see this ?:

http://help.sap.com/saphelp_46c/helpdata/en/c4/3a65e9505211d189550000e829fbbd/content.htm

http://help.sap.com/saphelp_46c/helpdata/en/c4/3a65cf505211d189550000e829fbbd/content.htm

Regards.

[former_member204746 · Accepted solution]

thanks for your answer. I read both of your links. I use brconnect instead of SAPDBA but i do understand that this mechanism has not really changed.

EKPO is not an entry in table DBSTATC.

I was just wondering if anyone has tweaked stats_change_threshold to any other value than default 50. I feel that 50 is too high and that stats are not calculated as often as they shouldm especially for huge table such as EKPO.

[Former Member · Accepted solution]

Hi Eric,

I was reading too long in the marketplace, the SDN and the help of SAP and I have yet some doubts (black holes) about how SAP is able to maintain the DBSTATC table himself.

I see in some customers tables without statistics for one or two years and in my company the same. Tables like the MARA without statistics from 1/1/07 isn't normal.....

but sometimes we've to believe in SAP, not ??

regards.

P.D.: If I see some new I'll tell you.

[former_member204746 · Accepted solution]

thanks Albert, hopefully someone else as a clue on this issue

[Former Member · Accepted solution]

Eric,

From what I can see, the DBSTATIC table has little bearing on the overall activity in the system. I.E. I have an ECC 5.0 system with 470 entries in the table, but I process 44,000+ tables when we trigger a full stats run.

All I can find on stats_change_threshold is that it must be greater than zero: http://help.sap.com/saphelp_bw30b/helpdata/en/02/0ae0c6395911d5992200508b6b8b11/content.htm - looks like if you lower the number to 10, you'll definatly increase the scope of the tables included in the stats run.

Maybe if you tested at a number like 30 first, you could confirm this. I'd just be concerned that if you have a particularly large database, you could begin eating up disk with new index contents. Not an extreme possibility, but small steps as you work to 10.

Let me know if you try this. This is new inforamtion to me as well.

Thanks!

Tim