Generic driver resources


baan_sql_cacherows / BAAN_SQL_CACHEROWS
Driver resource	baan_sql_cacherows
Environment variable	BAAN_SQL_CACHEROWS
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 are internally cached by the query processor for sorting, aggregation functions or prepared sets. When this limit is exceeded, temporary files are generated. A prime number must be specified for optimal performance of the internally used hash functions.


baan_sql_stmt_cache_size / BAAN_SQL_STMT_CACHE_SIZE7
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	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. When this variable is set, debug information is printed by the client to the log file (client). The information contains various categories you can enable separately, but most categories are not relevant. The available values of the `baan_sql_trace` variable and their descriptions are shown in these rows: 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 is used to generate debugging information about the communication between the client and the database driver. When set, the client prints debugging information to standard error (stderr). These categories of debugging information can be specified: 00001: server types 00002: database actions 00004: delayed lock actions 00010: reference information 00040: TSS info from %BSE%\lib\tss_mbstore 00100: permission information Multiple categories can be defined by adding the octal values. The value is compared bitwise to determine if a given category must be logged.


bdb_driver / BDB_DRIVER
Driver resource	bdb_driver
Environment variable	BDB_DRIVER
Client/Server resource	Set for client only
Type	String
Default	None
Description	This variable is used to set a database specification, usually found in the table definition file, tabledef6.1 Baan IV) or tabledef6.2 (Baan 5.0/LN. When this variable is set, all tables are accessed using the database driver specified and the table definition file is not read. The driver specified must be defined in the %BSE%\lib\ipc_info file.


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	Does not apply to Baan IV application sessions. This variable defines the mechanism for terminating idle database drivers by the application virtual machine. Whenever the database driver has no more open sessions, it can be terminated by the application virtual machine. Closing an idle database driver is done after several schedule ticks. A schedule tick is generated whenever an LN session is ended. 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 is terminated.


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 is started to handle any 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. Whenever the client process has no more references, such as cursors or queries, to the session, it can be closed by the client. Closing an idle session is done 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. When the value of the schedule counter reaches the value of `bdb_max_session_schedule`, the session is closed. The default for `bdb_max_session_schedule` is three. Setting `bdb_max_session_schedule` to one results in fewer connections from the driver to the RDBMS because whenever an LN session is ended; the corresponding RDBMS session (logon) is closed (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
Driver resource	dbsinit
Environment variable	—
Client/Server resource	Set for server only
Type	Integer (octal)
Default	01
Description	This variable allows flags to be set to specify the optimizations to be used. At this time, legal value is 001. Other values are reserved and must not be used. A flag of 001 specifies that an optimistic approach must be used when checking for references in parent tables. The referenced row in the parent table is not locked, improving the overall concurrency. If this flag is not set, optimistic reference checking is not used. See Optimistic and pessimistic reference checks. Pessimistic reference checking is not available for LN MSQL driver currently. Multiple categories can be defined by adding the octal values. The value is compared bitwise to determine if a given category must be logged. This parameter is deprecated and is removed in the next 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. These debugging categories can be specified: 0000001: Data Dictionary information of tables within the driver 0000004: Log execution plan 0000010: Row action information 0000020: Table action information 0000040: Transaction action information 0000100: DBMS input/output data 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 Multiple categories can be defined by adding the octal values. The value is compared bit wise to determine if a given category must be logged. Caution: Enabling logging of execution plan is limited to `SELECT SQL` statements. Other SQL statements such as `INSERT`, `UPDATE`, `DELETE` are excluded from plan retrieval. Retrieval of SQL Server execution plans requires the `SHOWPLAN` privilege. The database administrator must grant this privilege to the (database) user who wants to retrieve the plan to the `DBSLOG` file.


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 is the longest time a record remains locked during a transaction. Note that the appropriate dbslog categories must be set.


dbslog_name / DBSLOG_NAME
Driver resource	—
Environment variable	DBSLOG_NAME
Client/Server resource	Set for server only
Type	String
Default	dbs.log
Description	Represents a file name where DBS logging information is to be written. If there is already a file with the same name, it 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.


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. This variable must be set to the same value for both client and server. This setting is ignored when the virtual machine and the driver are running in the same process, combo mode, which is the default mode.


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	In case of a Multi Language Enabled (MLE) environment, this variable determines the type of join. The type of join that is used between the data table and the corresponding shadow table that contains the translations. 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.


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`. TT_SQL_TRACE is used to view the Infor SQL query information that is handled in the client and server. If this variable is set, debug information is printed by the client to the display. The server only prints information if this is permitted by the dbslog variable. The information contains various categories which you can enable separately. The categories are: Evaluation trees SQL statements Bind variables Timings Communication debugging The available 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


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.


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	Does not apply to Baan IV. This variable can be used to enable or disable the use of shared memory to each of the database driver DDs. There are two valid values for this variable: 0 and 1. When it is set to 0, shared memory is disabled. When it is 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 within 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`.