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-02171: invalid value for MAXLOGHISTORY

1 Answers  

---

ORA-24333: zero iteration count

2 Answers   IBM,

---

ORA-23436: missing template authorization for user

1 Answers  

---

PCC-02323: found typedef name used in an expression (expecting a value)

1 Answers  

---

ORA-30502: system triggers cannot have INSERT, UPDATE, or DELETE as triggering events

1 Answers  

---

ORA-18003: an outline already exists with this signature

1 Answers  

---

ORA-28040: No matching authentication protocol

1 Answers  

---

ORA-22607: image handle already generated

1 Answers  

---

NNL-00016: cannot start server, error getting program directory's name

1 Answers  

---

DRG-11807: No Content

1 Answers  

---

CLSS-00200: local node string not listed in configuration

1 Answers  

---

ORA-25963: join index must be created on tables

1 Answers  

---