Answer / guest

Cause: Attempting to make a tablespace read only while there
are active transactions in the database. All transactions
must commit or rollback to insure that there is no undo for
a tablespace before it can be made read only. This includes
in doubt distributed transactions.

Action: Prevent any more transactions from being started.
Putting the database in restricted mode usually helps. If
there are any in doubt transactions they must also be resolved.

Please add more information about this Error

ORA-19626: backup set type is string - can not be processed by this conversation

1 Answers  

---

TNS-00021: INTCTL: missing INTERCHANGE_DATA in INTCHG.ORA

1 Answers  

---

ORA-01268: invalid TEMPFILE clause for alter of permanent TABLESPACE

1 Answers  

---

ORA-32008: error while processing parameter update at instance string

1 Answers  

---

RMAN-06040: controlfile is already restored to file string

1 Answers  

---

PLS-00510: Float cannot have scale

1 Answers  

---

ORA-26713: remote object does not exist or is inaccessible

1 Answers  

---

ORA-16572: Data Guard configuration file not found

1 Answers  

---

ORA-06043: NETDNT: message send failure

1 Answers  

---

ORA-28525: unable to create Heterogeneous Services error message text

1 Answers  

---

ORA-39108: Worker process string violated startup protocol. Worker error:

1 Answers  

---

ORA-01655: unable to extend cluster string.string by string in tablespace string

1 Answers  

---