There is another thing....
ERadaell, October 21, 2015 - 7:14 pm UTC
This error could occur on permanent tablespaces too (and seems to be the case).
That said, i'd advise you (and your DBAs) to use "autoextend" on datafiles and create a script to monitor this behavior (when the datafile is almost hitting the maxsize). You'll need access to dba_data_files and dba_tablespaces.
Also, you must notify the DBAs about unusual big data loads. They will create new datafiles to accomplish this load.
If that will not solve the entire problem, at least it's a good start.