R
Rohan
Guest
Red Hat Enterprise Linux 6.7, Openedge 11.3.2. (24x7) I have a long running transaction (over 24hours) which doesn't respond to usual proshut command. This is a fairly busy production db. The user no longer has an active Linux login, but does have a _progres process active. They also have various exclusive and shared locks. In an attempt to disconnect the user, I tried (as the db owner account) "proshut dbname -C disconnect 269". Output is normal: "User 269 disconnect initiated. (6796)" . There is no entry in the db.lg to confirm this. I also tried Dimtri Leven's disconn-long-trans.p (thanks Dmitri), but without effect. The BI file is usually up to around 1GB for this db, but currently over 8GB and growing. -bithold is 19GB. BI dedicated filesystem size is 40GB. -bistall = yes. Interestingly, in promon the user appears in "1.User Control" list, but not in the list of users to disconnect in menu option "8.Shut Down Database">"1.Disconnect a User". Any suggestions on how to end this transaction, while remaining up and running?
Continue reading...
Continue reading...