disconnect use and lock release

[ymjamal]

Or did you leave "not" out of "When I disconnect this user via promon option 8, the lock is not(?) released."

No. I did not forget the not.
When the user locking is dbadmin, then when the user is disconnected the lock is released.
But if the user locking is NOT dbadmin, disconnecting the user does not release the lock.

I'll soon get a snapshot from the db log file and post as soon as I can.

TIA

 

[TomBascom]

You might try answering all of the follow-up questions. It will go a long ways towards resolving your issue.

When you only answer one it leaves the false impression that the others are not important or that they have obvious answers that have somehow been covered by the answer that you did deign to provide.

Outstanding follow-up questions:

1) Why would you want PSC to simulate (duplicate?) this (working) scenario? You clarified that it does actually work. Which just makes it even more confusing that you think there is something to be reported to PSC and for them to "simulate".

2) Is "dbadmin" a privileged user?

3) Does your DBA have a better description of the problem to be resolved?

The issue now seems to have morphed and been clarified to: "Disconnecting non-dbadmin users doesn't seem to work."

Additional points to clarify about that statement:

a) When you say "I sign on as" and "from another session of user" are you referring to the OS login id or the application login id?

b) What OS is this?

c) What userid is used to start the database?

 

[ymjamal]

1) It works only if the locking user is dbadmin.
2) No special pervilages to dbadmin except that is the owner of the database.
3) Our DBA has no clue. I took a snap shot of the database log file which may help identify the reason.
You are right the issue has now morphed. Originally when I posted I did not know that was the case.
a) I mean both unix and connection to db.
b) HP Unix 11.11 - Progress 10.1C
c) DataBase started by dbadmin.

Follows my test as user jamaly locking, after that as dbadmin locking.
Tom,
Notice the content of databse log. They are different in these 2 cases.

find first gen_loc
where gen_loc.entity = ""
and gen_loc.loc = "01"
exclusive-lock no-error.
if available gen_loc then do:
update gen_loc.add1.
end.
[While the update is waiting for go]:
[2011/11/14@12:33:28.425-0500] P-15480 T-1 I Usr 11: (708) Userid is now EWRAPPER.
[2011/11/14@12:33:28.509-0500] P-15480 T-1 I Usr 11: (12699) Database ltrack Options:
[2011/11/14@12:33:35.061-0500] P-15498 T-1 I Usr 12: (452) Login by jamaly on /dev/pts/tc.
[2011/11/14@12:33:35.117-0500] P-15498 T-1 I Usr 12: (12699) Database ltrack Options:
[2011/11/14@12:33:36.982-0500] P-15498 T-1 I Usr 12: (708) Userid is now jamaly.
dbadmin@hpdev:/u1$
***************************************************************************************
dbadmin@hpdev:/u1$cd /u/dlc101/bin
dbadmin@hpdev:/u/dlc101/bin$promon /u1/ltrack

OpenEdge MONITOR Release 10
Database: /u1/ltrack
1. User Control
2. Locking and Waiting Statistics
3. Block Access
4. Record Locking Table
5. Activity
6. Shared Resources
7. Database Status
8. Shut Down Database
R&D. Advanced options
T. 2PC Transactions Control
L. Resolve 2PC Limbo Transactions
C. 2PC Coordinator Information
J. Resolve JTA Transactions
M. Modify Defaults
Q. Quit
Enter your selection: 4
1. Display all entries
2. Match a user number
3. Match a range of user numbers
4. Match a record id
Q. Return to main menu
Enter your selection: 1

Record Locking Table:
Usr Name Chain # Rec-id Table Lock Flags Tran State Tran ID
12 jamaly REC 3608 15242337 15 EXCL Begin 124170
9637
RETURN - repeat, U - continue uninterrupted, Q - quit:
***********************************************************************************
Enter your selection: t
1. Display all entries
2. Match a user number
3. Match a range of user numbers
Q. Return to main menu
Enter your selection: 1

