- 17.9K All Categories
- 3.4K Industry Applications
- 3.4K Intelligent Advisor
- 73 Insurance
- 537.3K On-Premises Infrastructure
- 138.6K Analytics Software
- 38.6K Application Development Software
- 6K Cloud Platform
- 109.6K Database Software
- 17.6K Enterprise Manager
- 8.8K Hardware
- 71.2K Infrastructure Software
- 105.3K Integration
- 41.6K Security Software
Prioritize some tables in datapump extract
I've occasionally had the problem (and I've seen other people have too) where when doing a datapump extract of a schema or a large number of tables you sometimes want to extract a particular table first - it may be very dynamic or have a truncate run against it at regular intervals but it's size means it isn't extract until later on in the export - at which point it fails rendering the whole export invalid.
Generally doing the biggest tables first makes sense but it would be nice to flag problem tables in some way to say 'do this/these first'
You can kinf of trick datapump like this Oracle DBA Blog 2.0: Getting datapump to follow orders? but it would be much neater to just allow this functionality.
As the whole API has a PLSQL wrapper round it i don;t think this would be that difficult to implement - it would just be a slight change to the ordering algorithm?
The same could also be required with import where you maybe wanting to load parents before children if just uploading data.