Skip to main content
Version: 5.6

Oracle Plug-in

The Oracle database is a powerful database for business applications. The OPC Router supports native connectivity via the corresponding Oracle client drivers and TNS. You can find a detailed video on this topic under “Connecting Database Systems” in our Tutorial Stream.

The following properties can be configured in the Oracle plug-in:

“Connection Settings” tab

PropertyDescription
NameName under which the Oracle database server appears in the connection configuration. Choose a name that is unique to you during the connection configuration.

Connection Type

Three different connection types are available. Depending on the selected connection type, various properties can be configured.

PropertyDescription
Host/IPHostname or IP address of the server.
PortPort under which the Oracle database service is accessible.
DatabaseThe database to which you want to connect.
Note:

This property must be set for a successful connection test. | | Schema | The Oracle schema to be used can be selected here. |

PropertyDescription
Windows AuthenticationUses the Windows account of the OPC Router service instead of a username and password. This account must have the necessary access rights to the database. For project configuration, the rights of the user under which the configuration environment is running apply. Notes on configuring Windows user accounts for the OPC Router.
UserUsername for logging in to the Oracle database server
PasswordPassword for logging in to the Oracle database server

“Advanced Connection Parameters” tab

PropertyDescription
Command TimeoutTime 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 for connections executing long queries must also be increased.
Connection TimeoutTime in seconds that establishing a connection to the database is allowed to take.
Concurrent ConnectionsNumber of connections the router is allowed to establish to the database simultaneously. The more concurrent connections allowed, the faster the router will be, but this can slow down the database. Ask your database administrator how many connections they will allow the router to use. This naturally also depends on the size of the project.
Polling IntervalInterval in seconds at which the database is queried.

“Advanced” Tab

PropertyDescription
Bracket BehaviorThis 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 ValuesIf this option is enabled, the values “1”, “y”, “t” are converted to true, and “0”, “n”, “f” are converted to false.
Oracle append schemaIf this option is enabled, the schema is appended to the identifier. A brief explanation can be found here.
Oracle column data type sourceThis property determines how the data types of the columns should be handled. A more detailed explanation can be found here.
Oracle homeDirectory where the Oracle client software was installed.
Include Oracle packagesIf this option is enabled, stored procedures located in packages are also listed.

Bracket behavior

  • Enclose in quotes if a period is present: This mode is intended for backward compatibility. If a period (.) is included in an identifier, quotes 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 certain that your identifiers do not contain 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.
note

Please note that in Oracle, the use of quotes serves 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 appended 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 appended to the identifier. This can be useful if you are working with only one schema or if you want full 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 during reading. This can simplify the transfer of data to another system.
  • Data Reader: Data types are retained during reading and not converted. This setting is helpful when it is important to preserve the exact data types.