DSXchange

It may be possible but is still not supported (unspported combinations are begging for errors...).

That error is still unrelated to your DB2 software and dsenv changes.

You should still contact support about it, unless you want to delete the stage type definition and rebuild it in each project on your own. Sounds like it's corrupted.

Search the IBM Support Portal on the error message and find 0 results. That's a sure sign it's not a common problem...

Did you resolve it?

No; it's not dependent on version. From Unix ODBC SQL Server drivers, it is a requirement to use SQL Server authentication. Windows authentication is only for Winodws platforms.

It only indicates edits if you edit after someone has replied...

I'm not sure there is reason to be concerned about infinite loop, especially if it tested fine on 1.4 million records already. You could run your own load test by concatenating your input file many times over or generating say 200 million records to test it with. Another possible way to detect this ...

vamsi.4a6 wrote:1)why can not we use disable constraints oracle statement in Before SQL (node) statement for oracle connector stage for child table?

Read the topic again and you may interpret the reason as being a stubborn DBA: "i tried that but they would't disable the constraints."

The reason is given in the first 2 lines of this topic, but here it is again: These files have date suffix in the name but the file name is distinct. e.g A_02122012,B_02122012 etc. And one can easily imagine that the date suffix in each file name will change every day. Unix date command is one way t...

"The Stagetype 'DB2ConnectorPX' cannot be found in the repository' That error is unrelated to your DB2 software and dsenv changes. You should be able to add that stage type into any job whether or not the server is configured with DB2 Connectivity. Try adding a variety of other stage types to ...

arvind_ds wrote:Ideally number of nodes in the configuration file = Half the cores.

I think the above rule of thumb is a good starting point rather than an ideal ending point.

If you're installing server tiers onto Windows platform, make sure you install it according to the system requirements (i.e. install on Windows Server 2008).

Check the DataDirect web site and/or product manuals for database versions supported by the ODBC drivers.

Also check with DataStage Support to get confirmation.

This topic has been discussed here as well:

viewtopic.php?t=145041

Review my suggestions from this topic...

viewtopic.php?t=145389

Don't run AV software on the server. That's a good reason why! So, you need to find a way to restore that file. Can you restore from backup or copy it over from another server?

If some jobs don't show, something can be corrupted. You can try opening the job from Designer repository, saving it as a new name and deleting the old job from there. Naming it back, etc.