ERROR OGG-02028 Failed to attach to logmining server Error code 12801,
error message: ORA-12801: error signaled in parallel query server P080, instance psin9p623:UA01OSL2 (2)
ORA-12853: insufficient memory for PX buffers: current 4478816K, max needed 52002720K
ORA-04031: unable to allocate 65560 bytes of shared memory (“large pool”,”unknown object”,”large pool”,”PX msg pool”)
ORA-06512: at “SYS.LOGMNR_KRVRDLUID3”, line 1351
ORA-06512: at line 1.

ERROR OGG-01668 PROCESS ABENDING.http://www.cndba.cn/redhat/article/2575

cause:引起的原因是：
CPU_COUNT and PARALLEL_MAX_SERVERS causing the issue.http://www.cndba.cn/redhat/article/2575

The issue in here appears to be with not enough space for PX msg pool. Changing the PARALLEL_MAX_SERVERS and CPU_COUNT to lesser values will fix the issue.

To enable Instance Caging, set the cpu_count of each instance and then enable CPU Resource Manager.

alter system set cpu_count = 4;
alter system set resource_manager_plan = ‘default_plan’;http://www.cndba.cn/redhat/article/2575

Monitor Instance Caging http://www.cndba.cn/redhat/article/2575

To verify that Instance Caging is enabled, check that “instance_caging” equals “ON” and that “cpu_count” is set appropriately.http://www.cndba.cn/redhat/article/2575

select instance_caging from v$rsrc_plan where is_top_plan = ‘TRUE’;
show parameter cpu_count;

To monitor Instance Caging on an instance, monitor the average number of running and waiting sessions.

select to_char(begin_time, ‘HH24:MI’) time, sum(avg_running_sessions) avg_running_sessions, sum(avg_waiting_sessions) avg_waiting_sessions from v$rsrcmgrmetric_history group by begin_time order by begin_time;
“avg_running_sessions” is the average number of running sessions for this minute. If avg_running_sessions is much smaller than cpu_count, the instance is not fully utilizing its cpu_count allocation. cpu_count could be decreased without affecting performance.

“avg_waiting_sessions” is the average number of sessions waiting to be scheduled for this minute. If avg_waiting_sessions is consistently bigger than 0, the performance of the instance could be improved by increasing cpu_count by this amount.

Tuning Instance Caging

You can dynamically tune Instance Caging by adjusting the value of cpu_count. Changes will take effect within seconds.

We do not recommend that you change cpu_count too frequently, since changing its value has some overhead. We also don’t recommend that you set it to 1 or change the value from a very small number to an extremely large value.

版权声明：本文为博主原创文章，未经博主允许不得转载。