Migrating to ArcSDE 64 bit on Linux or UNIX 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 using ArcSDE 32 bit with a 32-bit database and want to switch to using ArcSDE 64 bit and a 64-bit database, you must either move the database to the new DBMS instance or create a new database and move your existing data to it.

Steps:

First, upgrade your existing geodatabase if needed.
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. Grant upgrade permissions to the ArcSDE administrative user.

   For most geodatabases, this is the sde user. For geodatabases in Oracle created in a user's schema, this is the owner of the schema.

   See User permissions for geodatabases in PostgreSQL for a list of the privileges required to upgrade.

7. Create a backup of the existing database.
8. Upgrade the geodatabase to the 32-bit version of the ArcSDE release equivalent to the 64-bit release you plan to use.
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 paste them into the new $SDEHOME/etc directory folder on the 64-bit server after you install the ArcSDE component but before creating a geodatabase on the 64-bit server.
10. Setup a 64-bit version of the DBMS on a 64-bit server.
11. Re-create user accounts in the new database and on the new server if using operating system logins.
12. Install the 64-bit version of ArcSDE on the 64-bit server.

    See

13. Decide how you want to transfer your data. You can do one of the following:
    • Move the entire database from the 32-bit instance to the 64-bit instance using DBMS tools.
    • Set up a second geodatabase in the 64-bit database and use XML workspace documents to move the data from the old geodatabase to the new one.
    • Set up a second geodatabase in the 64-bit database and copy and paste the data in ArcGIS to move the data from the old geodatabase to the new one.
    • Set up a second geodatabase in the 64-bit database and use ArcSDE export files to move the data from the old geodatabase to the new one.

    If you decide to move the entire database, consult your DBMS documentation and use the method you prefer. Then start an ArcSDE service (if using one) using the sdemon -o start command.

14. If you decide to set up a second geodatabase and move the data, you can do the following:
    1. Create a geodatabase in the new 64-bit PostgreSQL instance.
       Note:

       If your site uses only direct connections to the geodatabase, you can skip starting an ArcSDE service. However, you must update the tnsnames.ora files on the client machines to connect to the new server and database.

    2. Move the data from the 32-bit geodatabase to the 64-bit geodatabase using XML workspace documents, copy and paste, or ArcSDE export files.

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

    3. After moving the data, rebuild indexes and update database statistics.
15. After testing to be sure everything is working properly in the new geodatabase, uninstall the ArcSDE component from the 32-bit server.