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-25300: Cannot drop buffer for queue with buffered subscribers

1 Answers  

---

ORA-32631: illegal use of objects in MODEL

1 Answers  

---

ORA-12685: Native service required remotely but disabled locally

1 Answers  

---

ORA-30102: 'string' is not in the legal range for 'string'

1 Answers  

---

LSX-00009: data missing for type "~S"

1 Answers  

---

ORA-31498: description and remove_description cannot both be specified

1 Answers  

---

LFI-00120: Unable to parse root filename string.

1 Answers  

---

PLS-00719: only widening of attribute 'string' constraints is allowed

1 Answers  

---

ORA-38737: Expected sequence number string doesn't match string

1 Answers  

---

NNO-00113: line string: alias data already exists, all other data ignored

1 Answers  

---

ORA-10922: Temporary tablespace group is empty

1 Answers  

---

ORA-24853: failed to connect thread to shared subsystem

1 Answers  

---