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.

Transaction Log full error

2 posts in ,  AdministrationGeneral Discussion Internet Last posting was on 2001-05-01 18:43:22.0Z
Raghavendra Kulkarni Posted on 2001-05-01 07:24:24.0Z
From: "Raghavendra Kulkarni" <raghu@antispam.com>
Subject: Transaction Log full error
Date: Tue, 1 May 2001 12:54:24 +0530
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Message-ID: <sGV5Eom0AHA.256@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.administration,sybase.public.sqlserver.general,sybase.public.sqlserver.internet
NNTP-Posting-Host: 216.160.29.41
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.administration:513 sybase.public.sqlserver.general:320 sybase.public.sqlserver.internet:175
Article PK: 1062758

Hi all

Every once in a couple of weeks when we run our application we seem to be
getting a transaction log full error. In fact we have ample space allocated
for the log. For some reason the database seems to freeze up as the
allocated tran log area gets gobbled up. It ultimately reaches within a
couple of mb of the allocated space and will give this error.

Is it some process within the application that is causing this to happen?
Are there are any processes to look for within Sybase that may provide
pointers as to what may be happening. There is no consistency as to why it
happens. At times everything will work great till the db gives way thus.

We are trying to port a C++ app to the web. The error occurs on both the web
app and the C++ app. There are stored procedures that are inherited from the
days of the earlier legacy applications that are used by the new web app.

Any pointers are as usual greatly appreciated.

Raghu


Benny Pei Posted on 2001-05-01 18:43:22.0Z
Message-ID: <3AEF03CA.AD207FB3@yahoo.com.NOSPAM>
Date: Tue, 01 May 2001 14:43:22 -0400
From: Benny Pei <bplegend@yahoo.com.NOSPAM>
X-Mailer: Mozilla 4.61 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Transaction Log full error
References: <sGV5Eom0AHA.256@forums.sybase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.administration,sybase.public.sqlserver.general,sybase.public.sqlserver.internet
Lines: 48
NNTP-Posting-Host: wasteland.nyc.office.juno.com 64.136.0.78
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.administration:512 sybase.public.sqlserver.general:319 sybase.public.sqlserver.internet:174
Article PK: 1062789

Several things:

1. This query shows you all the open transactions on your server order by
starttime.

select l.spid,
db_name(l.dbid) "db name",
name "proc name",
hostname,
starttime
from master..syslogshold l, master..sysprocesses p
where l.spid=p.spid
order by starttime

2. Perhaps there is change in behavior in your application which generate extra
transaction log. You can start doing more frequent transaction log dump if this
is the case. It occured to us last time when we had the transaction log filled
up several days in a row and developers never admitted that they changed
anything. After a few days of poking around the server and logs, it tunred out
to be a bug in one of the stored procedures.

3. dbadevil.com has a log analyzer tool to look what is in the transaction log.

Hope it helps.

benny

Raghavendra Kulkarni wrote:

> Hi all
>
> Every once in a couple of weeks when we run our application we seem to be
> getting a transaction log full error. In fact we have ample space allocated
> for the log. For some reason the database seems to freeze up as the
> allocated tran log area gets gobbled up. It ultimately reaches within a
> couple of mb of the allocated space and will give this error.
>
> Is it some process within the application that is causing this to happen?
> Are there are any processes to look for within Sybase that may provide
> pointers as to what may be happening. There is no consistency as to why it
> happens. At times everything will work great till the db gives way thus.
>
> We are trying to port a C++ app to the web. The error occurs on both the web
> app and the C++ app. There are stored procedures that are inherited from the
> days of the earlier legacy applications that are used by the new web app.
>
> Any pointers are as usual greatly appreciated.
>
> Raghu