dbutility Command-Line Options

This section explains the command-line options you can enter with dbutility commands, with all lowercase options first in alphabetical order and all uppercase options following. Use the following syntax to include the command-line options:

dbutility [options] command

where [options] begin with the forward slash (/) or hyphen (-) and are followed by a letter and a possible argument, as listed in the following table. If you use a UNIX Client, all options must start with a hyphen (-). Note the following guidelines for using command-line options:

  • All options are case-sensitive.
  • The options can be used in any order.
  • When you enter any of these command-line parameters, do not type the [brackets]. The [brackets] indicate that the command-line parameter is optional.
  • Following the option letter, you can enter option arguments with or without a space. For example, -tl and -t l are equivalent.
  • If an argument is blank (an empty character string), you can omit it if the next entry on the command line is another option (for example, -D). Otherwise, you must enter the blank argument as " " (quotation marks) with both leading and trailing spaces.


Assume you want to override the environment variable for the relational database name and enter a blank instead (which is the same as the using the default database name). To do this, you could enter either of the following:

dbutility -U usera -P secret -D "" configure

dbutility -U usera -D -P secret configure

(Both of these examples override the environment variable DBDATABASE.) For a complete reference of command-line options paired with their equivalent environment variables and configuration file parameters, see Reference Tables.

This option

Does this


Displays short help, which includes dbutility command syntax and parameters but not options.


Toggles the setting of the display_active_only parameter.


Toggles the setting of the defer_fixup_phase parameter during a clone command.


When used with any dbutility command, this option enables full tracing. This is the same as entering -t 8191 (or -t 0x1FFF).

If you are not sure whether to use the -d option or the -t option, you may want to use the -d option. It is often better to have too much tracing information than not enough.

-f filename

Specifies an input configuration file other than the default filename when used with an import command. If filename doesn't start with a backslash (\) on Windows or a forward slash (/) on UNIX, it is assumed to be in the config subdirectory of the working directory. Conversely, if filename starts with the appropriate slash, it is taken to a full file specification.


Displays long help, which includes dbutility command options, syntax, and parameters.


Used with a reload command to preserve the stateinfo for data sets whose format levels and item counts remain unchanged.


Includes a 5-digit millisecond timer in all trace messages. The millisecond timer is appended to the timestamp in the trace file. This option does not affect log file output.


Used with the runscript command to override your entry for user_script_dir so that you can run any script that is not located in that directory.


Overrides shutdown periods, including those initiated by the stop_time and end_stop_time values in the DATASOURCES client control table for the data source entry when the controlled_execution configuration file parameter is enabled.


Forces the parameter use_dbconfig to be treated as False when running a redefine command. The use_dbconfig parameter is internal and not directly editable. However, this parameter is set to True in the following situations:

  • When a data source is created using the Client Configurator
  • When a define command creates the data source and no users scripts are encountered
  • When you run the dbscriptfixup program

    In all other cases, including after an upgrade using the migrate program, the use_dbconfig parameter is set to False.

    Its purpose is to ensure that the Client Configurator isn't run with improperly setup client control tables. This would cause all changes that were made via user scripts to be lost.


Loads relational database tables that cannot be loaded via the bulk loader utility (SQL*Loader for Oracle and bcp for Microsoft SQL Server).

The -s option inhibits the use of the bulk loader utility during the data extraction phase of cloning. The DATABridge Client loads the table using SQL statements instead.

Caution: Use this option only when certain tables will not load via the bulk loader utility. Do not use it under normal circumstances. The -s option slows the cloning process considerably.

-t mask

Enables trace options designated by mask. See Enabling a Trace.

If you are unsure whether to use the -d option or the t- option, you may want to use the -d option. It is often better to have too much tracing information than not enough.


Creates override conditions that dbutility would otherwise interpret as a possible user error. These situations include the following:

  • Creating a second set of client control tables within one relational database. In this case, the second set of tables must be owned by a different user ID.
  • Starting over by dropping and creating the client control tables, even though this removes all of the state information associated with the user tables.
  • Attempting to define a data source that already exists.

    With the dbutility dropall command, use this option to drop DATABridge Client tables that still contain data.


Provides information in addition to what is provided by the DATABridge Client log file and is mostly used as a debugging tool. Because this option can generate a substantial number of messages, it is treated the same as a trace (generated messages do not appear in the log file).

The -v option does the following:

  • Enables tracing with -t1. If tracing is already specified with the -t option, the -v option sets the 1 bit in the mask to enable the tracing of log messages (that is, a verbose form of the log file in the trace file).
  • Writes a message to the trace file after every update received from DBServer or DBEnterprise.
  • Causes DATABridge Client scripts and user scripts to display the number of rows affected by INSERT, UPDATE, and DELETE SQL statements.


Toggles the setting of the use_dbwait parameter.


Makes the clone command clone all active data sets except for those specified at the command line.


Forces the Client to reclone data sets with a mode of 11 and 12.


Caution: This option is for troubleshooting only in a test environment. Do not use it in a production environment.

Allows dbutility to simulate a dbutility process or clone command without actually storing data. For troubleshooting purposes.

After the client control tables are loaded for the specified data source, the program sets a global flag that disables all SQL execution by the ODBC (Microsoft SQL Server) or OCI (Oracle) interface routines.

Using this option with statistics enabled (show_statistics and show_perf_stats both set to True) to determine the rate at which the DATABridge Engine and the DATABridge Client can process data without including any of the additional delays caused by the relational database. If this rate is significantly slower than the rate you get when the -z option is set, you can conclude that the slowness is caused by the actual relational database, which might need to be tuned.


Prevents the Client from deleting the tables when cloning virtual data sets that have the DSOPT_Ignore_Dups option bit (value 32) set in the ds_options column of the DATASETS client control table. Instead, it drops their indexes and appends the new records to the tables.


Causes the display command to report only the second half of the DATASETS client control table to the trace.log file, then causes the program to quit. (In most cases, the information in the second half of the DATASETS client control table is the only information you actually need from that table.)


Toggles the inhibit_console parameter. On UNIX, this doesn't apply if you run dbutility as a background run.

-D databasename

(Oracle only) Specifies the relational database you are using.

-F afn

Makes the Client act as if a "QUIT AFTER afn" command had been executed. Applies only to process and clone commands. The range of values allowed are 1 through 9999.


Inhibits audit file removal WFLs from running on the host during a process command. This option is also implied during a clone command and when used with the ‑z option.


Forces the Client to start using a new log file.


Toggles the setting of the enable_optimized_sql parameter.

-O ODBCdatasource

Specifies an ODBC data source that connects to the Microsoft SQLServer and DB2 clients.

-P password

Defines the password for accessing the relational database.


Treats every data set as if its DS_Needs_Redefining status bit is set and allows the program to rebuild the control tables when you change a configuration parameter such as optimize_updates or read_null_records.


Forces the Client to start using a new trace file. See Log and Trace Files.

-U userid

Specifies the user ID defined in the relational database.


Used with the unload command, this option lets you specify the control table version you want. To create tables that you can use with an older Client version, use the value that corresponds to that version.

Values for the DATABridge Client are as follows:



Version 6.2



Version 6.1 SP3



Version 6.1



Version 6.0









Version 5.2 (base release)



Version 5.1


Uses Integrated Windows Authentication to connect to the SQL Server database.

-X password

Used to define a host password. The host password is required only when it is configured on the host in the DBServer control file.

Caution: The password is currently not encrypted in communications between the DATABridge Client and DATABridge Server.


Forces a process or clone command to drop and create the tables of all recloned data sets, regardless of the use of the deleted_record or expanded update_type columns.