database parameter to back out a transaction after a period of time

[guardian]

Hello,

We've introduced some new processes to our system that give us some potential BI growth vulnerabilities.

We have a few bad transactions that remain active if the user is sitting at certain prompts. (Yes, I know these need to be fixed). We've now added some batch processes that create/delete a bunch of records. My concern is that one of these batch processes will be run when one of these bad "UI" transactions is active and therefore cause the BI to grow too large.

We've got 2 fixed BI extents and 1 variable BI extent. The BI directory is 3 gb. I'm worried about hitting that 3 gb limit. We are going to implement bithold and bistall to address that issue.

Now to my question: is there a database parameter that can be set to back out a transaction after a period of time? The reason I ask is that I'm the only one in our department that is currently able to identify these poor UI transactions. If I'm out of the office, it would be nice if those transactions resolved themselves.

I know, I know - fix the code. We've got a resource issues there as well...

Thanks for our time
Patrick Maloney

 

[MaximMonin]

If you have 10.1B or later (64bit) db option enablelargefiles let you create bi files more than 2GB. So there isnt any risk to hit 3Gb limit.

Second option is to write background process that disconnects those users and let it to create/delete records w/o "bad UI transaction".

 

[tamhas]

There is no global parameter ... and it would be dangerous if there were. There are certainly coding techniques, especially if you have 10.2B, but ... that's coding ... and if you are doing coding the right thing to do is to fix the program so that there is no open transaction at a user prompt.