PLS-00252: reference to the wrong copy of package STANDARD
- 1 Answers
- 2627 Views
- I also Faced
- E-Mail Answers
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
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-09945: Unable to initialize the audit trail file
ORA-22331: cannot alter an incomplete type
DRG-50861: failed to obtain type descriptor
ORA-14520: Tablespace string block size [string] does not match existing object block size [string]
SQL*Loader-00512: Unable to free read buffer
SQL*Loader-00456: end of collection found after number elements when looking for number elements
NNO-00059: cannot construct topology checkpoint file name
PCC-00080: TYPE identifier already TYPEd
SQL*Loader-00812: error creating internal table: string
ORA-00399: corrupt change description in redo log
DRG-10304: unexpected error sending command(s) to Oracle Text server
ORA-24122: invalid block range specification
Oracle Errors 
