Answer / guest

Cause: The most likely cause of this error is that one of
the databases to which RMAN had previously connected is not
started or has has been shutdown. Other error messages
should identify exactly which database is the problem.

Action: Startup the database causing the problem.

Please add more information about this Error

ORA-02764: Invalid package mode

1 Answers  

---

TNS-00100: Unable to allocate memory

1 Answers  

---

PLS-00308: this construct is not allowed as the origin of an assignment

1 Answers  

---

RMAN-06520: archived logs required to recover from this backup will not be kept

1 Answers  

---

RMAN-06429: %s database is not compatible with this version of RMAN

1 Answers  

---

ORA-01742: comment not terminated properly

1 Answers  

---

SQL-02102: Inconsistent cursor cache. No global cursor entry.

1 Answers  

---

PCC-00107: The CONNECT statement is Oracle implementation dependent

1 Answers  

---

ORA-31215: DBMS_LDAP: PL/SQL - Invalid LDAP mod value.

1 Answers  

---

ORA-15196: invalid ASM block header [string:string] [string] [string] [string] [string != string]

1 Answers  

---

RMAN-20222: datafilename not found in recovery catalog or is ambiguous

1 Answers  

---

ORA-00271: there are no logs that need archiving

1 Answers  

---