Oracle Table Space Management related

Here is an example of my own test environment:

1. The tablespace's block_size is 8192 bytes, or 8KBytes. From the data dictionary, the max_size is 2147483645, which is about 15.9TBytes.

2. When creating a tablespace, you can choose Bigfile or smallfile, which I should default to is Smallfile. It is found that both bigfile and smallfile do not affect the max_size of the tablespace, but the size of the data_file is affected. When using bigfile not to manually specify the maximum size of the data file, the discovery data file MaxBytes is 35184372064256 bytes, approximately 31.9TBytes, and the size of the data file is not manually specified using Smallfile. Discovery data File MaxBytes is 34359721984 bytes, approximately 31.9GBytes. This problem arises when the maximum size of a tablespace is approximately 15.9TBytes, regardless of whether you specify Bigfile or Smallfile, so that when you specify Bigfile, the size of the data file is larger than the size limit of the table space. Speculation is that when you create a tablespace or modify a tablespace, the specified data file can specify reuse so that multiple tablespaces can share a single data file. When specifying Smallfile, the maximum size of the data file is 31.9GBytes, which is smaller than the maximum size of table space 15.9TBytes, and the solution is that a tablespace can have multiple data files.
3.

Oracle Table Space Management related