Answer / guest

Cause: When an instance was started, the DMON process on the
instance failed to access the Data Guard broker
configuration. This can happen if the DG_BROKER_CONFIG_FILE1
and DG_BROKER_CONFIG_FILE2 initialization parameters are not
set up correctly to point to the broker configuration files
shared among all instances.

Action: Set DG_BROKER_CONFIG_FILE1 and
DG_BROKER_CONFIG_FILE2 to the correct file specifications
that point to the broker configuration files shared among
all instances. Bounce the DMON process by setting
DG_BROKER_START initialization parameter to FALSE and then
to TRUE.

Please add more information about this Error

ORA-24010: QUEUE string does not exist

1 Answers  

---

ORA-19002: Missing XMLSchema URL

1 Answers  

---

ORA-21701: attempt to flush objects to different servers

1 Answers  

---

ORA-29702: error occurred in Cluster Group Service operation

1 Answers  

---

RMAN-06439: RMAN must be upgraded to version string to work with this package

1 Answers  

---

ORA-29553: class in use: string.string

1 Answers  

---

ORA-31636: session is already attached to job string for user string

1 Answers  

---

PLS-00416: The third argument of DECODE cannot be NULL

1 Answers  

---

NNL-00854: Fastest rename processing time: string

1 Answers  

---

SQL*Loader-00113: Invalid silent mode option

1 Answers  

---

ORA-14134: indexes cannot use both DESC and REVERSE

1 Answers  

---

ORA-29514: class name contains illegal character

1 Answers  

---