Answer / guest

Cause: The group name is null, the group name is misspelled,
the invocation or given database is not the masterdef, or
one of the masters does not believe the invocation database
is the masterdef.

Action: If the given group name and masterdef were both
correct, connect to the masterdef and retry the request, or
relocate the masterdef at the (errant) databases using
relocate_masterdef.

Please add more information about this Error

ORA-19815: WARNING: string of string bytes is string used, and has string remaining bytes available.

1 Answers  

---

ORA-07305: ksmcsg: illegal database buffer size.

1 Answers  

---

ORA-38761: thread string redo log sequence number string could not be accessed

1 Answers  

---

RMAN-08050: cataloged datafile copy

1 Answers  

---

ORA-24169: rule condition has unrecognized variables

1 Answers  

---

ORA-36986: (XSRELGID05) Relation workspace object must be dimensioned by workspace object.

1 Answers  

---

QSM-01060: illegal subquery in the HAVING clause

1 Answers  

---

NID-00505: REVERT Revert failed change NO

1 Answers  

---

ORA-25508: database is not mounted

1 Answers  

---

ORA-08114: can not alter a fake index

1 Answers  

---

ORA-04030: out of process memory when trying to allocate string bytes (string,string)

1 Answers  

---

TNS-02502: Authentication: unable to find initialization function

1 Answers  

---