Record lock timeouts

[system]

Yeah we are using SQL. Most of the reports donÂ’t just read data but
actually compile data into tables first and then read it, and then clear the
table.



Daniel Laidig



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
too_much_hg
Sent: Friday, April 24, 2009 1:50 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Record lock timeouts








Daniel,

We see something similar to this.

Why would they lock a record when the report is only reading the information
in the first place ?

Are you running SQL ?

Neil

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> , "Daniel
Laidig" <daniellaidig@...> wrote:

>
> We got this Record lock timeout error pretty frequently (twice a week)

when

> first moving to Vantage 8. During the record timeout, MES could still
> process transactions but no one in vantage could save or add any records,

no

> matter what table. They could access all records but just couldn't save
> them. Once the user clicks save, the vantage screen just turns white and

it

> looks like vantage crashes. But if we instructed them to wait 30 minutes,
> the record lock would clear and their record would save. Users were
> obviously getting very frustrated and vantage support was, of course no
> help. They had no idea why our records were being locked and just told us
> we had to deal with it. We did find that every time our records were
> locked, a user had run a big report, mostly where used report WITHOUT
> putting a filter partnumber so it was running where used for ALL 80K parts
> in our database! When we had a record lock timeout and cleared a report
> that had been running in the background for days, everything went back to
> normal. So every night, we clear stale sessions and reports that are
> running and have been forgotten about. We haven't had a record lock since
> then. Hope that helps.
>
> Daniel Laidig
>
>
> From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of

> too_much_hg
> Sent: Thursday, April 23, 2009 4:20 PM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: Record lock timeouts
>
>
>
>
>
>
>
>
> Yes, we are at Patch 33.
>
> I am going to post another question about how to do maintenance on the
> database .... like nullfixer.r and any other tools I should run and

how/when

> to run them.
>
> Maybe I will get some good tips from that.
>
> Neil
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%40yahoogroups.com> ,

> "Steve_E" <vantage@> wrote:
> >
> > No, I worked with tech and progress to fix the locking problem.
> >
> > Have you installed the latest and greatest progress patch?
> >
> > Steve
> >
> >
> > -----Original Message-----
> > From: too_much_hg [mailto:neil_willet@]
> > Sent: April 23, 2009 10:52 AM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>

<mailto:vantage%40yahoogroups.com>

> > Subject: [Vantage] Re: Record lock timeouts
> >
> >
> >
> >
> >
> > Has anyone out there modified this (progress side) parameter on their
> system ?
> >
> > What experience have you had after making this change ?
> >
> > Is this something that I would want to change even tho I have SQL 2005

for

> the Database ? Since SQL defaults to 3min maybe I should set my Progress
> value to 5min from the default 30min.
> >
> > Trying to understand the implications of making this change.
> >
> > Thanks,
> > Neil
> >
> > --- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com, DD
> <ddavis4569@> wrote:
> > >
> > > I believe you are thinking about the SQL database lock value. It
> defaults to 3 minutes.
> > > The Progress Lock Timeout is 30 minutes but can be set to a minumun of

1

> minute.
> > > Â
> > > Â
> > > Â
> > > Lock Timeout (-lkwtmo) seconds
> > > The wait time, in seconds.
> > > Use Lock Timeout (-lkwtmo) to specify a different wait time (in
> seconds). A Progress process
> > > encountering a locked resource waits for a limited time before
> continuing execution. If the
> > > resource is still locked, the process times out and the wait is
> canceled. This feature is called
> > > â€Å"lock wait timeout.”
> > > The default wait time is 1800 seconds (30 minutes). The minimum value

is

> 60 seconds. If a user
> > > specifies a value less than 60 seconds, Progress silently sets the

value

> at 60 seconds.
> > > NOTE: The wait time is accurate to within one minute of the value
> specified.
> > > Lock timeout applies to interactive and batch clients.
> > > Lock timeout affects WAIT-FOR record locks, schema locks, and
> transaction commit locks.
> > > Lock timeout does not affect internal locks used inside the database
> manager, such as buffer
> > > locks.
> > >
> > >
> > > --- On Wed, 4/22/09, Nigel Kerley <nigel.kerley@> wrote:
> > >
> > > From: Nigel Kerley <nigel.kerley@>
> > > Subject: [Vantage] Re: Record lock timeouts
> > > To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
> > > Date: Wednesday, April 22, 2009, 3:06 AM
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Hi Neil,
> > >
> > > My understanding is that the default Progress timeout is 3 minutes.
> > > So if you can't find any setting that changes it, that's what it

should

> be.
> > >
> > > Nigel.
> > >
> > > --- In vantage@yahoogroups .com, "too_much_hg" <neil_willet@ ...>

wrote:

> > > >
> > > > Hi Nigel,
> > > >
> > > > Do you know what the default value in PET is ?
> > > >
> > > > I don't have any setting in mine and I think I have had some record
> lock problems as well.
> > > >
> > > > Thanks,
> > > > Neil
> > > >
> > > > --- In vantage@yahoogroups .com, "Nigel Kerley" <nigel.kerley@ >
> wrote:
> > > > >
> > > > > Hi Ed,
> > > > >
> > > > > The default timeout is (I believe) 3 minutes, so it appears at
> though someone has already adjusted yours. You need to find out where the
> config was adjusted and change this setting - rather than "blindly" insert

a

> new setting.
> > > > >
> > > > > The usual place to make this change is in the mfgsys.pf file
> (\\server\epicor\ mfgsys\server\ config). There may be an entry on the

first

> line like "-lkwtmo 1800". The figure is the number of seconds for the
> timeout.
> > > > >
> > > > > The only other place I can think of for this is in the database
> settings within PET. Go to Databases | MfgSys803 | Configurations |
> defaultConfiguratio n - then Properties and look in "Other server

