Kbase P138637: Calling mergeprop within a for loop causes AdminServer to not pick up all the changes made
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/12/2008 |
|
Status: Unverified
SYMPTOM(s):
Calling mergeprop within a for loop causes AdminServer to not pick up all the changes made
mergeprop is called within for loop to delete (e.g.) two databases, but when querying the AdminServer afterwards it still shows one of the two database (the second of the two that were supposed to be removed)
conmgr.properies files does reflect the changes correctly, both database entries are gone
AdminServer has to be restarted to pick up all the changes correctly
FACT(s) (Environment):
mergeprop is being called as follows:
for %a in (*test*.delta) do e:\Progress\oe101c\bin\mergeprop -action delete -type database -delta %a
Problem does not occur when mergeprop is executed normally and not from within a for loop
Windows
OpenEdge 10.1B
OpenEdge 10.1B03 Service Pack
CAUSE:
Bug# OE00178844
FIX:
Upgrade to 10.1C02, the problem does not occur in this release.
Alternatively do not use a for loop to call mergeprop, run it seperately for each change you wish to make.