Answer / guest

Cause: OTT was unable to allocate memory.

Action: Contact ORACLE customer support.

Please add more information about this Error

Answer / gopal

It may arise because of insufficient memory in tablespace.
Check whether ur tablespace is full or not. One solution of
it is to allow tablespace to auto extend mode and set the
limit to unlimited.

ORA-27056: could not delete file

1 Answers  

---

RMAN-20001: target database not found in recovery catalog

2 Answers  

---

ORA-29259: end-of-input reached

1 Answers  

---

SQL*Loader-00801: all INTO TABLE clauses must have the same options (string)

1 Answers  

---

NNL-00525: Shows or sets the server's default-forwarding status

1 Answers  

---

---

QSM-02139: agg(expr) requires correspondng agg(expr+expr) function

1 Answers  

---

RMAN-10004: unable to connect to recovery catalog

1 Answers  

---

ORA-16755: failed to set initialization parameter

1 Answers  

---

PLS-00630: pipelined functions must have a supported collection return type

2 Answers  

---

ORA-01373: insufficient memory for staging persistent LogMiner session

1 Answers  

---

ORA-02145: missing STORAGE option

1 Answers   Oracle,

---

ORA-09809: Unable to get user's group ID from connection

1 Answers  

---