action.skip

Usage Errors

Usage error messages appear onscreen and in the log file in response to incorrect syntax or missing parameters when you enter dbutility commands. If tracing is enabled, messages are also captured in the trace file. These messages are prefixed by the timestamp hh:mm:ss (where hh is hours, mm is minutes, and ss is seconds)

Each usage message indicates the correct syntax and parameters, as follows:

USAGE ERROR: dbutility [options] clone <DataSource> <DataSets>
USAGE ERROR: dbutility [options] configure
USAGE ERROR: dbutility [options] createscripts <DataSource>
USAGE ERROR: dbutility [options] define <DataSource> <host> <port>
USAGE ERROR: dbutility [options] display <DataSource>
USAGE ERROR: dbutility [options] drop <DataSource>
USAGE ERROR: dbutility [options] dropall
USAGE ERROR: dbutility [options] export [<File>]
USAGE ERROR: dbutility [options] generate <DataSource>
USAGE ERROR: dbutility [options] import [<File>]
USAGE ERROR: dbutility [options] process <DataSource>
USAGE ERROR: dbutility [options] redefine <DataSource>
USAGE ERROR: dbutility [options] refresh <DataSource> <DataSet>
USAGE ERROR: dbutility [options] reload <DataSource> <File> [<DataSet>...]
USAGE ERROR: dbutility [options] reorganize <DataSource>
USAGE ERROR: dbutility [options] rowcounts <DataSource>
USAGE ERROR: dbutility [options] runscript <ScriptFile>
USAGE ERROR: dbutility [options] switchaudit <DataSource>
USAGE ERROR: dbutility [options] tcptest <DataSource> [host port]Len Count
USAGE ERROR: dbutility [options] unload <DataSource> <File>

For information on dbutility commands and options, see Appendix B in the Databridge Client Administrator's Guide.