This describes the wi_pendtime_bygroups table and how each column of data arises from
the DPR_BYINTERVAL table .
The wi_pendtime_bygroups get its data from the
DPR_BYINTERVAL table.
The data is grouped into different group type and the pending time is summed against this group type for the hour. Then the summary record is being put into this table.
This is the column description of each data column of WI_PENDTIME_BYGROUPS and how each column is filled with data.
Columns |
Description |
Key |
CLUSTER_CODE |
This comes from the CLUSTER_NAME field in the raw table. Once we get the cluster_name, we then look it up in the wi_clustercode table to see if we have already has a record of it in there. If we do, then we'll get the code back, otherwise, we will insert it into the wi_clustercode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing sequence+1. |
Primary key |
TIME_STAMP |
This is in GMT and is always end in the hour such as 02:00:00. This marks the time that this record is aggregated. For example, 02:00:00 means that all the records between 02:00:00 and 02:59:00 are aggregated into this record. |
Primary key |
GROUP_TYPE |
This indicates what kind of grouping this record belongs to. The different group type are: "By Host Type", "By Reason" and "By Cluster" |
Primary key |
GROUP_CODE |
This could comes from different source and it is depends on the group_type. If the group_type is "By Host Type", then it comes from a subfield of the "PendReason" field from the data file. If it is "By Cluster", then it comes from the "ClusterName" field in the data file. If it is "By Reason", then it comes from the subfield of "PendReason". Once we get the fields, we then look it up in the wi_dimensioncode table to see if we have already has a record of it in there by matching the dimension_name. If we do, then we'll get the code back, otherwise, we will insert it into the wi_dimensioncode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing code+1. |
Primary key |
REASON_TYPE_CODE |
This comes from the "PendReasonType" field from the data file or it may come from each pending reason of the PendReason field. Once we get the fields, we then look it up in the wi_dimensioncode table to see if we have already has a record of it in there by matching the dimension_name. If we do, then we'll get the code back, otherwise, we will insert it into the wi_dimensioncode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing code+1. |
Primary key |
REASON_CODE |
This comes from the "PendReason" field from the data file or it may come from each pending reason of the PendReason field. Once we get the fields, we then look it up in the wi_dimensioncode table to see if we have already has a record of it in there by matching the dimension_name. If we do, then we'll get the code back, otherwise, we will insert it into the wi_dimensioncode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing code+1. |
Primary key |
PEND_MINUTES |
This field is calculated from every subrecord in the "PendReason" field in the data file based on the JOBDISTR and INTERVAL of each record. By using the HostDuration transformer, we calculate the specific pending time for each pending reason. The calculated time is then transformed into minutes and put into this field. |
|
LOCAL_SERVERTIME |
This comes from the "Time_stamp" in this table. This is transformed into local server time. |
|
INSERT_SEQ |
This is a system generated sequence number. For each new record inserted, an unique sequence number is being assigned to this column. |
|