DSXchange

ajith wrote:I heard that HP-UX needs SHLIB_PATH in addition to LD_LIBRARY_PATH.

It's one or the other, depending on your operating system. H-PUX uses SHLIB_PATH.

It's not about specifying the length per se, but about char versus varchar. When you declared the first field to be a char(6), that means it will always have 6 characters in it - period. DataStage isn't seeing that.

It needs to be declared as a varchar as well.

So, in other words an Oracle sqplus setting, nothing to do with the shell script at all but rather the sqlplus script.

You are probably confused by the lack of a '.txt' extension on the split files. It doesn't mean that it 'changed the format', if you open them you'll see they are still fine. Part of your 'split post-processing' will need to be renaming the files back to your desired pattern, including restoring the...

The generic answer to your 'how to convert a date' question is 'using IConv/OConv'. There are tons of posts here with examples, you'll find them as well in the online help for each function. It would help to mention the target database as that can change things, but typically a 'timestamp' means dat...

Don't you have access to any Teradata resources where you work? You need to find out if they even support the concept, something analogous to an Oracle 'sequence' object or other database's SERIAL field - and that's got nothing to do with DataStage.

Your other option would be to concatenate all of the files you need to process into one large 'work' file and then process that rather than running a jillion instances of the job.

Those are reserved words and must be double-quoted if you want to use them in a sqlldr control file.

Exactly... sometimes people think the 'Sort' fields in the Aggregator stage are there to tell it how you want it sorted. They are actually there to assert the sorted order of the incoming data. If the sorted order matches the grouping / aggregation being done, then the stage can do much less work, r...

Ok, then you've obviously blown the aggregator out of the water with that volume. Presort the data before the Aggregator stage in a manner that supports the grouping being done and then assert that in the Aggregator stage. You can handle pretty much any amount that way but the sorting could be an is...

That doesn't really help.

How about some details? What goes on between those two stages? Volume being processed? Anything you can think of that may help...

Not knowing anything about your job - a guess. What kind of volume are you aggregating? There is a limit to the amount of data that you can aggregate at any given time without pre-sorting the data and when you hit that limit, the stage just kind of falls over dead. Help us help you when you ask for ...

You've found it, but for other's benefit it is located under the 'Real Time' portion of the palette in the Designer. Not being one of the 'optional' plug-in types of stages, it installs automatically, so no worries about it not showing up. Hopefully.

Sure... you should have three XML related stages installed: XML Input, XML Transformer and lastly the XML Output stage which you would use to create XML files.

You should also be able to find an 'XML Pack 2.0' pdf manual in your 'Docs' directory which will walk you through use of the stages.