Transaction Control:
Usr Name Trans Login Time R-comm? Limbo? Crd? Coord Crd-task
12 jamaly 1241709637 11/14/11 12:33 no no no 0
RETURN - repeat, U - continue uninterrupted, Q - quit:
**********************************************************************************
Enter your selection: 8
usr pid time of login user id tty Limbo?
5 15325 Mon Nov 14 12:33:20 2011 APW no
6 15330 Mon Nov 14 12:33:21 2011 APW no
7 15338 Mon Nov 14 12:33:23 2011 BIW no
8 15342 Mon Nov 14 12:33:25 2011 WDOG no
9 15384 Mon Nov 14 12:33:26 2011 BATCH batch no
10 15412 Mon Nov 14 12:33:27 2011 FINISHER batch no
11 15480 Mon Nov 14 12:33:28 2011 EWRAPPER batch no
12 15498 Mon Nov 14 12:33:35 2011 jamaly /dev/pts/tc no
1 Disconnect a User
2 Unconditional Shutdown
3 Emergency Shutdown (Kill All)
x Exit
Enter choice>
***********************************************************************************
Enter choice> 1
Enter the user number which is to be disconnected: 12
User 12 disconnect initiated. (6796)
usr pid time of login user id tty Limbo?
5 15325 Mon Nov 14 12:33:20 2011 APW no
6 15330 Mon Nov 14 12:33:21 2011 APW no
7 15338 Mon Nov 14 12:33:23 2011 BIW no
8 15342 Mon Nov 14 12:33:25 2011 WDOG no
9 15384 Mon Nov 14 12:33:26 2011 BATCH batch no
10 15412 Mon Nov 14 12:33:27 2011 FINISHER batch no
11 15480 Mon Nov 14 12:33:28 2011 EWRAPPER batch no
1 Disconnect a User
2 Unconditional Shutdown
3 Emergency Shutdown (Kill All)
x Exit
Enter choice>
*********************************************************************************
Before backuout from session of jamaly:

[2011/11/14@12:33:35.061-0500] P-15498 T-1 I Usr 12: (452) Login by jamaly on /dev/pts/tc.
[2011/11/14@12:33:35.117-0500] P-15498 T-1 I Usr 12: (12699) Database ltrack Options:
[2011/11/14@12:33:36.982-0500] P-15498 T-1 I Usr 12: (708) Userid is now jamaly.
[2011/11/14@12:41:08.437-0500] P-16037 T-1 I SHUT 13: (-----) User 12 disconnect initiated
[2011/11/14@12:41:08.437-0500] P-15317 T-1 I BROKER 0: (-----) Sending signal 7 to user 12
dbadmin@hpdev:/u1$
*********************************************************************************
Record Locking Table:
Usr Name Chain # Rec-id Table Lock Flags Tran State Tran ID
12 jamaly REC 3608 15242337 15 EXCL Begin 124170
9637
RETURN - repeat, U - continue uninterrupted, Q - quit:
********************************************************************************
Transaction Control:
Usr Name Trans Login Time R-comm? Limbo? Crd? Coord Crd-task
12 jamaly 1241709637 11/14/11 12:33 no no no 0
RETURN - repeat, U - continue uninterrupted, Q - quit:
********************************************************************************
[now, in my session waiting for update of add1 I will backout (F4), only then the
lock is released and disconnect is compleeted]

*******************************************************************************
Transaction Control:
Usr Name Trans Login Time R-comm? Limbo? Crd? Coord Crd-task
RETURN - repeat, U - continue uninterrupted, Q - quit:
********************************************************************************
After F4 in the session of jamaly:

[2011/11/14@12:33:36.982-0500] P-15498 T-1 I Usr 12: (708) Userid is now jamaly.
[2011/11/14@12:41:08.437-0500] P-16037 T-1 I SHUT 13: (-----) User 12 disconnect initiated
[2011/11/14@12:41:08.437-0500] P-15317 T-1 I BROKER 0: (-----) Sending signal 7 to user 12
[2011/11/14@12:48:58.310-0500] P-15498 T-1 I Usr 12: (453) Logout by jamaly on /dev/pts/tc.

