DSXchange

You will need to specify an -itag option so that the second installation uses different shared memory key. Read all about it in the installation instructions.

Build a table definition and view its parallel layout to get the correct syntax.

This is a different error than the syntax error you had before. DSJE_BADPARAM means one of three things: there is no parameter set called project_param_set in the project there is no parameter called data_path in the parameter set the parameter set has not been loaded into the job design Please veri...

Try it with no space between the "]" and the "{".

Four jobs. One to make the decision about what to do, based on table_a1 and whether the first run has occurred. The other three to do one each of the tasks you described. Triggers or Nested Condition activity to perform the logic in the sequence.

What Craig is intimating is that you have a -param in the dsjob command line and another in the value of the psValue shell variable. The dsjob command objects to what becomes an empty -param argument. Think about what the expanded command would look like.

Stop pushing, especially on weekends. People post as, if and when they can. If they feel like it. There is no compulsion.

Please document the specification for what has to occur - the target-from-source mappings, if you will - in English. (Doing so may even help you to an unassisted solution.)

It is not mandatory for metadata in DataStage ("UniVerse") tables to be complete. There is always an @ID - this is the physical key. Try LIST.DICT VOC to see what is defined for VOC. SELECT * is governed by the existence of an @SELECT entry in the file dictionary or, if that is not present...

The server routine would need to: attach to the job (DSAttachJob) open the text file (OpenSeq or OpenSequentialFile) read through its log (DSGetLogSummary, DSGetNewestLogId, DSGetLogDetail) write required information to text file (WriteSeq) close text file (CloseSeq) detach from job (DSDetachJob) ha...

hargun wrote:can anyone advise me to solve this error.

Stop trying to insert duplicate key.

You are trying to insert a row that has a key value that already exists in the table. The database server is - correctly - preventing you from doing this.

Use "dot notation".

My bad. I didn't notice you're doing a sparse lookup. A sparse lookup expects no duplicates - it expects that you're doing a lookup on the primary key (or some other column supported by a unique index).

Be careful of what you wish for. What happens if you invoke View Data on a table contains many crores of rows?

Or are you being paid by the hour?

Not unless you write one yourself. I don't think it's that easy a task. Try formulating the specification in English of what you would need to do to implement this logic, and we can take a look at that to see whether any solution springs to mind. Is the longest path likely always to be the final one...

First question (from a non-Netezza person): are the NZLoad log files in text format or in some binary format? Second question: if they are in text format, is there any consistency to the layout of lines - that is, other than treating the line as a single VARCHAR, is there any metadata you could appl...