Skip to main content

How to Add a Temporary Tablespace in Oracle Standalone Database

🧱 How to Add a Temporary Tablespace in Oracle Standalone Database

Temporary tablespaces in Oracle are used for sorting operations, managing global temporary tables, and handling intermediate result sets. It's a good practice to add or manage these tablespaces especially in large databases or when the default temp tablespace gets full or fragmented.

In this guide, we'll walk you through a clean and safe method to create a new temporary tablespace, make it default (if needed), and drop the old one (optional).


πŸ”§ Step-by-Step Instructions

1️⃣ Connect to the Database as SYSDBA

sqlplus / as sysdba
-- or
sqlplus sys@ORCL as sysdba

2️⃣ Identify Existing Temporary Tablespaces

SELECT tablespace_name, status, contents 
FROM dba_tablespaces 
WHERE contents = 'TEMPORARY';

3️⃣ Create a New Temporary Tablespace

CREATE TEMPORARY TABLESPACE temp_new
TEMPFILE '/u01/app/oracle/oradata/ORCL/temp_new01.dbf'
SIZE 500M
AUTOEXTEND ON NEXT 100M MAXSIZE 5G
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

πŸ’‘ Tip: Adjust the TEMPFILE path and sizing parameters based on your filesystem and usage needs.

4️⃣ Make the New Temp Tablespace Default (Optional)

ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp_new;

5️⃣ Verify the Default Temporary Tablespace

SELECT property_name, property_value 
FROM database_properties 
WHERE property_name = 'DEFAULT_TEMP_TABLESPACE';

6️⃣ Drop the Old Temp Tablespace (Optional)

DROP TABLESPACE temp_old INCLUDING CONTENTS AND DATAFILES;

⚠️ Caution: Ensure the tablespace is no longer in use and is not the default before dropping it.


🧠 Why Manage Temporary Tablespaces?

  • Improve performance during large sorts and index creations.
  • Prevent "Temp Segment Full" errors by allocating enough space.
  • Enable better segregation for different types of workloads.

🚨 Best Practices

  • Always use EXTENT MANAGEMENT LOCAL and UNIFORM SIZE for better management.
  • Monitor temp usage with v$tempseg_usage and dba_temp_files.
  • Use AUTOEXTEND carefully to avoid unexpected filesystem usage spikes.

🎯 This process ensures your Oracle database handles temporary operations efficiently, helping prevent common space-related issues during sorts, joins, and global temp table operations.

Comments

Popular posts from this blog

πŸš€ Automating Oracle Database Patching with Ansible: A Complete Guide

Oracle database patching has long been the bane of DBAs everywhere. It's a critical task that requires precision, expertise, and often results in extended maintenance windows. What if I told you that you could automate this entire process, reducing both risk and downtime while ensuring consistency across your Oracle estate? πŸ’‘ In this comprehensive guide, I'll walk you through a production-ready Ansible playbook that completely automates Oracle patch application using OPatch. Whether you're managing a single Oracle instance or hundreds of databases across your enterprise, this solution will transform your patch management strategy! 🎯 πŸ”₯ The Challenge: Why Oracle Patching is Complex Before diving into the solution, let's understand why Oracle patching is so challenging: πŸ”— Multiple dependencies : OPatch versions, Oracle Home configurations, running processes ⚠️ Risk of corruption : Incorrect patch application can render databases unusable ⏰ Downtime requirements : Da...

🐳Oracle 19c Database Deployment with Docker

Oracle 19c Database Deployment with Docker 🐳 Oracle 19c Database Deployment with Docker Welcome to this comprehensive guide on deploying, configuring, and managing Oracle 19c Database using Docker containers. This blog will walk you through the entire process from setup to production best practices with practical code examples. Docker provides an excellent way to run Oracle databases in isolated, portable containers, making it easy to deploy and manage Oracle 19c instances for development, testing, and production environments. This approach offers numerous benefits: πŸ”’ Isolation : Run Oracle in a containerized environment without affecting your host system 🚚 Portability : Easily move your database between different environments πŸ”„ Reproducibility : Quickly spin up identical database instances ⚡ Resource Efficiency : Use Docker's resource management capabilities to control CPU, memory, and stor...

πŸš€ DB BOT: Real-Time Oracle & GoldenGate Monitoring in Slack

In today's fast-paced DevOps environment, quick access to database metrics is essential. This blog will walk you through creating a Slack bot that provides real-time monitoring of Oracle databases and Golden Gate replication. With simple slash commands, your team can check tablespace usage, Flash Recovery Area status, and Golden Gate replication health directly in Slack. Project Overview Our "DB Bot" offers these key capabilities: Monitor tablespace usage across multiple Oracle databases Check Flash Recovery Area (FRA) status on multiple databases View GoldenGate process status across different servers List GoldenGate credential stores Monitor replication lag in GoldenGate Prerequisites Node.js v14+ Python 3.6+ Oracle client libraries (instantclient_21_19) Access to Oracle databases and GoldenGate servers A Slack workspace with permissions to add apps   Project Structure oracle-slack-bot...