ORA-01640: cannot make tablespace read only with active
transactions
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-13362: disjoint sub-element in a compound polygon
ORA-29360: retry operation. Too much concurrent activity
ORA-13138: could not determine name of object string
LRM-00120: 'string' is not a legal Oracle number for 'string'
ORA-39018: master process received invalid message number string
ORA-00024: logins from more than one process not allowed in single-process mode
ORA-31445: invalid lock handle while acquiring lock on string
PLS-00543: a PLSQL Table may not contain a nested table type or VARRAY.
PROC-00105: Logging error
ORA-24403: error occured while trying to destroy the connection pool
PLS-00737: LIBRARY file specification exceeds the maximum allowed length
DRG-11711: too much data for term string