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-04930: open sequence number failed or initial state is valid

1 Answers  

---

ORA-00608: testing error [string] [string] [string] [string] [string]

1 Answers  

---

DRG-10709: this preference is referenced by string and cannot be dropped

1 Answers  

---

QSM-00999: Advisor feature is not currently implemented

1 Answers  

---

ORA-12476: least upper bound resulted in an invalid OS label

1 Answers  

---

DRG-12220: a valid tag must be provided

1 Answers  

---

ORA-31403: change table string already contains a column string

1 Answers  

---

ORA-01099: cannot mount database in SHARED mode if started in single process mode

1 Answers  

---

ORA-29936: NULL association is allowed only with a column or an index

1 Answers  

---

ORA-30183: invalid field width specifier

1 Answers  

---

ORA-26698: %s did not have a string rule set

1 Answers  

---

ORA-07280: slsget: unable to get process information.

1 Answers  

---