DSXchange

Linky?

You and Kumar are a little... out of sync. The 'deadlocks' Kumar mentions are within DataStage and are totally unrelated to the issue you are facing in your Informix database. Without intimate knowledge of your job design, it would be hard to say exactly what is going on. You are either running into...

It can't find the sort command. I accidentally removed the leading slash when copying it from your message, so you'll need to add it back in. I've corrected my previous post as well. Try it again with "/usr/bin/sort -u" in the filter command.

I'm not aware of any mechanism to do so. The 'current working directory' of any job is the Project that it is running in so relative pathed files would be relative from there.

Best to fully path any files and use job parameters to specify those paths, in my opinion.

Don't redirect your output. The filter command option changes the stage to read from standard in, so that defeats the whole purpose. So, put /user/kolluria/work/ipfiles/out0126.dat in the normal file name area and then just: /usr/bin/sort -u in the filter command and you should be good to go.

Are you actually trying to bulk load an Oracle 7.x database? You may need to contact Support on this, I don't recall ever actually having used the stage in question... sorry.

Sorry, I don't even have that plug-in loaded here as we've no need for it. I assumed it would have the fairly standard 'Tables' section like ODBC has or a 'From' section ala OCI. Sounds like you have it all under control, in any case.

Interesting.... the ORABULK stage in 7.0.1 had both modes.

Can you go into Manager, find the stage listed under Stage Types and let us know the date and version number on it for grins?

This is all available with a search of the forum. Arnd has covered it but there is also a 'Full Wurlod' on the subject from Ray as well.

Interesting note in the readme for 7.5.1A mentioned that they will no longer log these 'Printer memory segment' messages. FYI.

What version of DataStage? Are you running this in Manual or Automatic mode?

Since your source file has nothing at all to do with the output file why not approach the matter differently. Take a dummy source file with more rows than you want to generate and read it in a simple job. Ignore any columns from that source file, in your transform stage just set the output column v...

so should it be: owner.tablename.column? Ack! Messed up the example, I'll need to go edit that. You could fully qualify it but you shouldn't have to typically there. Qualify the tablename in the Table / From section. So, owner.table and table.column should get you where you need to get. Assuming th...

No, you cannot. If you need different column sets for insert versus update, you'll need two links.

The problem I am having is in the source OLEDB stage, 2 of the columns (eg. ORDERID and ITEMID) are in common with 2 of the tables. In other words, there is a ORDERID and ITEMID in, say, 2 of the sources tables that are named the same. So when the SQL is generated there is a conflict because it doe...