Consultor Eletrônico

Status: Unverified

FACT(s) (Environment):

HP-UX 11.0 32-bit

FACT(s) (Environment):

Progress 9.1B

SYMPTOM(s):

Performance of database degrades after customized dump and load.

This is a 100GB database, composed of only one table

Customized dump and load process.

The scatter factor for the data area, as recorded by dbanalys, went from 1.0 after idxbuild to 3.1 in a few short days.

Rm Chain analysis prior to procopy of new database to position of old database shows a number of warnings:
[Warning] DBKEY <number > w/free space less than 75 found on RM chain. (3896)

Test queries run up to three times slower, if not by the index used to dump the database.

Adding new records, the recids assigned skip huge blocks of numbers and after xxx number of records entered, the recids are contiguous and the same occurs for each set of new records entered.

CHANGE:

Two databases, one the mirror of the other.
Split the mirror.
Old=production database
New=mirror of production database.
Dumped the .df file
Used 4GL code to dump the data from new database in ranges, dumping a number of segments concurrently.
Once the .df and data were dumped, the new db was deleted.
Prostrct create...created "new" database using the same structure description file (st)
Copied the empty into the newly created void database.
Loaded the df file.
Did a bulkload of the files, one segment at a time.
Ran idxbuild.

While the db were split, they place a replication trigger on the production database to record any records that were changed over the time it took to get this "new" database ready for use.

On the newly created database they ran "REPLAY"..4gl code to replay those records recorded by the replication trigger, overwriting the same records on the "new" database.
They did a procopy of this "new" database to the directory where the old database had been backed up and removed.

CAUSE:

Customized dump and load of the database.

FIX:

Recommend Consultant Services.