Answer / guest

Cause: The connection was lost while doing this call. It may
not be safe to replay it after failover.

Action: Check to see if the results of the call have taken
place, and then replay it if desired.

Please add more information about this Error

Answer / bladmeer

casee :
you are using third part to do some transaction on the
database like perl.exe or jdbc connection and the
connection from this part was reset so try to solve the
third part connection problem

LPX-00657: Invalid output PI '~S'.

1 Answers  

---

RMAN-20506: no backup of archivelog found

1 Answers  

---

ORA-01952: system privileges not granted to 'string'

1 Answers  

---

RMAN-06188: cannot use command when connected to a mounted target database

1 Answers  

---

ORA-02098: error parsing index-table reference (:I)

1 Answers  

---

---

ORA-22916: cannot do an exact FETCH on a query with Nested cursors

1 Answers  

---

SQL*Loader-00602: Maximum converted length number of column string is too big for bind array

1 Answers  

---

QSM-01052: referential integrity constraint on table, string, not VALID in ENFORCED integrity mode

1 Answers  

---

PCC-02393: SQL statement found inside an EXEC SQL DECLARE SECTION

1 Answers  

---

ORA-02762: file number to be cancelled is greater than the maximum.

1 Answers  

---

LPX-00405: unable to allocate memory

1 Answers  

---

ORA-00297: must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START

1 Answers  

---