APMDB more useful commands
Article ID: 195573
Updated On:
Products
Issue/Introduction
Growth of the APM database can lead to performance issues in Team Center but it can even be as severe as to prevent the Enterprise Manager from starting
Here are some considerations that have come out of investigations where there has been large database growth
Environment
Release : 10.7.0
Component : Introscope
Resolution
Run these commands to see if there are are any obsolete entries in the database that should have been removed by pruning.
SELECT COUNT(1) FROM appmap_model_vertices m
WHERE NOT EXISTS (
SELECT 1 FROM appmap_id_mappings id
JOIN appmap_vertices v ON v.vertex_id = id.vertex_id
WHERE id.external_id = m.external_id
)
SELECT COUNT(1) FROM appmap_id_mappings m
WHERE m.vertex_id > 0 AND m.type = 'V'
AND NOT EXISTS (SELECT 1 FROM appmap_vertices v WHERE v.vertex_id = m.vertex_id)
If the value returned is significantly above zero, check if pruning is enabled and check logs for any errors related to pruning.
If using APM 10.7 make sure you are using the latest hotfix to address pruning issues.
Maximum recommendations on row counts in tables are:
1 million for appmap_vertices
10 million for appmap_attribs
Use the following queries to estimate growth of rows per day
select date_trunc('day', start_time), count(*) from appmap_vertices group by 1 order by 1;
select date_trunc('day', end_time), count(*) from appmap_vertices group by 1 order by 1;
select date_trunc('day', start_time), count(*) from appmap_attribs group by 1 order by 1;
select date_trunc('day', end_time), count(*) from appmap_attribs group by 1 order by 1;
- Calculate an average for the start_time and end_time results.
- Subtract end_time from start_time, which gives an estimate of table growth per day.
- Use the following properties to set appropriate limits for data retention
Additional Information
More details on the data retention configuration properties
Feedback
