Results 1 to 4 of 4

Thread: Default values overwritten by NULLS

  1. #1
    mparpal is offline Junior Member
    Join Date
    Jan 2011
    Posts
    2
    Rep Power
    0

    Default values overwritten by NULLS

    I am inserting records into an Oracle table that has 3 columns with default values. I am leaving the "ignore" option on as the source for these 3 columns, however, a NULL value is being inserted which is disallowing the defaults to be set. :confused:

    Please help with a solution/workaround to this issue. Thanks.

  2. #2
    katoom is offline Junior Member
    Join Date
    Jan 2011
    Posts
    2
    Rep Power
    0
    Am having the same issue- a no null date column specified with a sysdate default is not allowing inserts- error saying cannot insert null into ..column.

    Changing the column to allow nulls allows inserts, but then nulls are written instead of the default sysdate.

    Any other options?

  3. #3
    katoom is offline Junior Member
    Join Date
    Jan 2011
    Posts
    2
    Rep Power
    0
    Not an attunity error, just a ssis feature- to workaround, add a derived column component to the workflow, choose the problem columns that are receiving nulls, and put the desired default values into the columns- done!

  4. #4
    mparpal is offline Junior Member
    Join Date
    Jan 2011
    Posts
    2
    Rep Power
    0
    katoom,

    Thanks for your solution - it works perfectly! I had tried that previously but couldn't get it to work so I gave up on it (a little too soon as it turns out). Moving the Derived Column section prior to the Data conversion section made it work.

    Thanks again for your help! :D

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •