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

NNO-00156: warning: hint number address length number exceeds maximum of number, hint ignored

1 Answers  

---

LRM-00106: out of memory

1 Answers  

---

ORA-07700: sksarch: interrupt received

1 Answers  

---

DRG-50925: could not parse return value of PL/SQL

1 Answers  

---

ORA-01374: _log_parallelism_max greater than 1 not supported in this release

1 Answers  

---

NNL-00280: No restart currently scheduled

1 Answers  

---

ORA-03291: Invalid truncate option - missing STORAGE keyword

1 Answers  

---

ORA-36884: (XSSRF03) The value of the first parameter of the AW single row function is incorrect.

1 Answers  

---

RMAN-03018: asynchronous RPCs are working correctly

1 Answers  

---

PROT-00008: Failed to import data from specified file to the cluster registry

1 Answers  

---

ORA-24002: QUEUE_TABLE string does not exist

1 Answers  

---

RMAN-08534: channel string: controlfile restore from autobackup complete

1 Answers  

---