Eloquence B.07.10 Release Notes

Eloquence B.07.10 Release Notes - Database

Overview / Database Utility Changes

Database Utility Changes

This document lists the detailed user visible changes for each utility program.

Contents:

schema
dbutil
prschema
dbtables
dbexport
dbimport
dbstore
dbctl
dbvolcreate
dbvolextend
dbvolchange
dbvoldump
dbrecover
dbfsck

schema

The schema utility was modified to allow up to 8 index segments for application use. schema will fallback to the prevoious limit of 7 when used with older Eloquence versions.
The schema utility was modified to allow referencing an item in multiple index segments.
The syntax to define an index item was enhanced to allow specifying IITEM options and a start offset for index segments.
```
 iItemName [(options)] = ItemName[:[start.]length] [, ...] ;
```
The option EMPTY specifies to not create index entries for default item values.
The optional start and length for an index segment specify a starting position into an item and the size of the index segment. Start defaults to 1 (begin of the referenced item) and length defaults to the item size.
For example:
```
 MATCHCODE (EMPTY) = NAME:10;
 MATCHCODE (EMPTY) = NAME:2.5;
```
The schema processor has been enhanced to be more consistent on warning and error messages. Each message now specifies if a message is either an error or warning message. Warning messages are output with a message id that could be used with the -w option to selectively suppress the warning message.
The new -w command line option allows to suppress the output of specific warning messages.
```
 -w id[,..]
```
The -w option expects a list of warning message ids, separated by comma. The specified warning is then suppressed.
For example:
When unrefenced items are present in a schema definition, the schema processor did output the following warning message and list all unreferenced item names.
```
 *** Unreferenced items:
```
The message has been changed to:
```
 *** (WARNING #11) Unreferenced items:
```
When the command line option -w11 is specified, the message is suppressed.

dbutil

The dbutil utility was modified to allow users updating their own password without requiring additional privileges. This is not allowed for the user public and currently only works in scripting mode.
The CHANGE PASSWORD syntax was enhanced to make specifying the user name optional.
```
 CHANGE PASSWORD [FOR USER "user"] TO "password";
```
If the user is not specified, it defaults to the currently logged in user. For example:
```
 CHANGE PASSWORD TO "whatever";
```
This may be used to change (or remove) the password of the current user. As an alternative, the previous syntax may also be used but requires the specified user matches the current user.
The CREATE IITEM syntax was modified to allow specifying IITEM options and a start offset for index segments.
```
 CREATE IITEM 
  iItemName [(options)] = ItemName[:[start.]length] [, ...] ;
```
The option EMPTY specifies to not create index entries for default item values.
The start and length options for an item may specify a starting position into an item and the size of the index segment different from the item.
For example:
```
 CREATE IITEM match(EMPTY) = name:1.8;
```
The CHANGE IITEM syntax was changed to allow specifying IITEM options and a start offset for index segments:
```
 CHANGE IITEM iItemName
  [NAME NewiItemName]
  [TYPE ItemName[:[start.]length] [, ...]
  [FLAGS [iitem_options];
```
The FLAGS clause allows to set/reset iitem options. Currently, only the EMPTY option is valid. For example:
```
 CHANGE IITEM <iitem> FLAGS EMPTY;
```
This may be used to set the EMPTY option for the index.
```
 CHANGE IITEM <iitem> FLAGS;
```
This may be used to reset the options for the index.
The dbutil utility was modified to allow up to 8 index segments for application use.
The dbutil utility was modified to allow referencing an item in multiple index segments.

prschema

The prschema utility was modified to support iitem options and index segment offsets.
The option -B was added to allow enabling backwards compatible output for Eloquence versions before 7.0.
The prschema utility was modified to always output the primary path designator in TurboIMAGE compatible mode.
The prschema utility was modified to use a min. capacity value of 1. Previous versions could output a capacity value of zero for empty data sets.
The prschema utility was modified to add linebreaks in the iitem definition if the output could exceed 70 columns.

dbtables

The dbtables utility was modified to correct inconsistent item types in turboIMAGE compatibility mode.
The option -B was added to allow enabling backwards compatible output for Eloquence versions before 7.0.
The dbtables utility was modified to support index segment offsets.
The dbtables utility was modified to include current number of entries and highest allocated record number in the data set section.

dbexport

The dbexport utility was modified to support files sizes greater than 2 GB
A new -x command line option was added to dbexport that allows to specify a list of data sets to be excluded
When the -x option is not present the command line may specify a list of data sets to be processed. With the -x option present, this is understood as a list of data sets to be excluded.

dbimport

The dbimport utility was modified to support files sizes greater than 2 GB
The dbimport utility was modified to ignore underflow/overflow conversion failures for IEEE values
The dbimport utility was modified to output more detailed information on conversion errors
A new -x command line option was added to dbimport that allows to specify a list of data sets to be excluded
When the -x option is not present the command line may specify a list of data sets to be processed. With the -x option present, this is understood as a list of data sets to be excluded.
dbimport has been modified on HP-UX and Linux to handle CR/LF as a line terminator in a restructure file

dbstore

The dbstore utility is similar to the builtin dbstore function of the eloqdb6 server that is used with dbctl.
The dbstore utility allows to perform a dbstore operation when the server is not active or while the server is in on-line backup mode. If the eloqdb6 is in on-line backup mode the dbstore utility does not require exclusive access and may be performed while the database is in use.
```
  usage: dbstore [options] database {archive_file|-}
  options:
   -help   - show usage (this list)
   -u user - set user name
   -p pswd - set password
   -c cfg  - server configuration file
```
The dbstore utility supports the EQ_DBUSER and EQ_DBPASSWORD environment variables to specify the user and password.

dbctl

The dbctl utility was modified to return exit status 3 if the server indicates a command has failed. This simplifies the use of dbctl in scripts.

dbvolcreate

The dbvolcreate utility was modified to support configurable volume limits

dbvolextend

The dbvolextend utility was modified to support configurable volume limits
The new option -R may be used to recreate all missing LOG volumes. If the -v option is applied in addition, dbvolextend lists all LOG volumes it recreates.
For example:
```
 dbvolextend -v -R
```

dbvolchange

The dbvolchange utility was modified to support configurable volume limits

dbvoldump

The dbvoldump utility was enhanced to enable use while the eloqdb6 server process is active. Previous dbvoldump versions required exclusive access to the volume files and could not be used when the server process was active.

dbrecover

The dbrecover utility was enhanced to improve recovery performance. dbrecover uses temporary files to collect all changes which belong to a single transaction. This handling was optimized, resulting in a substantial performance increase on HP-UX (and to some lesser extent on other platforms).

dbfsck

The dbfsck utility was enhanced to perform additional consistency tests on pool and btree objects.
The dbfsck utility allows to specify node ids (node numbers) on the command line. If present pass 2 does only process the specified nodes.
The dbfsck utility can now be used in on-line read-only mode while the eloqdb6 process is active and in on-line backup mode. This allows to check the consistency of the database environment while the database is in use.