|
For the initial index installation and build, DBINSTAL should
be run interactively. Manually define the MDK and ASK indexes
for each table and then run the Build command to populate
the index files. After this is complete, run OAHELPER to generate
an installation batch script. This script allows the indexes
to be re-installed and re-built in the future by simply executing
the script. This installation script can be easily modified
using any text editor.
 If
DBINSTAL prematurely stops on UNIX systems (for example, results
in a core dump), particularly on HP-UX systems, then run DBINSTAL
again for each indexing operation, or try reducing the memory
allocation through DBINSTAL's BUF=n option. This problem is
due to an anomaly in some versions of UNIX. A DISC work-around
is in progress.
Use the DBINSTAL Build BUF=n option to allocate an appropriate
amount of memory for DBINSTAL indexing operations.
Determining the optimal BUF=n size is best done by trial
and error on a subset of the database. Monitor the number
of sort segments required (displayed by DBINSTAL). The maximum
is 2048 segments. Vary the BUF=n size on the database subset,
and use the BUF=n value that provides a sort segment size
closest to 1024.
Use 8 Mbytes of BUF=n space for each Distributed Index (;DI)
processed. If a Build option of @9 is used, then the BUF=n
size should be set to 72 (8 * 9).
top
|
