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

NNL-00936: Requests refused, DATA-EXISTS violation: number

1 Answers  

---

ORA-14159: duplicate subpartition name

1 Answers  

---

LSX-00283: referenced notation "~S" is not defined

1 Answers  

---

TNS-00144: PUMP_CONNECTIONS value in INTCHG.ORA is too large.

1 Answers  

---

TNS-01067: Service display mode is string

1 Answers  

---

ORA-00476: RECO process terminated with error

1 Answers  

---

RMAN-03031: this option of set command needs to be used inside a run block

1 Answers  

---

NID-00100: Cannot open datafile "string"

1 Answers  

---

ORA-32637: Self cyclic rule in sequential order MODEL

1 Answers  

---

RMAN-06210: List of Mismatched objects

1 Answers  

---

ORA-23386: replication parallel push cannot create slave processes

1 Answers  

---

LFI-01511: unlink() failed(OSD errno = string) in string.

1 Answers  

---