Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Siebel Business Process & Functionality (MOSC)

Recommended stats collection for S_ORG_EXT table causing performance issue.

Jul 12, 2016 5:36PM edited Dec 14, 2016 4:00AM in Siebel Business Process & Functionality (MOSC) 2 commentsAnswered

We are using recommended method by oracle to collect stats on the S_ORG_EXT table using coe script as :--

:EXEC DBMS_STATS.GATHER_TABLE_STATS('"SIEBEL"', '"S_ORG_EXT"', estimate_percent => 10, method_opt => 'FOR ALL INDEXED COLUMNS SIZE 254', degree =>

DBMS_STATS.DEFAULT_DEGREE, cascade => TRUE);

But one of the query executing on the table is doing "full index scan" on S_ORG_EXT_M57 index which is a bad plan.

When collecting 100% stats for the table then it is using good plan which don't use the S_ORG_EXT_M57 index

Bad plan

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month