Generic driver resources


baan_sql_cacherows / BAAN_SQL_CACHEROWS
Driver resource	`baan_sql_cacherows`
Environment variable	`BAAN_SQL_CACHE_ROWS`
Client/Server resource	Set for both client and server
Type	Integer
Default	71
Description	Does not apply to Baan IV and Baan 5.0 application sessions. This variable influences the number of records that the query processor internally caches for sorting, aggregation functions, or prepared sets. If you exceed this limit, temporary files are generated. For optimal performance of the internally used hash functions, specify a prime number.


baan_sql_stmt_cache_size / BAAN_SQL_STMT_CACHE_SIZE
Driver resource	`baan_sql_stmt_cache_size`
Environment variable	`BAAN_SQL_STMT_CACHE_SIZE`
Client/Server resource	Set for client only
Type	Integer
Default	330
Description	Does not apply to Baan IV and Baan 5.0 application sessions. This resource sets the number of inactive queries that must be retained for reuse.


baan_sql_trace / BAAN_SQL_TRACE
Driver resource	`baan_sql_trace`
Environment variable	`BAAN_SQL_TRACE`
Client/Server resource	Set for client only
Type	Integer (Octal)
Default	0
Description	Does not apply to Baan IV and Baan 5.0 application sessions. This variable is introduced to view the SQL query information being handled in client and server. If you set this variable, debug information is printed by the client to the log file (client) or `dbs.log` file (server). The information contains various categories you can enable separately, but most categories are not relevant for the audience of this document. The relevant values of the `baan_sql_trace` variable and the descriptions of these values are: 0002000: Major query interface logging 0004000: Detailed query interface logging


bdb_debug / BDB_DEBUG
Driver resource	`bdb_debug`
Environment variable	`BDB_DEBUG`
Client/Server resource	Set for client only
Type	Integer (octal)
Default	0
Description	This variable allows generating debugging information about the communication between the client and the database driver. If you set this variable, the client prints debugging information to standard error (`stderr`). You can specify these categories of debugging information: 00001: server types 00002: database actions 00004: delayed lock actions 00010: reference information 00100: permission information To define multiple categories, you can add the octal values. To determine if a given category must be logged, the value is compared bitwise.


bdb_driver / BDB_DRIVER
Driver resource	`bdb_driver`
Environment variable	`BDB_DRIVER`
Client/Server resource	Set for client only
Type	String
Default	None
Description	With this variable you can set a database specification, usually found in the file tabledef6.2. If you set this variable, all the tables are accessed using the database driver specified, and tabledef6.2 is read. You must specify the driver specified in the file $BSE/lib/ipc_info.


bdb_max_server_schedule / BDB_MAX_SERVER_SCHEDULE
Driver resource	`bdb_max_server_schedule`
Environment variable	`BDB_MAX_SERVER_SCHEDULE`
Client/Server resource	Set for client only
Type	Integer
Default	3
Description	This variable defines the mechanism for terminating idle database drivers by the application virtual machine. If the database driver has no more open sessions, the application virtual machine can terminate the driver. You close an idle database driver after several schedule ticks. A schedule tick is generated whenever you end an LN session. At this point, all idle database drivers have a schedule counter incremented. When the value of the schedule counter reaches the value of `bdb_max_server_schedule`, the database driver ends.


bdb_max_sessions / BDB_MAX_SESSIONS
Driver resource	`bdb_max_sessions`
Environment variable	`BDB_MAX_SESSIONS`
Client/Server resource	Set for server only
Type	Integer
Default	0 (unlimited)
Description	This variable defines the number of sessions per driver. If any driver has reached this threshold, a new driver starts that handles new sessions.


bdb_max_session_schedule / BDB_MAX_SESSION_SCHEDULE
Driver resource	`bdb_max_session_schedule`
Environment variable	`BDB_MAX_SESSION_SCHEDULE`
Client/Server resource	Set for server only
Type	Integer
Default	3
Description	This variable defines the mechanism for closing idle sessions in the driver. If the client process has no more references, cursors or queries, to the session, the client can close the client process. The client closes an idle session after several schedule ticks. A schedule tick is generated whenever an LN session is ended. At this point, all idle sessions have a schedule counter incremented. If the value of the schedule counter reaches the value of `bdb_max_session_schedule`, the session closes. The default for `bdb_max_session_schedule` is three. If you set `bdb_max_session_schedule` to 1, this results in fewer connections from the driver to the RDBMS. This is because whenever an LN session ends, the corresponding RDBMS session (logon) closes (logoff).


bdb_use_row_version
Driver resource	`bdb_use_row_version`
Environment variable	-
Client/Server resource	Set for client only
Type	Integer
Default	0
Description	If this resource is set to 1, every table that is created is extended with an extra column named `rcd_vers`. The value in this column identifies a row version and is updated by every update or delete action. The column is used to optimize the delayed locking approach, also known as optimistic locking. The value is used to verify that the row was not modified since the delayed lock was placed. Note: Changing this resource means that you cannot use the existing tables anymore. A possible, though potentially time consuming, solution is to export all data, change the resource value, and then import all data again.


