Results 1 to 4 of 4

Thread: LOgs full

  1. #1
    Join Date
    Oct 2008
    Posts
    82

    Cool Unanswered: LOgs full

    Can any one plz help me ... how to check why the logs are getting full so frequently


    VERsion : 9.7
    fp 3
    os : AIX
    Partitioned environment

  2. #2
    Join Date
    Apr 2006
    Location
    Belgium
    Posts
    2,514
    Provided Answers: 11
    do you get logfull sqlcode
    maybe long running transactions.. mass delete/update...
    Best Regards, Guy Przytula
    Database Software Consultant
    Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
    Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
    DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
    Information Server Datastage Certified
    http://www.infocura.be

  3. #3
    Join Date
    Nov 2010
    Posts
    14
    In case of "log full" situation, you can find the application handle who is holding the active log from db2diag.log

    Code:
    db2diag -g message:="The active log is full"

    Also, you can use sysibmadm.snapappl and sysibmadm.snapappl_info admin views for getting info on who is hogging the log space.
    /* SK Chandra */

  4. #4
    Join Date
    Apr 2008
    Posts
    39
    This is case of applcaition performanve tunning with db. Please check what application are are running against the db at that time and Need to eleminate highly log space used application. Then issue frequent "COMMIT" in that activity. For immidiate relief you may want to add some more logs.

    Thanks
    Naval K

Posting Permissions

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