A technical repository for diagnosing failures that occur at the code-to-database interface. Instead of standard SQL tuning, these entries focus on software-level crashes. Each guide provides a deep-trace analysis and a verified path to stabilizing the internal execution engine.
ORA-06564 says “does not exist” — but the object usually does. The real failure is visibility: privilege boundaries, PDB namespace isolation, Data Pump migration gaps, or legacy scripts that assume pre-12c global directory scope. This article traces five distinct root causes behind the same error message and maps how directory object behavior changed across Oracle 11g through 23ai.
ORA-29400 covers four completely different failure modes — missing files, corrupted CSVs, disk exhaustion, and permission mismatches — behind one generic error code. This article traces each root cause through real production incidents in multi-tier architectures where Oracle External Tables depend on files from upstream services, and shows why the database is almost never where the problem actually started.