• FTS index support
• dbftswords utility
• ftsdump utility

• dbrepack utility
• dbpasswd utility
• Improved dbrepl utility
• Running replication as a background service
• prdbutil utility

• dbctl input mode
• dbctl replication status (slave server)
• dbctl replication monitor (slave server)
• dbctl volume

• Database server changes
• Miscellaneous Changes

Please refer to the FTS documentation for more information.

dbftswords utility

For more information please refer to the dbftswords documentation.

ftsdump utility

For more information please refer to the ftsdump documentation.

dbrepack utility

For more information please refer to the dbrepack documentation.

dbpasswd utility

Database password files may be used to authenticate with the database server (eg. by using the EQ_DBUSER environment variable). The dbpasswd utility adds the option to use protected password files and to impose additional restrictions on their use, such as expiration period, operating system user or host system. It provides a convenient and secure option to avoid using clear text passwords and to manage database passwords.

For more information please refer to the dbpasswd documentation.

dbrepl utility

For more information please refer to the dbrepl documentation.

Running replication as background service

For more information please refer to the dbrepl documentation.

prdbutil utility

For more information please refer to the prdbutil documentation.

dbctl input mode

The dbctl utility was enhanced to allow reading commands from stdin rather than the command line. This allows using dbctl interactively and simplifies submitting multiple dbctl commands with a single dbctl invocation.

If the -i option is present, any dbctl commands are read from stdin. The exit command (or an EOF condition) may be used to exit from dbctl. A leading "#" or "!" indicates a comment and is ignored.
Any commands read from stdin are echoed if stdin is not connected to a tty device (script use). The option -e may be used to disable the command echo.
In input mode, dbctl will exit if a command failure is encountered if stdin is not connected to a tty device (batch use).

The example below demonstrates the dbctl -i option in a script to obtain slave server replication status repeatedly every 10 seconds:

while :; do echo replication monitor; sleep 10; done | ./dbctl -ie 

For more information please refer to the dbctl documentation.

dbctl replication status (slave server)

For example:

$ dbctl replication status slave
Server is configured as SLAVE
Replication is active (activity 158 sec ago, lag 0 sec)
Last checkpoint is 45-1.1 (2012-09-05 16:57:32)
Forward-logging is enabled
Forward-log is '/data/test/S/fw/fw-44-1.log'

• The activity field ("last activity") indicates the last time when replication data was received by the slave server (difference in seconds from the current time).

• The lag field ("estimated replication delay") indicates the time difference between the master timestamp in the replication data and the time the data was received on the slave server (difference in seconds).

• The lag field is only present when replication is active (dbrepl connected to the slave server). The activity field is present when dbrepl was previously connected to the slave server.

• replication active - 0=dbrepl not connected, 1=dbrepl connected

• last activity (seconds) - numeric, number of seconds since last time when replication data was received by the slave server

• replication lag (seconds) - numeric, time difference (in seconds) between the master timestamp in the replication data and the time the data was received on the slave server. Zero if replication is not active.

• last master checkpoint (gen-seq.tag)

• last master checkpoint (timestamp) - numeric, timestamp in seconds since the epoch

This information returned is substantially identical to "dbctl replication status" and is intended to simplify replication status monitoring.

dbctl volume

dbctl volume limit

Returns the current volume size limit

dbctl volume limit MB

Allows specifying a new volume size limit (in MB)

dbctl volume list

List database volumes and properties

dbctl volume id

List the database volume properties for volume id

dbctl volume id max MB

Allows to change the size limit of the volume (in MB). This has the same effect as dbvolchange.

dbctl volume id ext MB

Allows to change the extension size of the volume (in MB). This has the same effect as dbvolchange.

Also note that any change to the global volume size limit does not persist a database server restart. It only applies to the running server process and does not automatically update the VolumeFileSizeLimit in the eloqdb server config file.

Database server changes

• Changed timestamp format in log files to YYYY-MM-DD HH:MM:SS

• The [server] LogTimeFmt config item may be used to specify the logfile timestamp format for the database server.

• The database server restructuring procedure was enhanced to use a more efficient bulk rebuild procedure when rebuilding indexes (FTS and btree). This makes temporary use of memory to accelerate btree indexing performance noticeably. The max. amount of temporary memory used for index rebuild may be configured with the [config] RestructMemLimit config item. The default memory limit is currently 100 MB. Larger values (such as 300 MB) may noticeably improve rebuild performance for large databases. Memory consumption during index rebuild may be reduced when using the 32-bit eloqdb32 and address space is tight (at the cost of rebuild performance).

• FTS indexes are rebuilt selectively. Only FTS data that is affected by a database structural change is rebuilt.

• Rebuilding a btree index should use less disk space in the forward log.

• The dbctl replication status and the HTTP config status page on a slave server have additional information on the last replication activity and the estimated replication lag. This is intended to simplify monitoring the replication status.

• The dbrepl utility may now be used with operator capabilities. Previous server versions required dba capabilities for replication.

Miscellaneous Changes

• The startup banner message was removed from most database utilities to simplify use in scripting. In previous versions the banner message was output to stderr when the utility was started. Affected utilities were changed so the utility name is present in any error messages.

• The dbinfo utility was enhanced to indicate a data set has encrypted or masked fields. In this case an indicator column is output in addition.

  The width of the "capacity" and "entries" columns was extended from 8 to 9 digits.

• The dbtables utility was enhanced to list FTS fields.

• The schema utility was enhanced to create new databases. This makes the use of dbcreate optional. dbcreate may still be used but has no effect if the database is already created.

• The database client library and utilities were enhanced to support encrypted password files.