Answer / guest

Cause: s for the failure. The control program's SQLNET.ORA
file must exist in the correct system-specific location, and
must be readable by the control program. The file must
contain a names.preferred_servers entry with valid name
server addresses. If the user has changed managed servers
with the SET SERVER command, the new server must be running,
and must be able to resolve the address or forward the
request to another server which can resolve the address.
Alternatively, a TNSNAMES.ORA file with valid name server
names and addresses must exist in the correct
system-specific location.

Action: For further details, turn on tracing and re-execute
the failing operation. If the error persists, contact
Worldwide Customer Support.

Please add more information about this Error

DRG-11832: Request Entity Too Large

1 Answers  

---

IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier

0 Answers  

---

PLS-00641: INTO clause not allowed for this SELECT statement

1 Answers  

---

ORA-00286: no members available, or no member contains valid data

1 Answers  

---

PLS-00642: local collection types not allowed in SQL statements

1 Answers  

---

---

ORA-09767: osnmfs: bad return code from msg_send.

1 Answers  

---

QSM-02023: nested cursor

1 Answers  

---

ORA-16813: apply service not running on the apply instance string recorded by the broker

1 Answers  

---

ORA-04011: sequence string must range between string and string

1 Answers  

---

PLS-00643: booleans, index tables, records and cursors not allowed in SQL statements

1 Answers  

---

ORA-14298: LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

1 Answers  

---

ORA-16628: The broker protection mode is inconsistent with the database setting.

1 Answers  

---