I think the problem that you describe here is the Tablespace Space Threshold. You can get your current threshold settings via (also have a look at the documentation):
SELECT * FROM dba_thresholds
WHERE object_type = 'TABLESPACE' AND object_name = <Your tablespace>;
In my case that gives me:
METRICS_NAME: Tablespace Space usage
WARNING_OPERATOR: GE
WARNING_VALUE: 85
CRITICAL_OPERATOR: GE
CRITICAL_VALUE: 97
OBSERVATION_PERIOD: 1
CONSECUTIVE_OCCURRENCES: 1
INSTANCE_NAME: database_wide
OBJECT_TYPE: TABLESPACE
OBJECT_NAME: null
STATUS: VALID
You can modify your thresholds or deactivate them altogether via the DBMS_SERVER_ALERT.SET_THRESHOLD
method. For example, to deactivate the threshold on my system I use:
BEGIN
DBMS_SERVER_ALERT.SET_THRESHOLD(
metrics_id => DBMS_SERVER_ALERT.TABLESPACE_PCT_FULL,
warning_operator => DBMS_SERVER_ALERT.OPERATOR_DO_NOT_CHECK,
warning_value => '0',
critical_operator => DBMS_SERVER_ALERT.OPERATOR_DO_NOT_CHECK,
critical_value => '0',
observation_period => 1,
consecutive_occurrences => 1,
instance_name => NULL,
object_type => DBMS_SERVER_ALERT.OBJECT_TYPE_TABLESPACE,
object_name => NULL);
END;
/
By querying DBA_THRESHOLDS again I now have:
METRICS_NAME: Tablespace Space usage
WARNING_OPERATOR: DO NOT CHECK
WARNING_VALUE: 0
CRITICAL_OPERATOR: DO_NOT_CHECK
CRITICAL_VALUE: 0
OBSERVATION_PERIOD: 1
CONSECUTIVE_OCCURRENCES: 1
INSTANCE_NAME: database_wide
OBJECT_TYPE: TABLESPACE
OBJECT_NAME: null
STATUS: VALID