ORA-12850 is Raised by Mmon Slave Automatic Report Flush Action
(Doc ID 2217969.1)
Last updated on JULY 08, 2021
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- ORA-12850 is raised by mmon slave process in RAC env:
- alert.log shows following message:
Errors in file /oracle/.../xxx_m002_878.trc:
ORA-12850: Could not allocate slaves on all specified instances:2 needed, 1 allocated - Check ACTION NAME=Automatic Report Flush and SQL statement(WITH MONITOR_DATA ...) in the MMON slave trace file:
*** SERVICE NAME:(SYS$BACKGROUND) 2016-12-27 23:57:41.261
*** MODULE NAME:(MMON_SLAVE) 2016-12-27 23:57:41.261
*** CLIENT DRIVER:() 2016-12-27 23:57:41.261
*** ACTION NAME:(Automatic Report Flush) 2016-12-27 23:57:41.261 <----- HereORA-12850: Could not allocate slaves on all specified instances:
2 needed, 0 allocated
Dump of memory from 0x00000007B7237D68 to 0x00000007B724DAAC
7B7237D60 48544957 4E4F4D20 [WITH MON]<----- Here
7B7237D70 524F5449 5441445F 53412041 45532820 [ITOR_DATA AS (SE]1 <----- Here
...
- Setting errorstack for ORA-12850, you can see following current SQL statement.(SQL_ID is dfffkcnqfystw):
----- Current SQL Statement for this session (sql_id=dfffkcnqfystw) -----
WITH MONITOR_DATA AS ...
...
FROM GV$SQL_MONITOR
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |