Where is db2 error log

Skip to content. Skip to navigation. If the file name is omitted, the db2diag. Word search. Invert word match. Displays the history of logged messages for the specified time interval. This option can be specified with the following options: historyPeriod Specifies that logged messages are displayed starting from the most recent logged record, for the duration specified by historyPeriod.

The historyPeriod option is specified using the following format: Number timeUnit , where Number is the number of time units and timeUnit indicates the type of time unit: M month , d day , h hour , m minute , and s second. The default value for Number is 30, and for timeUnit is m. Kiran Kumar Posted September 2, 0 Comments. Hi Instead of newlogpath use logtarget in restore. Good Morning guys, It was my mistake instead specifying logtarget parameter I gave newlogpath.

Register or Login. Welcome back! Reset Your Password We'll send an email with a link to reset your password. Stay ahead! Get the latest news, expert insights and market research, tailored to your interests. Sign in with email Enter the email address associated with your account.

You auth link is expired or incorrect, please try again. Because you can change the log path location, the logs needed for roll-forward recovery may exist in different directories or on different devices. You can change this configuration parameter during the roll-forward process to allow you to access logs in multiple locations. The change to the value of newlogpath will not be applied until the database is in a consistent state.

Note: The database manager writes to transaction logs one at a time. The total size of transactions that can be active is limited by the database configuration parameters:. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 11 years, 5 months ago. Active 5 years, 1 month ago. In my opinion, it is still important to be able to read a text db2diag. There is a wealth of data in there.

Finally, a lot of error messages or other data are at the end, in 16 or after. Those are merely the highlights — I highly recommend reading the IBM DB2 Knowledge Center page on it to really understand reading and therefore querying entries in the db2diagnostic log.

This is what the results looked like:. I should really force voters to login so I could see how many of the responses were just Ian messing with me. A larger number than I expected admitted to using it. It is up to you whether or not you use the DB2 administration notification log. Just know that there is often more information in db2diag. Never forget your OS level logging when investigating db2 problems. A disk issue, for example, can explain a lot of oddness that may be harder to explain just from database level error logging.

This entry has focused on the DB2 diagnostic log and the DB2 adminstration notification log. But there are other things that land in this directory, including:. They should be cleaned up on a regular basis, though, too, to prevent them from filling up the disk. I usually keep them for a minimum of 30 days. Hi Ember, thank you for your blog.