Search found 773 matches

by keshav0307
Mon Mar 29, 2010 12:22 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: how to read multiple stages in datastage one by one
Replies: 14
Views: 6810

Read 1st file, and write into a sequential file(file_1), and in the output of the file_1 read the 2nd file, and append to file_1 , again in the output read 3rd file and append to File_1
by keshav0307
Sun Mar 28, 2010 11:05 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: how to read multiple stages in datastage one by one
Replies: 14
Views: 6810

Server job it is certainly possible and easy to implement. Parallel , possible, tricky. and probably not very useful. i don't have PX environment now so can't test. try this take the last records from 1st file as refrence input to the second file using lookup stage, so that the second file will wait...
by keshav0307
Sun Mar 28, 2010 8:12 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: how to read multiple stages in datastage one by one
Replies: 14
Views: 6810

Assuming you need to do some data validation of each file, and that's the reason you can't combined 3 files into 1 (using cat command etc.) .

you can have a single job with multi instance, to append into a single file, from the three(or more) instance of job.
by keshav0307
Thu Mar 25, 2010 10:19 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: data not reterving from teradata stage
Replies: 4
Views: 1666

are you using user defined Query?? can you post the query.

is it throughing any error or warning??
by keshav0307
Mon Mar 22, 2010 6:06 pm
Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
Topic: Protected Ptoject question ?
Replies: 1
Views: 1382

NO
by keshav0307
Mon Mar 22, 2010 5:56 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: lookup stage problem
Replies: 5
Views: 2085

can you put some example of source1 and source2 data. and what is you are expecting in the output
by keshav0307
Mon Mar 22, 2010 1:41 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Job failing with warnings
Replies: 3
Views: 1446

In the source table the column type is decimal[28,0],
whereas in the OEE stage, the coulmn is defined as Integer.
by keshav0307
Thu Feb 25, 2010 8:04 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: TRansformer
Replies: 4
Views: 2464

not sure if it can be done in Parallel.
but in a server job, using link partition(hash partition on that column) will do.
by keshav0307
Wed Feb 17, 2010 11:07 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Join of tables with huge volume of data - scratch space
Replies: 8
Views: 4840

for large volume of data to join, more number of nodes.

can you post the content of configuration your are using for this job?
by keshav0307
Sun Feb 07, 2010 1:41 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Multiload stage received signal SIGSEGV
Replies: 1
Views: 1645

check the Mload Log file for detail error.
by keshav0307
Thu Feb 04, 2010 11:32 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Dataset Query
Replies: 10
Views: 3537

the second job should also have four node to read the dataset..
so if you want to process the data in 2 node in second job, then make the other two node in "read only" pool.
by keshav0307
Thu Jan 21, 2010 7:42 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Oracle Enterprise stage errors out
Replies: 1
Views: 1209

may be the scratch area is not enough to hold the input data in join stage.
by keshav0307
Tue Jan 12, 2010 8:34 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: grid issue : main_program: Accept timed out retries = 16
Replies: 2
Views: 4413

in the grid queue , all the compute node is busy.. command qstat will show how many jobs already in queue... so delete the jobs from grid queue using qdel .......

by disabling the grid, you are by passing the queue, and overloading the compute node.