Answer / guest

Cause: A failure occurred during initialization of a network
connection from the Oracle server to a second process: 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: --
Database link setup for an Oracle-to-Oracle connection
instead connects to a Heterogeneous Services agent or an
external procedure agent. -- Database link setup for a
Heterogeneous Services connection instead connects directly
to an Oracle server. -- The extproc_connection_data
definition in tnsnames.ora connects to an Oracle instance
instead of an external procedure agent. -- Connect data for
a Heterogeneous Services database link, usually defined in
tnsnames.ora, does not specify (HS=). -- Connect data for an
Oracle-to-Oracle database link, usually defined in
tnsnames.ora, specifies (HS=).

Action: Check Net8 administration in the following ways: --
When using TNSNAMES.ORA or an Oracle Names server, make sure
that the connection from 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 connects to the correct program. -- Confirm in
TNSNAMES.ORA or the equivalent service definition that
service 'extproc_connection_data' does NOT contain (HS=), or
that the service definition used by a Heterogeneous Services
database link DOES contain (HS=).

Please add more information about this Error

QSM-00803: The STORAGE_CHANGE parameter value string cannot be zero or negative for partial workloads.

1 Answers  

---

NZE-28770: Data source is already initialized.

1 Answers  

---

SQL*Loader-00525: OCI return status: success

1 Answers  

---

ORA-22907: invalid CAST to a type that is not a nested table or VARRAY

1 Answers  

---

ORA-22925: operation would exceed maximum size allowed for a LOB value

1 Answers  

---

ORA-07213: slgcs: times error, unable to get wall clock.

1 Answers  

---

ORA-07639: smscre: SGA pad area not large enough (string bytes required)

1 Answers  

---

ORA-07645: sszfsl: $CHANGE_CLASS failure

1 Answers  

---

ORA-33998: (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object.

1 Answers  

---

ORA-30550: index depends on a package/function spec/body which is not valid

1 Answers  

---

NNL-00933: Requests refused, OTHER-DATA violation: number

1 Answers  

---

ORA-32762: Turn on Temp LOB Ref Count Tracing

1 Answers  

---