configdatabase - Configure Named Database Access

configdatabase [--gui|--noui] [--copy=NAME] name [NAME=value ...]

configdatabase --drop name

configdatabase --print name

configdatabase --list

Use configdatabase to create named database access configurations. These are then available for the configdadb utility as templates to configure database access for data areas.

When you create a named database access configuration, the utility prompt you for the necessary information for a database access configuration and will validate your specifications.


Program Option	Description
`-g` or `--gui`	Prompt for interactive database access configuration specifications through an input form.
`-n` or `--noui`	Use `configdatabase` in non-interactive mode. In this mode, the utility will create a new database access configuration based on the last database access configuration that was created, using the new name you provide.
`--copy=NAME`	Create a new database access configuration by copying from the configuration identified through your value for `NAME`.
`name`	The name of the database access configuration.
`--drop name`	Delete the specified database access configuration.
`--print name`	Print the values for specified database access configuration.
`--list`	List all of the defined database access configurations.
`NAME=value ...`	Provide a value for a database parameter, where `NAME` is the name of the parameter and `value` is the value you want it to have. You can enter multiple parameter/value pairs.


Database Access Option	Description
Automatically create schemas for data areas?	Select `TRUE` or `FALSE`. If you select `TRUE`, you will later need to provide a prefix to use to build user names, a password to connect to as `sys`, and a password to use when creating users. If you select `FALSE`, you will later need to provide the Oracle user ID to use when connecting to the database and the password for that user.
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 prefix to use to build user names.	The user name is used to keep the data for a data area separate from any other data stored in the database. All tables will be created with this user as the table owner. To ensure a unique user name is used for each data area, a name is formed by concatenating this prefix, an underscore, and the data area name. The resulting user name cannot exceed 18 characters in length and must start with a letter. This field is only present if you selected `TRUE` when asked if you want to automatically create schemas.
The password to connect to as sys.	This field is only present if you selected `TRUE` when asked if you want to automatically create schemas.
The password to use when creating users.	This password to set for the Oracle user that is auto-created for each data area. This field is only present if you selected `TRUE` when asked if you want to automatically create schemas.
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. This field is only present if you selected `FALSE` when asked if you want to automatically create schemas.
The password for the Oracle user ID.	This field is only present if you selected `FALSE` when asked if you want to automatically create schemas.