5.0 Schema Changes

Yahoo Archive
1
For anyone having trouble with the schema change... there is
a fast schema change procedure available from epicor. You'll
have to call support and ask for it.

Tim Care wrote:
>
> Rick,
>
> In trying to convert our db on a test system, we ran into
> the same problem. What we ended up doing was running
> the conversion on the server, and changing the connect options
> in the schema change vtg file to -1. You do need to have
> provision in order to do this. Support can talk you through the
> setup of the vtg file. Hope this helps. Good luck.
>
> Tim Care
> Electro Chemical Finishing
>
> ----- Original Message -----
> From: "Rick Spriggle" <rspriggle@...>
> To: <vantage@yahoogroups.com>
> Sent: Monday, March 05, 2001 7:17 AM
> Subject: [Vantage] 5.0 Schema Changes
>
> > Currently we are on 3.00.632 and have an approximately 1gb database. This
> > spring we would like to jump right to 5.0. I did the conversions to 4.0
> on
> > a test server and it amounted to about a days worth - manageable - and the
> > database grew to 1.2gb. Now I'm doing the 5.0 schema changes and it has
> > been running since 1:00pm last Thursday, 90 hours on the task manager cpu
> > counter! Yes, I have crash protection turned off or at least I think I
> do.
> > This was the part where Epicor's installation instructions for Progress
> > Explorer really fell short and I had to use the online help.
> >
> > What has anybody else with a large database done to get around this? I
> > remember a discussion earlier in the year about connecting as a single
> user
> > to run the schema changes. Assuming we were already live on 4.0 and that
> > step was out, what am I supposed to do to upgrade, tell the plant to shut
> > down for a week? Any suggestions are welcome.
> >
> > Thanks,
> >
> > Rick
> >
> > PS - And Epicor wonders why we are still on 3.0.
> >
> >
> >
> >
> >
> > Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
> >
> >
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
2
Currently we are on 3.00.632 and have an approximately 1gb database. This
spring we would like to jump right to 5.0. I did the conversions to 4.0 on
a test server and it amounted to about a days worth - manageable - and the
database grew to 1.2gb. Now I'm doing the 5.0 schema changes and it has
been running since 1:00pm last Thursday, 90 hours on the task manager cpu
counter! Yes, I have crash protection turned off or at least I think I do.
This was the part where Epicor's installation instructions for Progress
Explorer really fell short and I had to use the online help.

What has anybody else with a large database done to get around this? I
remember a discussion earlier in the year about connecting as a single user
to run the schema changes. Assuming we were already live on 4.0 and that
step was out, what am I supposed to do to upgrade, tell the plant to shut
down for a week? Any suggestions are welcome.

Thanks,

Rick

PS - And Epicor wonders why we are still on 3.0.
3
Rick:
My 340 mb database (relatively small compared to some of the
rest of you guys) took about an hour and 10 minutes for the schema change
and about ? hour for the conversions. Obviously network speed, hardware
configuration has something to do with it but it shouldn't take that long.
Even a day going to 4.0 sounds like a long time.

Anyways, I did my schema change by starting a Vantage session on the server.
That way I at least eliminated the network traffic issue.

I did the 5.0 conversion a couple times and it didn't take that long. Call
me if you have any questions. We'll get it taken care of.

Terry L. Williams I.S. Manager Chipsco, Inc. 9936 Liberty St. Ext.
Meadville, PA 16335 814-333-6331 x236 fax: 814-337-2548 tlw@...
<mailto:tlw@...> www.chipsco.com <http://www.chipsco.com/>

-----Original Message-----
From: Rick Spriggle [mailto:rspriggle@...]
Sent: Monday, March 05, 2001 7:18 AM
To: vantage@yahoogroups.com
Subject: [Vantage] 5.0 Schema Changes

Currently we are on 3.00.632 and have an approximately 1gb database. This
spring we would like to jump right to 5.0. I did the conversions to 4.0 on
a test server and it amounted to about a days worth - manageable - and the
database grew to 1.2gb. Now I'm doing the 5.0 schema changes and it has
been running since 1:00pm last Thursday, 90 hours on the task manager cpu
counter! Yes, I have crash protection turned off or at least I think I do.
This was the part where Epicor's installation instructions for Progress
Explorer really fell short and I had to use the online help.

What has anybody else with a large database done to get around this? I
remember a discussion earlier in the year about connecting as a single user
to run the schema changes. Assuming we were already live on 4.0 and that
step was out, what am I supposed to do to upgrade, tell the plant to shut
down for a week? Any suggestions are welcome.

Thanks,

Rick

PS - And Epicor wonders why we are still on 3.0.




