Message is displayed in the logs when small values are unable to be inserted into the timeslice table because the value is beyond the precision that the table will store. This does not cause the job to fail.
Steps to Reproduce:
Expected Results: No Errors
Actual Result: The following error in the bg-ca.logs:
WARN 2016-02-17 03:08:39,549 [Dispatch Thread-5515 : bg] niku.blobcrack ... Slice value is not in the valid range. Object ID = 5014148 Request ID = 106 Date = 2014-08-23T00:00:00 Value = 3.280845143079422E-13 WARN 2016-02-17 21:23:28,771 [Dispatch Time Slicing : [email protected] (tenant=ppm)] niku.blobcrack ... Slice value is not in the valid range. Object ID = 5002001 Request ID = 5000024 Date = 2016-02-01T00:00:00 Value = 0.0. Value will be set to 0
The total amount entered in the source field (stored on the BLOB field) is sliced into daily amounts based on the date range for the period. If the resulting slice (daily) amount is a number that does not fit into the field definition precision, the amount cannot be stored.
Release: All Supported Releases
Component: Clarity Time Slicing
Based on the message shown in the BG Log (Request ID = 106), you can determine what type of slice data to look for.
SELECT * FROM PRJ_BLB_SLICEREQUESTS
WHERE ID = 106
The results show the REQUEST_NAME = W_ALC
This is the Internal Weekly Allocation Slice Request. This Slice Request is automatically sliced when data is changed for a Project Team Member.
To locate the specific Allocation record instance, the 'Object ID' in the Warning Message can be used to query into the PRTEAM Table. The PRTEAM table holds the curve for Resource Allocations.
Based on the message shown in the BG Log (Object ID = 5014148), this query shows Project Team allocation record. (This query is applicable to this slice for allocations)
AND I.ID = T.PRPROJECTID
AND T.PRRESOURCEID = R.ID
AND T.PRID = 5014148
You can then locate the Project and the Team Member in the application to view the original curve data and make adjustments.
Once you make adjustments, the slicing will attempt to crack the blob again and you can check the BG Log to see if the message persists.
This is just one example of how this message is useful for locating and resolving data issues. Other Slice Request IDs will correspond to different types of data and will require references to different tables and application UI pages. Use the Technical Reference Guide for additional information.
If the warning messages are suppressed in the CSA Log Configuration, turn the debug level to WARN so that you can see these messages. To suppress the warning messages set the debug level to ERROR and then only error messages will appear; no warning messages will appear for this component.
To configure the logs, please do the following.