Kbase P160754: Binary dump and load operations take longer in version 10.2A01+
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/3/2010 |
|
Status: Verified
SYMPTOM(s):
Binary dump and load operations take longer in version 10.2A01+
operation is sequential, each table dumped consecutively then loaded one after the next through a batch simple batch script
the time difference is consistently 1 second slower per dump or load operation
FACT(s) (Environment):
Windows
OpenEdge 10.2A01 Service Pack
OpenEdge 10.2A02 Service Pack
OpenEdge 10.2B
CAUSE:
Bug# OE00195014
CAUSE:
The extra time (about 1 second) is spent during database disconnection. This only affects client on Windows platforms. The 1 second pause, also affects any online utility not only binary dump.
FIX:
The performance difference is essentially +1 second PER binary dump or load operation. The time difference is therefore:
[Number of tables] x 1 second as each needs a 'logout' before proceeding to the next operation.
Workaround: 10.2A01, 10.2A02, 10.2A03
Backup the %DLC%\bin from the current 10.2A + SP install, then restore the OpenEdge 10.2A00 (FCS) backup (optionally created when a Service Pack is installed) to the environment before running the dump and load.
For OE 10.2B00, unless a 10.2A00 or 10.1B environment is available, there is currently no workaround. Consider excluding empty tables from the dump/load operation to minimise the impact.