dbsinit / DBSINIT
Driver resource	`dbsinit`
Environment variable	`DBSINIT`
Client/Server resource	Set for server only
Type	Integer (octal)
Default	1
Description	With this variable you can set flags to specify the optimizations to be used. At this time, legal values are 0, not set, or 1. Other values are reserved and must not be used. To define multiple categories, add the octal values. To determine if a given category must be logged, the value is compared bitwise. This parameter is deprecated and removed in a future release.


dbslog / DBSLOG
Driver resource	`dbslog`
Environment variable	`DBSLOG`
Client/Server resource	Set for server only
Type	Integer (octal)
Default	0
Description	This variable provides detailed debugging information about the online processing of the driver. The information is logged in the file dbs.log in the driver’s current directory. You can specify these debugging categories: 0000001: Data dictionary information on tables in the driver 0000002: Query info (SQL Level 1) 0000004: Query plan info (SQL Level 2) 0000010: Row action information 0000020: Table action information 0000040: Transaction action information 0000100: DBMS input/output data (SQL Level 2) 0000200: Administration file info (SQL drivers) 0000400: DBMS SQL statements 0001000: General debug statements 0002000: Query processing info (for tt_sql_trace info) 0010000: Log Connections and Cursors 0004000: Data buffering info (communication) 0100000: Lock retries logged (includes session name) 0200000: Logs successful locks and longest lock duration in a transaction To define multiple categories, you can add the octal values. To determine if a given category must be logged, the value is compared bitwise.


DBSLOG_LOCK_PROF
Driver resource	—
Environment variable	`DBSLOG_LOCK_PROF`
Client/Server resource	Set for server only
Type	Floating point number
Default	0
Description	Specifies the minimum duration of a lock that must be logged. Any locks of shorter duration are not logged. This variable specifies the minimum number of seconds, to a precision of milliseconds, that must elapse before a lock is logged. Lock time is calculated as the time from when the first record in a transaction is locked to the time of the commit or abort. This time is the longest time a record remains locked during a transaction. Note that you must set the appropriate `dbslog` categories.


dbslog_name / DBSLOG_NAME
Driver resource	`dbslog_name`
Environment variable	`DBSLOG_NAME`
Client/Server resource	Set for server only
Type	String
Default	`dbs.log`
Description	Allows specifying a file name where DBS logging information must be written. If a file already exists with the same name, the file is used for logging. If the file is locked during write operations, multiple servers can use the same log file.


enable_refmsg / ENABLE_REFMSG
Driver resource	`enable_refmsg`
Environment variable	`ENABLE_REFMSG`
Client/Server resource	Set for server only
Type	Boolean
Default	0 (disabled)
Description	There are two valid values for this variable: 0 and 1. When set to 0, no log messages are generated. When set to 1, log messages are generated in the database driver log file. For example, when an update of a delete action was denied because of existing references.


hint_idx_weight_equal / HINT_IDX_WEIGHT_EQUAL
Driver resource	`hint_idx_weight_equal`
Environment variable	`HINT_IDX_WEIGHT_EQUAL`
Client/Server resource	Set for server only
Type	Integer
Default	1
Description	This variable controls the index hint generation. For information on the influence of this variable on the index hint generation, see Database Driver Configuration and Tuning.


hint_idx_weight_factor / HINT_IDX_WEIGHT_FACTOR
Driver resource	`hint_idx_weight_factor`
Environment variable	`HINT_IDX_WEIGHT_FACTOR`
Client/Server resource	Set for server only
Type	Floating point number
Default	1.0
Range	0.0 … 1.0
Description	This variable controls index-hint generation. For information on the influence of this variable on the index-hint generation, see Database Driver Configuration and Tuning.


hint_idx_weight_range / HINT_IDX_WEIGHT_RANGE
Driver resource	`hint_idx_weight_range`
Environment variable	`HINT_IDX_WEIGHT_RANGE`
Client/Server resource	Set for server only
Type	Integer
Default	1
Description	This variable controls the index-hint generation. For information on the influence of this variable on the index-hint generation, see Database Driver Configuration and Tuning.


rds_full / RDS_FULL
Driver resource	`rds_full`
Environment variable	`RDS_FULL`
Client/Server resource	Set for both client and server
Type	Integer
Default	5
Description	This variable defines the maximum number of rows transferred between the LN application virtual machine and the driver as one block. Multiple blocks, and thus network round trips, are transferred if more rows are requested. You must set this variable to the same value for the client and server. The `sql.set.rds.full()` function or the “buffer <n> rows query overrule this default setting.