********************************************************************************
[Now, I'm going to repeat this test but instead of using my signon to update add1 of gen_loc, I'll use dbadmin].
[2011/11/14@12:49:29.466-0500] P-17218 T-1 I Usr 12: (452) Login by dbadmin on /dev/pts/tc.
[2011/11/14@12:49:29.520-0500] P-17218 T-1 I Usr 12: (12699) Database ltrack Options:
[2011/11/14@12:49:33.790-0500] P-17218 T-1 I Usr 12: (708) Userid is now dbadmin.
dbadmin@hpdev:/u1$
*******************************************************************************
Record Locking Table:
Usr Name Chain # Rec-id Table Lock Flags Tran State Tran ID
12 dbadmin REC 3608 15242337 15 EXCL Begin 124172
6328
RETURN - repeat, U - continue uninterrupted, Q - quit:
********************************************************************************
Enter your selection: 8
usr pid time of login user id tty Limbo?
5 15325 Mon Nov 14 12:33:20 2011 APW no
6 15330 Mon Nov 14 12:33:21 2011 APW no
7 15338 Mon Nov 14 12:33:23 2011 BIW no
8 15342 Mon Nov 14 12:33:25 2011 WDOG no
9 15384 Mon Nov 14 12:33:26 2011 BATCH batch no
10 15412 Mon Nov 14 12:33:27 2011 FINISHER batch no
11 15480 Mon Nov 14 12:33:28 2011 EWRAPPER batch no
12 17218 Mon Nov 14 12:49:29 2011 dbadmin /dev/pts/tc no
1 Disconnect a User
2 Unconditional Shutdown
3 Emergency Shutdown (Kill All)
x Exit
Enter choice> 1
Enter the user number which is to be disconnected: 12
User 12 disconnect initiated. (6796)
usr pid time of login user id tty Limbo?
5 15325 Mon Nov 14 12:33:20 2011 APW no
6 15330 Mon Nov 14 12:33:21 2011 APW no
7 15338 Mon Nov 14 12:33:23 2011 BIW no
8 15342 Mon Nov 14 12:33:25 2011 WDOG no
9 15384 Mon Nov 14 12:33:26 2011 BATCH batch no
10 15412 Mon Nov 14 12:33:27 2011 FINISHER batch no
11 15480 Mon Nov 14 12:33:28 2011 EWRAPPER batch no
1 Disconnect a User
2 Unconditional Shutdown
3 Emergency Shutdown (Kill All)
x Exit
Enter choice>
****************************************************************************
I do not have to backout (F4) for the connection to get terminated.

[2011/11/14@12:49:33.790-0500] P-17218 T-1 I Usr 12: (708) Userid is now dbadmin.
[2011/11/14@12:57:07.545-0500] P-17955 T-1 I SHUT 13: (-----) User 12 disconnect initiated
[2011/11/14@12:57:07.545-0500] P-15317 T-1 I BROKER 0: (-----) Sending signal 7 to user 12
[2011/11/14@12:57:07.546-0500] P-17218 T-1 I Usr 12: (2252) Begin transaction backout.
[2011/11/14@12:57:07.547-0500] P-17218 T-1 I Usr 12: (2253) Transaction backout completed.
[2011/11/14@12:57:07.549-0500] P-17218 T-1 I Usr 12: (453) Logout by dbadmin on /dev/pts/tc.
****************************************************************************
My question is why when the user locking is dbadmin is behaves as expected and when
the user is NOT dbadmin it does not backout the transaction and logout?

 

[TomBascom]

1) It works only if the locking user is dbadmin.
2) No special pervilages to dbadmin except that is the owner of the database.
3) Our DBA has no clue. I took a snap shot of the database log file which may help identify the reason.
You are right the issue has now morphed. Originally when I posted I did not know that was the case.
a) I mean both unix and connection to db.
b) HP Unix 11.11 - Progress 10.1C
c) DataBase started by dbadmin.

