Show Navigation | Hide Navigation
You are here:
Geodatabases and ArcSDE > Administering ArcSDE geodatabases > Installing and upgrading the ArcSDE component

Upgrade summary for ArcSDE geodatabases

Release 9.3
Last modified December 3, 2010
E-mail This Topic Printable Version Give Us Feedback

Print all topics in : "Installing and upgrading the ArcSDE component"

Related Topics

Note: This topic was updated for 9.3.1.

Listed below is the general sequence of tasks to install a newer version of the ArcSDE component, upgrade the ArcSDE and geodatabase system tables, and install updated stored procedures and locators for geodatabases licensed with ArcGIS Server Enterprise. For more complete information about upgrading, consult the installation guides provided with the ArcSDE component of ArcGIS Server Enterprise.

  1. Back up all databases.
  2. If you are using a geodatabase in DB2, you must delete all multiversioned views before upgrading. If you do not, the geodatabase upgrade will fail. The multiversioned views can be re-created after the upgrade completes. Before deleting them, be sure to check the permissions on the views so you can regrant them after they are re-created.
  3. Remove any custom functionality you may have added to the ArcSDE geodatabase system tables outside of ArcGIS such as triggers, participation in SQL Server replication, or additional indexes. The upgrade procedure cannot be aware of customizations you make to the system tables. If such customizations prevent the alteration of a system table's schema, the upgrade will fail.
  4. If you are using an ArcSDE service, stop (do not pause) the service before uninstalling the ArcSDE component. If you plan to re-create the service after upgrading, go ahead and delete the service as well.
  5. Uninstall the earlier version of the ArcSDE component.
  6. Install the new release of the ArcSDE component.
  7. For most DBMSs, elevated permissions are necessary for the administrative user to upgrade the geodatabase. These permissions are outlined in the ArcSDE installation guide for each DBMS. Be sure the administrative user is granted these permissions before proceeding.

  8. In addition, the ArcSDE administrator must have write permission to either the SDEHOME/geocode directory on the server or the directory to which the TEMP environment variable is set. This is because, during an upgrade, ArcSDE attempts to make backups of the locator files in the geocode directory. If that fails, ArcSDE attempts to write the backups to the TEMP directory. If the ArcSDE administrator does not have write permission to either of these directories, a warning is generated and new locators are loaded.

  9. Make sure there are no users currently connected to the geodatabase. If there are other connections to the geodatabase when you upgrade, upgrade will fail.
  10. Upgrade your geodatabase tables, stored procedures, and locators using the sdesetup –o upgrade command or, on Windows, run the repository setup portion of the Post Installation wizard. Consult the ArcSDE Administration Command Reference provided with the ArcSDE component of ArcGIS Server Enterprise for details on using the sdesetup command.

  11. Be aware that if you are using Oracle and have geodatabases in user schemas in addition to the SDE master geodatabase, you must separately run sdesetup to upgrade each of these geodatabases. Upgrade the SDE master geodatabase first, then the geodatabases in the user schemas. The upgrade must be run by the owner of the geodatabase and all geodatabases must be at the same release.

  12. If you received a new license file with the latest version of the ArcGIS Server Enterprise software, update the license key in the geodatabase by running the sdesetup –o update_key command or, on Windows, run the authorization portion of the Post Installation wizard. If you have more than one geodatabase, you need to update the license file in each of the geodatabases.

  13. On Windows, re-create and start the ArcSDE service (if used) using the ArcSDE service creation portion of the Post Installation wizard or the sdeservice and sdemon commands. On UNIX or Linux, start an ArcSDE service using the sdemon command.
ESRI recommends that you test upgrades of the geodatabase, upgrades of your DBMS, or upgrades to both on a separate development server. After you have tested the upgraded geodatabase on the development server and everything is working as you expected, you can upgrade your production geodatabase.

The following is a list of things to keep in mind when you upgrade:

Please visit the Feedback page to comment or give suggestions on ArcGIS Desktop Help.
Copyright © Environmental Systems Research Institute, Inc.