Only IDC files larger than 1MB become BAD files; what is the most likely root cause?

Only IDC files larger than 1MB become BAD files; what is the most likely root cause?

• A. Tablespace is almost full.
• B. The database user lacks permissions to write to the directory.
• C. IDC files are corrupted during transfer.
• D. A network bandwidth bottleneck causing truncation.

Answer: (A)

The situation points to a storage-space issue in the place where IDC files are stored. When the tablespace is nearly full, the system can’t allocate enough space for larger IDC files, so those bigger files can’t be written and end up being marked BAD. Smaller IDC files can still fit, so they don’t trigger the same failure. The observed pattern—only files above a certain size become BAD—fits space constraints rather than a permission problem, data corruption, or a network truncation issue, which would affect files more broadly or in a non-size-dependent way. To fix this, check the tablespace usage and increase space or clean up old data.

The situation points to a storage-space issue in the place where IDC files are stored. When the tablespace is nearly full, the system can’t allocate enough space for larger IDC files, so those bigger files can’t be written and end up being marked BAD. Smaller IDC files can still fit, so they don’t trigger the same failure. The observed pattern—only files above a certain size become BAD—fits space constraints rather than a permission problem, data corruption, or a network truncation issue, which would affect files more broadly or in a non-size-dependent way. To fix this, check the tablespace usage and increase space or clean up old data.