DSXchange

No use at all, but it is there; kind of like an appendix.

I guess I misunderstood the question as well. So you are looking at running either Windows 2003 or Linux on the IBM Blade Server that will host the DS Engine - same HW but different OS's? I always envision Windows to use a lot more of the system resources than UNIX and be less efficient with process...

The repository database is not heavily used (compared to a DWH or staging DB) so any performance differences should be negligible. More important is your choice of platform for the actual DS Engine and for the DWH database or target - their configuration and sizing will have a much more significant ...

The differences overall between the two OSs for the repository are not that significant and chances are high that you won't notice any differences from DataStage. This means the decision is not truly technical but related to your infrastructure. Do you have more OS level expertise on one platform or...

Welcome to DSXchange.

Use APT_DISABLE_OPERATOR_COMBINATION set to "false" to see which stage is generating the error. Also, search the forum for posts with the keyword "TRUNCATED_CHAR_FOUND" to see if any of those threads describe your problem.

In most client scenarios the actual Model used to build the warehouse is a home-grown solution and often reflects the company's way of looking at and using data. There are a couple of different basic business-specific models that are available for purchase, but even these are usually highly modified...

What floating point error do you get after changing the scale?

export the job to a .dsx file and edit the RCP tag and re-import it.

Check the stage output link to ensure that RCP is indeed turned off; perhaps this job was imported from a project where RCP was enabled.

I'm not sure that there is a limit that you can reach, as DataSets use multiple physical files to store data.

Put in a dummy transform as suggested, with straight pass-through of columns and see what happens on compile and run.

The "IDENT1" means it is a dummy stage inserted between two passive stages in the job. Are you certain that this is a Parallel job and not a Server job? What passive stages do you have in the job that are next to each other (i.e. source/target file or database stages)

Now I have the query that can i directly migrate it by automatic upgrade as specified in the previous posts?? Yes, export from the old, import in the new. Or Else should I first do a 5.22 to 7.5 server and then 7.5 server to 7.5.2 parallel? I am not sure why you would need to do this. Also do I nee...

Can you try putting the result of the Macro into a VarChar column as a test, perhaps this macro is typed as a varchar and not working for some reason.

That is very odd indeed. What about "COUNT VOC USING DICT VOC", does that return the same error as "COUNT DS_JOBOBJECTS USING DICT VOC"?