Connect to Oracle from ArcGIS

To connect to Oracle from ArcGIS clients, install an Oracle client on the ArcGIS client machines, set environment variables that reference the Oracle client, and create a database connection from ArcGIS.

To publish ArcGIS Server web services that reference the data in the Oracle database, register the database connection file with your ArcGIS Server sites.

Install Oracle client software

Oracle client software must be installed on all ArcGIS client machines that will connect to the database. If you do not have the privileges to install software on the machines where ArcGIS clients are running, you'll need to have your IT department install and configure the Oracle client for you.

Install a release of the Oracle client application that is compatible with the release of the database to which you want to connect.

You can obtain the Oracle Instant, Runtime, or Administrator Client from Oracle, and install it on the client computer, following the directions in your Oracle documentation.

Use the information in the following table to determine the appropriate Oracle client configuration to use:

Installation combinations	Configuration to use
ArcGIS Server (single-machine site) and Oracle are installed on the same server; ArcGIS Pro is installed on different machines.	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 database management system. Ensure the LD_LIBRARY_PATH (Linux) or PATH (Microsoft Windows) 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 and ArcGIS Pro machines.
ArcGIS Server is installed on one or more machines that are separate from the DBMS. ArcGIS Pro is installed on computers separate from both Oracle and ArcGIS Server.	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 ensure 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 and ArcGIS Pro machines.
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, ArcGIS Pro, and Oracle are installed on one machine.	ArcGIS Server and ArcGIS Pro will use the 64-bit client files installed with the Oracle database management system 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 from ArcGIS Pro

After you install the Oracle client on the ArcGIS Pro computer, set the PATH environment variable to the location of the Oracle client and create a database connection.

Set the PATH variable

Set the PATH environment variable on the ArcGIS Pro machine to the location of the Oracle Client installation. See the Microsoft Windows documentation if you need instructions for setting the PATH environment variable.

If ArcGIS Pro was open on the machine before you set the PATH variable, restart it to pick up the new setting.

Connect to the database

Add a database connection using the Database Connection dialog box or the Create Database Connection geoprocessing tool.

The following steps describe using the Database Connection dialog box to connect to Oracle.

1. Open the Catalog pane in ArcGIS Pro.
2. Right-click Databases and click New Database Connection.
3. Choose Oracle from the Database Platform drop-down list.
4. Either type the Oracle TNS name in the Instance text box, or provide one of the following Oracle Easy Connect strings:
   • The name of the Oracle server/Oracle service name or ID

     For example, if Oracle is installed on myserver and myosvc is the Oracle service name, type the following:

     myserver/myosvc

   • The name of the Oracle server:Oracle port number/Oracle service name or ID

     In this example, Oracle is installed on myserver, is listening on port 60000, and myoservice is the Oracle service name.

     myserver:60000/myoservice

   • The URL of the Oracle server

     The URL for the same instance shown in the last example would be the following:

     //myserver:60000/myoservice

   • The name of the Oracle server (You can use this if the Oracle listener on the server is configured to point to a default instance.)
   • The IP address of the Oracle server/Oracle service name or ID

     For example, if the address of the server is 10:10:10:10, and the Oracle service name is orasvc, type 10:10:10:10/orasvc.

     For IPV6 addresses, place brackets around the address, for example, [4000:ab5:0:0:f666:d191:77f5:e2bd]/orasvc.

   • The IP address of the Oracle server:Oracle port number/Oracle service name or ID

     In this example, the IP address is 10:20:30:40, port is 59999, and the Oracle service is myomy1: 10:20:30:40:59999/myomy1.

     An IPV6 address for the same port and service would look like the following: [6543:ef4:0:1:f587:l249:12f9:a3cd]:59999/myomy110:20:30:40:59999/myomy1.

   Ensure your Oracle instance is configured to allow Easy Connect. If you have the full Oracle client installed but want to use Easy Connect syntax to connect, ensure the sqlnet.ora file on the client is configured to allow the use of Easy Connect and the Oracle server is configured to allow Easy Connect syntax. Also note that if your Oracle instance is not listening on the default Oracle port number, you must use connection syntax that includes the port number.

