Tuning Siebel on Exadata

Hi,

We are running Siebel 8.2 on Oracle 11G Exadata. We have been tuning our sql using baselines.

This is proving to be high maintenance since the sql change frequently due to config change or users (changing columns to display etc).

We used to run our Siebel application on SQL Server before and when we tuned a sql (usually with an index) it fixed that query and also similar query.

All Siebel connections have the following session settings

ALTER SESSION SET OPTIMIZER_MODE = FIRST_ROWS_10 ;

ALTER SESSION SET HASH_JOIN_ENABLED = FALSE ;

ALTER SESSION SET "_OPTIMIZER_SORTMERGE_JOIN_ENABLED" = FALSE ;

ALTER SESSION SET "_OPTIMIZER_JOIN_SEL_SANITY_CHECK" = TRUE ;