DSXchange

Welcome! :D

Apparently, this is somewhat of of a known issue. At least in certain versions. Probably best to contact your Support provider and see if there is a patch for this or if you need to limit the length of your userids.

Also, I had a chat with one of the instructors who said "If Oracle takes too much time processing the query then DS will fail" Umm... let's play Jeopardy: "What is false?". Let's not worry about that right now. When you get back to your job and try this again, let us know what issue(s) you are havi...

A very basic answer: Yes. Without the 'vice-versa' part. Older versions can be imported into newer releases and will be automagically 'converted' during the process. There is no such backwards equivalent. The difference between them? Pretty much the same as any other software: bug fixes, new feature...

7.5.2 would be a newer release than 7.5.0.1, but I assume you already recognize that. If you are asking what changed between those releases, only the vendor knows for certain. The 'readme' that comes with any version lists changes from previous releases, but who knows how all encompassing it is? I ...

The former. It has no clue how many rows any given sql has affected.

What, getting data out of a DB2 table using OCI stage?? I'd like to see that! Puh-leeze. Just mentioning that it does work in the OCI stage, therefor there is a reasonable expectation that it should work as well in the DB2 stage. Of course, maybe it just be broke there. It looks like it is not reso...

It sure sounds like a upgrade related issue. Best to call your Support provider, open a case, that's really where you should be taking this issue next if you haven't already.

What i got frm ur Q is: U want Come on... we're not your bestest l33t buddies on the other end of an IM or text message. This is a support forum for professionals. Seeing as how English isn't the first language of a great many people here, let's take a extra moment to use real words spelled all the...

If you truly don't want to see them, redirect standard error to /dev/null when you launch your script. Or use DCount to count the output and take the last one.

If you 'know' it will always be too big to cache, don't set it - it will save a little startup time. Will it hurt to set it? No. It will try and you'll get a message it could not be cached.

You should RESET the job only if it needs to be reset. Check first and conditionally issue that command if the previous run aborted. That being said, simply resetting a job doesn't open or validate a sequential file as far as I know. Now, if it had aborted for some reason, the reset itself can log a...

Sure, but the secret is the version of the Oracle client you use to do that. From what I've seen, you'll probably want to use a 9i client for that.

Wow... Ken dropping a Mario reference. Who woulda thunk it?

Works fine from the OCI stages from what I recall. Not something I do very often (hardly ever) but have done it.

Am I right providing my project folder as "DsxPath" ? Maybe this only works on a unix/linux system? No, it will work on any system. No, you do not provide it a path to your Projects, but instead create a ".dsx" export from the Manager of the source of all jobs in your project. Then point it to that...