Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-01640: cannot make tablespace read only with active
transactions
- 1 Answers
- 4114 Views
- I also Faced
- E-Mail Answers
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
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-27034: maximum length of ORACLE_SID exceeded
DGM-16906: Unable to accept commands: no memory
ORA-23355: object string.string does not exist or is invalid at master site
ORA-06021: NETASY: connect failed
ORA-25019: too much concurreny
ORA-07671: $IDTOASC failed translating an integrity category
QSM-01071: a lossy join in materialized view, string, from table, string, not found in query
QSM-02125: subquery join conditions don't meet requirements for capability
ORA-37111: Unable to load the OLAP API sharable library: (string)
ORA-14284: one or more of table's subpartitions reside in a read-only tablespace
NNF-04006: Could not create outputfile
ORA-28653: tables must both be index-organized
Oracle Errors 