Yahoo! Groups Sponsor
Click Here to Find Software Faster
Click Here to Find Software Faster
<http://rd.yahoo.com/M=162801.1342103.2934627/D=egroupmail/S=1700007183:N/A=
599088/*http://www.knowledgestorm.com/jump_white.html?c=Yahoo&n=eLert_Comput
ersInternet_Software_WhiteGridTime&t=ad>


Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
<http://docs.yahoo.com/info/terms/> .


[Non-text portions of this message have been removed]
4
Actually just completed the upgrade to 5.0 last weekend. I had a 1.5GB
database. The Schema change took 4 hours to finish. As for the database
conversion, it took a total of 12 hours to complete. One problem I did
run into that you may want to look out for is the Lock Table overflow
error -L. 7 hours into the conversion I started to get this error. It
did not stop until I bumped my -L setting up to 350,000.

Steven Beals
Beaver Brook Circuits, Inc.

-----Original Message-----
From: Terry Williams [mailto:tlw@...]
Sent: Monday, March 05, 2001 8:26 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] 5.0 Schema Changes


Rick:
My 340 mb database (relatively small compared to some of the
rest of you guys) took about an hour and 10 minutes for the schema
change
and about ? hour for the conversions. Obviously network speed, hardware
configuration has something to do with it but it shouldn't take that
long.
Even a day going to 4.0 sounds like a long time.

Anyways, I did my schema change by starting a Vantage session on the
server.
That way I at least eliminated the network traffic issue.

I did the 5.0 conversion a couple times and it didn't take that long.
Call
me if you have any questions. We'll get it taken care of.

Terry L. Williams I.S. Manager Chipsco, Inc. 9936 Liberty St. Ext.
Meadville, PA 16335 814-333-6331 x236 fax: 814-337-2548
tlw@...
<mailto:tlw@...> www.chipsco.com <http://www.chipsco.com/>

-----Original Message-----
From: Rick Spriggle [mailto:rspriggle@...]
Sent: Monday, March 05, 2001 7:18 AM
To: vantage@yahoogroups.com
Subject: [Vantage] 5.0 Schema Changes

Currently we are on 3.00.632 and have an approximately 1gb database.
This
spring we would like to jump right to 5.0. I did the conversions to 4.0
on
a test server and it amounted to about a days worth - manageable - and
the
database grew to 1.2gb. Now I'm doing the 5.0 schema changes and it has
been running since 1:00pm last Thursday, 90 hours on the task manager
cpu
counter! Yes, I have crash protection turned off or at least I think I
do.
This was the part where Epicor's installation instructions for Progress
Explorer really fell short and I had to use the online help.

What has anybody else with a large database done to get around this? I
remember a discussion earlier in the year about connecting as a single
user
to run the schema changes. Assuming we were already live on 4.0 and
that
step was out, what am I supposed to do to upgrade, tell the plant to
shut
down for a week? Any suggestions are welcome.

Thanks,

Rick

PS - And Epicor wonders why we are still on 3.0.




Yahoo! Groups Sponsor
Click Here to Find Software Faster
Click Here to Find Software Faster
<http://rd.yahoo.com/M=162801.1342103.2934627/D=egroupmail/S=1700007183:
N/A=
599088/*http://www.knowledgestorm.com/jump_white.html?c=Yahoo&n=eLert_Co
mput
ersInternet_Software_WhiteGridTime&t=ad>


Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
<http://docs.yahoo.com/info/terms/> .


[Non-text portions of this message have been removed]





Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
5
Rick,

In trying to convert our db on a test system, we ran into
the same problem. What we ended up doing was running
the conversion on the server, and changing the connect options
in the schema change vtg file to -1. You do need to have
provision in order to do this. Support can talk you through the
setup of the vtg file. Hope this helps. Good luck.

Tim Care
Electro Chemical Finishing

----- Original Message -----
From: "Rick Spriggle" <rspriggle@...>
To: <vantage@yahoogroups.com>
Sent: Monday, March 05, 2001 7:17 AM
Subject: [Vantage] 5.0 Schema Changes


> Currently we are on 3.00.632 and have an approximately 1gb database. This
> spring we would like to jump right to 5.0. I did the conversions to 4.0
on
> a test server and it amounted to about a days worth - manageable - and the
> database grew to 1.2gb. Now I'm doing the 5.0 schema changes and it has
> been running since 1:00pm last Thursday, 90 hours on the task manager cpu
> counter! Yes, I have crash protection turned off or at least I think I
do.
> This was the part where Epicor's installation instructions for Progress
> Explorer really fell short and I had to use the online help.
>
> What has anybody else with a large database done to get around this? I
> remember a discussion earlier in the year about connecting as a single
user
> to run the schema changes. Assuming we were already live on 4.0 and that
> step was out, what am I supposed to do to upgrade, tell the plant to shut
> down for a week? Any suggestions are welcome.
>
> Thanks,
>
> Rick
>
> PS - And Epicor wonders why we are still on 3.0.
>
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>