PLW-05004: identifier string is also declared in STANDARD or
is a SQL builtin
- 1 Answers
- 2595 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: The indicated identifier was also either: o) declared
in package STANDARD, or o) a SQL builtin function, or o) a
pseudo-column. This situation can result in name resolution
issues since the STANDARD/builtin declaration will be chosen
over the local declaration in SQL statements; however the
local declaration will be chosen over the STANDARD/builtin
declaration outside SQL scope. (See the documentation on
PL/SQL name resolution.)
Action: Either: o) rename the given identifier, o) qualify
any references to the identifier with the containing scope's
name, or o) make sure the intended resolution occurs if
using the identifier in SQL scope.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
SQL*Loader-00250: Work data sets are not used by SQL*Loader
LSX-00248: invalid duration "~S"
ORA-07274: spdcr: access error, access to oracle denied.
ORA-07842: sllfcl: SYS$CLOSE failure
ORA-33006: (XSAGDNGL02) The relation workspace object is not related to itself.
NNL-01077: Save Config on Stop string
RMAN-08584: copying current controlfile
ORA-14404: partitioned table contains partitions in a different tablespace
PCC-01017: The SQLCA and a SQLCODE variable cannot both be used
ORA-03280: invalid DATAFILE filename specified
ORA-36157: (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword.
ORA-27067: size of I/O buffer is invalid
Oracle Errors 
