nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is there a way to copy a Enterprise Geodatabase (SDE) to another remote location with out shutting down the database.

DanielWilson

We want to copy an enterprise geodatabase (SDE) from one location to another without shutting down the source database. We can use either SQL Server or Oracle. The dba's tell us they need to shutdown the database, which is an issue because users could have geoprocessing scripts running. ESRI replication is not an option because we have ETL's that delete and recreate feature classes.

Find more posts tagged with

Accepted answers

All comments

JoeBorgione

Can you run a complete back up to a file and then transfer the back up file to the remote location and import/extract there?

Anonymous User

With Oracle, you can try using exp or expdb for a full export to a dmp file that you can import in an different Oracle instance.

Regards

Jesús de Diego

George_Thompson

If you have Oracle RMAN, I believe that it can take a hot backup of the database and then that could be restored to a new instance of Oracle.

Oracle information:

Hot and Cold Backups - Overview - Oracle - Oracle - Toad World

Backing Up the Database

SQL Server information:

Backup Overview (SQL Server)

These might be some good spots to start.........

DanielWilson

The feedback I'm getting from the DBA's is that RMAN hot backup or exp/exdb can't be automated. We need to be able to automate the process.

George_Thompson

I am not sure of another way to do this unless they set up the RDBMS replication process which could cause issues with the Geodatabase functions that are built in and not supported, as far as I know.

How often do they want to make a copy?

DanielWilson

Ideally nightly, but every other night would also work. We went down the RDBMS replication path but it did not work because the destination needed to be read only and the SDE schema needs write access.

George_Thompson

Think that I am out of ideas. I do find it difficult that you could not script or schedule RMAN to do something like that.......

KevinDunlop

This is not an ideal way but you could create a python script that makes a FGDB each night and copies all feature class, datasets, and tables to it. Once they are in the FGDB you can copy them into other database. You could always go directly from the SDE and to SDE via the script and skip the FGDB if your system permits that. Then use windows task scheduler to automatically run the script at a certain time (ex: 2 am).

Problem with this method is that you are making a copy so you have to transfer everything not just the stuff that changed. In addition, you will need to delete the stuff at the destination before copying to prevent errors and duplication. In addition, you will have to copy every version you have if you are using versioning and they won't be linked properly in the destination.

Anonymous User

For sure exp/imp process can be automated....

Jesús de Diego

BirajaNayak

How big the geodatabase like how many feature dataset, feature classes and what is the maximum number of columns and rows a feature class has.

You can use copy and paste option in Arccatalog or geoprocessing tool to transfer data from one geodatabase to other after deleting them from receiving end. By stating so, the time taken for copy and paste should be suitable to your workflow. This process can be automated using python.

BirajaNayak

Another question is to understand your overall requirement so that we can suggest if there is any better approach to it. Please explain your holistic requirement and will go from there.

Anonymous User

We have SDE on Oracle. Weekly, we run RMAN that restores into a 'published' instance for consumption and to keep load away from the editing/managed instance.

Our DBA's set this up by:

1. Perform RMAN duplicate:

duplicate database to 'GISPUBLISHED' skip tablespace ORTHOS backup location 'F:\exports\GISPUBLISHED\RMAN';

2. Scheduled through Windows task scheduler, runs on the weekends not anytime near scheduled server backups.

The DB is only 2GB and takes approx. 20 minutes.

The published DB will drop while getting restored... but it's a copy so, whatev - doesn't kill dependent map services or the prod instance.

Depending on oracle version, you may have to delete some files:

del e:\oradata\GISPUBLISHED\*.* /q

del F:\fast_recovery_area\GISPUBLISHED\*.* /s /q

Enjoy,

Paul Giroux & DBA Dan!

Greater Sudbury

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.