Error during conversion

John,

I believe this email is for you and not me.

Thanks!

-----Original Message-----
From: Wayne Cox
To: vantage@yahoogroups.com
Cc: paul.pachniak@...
Sent: 3/22/02 9:37 PM
Subject: Re: [Vantage] Error during conversion.

At 05:25 AM 3/23/2002 +0000, you wrote:
>I received the following error about one hour into the 5.0 data
>conversion. **CRC for index 'MainKey' on table 'OPrice' does not
>match CRC in procedure 'cv/cvxa0036.p'. Try recompiling. (7968)

Just a guess... but the instructions say that after copying / restoring

the old DB, you need to start & stop the Progress server under 5.0 to
update some flag in the DB file. You're also supposed to rebuild all
the
indexes before the conversion. Both of those sound like they're similar

with your error message.

If you just installed the new rev of Progress per Epicor's instructions
and
haven't done any tuning, then your DB is grossly mis-configured
performance
wise. At a minimum you should edit Progress\Startup.PF and add a line
to
increase the -B parameter. -B 50000 is a good start, or use something
bigger is you're familiar with the settings. This can cut the schema
updates and data conversions form hours to minutes. Once you're up and
running, get the Progress Explorer working and tune per the Epicor
document
that's available.

-Wayne Cox





Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/links

Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
I received the following error about one hour into the 5.0 data
conversion. **CRC for index 'MainKey' on table 'OPrice' does not
match CRC in procedure 'cv/cvxa0036.p'. Try recompiling. (7968)
followed by an OK button, which when pressed stops the conversion.

If anyone has gotten this same error I would appreciate a fix as I
would like to complete the installation before the end of the weekend.

Thanks!
At 05:25 AM 3/23/2002 +0000, you wrote:
>I received the following error about one hour into the 5.0 data
>conversion. **CRC for index 'MainKey' on table 'OPrice' does not
>match CRC in procedure 'cv/cvxa0036.p'. Try recompiling. (7968)

Just a guess... but the instructions say that after copying / restoring
the old DB, you need to start & stop the Progress server under 5.0 to
update some flag in the DB file. You're also supposed to rebuild all the
indexes before the conversion. Both of those sound like they're similar
with your error message.

If you just installed the new rev of Progress per Epicor's instructions and
haven't done any tuning, then your DB is grossly mis-configured performance
wise. At a minimum you should edit Progress\Startup.PF and add a line to
increase the -B parameter. -B 50000 is a good start, or use something
bigger is you're familiar with the settings. This can cut the schema
updates and data conversions form hours to minutes. Once you're up and
running, get the Progress Explorer working and tune per the Epicor document
that's available.

-Wayne Cox