Progress 10.2B03 / RHEL 5.11 - yep I know both are antient. Webe upgrading to OE 11.3 in Dec but I can't wait that long.
We have a situation where a SELF service user got disconnected and left a transaction with subsequent locks. Proshut disconnect doesn't let us finish him off.
1. His associated /u/progress/dlc/bin/_progres process lingers with Parent of PID 1 (one) - I've toying with the thought of totally clobber (kill -9) that process (not 1 but the child _progres). But I'm hesitant.
I thought a better way would to be to rollback his transaction using promon's "Resolve 2PC Limbo Transactions" option.
The record locks seems to indicate the transaction is in limbo:
Usr Name Chain # Rec-id Table Lock Flags Tran State Tran ID
354 dank REC 9422 64335249 154 EXCL L Active 196001859
354 dank REC 19990 83078865 154 EXCL L Active 196001859
354 dank REC 20785 10902328 154 EXCL L Active 196001859
354 dank REC 20787 10902330 154 EXCL L Active 196001859
But
Transaction Control:
Usr Name Trans Login Time R-comm? Limbo? Crd? Coord Crd-task
354 dank10 196001859 11/10/16 09:55 no no no 0
says it's not in Limbo.
2. Looks like we don't have 2PC enabled. So I guess this is not an option. Or will the Resolve option still work without any problems?
Any suggestions on how get rid of the locks / rollback the transaction other than restarting the database are greatly appreciated.
We have a situation where a SELF service user got disconnected and left a transaction with subsequent locks. Proshut disconnect doesn't let us finish him off.
1. His associated /u/progress/dlc/bin/_progres process lingers with Parent of PID 1 (one) - I've toying with the thought of totally clobber (kill -9) that process (not 1 but the child _progres). But I'm hesitant.
I thought a better way would to be to rollback his transaction using promon's "Resolve 2PC Limbo Transactions" option.
The record locks seems to indicate the transaction is in limbo:
Usr Name Chain # Rec-id Table Lock Flags Tran State Tran ID
354 dank REC 9422 64335249 154 EXCL L Active 196001859
354 dank REC 19990 83078865 154 EXCL L Active 196001859
354 dank REC 20785 10902328 154 EXCL L Active 196001859
354 dank REC 20787 10902330 154 EXCL L Active 196001859
But
Transaction Control:
Usr Name Trans Login Time R-comm? Limbo? Crd? Coord Crd-task
354 dank10 196001859 11/10/16 09:55 no no no 0
says it's not in Limbo.
2. Looks like we don't have 2PC enabled. So I guess this is not an option. Or will the Resolve option still work without any problems?
Any suggestions on how get rid of the locks / rollback the transaction other than restarting the database are greatly appreciated.