What I Learned From My First DBA Tablespace Rescue and Migration

I am a senior-year DBA intern who was asked to help a developer fix a stored‑procedure failure caused by a tablespace running out of space.

The error turned out to be that the tablespace was of type BIGFILE , which supports only a single data file that can grow to terabytes. Because the existing data file had reached its maximum, I attempted to add another file, but Oracle rejected it with the message “bigfile tablespace cannot add data file.”

After checking the OS, I discovered the underlying disk was only a 100 GB old drive that was nearly full, so the resize operation kept failing with file I/O errors. The mentor suggested increasing the data‑file size, but the OS still lacked free space, leading to repeated resize failures.

Eventually, we created a new regular tablespace, moved the user’s default to it, and retested the procedure. Although some data migrated successfully, the original tablespace still reported insufficient space, confirming that the root cause was the disk‑space shortage.

Later, the developer upgraded to a 500 GB disk and asked me to migrate the existing data files. The migration involved copying the data files, renaming them, and adjusting permissions. During the rename step, we encountered permission errors because the subdirectory permissions were set to 640 for the data file but should have been 755 for the directory.

Reflecting on the experience, I identified two major mistakes: (1) I failed to communicate clearly why I needed OS access, so the developer did not prioritize the request; (2) I abandoned the disk‑space hypothesis too early and got distracted by other troubleshooting steps, missing the obvious cause of the I/O errors.

Additional personal lessons include the importance of staying calm under pressure, avoiding assumptions about one’s role as an intern, keeping email notifications active to receive timely instructions, and always double‑checking permissions and environment constraints before proceeding with production changes.

These insights are shared to help other newcomers to the DBA field avoid similar pitfalls and develop stronger analytical and communication skills.