Search found 520 matches

by mhester
Mon Oct 25, 2010 1:40 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Need transformation logic
Replies: 3
Views: 1810

If this is an ongoing requirement for various source systems then I might suggest that you wrap a "character removal/strip" C function and make it available for all to use. If you only need to do it in one place then what was given will work.
by mhester
Mon Oct 25, 2010 1:37 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Config file warning...
Replies: 10
Views: 7036

Swap is physical disk and when configured is identified as swap. You need to get with your OS admin folks to help. As with anything there are various configurations for swap etc... that will affect your implementation, but your initial issue is swap related and has nothing to do with RAM, although r...
by mhester
Mon Oct 25, 2010 12:03 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Config file warning...
Replies: 10
Views: 7036

With an 8 node configuration you would need at least 2.3gb and since that is a bit odd why not just allocate 4gb which is pretty standard for swap and be done with it.
by mhester
Mon Oct 11, 2010 12:35 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: node setting
Replies: 11
Views: 2771

Yes, shell scripting would probably be the best way to do this. ... If, and only if, you wanted to create a configuration that had compute nodes that are available for use and nothing more elaborate. Anything beyond this simple task like "is the compute node in use" or "does the comp...
by mhester
Mon Oct 11, 2010 6:32 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Performance issue in reading 6GB file
Replies: 15
Views: 4859

This issue is probably more closely related to how you have defined the record layout and the output record. If you include the Group etc... then it will take a bunch of time to read the data especially with rows that wide. I just had this issue with an 18gb file and 1800 columns and I was able to g...
by mhester
Mon Oct 11, 2010 6:27 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Output dataset not partitioned as expected
Replies: 11
Views: 4261

set APT_DUMP_SCORE=1 and see what the framework is really doing
by mhester
Thu Sep 23, 2010 10:43 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: hash partioning problem in remove duplicate stage
Replies: 3
Views: 4935

I believe that in scenario 1 it is working exactly as you have coded it. You are partitioning on key and timestamp which will not produce the same data distribution as simply partitioning on the key as in your second scenario.
by mhester
Thu Sep 23, 2010 9:29 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: APT_CombinedOperatorController,0: *** glibc detected *** /op
Replies: 1
Views: 2128

inputstring is a pointer and it has not been initialized. strlen is probably throwing the error. To clarify. I would look at the following - compiler flags - are you pointing to the correct glibc? you could be freeing a null pointer which would cause this error could be getting a sigsegv error, but ...
by mhester
Wed Sep 22, 2010 4:25 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Update DB2 table takes longer time
Replies: 4
Views: 2313

Need a bit more information.
  • 1) Target table size?
    2) Is this a DPF database?
    3) Indexed on the key columns?
    4) What happens when you run the job to /dev/null?
by mhester
Wed Sep 22, 2010 3:32 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Problem with a job running under DS81 that ran fine under7.5
Replies: 3
Views: 1558

Partitioned reads and writes were never available in 8.0 only in 8.1 with the DB2 Connector. DB2 Connector partitioning was available, but the "guts" were not there. The connector makes a call to the DPF DB to read the partition map and db2nodes.cfg for the table being loaded or read and u...
by mhester
Wed Sep 22, 2010 3:19 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Dataset Management does not work from Director or Designer
Replies: 3
Views: 2056

That is what I figured and agree that it should work. Do you know if you have all of the patch levels for the client? Did you open the PMR as a 2 or 3? - if it is a 3 then I would make it a 2 citing the inability for prod support to review rejects etc.... make up something :)
by mhester
Wed Sep 22, 2010 3:15 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Interesting SQL design conundrum
Replies: 6
Views: 3638

I am going to go out on a limb here and give my opinion that as long as the data are not filtered per Kim or Andy's suggestion (not even sure that would work either) and that each instance processes the same table and can run at the same time then it is unlikely that this can be solved with SQL quer...
by mhester
Wed Sep 22, 2010 3:11 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Dataset Management does not work from Director or Designer
Replies: 3
Views: 2056

Bill,

We are also on 8.1 and have not witnessed this behavior, but if you need to view the kinds of information that the Dataset Manager would show have you used orchadmin?

Not meaning to sideswipe your issue.
by mhester
Wed Sep 22, 2010 1:44 pm
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Avoid Job Lock
Replies: 2
Views: 1435

To build on what Andy has given. Also make sure that if a timeout value is given in the Administrator client that folks do not leave a job open and inactive longer than this time. Also, there are a couple of places where jobs get locked - UniVerse and Websphere. If it is a Websphere lock then a sess...
by mhester
Tue Sep 21, 2010 11:45 am
Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
Topic: Problem with a job running under DS81 that ran fine under7.5
Replies: 3
Views: 1558

That is actually contrary to what I have seen. I do not use eSame and have not since the first version of this tool. Auto has always worked. Did you see a repartitioner in the score for the job? If the job that created the dataset used in the scd job was partitioned by columns that are different tha...