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)

Hash Partitioning on S_SRM_REQUEST_M7?

Sep 7, 2016 1:20PM in Siebel Business Process & Functionality (MOSC)

Oracle 11.2.0.4 Siebel 8.1.1.1 [21211]

Cust is noticing periodic spikes on their Database cluster. During these spikes there are hot blocks on the S_SRM_REQUEST index M7.

Customer has already implemented a reverse key (on S_SRM_REQUEST_P1). DB RAC team is exploring below options:

1] Would building a reverse index on M7?

(note the the first index-column is STATUS - and this is not a sequnce/number..)

2] Will it help to use a hash-partition on that index M7?

Is hash partitioning the solution and safe for other processing?

3] Any other implementation facing such hot block behavior on S_SRM_REQUEST M7 from other large customers?

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