What Are the Parameters in the Lawson Database Interface Configuration File?

The following topics describe the parameters in the Lawson db.cfg database interface configuration file:

Parameters that Specify Your Database Implementation

The parameters in the following table configure the database.


Parameter	Description
`[SECTION]`	A section name to group parameters. At least one entry is required; if your product line configuration includes multiple databases, you can have more than one entry. If you specify a value for dbname in %LASRCDIR%\dict\dataarea.xml, the section name should match the dbname. If you do not specify a value for dbname in dataarea.xml, the section name should be one of the following, depending on your database type. `COMMON` Any parameters placed in this section will apply to all database instances defined in the db.cfg file. `MSFDB` Indicates the database in this section is a Microsoft SQL Server database. `ORADB` Indicates the database in this section is an Oracle database. `UPGDB` (Deprecated) This parameter allows one additional database connection. You must specify the database type within this section using the DBTYPE parameter.
`DBSERVER`	`DBSERVER` is the name of the server where your database is installed (or the alias). Enter a value for the server you need access to. Note: Normally you use `DBSERVER` when your database is installed in a client/server configuration using more than one machine. It is recommended that you use `DBSERVER` instead of the Oracle TWO_TASK parameter.
`ORACLE_HOME`	The directory where the database is installed.
`DBTYPE`	Deprecated. Formerly used to indicate the type of database for this set of data. Normally this parameter was only used when the database section is designated `[UPGDB]`. This value would match the value of the dbtype parameter in the `dataarea.xml` file. You can change that value using the `changeda` command.
`PORT`	The port number for the database server.
`LOGINNAME`	This is the user name used when the database driver connects to the database. The default is `lawson`. The parameter is not required if SERVICENAME is specified.
`PASSWORD`	This is the password for `LOGINNAME`, which the database driver uses when it connects to the database. The default is `lawson`. The parameter is not required if SERVICENAME is specified.
`SERVICENAME`	This parameter specifies the name of the database service for this data area. If you do not enter a database service, the login procedure defaults to using the LOGINNAME and PASSWORD specified in this file.
`SCHEMA`	Deprecated. Do not use this parameter in the `db.cfg` file. This value is configured in the `dataarea.xml` file.

Parameters that Support Text Search

The parameters in the following table configure the Lawson database driver to use text indexing and search features provided by the database.

If you do not set any values, Oracle will set a default 30 minute interval for the synchronization of text indexes.


Parameter	Description
`CTXPARMS`	For Oracle, replaces the parameters clause of a CREATE INDEX statement for text indexes with the appropriate DDL string entered following this parameter. Use this parameter instead of TEXT_COMMIT, TEXT_NO_COMMIT, or TEXT_SYNC if you need control over DDL generation.
`TEXT_COMMIT`	For Oracle, `TRUE` means that the text index is updated when the database commitment occurs. If you need control over DDL generation, use the CTXPARMS parameter.
`TEXT_INTERVAL`	For Oracle, the number of minutes between text index repopulation. (This provides the easiest way to set the interval between text index repopulation.) The default is 30.
`TEXT_NO_COMMIT`	For Oracle, `TRUE` means that the text index will never be updated. In this case, the database administrator must perform the text index update. If you need control over DDL generation, use the CTXPARMS parameter.
`TEXT_SYNC`	For Oracle, specifies an interval upon which the text search index will be created. A recurring job will automatically be created. For example, this setting of could be added to specify a 30-minute interval for a recurring job that commits any text index changes: `TEXT_SYNC=every "SYSTIMESTAMP + INTERVAL ''30'' MINUTE"` If you need control over DDL generation, use the CTXPARMS parameter.
`PARALLEL`	For Oracle, specifies the number of processes to use for parallel processing of text index builds. It is recommend to set this value to `n-1`, where `n` is the number of processors you have on your machine.

Parameters that Configure Record Caching

Use the following parameters to enable record caching.


Parameter	Description
`ARRAYBUFSIZE`	Indicates the maximum number of rows to be fetched at a time from the database. The default is 10 rows. The setting for this variable in the database driver configuration file applies to all files in the data area.
`INSERTBUFSIZE`	Indicates the maximum number of rows to be buffered in the database driver before an array insert flushes data out to the database. This parameter must be set to a value greater than 1 to enable array inserts. Lawson recommends a setting of 10 for normal use. When you perform a dbcopy or database reorganization, particularly when a large amount of data has been inserted into the database, you may want to increase the size of this parameter. Lawson recommends increasing it to 50 in these cases. Return the parameter to your normal setting when the dbcopy or the database reorganization completes.

Parameters that Support Use of Database Vendor Features

The parameters in the following table configure the Lawson database driver to use features provided by your database.


Parameter	Description
`RESUMABLE`	Optional. Allows values of `TRUE` (on) or `FALSE` (off). Specifies whether the database suspends when a table space runs out of space, to wait for DBA intervention. This feature applies only to Landmark programs (such as the database reorganization utility) execution.
`RESUMABLE_TIMEOUT`	Optional. Requires `RESUMABLE` set to `TRUE`. Specify how long, in seconds, the database waits for DBA intervention.
`SHOW_PLAN`	Optional. Invoke the database SQL explain plan.