Results 1 to 3 of 3
  1. #1
    Join Date
    Nov 2004
    Posts
    1,427
    Provided Answers: 4

    Unanswered: Copying one Timestamp to another and recieving "Value Too Long" error

    I am copying a timestamp field from one table (the old one) to a timestamp field in another table (the new one that will replace the old one).

    Code:
    Insert into NEW_TABLE (
    	NR_DOC, 
    	TS_INPUT
    )
    SELECT 
    	NR_DOC,
    	TS_CREATE
    FROM OLD_TABLE
    ;
    I receive an error
    [IBM][CLI Driver][DB2/NT]SQL0433N Value "2007-05-09-10.15.51.672000" is too long. SQLSTATE=22001

    How can the value in one timestamp field be too long to fit in another timestamp field ??

    I tried to do a TIMESTAMP(TS_CREATE), in the hope that that would ease DB2 a bit, but that trick didn't work.
    With kind regards . . . . . SQL Server 2000/2005/2012
    Wim

    Grabel's Law: 2 is not equal to 3 -- not even for very large values of 2.
    Pat Phelan's Law: 2 very definitely CAN equal 3 -- in at least two programming languages

  2. #2
    Join Date
    Jun 2006
    Posts
    471
    there is an apar talking about this
    IY95753: FP14 ONLY
    have a look..
    Best Regards, Guy Przytula
    DB2 UDB LUW certified V6/7/8

  3. #3
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Do you mind showing us the table definitions? The actual ones?
    ---
    "It does not work" is not a valid problem statement.

Posting Permissions

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