Search found 103 matches
- Mon Jun 04, 2012 5:23 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: SCD Type 2 producing incorrect inserts
- Replies: 7
- Views: 5075
Wow, how did you do that!? It's as though you're looking over my shoulder. Yes, I had missed that the input column was Unicode and the dimension column wasn't. But correcting this oversight still didn't fix the problem. Stranger still, it still shouldn't find a match when running on 1 node. I'm gett...
- Sun Jun 03, 2012 10:29 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: SCD Type 2 producing incorrect inserts
- Replies: 7
- Views: 5075
Thanks for the response Craig, but it didn't fix things. The Score now shows: . . . ds2: {op1[4p] (parallel copyPlaceholder4) eAny=>eCollectAny op2[4p] (parallel copyPlaceholder4:RF02Before-FILTERED)} ds3: {op1[4p] (parallel copyPlaceholder4) eAny=>eCollectAny op7[4p] (parallel APT_TransformOperator...
- Sun Jun 03, 2012 6:53 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: SCD Type 2 producing incorrect inserts
- Replies: 7
- Views: 5075
SCD Type 2 producing incorrect inserts
Problem: - When rerunning the job with no changes to the source data, the SCD stage identifies all rows as new inserts. - This problem does not occur when running on a single node. SCD configuration: - Input partitioning tab: The dimension link partitioning=Auto; the input link partition=Hash on BA...
- Wed May 23, 2012 8:24 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Stage Variables allowing calculations with null operands
- Replies: 3
- Views: 4086
- Wed Mar 28, 2012 10:32 pm
- Forum: General
- Topic: Escaping # in Execute Command definition
- Replies: 4
- Views: 3424
- Wed Mar 28, 2012 6:28 pm
- Forum: General
- Topic: Running multiple jobs
- Replies: 5
- Views: 2003
- Wed Mar 28, 2012 6:05 pm
- Forum: General
- Topic: Escaping # in Execute Command definition
- Replies: 4
- Views: 3424
Escaping # in Execute Command definition
Requirement: We need to read a text file that has a record for each of the tables to be loaded. The file can have comment lines, which begin with a #. e.g. #Batch Code, Source File, Schema File, Target Table, Key Field(s) #PRS tables PRS,PRS-EMPLOYEE-*-EXTRACT.DAT,EmployeeFile.schema,EMPLOYEE,EMP_I...
- Sat Feb 11, 2012 1:42 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Performance of repartitioning
- Replies: 5
- Views: 2478
If it were a cartesian join then we'd have 500,000,000 rows. :) Yes, thanks qt_ky. SURA made that point too. The 20K was just some test data I had lying around. It is also indicative of the numbers we can expect in production, so you're right that in this case, Clear ing the partitioning will have n...
- Fri Feb 10, 2012 12:12 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Performance of repartitioning
- Replies: 5
- Views: 2478
- Thu Feb 09, 2012 7:46 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Performance of repartitioning
- Replies: 5
- Views: 2478
Performance of repartitioning
Problem: If we run the batchflow with a different number of nodes, some jobs fail with the message: There are irreconcilable constraints on the number of partitions of an operator: parallel copyPlaceholder05. The number of partitions is already constrained to 2, but an eSame partitioned input virtu...
- Fri Nov 18, 2011 5:09 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Input buffer underrun
- Replies: 2
- Views: 2660
- Thu Nov 17, 2011 8:41 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Input buffer underrun
- Replies: 2
- Views: 2660
Input buffer underrun
Requirement: We have a job that reads a dataset, makes the required changes, and overwites the dataset. To do this, we write to a temporary dataset, and after the job completes successfully, we "rename" the temporary dataset to the proper dataset name (using orchadmin copy ). Problem: We ...
- Wed Aug 03, 2011 5:51 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Improving performance of DB2 insert
- Replies: 3
- Views: 6689
- Tue Aug 02, 2011 11:26 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Improving performance of DB2 insert
- Replies: 3
- Views: 6689
Re: Improving performance of DB2 insert
Thanks Michael. It's good to know we're on the right track. Now we just need to get the bulk load working! [Edit: the job fails with the 262276 message before writing the message file] Since we saved so much time by dropping indexes, we plan to use the "do not update table indexes" option,...
- Tue Aug 02, 2011 9:45 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Improving performance of DB2 insert
- Replies: 3
- Views: 6689
Improving performance of DB2 insert
Requirement: We are trying to improve the performance of a simple load job: Sequential File -> Transformer (adding some metadata columns) -> Db2Connector The job was taking ~15 minutes to load 4,117,660 rows (the average rowsize is 244 bytes). The job was run using 2 nodes, which looks like it runs...