Results 1 to 3 of 3
  1. #1
    Join Date
    Mar 2004
    Posts
    2

    Angry Unanswered: Full transaction log

    Hi

    I have a problem with a full transaction log in ASE 12.5. When I found out that the transaction log was full I tried to alter the db.

    alter db log on ....

    That didn´t work because the db was marked as suspect. I followed the tips that I found on Sybase homepages "How to reset a database's "suspect" status. I think that worked fine, but when I restart the server I get this in the errorlog.

    00:00000:00001:2004/03/18 10:42:54.01 server Recovering database 'BOWDB'.
    00:00000:00001:2004/03/18 10:42:54.48 server Redo pass of recovery has processed 13 committed and 0 aborted transactions.
    00:00000:00001:2004/03/18 10:42:54.48 server Error: 631, Severity: 21, State: 2
    00:00000:00001:2004/03/18 10:42:54.48 server The length of 16 passed to delete row routine for the row at offset 1200 is incorrect on the following page: Page pointer = 0x21806000, pageno = 692330, status = 0x2, objectid = 1166627199, indexid = 4, level = 0. The expected row length is 16. The offset should be no greater than 1040.
    00:00000:00001:2004/03/18 10:42:54.48 server Error: 3414, Severity: 21, State: 1
    00:00000:00001:2004/03/18 10:42:54.48 server Database 'BOWDB' (dbid 4): Recovery failed. Check the SQL Server errorlog for further information as to the cause.

    What can I do? All I want to do is to increase the size of the db. Why is it messing with me?

    /BOW

  2. #2
    Join Date
    Jun 2003
    Posts
    140

    Re: Full transaction log

    First of all you should find out why db was marked as suspect ,
    in most cases, this error occurs when index or data page is corrupted,
    try to find out why it was happend from error log . See ASE
    troubleshooting guide for exact explaination of error no 631 they have very clearly mentioned what are all the things to take care when this error occurs

  3. #3
    Join Date
    Mar 2004
    Posts
    2

    Re: Full transaction log

    I don´t know how to find that out. This is the first error that occured.

    00:00000:00019:2004/03/17 11:24:43.81 server Space available in the log
    segment has fallen critically low in database 'BOWDB'. All future
    modifications to this database will be suspended until the log is
    successfully dumped and space becomes available.
    00:00000:00020:2004/03/17 11:24:43.85 server Error: 2812, Severity: 16,
    State: 5
    00:00000:00020:2004/03/17 11:24:43.85 server Stored procedure
    'sp_thresholdaction' not found. Specify owner.objectname or use sp_help to
    check whether the object exists (sp_help may produce lots of output).
    00:00000:00008:2004/03/17 11:24:44.53 server 1 task(s) are sleeping waiting
    for space to become available in the log segment for database BOWDB.
    00:00000:00008:2004/03/17 11:25:44.59 server 1 task(s) are sleeping waiting
    for space to become available in the log segment for database BOWDB.
    00:00000:00008:2004/03/17 11:26:44.53 server 1 task(s) are sleeping waiting
    for space to become available in the log segment for database BOWDB.
    00:00000:00008:2004/03/17 11:27:44.56 server 1 task(s) are sleeping waiting
    for space to become available in the log segment for database BOWDB.

    /BOW

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •