Hi all, Sorry for the insistence, but I caught the same error today. I was checking the the loads scheduled for the last weekend and in one of the tables I could found again the 2001-08-00-00.00.00.000000 TIMESTAMP. As you can see this time it seems it was able also to write well the month (this load run about 10 or 11 p.m of friday 31/08) but lost everything after it! I checked the db2diag.log and looked for the entries with times close to the other rows TIMESTAMP and the only entry I found are the ones of the LOAD and all of them are normal; moreover there are no other entry with errors or warning So 'cos it's starting to be a bothering issue I just wanted to know if anyone got something similar also because if I want to contact db2 support I don't have any logs indicating a problem so I don't know where to start! Thanks again Fabrizio -----Original Message----- From: Napolitano, Fabrizio To: '[EMAIL PROTECTED]' Sent: 31/08/01 12.56 Subject: UDB EEE 7.1: TIMESTAMP out of date range Hi there, I'm struggling with a strange situation working with TIMESTAMP. This is my environment: DB2 UDB EEE v7.1 fp3 on AIX 4.3.3 (one DB on a SP 4 nodes, and one on a SP 2 nodes) Two DBs have exactly the same design. Now this time my troubles are with TIMESTAMP. Most of our tables have one colunmn defined as TIMESTAMP NOT NULL with DEFAULT. All of this tables are loaded omitting the TIMESTAMP column so if I'm not going dumb the timestamp should be calculated by DB2 . I first caught the problem when I exported one table from the first DB to move it in the second one. Infact when I tried to reload the file on the other table I got one record discarded the reason was a date column is out of range. Found the discarded record I discovered what was wrong: the format of the timestamp was a bit strange 2000-00-00-00.00.00.000000 well I loked in the table on the first DB: $ db2 "select distinct (TIMESTAMP_COL) from MY_SCHEMA.MY_TABLE" and I got this : TIMESTAMP_COL -------------------------- 2000-00-00-00.00.00.000000 2001-01-10-15.48.49.404347 2001-02-07-12.53.11.167967 2001-03-22-11.41.03.474725 2001-03-22-11.41.03.483433 ... only one record had the 2000-00-00-00.00.00.000000 TIMESTAMP. How does it is possible ? Any idea? What does it mean? Can this bring to future problems but the noisance of insert back this record in the second DB and maybe updating it in the first one to avoid it reapeting? Thanks in advance Fabrizio ===== To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
