Answer / guest

Cause: A failure occurred during initialization of a network
connection from a client process to the Oracle server: The
connection was completed but a disconnect occurred while
trying to perform protocol-specific initialization, usually
due to use of different network protocols by opposite sides
of the connection. This usually is caused by incorrect Net8
administrative setup for database links or external
procedure calls. The most frequent specific causes are: --
The connection uses a connect string which refers to a
Heterogeneous Services agent instead of an Oracle server. --
The connection uses a connect string which includes an (HS=)
specification.

Action: Check Net8 administration in the following ways: --
When using TNSNAMES.ORA or an Oracle Names server, make sure
that the client connection to the ORACLE server uses the
correct service name or SID. -- Check LISTENER.ORA on the
connection end point's host machine to assure that this
service name or SID refers to the correct server. -- Confirm
in TNSNAMES.ORA or the equivalent service definition that
the connect string does NOT contain (HS=).

Please add more information about this Error

KUP-03022: lob data could not be found for field string

1 Answers  

---

ORA-26025: SKIP_INDEX_MAINTENANCE option requested

1 Answers  

---

TNS-01043: Password changed for string

1 Answers  

---

ORA-15198: operation string is not yet available

1 Answers  

---

ORA-16571: Data Guard configuration file creation failure

1 Answers  

---

RMAN-06035: wrong version of recover.bsq, expecting string, found string

2 Answers  

---

LSX-00124: "list" element is improperly defined

1 Answers  

---

ORA-33334: (DSSEXIST04) Analytic workspace string is not attached.

1 Answers  

---

RMAN-06139: WARNING: controlfile is not current for REPORT SCHEMA

1 Answers  

---

DRG-11121: failed to read from file string

1 Answers  

---

KUP-04013: other system error

1 Answers  

---

ORA-13509: error encountered during updates to a SWRF table

1 Answers  

---