Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

Built-in parameter MappingRunStartTime is showing wrong year when used on the last day of the year
Problem Description
All mappings using built-in parameter MappingRunStartTime that are executed on December 31st show an incorrect value, showing a year ahead. The message below is for a mapping executed on 31/12/2018

2018-12-31 08:30:38.662 INFO: [LDTMPARAM_0013] The Integration Service uses the value [12/31/2019 08:30:38] for the system parameter [MappingRunStartTime].

The same issue was observed for jobs ran on 2018-12-30. 

2018-12-30 02:01:19.266 <DefaultWorkManager-WorkerThread-144> INFO: [LDTMPARAM_0013] The Integration Service uses the value [12/30/2019 02:01:17] for the system parameter [MappingRunStartTime].​
​​
Cause
This incorrect behavior for parameter $sys.MappingRunStartTime ​is caused by CR BDM-20274.
Solution
This issue is specific to this day: December 31st, so next day, January 1st, parameter value will be back to normal.
The fix for CR BDM-20274 is going to be included since 10.2.2 and it is marked to be included in next HF2 for 10.2 to avoid this happening at the end of 2019.
More Information


Applies To
Product: Data Quality
Problem Type:
User Type:
Project Phase:
Product Version:
Database:
Operating System:
Other Software:

Reference
Attachments
Last Modified Date:2/20/2019 10:28 PMID:566156
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)