Oracle Plug-in
UsernameThe Oracle database is a powerful database for business applications. The OPC Router supports the native connection via the corresponding Oracle client drivers and TNS. You can find a detailed video on this topic under “Connection of 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 configuration. Select a name that is unique for you during connection configuration. |
Connection type
There are three different connection types available. Various properties can be configured depending on the connection type selected.
- 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 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. |
| TNS name | Name of the TNS configuration to be used. |
| Port | Port under which the Oracle database service can be reached. |
| Schema | The schema to be used |
warning
Only one cloud wallet can be configured. As soon as a Cloud Wallet is used, no other Oracle plug-in can be used
| Cloud Wallet | Wallet file that contains the access data of the database to which a connection is to be established. |
| Database | Database to which a connection is to be established |
| 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”) must 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 in at the Oracle database server |
| Password | Password for logging in at the Oracle database server |
“Advanced connection parameters” tab
| Command Time-out | Time in seconds that the router waits for the completion of an SQL command. It may be necessary to increase the value for long-lasting queries. Please note that the connection timeout must also be increased for connections in which long queries are being executed. |
| Connection Time-out | Time in seconds that a connection to the database may take. |
| Concurrent connections | Number of concurrent connections that the router may establish to the database. 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. Of course, this also depends on the size of the project. |
| Polling interval | Interval in seconds at which the database is polled. |
“Advanced” tab
| 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 | If this option is active, the values “1”, “y”, “t” are converted to true and “0”, “n”, “f” to false values. |
| Oracle append schema | If this option is active, the schema is added 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 in which the Oracle Client software was installed. |
| Include Oracle packages | If this option is active, stored procedures that are located in packages are also listed. |
Bracket behavior
- Put in quotation marks if dot is present: This mode is intended for backward compatibility. If a dot (.) is contained in an identifier, quotation marks are added. This is useful if you have database objects with dots in their names, such as
datenbank.schema."tabelle.name". - Never put in quotation marks: 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 special characters or spaces.
- Always use double 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 double quotes is 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 previous versions.
- Yes: The schema is always being 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 being added to the identifier. This can be useful if you are only working with one schema or if you want to have full control over the SQL statements generated by the plugin.
Oracle column data type source
- Auto: The data types are converted to the most appropriate data type when reading. This can simplify the transfer of data to another system.
- Data Reader: The data types are retained when reading and are not being converted. This setting is helpful if it is important to retain the exact data types.