Oracle physical structure and logical structure

There is a figure that clearly shows the differences between the physical and logical structures of Oracle. For example:
Each database must consist of one or more tablespaces. (One-to-many relationship)
Each tablespace must be composed of one or more data files
File. (One-to-many relationship)
Each tablespace can contain one or more segments. (One-to-many relationship)
Each data file must consist of one or more operating system blocks (OS bolck. (One-to-many relationship)
Each segment must be composed of one or more intervals (one-to-multiple relationship)
Each interval must be composed of one or more Oracle data blocks (Oracle
Block. (One-to-many relationship)
Each interval must be located and can only be located in one data file. The space in the data file can be allocated with one or more intervals (Multiple-to-one relationship)
Each Oracle data block must be composed of one or more operating system data blocks (one-to-many relationship) Physical Structure
1. data File
File) is the operating system file that saves Oracle data. Many data files are created during database creation. These data files can store data dictionaries, SYSAUX tablespace data, and other tablespace data that you want to create at the same time.
2. Operating System Database (OS
Block) is the smallest allocation unit used by the file system. For example, 4 kb or 8 KB


Logical Structure
1. tablespaces SYSTEM tablespaces contain data dictionaries (tables that describe the database's own structure, all objects, users, and roles ). The SYSTEM tablespace is the location of the data dictionary in the database. If there is no SYSTEM tablespace, the database will not be able to operate
After creating a database, you need to create other tablespaces that store data.
2. segments are allocated to several segments in the segment tablespace. Segments are stored objects, such as a table or an index. Note: views do not store data, so they are not segments.
3. A partition (extent) is a collection of several adjacent data blocks allocated to a specific segment. You can manage partitions locally in a tablespace.
4. block is the smallest unit of I/O in the database. When the database needs to read data, it cannot read only one record, but must read the entire data block. The data block capacity cannot be modified only when the tablespace is created.