https://www.oraclescripts.com/tags/tablespace-monitoring/Recent content in Tablespace Monitoring on Oracle ScriptsHugo -- gohugo.ioenOracleScripts.comFri, 02 Feb 2024 00:00:00 +0000https://www.oraclescripts.com/post/query-segments-nearing-maximum-extents-in-oracle-database/Fri, 02 Feb 2024 00:00:00 +0000https://www.oraclescripts.com/post/query-segments-nearing-maximum-extents-in-oracle-database/ <h2 id="identify-oracle-database-segments-nearing-their-maximum-extent-limit">Identify Oracle Database Segments Nearing Their Maximum Extent Limit</h2> <p>Oracle ignores the <code>MAXEXTENTS</code> storage parameter for objects in a locally managed tablespace, unless the tablespace has <code>ALLOCATION_TYPE</code> set to <code>USER</code>. That one rule decides whether the query below is useful on your database. It is a real early warning in a dictionary-managed tablespace. In a default, locally managed tablespace it will usually return nothing, because the limit it measures is not enforced.</p>