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-00293: Missing XMLTYPE directive in control file for table string

1 Answers  

---

ORA-06528: Error executing PL/SQL profiler

1 Answers  

---

RMAN-12020: error on step filtered for normal output string

1 Answers  

---

ORA-24852: protocol error during statement execution

1 Answers  

---

AMD-00147: invalid Custom Measure creation mode "string" specified

1 Answers  

---

IMP-00086: TOID "string" not found in export file

1 Answers  

---

ORA-00040: active time limit exceeded - call aborted

1 Answers  

---

TNS-04047: Invalid specification for destination

1 Answers  

---

ORA-12034: materialized view log on "string"."string" younger than last refresh

2 Answers  

---

ORA-24392: no connection pool to associate server handle

1 Answers  

---

ORA-12406: unauthorized SQL statement for policy string

1 Answers  

---

ORA-16083: LogMiner session has not been created

1 Answers  

---