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-01097: cannot shutdown while in a transaction - commit or rollback first

1 Answers  

---

RMAN-08590: channel string: datafile conversion complete, elapsed time: string

1 Answers  

---

ORA-24362: improper use of the character count flag

1 Answers  

---

ORA-16103: Logical Standby apply must be stopped to allow this operation

1 Answers  

---

NNL-00004: invalid command argument "string"

1 Answers  

---

ORA-02736: osnfpm: illegal default shared memory address

1 Answers  

---

ORA-09967: scumnt: unable to create or open file

1 Answers  

---

ORA-38449: table "string" does not exist or is not accessible

1 Answers  

---

ORA-13504: No SYSAUX datafile clause specified

1 Answers  

---

ORA-00234: error in identifying or opening snapshot or copy controlfile

1 Answers  

---

NNO-00054: invalid domain name "string"

1 Answers  

---

ORA-14290: PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

1 Answers  

---