Vantage Locks and Protop utility

Michael,

We are also experiencing similar locks in the db. It seems to be occurring when large reports are run from within vantage or crystal reports that are complicated are run periodically. We use an SQL backend and are able to run some queries to track the Locks backwards.

Unfortunately we cannot see the exact user causing the problem. All we see is "Business objects" or the databases name.

If you find anything we would be grateful for any knowledge.

Thanks

--- In vantage@yahoogroups.com, "michael.hutcheson@..." <michael.hutcheson@...> wrote:
>
> Hello,
>
> We are using Vantage 8.03.406 on a Progress backend and experience locks on certain forms, usually the labour Entry screen when large reports (i.e. sched shipments, WIP reconciliation). I've had a call logged with Epicor for months, I keep sending them log files, they keep asking for more, I keep sending more, they keep asking for more and so on.
>
> I've been looking into and it must be when the reports are run, they are creating a lock on a table that is used by these forms. It returns to normal either once the report is finished or after a server reboot. Is there any settings I can look at\amend on the app servers or database? I did create an additonal app server just for print jobs, but this was after the above started, and hence did not solve the problem.
>
> Also, has anyone used the protop tool from the below website?
>
> http://dbappraise.com/protop.html
>
> I'm trying to investigate where the locks happend and if it is a particualr client. I've changed the app server to verbose mode and added the '-debugalert' to the startup parameter to catch the client name. I'm kind of teaching myself Progress here to any help or tips would be great.
>
> Thanks,
>
> Michael
>
Hello,

We are using Vantage 8.03.406 on a Progress backend and experience locks on certain forms, usually the labour Entry screen when large reports (i.e. sched shipments, WIP reconciliation). I've had a call logged with Epicor for months, I keep sending them log files, they keep asking for more, I keep sending more, they keep asking for more and so on.

I've been looking into and it must be when the reports are run, they are creating a lock on a table that is used by these forms. It returns to normal either once the report is finished or after a server reboot. Is there any settings I can look at\amend on the app servers or database? I did create an additonal app server just for print jobs, but this was after the above started, and hence did not solve the problem.

Also, has anyone used the protop tool from the below website?

http://dbappraise.com/protop.html

I'm trying to investigate where the locks happend and if it is a particualr client. I've changed the app server to verbose mode and added the '-debugalert' to the startup parameter to catch the client name. I'm kind of teaching myself Progress here to any help or tips would be great.

Thanks,

Michael