Results 1 to 5 of 5
  1. #1
    Join Date
    Feb 2012
    Posts
    8

    Unanswered: Transaction Log file is full error

    Hi,

    I m trying to update a table in DB2 database. I m getting below error.

    DB21034E The command was processed as an SQL statement because it was not a
    valid Command Line Processor command. During SQL processing it returned:
    SQL0964C The transaction log for the database is full. SQLSTATE=57011

    SQL0964C The transaction log for the database is full.

    Can anyone help me in this issue??

  2. #2
    Join Date
    Aug 2008
    Posts
    147
    One way is to increase the amount of secondary log files.

    db2 update db cfg for MY_DB_NAME using LOGSECOND 100

    The reason this error is occurring is that the objects loaded into the transaction which is causing the the transaction logs to overfill.
    ---------------------------------
    www.sqlserver-dba.com
    www.dba-db2.com

  3. #3
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    Aside from increasing the logs, you can make sure that your transactions commit and/or commit more frequently.
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

  4. #4
    Join Date
    Feb 2012
    Posts
    8
    Quote Originally Posted by stolze View Post
    Aside from increasing the logs, you can make sure that your transactions commit and/or commit more frequently.
    Stolze,
    Thanks for your reply....
    While executing update query, how do i commit my transaction

  5. #5
    Join Date
    Aug 2008
    Posts
    147
    For example, you can run your code on smaller batches. This tactic allows the COMMIT to occur more frequently.
    ---------------------------------
    www.sqlserver-dba.com
    www.dba-db2.com

Posting Permissions

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