Environment
Business Service Manager 4.0
Business Service Manager 4.5
Situation
There are a few steps that need to be followed to disable version tracking. Disabling the checkbox in configstore GUI alone doesn't disable version tracking.
The issue is that the triggers that are added have no way of getting dropped in this case so data will continue to collect in the configstore with no way to purge.
The issue is that the triggers that are added have no way of getting dropped in this case so data will continue to collect in the configstore with no way to purge.
Resolution
To drop version history tracking:
First - best practices
-backup the configstore database
-export the configstore for review later (to compare size before and after)
-have a plan of execution and a roll back plan ready if needed.
-shut down MO
-in moscfg (default configstore) set the version transaction history flag to false
drop the triggers:
DROP TRIGGER CFG_ENTRY
DROP TRIGGER CFG_ATTRIBUTE.
drop the tables:
DROP TABLE CFG_ENTRY_HISTORY,
DROP TABLE CFG_ATTRIBUTE_HISTORY,
-run moscfg and validate history is set to false and that it loads properly.
-restart MO
First - best practices
-backup the configstore database
-export the configstore for review later (to compare size before and after)
-have a plan of execution and a roll back plan ready if needed.
-shut down MO
-in moscfg (default configstore) set the version transaction history flag to false
drop the triggers:
DROP TRIGGER CFG_ENTRY
DROP TRIGGER CFG_ATTRIBUTE.
drop the tables:
DROP TABLE CFG_ENTRY_HISTORY,
DROP TABLE CFG_ATTRIBUTE_HISTORY,
-run moscfg and validate history is set to false and that it loads properly.
-restart MO