Using RESUMABLE Session to Avoid Transaction Abort Due to Space Errors
(Doc ID 136941.1)
Last updated on APRIL 14, 2021
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
This document explains the cases when the resumable space allocation feature can be useful.
In case a transaction is suspended for space allocation reasons,the resumable space allocation feature allows the transaction to be resumed.
These are very common situations when a transaction is interrupted for a space allocation issue:
* storage settings inappropriate for the table being inserted
* storage settings inappropriate for the rollback segment being used for the transaction
* lack of space on temporary tablespace
* user quotas restricted
* users privileges missing
The resumable statement feature allows the DBA, once having applied the appropriate solution to the space allocation issue, to resume the suspended
transaction which does not loose all the work done previously.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!