[6.1] Lock Table Setting

Since this is a one-time conversion, use -1 parameter for single-user mode. I believe Progress doesn't use Lock Table entries in that mode.

And if you want it to run faster, use -i for no database integrity. But backup the database before you start.

----- Original Message -----
From: "Chris Crosta" <chris@...>
To: <vantage@yahoogroups.com>
Sent: Wednesday, April 19, 2006 10:21 AM
Subject: RE: [Vantage] [6.1] Lock Table Setting


Todd,

I had to set mine to 250,000 to get this run on my first month end after
going live, you may need to go higher depending on the number of
transactions you have.



Chris



_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Todd Caughey
Sent: Wednesday, April 19, 2006 10:12 AM
To: vantage@yahoogroups.com
Subject: [Vantage] [6.1] Lock Table Setting



We have a test database we are trying to run a G/L conversion on prior
to turning on G/L posting of costs. The specific conversion is 5,120
(Set Part TranG/L Account and Cost of Sales for WIP Shipments). Every
time we try to run it it crashes with a message to increase the -L
parameter for the lock table. I did this for the Test database
(Properties under DefaultConfiguration in PET). First to 25,024 (from 8
thousand something) to match the production DB, then on advice from
support to 163,840 (and in both cases stopped and restarted the DB).
Still getting the same error.

I suspect it is grabbing a HUGE number of records due to our being live
for over 5 years and lots of PartTran records. Any idea how large I can
set this parameter? What impact would this have on the system in
general, in particular the neighboring Live production database? Or
should I first be looking at trimming the PartTran table (if possible)?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co.


[Non-text portions of this message have been removed]
We have a test database we are trying to run a G/L conversion on prior to turning on G/L posting of costs. The specific conversion is 5,120 (Set Part TranG/L Account and Cost of Sales for WIP Shipments). Every time we try to run it it crashes with a message to increase the -L parameter for the lock table. I did this for the Test database (Properties under DefaultConfiguration in PET). First to 25,024 (from 8 thousand something) to match the production DB, then on advice from support to 163,840 (and in both cases stopped and restarted the DB). Still getting the same error.

I suspect it is grabbing a HUGE number of records due to our being live for over 5 years and lots of PartTran records. Any idea how large I can set this parameter? What impact would this have on the system in general, in particular the neighboring Live production database? Or should I first be looking at trimming the PartTran table (if possible)?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co.


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

I had to set mine to 250,000 to get this run on my first month end after
going live, you may need to go higher depending on the number of
transactions you have.



Chris



_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Todd Caughey
Sent: Wednesday, April 19, 2006 10:12 AM
To: vantage@yahoogroups.com
Subject: [Vantage] [6.1] Lock Table Setting



We have a test database we are trying to run a G/L conversion on prior
to turning on G/L posting of costs. The specific conversion is 5,120
(Set Part TranG/L Account and Cost of Sales for WIP Shipments). Every
time we try to run it it crashes with a message to increase the -L
parameter for the lock table. I did this for the Test database
(Properties under DefaultConfiguration in PET). First to 25,024 (from 8
thousand something) to match the production DB, then on advice from
support to 163,840 (and in both cases stopped and restarted the DB).
Still getting the same error.

I suspect it is grabbing a HUGE number of records due to our being live
for over 5 years and lots of PartTran records. Any idea how large I can
set this parameter? What impact would this have on the system in
general, in particular the neighboring Live production database? Or
should I first be looking at trimming the PartTran table (if possible)?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co.









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