Lieutenant Commander Lieutenant Commander
Lieutenant Commander
411 views

delete unwanted tables/data from the ucmdb database

Hi ,

our database folder size has gone upto 900gb , could anyone suggest what unwanted tables/data could be deleted from the database server to lower the DB folder size . As it is also impacting the performance .

 

 

8 Replies
Micro Focus Expert
Micro Focus Expert

Hello,

Your DBA can check if indeed the ucmdb DB file(s) use more space or DB logs, or the DB server just allocated too much(in this case you can shrink) . Anyway it is highly recommended to run a select on the DB to show all ucmdb tables and their disk space  .Display them in descending order.

There are cases when the ucmdb history tables might use most of the disk space(high discovery volume, discovery issues etc).  You can run jmx deleteUnboundHistoryTables to see if there are any unbounded  tables. If the sql mentioned above shows that there are many history tables with high disk usage then you can check if you can decrease the history months to save back setting and purge them.

Basically you should not delete any tables manually. If everything looks fine then you just have to allocate more disk space to the DB server .

 

Hope it helps.

Best Regards,

 

 

Micro Focus Expert
Micro Focus Expert

Maybe you can delete also the old Content Packs like described here https://community.microfocus.com/t5/Universal-Discovery-CMDB-User/Maintenance-tip-cleanup-of-the-old-Content-Packs/td-p/2776901
This won't save a lot of space but... maybe it's worth trying.


Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
Lieutenant Commander Lieutenant Commander
Lieutenant Commander

Hi ,
thanks for your input here .
we have deleted the unbound tables but no much difference .
but we can check on the history tables , sort them and purge .
0 Likes
Lieutenant Commander Lieutenant Commander
Lieutenant Commander

Hi John ,

thanks for the reply.
we have deleted the old CP but yeah like you said it wont make much of difference .
0 Likes
Micro Focus Expert
Micro Focus Expert

Hello Pankaj,

well I knew that it won't bring a significant difference as each CP zip file will have around 400MB and most probably you are looking in freeing up several GB. Still, it's a small effort and a maintenance task which doesn't hurt to implement it.
Can you get a list of the tables sorted by size? Maybe we can tell from the table names what occupies too much space. Maybe you have a lot of History tables due to flipping data syndrome.
Also, the log files usually tend to get big over time.


Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
0 Likes
Lieutenant Commander Lieutenant Commander
Lieutenant Commander

Hi john ,

I will get back with the list of tables .
about db logs , 900gb excludes logs files and they have been removed .
Thanks !
0 Likes
Micro Focus Expert
Micro Focus Expert

Hello,

You can provide the list of the top 10-20 tables that uses most disk space.

Note that a history month for all ucmdb CITs ,  with no customer classes, stores ~850-900 tables. If you have the default history settings then it will be 3 times this amount. Now the size of each table depends on the numbers of rows being store. Probably HDM_ROOT and HDM_ROOT_LINK can be big but also for CITs like composition. You have to check this. If there is an issue related to discovery then

  1. you can wait ~3 months so the tables will be purged
  2. or do it manually from jmx.But you will lose history . It depends on your requirements 

You did not mentioned your ucmdb version but if you have a version older than 2019.11 you should apply binary https://softwaresupport.softwaregrp.com/doc/KM03512489 

The side effect of the above defect is that for CIs identified with key attributes it inserts new history entries when the CIs were touched.

Hope it helps.

Best Regards,

 

 

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Dear,

Is the aging enabled ? if not , its recommened to enable aging, and it helps to an extend on this subject matter issue. and deleting data directy from DB isnt a good approach.

With Kind Regards,

Loghanath S

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.