arguments"

> for "-lkwtmo 1800".
> > > > >
> > > > > By any chance, did this timeout come from a Service Connect
> workflow? The timeouts for them can be set in the workflow itself.
> > > > >
> > > > >
> > > > > Nigel.
> > > > >
> > > > > --- In vantage@yahoogroups .com, "Ed Garbowski" <egarbowski@ >
> wrote:
> > > > > >
> > > > > > We ran into a progress record lock problem this weekend that
> brought to light an excessive timeout that I'd like to adjust. The lock
> released after 30 minutes which should be reduced to 2 minutes or so. Can
> anyone tell me where the database timeout defaults can be adjusted?
> > > > > >
> > > > > > Thanks,
> > > > > > Ed
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

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

[system]

We ran into a progress record lock problem this weekend that brought to light an excessive timeout that I'd like to adjust. The lock released after 30 minutes which should be reduced to 2 minutes or so. Can anyone tell me where the database timeout defaults can be adjusted?

Thanks,
Ed

[system]

Hi Ed,

The default timeout is (I believe) 3 minutes, so it appears at though someone has already adjusted yours. You need to find out where the config was adjusted and change this setting - rather than "blindly" insert a new setting.

The usual place to make this change is in the mfgsys.pf file (\\server\epicor\mfgsys\server\config). There may be an entry on the first line like "-lkwtmo 1800". The figure is the number of seconds for the timeout.

The only other place I can think of for this is in the database settings within PET. Go to Databases | MfgSys803 | Configurations | defaultConfiguration - then Properties and look in "Other server arguments" for "-lkwtmo 1800".

By any chance, did this timeout come from a Service Connect workflow? The timeouts for them can be set in the workflow itself.


Nigel.

--- In vantage@yahoogroups.com, "Ed Garbowski" <egarbowski@...> wrote:
>
> We ran into a progress record lock problem this weekend that brought to light an excessive timeout that I'd like to adjust. The lock released after 30 minutes which should be reduced to 2 minutes or so. Can anyone tell me where the database timeout defaults can be adjusted?
>
> Thanks,
> Ed
>

[system]

Hi Nigel,

Do you know what the default value in PET is ?

I don't have any setting in mine and I think I have had some record lock problems as well.

Thanks,
Neil

--- In vantage@yahoogroups.com, "Nigel Kerley" <nigel.kerley@...> wrote:
>
> Hi Ed,
>
> The default timeout is (I believe) 3 minutes, so it appears at though someone has already adjusted yours. You need to find out where the config was adjusted and change this setting - rather than "blindly" insert a new setting.
>
> The usual place to make this change is in the mfgsys.pf file (\\server\epicor\mfgsys\server\config). There may be an entry on the first line like "-lkwtmo 1800". The figure is the number of seconds for the timeout.
>
> The only other place I can think of for this is in the database settings within PET. Go to Databases | MfgSys803 | Configurations | defaultConfiguration - then Properties and look in "Other server arguments" for "-lkwtmo 1800".
>
> By any chance, did this timeout come from a Service Connect workflow? The timeouts for them can be set in the workflow itself.
>
>
> Nigel.
>
> --- In vantage@yahoogroups.com, "Ed Garbowski" <egarbowski@> wrote:
> >
> > We ran into a progress record lock problem this weekend that brought to light an excessive timeout that I'd like to adjust. The lock released after 30 minutes which should be reduced to 2 minutes or so. Can anyone tell me where the database timeout defaults can be adjusted?
> >
> > Thanks,
> > Ed
> >
>

[system]

Here is what the Progress Startup Reference book has to say:
Â
Client 4GL Parameters
Lock Timeout -lkwtmo seconds Specify a different “lock wait timeout.”
Â
Lock Timeout (-lkwtmo) seconds
The wait time, in seconds.
Use Lock Timeout (-lkwtmo) to specify a different wait time (in seconds). A Progress process
encountering a locked resource waits for a limited time before continuing execution. If the
resource is still locked, the process times out and the wait is canceled. This feature is called
“lock wait timeout.”
The default wait time is 1800 seconds (30 minutes). The minimum value is 60 seconds. If a user
specifies a value less than 60 seconds, Progress silently sets the value at 60 seconds.
NOTE: The wait time is accurate to within one minute of the value specified.
Lock timeout applies to interactive and batch clients.
Lock timeout affects WAIT-FOR record locks, schema locks, and transaction commit locks.
Lock timeout does not affect internal locks used inside the database manager, such as buffer locks.

--- On Tue, 4/21/09, too_much_hg <neil_willet@...> wrote:

From: too_much_hg <neil_willet@...>
Subject: [Vantage] Re: Record lock timeouts
To: vantage@yahoogroups.com
Date: Tuesday, April 21, 2009, 1:02 PM








Hi Nigel,

Do you know what the default value in PET is ?

I don't have any setting in mine and I think I have had some record lock problems as well.

Thanks,
Neil

--- In vantage@yahoogroups .com, "Nigel Kerley" <nigel.kerley@ ...> wrote:
>
> Hi Ed,
>
> The default timeout is (I believe) 3 minutes, so it appears at though someone has already adjusted yours. You need to find out where the config was adjusted and change this setting - rather than "blindly" insert a new setting.
>
> The usual place to make this change is in the mfgsys.pf file (\\server\epicor\ mfgsys\server\ config). There may be an entry on the first line like "-lkwtmo 1800". The figure is the number of seconds for the timeout.
>
> The only other place I can think of for this is in the database settings within PET. Go to Databases | MfgSys803 | Configurations | defaultConfiguratio n - then Properties and look in "Other server arguments" for "-lkwtmo 1800".
>
> By any chance, did this timeout come from a Service Connect workflow? The timeouts for them can be set in the workflow itself.
>
>
> Nigel.
>
> --- In vantage@yahoogroups .com, "Ed Garbowski" <egarbowski@ > wrote:
> >
> > We ran into a progress record lock problem this weekend that brought to light an excessive timeout that I'd like to adjust. The lock released after 30 minutes which should be reduced to 2 minutes or so. Can anyone tell me where the database timeout defaults can be adjusted?
> >
> > Thanks,
> > Ed
> >
>



















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

