Results 1 to 7 of 7
  1. #1
    Join Date
    Jan 2004
    Location
    UK
    Posts
    52

    Unanswered: ADM10501W Health indicator "Log Filesystem Utilization" ("db.log_fs_util")

    Hi friends,

    I am getting following warning in my Event Viewer. Is it of a serious kind which might create problem in future. What does this mean and how to take care of this. Thanks.

    2004-07-15-10.23.09.221000 InstanceB2 Node:000
    PID:1816(db2syscs.exe) TID:1876 Appid:none
    Health Monitor HealthIndicator::update Probe:500

    ADM10501W Health indicator "Log Filesystem Utilization" ("db.log_fs_util")
    breached the "upper" warning threshold of "50" with value "56" on "database"
    "DB2.FMS_OW3T". Calculation: "((os.fs_used/os.fs_total)*100);" =
    "((22696579072/40048852992)*100)" = "56". History (Timestamp, Value, Formula):
    "()"

  2. #2
    Join Date
    Feb 2004
    Location
    Copenhagen
    Posts
    220

    Arrow Yes

    I'm guessing you are using Archive logging (logretain=yes)

    Thus all your changes are written to disk.

    If you don't free diskspace by pruning your log, eventually your
    log file system will fill up, and you won't be permitted to run
    transactions against the database.

    BOW
    Kristian K. Hansen
    Project Supervisor
    National Board of Health

  3. #3
    Join Date
    Jan 2004
    Location
    UK
    Posts
    52
    But, I have got this in my "db cfg"

    Log retain for recovery enabled (LOGRETAIN) = OFF
    User exit for logging enabled (USEREXIT) = OFF

    But, here I would like to tell u something. Some days back I created a sample database and updated the LOGRETAIN = yes and USEREXIT = yes for the sample database. However, I dropped the database after taking a online backup and again restoring it. I did this for testing purpose only.

    Thanks.

  4. #4
    Join Date
    Feb 2004
    Location
    Copenhagen
    Posts
    220

    Arrow Circular logging

    If you're using circular logging
    the logfiles will become ready for resuse
    as soon as you commit your transactions.

    If you, once in a while, get a warning that you
    are using just above 50% of the total log -
    you are in great shape.
    Kristian K. Hansen
    Project Supervisor
    National Board of Health

  5. #5
    Join Date
    Jan 2004
    Location
    UK
    Posts
    52
    Actually previously I was getting the Warning again and again. So.. I changed the LOGFILSZ from 1MB to 2MB and LOGSECOND from 1 to 5.

    Previous Status
    ----------------
    Log file size (4KB) (LOGFILSIZ) = 1024
    Number of primary log files (LOGPRIMARY) = 3
    Number of secondary log files (LOGSECOND) = 1

    Current Status
    --------------
    Log file size (4KB) (LOGFILSIZ) = 2048
    Number of primary log files (LOGPRIMARY) = 3
    Number of secondary log files (LOGSECOND) = 5

    How to know whether it is circular logging?

  6. #6
    Join Date
    Feb 2004
    Location
    Copenhagen
    Posts
    220

    Arrow

    If you have specified

    (LOGRETAIN) = OFF
    (USEREXIT) = OFF

    You are, per se, using circular logging

    I would suggest that you increased the number
    og primary log files instead, and if you
    have many large transactions - the size

    HTH
    Kristian K. Hansen
    Project Supervisor
    National Board of Health

  7. #7
    Join Date
    Jan 2004
    Location
    UK
    Posts
    52
    Thanks a lot.

Posting Permissions

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