Answer / guest

Cause: A reference is made to the fixed package version of
STANDARD when the database is open, or to the on-disk
version when the database is closed. Explicit use of a
SYS.X$ package name can lead to this. One might also see
this from a compilation that begins while the db is closed
but has the bad luck to have another session open the db
before compilation is complete. Another possible cause is
having 'set serveroutput on' through svrmgrl when doing an
'alter database close'.

Action: Make use of on-disk versions of packages when the
database is open and fixed (preloaded) versions when the
database is closed. Do not attempt to use the wrong set. It
should be quite hard to reference the wrong set, except by
using SYS.X$ package names explicitly. Also, be sure to 'set
serveroutput off' before doing an 'alter database close'.

Please add more information about this Error

ORA-06760: TLI Driver: timeout reading orderly release

1 Answers  

---

RMAN-10006: error running SQL statement: string

1 Answers  

---

ORA-13757: "SQL Tuning Set" "string" is active.

1 Answers  

---

PLS-00323: subprogram or cursor 'string' is declared in a package specification and must be defined in the package body

1 Answers  

---

PLS-00145: duplicate external WITH CONTEXT specification in subprogram expression

1 Answers  

---

ORA-32634: automatic order MODEL evaluation does not converge

1 Answers  

---

RMAN-05506: error during recursive execution

1 Answers  

---

ORA-32591: connect string too long

1 Answers  

---

LFI-00126: Record format can only be one of Fixed or Variable.

1 Answers  

---

ORA-36638: (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object.

1 Answers  

---

TNS-00076: component by specifying the component name in

1 Answers  

---

ORA-16715: Log transport related property string of standby "string" is inconsistent.

1 Answers  

---