Oracle 18.5 on Exadata
I have tablespace created as bigfile with initial 20G next 256G and maxsize 20T
we use a tablespace per day to store the data we capture. Most tablespaces are between 300G and 500G disk allocation. Suddenly we have a tablespace that has been extended to 20T. There have been 5 occurrences so far since 2019.
Where do I begin to look for the reasons and solution? If I make the next to be say, 20G what will stop the runaway situation. Also does the database not know that some process has already initiated the file extension so as to not repeat6ed do this?
Regards