We are getting a ORA-00257 error, which I know means no more disk space. Sure enough, the 70GB disk is full. Given that the entire database exports into a 245MB file, I went looking for culprits. (This is a machine we acquired during a recent corporate acquisition, then repurposed.) The most obvious culprit is the rman/ directory which contains five .dbf files and a snotload of log_tnnnnnnnnn_snnnn_p1 files. In this case, "snotload" is a technical term meaning approximately 18GB worth. The .dbf files are consuming another 22GB of disk space. None of these files shows a date more recent than March 20th. Obviously, I'd like to nuke these. Here are my concerns:
1) What are these files? If I'm not mistaken, RMAN is Oracle Replication Manager, and I'm pretty certain we're not using that (which would explain why it hasn't been touched since March 20th.)
2) This database is on a clustered Sun configuration running Solaris. I know enough about Unix to know that if there is an open file handle on the files, removing them won't do anything until the handle is closed. What might have these files open, and what do I need to do to make it let go?
3) Given that it's clustered, are there any other gotchas I should be aware of before I nuke these files?
Thanks!
Start Free Trial
