configdadb - Configure the Data Area for Database Access

configdadb [OPTIONS] [-s|m|b] [-fg] [-p productline] dataarea

configdadb configures a data area for database access, including building the database configuration files and database schemas as needed.

If you use Oracle, when you run the configdadb utility in non-auto mode, you will need to specify values for the following:


Value	Description
The database server configuration to use for the data area.	Specify a named database access configuration or specify `None`. If you specify `None`, you will then need to specify the additional values below. For more information about defining a database access configuration, see the configdatabase - Configure Named Database Access. Note: This prompt or field only appears if you have already defined at least one database access configuration through the `configdatabase` utility.
The database to use for this data area.	Choose the number from the list presented by the interview that represents the database you will use, or if in GUI mode, select the database from the drop-down list.
The Oracle protocol for the server connection.	`TCP` or `TNS`. You can select `TNS` if you have a TNS file configured. Otherwise, you will need to specify the host and port of the database server.
The full path for the Oracle home directory.	If your Oracle protocol is `TNS`, specify this path.
The TNS name for the Oracle server.	If your Oracle protocol is `TNS`, specify the TNS name.
The host name of the remote Oracle database.	If your Oracle protocol is `TCP`, specify the host for the database.
The port number of the remote Oracle database	If your Oracle protocol is `TCP`, specify the port for the database.
The SID (Service_Name) for the Oracle database.	If your Oracle protocol is `TCP`, specify the SID for the database. You can find this by looking in the tnsnames.ora file or by running the `lsnrctl status` command, and then finding the service for the database that the listener is listening for.
Do you want to use unicode support?
The name of the table space to use when creating tables.	This must already exist and be defined as locally managed.
The name of the table space to use when creating indexes.	This must already exist and be defined as locally managed.
The name of the table space to use for large objects.	This must already exist and be defined as locally managed.
The Oracle user ID to use when connecting to the database.	This existing user will become the owner of the tables created during for the data area. The user name is used to keep the data for this data set separate from any other data stored in the database. All tables will be created with this name as the table owner. You must use a unique user name for each data area.
The password for the Oracle user ID.

The following files are created or updated by configdadb:

$LARUNDIR/dataarea/db.cfg
$LASRCDIR/dict/dataarea.xml


Program Option	Description
`-f` or `--force`	Force a rebuild of the database configuration files, even if they exist.
`-g` or `--gui`	Prompt for interactive data area specifications through an input form.
`-e` or `--env=envName`	(Internal use only) The environment data area to associate with.
`-s` or `--s3`	Create entries for Infor Lawson System Foundation connection information in the `dataarea.xml` file (generally used only by installer programs).
`-m` or `--m3`	Create entries for Lawson M3 Foundation connection information in the `dataarea.xml` file (generally used only by installer programs).
`-b`	Create entries for both Infor Lawson System Foundation and Lawson M3 Foundation connection information in the `dataarea.xml` file (generally used only by installer programs).
`-p productline` or `--pl=prodlineName`	The product line to base the data area on. This defaults to the data area name. This option is only needed if you have more than one data area within a product line.
`--auto`	Auto configuration. In this case, `configdadb` runs without prompting for any additional data. If there is missing or incorrect information, the program errors out.
`db=Name`	The name of an existing database configuration to use as a configuration template. You create database configurations through the `configdatabase` utility.
`--panel=FileName`	Internal use only.
`--view`	(Internal use only) To use with an existing database.
`NAME=VALUE`	(Internal use only) To override a parameter value (such as "SCHEMA") from the database configuration with the specified value.
`dataarea`	The data area to create.