{"id":3710,"date":"2025-05-29T17:04:47","date_gmt":"2025-05-29T17:04:47","guid":{"rendered":"https:\/\/w3buddy.com\/?post_type=cposts&p=3710"},"modified":"2025-05-29T17:04:48","modified_gmt":"2025-05-29T17:04:48","slug":"tablespaces","status":"publish","type":"cposts","link":"https:\/\/w3buddy.com\/blog\/notes\/getting-started-with-oracle-dba\/tablespaces\/","title":{"rendered":"Tablespaces"},"content":{"rendered":"\n

\ud83e\udde0 What Is a Tablespace?<\/strong>
A tablespace is a logical storage container for segments like tables, indexes, and other schema objects that consume space.<\/p>\n\n\n\n

Think of it as a folder where Oracle stores structured data.
In a CDB (Container Database)<\/strong>, each PDB (Pluggable Database)<\/strong> and application root has its own set of tablespaces.<\/p>\n\n\n\n

\ud83d\udce6 Types of Tablespaces in Oracle Multitenant<\/strong><\/p>\n\n\n\n

Tablespace<\/th>Description<\/th><\/tr><\/thead>
SYSTEM<\/strong><\/td>\ud83d\udcda Contains the data dictionary \u2014 internal Oracle metadata like tables, views, triggers, and stored code. Required for every PDB.<\/td><\/tr>
SYSAUX<\/strong><\/td>\ud83e\uddf0 Auxiliary to SYSTEM. Holds data for Oracle features (like AWR, OEM, etc.) that used to require separate tablespaces.<\/td><\/tr>
UNDO<\/strong><\/td>\u21a9\ufe0f Stores undo information for rolling back transactions.
\u2022 Local undo mode (default):<\/em> Each PDB has its own undo tablespace.
\u2022 Shared undo mode (for Oracle RAC):<\/em> One undo tablespace per instance, shared across all containers.<\/td><\/tr>
TEMPORARY<\/strong><\/td>\u2744\ufe0f Stores temporary or transient data (e.g., sorting results).
Each CDB root, application root, and PDB has its own temporary tablespace.
No permanent objects reside here; data lasts only for the session.<\/td><\/tr>
User-Created<\/strong><\/td>\ud83e\uddd1\u200d\ud83d\udcbb Tablespaces you create to store user data like application tables and indexes.
You can use the default USERS tablespace or create custom ones (e.g., SALES_TBS, HR_TBS) for better organization and management.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

\ud83d\udcc2 How Tablespaces Fit Into Storage<\/strong>
Tablespaces map to physical data files on disk.<\/p>\n\n\n\n

    \n
  • One tablespace consists of one or more data files.<\/li>\n\n\n\n
  • Each PDB or application container manages its own tablespaces.<\/li>\n\n\n\n
  • Tablespaces are isolated, meaning data files aren\u2019t shared across tablespaces.<\/li>\n<\/ul>\n\n\n\n

    \ud83d\udee0\ufe0f DBA Tip of the Day<\/strong>
    \ud83d\udca1 Define custom tablespaces for large applications or critical modules. This helps improve performance, backup control, and storage management \u2014 especially in multitenant environments.<\/p>\n","protected":false},"excerpt":{"rendered":"

    \ud83e\udde0 What Is a Tablespace?A tablespace is a logical storage container for segments like tables, indexes, and other schema objects that consume space. Think of it as a folder where Oracle stores structured data.In a CDB (Container Database), each PDB (Pluggable Database) and application root has its own set of tablespaces. \ud83d\udce6 Types of Tablespaces […]<\/p>\n","protected":false},"template":"","meta":{"googlesitekit_rrm_CAowu461DA:productID":""},"categories":[960,952],"class_list":["post-3710","cposts","type-cposts","status-publish","hentry","category-getting-started-with-oracle-dba","category-notes"],"_links":{"self":[{"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/cposts\/3710","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/cposts"}],"about":[{"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/types\/cposts"}],"wp:attachment":[{"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/media?parent=3710"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/w3buddy.com\/blog\/wp-json\/wp\/v2\/categories?post=3710"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}