Solution : https://service.sap.com/sap/support/notes/599694 (SAP Service marketplace login required)
Summary :
SAP Note discusses enhancements concerning extent allocations in Locally Managed Tablespaces (LMTS) with autoallocate attributes. It outlines standardized next extent sizes: 64K, 1M, 8M, 64M, facilitating reuse and reduced external fragmentation. Oracle independently sets the next extent based on former segment sizes, simplifying management and limiting configurable options. The note also touches upon the behavior under varying initial settings, detailing how initial sizes affect the distribution of extent sizes and offer examples of resultant segment configurations. Crucially, converting from dictionary-managed to locally-managed tablespaces might significantly increase storage requirements, especially in systems like BW with numerous small partitions.
Key words :
extent größe seg < 1m 64k 1m <= seg < 64m 1m64m <= seg < 1g 8m 1g <= seg 64mexample, terms lmts allocate extent extend dba_segments dba_tables dba_indexesnext initial autoallocate reason, prerequisites locally managed tablespace extent allocation autoallocate, lmts autoallocate tablespaces, select larger initial values, allocate 64k, locally managed tablespaces, 64m extents, dictionary managed tablespaces, require additional information
Related Notes :
| 666061 | FAQ: Database objects, segments and extents |
| 659487 | CC-ERROR: Resource analysis terminates on ORACLE |