Answer / guest

Cause: Could have been taken offline before by DBA or
cleaned up by SMON.

Action: Check the status of rollback segment in undo$ or
dba_rollback_segs to make sure the rollback segment is
actually online.

Please add more information about this Error

ORA-02171: invalid value for MAXLOGHISTORY

1 Answers  

---

LPX-00239: invalid attribute type "~s"

1 Answers  

---

ORA-01263: Name given for file destination directory is invalid

2 Answers  

---

RMAN-08544: channel string: specifying archivelog(s) for proxy restore

1 Answers  

---

ORA-09832: infoCallback: bad message format.

1 Answers  

---

NPL-00413: incoming ASN.1 encoding has length string, maximum allowed is string

1 Answers  

---

SQL*Loader-00916: Error checking path homogeneity

1 Answers  

---

TNS-12674: Shared server: proxy context not saved

1 Answers  

---

LFI-01512: stat() failed

1 Answers  

---

ORA-14156: invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause

1 Answers  

---

PLS-00598: comparison of object with NULL using "string" is not allowed

1 Answers  

---

ORA-12813: value for PARALLEL or DEGREE must be greater than 0

1 Answers  

---