Does table space in the production database automatically expand?

In my opinion, since ORACLE has set Automatic scaling, it must have its own intention. How can we use it manually or automatically in the production environment? It mainly depends on the production environment.


The first is to check the data volume generated by the business, the size of the data file to be extended at a time, 20 mb will be too frequent, and 1 GB will be too long for disk operation. auto scaling affects performance. the performance mainly depends on your hardware configuration.


2. The advantage of manual expansion is that you can expand data files during off-peak hours, but the trouble is management. If you don't need to add data files manually, doesn't it affect business operations?


Third, automatic expansion. Is the data file hard disk sufficient? Is 32 GB occupied by other files in Linux? Note that the UNDO tablespace and the TEMP tablespace are the disk space occupied when the system tablespace is automatically extended.




The overall opinion is automatic + Manual
1. Automatically prevents service interruption due to insufficient space
2. manual scaling can avoid performance problems caused by automatic scaling.

3. Manual expansion can occupy disk space in advance to avoid automatic expansion without disk space expansion!

How can we monitor it?