dbTalk Databases Forums  

Re: Transaction logging question (s)

comp.databases.btrieve comp.databases.btrieve


Discuss Re: Transaction logging question (s) in the comp.databases.btrieve forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Wayne
 
Posts: n/a

Default Re: Transaction logging question (s) - 09-07-2006 , 05:14 PM






Hi Karl,

When the Transactional Engine is stopped, it "flushes" all log files
that contain committed transactions.

So, here are a few reasons why some of your customers have many
existing log files (not in any particular order), some good, some bad:

1. They rarely have any reason to restart their server or Pervasive
Engines. In this case, you may want to suggest that they schedule a
restart occasionally. If they already restart what we might reasonably
consider fairly often, then what they do with your software is
generating lots of transactions and you should consider logging to a
separate drive or a separate system from the database server. This
would also improve performance on the database server.
2. They have lots of system failures of some nature during
transactions, which is the opposite of #1.
3. There might be a, well, bug, in the application that, for example,
allows a long time to elapse between a Begin Transaction and an End
Transaction. Or allows the user to exit from the procedure or the
application without forcing an End Transaction. An example that I have
actually seen is to issue a Begin Transaction upon entry to a some
interactive procedure like Customer Maintenance or Order Entry and not
issue an End Transaction until the user is finished. This keeps the
open files in transaction state way too long for safety, as it gives
the user too many opportunities to break the program or a system
failure to occur. This function might be something that some of your
customers use a lot and others don't.

I can't think of anything else right now, but you get the idea, and I'm
sure somebody else can think of a few more.

Hope this helps.

Wayne Freeman
Analytica Business Systems
A Pervasive Software Premier Partner
www.analyticabiz.com
Karl A. Sørensen ha scritto:

Quote:
We have several customers running Psql 9 with transaction logging turned on.
The strange thing is that at some customer sites, the transaction logs fills
up until they run out of disk space. On other sites (some with a lot moredb
intensive system), the size of the transaction log directory i somehow kept
at a reasonable size automatically.

Question:
What causes this, and what is the remedy ?

TIA
Karl


Reply With Quote
  #2  
Old   
Leonard
 
Posts: n/a

Default Re: Transaction logging question (s) - 09-08-2006 , 08:57 AM






There is also the possibility that the database engine does not have
OS level rights to delete files from the transaction log directory.

As to #3 listed below there was one in PSQL 9.0 and 9.10 where the
logs could accumulate. It is fixed in PSQL 9.50 so they may want to
consider patching up if possible.

Leonard

On 7 Sep 2006 15:14:20 -0700, "Wayne" <sales (AT) analyticabiz (DOT) com> wrote:

Quote:
Hi Karl,

When the Transactional Engine is stopped, it "flushes" all log files
that contain committed transactions.

So, here are a few reasons why some of your customers have many
existing log files (not in any particular order), some good, some bad:

1. They rarely have any reason to restart their server or Pervasive
Engines. In this case, you may want to suggest that they schedule a
restart occasionally. If they already restart what we might reasonably
consider fairly often, then what they do with your software is
generating lots of transactions and you should consider logging to a
separate drive or a separate system from the database server. This
would also improve performance on the database server.
2. They have lots of system failures of some nature during
transactions, which is the opposite of #1.
3. There might be a, well, bug, in the application that, for example,
allows a long time to elapse between a Begin Transaction and an End
Transaction. Or allows the user to exit from the procedure or the
application without forcing an End Transaction. An example that I have
actually seen is to issue a Begin Transaction upon entry to a some
interactive procedure like Customer Maintenance or Order Entry and not
issue an End Transaction until the user is finished. This keeps the
open files in transaction state way too long for safety, as it gives
the user too many opportunities to break the program or a system
failure to occur. This function might be something that some of your
customers use a lot and others don't.

I can't think of anything else right now, but you get the idea, and I'm
sure somebody else can think of a few more.

Hope this helps.

Wayne Freeman
Analytica Business Systems
A Pervasive Software Premier Partner
www.analyticabiz.com
Karl A. Sørensen ha scritto:

We have several customers running Psql 9 with transaction logging turned on.
The strange thing is that at some customer sites, the transaction logs fills
up until they run out of disk space. On other sites (some with a lot more db
intensive system), the size of the transaction log directory i somehow kept
at a reasonable size automatically.

Question:
What causes this, and what is the remedy ?

TIA
Karl


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.