Oracle Plug-in
The Oracle database is a powerful database for business applications. OPC Router supports native connection via the corresponding Oracle client drivers and TNS. A detailed video on this topic can be found under "Connecting Database Systems" in our tutorial stream.
The following properties can be configured in the Oracle plug-in:
"Connection Settings" tab
| Name | Name under which the Oracle database server appears in the connection project. Choose a name that is unique for you during connection project planning. |
Connection type
There are three different connection types available. Depending on the selected connection type, different properties can be configured.
- Hostname
- TNS
- Cloud Wallet
| Host/IP | Host name or IP address of the server. |
| Port | Port under which the Oracle database service can be reached. |
| Database | The database to connect to. Note: This property must be set for a successful connection test. |
| Schema | Here you can select the Oracle schema to be used. |
| Property | Description |
|---|---|
| TNS Name | Name of the TNS configuration to be used. |
| Port | Port at which the Oracle database service is accessible. |
| Schema | The schema to be used |
Only one cloud wallet can be configured. Once a cloud wallet is in use, no other Oracle plug-in can be used.
| Property | Description |
|---|---|
| Cloud Wallet | Wallet file in which the access data for the database to be connected to is stored. |
| Database | Database to be connected to |
| Property | Description |
|---|---|
| Windows Authentication | If this option is active, Windows authentication is used instead of the User and Password properties. Local user accounts, DCOM users, and Windows domain users (NT authentication) are supported. To use Windows authentication, the user under which the OPC Router service is started (by default, "System") have access rights to the database. To be able to configure, the user under which the configuration environment was started must have access rights to the database. |
| User | User name for logging on to the Oracle database server |
| Password | Password for logging on to the Oracle database server |
"Advanced Connection Parameters" tab
| Property | Description |
|---|---|
| Command Timeout | Time in seconds that the router waits for an SQL command to complete. For long-running queries, it may be necessary to increase this value. Please note that the connection timeout must also be increased for connections in which long queries are executed. |
| Connection Timeout | Time in seconds that a connection to the database may take. |
| Simultaneous Connections | Number of connections that the router may establish to the database in parallel. The more simultaneous connections are allowed, the faster the router is, but this can slow down the database. Ask your database administrator how many connections they allow the router to make. This depends, of course, on the size of the project. |
| Polling Interval | Interval in seconds at which the database is queried. |
"Advanced" tab
| Property | Description |
|---|---|
| Bracket behavior | This property determines when and how square brackets are used in your Oracle plugin. A detailed explanation of the individual options can be found here. |
| Convert Boolean values | When this option is enabled, the values "1," "y," and "t" are converted to true, and "0," "n," and "f" are converted to false. |
| Oracle append schema | When this option is enabled, the schema is appended to the identifier. A brief explanation can be found here. |
| Oracle column data type source | This property determines how the data types of the columns are to be handled. A more detailed explanation can be found here. |
| Oracle home | Directory where the Oracle client software was installed. |
| Include Oracle packages | If this option is enabled, stored procedures located in packages are also listed. |
Bracket behavior
- Enclose in quotes if period is present: This mode is intended for backward compatibility. If a period (.) is included in an identifier, quotation marks are added. This is useful if you have database objects with periods in their names, such as
database.schema."table.name". - Never enclose in quotes: In this mode, no double quotes are added, regardless of the identifier. This can be useful if you are sure that your identifiers do not contain any special characters or spaces.
- Always enclose in quotes: In this mode, double quotes are always added. This is useful if your identifiers may contain special characters, spaces, or reserved words.
Please note that in Oracle, quotes are used to escape identifiers that would otherwise be interpreted as reserved words. It also allows the use of special characters and spaces in identifiers.
Oracle append schema
- Legacy: Same behavior as in the previous version.
- YES: The schema is always added to the identifier. This is useful if you are working with multiple schemas in the same database and want to ensure that the correct tables and views are used.
- No: The schema is not added to the identifier. This can be useful if you are only working with one schema or if you want to have complete control over the SQL statements generated by the plugin.
Oracle column data type source
- Auto: Data types are converted to the most appropriate data types when read. This can simplify the transfer of data to another system.
- Data Reader: Data types are retained when read and are not converted. This setting is helpful when it is important to retain the exact data types.