Oracle Database / Storage, Undo & Redo
Check whether a tablespace is bigfile before extending it
A storage remedy suitable for a smallfile tablespace may be invalid for a bigfile tablespace. Confirm its type and current files first.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT tablespace_name, bigfile, status, contents, block_size FROM dba_tablespaces WHERE tablespace_name = 'APP_DATA';Read the result
BIGFILE identifies the tablespace design; CONTENTS distinguishes permanent, temporary and undo use. File-size ceilings also depend on block size and platform limits.
Resolve and verify
Choose the documented resize or growth method for this tablespace type and validate real storage headroom. Confirm quotas and autoextend ceilings separately.
Operational precautions
Do not blindly run ADD DATAFILE against a bigfile tablespace or assume UNLIMITED overrides physical limits.