DSXchange

Kim Duke has one stashed away on his website:

http://www.duke-consulting.com

$ENV is correct, what's not correct is your $NLS_LANG value. "UTF8" doesn't stand on its own, try "AMERICAN_AMERICA.UTF8" instead. Note that you may also need to set "LC_CTYPE" for this to work, I use "C.utf8" there.

Job logs are stored in hashed files under the associated project directory. They take the name of RT_LOGnnn where 'nnn' is the internal number assigned to the job in the repository. You can access them using the 'dsjob' function, which supports the same log access functions as does DataStage: -logsu...

I'd still look at the UtilityRunJob mechanism, but make it a mult-instance job run X ways with each instance handling 1 of each X records in the driving source file via the mod() function.

So, someone just dropped you in the deep end of the pool without any training or even a pair of water wings? Nothing unusual about this scenario. The good news is, once you get this figured out, the common widget used means you shouldn't have problems with any of the other stages. More than likely. ...

It's been reported as working in some areas, guess not here. Something else to try is two single quotes for each one: CUSTOMER_NUMBER IN (''01135101'',''01200662'',''ABCD'') AND Note they are NOT double-quotes, but rather two single quotes. I guess you could also try a quoted quote and see if that m...

So DataStage doesn't think what is coming out of your database is a date. Answer my other question, please - what does the selected date data look like?

I searched for "current date" and got 81 hits in the PX forum.


Should be a good starting point.

Metadata mismatch. What is the datatype in your stage for that column? What does the selected data look like?

In a "non-NLS enabled" environment, there's no tab as you don't really have a default setting AFAIK. That or it is effectively set to "none". Nothing stopping you from adding a user defined environment variable setting $NLS_LANG to UTF8 if you so desire and it would automatically take effect in all ...

Kind of odd that View Data works but the job doesn't, usually it seems to me to be the other way 'round. Under what circumstances would that happen? Metadata issues?

There's no direct link. You need to go to his site, ask for a userid and - once granted - grab the utilities from his download area.

http://www.kennethbland.com/

"the no of updates are more than the updates".

Server job, so no "EE" stage.

How big is this weekly file? That size and the ratio of inserts to updates (which is important to know) will drive the design.

kittu.raja wrote:

chulett wrote:First suggestion - take your actual "exporting nulls" error and search the forums for that exact string. ...

Mine is the only message it has in the forum. Nobody has raised this issue before

No, you're not. Use a common portion of your actual error, not what you put in your first post.