| |
The eloqdb program implements the Eloquence database server. Depending
on OS platform, it may be available as 32-bit eloqdb32 or 64-bit eloqdb64
executable (or both).
The eloqdb server process may be started from the command line to
override selected options, but is typically controlled by a platform
specific init script on HP-UX and Linux (or run as Windows service)
to also allow integrating with system boot and shutdown.
usage: eloqdb [options]
options:
-help = show usage (this list)
-c name = configuration file
-d = debug mode
-l name = log file name (or console/syslog/default)
-f = run in foreground
-s name = service name (tcp/ip transport)
-F facility = syslog facility (USER/DAEMON/LOCAL0..LOCAL7)
-I ident = syslog identifier
-p pid_file = location of pid file (default is none)
The options are:
- -help
- The -help option displays a brief help text.
- -c cfg
- The -c option specifies the eloqdb server configuration file name.
If not specified, the default configuration file name depends on OS
platform and Eloquence version.
- -d flags
- The -d option specifies debug flags and may be used to override the
LogFlags setting in the eloqdb.cfg configuration file.
- -l logfile
- The -l option may be used to specify a log file, overriding the
LogFile setting in the eloqdb.cfg configuration file. The
log files "console" and "syslog" are special and result in log
output to stderr and syslog, respectively.
- -f
- The -f option causes eloqdb to run as foreground process. By default,
eloqdb detaches from the terminal and runs as a background process.
- -s service
- The -s option specifies the service name or TCP port to listen for.
It may override the Service setting in eloqdb.cfg and defaults
to eloqdb.
- -F facility
- The -F option allows to specify a syslog facility, overriding the
SysFacility setting in the eloqdb.cfg configuration file.
- -I ident
- The -I option allows to specify a syslog identifier, overriding the
SysIdent setting in the eloqdb.cfg configuration file.
- -p pidfile
- The -p option is used to create a PID file.
This option is primarily intended for use by the start/stop script to
manage eloqdb instances.
Before starting an eloqdb server process, a database server configuration
file (typically eloqdb.cfg) as well as DATA and LOG volume files must be
available.
Running multiple independent eloqdb server instances is possible by using
separate configuration (and volume) files and by configuring those instances
to use individual TCP service names or port numbers.
The example below starts an eloqdb foreground process for troubleshooting,
using a custom configuration file and directing custom level log messages
to the terminal:
$ eloqdb -c /tmp/eloqdb.cfg -d "*1E2" -l console -s 8888 -f
D1: Eloquence data base server started
D1: Eloquence data base server initializing
D0: Server patch level PE82-1312160
D1: [0] /tmp/db-01.vol
D1: [1] /tmp/log-1.vol
C1: Setting up buffer cache: 8192 buffers
L1: volume recovery: state of committed transactions is OK
L1: volume recovery: state of volume is OK
T1: Number of CPU cores in processor set is 2
D1: Communication buffer size = 1327104
D1: Communication buffer shmid = 11698194
D0: Eloquence database server active
Please note that the above example is very unusual. The typical use case would be
starting (and stopping) the eloqdb server with the platform specific HP-UX or Linux
init script (or via Windows service), as well as configuring a dedicated LogFile
in the eloqdb.cfg settings.
eloqdb.cfg configuration file
dbvolcreate utility,
dbvolextend utility,
dbctl utility.
|
|
