Migration from v 8.0 to v 8.1
Moderators: chulett, rschirm, roy
Migration from v 8.0 to v 8.1
Hello folks,
I was wondering if there is any reason for an upgrade from 8.0 to 8.1 ?
By the way I don't see any new significant stage compare to the 7.5.2.
Looks like few people are now working on the server version.
thanks.
I was wondering if there is any reason for an upgrade from 8.0 to 8.1 ?
By the way I don't see any new significant stage compare to the 7.5.2.
Looks like few people are now working on the server version.
thanks.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
There are no new stage types compared to 7.5. Why would there be? There are new versions of some (stage types are versioned independently of the base product). There are some new items of functionality, such as parameter sets.
The main reason to upgrade from 8.0 to 8.1 is that there are fewer bugs in, and fewer patches required for, the latter. Most of the new functionality is in parallel jobs and tools that work with them, such as dynamic optimization.
The main reason to upgrade from 8.0 to 8.1 is that there are fewer bugs in, and fewer patches required for, the latter. Most of the new functionality is in parallel jobs and tools that work with them, such as dynamic optimization.
Last edited by ray.wurlod on Tue Feb 17, 2009 2:55 pm, edited 1 time in total.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 612
- Joined: Thu May 03, 2007 4:59 am
- Location: Melbourne
Check out the release notes:
New features and changes in Version 8.1 IBM InfoSphere Information Server
Notable one: DataStage logging was changed at release 8.1 to log job run detail records into the operational repository, (xmeta) rather than the local project level log files, (RT_LOGxxx) that we utilized in prior releases for each job. Which ended up giving performance impact and also resulted in missing log entries in some cases. Vendor suggests modification of 2 DSparams to revert to pre 8.1 logging.
New features and changes in Version 8.1 IBM InfoSphere Information Server
Notable one: DataStage logging was changed at release 8.1 to log job run detail records into the operational repository, (xmeta) rather than the local project level log files, (RT_LOGxxx) that we utilized in prior releases for each job. Which ended up giving performance impact and also resulted in missing log entries in some cases. Vendor suggests modification of 2 DSparams to revert to pre 8.1 logging.
Joshy George
<a href="http://www.linkedin.com/in/joshygeorge1" ><img src="http://www.linkedin.com/img/webpromo/bt ... _80x15.gif" width="80" height="15" border="0"></a>
<a href="http://www.linkedin.com/in/joshygeorge1" ><img src="http://www.linkedin.com/img/webpromo/bt ... _80x15.gif" width="80" height="15" border="0"></a>
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
Not to mention that finding and looking at log files through Director is easy but finding and looking at log messages through the Information Server Reporting is a pain. The old logging is better. The main reason for going to 8.1 is all the products other than DataStage and QualityStage are much better. Workbench, Information Analyser, Glossary and FastTrack are more stable, have more functions and are easier to use.
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
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 278
- Joined: Wed Oct 03, 2007 8:45 am
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
I cannot find that stage, I'm on 8.1 and it is not mentioned in the documentation and it is not installed in my Designer. I can see an ODBC Connector and a Teradata Connector but my only DB2 stages are Enterprise, UDB and Z. It's funny that the Teradata Connector is there but not DB2 - no signs of favouratism for IBM databases!
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
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
I cannot find that stage, I'm on 8.1 and it is not mentioned in the documentation and it is not installed in my Designer. I can see an ODBC Connector and a Teradata Connector but my only DB2 stages are Enterprise, UDB and Z. It's funny that the Teradata Connector is there but not DB2 - no signs of favouratism for IBM databases!
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
The DB2 connector stage and distributed transaction stage are downloaded as a separate patch. There are 7 patches in total that need to be installed, 4 on the server side and 3 on the client side. You can download the patches from the following link: http://www-01.ibm.com/support/docview.w ... ss=ct14db2
I did see some slide from IOD 2008 about an Oracle connector but looks like it did not make this release.
I did see some slide from IOD 2008 about an Oracle connector but looks like it did not make this release.
Just got the DB2 connector installed. Note: This stage is only available in Parallel jobs. After installing I am able able to insert data in parallel. No complicated configuration required. The bulk load did not work out of the box. Looks like there is an issue with the default DB2 client installed with version 8.1 which results in the following error:
"write" mode set to "bulk load" fail with the SQLCODE SQL3009N
There is a patch available: http://www-01.ibm.com/support/docview.w ... wg21322938
Images of the new connector:
[/b]
"write" mode set to "bulk load" fail with the SQLCODE SQL3009N
There is a patch available: http://www-01.ibm.com/support/docview.w ... wg21322938
Images of the new connector:
[/b]
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
At some point the connectors will also be available in server jobs. They are supposed to supercede enterprise stages and server database stages. Taking IBM a long time to roll them out.
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
Hi all
Thanks
Can you tell me what the params are and where i can find themNotable one: DataStage logging was changed at release 8.1 to log job run detail records into the operational repository, (xmeta) rather than the local project level log files, (RT_LOGxxx) that we utilized in prior releases for each job. Which ended up giving performance impact and also resulted in missing log entries in some cases. Vendor suggests modification of 2 DSparams to revert to pre 8.1 logging.
Thanks
-
- Premium Member
- Posts: 278
- Joined: Wed Oct 03, 2007 8:45 am
Yah, nice to mention "2 params" and then not name them. Here's a thread with the details:
viewtopic.php?t=125607
viewtopic.php?t=125607
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers