Db2 CCM and JTS container sizes are growing expoenentially post data restore
I have restored the data from production db2 database to test db2 database for JTS and CCM both. In production environment the data backup image size is 129gb and CCM container size (jazzdata) is 169 gb (for last 8 years). But when I restore this to test database I see that data backup image size is 150fb and the ccm container size(jazzdata) is 321 gb within just 3 days. I dont know what is causing this issue. Same way JTS container size is test setup is larger than the production. But in ideal case as the test is replica of production it should be same.
Also in test setup I dont have db2 data warehouse configured. But production has separate Db2 data warehouse configured. Is this because data warehouse is missing in test setup.
|
Accepted answer
No problem.
With all Db2 applications, this type of maintenance is ongoing, and therefore should be looks at on a regular basis. This is dependent on the amount of work that is done in those applications.
There may be more activity in test than production? I'm assuming (and I know I should never do that) that your test and production systems are configured the same.
Not sure what you mean by prune logs in Db2. What logs are you referring to?
Transaction logs, database history log?
Not sure that you would prune transaction logs.
https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.admin.cmd.doc/doc/r0001992.html To manage transaction log files that would be dependent on what type of logging you are adopting for your Db2 databases.
Going back to your original question, you need to determine what is actually taking up the space in your database. Maybe there is something different happening now with the restore? Perhaps opening a case with Db2 support will help you explain the differences between prod and test.
https://www.ibm.com/mysupport/ and open a case with them. They should be able to help determine root cause.
Hope this helps.
Kind regards,
Anthony
aastha khatri selected this answer as the correct answer
Comments
Thanks Anthony!
Yes, I have raised an access request to open a case for Db2 support.
The difference between test and production is production is bare metal server and test is a VM. I have ensured that the configuration for both is same and all the Db2 parameters are same.
I was talking about the transaction log. We use below steps to delete the unwanted logs.
1.db2 get db config | grep "First active log file"
2. Then prune and delete all the logs before the file found in step-1
|
One other answer
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.