gareth.roberts
New Member
Hello,
As part of an upgrade to a new version of our product we have to apply a DF (with various new table, fields, indexes) to a database. We add the indexes inactive and then run an index rebuild to rebuild just the inactive indexes.
We are in the process of testing this process for one of our biggest clients whose database is just over 200GB. We applied the df with no problem and then ran the index rebuild, this takes just under 2 hours and reports that it is complete. However the index rebuild utility has not return back to the command prompt and the _dbutil process still has over 20 GB of memory committed to it. This is gradually reducing over time and we assume once this has all gone, and presumably committed to disk, the process will truly finish. This has been like this for nearly 5 hours now and has reduced to 12 GB.
The index rebuild was run with the following command:
proutil <dbname> -C idexbuild -TB 31 -TM 32 -SG 64 -B 20000
Is this expected behavior?
Is there anything we can do to speed this up?
OS is Windows Server 2008 R2 and OpenEdge version is 10.2B07 64 bit.
Thanks
Gareth
As part of an upgrade to a new version of our product we have to apply a DF (with various new table, fields, indexes) to a database. We add the indexes inactive and then run an index rebuild to rebuild just the inactive indexes.
We are in the process of testing this process for one of our biggest clients whose database is just over 200GB. We applied the df with no problem and then ran the index rebuild, this takes just under 2 hours and reports that it is complete. However the index rebuild utility has not return back to the command prompt and the _dbutil process still has over 20 GB of memory committed to it. This is gradually reducing over time and we assume once this has all gone, and presumably committed to disk, the process will truly finish. This has been like this for nearly 5 hours now and has reduced to 12 GB.
The index rebuild was run with the following command:
proutil <dbname> -C idexbuild -TB 31 -TM 32 -SG 64 -B 20000
Is this expected behavior?
Is there anything we can do to speed this up?
OS is Windows Server 2008 R2 and OpenEdge version is 10.2B07 64 bit.
Thanks
Gareth