Thank you.

Follows my test as user jamaly locking, after that as dbadmin locking.

You are still only showing one side of the problem (as originally stated, it may be that this has now morphed into such a different problem that that no longer matters).

Because this has been portrayed as a lock conflict issue (original post: "We need to disconnet a user that is locking record(s) needed by a batch process") I'm trying to follow along on my system -- I have 3 windows open. One for "session 1", another for "session 2" and a 3rd for PROMON. But I see nothing here to put into session 2. And no evidence of any lock conflict.

Notice the content of databse log. They are different in these 2 cases.

You lost me. I don't know what is different or what the 2 cases are.

find first gen_loc
where gen_loc.entity = ""
and gen_loc.loc = "01"
exclusive-lock no-error.
if available gen_loc then do:
update gen_loc.add1.
end.
[While the update is waiting for go]:

What does "waiting for the go" mean?

I see a program which is either going to get an exclusive lock and update, or which will block with a "gen_loc in use by..." message if someone else has a lock on gen_loc...

So what happens? Are you prompted to update? Or do you get the "in use by" message?

[2011/11/14@12:33:28.425-0500] P-15480 T-1 I Usr 11: (708) Userid is now EWRAPPER.
[2011/11/14@12:33:28.509-0500] P-15480 T-1 I Usr 11: (12699) Database ltrack Options:
[2011/11/14@12:33:35.061-0500] P-15498 T-1 I Usr 12: (452) Login by jamaly on /dev/pts/tc.
[2011/11/14@12:33:35.117-0500] P-15498 T-1 I Usr 12: (12699) Database ltrack Options:
[2011/11/14@12:33:36.982-0500] P-15498 T-1 I Usr 12: (708) Userid is now jamaly.

One of your sessions has logged in. Is it the one running the code above? Or something else?

dbadmin@hpdev:/u1$
***************************************************************************************
dbadmin@hpdev:/u1$cd /u/dlc101/bin
dbadmin@hpdev:/u/dlc101/bin$promon /u1/ltrack

OpenEdge MONITOR Release 10
Database: /u1/ltrack
1. User Control
2. Locking and Waiting Statistics
3. Block Access
4. Record Locking Table
5. Activity
6. Shared Resources
7. Database Status
8. Shut Down Database
R&D. Advanced options
T. 2PC Transactions Control
L. Resolve 2PC Limbo Transactions
C. 2PC Coordinator Information
J. Resolve JTA Transactions
M. Modify Defaults
Q. Quit
Enter your selection: 4
1. Display all entries
2. Match a user number
3. Match a range of user numbers
4. Match a record id
Q. Return to main menu
Enter your selection: 1

Record Locking Table:
Usr Name Chain # Rec-id Table Lock Flags Tran State Tran ID
12 jamaly REC 3608 15242337 15 EXCL Begin 124170
9637
RETURN - repeat, U - continue uninterrupted, Q - quit:

You are logged in and you have a lock.

Nobody else has a lock nor is anyone waiting on one so I'm not sure what you could be complaining about.

***********************************************************************************
Enter your selection: t
1. Display all entries
2. Match a user number
3. Match a range of user numbers
Q. Return to main menu
Enter your selection: 1

Transaction Control:
Usr Name Trans Login Time R-comm? Limbo? Crd? Coord Crd-task
12 jamaly 1241709637 11/14/11 12:33 no no no 0
RETURN - repeat, U - continue uninterrupted, Q - quit:

I'm not sure how I missed this before but... why are you looking in the Two-phase commit menu? Are you using 2PC??? Do you have more than 1 database? The sample code only involves one table so 2PC doesn't apply.

