Infor Lawson Database Server Configuration File (ladb.cfg)

The Infor Lawson Database Sever Configuration file (ladb.cfg) contains the parameters used by the Database Server (ladb). These parameters define the maximum number of processes, files, and servers; the maximum size of files; and other values for parameters used by ladb.

ladb.cfg Parameter Reference

Database administrators can tune databases as they see fit. If the following parameters do not work for your database, you can adjust them to fit your needs. For good performance, you must constantly monitor current performance, make adjustments, and measure the results of any changes.

Keep a record of all changes you make to the default table parameters. If you find it useful to change the table or system parameters, inform your support staff.

ladb.cfg Parameters

Location: $LAWDIR/system/ladb.cfg

This table shows the variables that affect all database types.

For all of the parameters in this table except the REUSE parameter, you must stop and start the Infor Lawson System Foundation Environment for the changes to take effect.


Parameter	Infor Lawson setting	Description
`DICTS`	15	Maximum number of open dictionaries.
`FILES`	1500	Maximum number of open tables. This value is set assuming all Infor Lawson applications exist in this Environment. The pre-configured setting is for a larger than anticipated load. If only a small set of applications exists, this value may be set to a smaller number.
`UFILES`	450	Maximum number of tables for each user.
`USERS`	500	Maximum number of user processes. Adjust as needed to meet your needs. Note: The `USERS` value should be less than or equal to the value of `FOREIGN`, but it is recommended not to be less than half the value of `FOREIGN`.
`REUSE`	OFF	Specify how idle drivers may be used by `ladb` for new connections. Valid values for setting the `REUSE` flag are ON (TRUE or 1 may also be used) Allow any available idle connection to be reused by `ladb` when a new file is opened in the same data area. Note: `REUSE` can only be set to ON (TRUE/1) when `LAWSONUID` is set to 1. OFF (FALSE or 0 may also be used). Allow drivers to be reused only by the same user. Drivers are stopped when the user's connection to `ladb` is dropped. The REUSE flag can also be reset by the `dbadmin` utility while `ladb` is running. See Utilities for Managing ladb
`IDLETIME`	1	Number of minutes a database driver not referenced by any client program (IDLE) stays in the driver re-use pool. This parameter only applies if `REUSE` is set to ON Valid values for the `IDLETIME` flag are any integer value greater than zero.
`FOREIGN`	500	Maximum number of foreign database driver processes that ladb will create. Note: The FOREIGN value should be more than or equal to the value of `USERS`, but it is recommended not to be more than twice the value of `USERS`. See Adjusting the FOREIGN parameter.
`IFILES`	450	Number of tables for each interface.
`LAWSONUID`	0	Indicates whether to execute foreign servers as uid lawson instead of the calling process's uid (0 = no, 1 = yes).

Parameters That Configure Timed Statistics

This table shows the parameters you can use to enable timed statistics:


Parameter	Description
`TIMESTATS`	Optional. Enables the timed statistics feature. Allows values of `TRUE` (on) or `FALSE` (off).
`USERFILTER`	Optional. Requires that `TIMESTATS` is set to `TRUE`. The name of the user to monitor. If a user name has no program listed next to it, all programs being run by that user are monitored. Note: If you have modified the `USERFILTER` parameter with a prefix to identify a user as an operating system user (`USERFILTER=OSID:username`) or a web user (`USERFILTER=LOBS:username`), remove the prefix (`OSID:` or `LOBS:`) from this parameter.
`PROGRAMFILTER`	Optional. Requires that `TIMESTATS` is set to `TRUE`. The program to monitor when using timed statistics. If the program has no user entry preceding it, all instances of this program are monitored.
`DATAAREAFILTER`	Optional. Requires that `TIMESTATS` is set to `TRUE`. The data area to monitor when using timed statistics.
`TIMESTATSDIR`	Optional. Requires that `TIMESTATS` is set to `TRUE`. The directory for the output files from the timed statistics monitor. This must be an absolute path. The default for Oracle is `tmp`.

Adjusting the FOREIGN parameter

If the FOREIGN parameter value is too low, you may receive error messages saying that there are too many open drivers. This means that a client (such as IOS or lacobrts) has tried to open a database connection when the maximum number of drivers was already being used. You can use dbusers -p to view the client process ID and the command.

If you need to adjust the FOREIGN parameter value, use a value that provides database driver processes for the following:

For each job queue, the number of concurrent jobs for that queue.
The number of online lacobrts processes (from the latm.cfg RUNAPPS parameter).
The number of server processes (such as lajs, latm, and ladb) that open database connections.
The number of Infor Lawson Interface Desktop users who run with USE_LATM equal to FALSE
The command line utilities that open database connections (such as dbadmin and dbdef). (Add perhaps 10 to 20 to cover these.)
The number of connections needed by WebSphere (such as the Drill servlet and CGI calls), by the security server, and by any direct IOS connections.
Increase the number from all the above to as much as double the number because each client can or will connect to both GEN and the application data area.

Your database must also be configured with a high enough maximum connection count to support all of the Infor Lawson System Foundation database drivers plus any non-driver Infor Lawson System Foundation connections, such as those through sqldbcopy.

Keep in mind that the higher the value for the FOREIGN parameter, the more likely you are to overwhelm the database server. The goal is to have enough concurrent work to keep the database busy but not so much that it gets bogged down.

If you adjust this value, also adjust the MSGMNI kernel parameter. For more information, see your system documentation for the location of the kernel tuning parameters for your specific platform.