Quantcast
Channel: SCN : All Content - PowerBuilder Developer Center
Viewing all articles
Browse latest Browse all 2935

Open Transactions with Autocommit = false in ASE

$
0
0

Hi Everyone,

 

We've just encountered a problem with our applications after upgrading our database to ASE 16.  I found some ancient posts and articles about transaction logs filling up with early versions of ASE and Powerbuilder when Autocommit is false because it keeps transactions open and marked as the oldest open transaction.  We've been using these apps for years with ASE 11.9, 12.5 and then 15 without any issue, but now it seems with ASE 16 any select statements sent from Powerbuilder keep an open transaction which is marked as the oldest open transaction in syslogshold.  They don't clear until a commit is issued, either after an update operation or when the application is closed.

 

Has anyone had this problem recently, or have any suggestions for fixing it?  I know I could set Autocommit to true and do explicit transaction handling, but that would be quite a big change for all of our applications.  I am thinking of adding a commit in the application idle event, but I'm not 100% sure whether that is a good or bad idea. Any suggestions would be welcome.

 

The applications are written in Powerbuilder 10.2 and 10.5

 

Thanks.


Viewing all articles
Browse latest Browse all 2935

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>