Differences between ORAOCI8 2.2 and 2.3
Posted: Wed Mar 07, 2001 2:44 am
I have logged this with Informix today (hi Louise), so while they are researching it, I was wondering if anyone else in this group has encountered this problem.
We are currently using DataStage 3.5 and extensively use the ORAOCI8 plugin (version 2.2). When doing a reference lookup with this plugin, if multiple rows are returned, only the first is used. The others are discarded.
There are some situations where I use fuzzy matching and sort the rows so as to get the best match as the first of the rows returned.
I have been looking forward to DataStage 4.x as it has the ability to optionally return multiple rows which would also be very helpful for me in some situations. Unfortunately, it appears that this is only available for UniVerse and ODBC stages, not plugins.
We have started testing our jobs on DataStage 4.1.1
Unfirtunately, the behaviour of the ORAOCI8 ver 2.3 plugin (which came with DS 4.1.1) has caught me completely by surprise. When multiple rows are returned, it generates an Oracle error. It would appear that this newer plugin now explicitly tells Oracle that it only wants a single row. If the query returns more than one row then you get an Oracle error.
Has anyone else encountered this? Is there anything that can be done about it?
Thanks,
David Barham
Information Technology Consultant
CoalMIS Project
Anglo Coal Australia Pty Ltd
Brisbane, Australia
e-mail: David.Barham@anglocoal.com.au
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else.
We are currently using DataStage 3.5 and extensively use the ORAOCI8 plugin (version 2.2). When doing a reference lookup with this plugin, if multiple rows are returned, only the first is used. The others are discarded.
There are some situations where I use fuzzy matching and sort the rows so as to get the best match as the first of the rows returned.
I have been looking forward to DataStage 4.x as it has the ability to optionally return multiple rows which would also be very helpful for me in some situations. Unfortunately, it appears that this is only available for UniVerse and ODBC stages, not plugins.
We have started testing our jobs on DataStage 4.1.1
Unfirtunately, the behaviour of the ORAOCI8 ver 2.3 plugin (which came with DS 4.1.1) has caught me completely by surprise. When multiple rows are returned, it generates an Oracle error. It would appear that this newer plugin now explicitly tells Oracle that it only wants a single row. If the query returns more than one row then you get an Oracle error.
Has anyone else encountered this? Is there anything that can be done about it?
Thanks,
David Barham
Information Technology Consultant
CoalMIS Project
Anglo Coal Australia Pty Ltd
Brisbane, Australia
e-mail: David.Barham@anglocoal.com.au
This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender by return e-mail, and delete this e-mail from your in-box. Do not copy it to anybody else.