This project has moved. For the latest updates, please go here.

Unable to Hash 12/03/3588

Oct 20, 2012 at 11:23 PM

I have a field that contain the date 12/03/3588.  This is a valid DATETIME2 value. 

Should this work?

Rob

Coordinator
Oct 21, 2012 at 12:46 PM

Rob,

Yes this should work.  It does in all my testing.

MD5 Hash for 12/03/3588 is 0xCA 0x08 0x29 0xCA  0xDF 0x8D 0x29 0xDB  0x99 0x7D 0x69 0x9E  0xAF 0x98 0x1F 0xD5

MD5 Hash for 12/03/3589 is 0xCA 0x2D 0x0F 0x22  0x2B 0xBD 0xDE 0xBD  0xB1 0xC5 0xA0 0xC1  0xBE 0xC9 0xAE 0x70

MD5 Hash for 12/31/9999 is 0x1B 0x1D 0x7A 0x4B  0xEE 0xDE 0xB1 0x18  0x58 0x14 0x71 0x39  0xB9 0xA4 0x82 0x7F

MD5 Hash for 01/01/0001 is dependant on the datatype being used, as some SSIS date data types do NOT support this date...

  • 0x00 0x8D 0x08 0x2B  0x5E 0xA7 0x7B 0x9D  0x39 0x38 0xFB 0xA9  0xB0 0xDE 0xD8 0x01   
  • 0xCF 0x65 0x2F 0x8E  0x96 0x11 0xBA 0xC6  0x8D 0x3E 0xD4 0xBC  0x80 0x7E 0x5F 0x5E

No error is thrown by Multiple hash for any of these date values.

 

If you are getting an error, please post the details.

Keith.

Marked as answer by kmartin on 7/8/2014 at 6:29 AM
Oct 21, 2012 at 4:54 PM

Keith,

Thank you for your reply.  When I query the field in question in Oracle SQL Developer, it returns 12/03/3588.  However, I converted it to text in SSIS and trapped it in a data viewer.  Now I got -3588/12/03.  I think it is a bug in Oracle myself.

I am loading a Slowly Changing Dimension and this errorred on data from a long time ago.  I woke up in the middle of the night and remembered the problem and how we trapped it.  I added a Character Conversion step and am discarding bad dates.  Fortunately there are only a few records like this.

Rob