5. Choose the type of authentication to use when connecting to the database: Database authentication or Operating system authentication.
   • If you choose Operating system authentication, you do not need to type a username and password—the connection is made using the login name and password used to sign in to the operating system. If the login used for the operating system is not a valid database login, the connection fails. Be aware that you cannot use operating system authentication if you are using the Oracle instant client.

     Note:

     When you use operating system authentication in Oracle, the operating system login is prefixed with an os_authent_prefix string (by default, OPS$) and stored in the USERNAME table. The maximum number of characters allowed for the username when connecting to the geodatabase is 30. In these specific cases, ArcGIS will place quotation marks around your username to pass it to the database. Those quotation marks count toward the 30-character total.

   • If you choose Database authentication, you must provide a valid database username and password in the User name and Password text boxes, respectively. Usernames can be a maximum of 30 characters.

     Uncheck Save user name and password if you prefer not to save your login information as part of the connection; doing this can help maintain the security of the database. However, if you do this, you will be prompted to provide a username and password every time you connect.

   Note:

   Save user name and password must be checked for connection files that use database authentication and provide ArcGIS web services with access to the database, or if you want to search ArcGIS Pro to locate data accessed through this connection file.

6. Type a name for the connection file in the Connection File Name field.

   As you provide connection information, a default name is created. You can use the default, or type a more descriptive file name.

   This is the name that will appear in the Catalog pane and view, and the name of the .sde file stored on disk.

7. Optionally, expand the Additional Properties section and specify additional parameters to connect that are in addition to those required in the previous steps.

   Type the required property in the Property field and type the corresponding value in the Values field.

   Read the Oracle documentation for information about additional and optional connection parameters.

8. Click Validate to confirm that the connection information is valid and the database is accessible.

   If the database contains a geodatabase and the connection is valid, the Geodatabase Properties tab is now active. If necessary, you can alter geodatabase connection properties to connect to a traditional version other than the default version, configure the connection as a branch version connection, or connect to a historical moment.

9. Click OK to create the connection file.

A database connection appears under Databases in the Catalog pane, and a connection file (.sde) is created in the ArcGIS Pro project directory.

Connect from ArcGIS Server

After you install a 64-bit Oracle client on all machines in the ArcGIS Server site, set variables, create a database connection file, grant privileges, and register the database with your ArcGIS Server site.

Set the PATH environment variable (Windows only)

Set the PATH environment variable on each ArcGIS Server Windows server to the location of the Oracle Client installation. See the Microsoft Windows documentation if you need instructions for setting the PATH environment variable.

If ArcGIS Server was running before you configured the Oracle client and set the PATH variable, you must restart ArcGIS Server. You can restart ArcGIS Server from the Windows Services interface.

Set the LD_LIBRARY_PATH environment variable (Linux and Oracle Administrator, Developer, or Runtime client only)

If you installed the Oracle Administrator, Developer, or Runtime client, set the LD_LIBRARY_PATH system variable to the Oracle client home directory.

If you installed the Oracle Instant client, set the LD_LIBRARY_PATH variable in the init_user_param.sh script.

Alter the init_user_param.sh script (Linux only)

After you install the database client files, alter the init_user_param.sh script installed with ArcGIS Server to reference the client files. You can access this script by browsing to the <ArcGIS Server installation directory>/arcgis/server/usr directory.

You must update the init_user_param.sh on every machine in the ArcGIS Server site.

Note:

If your user profile references the Oracle client and the client information differs between the user profile and init_user_param.sh, ArcGIS Server may experience problems when attempting to connect to the database. To alleviate connection issues, remove the reference information from your user profile and reference your database client libraries again using the following steps:

