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-31399: Cannot contact LDAP server string at port number

1 Answers  

---

ORA-31674: worker process interrupt for unhandled exception in master process

1 Answers  

---

ORA-27041: unable to open file

1 Answers  

---

ORA-06775: TLI Driver: error reading break mode

1 Answers  

---

RMAN-06010: error while looking up datafile: string

1 Answers  

---

ORA-16761: Resource guard could not stop logical apply engine

1 Answers  

---

ORA-28534: Heterogeneous Services preprocessing error

1 Answers  

---

ORA-19595: archivelog string already included in backup conversation

1 Answers  

---

ORA-30735: cannot create multiple subtables of the same type under a supertable

1 Answers  

---

ORA-29883: cannot create a domain index on column expressions

1 Answers  

---

PCC-02368: An EXEC TOOLS host variable context name is not type char

1 Answers  

---

NNL-01078: Access/Create File Error : string

1 Answers  

---