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-00472: PMON process terminated with error

1 Answers   TCS,

---

RMAN-06527: KEEP option is not supported for backup of backup sets

1 Answers  

---

ORA-09931: Unable to open ORACLE password file for reading

1 Answers  

---

ORA-09317: szprv: insufficient privileges

1 Answers  

---

RMAN-06207: WARNING: string objects could not be deleted for string channel(s) due

1 Answers  

---

ORA-02476: can not create index due to parallel direct load on table

1 Answers  

---

IMG-00519: illegal combination of parameters

1 Answers  

---

NNO-00700: warning: cannot checkpoint the cache, trying again in number seconds

1 Answers  

---

DRG-13011: language column must be specified when using the multi lexer

1 Answers  

---

ORA-13011: value is out of range

1 Answers  

---

RMAN-20230: datafile copy not found in the recovery catalog

1 Answers  

---

RMAN-05501: aborting duplication of target database

1 Answers  

---