Workaround:
1. Apply patch 13911083.
Check the Oracle patch in Metalink, at this time(Feb 2013) there are patches on Linux/HP platform, but regarding AIX platform there are no patches.
OR
2. Flush SHARED_POOL
For clearing up the dirty cursors related to GV$INSTANCE query, issue below command in the problematic instance(s).
SQL> ALTER SYSTEM FLUSH SHARED_POOL;
If you may startup database instance, it's a better approach.
OR
3. Purge the individual cursor in shared_pool.
With below query, you could check the problematic cursor and there is one cursor with 0 value of executions(for example, in the third line).
set linesize 190
col module for a30
col sql for a40
select
a.parsing_schema_name
,a.sql_id
,a.plan_hash_value
,a.child_number "C_N"
,substr(a.sql_text,1,40) "SQL"
,a.executions,module
,rows_processed
,elapsed_time "Elapsed(ms)"
from v$sql a
where module like 'sp_ocap%'
/
PARSING_SCHEMA_NAME SQL_ID PLAN_HASH_VALUE C_N SQL EXECUTIONS MODULE ROWS_PROCESSED Elapsed(ms)
-----------------------------------------------------------------------------------------------------------------------
SPLEX1 b8w73kk02t0yk 2256767838 0 select obj# from sys.obj$ where name='CO 7 sp_ocap@chnodbp1 (TNS V1-V3) 7 1516
SPLEX1 9byphngbzp47f 3668658350 0 select count(*) from gv$instance where s 751 sp_ocap@chnodbp1 (TNS V1-V3) 750 19999413
SPLEX1 9byphngbzp47f 3668658350 1 select count(*) from gv$instance where s 0 sp_ocap@chnodbp1 (TNS V1-V3) 0 262664
Pick the SQL_ID and use that information in the below query for getting ADDRESS+HASH_VALUE value.
select address||','||hash_value into :name
from v$sqlarea
where sql_id = '9byphngbzp47f';
ADDRESS||','||HASH_VALUE
--------------------------------------------------------------------------------
070000035F8FA698,3623522542
After that, execute purge procedure as follows and then start Capture process again.
alter session set events '5614566 trace name context forever';
exec dbms_shared_pool.purge('070000035F8FA698,3623522542','C',1);
After applying one workaround of them, start Capture again to see if there is still any problem processing the message.
