Page 1 of 2 12 LastLast
Results 1 to 15 of 16
  1. #1
    Join Date
    Mar 2008
    Posts
    11

    Unanswered: How to resolve "Transaction log is full" issue

    Hi,

    I try to load 500,000 records in to our DB2 UDB Dev region(Ver 8.1) using load client utility. But i get the following error msg while doing it :

    "SQL0964C The transaction log for the database is full. SQLSTATE=57011"

    Can anyone help me in resolving this issue. Appreciate if necessary commands are also sent

    Thanks,
    Arunvijay

  2. #2
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    The LOAD command should not be using the transaction log. What is the command you are using? Also what OS is the DB2 server on?

    Andy

  3. #3
    Join Date
    Mar 2008
    Posts
    11
    i use the following command :

    db2 connect to dezwt01s user db2inst using test
    db2 load client from /data/db2/db2inst/Daily_Trx_1 of del modified by delprioritychar coldel~ usedefaults MESSAGES /data/db2/db2inst/Daily_trx1.log insert into db2dba.Daily_trx_sale_cmsn_fact_1;
    db2 terminate ;

    it is Unix OS

  4. #4
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    You can add the "SAVECOUNT n" clause that might fix what you are doing.

    Andy

  5. #5
    Join Date
    Jan 2008
    Posts
    45
    If it is a log issue increase primary or secondary logs or set LOGSECOND to -1 to enable infinite logging

  6. #6
    Join Date
    Jun 2006
    Posts
    471
    add nonrecoverable to end of the load statement = no logging...
    Best Regards, Guy Przytula
    DB2 UDB LUW certified V6/7/8

  7. #7
    Join Date
    Mar 2008
    Posts
    11
    it is working fine now..thanks all for ur replies

  8. #8
    Join Date
    Dec 2010
    Posts
    2

    Just one more question

    Can you please let us know which of the proposed solutions did help to solve the problem, thanks Piet

  9. #9
    Join Date
    Oct 2007
    Posts
    246
    piet
    nonrecoveable at the end would have solved the problem,
    przytula,
    incase the table was already having the data and was having constraint on it even using
    nonrecovable options will load insert it deletes and use the log for dat, please correct me on this i may be wrong.
    arun
    was dat the issue ??

  10. #10
    Join Date
    Dec 2010
    Posts
    2

    Thanks a lot Mathew-Paul

    I will go for the non recoverable option, cheers, Piet

  11. #11
    Join Date
    Oct 2007
    Posts
    246
    Quote Originally Posted by guyprzytula View Post
    add nonrecoverable to end of the load statement = no logging...
    hello sir,

    as u suggested nonrecoverable = no logging, incase we don't u this options "nonrecoverable" does it writes to log file while load ?? i believe it won't coz it ask for backup. please correct
    Regds
    Paul

  12. #12
    Join Date
    Dec 2010
    Posts
    123
    what is the command used?

  13. #13
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    Quote Originally Posted by Mathew_paul View Post
    hello sir,

    as u suggested nonrecoverable = no logging, incase we don't u this options "nonrecoverable" does it writes to log file while load ?? i believe it won't coz it ask for backup. please correct
    Regds
    Paul

    Take a look at http://www.dbforums.com/db2/1661713-load-command.html

  14. #14
    Join Date
    Oct 2007
    Posts
    246
    hi bella,
    u mean load without nonrecoverable option does log's minimal amt of logging is done.
    regds
    Paul

  15. #15
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    Load is a minimal logging utility (in case of all load options - copy yes / copy no / nonrecoverable). The delete phase, if performed, is the only time when load can produce a substantial number of log records.

Posting Permissions

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