Huge DB2 database size normal?
Hi everyone,
This week I updated all applications to 6.0.5 since we had problems with DM and we wanted to try out DM 6.0.5 and the new Model Manager. For now only a few employees were gathering some requirements and testing if everything works as expected, so the database should still be pretty small.
--- /home/db2inst1/db2inst1/NODE0000 ------------------------------------------------------------------------- /.. 7.2 GiB [##########] /SQL00004
Database 1 entry: Database name = RELM Local database directory = /home/db2inst1
All databases have a huge jazzdata file which makes up for the majority of the size of the directory. “jazzdata” is also configured to be the “Data tablespace container” in our applications, so it seems like the Jazz server is storing a lot of data for some reason. On the other hand, If I make a snapshot of the whole system (it’s a VM) it can be compressed down to around 2,5 GB, so I guess the database is pretty empty despite its huge size? We’re using DB2 11.1.2 fp2.
How can I figure out why the database is so huge and if the size is reasonable needed or just huge because of some faulty behavior? And if the size is only so huge by some faulty behavior, how could I fix that?
Let me know if you need some additional information.
Any help is much appreciated.
|
One answer
If I recall, there is are entries in the conf/APP/teamserver.properties that indicate an initial number of pages for the storage for one of the tablespaces:
|
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.
Comments
I am not a DBA and don't know usual sizes, however 2GB is no size at all for a database today. Note, my phone has 64GB storage already just as a guidance what big or small size is.
I think the database also sets space up for organization etc. It is a database and stores data to enhance access speed and not to reduce size.
I think I remember that some host guys complained that the initial DB size is already 2 GB, and that is just as it is.
Sure, 2GB is not much nowadays, but if it the databases alone add up to 42,3GB with only a few test artifacts in each application, I'm a bit concerned about the future size.
Having worked more with (also complex) webapplications and MySQL and the like everything more than a few megabytes for the database of a basically not yet used application seems huge to me.
Anyway, thanks for your answer, I'll try to keep an eye on the size of the databases.