Issue with DataStage 9.1 upgrade
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 36
- Joined: Mon Mar 03, 2014 3:09 am
Issue with DataStage 9.1 upgrade
We are working on DataStage upgrade from 8.0.1 to 9.1 version
We are facing the below issues during upgrade
1. Performance issue - parallel engine job startup times taking more time
2. Few Jobs getting hung when parameter APT_NO_BUFFERING_FUNNEL_INPUT=1 is set
3. The sort & remove duplicate (stages) algorithm is behaving differently between 8.0.1 and 9.1
4. Join stage with same input links is behaving differently in DS9.1 (auto partition).
5. Warnings are more in 9.1 compared to 8.0.1 for the same job
Can you please let us know whether we have faced these issue in any upgrade projects?
Also will we face the same issue if we upgrade to 8.5 instead of 9.1??
We are facing the below issues during upgrade
1. Performance issue - parallel engine job startup times taking more time
2. Few Jobs getting hung when parameter APT_NO_BUFFERING_FUNNEL_INPUT=1 is set
3. The sort & remove duplicate (stages) algorithm is behaving differently between 8.0.1 and 9.1
4. Join stage with same input links is behaving differently in DS9.1 (auto partition).
5. Warnings are more in 9.1 compared to 8.0.1 for the same job
Can you please let us know whether we have faced these issue in any upgrade projects?
Also will we face the same issue if we upgrade to 8.5 instead of 9.1??
1. Haven't seen it
2. Never used that option. Why are you turning buffering off on the funnels?
3. Can you quantify "different"? How? What behavior?
4. Again, what is "different"?
5. Most definitely. Starting at 8.1 and again at 8.5 the metadata rules were more strictly enforced, resulting in numerous warnings as jobs are now reporting their metadata doesn't match the metadata on the database. Job should be updated to match. What other types of messages are you seeing?
Null handling did change between 8.0.1 and 9.1 along with some other items which might be causing the join problems among other things.
Refer to this tech note for details on compatibility issues between those releases http://www-01.ibm.com/support/docview.w ... wg21459416
Did you also turn on NLS? If so, there are other issues related to enabling NLS. viewtopic.php?t=151139
2. Never used that option. Why are you turning buffering off on the funnels?
3. Can you quantify "different"? How? What behavior?
4. Again, what is "different"?
5. Most definitely. Starting at 8.1 and again at 8.5 the metadata rules were more strictly enforced, resulting in numerous warnings as jobs are now reporting their metadata doesn't match the metadata on the database. Job should be updated to match. What other types of messages are you seeing?
Null handling did change between 8.0.1 and 9.1 along with some other items which might be causing the join problems among other things.
Refer to this tech note for details on compatibility issues between those releases http://www-01.ibm.com/support/docview.w ... wg21459416
Did you also turn on NLS? If so, there are other issues related to enabling NLS. viewtopic.php?t=151139
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Found something that might be pertinent to the slow startup times for PX jobs.
You'll need a valid IBM login id to access this: https://www-304.ibm.com/support/entdocv ... wg1JR49593
Text is below:
JR49593: INFORMATION SERVER 9.1 PARALLEL JOBS HAVE LONG STARTUP TIMES DURING SCHEMA SETUP
Investigation has shown that there is an un-needed function call inside PX schema distribution code which slows down performance on some systems
Status: Open
You'll need a valid IBM login id to access this: https://www-304.ibm.com/support/entdocv ... wg1JR49593
Text is below:
JR49593: INFORMATION SERVER 9.1 PARALLEL JOBS HAVE LONG STARTUP TIMES DURING SCHEMA SETUP
Investigation has shown that there is an un-needed function call inside PX schema distribution code which slows down performance on some systems
Status: Open
Again you will hit same issue even 8.5.
We migrated 8.5 to 9.1. It looks like IBM released almost 15 to 20 fixes between 8.5 to 9.1. But we are seeing lot of improvement in 9.1 compare to 8.5.
It looks like you guys using very old version (8.0.1). Better to move 9.1 and also try to redesign some of old jobs which is designed on 8.0.
Thanks
Man
We migrated 8.5 to 9.1. It looks like IBM released almost 15 to 20 fixes between 8.5 to 9.1. But we are seeing lot of improvement in 9.1 compare to 8.5.
It looks like you guys using very old version (8.0.1). Better to move 9.1 and also try to redesign some of old jobs which is designed on 8.0.
Thanks
Man
One issue that we have observed on 9.1.2 (Solaris 64 with windows client) is that at times when the PX Oracle Connector of a readonly job is opened (when another client has job open), it will not show the Connector Properties tab, but reverts to the standard property editor. Similar issue was also observed for Db2Connector, though more severe - DSDesigner crashes.
Our support provider is looking into these issues. Based on what I could gather, few other shops are also facing this issue.
Our support provider is looking into these issues. Based on what I could gather, few other shops are also facing this issue.
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
Is number five - more warning messages - due to the use of a message handler that hasn't been migrated between versions? Have a look in the 8.0.1 DataStage Administrator to see if the project has a default message handler that downgrades or hides certain warning messages.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn