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-19816: WARNING: Files may exist in string that are not known to database.

1 Answers  

---

ORA-06742: TLI Driver: cannot alloc t_bind

1 Answers  

---

SQL*Loader-00283: file processing string "string" ignored for INFILE *

1 Answers  

---

QSM-01602: equivalence, string, requires join back to table, string, on column, string

1 Answers  

---

ORA-02090: network error: attempted callback+passthru

1 Answers  

---

PCC-02348: indicators are not allowed in EXEC IAF statements

1 Answers  

---

ORA-08237: smsget: SGA region not yet created

1 Answers  

---

RMAN-05502: the target database must be mounted when issuing a DUPLICATE command

1 Answers  

---

ORA-07641: smscre: Unable to use the system pagefile for the SGA

1 Answers  

---

ORA-22278: must update the LOB only through the LOB buffers

1 Answers  

---

ORA-22150: variable-length array has not been initialized

1 Answers  

---

ORA-01588: must use RESETLOGS option for database open

1 Answers  

---