Reprinted articles: https://www.cnblogs.com/lcword/p/5478772.html , if infringement, please contact me delete
Table space data file size and DB_BLOCK_SIZE setting, whereas this parameter has been specified when creating the database instance. DB_BLOCK_SIZE parameter can be set to 4K, 8K, 16K, 32K, 64K , etc. are several, the Oracle physical file only allows maximum 4,194,304 blocks (as determined by the operating parameters of the system, this number should be typically), tablespace data file maximum correspondence relationship can pass 4194304 × DB_BLOCK_SIZE / 1024M calculated.
4k maximum table space: 16384M
8K maximum table space: 32768M
16k maximum table space: 65536M
The maximum table size is 32K: 131072M
64k maximum table space: 262144M
And Oracle default allocation of 8K, that is, a space corresponding to a size of about 32768M, if you want to continue to increase the table space, then only through alter tablespace name add datafile size 1024M 'path / file_name'; adding data files manner can a.
Oracle data block is the smallest unit of space allocation, data on the various operations to herein, is also read from the disk oracle block. Once create database, db_block_size is unalterable. Because the oracle data is stored in units of blocks, any storage elements occupy at least a block, if you change the db_block_size, will inevitably lead to a partial block can not be used properly.
In fact, unix-like operating systems, the relationship between file blocks and blocks very close oracle (equivalent recommended), so as to ensure the efficiency of the database. In the windows might not be so particular about. 8k block recommended above, the test was done, the same configuration, 8k blocks about 40% faster than 4k, more than 3 times faster than 2k.