**********************************************************************************
Enter your selection: 8
usr pid time of login user id tty Limbo?
5 15325 Mon Nov 14 12:33:20 2011 APW no
6 15330 Mon Nov 14 12:33:21 2011 APW no
7 15338 Mon Nov 14 12:33:23 2011 BIW no
8 15342 Mon Nov 14 12:33:25 2011 WDOG no
9 15384 Mon Nov 14 12:33:26 2011 BATCH batch no
10 15412 Mon Nov 14 12:33:27 2011 FINISHER batch no
11 15480 Mon Nov 14 12:33:28 2011 EWRAPPER batch no
12 15498 Mon Nov 14 12:33:35 2011 jamaly /dev/pts/tc no
1 Disconnect a User
2 Unconditional Shutdown
3 Emergency Shutdown (Kill All)
x Exit
Enter choice>
***********************************************************************************
Enter choice> 1
Enter the user number which is to be disconnected: 12
User 12 disconnect initiated. (6796)
usr pid time of login user id tty Limbo?
5 15325 Mon Nov 14 12:33:20 2011 APW no
6 15330 Mon Nov 14 12:33:21 2011 APW no
7 15338 Mon Nov 14 12:33:23 2011 BIW no
8 15342 Mon Nov 14 12:33:25 2011 WDOG no
9 15384 Mon Nov 14 12:33:26 2011 BATCH batch no
10 15412 Mon Nov 14 12:33:27 2011 FINISHER batch no
11 15480 Mon Nov 14 12:33:28 2011 EWRAPPER batch no
1 Disconnect a User
2 Unconditional Shutdown
3 Emergency Shutdown (Kill All)
x Exit
Enter choice>
*********************************************************************************
Before backuout from session of jamaly:

Before? That makes no sense. Above you disconnected the user. Below the .lg file shows that occurring.

Does "backout" mean something other than "disconnect"?

[2011/11/14@12:33:35.061-0500] P-15498 T-1 I Usr 12: (452) Login by jamaly on /dev/pts/tc.
[2011/11/14@12:33:35.117-0500] P-15498 T-1 I Usr 12: (12699) Database ltrack Options:
[2011/11/14@12:33:36.982-0500] P-15498 T-1 I Usr 12: (708) Userid is now jamaly.
[2011/11/14@12:41:08.437-0500] P-16037 T-1 I SHUT 13: (-----) User 12 disconnect initiated
[2011/11/14@12:41:08.437-0500] P-15317 T-1 I BROKER 0: (-----) Sending signal 7 to user 12
dbadmin@hpdev:/u1$
*********************************************************************************

No messages like this?

[2011/11/14@14:40:59.913-0500] P-24460 T--809879808 I ABL 12: (2252) Begin transaction backout.
[2011/11/14@14:40:59.913-0500] P-24460 T--809879808 I ABL 12: (2253) Transaction backout completed.

The lack of these messages is saying that something has gone horribly wrong.

Is Progress installed setuid to root?

Use this command to see:

ls -l $DLC/bin/_progres

Has process 15498 really died:

ps -ef | grep 15498

Record Locking Table:
Usr Name Chain # Rec-id Table Lock Flags Tran State Tran ID
12 jamaly REC 3608 15242337 15 EXCL Begin 124170
9637
RETURN - repeat, U - continue uninterrupted, Q - quit:
********************************************************************************

So this is a new jamaly login?

Transaction Control:
Usr Name Trans Login Time R-comm? Limbo? Crd? Coord Crd-task
12 jamaly 1241709637 11/14/11 12:33 no no no 0
RETURN - repeat, U - continue uninterrupted, Q - quit:
********************************************************************************
[now, in my session waiting for update of add1 I will backout (F4), only then the
lock is released and disconnect is completed]

What is the point of this F4 action?

*******************************************************************************
Transaction Control:
Usr Name Trans Login Time R-comm? Limbo? Crd? Coord Crd-task
RETURN - repeat, U - continue uninterrupted, Q - quit:
********************************************************************************
After F4 in the session of jamaly:

