question

Brett B. avatar image
Brett B. asked ·

Database Size not Reported Correctly

Hello,

For some reason, DC RUM reported these database instance sizes as 1.7TB although our DBs cap at 1.2TB (which is what they were actually at (100%)). Any idea why it may report larger than the DB drive actually is?

nam server
databasesize.png (104.2 KiB)
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Adam P. avatar image
Adam P. answered ·

Brett,

It looks like you enabled i.e. Autodiscovery, then turned if off and shrink task did the rest ...

BTW: what report is this? And what are these IPs? AMDs?

2 comments Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Hey Adam, that could be correct. I believe we actually reduced our Storage Period from 10 days to 5. It is a DMI I created using the DB Status View (I had to steal it from atscon -> Database Status, and then save it into my viewable DMIs). The IPs are all CASs & ADSs.

0 Likes 0 · ·

Also, they're all filtered on Table Group "All".

0 Likes 0 · ·
Chris V. avatar image
Chris V. answered ·

I think the CAS may be reporting all appliable space, e.g. LOG and TEMP space usage too.

1 comment Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Hey Chris, I don't believe that to be true as LOG and TEMP are also stored on the same drive, with capacity 1.2TB.

0 Likes 0 · ·