You can store ArcSDE geodatabases in Oracle databases. This does not require Oracle Spatial, but use of Oracle Spatial types is supported with ArcSDE geodatabases in Oracle.
To see which operating systems and database versions are supported, go to the
ESRI support site and navigate to System Requirements for ArcGIS Server.
NOTE: If there is no native ArcSDE build for the operating system of the server hosting the Oracle database, then there is no support for SQL access to ST_Geometry. ST_Geometry storage can be used from ArcSDE clients, but SQL access to this data is not supported.
The setup, installation, and postinstallation procedures vary slightly between operating systems. The steps in this topic are an overview of the preinstallation, ArcSDE component installation, and postinstallation setups for ArcSDE for Oracle. For complete instructions, including instructions for installing the DBMS and ArcSDE component on separate machines, read the installation guide provided on the ArcSDE component installation media.
Before you can install the ArcSDE component and set up the geodatabase, there are a few tasks you must complete.
On Windows
- Install and configure the Oracle database management system (DBMS). If you are going to install the ArcSDE component on a server separate from the DBMS, you also need to install the Oracle client on the server where the ArcSDE component is installed.
The topics Oracle initialization parameters, Minimize disk I/O contention in Oracle, Tuning memory in Oracle, and Configuring Oracle Net Services to use ST_Geometry SQL functions can help you with this. Also consult your Oracle documentation.
- Make sure the Windows TEMP environment variable is set to a writable folder.
On Linux or UNIX
- Install and configure the Oracle DBMS. If you are going to install the ArcSDE component on a server separate from the DBMS, you also need to install the Oracle client on the server where the ArcSDE component is installed.
The topics Oracle initialization parameters, Minimize disk I/O contention in Oracle, Tuning memory in Oracle, and Configuring Oracle Net Services to use ST_Geometry SQL functions can help you with this. Also consult your Oracle documentation.
- Create an SDE operating system (OS) account to own the SDEHOME files.
- Set environment variables.
NOTE: Beginning with Oracle 10g, nonadministrative users do not have access to ORACLE_HOME. Therefore, if your ArcSDE administrator (the sde user) is not an administrator on the server, this user has to install the Oracle client so it gets installed in a location the sde user has permission to access. The Oracle client needs to be installed on whichever server the ArcSDE component is installed on; this is true for local (ArcSDE and Oracle DBMS on the same machine) and remote (ArcSDE and Oracle on different machines) configurations. For information on supported clients and databases, consult the ArcGIS Server system requirements page on the ESRI support site.
The installation files for the ArcSDE component are on a separate DVD in the ArcGIS Server media kit.
On Windows
- Insert the installation DVD into the drive.
- Launch the installation wizard for ArcSDE for Oracle.
- Follow the instructions in the wizard to install the ArcSDE component of ArcGIS Server.
NOTE: You must be a Windows administrator to install any software on the machine.
On Linux or UNIX
- Place the ArcSDE component media into the appropriate drive and mount the drive.
- Change directories to the appropriate drive.
- Run the installation command appropriate to the shell you are using to open the command-driven dialog box for the ArcSDE component installation procedure.
- Follow the instructions in the installation procedure.
Tip
- New installations of ArcSDE at 9.3 do not create public synonyms for ST functions and operators. That means all ST functions, such as ST_Point, and operators, such as ST_Buffer, must be fully qualified. For example, you would type "sde.ST_Point" or "sde.ST_Buffer" rather than ST_Point or ST_Buffer when executing SQL commands.
If you upgrade to ArcSDE 9.3 for Oracle from a previous release of ArcSDE, the public synonyms will still be in your geodatabase and you will not be required to fully qualify ST functions and operators.
|
The postinstallation tasks
- Create the ArcSDE geodatabase system tables.
- Create the ArcSDE administrator user if it does not already exist and give it necessary permissions to the database.
- Authorize the ArcSDE component.
- Set up and start an ArcSDE service (if you plan to use one).
In preparing to create the ArcSDE geodatabase system tables, determine if you need to specify storage settings for these system tables and their indexes. These settings are grouped under the DATA_DICTIONARY configuration keyword in the dbtune.sde file. You would need to alter the configuration parameter values prior to creating the geodatabase, then specify the altered dbtune.sde file when the geodatabase is created.
If you created a default table space for your SDE user, the system tables and indexes will be created in the SDE user's default table space without you having to alter the DATA_DICTIONARY parameters in the dbtune.sde file.
For details on these parameters, see
The DATA_DICTIONARY keyword and its related topics
The dbtune file and the DBTUNE table,
DBTUNE configuration keywords, and
DBTUNE configuration parameter name-configuration string pairs.
To create the geodatabase, the SDE user must have specific privileges. See the required installation privileges listed in
User permissions for geodatabases in Oracle.
On Windows
- Grant EXECUTE privilege on DBMS_PIPE and DBMS_LOCK to PUBLIC in the database.
- Use the ArcSDE for Oracle Post Installation wizard to complete the postinstallation setup.
If you do not want to alter any settings in the files in SDEHOME\etc, you can continue with the Post Installation wizard as soon as the installation wizard completes. If you customized any of the files, open the Post Installation wizard from the Start menu (Start > All Programs > ArcGIS > ArcSDE).The Post Installation wizard lets you select configuration files, creates the geodatabase schema, authorizes the software, and creates and starts an ArcSDE service.
- Optionally, you can revoke extra privileges (those needed for the setup of the geodatabase) from the SDE user.
On Linux or UNIX
- Create an Oracle SDE user and table space.
A script, create_sde_oracle.sql, is installed in the SDEHOME > tools > oracle directory that can be used to create the Oracle SDE user and table space. See Sample scripts installed with ArcSDE for Oracle for details.
- Modify files in SDEHOME/etc and /etc/services.
- Run sdesetup to create the geodatabase schema and authorize the software.
- Grant EXECUTE privilege on DBMS_PIPE and DBMS_LOCK to PUBLIC.
- Start an ArcSDE service (if you will use one).
- Optionally, you can revoke extra privileges (those needed for the setup of the geodatabase) from the SDE user.
If you are using Real Application Cluster (RAC), you must rename the version_util package, utilize the version_util.no_state_seq.sbp package, and load the correct package by following these steps:
- Navigate to the SDEHOME/lib (UNIX or Linux) or SDEHOME\bin (Windows) directory.
- Rename the original version_util.spb file as version_util.seq.spb and rename the version_util.no_state_seq.spb as version_util.spb.
- Start SQL*Plus in the directory where the files reside and connect as the SDE user.
- Execute the following command:
start version_util.spb sde
- Ensure there are no errors after this command is executed.
If you are utilizing
user schema geodatabases in Oracle, you need to do this for the SDE master geodatabase and each geodatabase stored in a user's schema. When you do this for the user's geodatabase, you need to connect to SQL*Plus as the geodatabase owner and, when you execute the command, specify the geodatabase user. For example:
start version_util.spd crane
