Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-01640: cannot make tablespace read only with active
transactions
- 1 Answers
- 4102 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-12660: Encryption or crypto-checksumming parameters incompatible
ORA-07259: spdcr: exec error, detached process failed in startup.
ORA-27204: skgfpqr: sbtpcqueryrestore returned error
ORA-01293: mounted database required for specified LogMiner options
ORA-23379: connection qualifier "string" is too long
KUP-04104: zoned decimal field has bad values for string
AMD-00141: parameter string of "string" not valid starting around "string"
PCC-00041: Unable to open output file "string"
ORA-30942: XML Schema Evolution error for schema 'string' table string column 'string'
ORA-39956: duplicate setting for PL/SQL compiler parameter string
ORA-31635: unable to establish job resource synchronization
AMD-00116: PROCEDURE string, read error
Oracle Errors 
