Skip To Content

Register an Oracle database with ArcGIS Server

As an ArcGIS Server administrator or a publisher in your organization, you have the option to register your on-premises data stores and cloud stores. In doing so, you are registering data folders, databases, and geodatabases with ArcGIS Server so that services you publish can reference the data in those folders, databases, and geodatabases. Data registration provides ArcGIS Server a list of locations to access. Data registration also helps ArcGIS Server adjust data paths when publishing across machines.

The following sections describe how to prepare your ArcGIS client to connect to an Oracle database (whether the database contains a geodatabase or not) and register the database with ArcGIS Server.

Install Oracle client software

Oracle client software must be installed on all ArcGIS client machines that will connect to the database. See Connect to Oracle from ArcGIS for instructions on installation and configuration of the Oracle client software. Use the following table to determine the appropriate configuration for your site:

Installation combinationsConfiguration to use

ArcGIS Server (single machine site) and Oracle are installed on the same server; ArcGIS Desktop is installed on different machines.

Install a 32-bit Oracle client on all ArcMap machines, and set the PATH variable to the Oracle client home directory.

Install a 64-bit Oracle client on all ArcGIS Pro machines, and set the PATH variable to the Oracle client home directory.

You do not need to install an Oracle client on the server because files to connect are installed with the Oracle DBMS. Just be sure the LD_LIBRARY_PATH (Linux server) or PATH (Windows server) system variable is set to the Oracle home directory.

If you set a tnsname for the Oracle client, you must use the same name on the ArcGIS Server , ArcMap, and ArcGIS Pro machines.

ArcGIS Server is installed on one or more machines that are separate from the DBMS. ArcGIS Desktop is on computers separate from both Oracle and ArcGIS Server.

Install a 32-bit Oracle client on all ArcMap machines, and set the PATH variable to the Oracle client home directory.

Install a 64-bit Oracle client on all ArcGIS Pro machines, and set the PATH variable to the Oracle client home directory.

Install the 64-bit Oracle client on all ArcGIS Server machines and be sure the PATH (Windows) or LD_LIBRARY_PATH (Linux) system variable is set to the Oracle client home directory.

If you set a tnsname for the Oracle client, you must use the same name on the ArcGIS Server , ArcMap, and ArcGIS Pro machines.

ArcGIS Server and ArcMap are installed on the same server; Oracle is installed on a different server.

You must install both the 64-bit and 32-bit Oracle clients on the machine where ArcGIS Server and ArcMap are installed.

Set the PATH variable so that the 64-bit Oracle client home directory is listed first.

If your ArcGIS Server site includes additional servers, install the 64-bit Oracle client on each of the servers in the site, and set the PATH variable to the Oracle client home directory.

ArcGIS Server and ArcGIS Pro are installed on the same server; Oracle is installed on a different server.

Install the 64-bit Oracle client on all ArcGIS Server machines. Both ArcGIS Server and ArcGIS Pro will use this client.

Set the PATH system variable to the Oracle client home directory.

ArcGIS Server, ArcMap, and Oracle are all installed on one machine.

Install the 32-bit Oracle client so that ArcMap can connect to the database.

ArcGIS Server will use the 64-bit client files installed with the Oracle DBMS to connect.

Make sure that the 64-bit Oracle home directory is listed first in the PATH system variable.

If your ArcGIS Server site includes additional servers, install the 64-bit Oracle client on each of the servers in the site, and set the PATH variable to the Oracle client home directory.

ArcGIS Server, ArcGIS Pro, and Oracle are all installed on one machine.

ArcGIS Server and ArcGIS Pro will use the 64-bit client files installed with the Oracle DBMS to connect.

Set the PATH variable to the Oracle client home directory.

If your ArcGIS Server site includes additional servers, install the 64-bit Oracle client on each of the servers in the site, and set the PATH variable to the Oracle client home directory.

Connect to Oracle

To register an Oracle database with an ArcGIS Server site, you'll need the following information:

  • The type of DBMS to which you are connecting (in this case, Oracle)
  • A valid Oracle connection string

    If your Oracle server and client are set up to use Easy Connect, you can provide a valid Easy Connect string. Some examples of this connection type are provided in Database connections in ArcMap. Or you can provide the Oracle tnsname. See Oracle's documentation for a full list of connection types and syntax.

  • The type of authentication to be used: database or operating system

    If database authentication is used, you must provide a valid database user name and password. You must save this information with the connection file.

    If operating system authentication is used, use a domain account for the ArcGIS Server account and add it to the Oracle database. ArcGIS Server will use this account to connect to the database.

Legacy:

Beginning with ArcGIS 10.3 geodatabases, you cannot use an ArcSDE service to connect to enterprise geodatabases. To connect to a 10.2.2 or earlier release enterprise geodatabase using an ArcSDE service, create an .sde file using the Create ArcSDE Connection File geoprocessing tool or a Python script, and import this connection when you register the geodatabase with ArcGIS Server.

Grant privileges

The database user, role, or ArcGIS Server account (if you're using operating system authentication) with which you connect to the database must be granted privileges in the database to access the data to be published. The privileges and the circumstances under which you need to grant them are as follows:

PrivilegeReason

CREATE SESSION

Required to connect to the database.

CREATE TABLE

Selection sets cause a log file table to be created in the geodatabase. You can change log file settings to avoid having to grant this privilege. See Log file table options for geodatabases in Oracle for more information.

SELECT privileges on the datasets to be published.

Grant the user or ArcGIS account at least SELECT privileges on the datasets to be published.

INSERT, UPDATE, and/or DELETE privileges on data published to editable feature services

To edit data through a feature service, privileges sufficient to edit must be granted on the datasets.

If you will be registering the geodatabase as a managed database, the account with which you connect must have privileges sufficient to create data in the geodatabase. See Privileges for geodatabases in Oracle for more information.

Register with ArcGIS Server

You can register the database from ArcGIS Server Manager or the Catalog tree in ArcMap. See the following topics for an explanation of registration options and how to register the database: