...
- Availability on OpenVMS and HPUX platforms.
- Possibility of page access to index-organized tables of Oracle database (IOT- index-organized tables). ODBC drivers Oracle contain an error (tested for versions 9.02.00.00 up to 9.02.00.06), that causes an application crash on the page access to IOT and therefore the ODBC version of the DBManager does not provide page access if finds out that the table is IOT.
- Less leakage of system resources: ODBC drivers for Oracle (tested for versions 9.02.00.00 up to 9.02.00.06) leak 4 handles in a connect/disconnect cycle, OCI interface leak leaks only one :-) .. in any case, we recommend setting a number of prepared connections for the object of Database type larger enough in order to prevent frequent opening and closing of the connections.
- Possibility to enable the debug information on the status of the Oracle cluster (see the parameter /DBCY).
Various runtime categories of the dbmanager.exe process:
- RTM.DBMANAGER.UPSERT - On the PostgreSQL platform when inserting data with the DB(S)_INSUPD action, UPSERT (INSERT ... ON CONFLICT (...) DO UPDATE ) is used. This syntax is supported by PostgreSQL since version 9.5.
Different runtime categories of the dbmanager_ora.exe process:
- RTM.DBMANAGER.STRICT_CHECK - If there is a column of text type in the table and this column is numeric in D2000, an error in converting to a number may occur during reading (ORA_01722: invalid number). If this runtime category is active, a strict check of column types is performed, and if such a column is detected, DbManager will refuse to work with the table (and the log will contain error messages).
- RTM.DBMANAGER.NO_COUNT_OVER - During page access (PG_CONNECT action and a browser), by default, the number of records is determined within the data-reading SQL query ( COUNT(*) OVER () ). In some cases, this reading can be slower than running an explicit query (SELECT COUNT(*) FROM <table>). We noticed a specific case on Oracle 19.21 and a table with more than 2.6 million rows (at an SGA size of 12GB). If this runtime category is active, the number of rows will be determined using an explicit query before the data is read.
| Info | ||
|---|---|---|
| ||
...