Migrating to ArcSDE 64 bit on Windows when the existing DBMS is 32 bit

If you have an existing 32-bit ArcSDE installation, you cannot directly upgrade to a 64-bit installation.

If you are running ArcSDE as a 32-bit application connecting to an existing 32-bit database management system (DBMS), but you want to move to a 64-bit ArcSDE installation and a 64-bit DBMS, follow the instructions in this topic to migrate your geodatabase.

Steps:

First, upgrade your existing geodatabase if needed. For example, if you are moving from 32-bit ArcSDE 9.3 to 64-bit ArcSDE 10 and ArcGIS 10.
1. Reconcile all geodatabase versions with the default version.
2. Delete the other geodatabase versions.
3. Compress the geodatabase.
4. Stop the ArcSDE service, if one is running.

   sdemon -o shutdown -i <service> -s <server_name> -p <ArcSDE_administrator_password>

   ArcSDE command line tools and their documentation are installed with ArcSDE.

5. Make sure there are no users currently making a direct connection to the geodatabase.

   You can use the sdemon command to do this.

   sdemon -o users -i <service> -s <server_name> -p <ArcSDE_administrator_password>

6. Create a backup of the database.
7. Grant upgrade permissions to the ArcSDE administrator user if an upgrade of the geodatabase is necessary.

   See User permissions for geodatabases in Oracle for a list of permissions.

8. Upgrade your existing geodatabase.

   Follow the upgrade instructions for the geodatabase release to which you want to upgrade and that are specific to your DBMS.

9. If you were using custom configuration files (dbtune.sde, dbinit.sde, giomgr.defs) in the geodatabase on the 32-bit server, you may want to copy these files from the old %SDEHOME%\etc directory so you can place them in the new %SDEHOME%\etc directory on the 64-bit server after you install ArcSDE but before creating a geodatabase on the 64-bit server.
Next, set up the new server and database.
10. Install your 64-bit DBMS software on your 64-bit server.
11. If the process you will use to move your data or database to the new server does not include moving the users, re-create users (and schemas, if necessary) and grant database privileges.
12. Install the 64-bit version of the ArcSDE component on a 64-bit server (either the one on which the DBMS resides or a remote one). Do not proceed with the Post Installation wizard.
13. Update the st_shapelib.dll library definition in the Oracle data dictionary of your new database.

    CREATE or REPLACE LIBRARY <library_name> AS
    '<path_to_library>'

Lastly, move your data to the new DBMS.
14. Decide how you want to transfer your data. You can do one of the following:
    • If your DBMS offers functionality to move the entire database, you can use the DBMS tools to do so. Move the entire database from the 32-bit instance to the 64-bit instance using DBMS tools.
    • Set up a second geodatabase on the 64-bit instance and use XML workspace documents, copy and paste in ArcGIS, or the Feature Class to Feature Class (multiple) geoprocessing tool to move the data from the old geodatabase to the new one.

    If you decide to move the entire database, see your DBMS documentation for instructions. If you decide to set up a second geodatabase and move the data, do the following:

    1. Perform the postinstallation setup using the Post Installation wizard to create a new geodatabase on the 64-bit instance.
    2. In ArcGIS Desktop, connect to the 32-bit geodatabase and the new 64-bit geodatabase.
    3. Move the data from the 32-bit geodatabase to the 64-bit geodatabase using XML workspace documents, copy and paste, or the Feature Class to Feature Class (multiple) geoprocessing tool.

       You should have each user transfer his or her own data so it will be owned by that same user in the new geodatabase.

    4. After moving the data, rebuild indexes and update database statistics.
    Note:

    Moving the data to a new geodatabase does not move versioned edits. Therefore, if you are using a versioned geodatabase but did not perform steps 1 through 3, you could lose edits that were not moved into the base tables.

15. After testing to be sure everything is working properly in the new geodatabase, uninstall the ArcSDE component from the 32-bit server.