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-14451: unsupported feature with temporary table

1 Answers  

---

KUP-04061: directory object string specified for LOBFILE column string is not valid

1 Answers  

---

ORA-08343: srclose: failed to close a redo server connection

1 Answers  

---

ORA-09842: soacon: Archmon unable to create named pipe.

1 Answers  

---

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

1 Answers  

---

AMD-00114: PROCEDURE string, internal error

1 Answers  

---

ORA-12011: execution of string jobs failed

1 Answers  

---

ORA-00972: identifier is too long

1 Answers  

---

ORA-25952: join index must only contain inner equi-joins

1 Answers  

---

ORA-02457: The HASH IS option must specify a valid column

1 Answers  

---

ORA-33006: (XSAGDNGL02) The relation workspace object is not related to itself.

1 Answers  

---

ORA-33052: (XSAGDNGL25) AGGMAP workspace object is a dimensioned AGGMAP; it can only be used to aggregate like-dimensioned variables.

1 Answers  

---