[system]

Thanks for that info.

I wonder what the danger of having the locks actuall time out ?

Seems to me that if it doesn't unlock for 30 minutes it probably will never unlock, might as well give up on the record after say .... 5 or 10 minutes.

Assuming it gave up on that record, does it proceed on to the next record that may be locked and wait all over again ? Probably.

I wonder if lowering this timeout would get thru "hung" processing much faster because it would "give up" on locked records faster and eventually fail it's way to the end in less time.

Sorry for the ramble, does this make sense ?

Neil

--- In vantage@yahoogroups.com, DD <ddavis4569@...> wrote:
>
> Here is what the Progress Startup Reference book has to say:
> ÂÂ
> Client 4GL Parameters
> Lock Timeout -lkwtmo seconds Specify a different “lock wait timeout.”
> ÂÂ
> Lock Timeout (-lkwtmo) seconds
> The wait time, in seconds.
> Use Lock Timeout (-lkwtmo) to specify a different wait time (in seconds). A Progress process
> encountering a locked resource waits for a limited time before continuing execution. If the
> resource is still locked, the process times out and the wait is canceled. This feature is called
> “lock wait timeout.”
> The default wait time is 1800 seconds (30 minutes). The minimum value is 60 seconds. If a user
> specifies a value less than 60 seconds, Progress silently sets the value at 60 seconds.
> NOTE: The wait time is accurate to within one minute of the value specified.
> Lock timeout applies to interactive and batch clients.
> Lock timeout affects WAIT-FOR record locks, schema locks, and transaction commit locks.
> Lock timeout does not affect internal locks used inside the database manager, such as buffer locks.
>
> --- On Tue, 4/21/09, too_much_hg <neil_willet@...> wrote:
>
> From: too_much_hg <neil_willet@...>
> Subject: [Vantage] Re: Record lock timeouts
> To: vantage@yahoogroups.com
> Date: Tuesday, April 21, 2009, 1:02 PM
>
>
>
>
>
>
>
>
> Hi Nigel,
>
> Do you know what the default value in PET is ?
>
> I don't have any setting in mine and I think I have had some record lock problems as well.
>
> Thanks,
> Neil
>
> --- In vantage@yahoogroups .com, "Nigel Kerley" <nigel.kerley@ ...> wrote:
> >
> > Hi Ed,
> >
> > The default timeout is (I believe) 3 minutes, so it appears at though someone has already adjusted yours. You need to find out where the config was adjusted and change this setting - rather than "blindly" insert a new setting.
> >
> > The usual place to make this change is in the mfgsys.pf file (\\server\epicor\ mfgsys\server\ config). There may be an entry on the first line like "-lkwtmo 1800". The figure is the number of seconds for the timeout.
> >
> > The only other place I can think of for this is in the database settings within PET. Go to Databases | MfgSys803 | Configurations | defaultConfiguratio n - then Properties and look in "Other server arguments" for "-lkwtmo 1800".
> >
> > By any chance, did this timeout come from a Service Connect workflow? The timeouts for them can be set in the workflow itself.
> >
> >
> > Nigel.
> >
> > --- In vantage@yahoogroups .com, "Ed Garbowski" <egarbowski@ > wrote:
> > >
> > > We ran into a progress record lock problem this weekend that brought to light an excessive timeout that I'd like to adjust. The lock released after 30 minutes which should be reduced to 2 minutes or so. Can anyone tell me where the database timeout defaults can be adjusted?
> > >
> > > Thanks,
> > > Ed
> > >
> >
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[system]

Hi Neil,

My understanding is that the default Progress timeout is 3 minutes.
So if you can't find any setting that changes it, that's what it should be.

Nigel.

--- In vantage@yahoogroups.com, "too_much_hg" <neil_willet@...> wrote:
>
> Hi Nigel,
>
> Do you know what the default value in PET is ?
>
> I don't have any setting in mine and I think I have had some record lock problems as well.
>
> Thanks,
> Neil
>
> --- In vantage@yahoogroups.com, "Nigel Kerley" <nigel.kerley@> wrote:
> >
> > Hi Ed,
> >
> > The default timeout is (I believe) 3 minutes, so it appears at though someone has already adjusted yours. You need to find out where the config was adjusted and change this setting - rather than "blindly" insert a new setting.
> >
> > The usual place to make this change is in the mfgsys.pf file (\\server\epicor\mfgsys\server\config). There may be an entry on the first line like "-lkwtmo 1800". The figure is the number of seconds for the timeout.
> >
> > The only other place I can think of for this is in the database settings within PET. Go to Databases | MfgSys803 | Configurations | defaultConfiguration - then Properties and look in "Other server arguments" for "-lkwtmo 1800".
> >
> > By any chance, did this timeout come from a Service Connect workflow? The timeouts for them can be set in the workflow itself.
> >
> >
> > Nigel.
> >
> > --- In vantage@yahoogroups.com, "Ed Garbowski" <egarbowski@> wrote:
> > >
> > > We ran into a progress record lock problem this weekend that brought to light an excessive timeout that I'd like to adjust. The lock released after 30 minutes which should be reduced to 2 minutes or so. Can anyone tell me where the database timeout defaults can be adjusted?
> > >
> > > Thanks,
> > > Ed
> > >
> >
>

[system]

I posted this yesterday morning before seeing DDs related post. It didn't appear in the Group so I didn't correct it.

