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

O2F-00337: Schema not found, or no types found in schema

1 Answers  

---

ORA-22620: buffer size too small to hold the value

1 Answers  

---

ORA-32058: operation restricted to SYSDBA users

1 Answers  

---

ORA-16706: no resource guard is available

1 Answers  

---

ORA-13138: could not determine name of object string

1 Answers  

---

NCR-04023: NCRR: Invalid object descriptor

1 Answers  

---

ORA-24071: cannot perform operation string, queue table string is being migrated

1 Answers  

---

PROT-00005: Clusterware is not running properly

1 Answers  

---

RMAN-06144: FROM or UNTIL may not be specified with LIST INCARNATION

1 Answers  

---

DRG-10800: query failed: string string string

1 Answers  

---

ORA-26062: Can not continue from previous errors.

1 Answers  

---

ORA-16060: Log file is current

1 Answers  

---