This dialog is used to configure a connection to an Oracle database. You can choose whether to analyze data in-database or to import it into your analysis. Note that you need to install a driver on your computer to get access to the Oracle connector. See the system requirements at http://support.spotfire.com/sr_spotfire_dataconnectors.asp to find the correct driver. You can also view Getting Started with Connectors to learn more about getting access to connectors in Spotfire.
To add a new Oracle connection to the library:
Select Tools > Manage Data Connections.
Click Add New > Data Connection and select Oracle.
To add a new Oracle connection to an analysis:
Select File > Add Data Tables.
Click Add.
Select Connection To > Oracle.
Option |
Description |
Server |
The name of the server where your data is located. To include a port number, add it directly after the server name preceded by colon. Example with port number: |
Connect
using |
|
SID
|
Select this option to specify an Oracle System Identifier (SID) to use when connecting to the database. SID is used to uniquely identify a particular database on a system. |
Service
name |
Select this option to specify a service name to use when connecting to the database. The service name is the TNS alias that you give when you remotely connect to your database. |
Authentication
method |
The authentication method to use when logging into the database. Choose from Windows authentication and Oracle authentication. Windows authentication When using Windows authentication, e.g., Kerberos, the access token of the currently logged in user will be used. Users that have been given the appropriate access rights to the Oracle database will be able to connect and read data. Domain credentials are not stored in the analysis file. Oracle authentication With database authentication the authentication is done using a database user. Database credentials can be stored, unencrypted, as part of the analysis file, using a setting in the Data Source Settings dialog. If credentials are found in the analysis file they will be used to automatically authenticate against the database. If no credentials or credentials profiles are found in the analysis file all who open the file will be prompted for database credentials. Note that there will be no prompting for credentials if the credentials embedded in the analysis file fail. |
Username |
The username you wish to use when logging into the Oracle database. |
Password |
The password for the specified username. |
Advanced
Option |
Description |
HA events |
If you are connecting to an Oracle RAC database, select this option to enable the ODP.NET connection pool to remove connections from the pool if an RAC service, service member or node goes down. Note: This option will only have effect if you are connecting to an Oracle RAC database. |
Load balancing |
If you are connecting to an Oracle RAC database, select this option to enable the ODP.NET connection pool to balance work requests across RAC instances. Note: This option will only have effect if you are connecting to an Oracle RAC database. |
Statement cache purge |
Select this option to empty the statement cache for your connection when you close the connection in Spotfire. The statement cache is used to store copies of the SQL statements (queries) that are sent from Spotfire to Oracle, in the Oracle database memory. |
Statement cache size |
Specify the maximum number of statements that can be stored in the statement cache. The default value is 0. |
Proxy user ID |
If you want to use a proxy user, specify the proxy user name. |
Proxy password |
If you are using a Proxy user ID, specify the password for that proxy user. |
Connection lifetime (s) |
In some situations, you might want certain connections to be removed from the ODP.NET connection pool. With the connection lifetime option, you can specify an amount of time in seconds. When you close the connection in Spotfire, if the connection had been open for longer than the lifetime value, it will be removed from the ODP.NET connection pool. The default value is 0, which means that connection lifetime is not used. |
Connection timeout (s) |
Specify the maximum number of seconds allowed for a connection to the database to be established. The default value is 15. Note: If you set the connection timeout to zero, it will be interpreted as no timeout. That is, there will be no upper limit for trying to connect. This is generally not recommended. |
Command timeout (s) |
Specify the maximum number of seconds allowed for a command to be executed. The default value is 120. Note: If you set the command timeout to zero, it will be interpreted as no timeout. That is, there will be no upper limit for trying to execute the command. This is generally not recommended. |