This content has been marked as final. Show 5 replies
Trace it and see what you're waiting on.
Agreed with Dom: tracing will tell you what it's actually doing. If you can't access the session or otherwise can't trace, you can use ASH, but lose granularity.
It isn't the Exadata ... it is the database.
As already suggested ... find out why by tracing.
Does your table happen to be highly partitioned?
Edited by: BobCarlin on May 23, 2012 9:43 PM
In the former plataform, it was already 11g?
11g increased the usage of mutex changing completly the internal behaviour from 10g.