Issue 1:
Encounter ora-31650 when using EXPDP
D:\oracle\diag\rdbms \TRACE>EXPDP \ "/As Sysdba\" Schemas=justin dumpfile=justin_120803.dmp Directory=datapumpdir
Connected to:oracle Database 11g Enterprise Edition Release 11.2.0.2.0-64bit Production
With the partitioning, OLAP, Data Mining and Real application testing options
Ora-31626:job does not exist
Ora-31650:timeout waiting for Master process response
The common reason for MOS is
1 RAC different nodes try to use EXPDP at the same time
2 SGA Insufficient, adjustment sga_target at least 1G
3 aq_tm_processes=0
Workaround:
But the database is a single instance, and sga_target/sga_max_size=8g should be enough, should be the 3rd reason, sure enough aq_tm_processes set to 0, just started to 2, still hold the wrong, and then changed to 10 to succeed. Restart the DB to take effect:
Issue 2:
EXPDP Export encountered ORA-39064: Could not write to log file
EXPDP Export encountered ORA-39064: Could not write to log file
[HTML]View Plain copy
- . . "User_xxxx" was exported. " Tab_yyyy "0 KB 0 rows
- ORA-39064: Unable to write to log file
- ORA-29285: File Write error
After searching for MOS, the following article gives a solution:
Error ORA-39064 might be encountered by DataPump Export (EXPDP) when Nls_lang are Different from Database Character Set (do C ID 1321034.1)
The solution given in this scenario is: Please set the character set in environment variable Nls_lang to database character set.
Here's how:
Set nls_lang=
12C EXPDP Issue