DataPump Import Fails With ORA-17502 And ORA-17500 When DumpFile Resides On A ZFS Shared Drive
(Doc ID 2200152.1)
Last updated on APRIL 03, 2020
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
- DataPump import fails with:
Import: Release 184.108.40.206.0 - Production on Thu Apr 20 10:15:13 2017
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 12c Enterprise Edition Release 220.127.116.11.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Advanced Analytics and Real Application Testing options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31640: unable to open dump file "<PATH>/<DUMP_NAME>.dmp" for read
ORA-17502: ksfdcre:3 Failed to create file <PATH>/<DUMP_NAME>.dmp
when the dump file is located on a shared folder which is a ZFS filesystem from a Solaris server using NFS.
- The import log file also shows the following additional error:
- The import job runs successfully when the dump files resides on a local filesystem.
- RMAN backup also fails to generate the backup pieces in this location:
ORA-19504: failed to create file "<PATH>/<FILE_NAME>.bck"
ORA-17502: ksfdcre:3 Failed to create file <PATH>/<FILE_NAME>.bck
ORA-17500: ODM err:Communication error on send
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document