Results 1 to 4 of 4
  1. #1
    Join Date
    Feb 2004
    Posts
    20

    Unanswered: "The transaction log in database mydatabase is almost full"

    Hi,

    I have a Sybase 11.9 DB running in a development environment and have encountered the following error whe trying to drop a table (get variations in this error when doing pretty much anything):

    The transaction log in database production is almost full. Your transaction is
    being suspended until space is made available in the log.

    From reading manuals etc, I gather that the normal procedure is to dump the
    tranasction log. Unfortunataly I get the following when attempting this:

    -------------%<-----------------
    1> dump transaction production to "/home/dab/tmp/sybtrandump"
    2> go
    Msg 4225, Level 16, State 1:
    Line 1:
    This database has not been dumped since it was created or upgraded. You must
    perform a dump database before you can dump its transaction log.
    -------------%<-----------------

    And when I attempt to dump the database in question I get:

    -------------%<-----------------
    1> dump database production to "/home/dab/tmp/sybdump"
    2> go
    Msg 7205, Level 17, State 2:
    Line 1:
    Can't open a connection to site 'SYB_BACKUP'. See the error log file in the SQL
    Server boot directory.
    Msg 7205, Level 18, State 3:
    Line 1:
    Can't open a connection to site 'SYB_BACKUP'. See the error log file in the SQL
    Server boot directory.
    -------------%<-----------------

    I understand this is because I don't have a backup server running. Is there someway of dumping without setting up a backup server? I'm not actually to
    concerned about the data in this database. I just want it back into a usable state so tha I can insert some new data into it.

    Thanks in advance.

    Daniel.

  2. #2
    Join Date
    Jan 2004
    Posts
    32
    Use one of the following commands to truncate the transaction log (these commands don’t need backup server running)

    To truncate the log without making a backup copy:
    dump tran[saction] database_name with truncate_only

    To truncate a log that is filled to capacity. Use only as a last resort:
    dump tran[saction] database_name with no_log

  3. #3
    Join Date
    Feb 2004
    Posts
    20
    Thanks. The first suggestion worked a treat. Excellent.

  4. #4
    Join Date
    Nov 2002
    Posts
    207
    You should also configure SYB_BACKUP for future backups.

Posting Permissions

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