DBA Data Files – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™. Oracle EBS module: Database Administration · all Database Administration reports
Overview
Data and temp files per tablespace with their size, free space, autoextend settings and the space still available up to the maximum size.
All sizes are shown in MB.
Available Size and Max Used Percent take autoextend into account, so they show how close a file is to its real limit. Used and free space of temp files are shown by DBA Tablespace Usage.
In Backup Mode flags data files left in hot backup mode (alter tablespace … begin backup).
Schedule the report with Max Used Percent From, for example 90, to get an email only when a data file is close to full.
Run this report in Excel in seconds: download Blitz Report™ free (your first 30 reports are free) or try it in the online demo.
Report Parameters
Tablespace, Max Used Percent From
Oracle EBS Tables Used
dba_data_files, dba_tablespaces, v$backup, dba_free_space, dba_temp_files
Report Categories
Related Reports
DBA Tablespace Usage, DBA Blocking Sessions, DBA SGA Active Session History, DBA AWR Active Session History, DBA SGA Buffer Cache Object Usage, DBA SGA+PGA Memory Configuration, DBA Sessions, Blitz Report Web Service Sessions, DBA Undo Statistics
Running This SQL Without Blitz Report
The SQL source can be run in any SQL client. Some Oracle EBS SQL reports in this library use functions from the utility package xxen_util – install it first. Blitz Report™ adds parameters, Excel output with pivots, scheduling and security on top.
Download & Import Options
| Resource | Link |
|---|---|
| Excel Example Output | DBA Data Files 12-Oct-2026 061632.xlsx |
| Blitz Report™ XML Import | DBA_Data_Files.xml |
| SQL Source | DBA Data Files.sql |
| Full Report on Enginatics | www.enginatics.com/reports/dba-data-files/ |
Case Study & Technical Analysis: DBA Data Files
Executive Summary
The DBA Data Files report lists every data file and temp file in the database, grouped by tablespace, with its size, free space, autoextend settings and the space still available up to its maximum size. All sizes are shown in MB. Database administrators use it to see how close each file is to its real limit, which is the figure that matters for autoextend files, and to find files left in backup mode. It can also be scheduled with a Max Used Percent threshold so that an email is sent only when a data file is close to full.
Business Challenge
- Hidden capacity limits: An autoextensible file can look small while still having room to grow, and an un-extended file with no headroom can stop a batch job. Administrators need the real limit, not the current size.
- Early warning of full tablespaces: Tablespaces that fill up stop transactions and concurrent requests, so usage must be watched before it reaches capacity.
- Backup hygiene: Data files left in hot backup mode need to be spotted quickly, so that the backup state can be ended.
- Temp space visibility: Temp files are sized and used differently from data files, and they need their own capacity view.
The Solution
- File-level sizing: Each data file shows its total size, used size, free size and used percentage, computed from the free-space dictionary view.
- Autoextend-aware capacity: Available Size and Max Used Percent are calculated against the larger of the current size and the autoextend maximum, so the figures reflect the real ceiling.
- Backup status flag: The In Backup Mode column shows whether a data file is in hot backup mode and, if so, since when.
- Temp file coverage: Temp files appear in the same list, with their size and available space, while usage columns are left blank because they are shown by DBA Tablespace Usage.
Technical Architecture (High Level)
Primary Tables
DBA_DATA_FILES: the data files, with their size, autoextend flag, maximum size, increment and status.DBA_TABLESPACES: the tablespace contents type and block size, used for the increment calculation and for classifying files.V$BACKUP: the backup status of each file, used for the hot backup flag.DBA_FREE_SPACE: free extents, summed per file to give the free size.DBA_TEMP_FILES: the temp files, which are reported in a second branch of the query.
Logical Relationships
DBA_DATA_FILESis joined toDBA_TABLESPACESon tablespace name, and toV$BACKUPon file number, which is an outer join so files not in backup still appear.- An inline view sums
DBA_FREE_SPACEby file ID, and this result is outer joined to the data files, so a file with no free space still returns its full size as used. - A second query branch reads
DBA_TEMP_FILESjoined toDBA_TABLESPACES, and returns the temp file size and available size, with the usage columns set to null. - The two branches are combined with UNION ALL and ordered by tablespace name and file name.
Parameters & Filtering
- Tablespace: Limits the output to one tablespace, including its data and temp files.
- Max Used Percent From: Returns only files whose maximum used percentage is at or above the threshold. Setting it to 90 gives an alert-style list of files close to full.
Performance & Optimization
- Hinted inline views: The data file and free space inputs are kept as no-merge inline views, so the optimizer does not fold them into the main query.
- Free space aggregated per file:
DBA_FREE_SPACEis summed by file ID before the join, so each data file is matched to a single free-space row. - Backup status outer joined:
V$BACKUPis outer joined by file number, so the backup check does not remove files that are not in backup. - Threshold filtering on the outer query: The Max Used Percent filter is applied to the combined result, so it is evaluated once per file, including temp files.
FAQ
Q: Why is Available Size different from Free Size? A: Available Size adds the space still available through autoextend up to the maximum size, while Free Size only counts free space inside the current file size. Q: How do I get an alert only for files that are nearly full? A: Set Max Used Percent From to a threshold such as 90 and schedule the report, so only files at or above that level are returned. Q: Why are the usage columns blank for temp files? A: Temp file usage is reported by DBA Tablespace Usage, so this report shows only the size and available space for temp files.
Useful Links
- Blitz Report™ – World’s Fastest Oracle EBS Reporting Tool
- Oracle Discoverer Replacement – Import Worksheets into Blitz Report™
- Oracle EBS Reporting Toolkits by Blitz Report™
- Blitz Report™ FAQ & Community Q&A
- Supply Chain Hub by Blitz Report™
- Blitz Report™ Customer Case Studies
- Oracle EBS Reporting Blog
- Oracle EBS Reporting Resource Centre
© Enginatics GmbH