DSXchange

The "logic" is that you name them as pivoting columns ColA, ColB and ColC in the Pivot stage properties.

Microsoft says it's introducing a subscription security service that will "make it easier for network technicians at big businesses to make sure computers don't fall prey to spyware or virus attacks." No way. They're serious? Scott Stanzel, Senior Product Manager in Microsoft's security technology u...

A quick way to test this is to change your "Lookup Unsuccessful" rule to Fail. Your job will abort on the first unsuccessful lookup. You can always change it back again.

Do NOT provide a key value from the DataStage job Columns collection. Your SQL should then have the form: INSERT INTO tablename(key_col, col2, col3, ...) VALUES (sequencename.NEXTVAL, :1, :2, ...) Make sure there are as many non key column references in the column names clause and pa...

Please sketch out your job design. In particular, does the Lookup stage precede or follow the Transformer stage?

Performing any arithmetic operation in a DataStage BASIC expression, such as adding zero to the number, will strip non-significant leading and trailing zeroes.

You might also investigate the Field() function, which is slightly more efficient that the group conversion you have chosen to do.

This is a known bug when connecting a 7.5x2 client to a 7.5.1 server. It may occur with other combinations also. As far as I am aware there is no fix for it yet.

You need to test explicitly for failure to attach jobs (clearly a job that has not been compiled will not have any run status) and bypass them. Any error in DSAttachJob returns an error code which is an integer less than zero. hJob = DSAttachJob(JobName, DSJ.ERRNONE) JobName = DSGetJobInfo&#...

Jobs in production should not generate any warnings, imho. So inspecting any generated warnings in the job log is an absolute must.

Your date is OK, but it's not a timestamp. Append " 00:00:00" to it using concatenation.

Ha, another one brainwashed by Oracle bin Larry! VARCHAR2 only exists in Oracle - the OP made no mention of Oracle. NVarChar (the "Standard" representation) does use two bytes per character. You (srinivas_dsx, and welcome aboard) can try using Long NVarChar for larger data. Or change the data type t...

It was working fine before the security patch. Now it isn't. Hmm?

When you have eliminated the impossible (nothing has changed in DataStage) everything else is the possible. -- Sherlock Holmes

Do you see the same problem with any of the other partitioning algorithms? This is a very surprising finding - Round Robin is about as simple as you can get! Can you please post the actual row counts from the output links of the Link Partitioner stage? And verify that you have row buffering enabled,...

Post the complete error message via copy and paste from the job log. Do not edit it in any way.