abhilashnair wrote:What if the output from DB2 is grouped but not sorted? What should be the partition method to bbe used in the Sort stage? Currently it is Auto.
Look in the Oracle "bad" file and "log" file for additional diagnostic information. This message has been reported by the Oracle bulk loader (sqlldr), not by DataStage. DataStage has simply logged it when it was received.
If you're executing the same SELECT on each partition you're effectively getting Entire partitioning. If that's not what you want, you're going to have to constrain the query appropriately and/or select in sequential mode and choose an appropriate partitioning algorithm.
You use a configuration file that makes reference to this node (as a fastname) and puts it in the conductor node pool. You set APT_CONFIG_FILE to point to this configuration file. Then you visit the Advanced tab in the stage and select the conductor node pool.
With DB2-Connect you can expose tables from one database on another. You can then effect your joins. IBM Information Integrator is another way that you might access these data.
Because of flexibility. Any vendor solution like the SAS one, or the SAP one, will tend to lock you in to that vendor's products. What happens, in three or four years, when you go through a merger or acquisition, and suddenly need to support other systems? DataStage has that flexibility.
In Designer, select New > Data Migration Job - it's there and works in 7.5x2 at least. ProfileStage allows you to generate a source to target mapping specification (including DataStage expressions) based on its results and/or imported metadata and, from that, can generate the DDL to create the targe...