Expensive SQL
The newly upgraded 11.2.0.2 database is behaving strangely. The most expensive SQL, with respect to CPU consumption, is the following:
MERGE INTO sqlobj$auxdata USING dual ON (:1 IS NULL) WHEN MATCHED THEN
UPDATE SET description = :2, creator = nvl(:3, creator), origin = :4,
version = :5, created = :6, last_modified = :7, last_verified = nvl(:8,
last_verified), parse_cpu_time = null, optimizer_cost = nvl(:9,
optimizer_cost), module = nvl(:10, module), action = nvl(:11, action),
priority = nvl(:12, priority), optimizer_env = nvl(:13, optimizer_env),
bind_data = nvl(:14, bind_data), parsing_schema_name = nvl(:15,
parsing_schema_name), executions = nvl(:16, executions), elapsed_time =
nvl(:17, elapsed_time), cpu_time = nvl(:18, cpu_time), buffer_gets = nvl
(:19, buffer_gets), disk_reads = nvl(:20, disk_reads), direct_writes = nvl
MERGE INTO sqlobj$auxdata USING dual ON (:1 IS NULL) WHEN MATCHED THEN
UPDATE SET description = :2, creator = nvl(:3, creator), origin = :4,
version = :5, created = :6, last_modified = :7, last_verified = nvl(:8,
last_verified), parse_cpu_time = null, optimizer_cost = nvl(:9,
optimizer_cost), module = nvl(:10, module), action = nvl(:11, action),
priority = nvl(:12, priority), optimizer_env = nvl(:13, optimizer_env),
bind_data = nvl(:14, bind_data), parsing_schema_name = nvl(:15,
parsing_schema_name), executions = nvl(:16, executions), elapsed_time =
nvl(:17, elapsed_time), cpu_time = nvl(:18, cpu_time), buffer_gets = nvl
(:19, buffer_gets), disk_reads = nvl(:20, disk_reads), direct_writes = nvl
0