DSXchange

Kapil - I give up. We are not trying to hide a solution from you and you don't need to restate your query. If someone could answer your question with the data listed so far they would have. You are getting a schema error. You need to list the schema the way DataStage sees it. Orchadmin will do that....

I'm not at a DataStage connection now, so I can't give you the exact path. It seems that "orchadmin" is not in your UNIX session's path. You will need to add it or execute the program from it's location. It should be in a bin directory underneath your $ORCHHOME directory; but you can always do a "cd...

That is very legible, try doing a UNIX "orchadmin describe {AbsoluteDataSetFileName}, that is easier to cut-and-paste as text here.

Can you change your output to a dataset, run the job and then look at the schema generated for the DataSet? This might help a bit, I think it might be your null handling in the output.

try a constraint "1=2" on your transform to see if the error remains even when you don't write any output. You might also put in a handler in your sequential file for the nullable column to replace that value (right-click on the column name, then "edit row")

Do you still get the same error if you change your sequential file destination to /dev/null? If yes, if you change your job to go straight from ODBC to a sequential file (with no transform stage)? I'm just trying to see which stage might be triggering your runtime error.

I would normally suggest just using a sequential file input. Can you post the first 10 lines or so of your XML?

kalpna wrote:...i've tried this with XML Spy as well,
it warns the same...

So it is clear that it isn't a DataStage XML error, but a document form error. What does XML Spy report as the error message?

Can you try making a copy and changing the job to work without the folder stage and loading the one XML you already checked to see if the error remains?

I would stick with UNIX. Use a call to "dsjob -ljobs" to get a list of jobs in a project and put that into a list, which you then use in a loop to issue the "dsjob -lparams" and redirect that output to a text file.

There are so many ways available to check this. Try using this web page to cut-and-paste your XML to see if it is well-formed. I suspect that it isn't.

Hashed file loading speed is also dependant upon the ways the primary key hashes into it's appropriate group. If all your writes tend to write into the same or similar groups according to the hashing algorithm, disk pages might have a higher likelihood of being in memory. Could you sort your input d...

tyvix, I'm not sure what you mean by a "uv command". You can use the subroutine call DSGetParamInfo() to get parameter information on a job that has run. Or, from UNIX/Windows command line you can issue the dsjob -paraminfo [-userid] <project> <job|jobid> <param> to get similar information.

Arun, you have just repeated your initial query with a small addition, so the answer is going to be the same. A "core" dump is a file generated by the UNIX error handler that store the memory image of a process including all the stack and register information. UVSH does not create a core file, it is...

Raj,

have you tried opening up the XML document in your xml-enable browser or by using one of the many structure-checking utilities available on the market to make sure that your document is well-formed?