Variables in the database driver configuration file

These topics describe the variables in the ORACLE database driver configuration file:

Parameters that Specify Your Database Implementation

The parameters in this table configure the database.


Parameter	Description
`LAWGATENAME`	oradb11 / oradb12.exe The name of the database driver executable, used between the Lawson applications and the Oracle database.
`ORACLE_HOME`	The directory where Oracle is installed.
`ORACLE_SID`	Required, unless you use `DBSERVER`. Normally you use `ORACLE_SID` when your database is installed in a single machine configuration. The Oracle database name associated with the data area, used when the Oracle instance is located on the same machine as the Database Server (ladb). Use of this configuration enables use of shared memory in communication between the Oracle client and server. Oracle recommends that the name be no longer than four characters (for example, `laws` for Lawson Software products.) Note: If there is more than one data area installed for use with Oracle, each one requires its own Oracle login name and database driver configuration file. Note: Because you can use one, all, or none of these variables, it is important to note that the `CONNECT_STRING_BATCH`, `CONNECT_STRING_ONLINE`, and `CONNECT_STRING_XX` variables override any specifications previously assigned to the Lawson `DBSERVER` or `ORACLE_SID`, or to the Oracle `TWO_TASK` variables.
`DBSERVER`	Required, unless you use `ORACLE_SID`. `DBSERVER` should be set to the value of `ORACLE_SID` if Lawson and Oracle are on the same server. It should be set to the value of TWO_TASK if Lawson is on a separate server from Oracle. Note: Normally you use `DBSERVER` when your database is installed in a client/server configuration using more than one machine. Lawson recommends that you use `DBSERVER` instead of the Oracle `TWO_TASK` variable. Note: Because you can use one, all, or none of these variables, it is important to note that the `CONNECT_STRING_BATCH`, `CONNECT_STRING_ONLINE`, and `CONNECT_STRING_XX` variables override any specifications previously assigned to the Lawson `DBSERVER` or `ORACLE_SID`, or to the Oracle `TWO_TASK` variables.
`LOGINNAME`	Required. Enter this parameter when using the `USE_CFG_FILE` login procedure―. Do not use the `LOGINNAME` parameter for any other login procedure. This is the user name used when the database driver connects to the Oracle database. The default is `lawson`.
`PASSWORD`	Required. Enter this parameter when using the `USE_CFG_FILE` login procedure―. Do not use the `PASSWORD` parameter for any other login procedure. This is the password for `LOGINNAME`, which the database driver uses when it connects to Oracle. The default is `lawson`.
`SERVICENAME`	This parameter is required when Lawson Security and Resource Management are implemented to manage users and secure data. 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 `USE_CFG_FILE`. You can either specify a `LOGINNAME` and `PASSWORD` in the ORACLE file, or configure the system so that each individual user accesses the database with a unique user name.

Parameters that Support Use of Database Vendor Features

The parameters in this table configure the database driver (oradb11 / oradb12) to use features provided by Oracle.


Parameter	Description
`DEADLOCKTIME`	Optional. The number of times the database should attempt to lock a file before returning a deadlock.
`DROPCHECKPOINT`	Optional. Specify the commit size for columns that are dropped.
`DROPUNUSED`	Specify which Oracle columns can be dropped.
`FAILOVER`	Optional. Requires that `DBSERVER` or a Connect String parameter is specified in the ORACLE database driver configuration file. Use Oracle FAILOVER.
`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 programs such as dbreorg.
`RESUMABLE_TIMEOUT`	Optional. Requires `RESUMABLE` set to `TRUE`. Specify how long, in seconds, the database waits for DBA intervention.
`SHOW_PLAN`	Optional. Invoke the Oracle SQL explain plan.

Parameters that Configure Oracle Connect Strings

Environment variables allow you to utilize the Oracle connect string feature, a feature which lets you process different types of programs (for example, batch or online) through different connections to the same server.

Lawson provides three environment variables: CONNECT_STRING_BATCH, CONNECT_STRING_ONLINE, and CONNECT_STRING_XX. You can use one, all, or none of these variables.

The CONNECT_STRING variables let you send batch and online programs through different connections to the same server. The CONNECT_STRING_XX variable, where XX is a Lawson system code, allows users to connect to an Oracle instance based on the system code of the program. This can be used to perform application partitioning in an Oracle Parallel Server (OPS) environment.

Using the connect string feature can increase system performance. For example, you can use multithreaded server (MTS) connections for online programs while continuing to use the default dedicated server connections for batch programs.

Note: The CONNECT_STRING_BATCH, CONNECT_STRING_ONLINE, and

CONNECT_STRING_XX

variables override any specifications previously assigned to the Lawson DBSERVER or ORACLE_SID, or Oracle TWO_TASK variables.

The parameters shown in this table are used to configure Oracle connect strings.


Parameter	Description
`CONNECT_STRING_BATCH`	Optional. The Oracle connect string feature lets you process batch or online programs through different connections to the same server. Using the connect string feature can increase system performance. The database driver (oradb11 / oradb12) uses this variable to connect to Oracle when the name of the calling program is not four characters long.
`CONNECT_STRING_ONLINE`	Optional. The Oracle connect string feature lets you process batch or online programs through different connections to the same server. Using the connect string feature can increase system performance. The database driver (oradb11 / oradb12) uses this variable to connect to Oracle when the name of the calling program is four characters long.
`CONNECT_STRING_XX`	Optional. `XX` is a Lawson system code. This variable allows users to connect to an Oracle instance based on the system code of the program. This can be used to perform application partitioning in an Oracle Parallel Server (OPS) environment.

Parameters that Configure Record Caching

Use these parameters to enable record caching.


Parameter	Description
`ARRAYBUFSIZE`	Optional. Indicates the maximum number of rows to be fetched at a time from the database server. The default is 10 rows. The setting for this variable in the database driver configuration file applies to all files in the data area or data ID unless a variable specific to a program has been created. When a variable specific to a program has been created, it overrides the setting in the database driver configuration file.
`INSERTBUFSIZE`	Optional. Only applies to specific utilities (dbreorg, dbcopy, importdb -b, impcsv -b) and batch tokens. 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 no larger than 10 for normal use. However, when you perform a dbcopy or dbreorg, particularly when a large amount of data has been inserted into the database, 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 dbreorg completes. See Editing the Lawson Database Driver Configuration File Applications commit records to the database at different intervals. When a commit occurs, the insert buffer is flushed. Batch tokens typically commit every 50 records, `importdb` commits every 100, and dbcopy commits every 3000 records. Setting `INSERTBUFSIZE` higher than the commit interval will result in buffered inserts of the commit interval size. As with `ARRAYBUFSIZE`, you can set this variable to control a specific program. The program-specific setting overrides the setting in the database driver configuration file.