Suspecting issues with the date dimension in Request Metrics
Hi, I'm doing a report which the first part of that report is as simple as show total amount of open defects in a project over time.
So I tried using the Request Metrics business view. Now I simply created a chart putting the the fact measure "Total Requests" on the Y-axis and the "Date" dimension on the X-axis. I Also created a filter which filters on a specific project.
Now I just wanted to test this to see what the output would be. I was expecting to see the Total amount of defects per day (Since we ETL every night)
But I just got all the Requests in one bar with the date 1899-12-31. Now my suspicion is that something is wrong either in the FM model or these metrics are wrong.
I tried many more ways to make this work after this without any luck. Anyone knows what the problem could be?
So I tried using the Request Metrics business view. Now I simply created a chart putting the the fact measure "Total Requests" on the Y-axis and the "Date" dimension on the X-axis. I Also created a filter which filters on a specific project.
Now I just wanted to test this to see what the output would be. I was expecting to see the Total amount of defects per day (Since we ETL every night)
But I just got all the Requests in one bar with the date 1899-12-31. Now my suspicion is that something is wrong either in the FM model or these metrics are wrong.
I tried many more ways to make this work after this without any luck. Anyone knows what the problem could be?
Accepted answer
the problem is in ETL, when you run it daily , it suppose to get current date, do a lookup to get date_id and put into date_id column of the request metrics table, but looks it fails to get a correct date_id, then -1 is inserted into date_id, ended up at 1899-12-31.
We have a defect about this on Oracle: The fact builds puts the default date of 1899-01-01 as the ETL date (77670)
We have a defect about this on Oracle: The fact builds puts the default date of 1899-01-01 as the ETL date (77670)