[2011/11/14@12:33:36.982-0500] P-15498 T-1 I Usr 12: (708) Userid is now jamaly.
[2011/11/14@12:41:08.437-0500] P-16037 T-1 I SHUT 13: (-----) User 12 disconnect initiated
[2011/11/14@12:41:08.437-0500] P-15317 T-1 I BROKER 0: (-----) Sending signal 7 to user 12
[2011/11/14@12:48:58.310-0500] P-15498 T-1 I Usr 12: (453) Logout by jamaly on /dev/pts/tc.

********************************************************************************
[Now, I'm going to repeat this test but instead of using my signon to update add1 of gen_loc, I'll use dbadmin].
[2011/11/14@12:49:29.466-0500] P-17218 T-1 I Usr 12: (452) Login by dbadmin on /dev/pts/tc.
[2011/11/14@12:49:29.520-0500] P-17218 T-1 I Usr 12: (12699) Database ltrack Options:
[2011/11/14@12:49:33.790-0500] P-17218 T-1 I Usr 12: (708) Userid is now dbadmin.
dbadmin@hpdev:/u1$
*******************************************************************************
Record Locking Table:
Usr Name Chain # Rec-id Table Lock Flags Tran State Tran ID
12 dbadmin REC 3608 15242337 15 EXCL Begin 124172
6328
RETURN - repeat, U - continue uninterrupted, Q - quit:
********************************************************************************
Enter your selection: 8
usr pid time of login user id tty Limbo?
5 15325 Mon Nov 14 12:33:20 2011 APW no
6 15330 Mon Nov 14 12:33:21 2011 APW no
7 15338 Mon Nov 14 12:33:23 2011 BIW no
8 15342 Mon Nov 14 12:33:25 2011 WDOG no
9 15384 Mon Nov 14 12:33:26 2011 BATCH batch no
10 15412 Mon Nov 14 12:33:27 2011 FINISHER batch no
11 15480 Mon Nov 14 12:33:28 2011 EWRAPPER batch no
12 17218 Mon Nov 14 12:49:29 2011 dbadmin /dev/pts/tc no
1 Disconnect a User
2 Unconditional Shutdown
3 Emergency Shutdown (Kill All)
x Exit
Enter choice> 1
Enter the user number which is to be disconnected: 12
User 12 disconnect initiated. (6796)
usr pid time of login user id tty Limbo?
5 15325 Mon Nov 14 12:33:20 2011 APW no
6 15330 Mon Nov 14 12:33:21 2011 APW no
7 15338 Mon Nov 14 12:33:23 2011 BIW no
8 15342 Mon Nov 14 12:33:25 2011 WDOG no
9 15384 Mon Nov 14 12:33:26 2011 BATCH batch no
10 15412 Mon Nov 14 12:33:27 2011 FINISHER batch no
11 15480 Mon Nov 14 12:33:28 2011 EWRAPPER batch no
1 Disconnect a User
2 Unconditional Shutdown
3 Emergency Shutdown (Kill All)
x Exit
Enter choice>
****************************************************************************
I do not have to backout (F4) for the connection to get terminated.

[2011/11/14@12:49:33.790-0500] P-17218 T-1 I Usr 12: (708) Userid is now dbadmin.
[2011/11/14@12:57:07.545-0500] P-17955 T-1 I SHUT 13: (-----) User 12 disconnect initiated
[2011/11/14@12:57:07.545-0500] P-15317 T-1 I BROKER 0: (-----) Sending signal 7 to user 12
[2011/11/14@12:57:07.546-0500] P-17218 T-1 I Usr 12: (2252) Begin transaction backout.
[2011/11/14@12:57:07.547-0500] P-17218 T-1 I Usr 12: (2253) Transaction backout completed.
[2011/11/14@12:57:07.549-0500] P-17218 T-1 I Usr 12: (453) Logout by dbadmin on /dev/pts/tc.
****************************************************************************

And in this case you have proper transaction backout.

My question is why when the user locking is dbadmin is behaves as expected and when
the user is NOT dbadmin it does not backout the transaction and logout?

I don't see any lock conflicts anywhere in any of this. In all of your examples there is only ever the one lock.

