Answer / guest

Cause: The Data Guard broker determined that there were
multiple database objects referring to the same physical
database.

Action: Examine the details of all databases in the broker
configuration and verify that there are not two or more
databases that indicate the same physical database. If you
detect this situation, remove and re-add the erroneously
defined database(s) to resolve the ambiguity.

Please add more information about this Error

ORA-31639: unexpected data found

1 Answers  

---

ORA-19040: Element string does not match expected string.

1 Answers  

---

ORA-22978: only simple attribute name is allowed in the WITH OBJECT OID clause

1 Answers  

---

NNO-00300: no listen addresses specified, at least one is required

1 Answers  

---

CLSS-00099: logfile open failed for string, err string

1 Answers  

---

---

QSM-00783: the specified value string contains an invalid date for parameter string

1 Answers  

---

ORA-14633: Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table

1 Answers  

---

LFI-01504: fseek() failed(OSD return value = string) in string.

1 Answers  

---

ORA-02464: Cluster definition can not be both HASH and INDEX

1 Answers  

---

PCC-00011: Already in a declare section at line number in file string

1 Answers  

---

ORA-16596: object not part of the Data Guard broker configuration

1 Answers  

---

ORA-19751: could not create the change tracking file

1 Answers  

---