<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data Dictionary Views on Oracle Scripts</title><link>https://www.oraclescripts.com/tags/data-dictionary-views/</link><description>Recent content in Data Dictionary Views on Oracle Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>OracleScripts.com</copyright><lastBuildDate>Sun, 04 Feb 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://www.oraclescripts.com/tags/data-dictionary-views/index.xml" rel="self" type="application/rss+xml"/><item><title>Identifying User Tablespaces and Space Usage in Oracle</title><link>https://www.oraclescripts.com/post/query-oracle-tablespace-usage-by-user/</link><pubDate>Sun, 04 Feb 2024 00:00:00 +0000</pubDate><guid>https://www.oraclescripts.com/post/query-oracle-tablespace-usage-by-user/</guid><description>
&lt;h2 id="query-to-display-all-tablespaces-used-by-a-specified-user-and-the-total-space-occupied-rounded-to-mb"&gt;Query to Display All Tablespaces Used by A Specified User and The Total Space Occupied (rounded to MB)&lt;/h2&gt;
&lt;p&gt;A schema audit before a migration, a quota review before approving more space, or a tablespace consolidation project all start with the same question: which tablespaces does a specific Oracle user actually touch, and how much room do they take up in each one? DBA_EXTENTS answers that question directly, without needing to know the schema's object list in advance or walking DBA_TABLES and DBA_INDEXES separately to build the same picture by hand.&lt;/p&gt;</description></item></channel></rss>