You specified extent management as local for a tablespace. How will it affect space management in the tablespace?

Local extent management does not enforce uniform extent sizes by itself; you choose between AUTOALLOCATE (system-managed variable sizes) or UNIFORM SIZE (fixed size), so extents can vary in size.

With local extent management, Oracle maintains a bitmap in the segment space management header of each data file within the tablespace, where each bit (or group of bits) represents the allocation status of an extent. This eliminates contention on the data dictionary tables (UET$ and FET$) and improves performance for concurrent space operations.

Managing free extents via data dictionary tables describes dictionary-managed tablespaces (the legacy method), which is the opposite of locally managed tablespaces.

Users can still explicitly specify extent sizes in locally managed tablespaces using the UNIFORM SIZE clause; the 'system managed' restriction applies only to segment space management (ASSM), not extent management.