DSXchange

DataStage won't care. Details, please - what transformations are you doing, if any, on those dates? What does your target SQL look like? Post your actual warning as well, in full.

The URL I found was this:

http://www.dsxchange.net/job_postings.html

But it is bone empty, I'm afraid. You're better off at places like LinkedIn, join some of the DataStage or ETL centric communities there... or elsewhere.

Not without details. For example, what does you input look like directly from the source? What transformations are you doing? What does it look like when it hits your target stage? You've given an example, but we don't know what 'state' it represents. Bottom line, though, is all you need to do is ge...

In other words, that same use that a template would serve in any other tool or process.

rsunny wrote:I haven't done anything with parameter8, but i am trying to fix it for parameter7 only.

OK, fine... by goofing up the sql and hard-coding one value, you now have only seven parameter markers. It is complaining about trying to put 15611 into a timestamp.

And note that I put 'solved' in quotes because for some odd reason you decided to hard-code your timestamp value in the DML and while it matches the format mask you used (and thus 'worked') it isn't the same value nor format as your actual data. Plus what kind of date/timestamp value is a STARTDATE ...

To the best of my knowledge, you need to contact the site owner for anything of that nature. I would probably start with the Editor under the Contact link at the top of the page unless someone has a better (more informed) suggestion.

Same as it would be in any other tool or process.

Well, look carefully at the message and you can see it's not quite the same error - you "solved" the problem for parameter 8 but now see the same issue for parameter 7.

We store that date/timestamp in another table, one dedicated to storing those "last extract dates" and then simply join the appropriate record from that table to our source query. Otherwise, as you've noted, you need the 'overhead' of a process to fetch and store it somewhere accessible ex...

No worries, simple enough for me to move it, just wanted to make sure it would be appropriate. <click> And here we are. :wink: Never heard of any such document, as noted I still think it would be best to involve your official support provider for help with that stage. I'm not sure how much experienc...

Let me be more specific - you are trying to create a routine that does what? Something you are certain cannot be done with the existing functions?

Search for a file called dsapi.h on your system and all will be revealed, error and status code wise. Or check here where someone decided to post them all, once upon a time.

As to the Ans in the email question, simply add it to your 'Body' text, something you are currently leaving blank.

Not in the job, but in the Oracle table itself - it is a TIMESTAMP? With what precision? If so, you should be using the TO_TIMESTAMP() function then.