'ORA-12850: Could Not Allocate Slaves On All Specified Instances: 2' Even Using Workaround "_report_capture_cycle_time"
(Doc ID 2386463.1)
Last updated on MARCH 03, 2022
Applies to:
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and laterOracle Database - Enterprise Edition - Version 12.1.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- Receiving error: ORA-12850: Could not allocate slaves on all specified instances: 2 needed, 0 allocated even following workaround from Document 2102131.1:
alter system set "_report_capture_cycle_time"=0;
After this the error ORA-12850 stopped .
But recently this error ORA-12850 has again appeared.
329801 Fri Mar 23 21:06:04 2018
329802 Errors in file <DIR>/trace/XXXXX_m004_235104.trc:
329803 ORA-12850: Could not allocate slaves on all specified instances: 2 needed, 0 allocated
329804 Fri Mar 23 21:12:52 2018*** 2018-03-23 21:06:04.348
*** SESSION ID:(11518.36615) 2018-03-23 21:06:04.348
*** CLIENT ID:() 2018-03-23 21:06:04.348
*** SERVICE NAME:(SYS$BACKGROUND) 2018-03-23 21:06:04.348
*** MODULE NAME:(MMON_SLAVE) 2018-03-23 21:06:04.348
*** CLIENT DRIVER:() 2018-03-23 21:06:04.348
*** ACTION NAME:(Automatic Report Flush) 2018-03-23 21:06:04.348
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 |