OCI DWH Qtree Report

[sstrznwra]

Hi,

I create a Report for Netapp qtree´s in OCI DWH (mysql) , the qtree are in the dwh_capacity.qtree_dimension

e.g.

with tk '15260' , when I look in

SELECT * FROM dwh_capacity.qtree_capacity_fact
where qtreeTk = 15260

Result:

Null 

Does anyone know what I am doing wrong?

Thanks

Michael

[ostiguy]

Does the qtree have a hard or soft quota on it?

A qtree doesn't really have any capacity unless a quota is tracking its utilization.

[sstrznwra · Accepted solution]

Hi Matt,

the qtree has a hardquota 10MB  and use 116KB, the dwh_inventory.qtree  shows the quota but no quotaUsedCapacity.

[moechnig]

I'm not sure off the top of my head of all th reasons we might not create capacity facts for a given qtree. 

It might be interesting to get a look at how many capacity facts you have for each of your qtrees. 

select sd.name storage, qd.name qtree, qd.tk qtreeTk, count(distinct(qcf.tk)) capacityFactCount
from dwh_capacity.qtree_capacity_fact qcf
right join dwh_capacity.qtree_dimension qd on qd.latest=1 and qd.tk=qcf.qtreeTk
right join dwh_capacity.storage_dimension sd on sd.identifier=qd.storageIdentifier and sd.latest=1
group by qd.tk
order by capacityFactCount desc;

[sstrznwra]

Hi,

The bold lines are the qtree that i can`t see in my report last week

Last week on Thursday I write a Testfile with 1MB to the Qtree , previously only 148KB were used ,and now I can see the data in my report  (see Attachment)

naso1p notesid 15258 116
naso1p notesid-rbgos 15261 116
naso1p notesid-rbgob 15259 4
naso1p notesid-rbgoi 15260 4
naso1p notesid-rbgos 11268 0
naso1p notesid 12216 0
naso1p notesid 14177 0
naso1p notesid 14393 0
naso1p notesid 14401 0
naso1p notesid 14849 0
naso1p notesid 7113 0
naso1p notesid 14929 0
naso1p notesid 10050 0
naso1p notesid 15121 0
naso1p notesid 10058 0
naso1p notesid 10615 0
naso1p notesid 10696 0
naso1p notesid 11096 0
naso1p notesid 11116 0
naso1p notesid 16129 0
naso1p notesid 11265 0
naso1p notesid-rbgob 11266 0
naso1p notesid-rbgoi 11267 0

Michael

[moechnig]

I'm not sure whether it is important to you to continue investigating this situation. 

If you do want to look into it further, it may be interesting to see what changed about the qtrees in question on Thursday, from OCI's point of view. 

select * from dwh_capacity.qtree_dimension where tk in (15259, 15260, 11266, 11267) order by name, tk;

It would also be interesting, for a qtree where you can reproduce this problem, to compare what you see in OCI with the output of a listing of qtree sizes from the ONTAP command line, such as "quota report". 

[sstrznwra]

Sure it`s importend for us, we try to understand how oci works

I send the to output from 

select * from dwh_capacity.qtree_dimension where tk in (15259, 15260, 11266, 11267) order by name, tk;

and the quota report in a PM  

thanks Michael

[ostiguy]

That is really good legwork Michael.

OCI does store everything internally in base 2 MB, so I am not surprised that ~100KB is rounded down to 0 MB, but I would like ot think we should be reporting the qtree regardless.

I think I'd like to see a datasource recording for this - if this site is sending OCI ASUP, could you email me the datasource name and OCI site name to ostiguy at netapp dot com?

Thanks

Matt