GReboute wrote:If you wanted to test Dan's suggestion, you could always grant the user account DBA access temporarily, and see if the failure still occurs. If it doesn't, then you know the problem relates to the siebel account, and that you're missing a grant somewhere. If you're concerned about doing that, you could create an account with the same permissions and grants as the siebel user, verify that the failure occurs, then grant that user the DBA role, and finally test to see if the failure occurs even with DBA permissions.
I don't understand what you mean exactly.
The guy connects to OEM with his account (account_guy_siebeladmin for ex.) navigate to the instance we granted him rights on, then he has to connect to the instance, OE asks for user/passwd, he inputs the siebel user/passwd => OEM is connected to the DB with siebel login.
account_guy_siebeladmin launch the SQL Tuning advisor, which runs its task, so far, so good. It is when he wants to APPLY tuning reco, he receive the errors.
So in my analyze, the priviliege issue is on the database siebel account => the one I provided grants extract in 1st post.