Upgrading geodatabases in user schemas in Oracle

You can create multiple geodatabases in one Oracle database. When you do this, you create a geodatabase in the schema of a user other than that of the sde user. For this reason, these geodatabases are referred to as user-schema geodatabases. These geodatabases contain their own ArcSDE and geodatabase system tables.

However, geodatabases you create in the schema of a user other than the sde user in a geodatabase in Oracle are not entirely self-contained; there is some functionality, such as the ArcSDE service or user-defined types, that are only in the master geodatabase in the sde user's schema. As a result of this, the following are true:

• You cannot upgrade a user-schema geodatabase while the master geodatabase is being upgraded.
• You must upgrade the master geodatabase before you upgrade geodatabases in user schemas.
• You must make a backup of the entire database; creating a backup of only a user's schema does not include the user-defined types and functions.
• Stopping the ArcSDE service on the master geodatabase disables service connections to user-schema geodatabases.

You upgrade the geodatabase in a user's schema separately, after you have upgraded the master geodatabase. Additionally, the schema owner, not the sde user, must upgrade geodatabases in his or her schema and, therefore, must be granted permissions to upgrade.

If you try to upgrade a user-schema geodatabase before upgrading the master geodatabase, you will receive the following message:

Cannot upgrade a user schema geodatabase
when the master schema geodatabase is at a previous release.
The master schema geodatabase must be upgraded first.
ERROR: Geodatabase schema object install not completed.

It is recommended that you keep all the geodatabases in the same Oracle instance at the same ArcGIS release, but you do not have to upgrade all the user-schema geodatabases in the Oracle database if you are using a direct connection to the geodatabase.

Caution:

Users cannot register data in multiple geodatabases in the same Oracle database. If a user owns data that is registered in both the master sde geodatabase and a user-schema geodatabase or in multiple user-schema geodatabases, upgrading will fail. If this occurs, the user must move his or her data into one geodatabase. This can be done using import tools, export tools, or copy and paste. After the data is moved, delete it from the other geodatabase.

The following steps explain how to upgrade a user-schema geodatabase using the Upgrade Geodatabase tool opened from the Database Properties dialog box:

Steps:

1. Follow the instructions in Preparing to upgrade a geodatabase in Oracle.
2. Make sure a backup has been made of the entire Oracle database.
3. Make sure the master geodatabase is already upgraded.
4. Start ArcCatalog, or start ArcMap, ArcGlobe, or ArcScene and open the Catalog window.
5. Expand the Database Connections node.
6. Connect directly to the user-schema geodatabase, logging in as the schema owner.
7. Right-click the geodatabase connection and click Properties.
8. Click the General tab.

   If an upgrade is needed, the Upgrade Geodatabase button is active.

   If the Upgrade Geodatabase button is not active, it could be because the connecting client is at the same release as the geodatabase, your DBMS is not at a supported upgradable release, you are using an ArcSDE service connection rather than a direct connection to the geodatabase, or you are connecting from an ArcGIS for Desktop Basic client.

Note:

You cannot run the Upgrade Geodatabase tool if any other geoprocessing tools are currently running as background processes on the client machine.

9. Esri recommends that you leave both the Pre-requisites check and Upgrade geodatabase options checked on the Upgrade Geodatabase geoprocessing tool. That way, the tool checks to see whether the prerequisites to upgrade have been met before continuing with the geodatabase upgrade.

   The prerequisite check detects other active connections to the geodatabase, whether the connecting user has sufficient privileges to upgrade the geodatabase, and that the database can support XML columns; makes sure all datasets can be opened; ensures that the master geodatabase has been upgraded before any user-schema geodatabases can be upgraded; and detects that the database and libraries are at the same release. If any prerequisite is not met, the tool terminates. You must correct any problems before you run the upgrade procedure again.

   The results of this check are reported on the geoprocessing tool dialog box. If the check (or upgrade) fails, results are also written to the GDBUpgrade.log, which can be found in c:\ Documents and Settings \<user name>\ Local Settings\Application Data\ESRI\<ArcGIS product> on Windows XP and Server 2003 operating systems; c:\Users\<user name>\AppData\Local\ESRI\<ArcGIS product> on Windows Vista, 7, or Server 2008 operating systems; or <user home>/.arcgis<#>/Application Data/ESRI on Linux operating systems.

10. Click OK to start the checks and upgrade.
11. If all checks are passed, the tool proceeds with the upgrade. The status for the prerequisites check and the upgrade are shown on the geoprocessing tool progress dialog box. If the upgrade fails, information is written to the GDBUpgrade.log. Additional information is written to the sdesetup.log, which can be found in the system TEMP directory.
12. When the tool successfully completes, click Close to close the geoprocessing tool progress dialog box.

Your geodatabase is upgraded to the latest release.

To upgrade network datasets, parcel fabrics, or mosaic datasets in the geodatabase, use the Upgrade Dataset geoprocessing tool or a Python script.

Note:

Upgrades of network datasets, parcel fabrics, or mosaic datasets are optional. However, if you do not upgrade them, you do not have access to the latest functionality in these datasets.