Change Tracking

[panderosa]

Hi,

I wonder what should be the level of details of change tracking - configuration rediscovery. If I have for example an Oracle application which includes several hundreds Oracle Objects like procedures, views, functions etc. Should I check each of them one by one when running automatic rediscovery in my CMDB to find any unauthorised changes? Or just enforce the appropriate Release and Deployment Management based on DML (assuming no unathorised changes can be applied against DB objects) and rediscover only main Oracle configuration topics like listener configuration, tablespaces configuration etc.

Darek

[MVPS]

Hello panderosa,

I assume we are talking here about the Configuration verification and audit activity, from the Configuration Management process.

This is made comparing the physical state of CIs with their configuration in the CMDB. So, at what level you will do it depends entirely of at what level you documented your CI in the CMDB.

Your Oracle application is a CI? Ok, so you should check it regularly for inconsistencies. Generally, it is done at a version level. If you want to do it at procedures, views and functions level, they will have to be in the CMDB, with their corresponding versions...

I would not recommend doing that, but it is up to you to decide what level of control is best for your case. But this kind of control is better described at a development level, like in the CMMI framework...

Regards