DSXchange

That's OK, it just means that the data browser doesn't know how to display Char(137). DataStage is probably reading it successfully, so you can convert the Char(137) back to whatever you like within the job, perhaps tab (Char(9)), perhaps "". Whatever is appropriate.

There are two methods. 1. Analyze the logic of the server jobs and write parallel jobs to implement that logic. You could, of course, hire a competent consultant to do this. 2. Give IBM a lot of money to do the same for you. They call it (their "service") "conversion tools" but most of it is outsour...

You are not getting that error only. It never appears in isolation. What other warnings or errors have been logged? Please post the exact messages (copy/paste - do not transcribe and especially do not attempt to add your own interpretations).

Suman wrote: The problem in the job is coming because of '&' in the input file name.

What proof do you have for this assertion?

You need a DateToString() function with a StringToDate() function as its argument. Supply appropriate date format strings to the two functions.

You seem to be confusing data partitions (~= processing nodes) with output links from a Filter or Transformer stage. Whatever you were to specify with DML expressions (in a Filter stage) will happen on every processing node - the data are already partitioned, and are being directed onto multiple lin...

What did you change so that it works?

Wherever you set ORACLE_HOME is a good place also to set NLS_LANG. Since you set ORACLE_HOME in the dsenv script for DataStage processes, that would be a good place for NLS_LANG too. Or you could set up NLS_LANG as an environment variable in the Administrator client, and therefore use different valu...

That's exactly what I mean to say. You could even leave it as Timestamp. They're the same to Oracle. You only need to worry about format if you are supplying string data and applying a TO_DATE function.

Possibly your Pivot stage is not properly installed or registered. I am not seeing the same issue. You are, I trust, using the parallel Pivot stage, not the server job Pivot stage?

What exact version of DataStage are you using, and on what platform?

You would need to remove the parent directory of DATA.30, which (if executed recursively) would take out DATA.30, OVER.30 and .Type30, and you need to remove D_hashedfile. Command = "rm -rf " : HashFileName : " && rm -f D_" : HashFileName Call DSExecute("UNIX&quo...

WHEN are you getting this error (for example during design, during compilation, when requesting job execution, during job run)? Is there any more to the error message? Are there any additional error messages? Load Mode is one of the properties of this stage. Have you set its value and, if so, to wha...

For starters, welcome aboard. Please note that correct terminology is hashed file, not hash file. Do you have caching enabled on your lookup? What happens if you remove the lookup from the job? What else is happening in the Transformer stage? Are there any warnings or errors logged?

I'm not aware of any documented limit on LongVarChar, and would be very surprised if it were as small as 4KB (because a VarChar can be that big). Suggestion: try VarChar(16384) rather than LongVarChar(16384) When, precisely, does this error occur? It is certainly possible to load VarChar(16384) or L...

Please be more exact about which stage types you have used in your design. We need to be precise about which particular "source stage" can not have an output link. Using version 7.5.1A on Linux the following job design does not generate the error you report. SequentialFile -----> Pivot -----> Sequen...