My thanks to DD for correcting me with the real default timeout of 30mins - I was too lazy to look up the reference book!

--- In vantage@yahoogroups.com, "Nigel Kerley" <nigel.kerley@...> wrote:
>
> Hi Neil,
>
> My understanding is that the default Progress timeout is 3 minutes.
> So if you can't find any setting that changes it, that's what it should be.
>
> Nigel.
>
> --- In vantage@yahoogroups.com, "too_much_hg" <neil_willet@> wrote:
> >
> > Hi Nigel,
> >
> > Do you know what the default value in PET is ?
> >
> > I don't have any setting in mine and I think I have had some record lock problems as well.
> >
> > Thanks,
> > Neil
> >
> > --- In vantage@yahoogroups.com, "Nigel Kerley" <nigel.kerley@> wrote:
> > >
> > > Hi Ed,
> > >
> > > The default timeout is (I believe) 3 minutes, so it appears at though someone has already adjusted yours. You need to find out where the config was adjusted and change this setting - rather than "blindly" insert a new setting.
> > >
> > > The usual place to make this change is in the mfgsys.pf file (\\server\epicor\mfgsys\server\config). There may be an entry on the first line like "-lkwtmo 1800". The figure is the number of seconds for the timeout.
> > >
> > > The only other place I can think of for this is in the database settings within PET. Go to Databases | MfgSys803 | Configurations | defaultConfiguration - then Properties and look in "Other server arguments" for "-lkwtmo 1800".
> > >
> > > By any chance, did this timeout come from a Service Connect workflow? The timeouts for them can be set in the workflow itself.
> > >
> > >
> > > Nigel.
> > >
> > > --- In vantage@yahoogroups.com, "Ed Garbowski" <egarbowski@> wrote:
> > > >
> > > > We ran into a progress record lock problem this weekend that brought to light an excessive timeout that I'd like to adjust. The lock released after 30 minutes which should be reduced to 2 minutes or so. Can anyone tell me where the database timeout defaults can be adjusted?
> > > >
> > > > Thanks,
> > > > Ed
> > > >
> > >
> >
>

[system]

I believe you are thinking about the SQL database lock value. It defaults to 3 minutes.
The Progress Lock Timeout is 30 minutes but can be set to a minumun of 1 minute.
Â
Â
Â
Lock Timeout (-lkwtmo) seconds
The wait time, in seconds.
Use Lock Timeout (-lkwtmo) to specify a different wait time (in seconds). A Progress process
encountering a locked resource waits for a limited time before continuing execution. If the
resource is still locked, the process times out and the wait is canceled. This feature is called
“lock wait timeout.”
The default wait time is 1800 seconds (30 minutes). The minimum value is 60 seconds. If a user
specifies a value less than 60 seconds, Progress silently sets the value at 60 seconds.
NOTE: The wait time is accurate to within one minute of the value specified.
Lock timeout applies to interactive and batch clients.
Lock timeout affects WAIT-FOR record locks, schema locks, and transaction commit locks.
Lock timeout does not affect internal locks used inside the database manager, such as buffer
locks.

--- On Wed, 4/22/09, Nigel Kerley <nigel.kerley@...> wrote:

From: Nigel Kerley <nigel.kerley@...>
Subject: [Vantage] Re: Record lock timeouts
To: vantage@yahoogroups.com
Date: Wednesday, April 22, 2009, 3:06 AM








Hi Neil,

My understanding is that the default Progress timeout is 3 minutes.
So if you can't find any setting that changes it, that's what it should be.

Nigel.

--- In vantage@yahoogroups .com, "too_much_hg" <neil_willet@ ...> wrote:
>
> Hi Nigel,
>
> Do you know what the default value in PET is ?
>
> I don't have any setting in mine and I think I have had some record lock problems as well.
>
> Thanks,
> Neil
>
> --- In vantage@yahoogroups .com, "Nigel Kerley" <nigel.kerley@ > wrote:
> >
> > Hi Ed,
> >
> > The default timeout is (I believe) 3 minutes, so it appears at though someone has already adjusted yours. You need to find out where the config was adjusted and change this setting - rather than "blindly" insert a new setting.
> >
> > The usual place to make this change is in the mfgsys.pf file (\\server\epicor\ mfgsys\server\ config). There may be an entry on the first line like "-lkwtmo 1800". The figure is the number of seconds for the timeout.
> >
> > The only other place I can think of for this is in the database settings within PET. Go to Databases | MfgSys803 | Configurations | defaultConfiguratio n - then Properties and look in "Other server arguments" for "-lkwtmo 1800".
> >
> > By any chance, did this timeout come from a Service Connect workflow? The timeouts for them can be set in the workflow itself.
> >
> >
> > Nigel.
> >
> > --- In vantage@yahoogroups .com, "Ed Garbowski" <egarbowski@ > wrote:
> > >
> > > We ran into a progress record lock problem this weekend that brought to light an excessive timeout that I'd like to adjust. The lock released after 30 minutes which should be reduced to 2 minutes or so. Can anyone tell me where the database timeout defaults can be adjusted?
> > >
> > > Thanks,
> > > Ed
> > >
> >
>



















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

[system]

Has anyone out there modified this (progress side) parameter on their system ?

What experience have you had after making this change ?

Is this something that I would want to change even tho I have SQL 2005 for the Database ? Since SQL defaults to 3min maybe I should set my Progress value to 5min from the default 30min.

Trying to understand the implications of making this change.

Thanks,
Neil