You are now describing a problem with "disconnect" terminating a user session. That is quite different from where this all started and it is still difficult to say what is really going on, there are still a lot of unclear procedures taking place and the timeline seems to be highly fluid.

My best wild guess, at the moment, is that you have setup permissions so that dbadmin can disconnect users but other users cannot. This may be because you have installed Progress without the executables being setuid to root --which prevents signals from being delivered properly. Or it might be something totally different.

 

[ymjamal]

Tom,

Waiting for lock is not the problem. I mentioned in my original post to explain why I did want to disconnect a user (It is due to a wait for lock by batch process that I need to disconnect a user).

So in my examples you will not see a session waiting for lock, that has nothing to do with disconnecting a user (or the reason for disconnecting).

My problem is when I disconnect a user it does not perform the transaction backout and the proper logout (as per log file). I found that out by looking at the log file (thanks to your suggestion).

There must be something different between a vanila user and dbadmin.

{Quote/]My best wild guess, at the moment, is that you have setup permissions so that dbadmin can disconnect users but other users cannot. This may be because you have installed Progress without the executables being setuid to root --which prevents signals from being delivered properly. Or it might be something totally different.[/Quote]
In both cases it is dbadmin that is running promon to disconnect.

At your sugestion:
[FONT=r_ansi][FONT=r_ansi] jamaly@hpprod:/home/jamali$ ls -l $DLC/bin/_progres
-rwsr-xr-x 1 root sys 9793536 May 8 2006 /u/dlc101/bin/_progres
jamaly@hpprod:/home/jamali$

and:
ps still shows the session connected.


There must be something different between a vanila user and dbadmin user.

TIA

[/FONT][/FONT]

 

[TomBascom]

Tom,

Waiting for lock is not the problem. I mentioned in my original post to explain why I did want to disconnect a user (It is due to a wait for lock by batch process that I need to disconnect a user).

So in my examples you will not see a session waiting for lock, that has nothing to do with disconnecting a user (or the reason for disconnecting).

To para-phrase: Waiting for a lock is not a problem. I want to disconnect the user because another user will have to wait for a lock.

I'm having a bit of trouble wrapping my head around that but I'll let it pass for now.

My problem is when I disconnect a user it does not perform the transaction backout and the proper logout (as per log file). I found that out by looking at the log file (thanks to your suggestion).

I can agree that that does indeed seem to be the problem that we are currently working on.

There must be something different between a vanila user and dbadmin.

My best wild guess, at the moment, is that you have setup permissions so that dbadmin can disconnect users but other users cannot. This may be because you have installed Progress without the executables being setuid to root --which prevents signals from being delivered properly. Or it might be something totally different.

In both cases it is dbadmin that is running promon to disconnect.

That seems like a new tidbit. I was under the impression that you were trying to use the same userid to disconnect the user in all cases.

In general you are going to have problems when non-privileged users attempt to disconnect users who do not share the same userid. Signals can only be passed across such boundaries by a privileged user (root).

The details regarding exactly what can happen and why may vary from OS to OS and between Progress releases.

At your sugestion:
[FONT=r_ansi][FONT=r_ansi] jamaly@hpprod:/home/jamali$ ls -l $DLC/bin/_progres
-rwsr-xr-x 1 root sys 9793536 May 8 2006 /u/dlc101/bin/_progres
jamaly@hpprod:/home/jamali$

The _progres executable is setuid to root.

and:
ps still shows the session connected.

That is as it should be. But it establishes that the session did not die (like from a kill -9).

There must be something different between a vanila user and dbadmin user.

I think that all that you are seeing is that you can disconnect your own sessions but not other people's.

 

[ymjamal]

I think that all that you are seeing is that you can disconnect your own sessions but not other people's.

Tom,
That is what I suspected.
So, I run promon as jamaly to disconnect the locking session (by jamaly) but that did not terminate the session.
It only works when dbadmin disconnects dbadmin.
There must be something at OS level. I'll ask our Unix guru to look into it.
Thanks for your help.