Preamble
The ALTER TABLESPACE operator is used to change the table space or one of its data files or temporary files. TABLESPACE is used to allocate space in an Oracle database where schema objects are stored.
Syntax for ALTER TABLESPACE operator in Oracle / PLSQL
ALTER TABLESPACE tablespace_name
{ DEFAULT
[ { COMPRESS | NOCOMPRESS } ] storage_clause.
| MINIMUM EXTENT integer [ K | M | G | T | P | E ]
| RESIZE integer [ K | M | G | T | P | E ]
| COALESCE
| RENAME TO new_tablespace_name
| { BEGIN | END } BACKUP
| { ADD { DATAFILE | TEMPFILE }
[ file_specification
[, file_specification ]
]
| DROP {DATAFILE | TEMPFILE } { 'filename' | file_number }
| RENAME DATAFILE 'filename' [, 'filename' ] TO 'filename' [, 'filename' ]
| { DATAFILE | TEMPFILE } { ONLINE | OFFLINE }
}
| { logging_clause | [ NO ] FORCE LOGGING }
| TABLESPACE GROUP { tablespace_group_name | " }
| { ONLINE
| OFFLINE [ NORMAL | TEMPORARY | IMMEDIATE ]
}
| READ { ONLY | WRITE }
| { PERMANENT | TEMPORARY }
| AUTOEXTEND
{ OFF
| ON [ NEXT integer [ K | M | G | T | P | E ] ]
[ MAXSIZE { UNLIMITED | ] ] [ K | M | G | T | P | E ] ] ?
}
| FLASHBACK { ON | OFF }
| RETENTION { GUARANTEE | NOGUARANTEE }
} ;
Parameters and arguments of ALTER TABLESPACE operator
- tablespace_name – the name of the tabular space to be deleted from the Oracle database.
- storage_clause – the syntax for the file storage_clause:
STORAGE
({ INITIAL integer [ K | M | G | T | P | E ]
| NEXT integer [ K | M | G | T | P | E ]
| MINEXTENTS integer
| MAXEXTENTS { integer | UNLIMITED }
| PCTINCREASE integer
| FREELISTS integer
| FREELIST GROUPS integer
| OPTIMAL [ K | M | G | T | P | E ] | NULL ]
| BUFFER_POOL { KEEP | RECYCLE | DEFAULT }
}
[ INITIAL integer [ K | M | G | T | P | E ]
| NEXT integer [ K | M | G | T | P | E ]
| MINEXTENTS integer
| MAXEXTENTS { integer | UNLIMITED }
| PCTINCREASE integer
| FREELISTS integer
| FREELIST GROUPS integer
| OPTIMAL [ K | M | G | T | P | E ] | NULL ]
| BUFFER_POOL { KEEP | RECYCLE | DEFAULT }
]
)
- file_specification – syntax for file_specification parameter:
{ [ 'filename' | 'ASM_filename' ].
[ SIZE integer [ K | M | G | T | P | E ] ]
[ REUSE ]
[ AUTOEXTEND
{ OFF
| ON [ NEXT integer [ K | M | G | T | P | E ] ]
[ MAXSIZE { UNLIMITED | ] ] [ K | M | G | T | P | E ] ] ?
}
]
| [ 'filename | ASM_filename']
| ('filename | ASM_filename')
[, 'filename | ASM_filename' ] ).
]
[ SIZE integer [ K | M | G | T | P | E ] ]
[ REUSE ]
}
Example: Renaming a data file
Consider the ALTER TABLESPACE operator, which renames the data file associated with the table space. For example:
ALTER TABLESPACE tbs_01 OFFLINE NORMAL;
ALTER TABLESPACE tbs_01
RENAME DATAFILE 'tbs_01.dat'
TO 'tbs_01_new.dat';
ALTER TABLESPACE tbs_01 ONLINE;
This ALTER TABLESPACE operator will take the table space in OFFLINE mode, and rename the data file from tb_01.dat to tb_01_new.dat, and then bring the table space back to ONLINE.
Example: Add a data file
Let’s consider the ALTER TABLESPACE operator, which adds a data file to the table space.
For example:
ALTER TABLESPACE tbs_02
ADD DATAFILE 'tbs_02.dat'
SIZE 20M
AUTOEXTEND ON;
This ALTER TABLESPACE operator adds the data file tbs_02.dat to the table space tbs_02.
Example: The TABLESPACE operator adds the data file tbs_02.dat to the table space tbs_02
Consider the ALTER TABLESPACE operator, which removes the data file from the table space. For example:
ALTER TABLESPACE tbs_03
DROP DATAFILE 'tbs_03.dat';
This ALTER TABLESPACE operator removes the data file tbs_03.dat in the table space tbs_03.
Example of adding Tempfile
Let’s consider the ALTER TABLESPACE operator, which adds a temporary file to the table space. For example:
ALTER TABLESPACE tbs_04
ADD TEMPFILE 'tbs_04.dat'
SIZE 10M
AUTOEXTEND ON;
This example of the ALTER TABLESPACE operator adds a temporary tbs_04.dat file to the tbs_04 table space.
Example of removing Tempfile
Let’s consider an example of the ALTER TABLESPACE operator, which removes a temporary file from the table space. For example:
ALTER TABLESPACE tbs_05
DROP TEMPFILE 'tbs_05.dat';
This example of the ALTER TABLESPACE operator will delete the temporary file tbs_05.dat in the table space tbs_05.
Alter Tablespace in Oracle
About Enteros
Enteros offers a patented database performance management SaaS platform. It proactively identifies root causes of complex business-impacting database scalability and performance issues across a growing number of clouds, RDBMS, NoSQL, and machine learning database platforms.
The views expressed on this blog are those of the author and do not necessarily reflect the opinions of Enteros Inc. This blog may contain links to the content of third-party sites. By providing such links, Enteros Inc. does not adopt, guarantee, approve, or endorse the information, views, or products available on such sites.
Are you interested in writing for Enteros’ Blog? Please send us a pitch!
RELATED POSTS
What Are the Biggest Database Performance Challenges Facing Modern Banks?
- 4 September 2026
- Database Performance Management
Modern banks face serious database performance challenges in banking, including transaction bottlenecks, growing data volumes, slow queries, legacy infrastructure, cloud complexity, security requirements, scalability problems, and limited real-time visibility. These issues can delay payments, affect digital banking experiences, increase operational risk, and raise infrastructure costs. Effective database monitoring and optimization help banks maintain reliable, responsive … Continue reading “What Are the Biggest Database Performance Challenges Facing Modern Banks?”
How Can Banks Improve Database Performance for High-Volume Financial Transactions?
Banks can improve database performance for high-volume financial transactions by reducing query latency, optimizing indexes, balancing workloads, monitoring database behavior in real time, and identifying bottlenecks before they affect customers. A strong bank database performance strategy combines observability, capacity planning, automation, and intelligent database performance optimization to keep payment, trading, lending, and digital banking systems … Continue reading “How Can Banks Improve Database Performance for High-Volume Financial Transactions?”
What Are the Most Common Database Performance Issues in Healthcare IT Systems?
The most common database performance issues in healthcare include slow SQL queries, poor indexing, locking, blocking, high concurrency, storage latency, resource contention, execution-plan changes, database growth, and workload spikes. EHR database performance issues can slow clinical workflows and patient-facing systems. Enteros helps healthcare IT teams detect anomalies, investigate root causes, optimize SQL, and improve database … Continue reading “What Are the Most Common Database Performance Issues in Healthcare IT Systems?”
How Can Hospitals Improve Database Performance for Faster EHR and Clinical Workflows?
Improving hospital database performance requires continuous monitoring, SQL optimization, indexing, workload analysis, anomaly detection, root cause analysis, and proactive capacity planning. Hospitals should also track latency, locking, storage I/O, and resource utilization across EHR and clinical systems. Enteros helps healthcare IT teams use AI-powered observability and performance intelligence to improve reliability, responsiveness, scalability, and healthcare … Continue reading “How Can Hospitals Improve Database Performance for Faster EHR and Clinical Workflows?”