Create Oracle Connections
You can create a new connection, or connect to an existing connection from the Create New Connection window.
Tip: You can configure Toad Data Point to accept connection information from Toad for Oracle.
Client Connection or Direct Connection
You can connect to your database using a native Oracle database provider in Toad using one of the following methods:
|
Connection Method |
Advantages |
Disadvantages |
|---|---|---|
|
Client connection Client tab—Uses an installed Oracle Client or Oracle Instant Client to establish a connection to the database from Toad. |
Supports LDAP See Configure Oracle LDAP Support for more information about configuring the Oracle client to use LDAP. |
Requires an Oracle client Note: Toad supports Oracle clients and Oracle Instant clients using version 9i or later. |
|
Direct connection Direct Connect tab—Uses TCP/IP to connect directly to the database. |
Does not require an installed Oracle Client Recommended for connecting to Oracle 8i databases |
This method only supports common data types. Some advanced Oracle object types cannot be retrieved when connecting using this method. This method does not support LDAP. (To connect using LDAP, use the Client Connection method instead.) This method cannot be used in a cross-connection query. |
|
Note: Quest recommends using one of the methods described in this table to connect to Oracle rather than an ODBC driver. Because ODBC connectivity is generic, it is not full-featured and may not be as robust as the fully exploited native database provider. | ||
Data Types Supported
Toad supports both the 32-bit and the 64-bit versions of the Oracle Client. The following table identifies which Oracle data types are supported for each client type.
| Data Type | Supported Using 32-Bit Client |
Supported Using 64-Bit Client |
|---|---|---|
| CHAR |  |
|
| VARCHAR2 and VARCHAR | |
|
| NCHAR and NVARCHAR2 | |
|
| LONG | |
|
| NUMBER | |
|
| DATE | |
|
| TIMESTAMP | |
|
| BLOB | |
|
| CLOB | |
|
| NCLOB | |
|
| BFILE |  |
|
| RAW, LONG RAW | |
|
| ROWID | |
|
| XMLType 1, 2 | |
|
| SDO_GEOMETRY | |
|
| VARRAY | |
|
| Nested Table | |
|
| User-Defined | |
|
Table Notes:
- An XMLType that uses an XML schema is supported, but only when using Oracle Client 11.2 or later.
- XMLType data that is stored as binary XML is not supported.
Configure the Oracle Instant Client
The Oracle Instant client installs only those files needed to connect to your database using OCI. Because this client does not write to the registry (no ORACLE_HOMES) or add to the environmental path, you must manually set environment variables so the client can be used with Toad.
To configure the Oracle Instant Client to work with Toad
- Save the Oracle Instant Client files in any location on the computer where Toad is installed.
- On your Windows desktop, right-click My Computer and select Properties.
- Select the Advanced tab and click Environment Variables.
-
Click New under System Variables and complete the following:
Variable name Variable Value PATH <Path where Instant Client is installed>;%PATH%
For Example: C:\Program Files\OracleInstantClient;%PATH%
TNS_ADMIN <Path where tnsnames.ora file is installed>
- To use the Oracle Instant Client connection in a cross-connection query, you must also install an Oracle ODBC driver. (While the Oracle Client full install includes an ODBC driver, the Oracle Instant Client does not.)
Note: You cannot use an Oracle Direct Connection in a cross-connection query.
Create an Oracle Connection
To create an Oracle connection
-
Click
on the toolbar (ALT+F+N).
-
Select Oracle from the Group list box.
-
Review the following for additional information:
Login Tab Description Database name
Select the alias to use when connecting. This list displays aliases from LDAP, as well as any local tnsnames.ora file.
When you initially open the connection dialog, Toad retrieves the list of LDAP names from the LDAP server. Toad caches this list and displays it upon subsequent requests, within one Toad session. To refresh the list, click
.
Note: If you do not select a database, Toad uses the ORACLE_SID for the selected home. If an ORACLE_SID value does not exist and you do not specify a database, you cannot connect.
Password
Enter the password to use when connecting.
Tip: After connecting, you can set a master password to further secure your connection in Tools | Options| Environment | Security.
Connect as
Select whether to connect as either SYSDBA or SYSOPER if you have the appropriate permissions. Otherwise, use the default.
Schema
Select a schema if you frequently work in a different schema than the one associated with your user name. Explain plan table
(Optional) Specify the location of an existing explain plan table to use instead of Toad automatically creating one for you when you execute a statement. This is useful if you do not have necessary permissions to create explain plan tables or want to use an existing table.
Category
Select or create a category if you want to color code Editor tabs for a specific connection. This can help differentiate between development and production databases. You can also set an option to color code the Object Explorer pane and object editor windows (Create, Alter, Drop, etc.). Save password
Select this check box if you plan to use this connection in a scheduled Automation script.
Note: This option is disabled if Toad was installed with Prohibit saving passwords selected.
Oracle Client Tab
Description
Current home
Modify the Oracle home to use, if needed.
TNSNames Editor
Click this button to edit your local TNSNames file.
Tip: You can press CTRL+F to open the Find/Replace window to locate entries in the TNS Names Editor. Pressing F3 locates the next entry that matches your criteria.
SQLNET Editor
Click this button to edit SQLNET.ORA parameters. Before editing this file, you should create a backup copy. See SQLNET.ORA Profile Parameters in the Oracle documentation for more information. Direct Tab
Description
SID
Enter the ORACLE_SID value for the database. This value is specified in the registry under each installed home.
Advanced Tab Description ODBC driver
If an Oracle Client is installed, the default is the Oracle ODBC driver.
If an Oracle Client is not installed, the default is the Microsoft Access ODBC driver.
Tip: You can specify the ODBC driver to use for all connections for this database provider in Tools | Options | Database | Oracle.
-
Click Connect to connect immediately while saving the connection information. Optionally, click Save to save the connection without connecting.
Note: Go to Tools | Options | Database | Oracle to specify default options to use in Oracle connections.
Tip: Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help | About.
Create Oracle BI Connections
Toad allows you to connect to the presentation layer of an Oracle Business Intelligence Enterprise Edition (OBIEE) data source.
See also, About Oracle BI Enterprise Data Sources .
Note: This feature is available in the Toad Data Point Professional Edition only.
To create an Oracle Business Intelligence Enterprise connection
- Click
- Select Oracle BI Enterprise from the Group list.
-
Enter the connection information in the Create New Connection dialog. Review the following for additional information:
URL Enter the URL to the Oracle Business Intelligence Enterprise data source to which you want to connect.
Note: You must include the port number in the URL as in the following examples:
format—http://<server path>:<port>/analytics/saw.dll
example—http://server01.mycompany.com:80/analytics/saw.dll
Password Enter the password to use when connecting.
Tip: After connecting, you can set a master password to further secure your connection in Tools | Options| Environment | Security.
Row Limit Select a row limit to enforce for query results.
default = 500,000
Category (Optional) Select an existing category or create a new one. Note: In NoSQL and Business Intelligence connections, Toad automatically saves the password in the connections.xml file as obfuscated text, as well as in Toad. To add additional password security, use Toad's Master Password feature.
-
Click Connect to connect immediately while saving the connection information. Optionally, click Save to save the connection without connecting.
- Upon creating an initial connection, Toad automatically maps the data source objects. This process runs in the background, and until it is finished, you may experience a delay when attempting to access these objects.
Important Information about Oracle BI Connections
You must incorporate the port into the OBIEE database connection URL in the following format:
http://<server name>:<port>/analytics/saw.dll
An example URL is http://server01.mycompany.com:80/analytics/saw.dll
Tips:
- Read about the considerations and limitations of working with OBIEE in Toad in About Oracle BI Enterprise Data Sources .
- Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help | About.
- You can specify a proxy server to use for Business Intelligence and NoSQL connections at Tools | Options | Database | Data Services.
Create PostgreSQL ODBC Connections
Toad Data Point allows you to easily create a connection to a PostgreSQL database using ODBC connectivity. You can connect with or without using a data source name (DSN).
Download and install the necessary ODBC driver to use for your PostgreSQL connection prior to creating the new connection in Toad.
Prerequisites
To create a successful ODBC connection, the architecture (bitness) of the driver in the specified DSN must match the architecture (bitness) of Toad. For example, 64-bit Toad requires an applicable 64-bit driver and 32-bit Toad requires an applicable 32-bit driver.
To create a PostgreSQL ODBC connection
- Click
- Select PostgreSQL from the Group list box.
- Use data source name
- To create the connection using a data source, select this option to display data source names.
- To create the connection without using a data source, clear this check box to display driver names. Select a driver and enter a server name, port number, and a database. Or select a driver and enter a ConnectionString.
- To create a data source to use in this connection, click
in the Data Source Name field. Then click Add.
- Select a PostgreSQL ODBC driver from the list, and click Finish.
- Specify the configuration properties required for the database in the Windows driver setup dialog. Save your settings when finished.
-
Specify the remaining connection properties in the Create New Connection dialog. Review the following for additional information:
Note: Specify a user that has been granted SELECT privilege in pg_catalog schema.
General Data source name
Select the driver or data source name you added in the previous steps.
User
Enter the user name to use when connecting.
Password
Enter the password to use when connecting.
Tip: After connecting, you can set a master password to further secure your connection in Tools | Options| Environment | Security.
Database
Select a database or schema. Click
to create a temporary connection and display available databases/schemas in the drop-down list.
Information
Data Source Name
Displays the selected driver or data source name.
Driver
Displays the ODBC driver associated with the data source.
Advanced Default Table Column Specify default options to use when creating a new table.
Column type—Select the default data type to use when creating a table.
Column length—For the selected column type, enter a default column length to use.
Advanced Options Block Cursor Size—Specify the number of rows to return in a single fetch of data from the result set.
Disable multi-threading—Multi-threading is disabled by default. Enable multi-threading only if supported by the driver. Multi-threading can improve performance, but can also result in unpredictable behavior if not supported by the driver.
Default: Selected
Category (Optional) Select an existing category or create a new one. -
Click Connect to connect immediately while saving the connection information. Optionally, click Save to save the connection without connecting.
Tip: Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help | About.
Considerations and Limitations for PostgreSQL ODBC Connections
| Consideration/Limitation | Details |
|---|---|
| User must have pg_catalog privilege |
To use a PostgreSQL ODBC connection in Toad, the connecting user must have the SELECT privilege in the pg_catalog schema. This privilege is required as it enables viewing PostgreSQL objects in the Object Explorer, as well as other features and functionality in Toad. If you attempt to connect using a user account that does not have the SELECT privilege in the pg_catalog schema, you will encounter the following error message: "User's privileges are insufficient to connect using Toad." |
Tips for Working with ODBC Connections
| Tip | Description |
|---|---|
| Filter DSN by bitness |
To filter Data Source Names displayed in the New Connection dialog by the bitness of Toad, go to Tools | Options | Database | ODBC. |
| Cache object metadata |
To cache object metadata for ODBC connections and retain it between sessions, go to Tools | Options | Database | ODBC and select to enable disk caching. Cached object metadata is retained until manually refreshed. |
| Refresh object metadata |
To refresh object metadata for all ODBC connections, in the Object Explorer right-click an object and select Refresh All. Right-click an object and select Refresh Schema to refresh only objects in that schema. |
ODBC Features
| Feature | Description |
|---|---|
| Bypass schema/instance selection in SQL Editor |
For ODBC connections, in the SQL Editor you can bypass selecting a schema/instance and specify this information through the script instead. This is useful if your script executes SQL against multiple schemas. To use this method, select I will set schema/instance in the script from the schema/instance drop-down list in the SQL Editor window. Then specify the schema/instance through your script. Note: When this option is selected, some code completion features, object actions, and object information tool tips are unavailable for this SQL Editor window. |
Create Salesforce Connections
Toad allows you to connect directly to Salesforce.com, one of the business intelligence data sources supported by Toad. Toad supports authentication using either a Salesforce security token or single sign-on with your corporate credentials.
See also, About Salesforce.com Data Sources.
Note: This feature is available in the Toad Data Point Professional Edition only.
To create a Salesforce connection
- Click
- Select Salesforce from the Group list. The Create New Connection dialog opens.
- To create a Salesforce connection using your Salesforce email login, select the Credentials tab.
-
Enter the connection information. Review the following for additional information:
URL Enter the Salesforce.com URL to which you want to connect.
Note: An example is https://login.salesforce.com.
Username Enter your email login.
Note: You must have a Salesforce email login to create this type of connection to Salesforce.com from Toad.
Password Enter the password to use when connecting.
Tip: After connecting, you can set a master password to further secure your connection in Tools | Options| Environment | Security.
Security token Enter your Security Token provided by Salesforce.
Note: You must have a Salesforce security token to create this type of Salesforce.com connection from Toad. See Important Notes about Salesforce Connections for more information.
Category (Optional) Select an existing category or create a new one.
- After entering the connection information, click Connect to connect immediately while saving the connection information. Optionally, click Save to save the connection without connecting.
-
-
To create a Salesforce connection using your corporate credentials (single sign-on), select the Corporate Credentials tab.
-
Enter your company's custom Salesforce URL. An example is https://company.my.salesforce.com or http://salesforce.servername.
Note: If you authenticate and request login to Salesforce through your company's server (e.g., http://salesforce.servername), you may need to contact your IT department to obtain the full URL to enter in this step.
-
If the Salesforce log-in page displays, enter your corporate credentials (user name and password) and click Log in to Salesforce.
Note: The Salesforce log-in page does not display when authenticating through your company's server.
- The Salesforce consent page displays. Click Allow to allow Toad access to your Salesforce data.
-
-
Upon creating an initial connection, Toad automatically maps the data source objects. This process runs in the background, and until it is finished, you may experience a delay when attempting to access these objects.
Note: In NoSQL and Business Intelligence connections, Toad automatically saves the password in the connections.xml file as obfuscated text, as well as in Toad. To add additional password security, use Toad's Master Password feature.
Manual Single Sign-On
Use the manual single sign on method when you want to create a Salesforce connection using your corporate credentials but you are having problems accessing Salesforce from Toad, for example, if Toad does not have access to the Internet.
Create a Salesforce.com connection - manual single sign-on
- In the Create New Connection dialog, select the Manual Single Sign On tab.
- Log-in to your Salesforce.com account using your browser. After you log-in, copy the full URL from the browser's address bar and paste it into the text box under Step 1 in the Manual Single Sign On tab.
- A URL appears in the text box under Step 2. Copy this URL and then paste it into the address bar in your browser.
- The Salesforce consent page displays. Click Allow.
- A page displays containing the authorization code. Copy the code and paste it into the text box under Step 3. Then click Connect.
Reauthorizing a Connection (If Using Corporate Credentials)
If you encounter an error message when attempting to connect to Salesforce using your corporate credentials connection, Toad's authorization (access) to Salesforce may be lost. Use the following procedure to re-establish authorization for the connection.
To Reauthorize
- In the Navigation Manager, disconnect from the connection. You must disconnect before you can re-authorize.
- After disconnecting, right-click the connection and select Properties.
- In the Connection Properties dialog, click Reauthorize in the Corporate Credentials tab.
-
If the Salesforce log-in page displays, re-enter your corporate credentials.
Note: The Salesforce log-in page does not display when authenticating through your company's server.
Important Notes about Salesforce Connections
- If you connect to Salesforce using a proxy, you must define the proxy server in Toad.
- A Security Token is required to log on to Salesforce.com from Toad, using your Salesforce email login.
- For information about how to generate a new security token, see the Salesforce documentation at https://login.salesforce.com/help/doc/en/user_security_token.htm.
- You may need to have your IP address included in your organization's list of trusted IP addresses. For more information, see the Salesforce documentation at http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_concepts_security.htm.
Tips:
- For more information about working with Salesforce.com in Toad, see About Salesforce.com Data Sources.
- Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help | About.
- You can specify a proxy server to use for Business Intelligence and NoSQL connections at Tools | Options | Database | Data Services.