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

ORA-29819: cannot associate default values with columns

1 Answers  

---

AUD-00808: ORDSpeechIndex: unable to CREATE internal Text index

1 Answers  

---

ORA-04086: trigger description too long, move comments into triggering code

1 Answers  

---

ORA-09822: Translation of audit file name failed.

1 Answers  

---

SQL*Loader-00432: converted data too large

1 Answers  

---

PLS-00171: duplicate dedicated AGENT specification in subprogram expression

1 Answers  

---

ORA-08445: syntax error in SIGN clause in mask options

1 Answers  

---

ORA-29270: too many open HTTP requests

1 Answers  

---

ORA-15016: invalid ASM_DISKGROUPS initialization parameter "string"

1 Answers  

---

ORA-23496: can not change disabled status for "string" and "string"

1 Answers  

---

RMAN-08072: deleted controlfile copy

1 Answers  

---

ORA-01675: max_commit_propagation_delay inconsistent with other instances

1 Answers  

---