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

QSM-01619: equivalence cannot be used in ENFORCED integrity mode

1 Answers  

---

NCR-01005: NCRS: Failed to flush the output buffer.

1 Answers  

---

ORA-23380: propagation mode "string" is not valid

1 Answers  

---

ORA-16732: Error executing dbms_logstdby.skip procedure

1 Answers  

---

DRG-11123: theme indexing is not supported

1 Answers  

---

PCC-00013: Unable to open include file "string" at line number in file string

1 Answers  

---

RMAN-06542: file string is excluded from whole database backup

1 Answers  

---

ORA-02214: duplicate BACKUP option specification

1 Answers  

---

PCB-00700: This statement can only be used with DYNAMIC=ANSI

1 Answers  

---

ORA-22887: type of REF column is not the same as that of its scoped table

1 Answers  

---

NNL-00041: Object string not in domain string

1 Answers  

---

NZE-29046: Session is resumable.

1 Answers  

---