A Migration Job's Output File procedure reports "Failed to open file ... on DIRECTORY" even though the Oracle DIRECTORY object was created (logged in as the application-owner user) pointing at a Windows path that genuinely exists on the database server.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Create (or re-grant) the Oracle DIRECTORY object while logged in as SYS, then explicitly grant READ and WRITE on that directory to the application-owner schema (GRANT READ, WRITE ON DIRECTORY <name> TO <AppOwner>) — a DIRECTORY object created directly as the application-owner user without this explicit SYS-level grant can silently fail to actually provide the filesystem access the migration job needs, even though the object itself appears to exist correctly and the underlying Windows path is genuinely valid.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions