Kbase P102231: prostrct create and prorest are slow
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/7/2006 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1x
OpenEdge 10.x
SYMPTOM(s):
prostrct create is slow
prorest is very slow
default startup.pf has been modified
Large -B set in default $DLC\startup.pf
CAUSE:
-B value being set in the $DLC\startup.pf is causing the issue.
Unless otherwise specified, prostrct and prorest will use the default startup.pf that is located in the Progress Installation $DLC directory. Although -B isn't required for use with prostrct create (Progress doesn't make use of the allocated blocks for that utility), if the -B has been specified in the pf, Progress will still try to allocate that amount of memory during the startup of the process. The executable (_dbutil) called by the prostrct and prorest scripts does not allocate the blocks as effectively as other Progress executables - it is, however, not intended for this function. Therefore, the default $DLC/startup.pf should not be modified.
FIX:
1. Ensure that the $DLC/startup.pf is unmodified and as at installation time, and specifically that it doesn't specify -B. prostrct create uses this file (unless -pf is set).
Progress does not advise making changes to the $DLC/startup.pf; it is a template file, one might say. If startup parameters are required to be set, then a copy of the default startup.pf should be made and then that copy should be modified and referenced using the -pf startup parameter.
2. A quick workaround would be to specify a pf file when running the prostrct create or prorest instead of the default,
e.g. prorest dbname dbname.bak -pf modified.pf