max_sql_input_binds / MAX_SQL_INPUT_BINDS
Driver resource	`max_sql_input_binds`
Environment variable	`MAX_SQL_INPUT_BINDS`
Client/Server resource	Set for server
Type	Integer
Default	512
Description	This resource sets the maximum number of the input binds that a query can have. Complex permission schemes can get too many additional clauses in their queries that they require enlarged bind buffers.


mle_join_type / MLE_JOIN_TYPE
Driver resource	`mle_join_type`
Environment variable	`MLE_JOIN_TYPE`
Client/Server resource	Set for server only
Type	Integer
Default	0 (INNER)
Description	This variable determines the type of join that is used between the data table and the corresponding shadow table that contains the translations. This is in case of a Multi Language Enabled (MLE) environment. The default join type (INNER) is recommended for normal circumstances. The database does not always generate an optimal execution plan. This can be the case when 5 data languages or more are used. To rectify this you can use a LEFT join type between the tables. This resource is implemented for MLE tables for all databases; it must be applied after extensive testing. When upgrading to a new database version, the use of this resource must be validated again. These values are supported: 0: INNER (default) 1: LEFT


query_comments/QUERY_COMMENTS
Driver resource	`query_comments`
Environment variable	`QUERY_COMMENTS`
Client/Server resource	Set for server only
Type	Integer
Default	0
Description	This variable allows enabling tracing queries in the database server. Enabling this resource results in inserting comments for some types of statements, for example queries. The comments include additional information about the database driver its process ID, the LN user name and the LN session name. Note: Enabling this resource severely impacts performance as it affects the query plan cache of the database server. Enabling this setting is for diagnostic purposes only.


shm_max_dd_cache_size / SHM_MAX_DD_CACHE_SIZE
Driver resource	`shm_max_dd_cache_size`
Environment variable	`SHM_MAX_DD_CACHE_SIZE`
Client/Server resource	Set for server only
Type	Integer
Default	12582912 (12Mb)
Description	This variable defines the maximum number of bytes that is used to cache database driver data dictionaries in the shared memory cache. If you exceed this limit, no further information are cached. A value of `0` is interpreted as unlimited. See `use_shm_info`.


ssts_set_rows / SSTS_SET_ROWS
Driver resource	`ssts_set_rows`
Environment variable	`SSTS_SET_ROWS`
Client/Server resource	Set for client only
Type	Integer
Default	3
Description	This variable defines the number of rows to be read ahead for a fetch request from the client. The default is three rows, that means that for one fetch request, three rows are read. For the next two fetch requests, rows are taken from the client row buffer or fetched from the database without re-executing the query.


table_load_array_size / TABLE_LOAD_ARRAY_SIZE
Driver resource	`table_load_array_size`
Environment variable	`TABLE_LOAD_ARRAY_SIZE`
Client/Server resource	Set for server only
Type	Integer
Default	100
Description	This variable defines the number of rows that are inserted using array interfacing when using the `bdbpost` or `bdbreconfig` utility.


tt_sql_trace / TT_SQL_TRACE
Driver resource	`tt_sql_trace`
Environment variable	`TT_SQL_TRACE`
Client/Server resource	Set for both client and server
Type	Integer (octal)
Default	0
Description	Applies to Baan IV and Baan 5.0 application sessions. For newer application versions, it is replaced by `baan_sql_trace`. This variable is introduced to view the Infor SQL query information being handled in client and server. If you set this variable, debug information is printed by the client to the display. The server only prints information if the `dbslog` variable allows it. The information contains various categories you can enable separately, such as evaluation trees, SQL statements, bind variables, timings, and communication debugging. The possible values of the `TT_SQL_TRACE` variable and the descriptions are: 000040 (c): Show queries with their QID 000200 (c): Show query execution times 002000 (c): Show calls of internal SQL functions 004000 (c+s): Show query execution tree 010000 (s): Show query evaluation plan 020000 (s): Show `FullTableScan` 040000 (c+s): Show qp tokens


use_shm_info / USE_SHM_INFO
Driver resource	`use_shm_info`
Environment variable	`USE_SHM_INFO`
Client/Server resource	Set for both client and server
Type	Boolean
Default	1 (enabled)
Description	You can use this variable to enable or disable the use of shared memory to each of the database driver data dictionaries. Two values are valid for this variable: `0` and `1`. If set to `0`, shared memory is disabled. If set to `1`, shared memory is enabled.


USR_DBC_RES
Driver resource	—
Environment variable	`USR_DBC_RES`
Client/Server resource	Set for client only
Type	String
Default	None
Description	This variable contains the file specification of an alternative resource file for the client. The file specification is based on the `BSE` directory and is in double quotes. When set, any resources in the alternative resource file override the same client resources set in `db_resource`.


USR_DBS_RES
Driver resource	—
Environment variable	`USR_DBS_RES`
Client/Server resource	Set for server only
Type	String
Default	None
Description	This variable contains the file specification of an alternative resource file for the client. The file specification is based on the `BSE` directory and is within double quotes. When set, any resources in the alternative resource file override the same server resources set in `db_resource`.