--- In vantage@yahoogroups.com, DD <ddavis4569@...> wrote:
>
> I believe you are thinking about the SQL database lock value. It defaults to 3 minutes.
> The Progress Lock Timeout is 30 minutes but can be set to a minumun of 1 minute.
> ÂÂ
> ÂÂ
> ÂÂ
> Lock Timeout (-lkwtmo) seconds
> The wait time, in seconds.
> Use Lock Timeout (-lkwtmo) to specify a different wait time (in seconds). A Progress process
> encountering a locked resource waits for a limited time before continuing execution. If the
> resource is still locked, the process times out and the wait is canceled. This feature is called
> “lock wait timeout.”
> The default wait time is 1800 seconds (30 minutes). The minimum value is 60 seconds. If a user
> specifies a value less than 60 seconds, Progress silently sets the value at 60 seconds.
> NOTE: The wait time is accurate to within one minute of the value specified.
> Lock timeout applies to interactive and batch clients.
> Lock timeout affects WAIT-FOR record locks, schema locks, and transaction commit locks.
> Lock timeout does not affect internal locks used inside the database manager, such as buffer
> locks.
>
>
> --- On Wed, 4/22/09, Nigel Kerley <nigel.kerley@...> wrote:
>
> From: Nigel Kerley <nigel.kerley@...>
> Subject: [Vantage] Re: Record lock timeouts
> To: vantage@yahoogroups.com
> Date: Wednesday, April 22, 2009, 3:06 AM
>
>
>
>
>
>
>
>
> Hi Neil,
>
> My understanding is that the default Progress timeout is 3 minutes.
> So if you can't find any setting that changes it, that's what it should be.
>
> Nigel.
>
> --- In vantage@yahoogroups .com, "too_much_hg" <neil_willet@ ...> wrote:
> >
> > Hi Nigel,
> >
> > Do you know what the default value in PET is ?
> >
> > I don't have any setting in mine and I think I have had some record lock problems as well.
> >
> > Thanks,
> > Neil
> >
> > --- In vantage@yahoogroups .com, "Nigel Kerley" <nigel.kerley@ > wrote:
> > >
> > > Hi Ed,
> > >
> > > The default timeout is (I believe) 3 minutes, so it appears at though someone has already adjusted yours. You need to find out where the config was adjusted and change this setting - rather than "blindly" insert a new setting.
> > >
> > > The usual place to make this change is in the mfgsys.pf file (\\server\epicor\ mfgsys\server\ config). There may be an entry on the first line like "-lkwtmo 1800". The figure is the number of seconds for the timeout.
> > >
> > > The only other place I can think of for this is in the database settings within PET. Go to Databases | MfgSys803 | Configurations | defaultConfiguratio n - then Properties and look in "Other server arguments" for "-lkwtmo 1800".
> > >
> > > By any chance, did this timeout come from a Service Connect workflow? The timeouts for them can be set in the workflow itself.
> > >
> > >
> > > Nigel.
> > >
> > > --- In vantage@yahoogroups .com, "Ed Garbowski" <egarbowski@ > wrote:
> > > >
> > > > We ran into a progress record lock problem this weekend that brought to light an excessive timeout that I'd like to adjust. The lock released after 30 minutes which should be reduced to 2 minutes or so. Can anyone tell me where the database timeout defaults can be adjusted?
> > > >
> > > > Thanks,
> > > > Ed
> > > >
> > >
> >
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[system]

No, I worked with tech and progress to fix the locking problem.

Have you installed the latest and greatest progress patch?

Steve


-----Original Message-----
From: too_much_hg [mailto:neil_willet@...]
Sent: April 23, 2009 10:52 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Record lock timeouts





Has anyone out there modified this (progress side) parameter on their system ?

What experience have you had after making this change ?

Is this something that I would want to change even tho I have SQL 2005 for the Database ? Since SQL defaults to 3min maybe I should set my Progress value to 5min from the default 30min.

Trying to understand the implications of making this change.

Thanks,
Neil

--- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com, DD <ddavis4569@...> wrote:
>
> I believe you are thinking about the SQL database lock value. It defaults to 3 minutes.
> The Progress Lock Timeout is 30 minutes but can be set to a minumun of 1 minute.
> Â
> Â
> Â
> Lock Timeout (-lkwtmo) seconds
> The wait time, in seconds.
> Use Lock Timeout (-lkwtmo) to specify a different wait time (in seconds). A Progress process
> encountering a locked resource waits for a limited time before continuing execution. If the
> resource is still locked, the process times out and the wait is canceled. This feature is called
> “lock wait timeout.”
> The default wait time is 1800 seconds (30 minutes). The minimum value is 60 seconds. If a user
> specifies a value less than 60 seconds, Progress silently sets the value at 60 seconds.
> NOTE: The wait time is accurate to within one minute of the value specified.
> Lock timeout applies to interactive and batch clients.
> Lock timeout affects WAIT-FOR record locks, schema locks, and transaction commit locks.
> Lock timeout does not affect internal locks used inside the database manager, such as buffer
> locks.
>
>
> --- On Wed, 4/22/09, Nigel Kerley <nigel.kerley@...> wrote:
>
> From: Nigel Kerley <nigel.kerley@...>
> Subject: [Vantage] Re: Record lock timeouts
> To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
> Date: Wednesday, April 22, 2009, 3:06 AM
>
>
>
>
>
>
>
>
> Hi Neil,
>
> My understanding is that the default Progress timeout is 3 minutes.
> So if you can't find any setting that changes it, that's what it should be.
>
> Nigel.
>
> --- In vantage@yahoogroups .com, "too_much_hg" <neil_willet@ ...> wrote:
> >
> > Hi Nigel,
> >
> > Do you know what the default value in PET is ?
> >
> > I don't have any setting in mine and I think I have had some record lock problems as well.
> >
> > Thanks,
> > Neil
> >
> > --- In vantage@yahoogroups .com, "Nigel Kerley" <nigel.kerley@ > wrote:
> > >
> > > Hi Ed,
> > >
> > > The default timeout is (I believe) 3 minutes, so it appears at though someone has already adjusted yours. You need to find out where the config was adjusted and change this setting - rather than "blindly" insert a new setting.
> > >
> > > The usual place to make this change is in the mfgsys.pf file (\\server\epicor\ mfgsys\server\ config). There may be an entry on the first line like "-lkwtmo 1800". The figure is the number of seconds for the timeout.
> > >
> > > The only other place I can think of for this is in the database settings within PET. Go to Databases | MfgSys803 | Configurations | defaultConfiguratio n - then Properties and look in "Other server arguments" for "-lkwtmo 1800".
> > >
> > > By any chance, did this timeout come from a Service Connect workflow? The timeouts for them can be set in the workflow itself.
> > >
> > >
> > > Nigel.
> > >
> > > --- In vantage@yahoogroups .com, "Ed Garbowski" <egarbowski@ > wrote:
> > > >
> > > > We ran into a progress record lock problem this weekend that brought to light an excessive timeout that I'd like to adjust. The lock released after 30 minutes which should be reduced to 2 minutes or so. Can anyone tell me where the database timeout defaults can be adjusted?
> > > >
> > > > Thanks,
> > > > Ed
> > > >
> > >
> >
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>







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

