Expansion after a single Oracle data file exceeds 32 GB

The tablespace data file capacity is related to the DB_BLOCK_SIZE setting. this parameter is specified when you create a database instance. The DB_BLOCK_SIZE parameter can be set to 4 K, 8 K, 16 K, 32 K, 64 K, etc, A maximum of 4194304 data blocks are allowed for Oracle physical files (this parameter is determined by the operating system, and generally this number is used ), the maximum correspondence between tablespace data files can be calculated by 4194304 × DB _ BLOCK_SIZE/MB.

Maximum 4 K tablespace: 16384 M

Maximum 8 K tablespace: 32768 M

Maximum 16 K tablespace: 65536 M

The maximum tablespace of 32 K is 131072 M.

Maximum 64 K tablespace: 262144 M

Oracle allocates 8 K space by default, that is, the space size corresponding to around M. If you want to continue to increase the tablespace size, you only need to add datafile 'path/file_name 'size 1024 M by using alter tablespace name; you can add data files.

Data blocks are the smallest space allocation unit in oracle. The data for various operations is stored here, and oracle reads and writes from the disk are also blocks. Once you create a database, db_block_size cannot be changed. Because oracle stores data in blocks, any storage Element occupies at least one block. If you change db_block_size, some blocks cannot be used normally.

In fact, in unix operating systems, the relationship between file blocks and oracle blocks is very close (it is recommended to be equal), in order to ensure the efficiency of database execution. In windows, it may not be so special. We recommend that you use more than 8 K blocks. Some tests have been conducted. In the same configuration, 8 K blocks are about 40% faster than 4 K, and 3 times faster than 2 K.