You see one of the following in Data Loss Prevention (DLP):
Receiving a tablespace warning with DLP, system alert warning that a tablespace in Oracle is almost full (>80%) or critically full (>90%).
“Corrupt incident” alerts because a tablespace is completely full and can no longer store incident data.
Summary Tablespace is almost full
Detail Oracle tablespace LOB_TABLESPACE is over 83% full
You need to extend one or more tablespaces in the Oracle database for DLP.
Caution: Pay close attention to which tablespace names the logs or alerts identify for extension. LOB_TABLESPACE is usually affected, but it can be USERS or other tablespaces. All tablespaces are extended the same way; substitute the appropriate tablespace name.
In DLP 14.x and later, you can view the “Tablespace Summary” in the DLP Enforce console.
Note: This summary does not fully describe the tablespace, such as the location of the database files.
Locate the Oracle database files
Before you can extend the tablespace, you need to know where the current Oracle database files are located.