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

DRG-52210: error while registering value for attribute: string

1 Answers  

---

ORA-30729: maximum number of columns exceeded

1 Answers  

---

ORA-01116: error in opening database file string

1 Answers  

---

ORA-26060: Can not convert type identifier for column string

1 Answers  

---

ORA-07267: spwat: invalid process number.

1 Answers  

---

ORA-13037: SRIDs do not match for the two geometries

1 Answers  

---

ORA-26506: null global context

1 Answers  

---

LSX-00166: both content types must be mixed or both must be element-only

1 Answers  

---

DRG-11504: invalid longsize parameter of string specified

1 Answers  

---

ORA-13012: an invalid window type was specified

1 Answers  

---

SQL*Loader-00948: subpartition string not part of table string

1 Answers  

---

NNO-00110: line string: unknown data type "string", data ignored

1 Answers  

---