Kbase P70063: conv89 running for over an hour and has to be killed
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
FACT(s) (Environment):
Windows 2000
Progress 8.3D
Progress 9.1D
SYMPTOM(s):
conv89 running for over an hour
lg file shows that conv89 process hanging during conversion of physical schema
Begin Conversion of Physical Schema. (6578)
Dump and load works ok.
CAUSE:
v8 database being used as an AS/400 schemaholder but additional tables and data had been added.
FIX:
Rethink the organization of your database and your strategy for implementing the schemaholder/dataserver -
1. The schemaholder shouldn't contain additional data/tables. The schemaholder is there to enable the connection to the AS/400 database itself. The schemaholder should be created using the relevant dataserver tools, and adding tables any other way could corrupt it as a schemaholder. This could have been what has happened here, and thus why the conv89 was failing.
2. If the resulting database is intended for use as a schemaholder, the schema holder shouldn't be converted by conv89, even if it doesn't contain additional data/tables. It should be generated using the relevant dataserver utilities for the version.
3. A dump and load isn't the correct way either if the v9 database is also intended for use as a schemaholder. There should be no requirement to dump and load, as a schemaholder shouldn't be containing data.