DSXchange

How, exactly, are you "reading 4 files" in your Server job?

The key is in your NLS_LANG (and probably LC_CTYPE) environment variable setting. In order for the conversion to happen properly, Oracle needs to know the source character set is different from its native character set. Otherwise, everything is moved over unconverted and thus can become invalid in t...

Have you read the 'XML PACK' pdf document in the Docs directory on your PC?

I personally would go for 'a' and have done so many times. Push back on the restriction that you are "not allowed" to create tables on the source. You should be using a 'connection account' to access the source, a functional user created specifically for your ETL processes and not an existing owner ...

karthikgk0705 wrote:it gave error msg like "could not find exclusive log for the job"

Like but not exactly like.

The key, as noted, is to take the actual error message and search this site for it. You'll find plenty of references to it.

Well, I sincerely doubt that was the actual 'fix'. I'd wager that in the time it took to arrange and perform the DataStage bounce, the lock either resolved itself or a DBA on the other end of the Oracle alert logs resolved the problem for them.

Only via the same mechanism you would use outside of DataStage - a dblink.

From the way the original post is phrased, I'd make no assumptions about knowledge "about web services and services in general". Perhaps something like this would help someone get started.

I've never heard of nor seen any such thing. A timestamp carried all the way through your job should not be an issue nor 'round up' in any fashion. But then I'm running 7.5.1A not 7.5.2 at the moment. Rather than continuing to chase the wild gooses, I'd suggest you contact your official support prov...

Ah... forgot about that little wrinkle. Usually that's considered a Bad Thing, but here... not so much.

'Super' Operator role, eh? Nice to know.

Such as?

Again, how many records are there total in your target file? I doubt it's getting 'hung up' but rather just taking a long time to perform a full table scan for each record. How long did you let it run before you decided it was stuck? Best at this point to enlist your DBA to either trace your session...

You'll need to find some other mechanism to deliver log information to them, something other than Director as you've already noted. I don't believe there is any such mechanism built into the Client tools that would allow log looking but not job running.

You'd need to put the contents of the file there rather than the filename itself. Then a job parameter can be used for the #TABLE_NAME# in the DML if you like.

Shouldn't be a problem. Are you sure you are dragging the link in the 'right' direction - from the Job Activity stage to the downstream stage?

What doesn't work about it, exactly? Is any error generated?