1. Ensure that the ArcGIS Server installation owner on each machine has at least read and execute permissions on the database client libraries.
2. Open the init_user_param.sh script in a text editor.
3. Remove the comment marks (#) from the lines beginning with export.

   If you installed the Oracle Administrator, Developer, or Runtime client, remove comment marks from all the Oracle lines beginning with export.

   #
   # For connection with Oracle Runtime or Administrator Client
   #
   export ORACLE_BASE=<Oracle_Installdir>/app
   export ORACLE_HOME=$ORACLE_BASE/<Oracle_release>/product/<Oracle_version>/<client_version>
   export ORACLE_SID=<set when applicable>
   export TNS_ADMIN=<set when applicable. e.g.$ORACLE_HOME/network/admin>
   export PATH=$ORACLE_HOME/bin:$PATH
   export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH

   If you are using the Oracle database Instant client libraries, you only need to uncomment and set the $LD_LIBRARY_PATH, for example:

   #
   # For connection with Oracle Instant Client
   #
   export LD_LIBRARY_PATH=<Location_to_instantclient_11_2>:$LD_LIBRARY_PATH

4. Set values for the export variables.
   • For Oracle Administrator, Developer, or Runtime clients, uncomment and set the following variables using information specific to your implementation:

     • ORACLE_BASE=<Oracle_Installdir>

       The <Oracle_Installdir> is the path to and name of the top-level directory where the Oracle client is installed.

     • ORACLE_HOME=$ORACLE_BASE/<Oracle_Release>/product/<Oracle_Version>/client_1

       This is the path to the Oracle client library files. Set ORACLE_HOME to the directory where these reside. By default, the directory name is client_1, but your installation may have a different directory name.

     • If you will be using an Oracle system ID (SID) to connect, set ORACLE_SID= to the Oracle system ID of your database. If you will be using an Easy Connect string to connect, comment out this line.
     • Set TNS_ADMIN= to the location of your Oracle client TNS administration files. If you will be using an Easy Connect string to connect, you do not need to set this value and must comment out this line.
   • For Oracle Instant clients, uncomment and set only the LD_LIBRARY_PATH variable, replacing <Location_to_instantclient> with the path to and directory name where the Oracle Instant client files are located.
   • If ArcGIS Server and Oracle are installed on the same server, uncomment and set the following variables:
     • ORACLE_BASE=<Oracle_Installdir>

       The <Oracle_Installdir> is the path to and name of the top-level directory where Oracle is installed.

     • ORACLE_HOME=$ORACLE_BASE/<Oracle_Release>/product/<Oracle_Version>/client_1

       This is the path to the Oracle library files. Set ORACLE_HOME to the directory where these reside. By default, the directory name is db_<n>, but your installation may have a different directory name.

     • If you will be using an Oracle system ID (SID) to connect, set ORACLE_SID= to the Oracle system ID of your database. If you will be using an Easy Connect string to connect, comment out this line.
     • Set TNS_ADMIN= to the location of your Oracle client TNS administration files. If you will be using an Easy Connect string to connect, you do not need to set this value and must comment out this line.
5. Save and close the script.
6. For the changes you made in the init_user_param.sh file to take effect, you must restart ArcGIS Server.

   To do this, run the stopserver.sh script, then run the startserver.sh script on each machine in the ArcGIS Server site.

   ./stopserver.sh

   ./startserver.sh

Create a database connection file

Create a database connection file using the Database Connection dialog box in ArcGIS Pro, as described above.

Alternatively, you can run the Create Database Connection tool in ArcGIS Pro or use Python to run the Create Database Connection command from an ArcGIS Server machine to create a database connection file (.sde) that connects to the database.

The following information is specific to creating a database connection file for use with ArcGIS Server:

• You must save the user information with the connection file.
• If you choose to use operating system authentication, use a domain account for the ArcGIS Server account and add the domain account to the Oracle database.

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:

Privilege	Reason
CREATE SESSION	Required to connect to the database.
CREATE TABLE	Selection sets cause a log file table to be created in the geodatabase. If a user does not have this privilege, log file tables will be created in the sde user's schema.
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, 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.

The database administrator must grant the first two privileges listed above. If the data is in a geodatabase, the data owner must grant the required privileges on the datasets. If the data is in a database, the data owner can grant privileges on datasets from ArcGIS or the database administrator can use database tools to grant the required privileges.

If you will be registering the geodatabase as a managed database for a stand-alone or federated ArcGIS Server site, the account with which you connect must have privileges to create data in the geodatabase.

See Privileges for geodatabases in Oracle or Privileges for using ArcGIS with an Oracle database for more information.

Register the database

To allow ArcGIS Server sites to access the data, use the database connection file you created to add a registered data store in ArcGIS Pro or add a data store item in the portal.