[system]

Yes, we are at Patch 33.

I am going to post another question about how to do maintenance on the database .... like nullfixer.r and any other tools I should run and how/when to run them.

Maybe I will get some good tips from that.

Neil

--- In vantage@yahoogroups.com, "Steve_E" <vantage@...> wrote:
>
> No, I worked with tech and progress to fix the locking problem.
>
> Have you installed the latest and greatest progress patch?
>
> Steve
>
>
> -----Original Message-----
> From: too_much_hg [mailto:neil_willet@...]
> Sent: April 23, 2009 10:52 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Record lock timeouts
>
>
>
>
>
> Has anyone out there modified this (progress side) parameter on their system ?
>
> What experience have you had after making this change ?
>
> Is this something that I would want to change even tho I have SQL 2005 for the Database ? Since SQL defaults to 3min maybe I should set my Progress value to 5min from the default 30min.
>
> Trying to understand the implications of making this change.
>
> Thanks,
> Neil
>
> --- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com, DD <ddavis4569@> wrote:
> >
> > I believe you are thinking about the SQL database lock value. It defaults to 3 minutes.
> > The Progress Lock Timeout is 30 minutes but can be set to a minumun of 1 minute.
> > Â
> > Â
> > Â
> > Lock Timeout (-lkwtmo) seconds
> > The wait time, in seconds.
> > Use Lock Timeout (-lkwtmo) to specify a different wait time (in seconds). A Progress process
> > encountering a locked resource waits for a limited time before continuing execution. If the
> > resource is still locked, the process times out and the wait is canceled. This feature is called
> > â€Å"lock wait timeout.”
> > The default wait time is 1800 seconds (30 minutes). The minimum value is 60 seconds. If a user
> > specifies a value less than 60 seconds, Progress silently sets the value at 60 seconds.
> > NOTE: The wait time is accurate to within one minute of the value specified.
> > Lock timeout applies to interactive and batch clients.
> > Lock timeout affects WAIT-FOR record locks, schema locks, and transaction commit locks.
> > Lock timeout does not affect internal locks used inside the database manager, such as buffer
> > locks.
> >
> >
> > --- On Wed, 4/22/09, Nigel Kerley <nigel.kerley@> wrote:
> >
> > From: Nigel Kerley <nigel.kerley@>
> > Subject: [Vantage] Re: Record lock timeouts
> > To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
> > Date: Wednesday, April 22, 2009, 3:06 AM
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi Neil,
> >
> > My understanding is that the default Progress timeout is 3 minutes.
> > So if you can't find any setting that changes it, that's what it should be.
> >
> > Nigel.
> >
> > --- In vantage@yahoogroups .com, "too_much_hg" <neil_willet@ ...> wrote:
> > >
> > > Hi Nigel,
> > >
> > > Do you know what the default value in PET is ?
> > >
> > > I don't have any setting in mine and I think I have had some record lock problems as well.
> > >
> > > Thanks,
> > > Neil
> > >
> > > --- In vantage@yahoogroups .com, "Nigel Kerley" <nigel.kerley@ > wrote:
> > > >
> > > > Hi Ed,
> > > >
> > > > The default timeout is (I believe) 3 minutes, so it appears at though someone has already adjusted yours. You need to find out where the config was adjusted and change this setting - rather than "blindly" insert a new setting.
> > > >
> > > > The usual place to make this change is in the mfgsys.pf file (\\server\epicor\ mfgsys\server\ config). There may be an entry on the first line like "-lkwtmo 1800". The figure is the number of seconds for the timeout.
> > > >
> > > > The only other place I can think of for this is in the database settings within PET. Go to Databases | MfgSys803 | Configurations | defaultConfiguratio n - then Properties and look in "Other server arguments" for "-lkwtmo 1800".
> > > >
> > > > By any chance, did this timeout come from a Service Connect workflow? The timeouts for them can be set in the workflow itself.
> > > >
> > > >
> > > > Nigel.
> > > >
> > > > --- In vantage@yahoogroups .com, "Ed Garbowski" <egarbowski@ > wrote:
> > > > >
> > > > > We ran into a progress record lock problem this weekend that brought to light an excessive timeout that I'd like to adjust. The lock released after 30 minutes which should be reduced to 2 minutes or so. Can anyone tell me where the database timeout defaults can be adjusted?
> > > > >
> > > > > Thanks,
> > > > > Ed
> > > > >
> > > >
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[system]

