Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

abort tran on log full - efficacy

2 posts in General Discussion Last posting was on 2011-02-16 21:35:29.0Z
vtpcnk Posted on 2011-02-16 15:23:03.0Z
Sender: 3b96.4d5aa7d0.1804289383@sybase.com
From: vtpcnk
Newsgroups: sybase.public.ase.general
Subject: abort tran on log full - efficacy
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4d5bebd6.73c2.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 16 Feb 2011 07:23:03 -0800
X-Trace: forums-1-dub 1297869783 10.22.241.41 (16 Feb 2011 07:23:03 -0800)
X-Original-Trace: 16 Feb 2011 07:23:03 -0800, 10.22.241.41
Lines: 10
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29973
Article PK: 79200

few days back our audit archive database was bombarded by
purge/inserts from our sybsecurity db. apparently more than
10 simultaneous processes tried to do this (purge the
archive and insert fresh audit data from sybsecurity).
though 'abort tran on log full' was set on the audit archive
db, the log still went full. so due to heavy
volume/simultaneous processes, is it possible to get past
thru 'abort tran' and fill up the log?

appreciate the feedback.


Bret Halford Posted on 2011-02-16 21:35:29.0Z
From: Bret Halford <bret@sybase.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: abort tran on log full - efficacy
References: <4d5bebd6.73c2.1681692777@sybase.com>
In-Reply-To: <4d5bebd6.73c2.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4d5c4321$1@forums-1-dub>
Date: 16 Feb 2011 13:35:29 -0800
X-Trace: forums-1-dub 1297892129 10.22.241.152 (16 Feb 2011 13:35:29 -0800)
X-Original-Trace: 16 Feb 2011 13:35:29 -0800, vip152.sybase.com
Lines: 34
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29979
Article PK: 79207


On 2/16/2011 8:23 AM, vtpcnk wrote:
> few days back our audit archive database was bombarded by
> purge/inserts from our sybsecurity db. apparently more than
> 10 simultaneous processes tried to do this (purge the
> archive and insert fresh audit data from sybsecurity).
> though 'abort tran on log full' was set on the audit archive
> db, the log still went full. so due to heavy
> volume/simultaneous processes, is it possible to get past
> thru 'abort tran' and fill up the log?
>
> appreciate the feedback.

What exactly do you mean by full?

Just so full that new transactions aborted with 1105s?
[This would be normal for "abort tran on log full" -
new transactions will be aborted until space is freed in the log]

So full that DUMP TRAN itself aborts with an 1105?
[This is abnormal, the free space accounting for the log was
apparently a little off; the last chance threshold is meant to reserve
enough space for all the log records that DUMP tran itself
generates]

So overfull that transactions were getting 3475 errors
when aborting.
[this is even more abnormal, the free space accounting for the
log was even further off, the last chance threshold may not
even have been triggered]

The later too shouldn't happen, but are possible as a result
of something going wrong (bug, earlier use of bypass recovery,
dump tran with no_log, etc.).