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

SQL*Loader-00252: Sort data sets are not used by SQL*Loader

1 Answers  

---

O2F-00303: No INTYPE file was specified

1 Answers  

---

ORA-23536: the object "string"."string" is not cached at the middle tier as expected.

1 Answers  

---

ORA-24395: cannot reinitialize non-existent pool

1 Answers  

---

ORA-19908: datafile string has invalid checkpoint

1 Answers  

---

ORA-33332: (DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again.

1 Answers  

---

NNL-00543: [show] version [<server_list>] : show the name and version of one or more Names servers

1 Answers  

---

ORA-22338: must specify CASCADE INCLUDING DATA when altering the final property

1 Answers  

---

ORA-22952: Nested Table equality requires a map method on the element ADT

1 Answers  

---

NNO-00604: disabling all request processing

1 Answers  

---

ORA-16213: ddl encountered, stopping apply engine

1 Answers  

---

ORA-01327: failed to exclusively lock system dictionary as required by build

1 Answers  

---