RQM: When doing DB2 incremental Backup, why does db2pd show 'dirty' even when the server had no activity at all?
![]()
George Harada (32●3●13)
| asked Feb 09 '17, 5:14 a.m.
edited Feb 13 '17, 12:05 p.m. by Muralidhar Rajagopal (101●1●4) The customer is using incremental backup for CLM.
|
2 answers
![]()
I am not an expert on DB2 management, but here are some thoughts. I believe when you are reporting on a table space being dirty, it is asking if there are any pages at all associated with the table space that are dirty. This document talks about dirty pages: https://www.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.admin.perf.doc/doc/c0005393.html
There is a command you can use to see how many dirty pages there are:
db2pd -db <yourdb> -dirtypages summary
So for example on my test this shows
Dirty pages % : 135 / 1000 (13.50% dirty)
You can leave off the summary to see all the dirty pages:
db2pd -db <yourdb> -dirtypages
On my DB the primary table space for QM artifacts (CONTENTTS) is id 3.
The second column in the non-summary dirty pages output is the table space ID.
I ran this command to ask how many of the dirty pages are from that tablespace:
db2pd -db <yourdb> -dirtypages | grep "^\d\s3" | wc
and the answer was 66 (about half of the 135 dirty pages).
I disconnected all clients from my db, stopped it and started it, and then checked the dirty pages. There were 2.
Comments Hi Frank,
|
![]() I got an answer from one of the RTC developers and thought I'd share, as below:
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.