We got this Record lock timeout error pretty frequently (twice a week) when
first moving to Vantage 8. During the record timeout, MES could still
process transactions but no one in vantage could save or add any records, no
matter what table. They could access all records but just couldnÂ’t save
them. Once the user clicks save, the vantage screen just turns white and it
looks like vantage crashes. But if we instructed them to wait 30 minutes,
the record lock would clear and their record would save. Users were
obviously getting very frustrated and vantage support was, of course no
help. They had no idea why our records were being locked and just told us
we had to deal with it. We did find that every time our records were
locked, a user had run a big report, mostly where used report WITHOUT
putting a filter partnumber so it was running where used for ALL 80K parts
in our database! When we had a record lock timeout and cleared a report
that had been running in the background for days, everything went back to
normal. So every night, we clear stale sessions and reports that are
running and have been forgotten about. We havenÂ’t had a record lock since
then. Hope that helps.

Daniel Laidig


From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
too_much_hg
Sent: Thursday, April 23, 2009 4:20 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Record lock timeouts








Yes, we are at Patch 33.

I am going to post another question about how to do maintenance on the
database .... like nullfixer.r and any other tools I should run and how/when
to run them.

Maybe I will get some good tips from that.

Neil

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Steve_E" <vantage@...> wrote:

>
> No, I worked with tech and progress to fix the locking problem.
>
> Have you installed the latest and greatest progress patch?
>
> Steve
>
>
> -----Original Message-----
> From: too_much_hg [mailto:neil_willet@...]
> Sent: April 23, 2009 10:52 AM
> To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> Subject: [Vantage] Re: Record lock timeouts
>
>
>
>
>
> Has anyone out there modified this (progress side) parameter on their

system ?

>
> What experience have you had after making this change ?
>
> Is this something that I would want to change even tho I have SQL 2005 for

the Database ? Since SQL defaults to 3min maybe I should set my Progress
value to 5min from the default 30min.

>
> Trying to understand the implications of making this change.
>
> Thanks,
> Neil
>
> --- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com, DD

<ddavis4569@> wrote:

> >
> > I believe you are thinking about the SQL database lock value. It

defaults to 3 minutes.

> > The Progress Lock Timeout is 30 minutes but can be set to a minumun of 1

minute.

> > Â
> > Â
> > Â
> > Lock Timeout (-lkwtmo) seconds
> > The wait time, in seconds.
> > Use Lock Timeout (-lkwtmo) to specify a different wait time (in

seconds). A Progress process

> > encountering a locked resource waits for a limited time before

continuing execution. If the

> > resource is still locked, the process times out and the wait is

canceled. This feature is called

> > â€Å"lock wait timeout.”
> > The default wait time is 1800 seconds (30 minutes). The minimum value is

60 seconds. If a user

> > specifies a value less than 60 seconds, Progress silently sets the value

at 60 seconds.

> > NOTE: The wait time is accurate to within one minute of the value

specified.

> > Lock timeout applies to interactive and batch clients.
> > Lock timeout affects WAIT-FOR record locks, schema locks, and

transaction commit locks.

> > Lock timeout does not affect internal locks used inside the database

manager, such as buffer

> > locks.
> >
> >
> > --- On Wed, 4/22/09, Nigel Kerley <nigel.kerley@> wrote:
> >
> > From: Nigel Kerley <nigel.kerley@>
> > Subject: [Vantage] Re: Record lock timeouts
> > To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
> > Date: Wednesday, April 22, 2009, 3:06 AM
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi Neil,
> >
> > My understanding is that the default Progress timeout is 3 minutes.
> > So if you can't find any setting that changes it, that's what it should

be.

> >
> > Nigel.
> >
> > --- In vantage@yahoogroups .com, "too_much_hg" <neil_willet@ ...> wrote:
> > >
> > > Hi Nigel,
> > >
> > > Do you know what the default value in PET is ?
> > >
> > > I don't have any setting in mine and I think I have had some record

lock problems as well.

> > >
> > > Thanks,
> > > Neil
> > >
> > > --- In vantage@yahoogroups .com, "Nigel Kerley" <nigel.kerley@ >

wrote:

> > > >
> > > > Hi Ed,
> > > >
> > > > The default timeout is (I believe) 3 minutes, so it appears at

though someone has already adjusted yours. You need to find out where the
config was adjusted and change this setting - rather than "blindly" insert a
new setting.

> > > >
> > > > The usual place to make this change is in the mfgsys.pf file

(\\server\epicor\ mfgsys\server\ config). There may be an entry on the first
line like "-lkwtmo 1800". The figure is the number of seconds for the
timeout.

> > > >
> > > > The only other place I can think of for this is in the database

settings within PET. Go to Databases | MfgSys803 | Configurations |
defaultConfiguratio n - then Properties and look in "Other server arguments"
for "-lkwtmo 1800".

> > > >
> > > > By any chance, did this timeout come from a Service Connect

workflow? The timeouts for them can be set in the workflow itself.

> > > >
> > > >
> > > > Nigel.
> > > >
> > > > --- In vantage@yahoogroups .com, "Ed Garbowski" <egarbowski@ >

wrote:

> > > > >
> > > > > We ran into a progress record lock problem this weekend that

brought to light an excessive timeout that I'd like to adjust. The lock
released after 30 minutes which should be reduced to 2 minutes or so. Can
anyone tell me where the database timeout defaults can be adjusted?

> > > > >
> > > > > Thanks,
> > > > > Ed
> > > > >
> > > >
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

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

[system]

Daniel,

We see something similar to this.

Why would they lock a record when the report is only reading the information in the first place ?

Are you running SQL ?

Neil

