DSXchange

This was a data related issue...the UPDATE failed on a unique index due to a duplicate SAP customer number..which should theoretically be impossible...perhaps someone manually "enhanced" the data?

Thanks...L8r!

Wade

We have an interesting problem that I am having trouble understanding... We have an environment that has been running daily for about 9 years and is quite stable. However, yesterday, on a load of about 100,000 records, a single record failed with : [DataStage][SQL Client][ODBC][Microsoft][SQL Native...

Hi, Craig, Thanks for the reply. I did try to reduce to a length of 19, but the problem persisted. I discovered in one of the existing routines that created a timestamp, it was appearing as I posted 2009-8-04 10:41:02 instead of 2009-08-04 10:41:02 I corrected the existing routine and re-tested succ...

Hi, Craig,

Datetime as selected from SQL Server> 2009-07-13 14:15

LASTUPDATE as generated in routine > 2009-8-04 10:41:02

Isn't StringToDate a Px transformation?? While it is available in Server, it doesn't seem to be working.

Addendum 2 : Best option is for the LASTUPDATE field to be set to Char(23,3), Data Element SQL:SMALLDATETIME. At least this does not yield any warnings during the load, though it does during a View Data. For me, this is not closed. There should be no warnings whatsoever, and this is not making sense...

Addendum: I noticed that concatenating ':00.000' to the end of the date fields is working, however, on our LASTUPDATE field which the run time is written to, it is NOT, though its datatype definition and structure at the target is identical to the other fields. This field still has the same, outstan...

This is a complex issue to describe relating to treatment of timestamp data, but after hours of A/B testing hopefully I can be concise. to this point, I have exhausted all conceivable options and still this is not working without warnings. Basing new development on the exact same approach used in th...

I also agree with Mike, and was also my concern. However, my client has decided to do this with another technology, so therefore, this is resolved on the DS side

Thanks

Wade

Hi guys Just got a requirement to do the following: Receive two files, one with the target metadata and another containing the data - Create the table based on the supplied metadata in the first file and then insert the data in the second file. This will need to be a generic solution, as there are p...

Found the solution... Due to large data volumes received during development, and performance issues, I had set the commit interval quite high. Now, however, I am only receiving under 100 records, which is under the commit interval. DataStage seems to be waiting for additional lines (which really doe...

Something I don't understand currently is happening during an insert to AS400. - DRS Stage over ODBC (AS400 client not installed on DS Server) - AS400 table is journalized - Field datatypes - all character except one numeric. Data verified for Numeric field to be numeric (eg. :010) for all records J...

Hi, This really should not be that complex, but I am having trouble getting it to work. I am trying to invoke a sequence at insert time in AS400, but my client prefers to use a sequence created in AS400 rather than the KeyMgtGetNextValue routine. I have been using the following sql in the ODBC stage...

Thanks, Ray...confession time.

My staging point, for some reason had the YYYYMMDD field defined as datatype "Date" instead of "decimal". once I set this correctly to "decimal", the problem was resolved.

Hi, Having a problem I am sure I have seen before, but going over my past projects, I have not found the solution I used before. I am updating from AS400 to the same AS400 with a hash file staging point after a transformer. The objective is to put today's date in the target field (Decimal 15,6) in t...