DSXchange

This is actually quite relevant! If I'm not mistaken, Java Integration stage was introduced in DataStage 9.1 and expands over capabilities in interacting with vendors APIs. Will definitely explore what can be achieved using Java to interface the SDO_GEOMETRY API Will post any findings worth of menti...

One business application is triangulation, that is you may want to find the most likely geo-localization of a point interest, from the data sent from SCADA devices, for instance. To the best of my knowledge more or less elaborate triangulation algorithms are implemented in SDO_GEOMETRY. Therefore, y...

Hello all, I am relatively new to spatial data and APIs. Have the following business requirement, to implement in DataStage: a. Read Geo-Localization data from flat file dumps, originating from an Oracle source; b. Transform and operate on read Geo-Localization data; and c. Load transformed Geo-Loca...

Unfortunately, an explicit conversion won't help, as far as my understanding goes. The whole purpose of using a "Column Import" stage is to parse the source text file, read as a LongVarChar; break it down into a collection of records, by means of the Orchestrate schema provided; and delive...

Parallel job parses a source file, using a schema and a Column Import stage. Delivers to a dataset.

62815 records involved. 4 timestamp columns to be delivered.

Job warns on a Broken pipe and ends up aborting on a SIGSEGV.

May the 62815 * 4 implicit conversions varchar to timestamp be an issue?

To complement the previous post from chulett: Operations Console has become available in release 8.7, launched around November 2011 and further enhanced in version 9.1 with the notable addition of a Workload Management feature.