|
|
|
Oracle Text Commit new id Allocation Trend:
An Excerpt from SGA Stat: SQL> select a.instance_number,begin_interval_time, bytes from dba_hist_sgastat a, dba_hist_snapshot b 2 where pool='shared pool' and 3 a.snap_id=b.snap_id and 4 a.instance_number=b.instance_number and 5 name='Oracle Text Commit new id' 6 order by begin_interval_time; ..... 1 06/10/2010 01:00:07,750 352864368 1 06/10/2010 02:00:55,107 353711568 ..... 1 12/10/2010 11:00:12,212 448444792 1 12/10/2010 12:00:27,412 449299672 1 12/10/2010 13:00:12,435 450157752 1 12/10/2010 14:00:19,294 450179512 ..... 1 04/11/2010 14:31:10,604 1622639416 1 04/11/2010 14:40:18,341 1623339552 1 04/11/2010 14:50:28,971 1623879936 1 04/11/2010 15:00:40,721 1623880712 722 rows selected. SQL> Oracle Text Commit new id had increased in small sizes. Summary:
Root Cause: This problem is Oracle BUG:8593562 encountered in Oracle Text environment. ..... It is incremented as the space is allocated, but not decremented as it is freed. It will reset when the instance is restarted. ..... The bug is currently in work by Development and expected to be resolved in a future release. ..... Ref: Growth of "Oracle Text Commit new id" memory with Sync on Commit Index [ID 872413.1] Workaround:
|
The Requested SUBPOOL:
The allocation was requested from sga heap(3,0), which is (SUBPOOL:3,DURATION:0).
All SUBPOOLS and Their DURATION Memories:
All PERMANENT SPACES were allocated in DURATION 0. Although there are enough free spaces in the other DURATIONS of (3,1),(3,2),(3,3); free space can not be allocated from them.
Ref: Oracle Bug 9911213: ORA-04031 AFTER APPLYING 10.2.0.4 PATCSHET
Since the lower limit of BUFFER CACHE was determined by DB_CAHCE_SIZE parameter; SHARED POOL could not grow by allocating a new EXTENT, then ORA-4031 appeared.
SUBPOOL Allocations:
The total size of Oracle Text Commit new id is 1.5GB (399237696+392833064+417149240+410783408). It's high.