InfoSphere 8.5 FP1 - any major known issues?
Moderators: chulett, rschirm, roy
InfoSphere 8.5 FP1 - any major known issues?
Hi Folks,
I'm on a site which has a new Infosphere 8.5 installation.
Before we embark on any development on this new platform i want know if there are any known issues up front instead of bumping into them along the away. So i can get these fixed or raised with the support people while they are still on site.
The configuration is:-
InfoSphere 8.5 fixpack 1.
SUSE Enterprise Linux 10 service pack 3.
Oracle 11gR2 for xmeta and iadb.
SQL Server 2008 and Oracle 11gR2 for source and target databases.
We plan to develop with Oracle Connector and ODBC connector stages.
Any advice greatly appreciated.
Jon
I'm on a site which has a new Infosphere 8.5 installation.
Before we embark on any development on this new platform i want know if there are any known issues up front instead of bumping into them along the away. So i can get these fixed or raised with the support people while they are still on site.
The configuration is:-
InfoSphere 8.5 fixpack 1.
SUSE Enterprise Linux 10 service pack 3.
Oracle 11gR2 for xmeta and iadb.
SQL Server 2008 and Oracle 11gR2 for source and target databases.
We plan to develop with Oracle Connector and ODBC connector stages.
Any advice greatly appreciated.
Jon
Re: InfoSphere 8.5 FP1 - any major known issues?
My target is SQL Server and i used WRITE method along with Surrogate_Key_Generator stage made the job to fail / hang. But this is for Win OS.
I suppose to raise a PMR for this issue.
Workaround is make the SQL Server EE stage to run in sequential mode.
Hence you are using unix, you might use ODBC and not sure how that will behave?.
DS User
I suppose to raise a PMR for this issue.
Workaround is make the SQL Server EE stage to run in sequential mode.
Hence you are using unix, you might use ODBC and not sure how that will behave?.
DS User
Re: InfoSphere 8.5 FP1 - any major known issues?
Thank you, I will keep this in mind, yes ODBC Connector will be used for SQL Server.SURA wrote:My target is SQL Server and i used WRITE method along with Surrogate_Key_Generator stage made the job to fail / hang. But this is for Win OS.
I suppose to raise a PMR for this issue.
Workaround is make the SQL Server EE stage to run in sequential mode.
Hence you are using unix, you might use ODBC and not sure how that will behave?.
DS User
thanks for your commend, we're currently using 8.5 FP1.iHijazi wrote:Major, No.
Minor, yes.
Workarounds, there is.
In the end it's all about what you use. But I recommend using it (upgrading if you are an 8.1 user).
It's always fun to fix issues
Cheers.
I'm working in the best interest of the customer which is to have a fully functioning product for development and to build confidence for delivery.
If i can be aware of the issues big or small beforehand all the better.
-
- Participant
- Posts: 11
- Joined: Wed Mar 16, 2011 5:56 am
some issues
We upgraded to 8.5 FP1 and noticed the following in the Designer client :
- the fan-symbols on the links have disappeared. However, you can still see them in the pop-up that comes up when you move your mouse over the job-name in the repository window
- in the sequential file stages, you can use DOS format for UNIX-files and vice versa, withought Designer complaining
We are not 100% sure we notice this behaviour since we installed the FP but lets say 90 %
- the fan-symbols on the links have disappeared. However, you can still see them in the pop-up that comes up when you move your mouse over the job-name in the repository window
- in the sequential file stages, you can use DOS format for UNIX-files and vice versa, withought Designer complaining
We are not 100% sure we notice this behaviour since we installed the FP but lets say 90 %
I want to add the problem of "Cannot insert LONGVARCHAR data into Oracle function SDO_GEOMETRY"
This is a known issue to IBM.
The problem is of not being able to pump more than 4000 characters to a function that can accept LOB that is within an Insert statement.
This problem has been identified so far with the Oracle Connector Stage.
I already have this problem described in a separate forum thread.
This is a known issue to IBM.
The problem is of not being able to pump more than 4000 characters to a function that can accept LOB that is within an Insert statement.
This problem has been identified so far with the Oracle Connector Stage.
I already have this problem described in a separate forum thread.
I want to add the problem of "Cannot insert LONGVARCHAR data into Oracle function SDO_GEOMETRY"
This is a known issue to IBM.
The problem is of not being able to pump more than 4000 characters to a function that can accept LOB that is within an Insert statement.
This problem has been identified so far with the Oracle Connector Stage.
I already have this problem described in a separate forum thread.
This is a known issue to IBM.
The problem is of not being able to pump more than 4000 characters to a function that can accept LOB that is within an Insert statement.
This problem has been identified so far with the Oracle Connector Stage.
I already have this problem described in a separate forum thread.