oracle中出現(xiàn)ORA-12850錯(cuò)誤怎么辦

這篇文章給大家分享的是有關(guān)oracle中出現(xiàn)ORA-12850錯(cuò)誤怎么辦的內(nèi)容。小編覺得挺實(shí)用的，因此分享給大家做個(gè)參考，一起跟隨小編過來看看吧。

1.問題現(xiàn)象
報(bào)錯(cuò)信息如下：

Thu Aug 24 10:01:33 2017

Errors in file /oradata/diag/rdbms/cdb/cdb2/trace/cdb2_m000_3564.trc:

ORA-12850: 無法在所有指定實(shí)例上分配從屬進(jìn)程:需要2,已分配1

trace 文件部分輸出輸出：
*** 2017-08-24 10:01:33.324
*** SESSION ID:(1390.13783) 2017-08-24 10:01:33.324
*** CLIENT ID:() 2017-08-24 10:01:33.324
*** SERVICE NAME:(SYS$BACKGROUND) 2017-08-24 10:01:33.324
*** MODULE NAME:(MMON_SLAVE) 2017-08-24 10:01:33.324
*** CLIENT DRIVER:() 2017-08-24 10:01:33.324
*** ACTION NAME:(Automatic Report Flush) 2017-08-24 10:01:33.324
*** CONTAINER ID:(1) 2017-08-24 10:01:33.324

2、報(bào)錯(cuò)分析
在mos找到了2篇文章和此次報(bào)錯(cuò)相吻合
ORA-12850 is Raised by Mmon Slave Automatic Report Flush Action (文檔 ID 2217969.1)
High CPU Usage and/or Frequent Occurrences of ORA-12850 For Monitor Queries by MMON From 12.1 (文檔 ID 2102131.1)
文中提到引起問題的原因：
bug:24554937 ORA-12850 WHILE MMON SLAVE AUTOMATIC REPORT FLUSH ACTION

There is a new feature in 12C called "Automatic Report Capturing Feature". As part of this feature, some monitoring SQLs are executed by MMON_SLAVE to identify the resource-intensive SQLs and generate the SQL Monitoring report automatically for those SQLs. Those SQLs consume little more CPU and it is expected behavior being a new feature. Such monitoring queries can be identified from (G)V$SQLSTATS.
==》大致意思是說12.1，引入了 "Automatic Report Capturing Feature"這個(gè)新特性，monitoring SQLs被執(zhí)行以便收集resource-intensive SQLs信息，生成SQL Monitoring report.當(dāng)monitoring SQLs消耗過高的cpu時(shí)會(huì)報(bào)ORA-12850.

3.解決方案
文章中提供了2中解決方案：
1.Apply Patch 24554937 if it is available for your version and platform.
2.執(zhí)行以下sql禁用新特性
SQL> alter system set "_report_capture_cycle_time"=0;

感謝各位的閱讀！關(guān)于“oracle中出現(xiàn)ORA-12850錯(cuò)誤怎么辦”這篇文章就分享到這里了，希望以上內(nèi)容可以對(duì)大家有一定的幫助，讓大家可以學(xué)到更多知識(shí)，如果覺得文章不錯(cuò)，可以把它分享出去讓更多的人看到吧！