The first thing to try is to use a direct export path by specifying DIRECT=Y. Alternatively, you can try to increase the default BUFFER setting to a much larger value (like 1 million bytes) to see if that helps. The BUFFER parameter is for conventional path exports, not direct path exports though.
You did not specify how big your database is or other specifics like your platform, CPU speed, number of physical disk devices, RAM, etc. All of these can play an important role in your export time. For instance, you probably won't be able to export an entire 10TB database in less than 20 hours. But a 100GB database should have no problems being exported in 20 hours.
Otherwise, you'll have to find out why your export process is taking so long. This means you'll have to start your export, then find your export session in V$SESSION. Once you know your export session's SID and SERIAL#, you can query V$SESSION_EVENT and V$SESSION_WAIT to see where the export session is spending its time. To give you an idea, please examine a white paper on my Web site titled "Tuning an Import With Wait Events." The same concepts can be applied to your export sessions.
Dig Deeper on Oracle database backup and recovery
Related Q&A from Brian Peasland
Oracle expert Brian Peasland answers one reader's question about common pitfalls when connecting Oracle to outside programs. Continue Reading
One reader asks expert Brian Peasland a question about datafile sizes with the Oracle RMAN duplicate 10g command. Continue Reading
Managing parent table-child table relations in Oracle SQL environments is key to efficient programming. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.