1Z0-052 · Question #63
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…
The correct answer is E. Replace the dumpfile option with the network_link = devdb.us.oracle.com. This question tests how to resolve a Data Pump import failure caused by a missing dump file when importing across databases using a database link.
Question
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?
Options
- AAdd the user, SYSTEM, to the schemas option.
- BAdd the network_link = devdb.us.oracle.com option.
- CChange the dumpfile option to [email protected].
- DReplace the schemas option with the network_link = devdb.us.oracle.com
- EReplace the dumpfile option with the network_link = devdb.us.oracle.com
How the community answered
(56 responses)- A13% (7)
- B5% (3)
- C4% (2)
- D21% (12)
- E57% (32)
Why each option
This question tests how to resolve a Data Pump import failure caused by a missing dump file when importing across databases using a database link.
Adding SYSTEM to the schemas option would not resolve the ORA-31640 file-not-found error, which is caused by an inaccessible dump file path.
network_link and dumpfile are mutually exclusive in Data Pump; adding network_link while retaining dumpfile would still produce errors.
The syntax [email protected] is not a valid form for the dumpfile parameter in Oracle Data Pump.
The schemas parameter defines which objects to import and must be retained; replacing it with network_link would remove the required schema scope.
The ORA-31640 error confirms the dump file cannot be found on the PRODDB server because the file resides on DEVDB. Replacing the dumpfile parameter with network_link=devdb.us.oracle.com instructs Data Pump to stream objects directly from DEVDB to PRODDB over the existing database link, eliminating any need for a physical dump file on the target server. The dumpfile and network_link parameters are mutually exclusive, so dumpfile must be removed.
Concept tested: Data Pump import via database link network_link parameter
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/sutil/oracle-data-pump-import-utility.html
Topics
Community Discussion
No community discussion yet for this question.