ETL Database does not update correctly

[DCIM_Support]

The ETL Database does not always update correctly. It is, therefore, not reliable for our reports. Examples:

1)    When the DC folder structure was changed, the ci_location string in dbo.configuration_item did not update accordingly; we had to drop the table in the ETL DB and export it again

2)    For a 2nd month the rack used/free space numbers in dbo.swo_kpi are the same – which is not possible, as there have been changes in ISX

We have gone through the available ETL settings in the webmin interface, but there appears to be no option whatsoever to tweak how exactly the export of the data is done.

What we do need is the ability to overwrite the existing data if it exists already in the reporting database, so that it updates properly. Or, for it to update fully if there are significant differences (which does not seem to always happen now). With the MS SQL export/import options, the option I refer to is:

Is this a known issue, is there a fix, or are they working on one?

(CID:132655462)

[DCIM_Support]

Hi Lukas,

To understand and investigate the issues, can you please provide the following data:

1- details & screen captures illustrating the issues

2- copy of the latest backup file

3- complete server logs (can be collected from webmin interface > StruxureWare DC Operation > Download Log Files > Download log files)

I will send you an invite (from my =S= box) soon, so the data can be safely shared with me, thanks.

ps: it seems your image have not been attached (it says Broken image).

Kind regards

(CID:132655471)

[DCIM_Support · Accepted solution]

Hi Lukas,

Many thanks for providing the data. During our detail investigations we found out that specific etl transformation(s) failing (due to data mismatch between the tables). I have logged a bug report for this, so it can be fixed. I have also sent you a direct message (by email) few minutes a go.

Kind regards

(CID:132657389)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.