Results 1 to 4 of 4
  1. #1
    Join Date
    Feb 2002
    Location
    Hamilton
    Posts
    149

    Unanswered: log directories on aix

    Currently we have the db2diag.log file going to the /home/instance/sqllib/db2dump path. Can we change that to another location, ie /var/???, so that it doesn't fill up the home filesystem? I believe you do it through updated the db cfg file but not sure. Any help would be great

    Mark

  2. #2
    Join Date
    Apr 2002
    Posts
    13
    Hello Mark,

    Use the following command to change the location of the diag log file:

    db2 update dbm cfg using DIAGPATH log_path_name

    where log_path_name is the name of the dir where the log should be written to.
    You must shop and start the instance to take effect the change.

    Thanks
    Anil.


  3. #3
    Join Date
    Feb 2002
    Location
    Hamilton
    Posts
    149
    so the command should look like this:

    db2 update dbm cfg using DIAGPATH /var/db2/ ????


    thanks

    Mark

  4. #4
    Join Date
    Oct 2001
    Posts
    68
    dbfocris is correct. Run the command "db2 get dbm cfg" first and see what your DB2DIAG setting is. i.e:

    Ohare:wpsulliv: db2 get dbm cfg

    Database Manager Configuration

    Node type = Database Server with local and remote clients

    Database manager configuration release level = 0x0900

    CPU speed (millisec/instruction) (CPUSPEED) = 1.149371e-06
    ...

    Diagnostic error capture level (DIAGLEVEL) = 3
    Diagnostic data directory path (DIAGPATH) = /home/db2inst1/sqllib/db2dump
    ...
    etc.. etc..

    Now you can see that DIAGPATH does not have a closing "/" as in your last question. So you can now set the new db2diag.log target filesystem to whatever you want. My one word of advice is not to use the /var filesystem. On AIX this is usually very very small and one of the first JFS filesystems to get extended by the SAs. Also "vi" and other utilties seem to like "/var/tmp" more so than "/tmp" in a base OS installation.

    We have defined new volume groups and new file systems across multiple controllers and disks to limit DB2 I/O as mush as possible, even for db2diag which is infrequently updated depending on the setting. Depending on your setup, you might want to rethink "/var".

    Cheers,
    WP

Posting Permissions

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