database, DEVDB, to the production database, PRODDB. A database link
devdb.us.oracle.com is created between PRODDB and DEVDB. You execute the following
command on the PRODDB database server:
$ impdp system/manager directory = DB_DATA
dumpfile = schemas.dat
schemas = hr
flashback_time = “TO_TIMESTAMP(’25-08-2007 14:35:00′, ‘DD-MM-YYYY
HH24:MI:SS’)”
The command fails displaying the following error:
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31640: unable to open dump file “/home/oracle/schema/schemas.dat” for read
ORA-27037: unable to obtain file status
What would you do to overcome the error?
A.
Add the user, SYSTEM, to the schemas option.
B.
Add the network_link = devdb.us.oracle.com option.
C.
Change the dumpfile option to [email protected].
D.
Replace the schemas option with the network_link = devdb.us.oracle.com
E.
Replace the dumpfile option with the network_link = devdb.us.oracle.com
The beginning of this question is missing.
Explanation:
[oracle@rtest ~]$ oerr ora 39000
39000, 00000, “bad dump file specification”
// *Cause: The user specified a dump file that could not be used in the
// current job. Subsequent error messages describe the inadequacies
// of the dump file.
// *Action: Specify a dump file that is usable for the job.
[oracle@rtest ~]$ oerr ora 31640
31640, 00000, “unable to open dump file \”%s\” for read”
// *Cause: Import was unable to open the export file for reading. This
// message is usually followed by device messages from the operating
// system.
// *Action: Take appropriate action to restore the device.
Action: Specify a dump file that is usable for the job
The beginning of this question is:
You want to import schema objects of the HR user using Oracle Data Pump from the development…