I'm trying to export a schema from an Oracle 10.2.0.5.0 database. For some reason, when I launch the expdp command, it finishes almost immediately and it only creates the log file, no dump file at all. It must be some silly mistake but I can't figure it out.
This is the command I'm executing on the server (logged in SSH as the Oracle user):
expdp my_user/my_pass@db schemas=my_user directory=my_dir dumpfile=exp.dmp logfile=exp.log
With SYS I get the same result:
expdp \"sys/sys_pass@db as sysdba\" schemas=my_user ...
There is only one database in the server, so I've also tried without the
@db part. Same result.
I've checked that
my_dir is properly defined and points to an existing filesystem location on the server, with available space (~3.4 GB free) and where the Oracle user can read and write. I've also granted read and write privileges to
my_dir. And I've quadruple-checked that
my_user is the correct schema with the tables I want to export.
This is the only output I get, both on the console (except the
;;;) and the logfile:
;;; Export: Release 10.2.0.5.0 - 64bit Production on Monday, 08 April, 2019 13:27:31 Copyright (c) 2003, 2007, Oracle. All rights reserved. ;;; Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options
And then nothing. No dump file, no errors, no nothing. It just ends.
I've found this page with a few useful (?) queries.
dba_resumable are empty. There are a few exports in
dba_datapump_jobs, all of them with status
NOT RUNNING; I don't know for sure because there isn't any "date" field, but I think they are old jobs, they don't change when I launch the
What else can I check?
Edit: if I run
echo $? immediately after the
expdp command, it outputs
1, which according to this page (for Oracle 12c, not 10.2...), means "exit with fatal errors". Yet, not important enough to write them in the logfile?