--- In vantage@yahoogroups.com, "Daniel Laidig" <daniellaidig@...> wrote:
>
> We got this Record lock timeout error pretty frequently (twice a week) when
> first moving to Vantage 8. During the record timeout, MES could still
> process transactions but no one in vantage could save or add any records, no
> matter what table. They could access all records but just couldn't save
> them. Once the user clicks save, the vantage screen just turns white and it
> looks like vantage crashes. But if we instructed them to wait 30 minutes,
> the record lock would clear and their record would save. Users were
> obviously getting very frustrated and vantage support was, of course no
> help. They had no idea why our records were being locked and just told us
> we had to deal with it. We did find that every time our records were
> locked, a user had run a big report, mostly where used report WITHOUT
> putting a filter partnumber so it was running where used for ALL 80K parts
> in our database! When we had a record lock timeout and cleared a report
> that had been running in the background for days, everything went back to
> normal. So every night, we clear stale sessions and reports that are
> running and have been forgotten about. We haven't had a record lock since
> then. Hope that helps.
>
> Daniel Laidig
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
> too_much_hg
> Sent: Thursday, April 23, 2009 4:20 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Record lock timeouts
>
>
>
>
>
>
>
>
> Yes, we are at Patch 33.
>
> I am going to post another question about how to do maintenance on the
> database .... like nullfixer.r and any other tools I should run and how/when
> to run them.
>
> Maybe I will get some good tips from that.
>
> Neil
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
> "Steve_E" <vantage@> wrote:
> >
> > No, I worked with tech and progress to fix the locking problem.
> >
> > Have you installed the latest and greatest progress patch?
> >
> > Steve
> >
> >
> > -----Original Message-----
> > From: too_much_hg [mailto:neil_willet@]
> > Sent: April 23, 2009 10:52 AM
> > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > Subject: [Vantage] Re: Record lock timeouts
> >
> >
> >
> >
> >
> > Has anyone out there modified this (progress side) parameter on their
> system ?
> >
> > What experience have you had after making this change ?
> >
> > Is this something that I would want to change even tho I have SQL 2005 for
> the Database ? Since SQL defaults to 3min maybe I should set my Progress
> value to 5min from the default 30min.
> >
> > Trying to understand the implications of making this change.
> >
> > Thanks,
> > Neil
> >
> > --- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com, DD
> <ddavis4569@> wrote:
> > >
> > > I believe you are thinking about the SQL database lock value. It
> defaults to 3 minutes.
> > > The Progress Lock Timeout is 30 minutes but can be set to a minumun of 1
> minute.
> > > Â
> > > Â
> > > Â
> > > Lock Timeout (-lkwtmo) seconds
> > > The wait time, in seconds.
> > > Use Lock Timeout (-lkwtmo) to specify a different wait time (in
> seconds). A Progress process
> > > encountering a locked resource waits for a limited time before
> continuing execution. If the
> > > resource is still locked, the process times out and the wait is
> canceled. This feature is called
> > > â€Å"lock wait timeout.”
> > > The default wait time is 1800 seconds (30 minutes). The minimum value is
> 60 seconds. If a user
> > > specifies a value less than 60 seconds, Progress silently sets the value
> at 60 seconds.
> > > NOTE: The wait time is accurate to within one minute of the value
> specified.
> > > Lock timeout applies to interactive and batch clients.
> > > Lock timeout affects WAIT-FOR record locks, schema locks, and
> transaction commit locks.
> > > Lock timeout does not affect internal locks used inside the database
> manager, such as buffer
> > > locks.
> > >
> > >
> > > --- On Wed, 4/22/09, Nigel Kerley <nigel.kerley@> wrote:
> > >
> > > From: Nigel Kerley <nigel.kerley@>
> > > Subject: [Vantage] Re: Record lock timeouts
> > > To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
> > > Date: Wednesday, April 22, 2009, 3:06 AM
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Hi Neil,
> > >
> > > My understanding is that the default Progress timeout is 3 minutes.
> > > So if you can't find any setting that changes it, that's what it should
> be.
> > >
> > > Nigel.
> > >
> > > --- In vantage@yahoogroups .com, "too_much_hg" <neil_willet@ ...> wrote:
> > > >
> > > > Hi Nigel,
> > > >
> > > > Do you know what the default value in PET is ?
> > > >
> > > > I don't have any setting in mine and I think I have had some record
> lock problems as well.
> > > >
> > > > Thanks,
> > > > Neil
> > > >
> > > > --- In vantage@yahoogroups .com, "Nigel Kerley" <nigel.kerley@ >
> wrote:
> > > > >
> > > > > Hi Ed,
> > > > >
> > > > > The default timeout is (I believe) 3 minutes, so it appears at
> though someone has already adjusted yours. You need to find out where the
> config was adjusted and change this setting - rather than "blindly" insert a
> new setting.
> > > > >
> > > > > The usual place to make this change is in the mfgsys.pf file
> (\\server\epicor\ mfgsys\server\ config). There may be an entry on the first
> line like "-lkwtmo 1800". The figure is the number of seconds for the
> timeout.
> > > > >
> > > > > The only other place I can think of for this is in the database
> settings within PET. Go to Databases | MfgSys803 | Configurations |
> defaultConfiguratio n - then Properties and look in "Other server arguments"
> for "-lkwtmo 1800".
> > > > >
> > > > > By any chance, did this timeout come from a Service Connect
> workflow? The timeouts for them can be set in the workflow itself.
> > > > >
> > > > >
> > > > > Nigel.
> > > > >
> > > > > --- In vantage@yahoogroups .com, "Ed Garbowski" <egarbowski@ >
> wrote:
> > > > > >
> > > > > > We ran into a progress record lock problem this weekend that
> brought to light an excessive timeout that I'd like to adjust. The lock
> released after 30 minutes which should be reduced to 2 minutes or so. Can
> anyone tell me where the database timeout defaults can be adjusted?
> > > > > >
> > > > > > Thanks,
> > > > > > Ed
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>