Q
Problem solve Get help with specific problems with your technologies, process and projects.

Ways to speed up a full export

I have a database exclusively for ESRI SDE consisting mainly of imagery (approximately 2 terabytes and growing). Currently a full expdp takes 12+ hours. Are there any possible parameters and/or options to expedite a full expdp in a shorter timeframe?

I have a database exclusively for ESRI SDE consisting mainly of imagery (approximately 2 terabytes and growing). Currently a full expdp takes 12+ hours with 12 datafolders, directories with four parallel processes, and each filesize=5gig. I am currently using auto management for the SGA. Are there any possible parameters and/or options to expedite a full expdp in a shorter timeframe?
ESRI's ArcSDE is a subject near and dear to my heart as I have worked extensively with this product for over six years now . . . since SDE 3.0!

Your question is not SDE-specific, but rather VLDB in nature, or Very Large Database. As your database grows larger...

and larger, it takes longer and longer to perform certain operations, such as take a full export of your entire database. To speed up the full export, look at the DIRECT path export. The other suggestions are already being implemented, like exporting to multiple destinations in parallel.

One of the things I question is the need to perform a full export. Why are you doing this? I sure hope it is not to perform a backup of your database. The export/import and Data Pump utilities are really not the means to back up a multi-terabyte database. The biggest problem is the amount of time it takes to perform that backup. Additionally, the recovery process can take days and days. You are better served by using RMAN for your backup and recovery needs.

Typically with imagery, the data is pretty static. I should know as two of my databases server imagery and are pretty close to 20TB each right now. I would be up the proverbial creek if I had to perform a full export of either of these databases. And even if I had the time to perform the export, I just do not have 20TB of spare disk lying around for my export destination. Since the data is static, I can back it up once with RMAN. I can then let RMAN back up only those changes to my database. This way, my backup window shrinks considerably.

Dig Deeper on Oracle database backup and recovery

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close