Answer / guest

Cause: The group name is null, the group name is misspelled,
the invocation database is not a master, or the invocation
database does not believe the given database is a master.

Action: If the given group name was correct, connect to a
current master and retry the request, make the invocation
database a master with add_master_database, or use
switch_mview_master if the invocation database is a
materialized view site.

Please add more information about this Error

SQL*Loader-00603: Maximum length number of column string is too big for bind array

1 Answers  

---

DRG-50701: error in listener.get_cmd()

1 Answers  

---

ORA-15041: diskgroup space exhausted

1 Answers  

---

LFI-01517: open() failed(OSD return value = string).

1 Answers  

---

ORA-16170: Terminal recovery may have left the database in an inconsistent state

1 Answers  

---

---

NZE-28859: SSL negotiation failure

1 Answers  

---

ORA-38716: Must supply an integer for the TYPE option.

1 Answers  

---

ORA-06025: NETASY: Configuration error

1 Answers  

---

ORA-13624: The task string is executing and cannot be deleted or modified.

1 Answers  

---

ORA-14606: Tablespace was specified for previous subpartitions in template but is not specified for string

1 Answers  

---

DRG-10311: remote send not supported

1 Answers  

---

ORA-23293: Cannot rename a column which is part of a join index

1 Answers  

---