Hi everybody.
Does anybody know the difference between the objects 'Oracle OCI' and 'Oracle Connector'?
Do they work different? When should I use one or the other?
The thing is, I need to load a large amount of data.
PS. I am working with a Server job.
Thank you so much.
Best Regards,
Difference between 'Oracle OCI' and 'Oracle Connector'
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 298
- Joined: Tue Aug 26, 2008 12:17 pm
Difference between 'Oracle OCI' and 'Oracle Connector'
Joyce A. Recacho
São Paulo/SP
Brazil
São Paulo/SP
Brazil
-
- Participant
- Posts: 22
- Joined: Thu Apr 19, 2012 3:31 am
- Location: India
With Oracle OCI, you can:
Generate your SQL statement.
Use a file name to contain your SQL statement.
Clear a table before loading by using a TRUNCATE statement. (Clear table)
Select how often to commit rows to the database. (Transaction size)
Input multiple rows of data in one call to the database. (Array size)
Read multiple rows of data in one call from the database. (Array size)
Specify transaction isolation levels for concurrency control and transaction performance tuning. (Transaction Isolation)
Specify criteria that data must meet before being selected. (WHERE clause)
Specify criteria to sort, summarize, and aggregate data. (Other clauses)
Specify the behavior of parameter marks in SQL statements.
Oracle OCI is dependent on the libclntsh shared library, which is created during the installation of the Oracle client software. You must include the location containing this shared library in the shared library search path for InfoSphere DataStage jobs to run successfully by using this stage.
Refer the below link about oracle connector:
http://publib.boulder.ibm.com/infocente ... tages.html
Generate your SQL statement.
Use a file name to contain your SQL statement.
Clear a table before loading by using a TRUNCATE statement. (Clear table)
Select how often to commit rows to the database. (Transaction size)
Input multiple rows of data in one call to the database. (Array size)
Read multiple rows of data in one call from the database. (Array size)
Specify transaction isolation levels for concurrency control and transaction performance tuning. (Transaction Isolation)
Specify criteria that data must meet before being selected. (WHERE clause)
Specify criteria to sort, summarize, and aggregate data. (Other clauses)
Specify the behavior of parameter marks in SQL statements.
Oracle OCI is dependent on the libclntsh shared library, which is created during the installation of the Oracle client software. You must include the location containing this shared library in the shared library search path for InfoSphere DataStage jobs to run successfully by using this stage.
Refer the below link about oracle connector:
http://publib.boulder.ibm.com/infocente ... tages.html
Regards,
Sai Krishna
Sai Krishna
-
- Participant
- Posts: 22
- Joined: Thu Apr 19, 2012 3:31 am
- Location: India
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
42% of all statistics are made up.saiwelcomes wrote:Better use Oracle Connector stage to handle large volumes of data. It is 20% faster than OCI stage.
Where did you get this figure?
Are there any specified conditions under which the 20% was obtained?
I could create jobs in which the OCI is faster than the Oracle Connector; I could create jobs in which the Oracle Connector outperforms the OCI stage by a factor of 10x or more.
It all depends...
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: 298
- Joined: Tue Aug 26, 2008 12:17 pm
... and 42% is a very noticeable number, indeed!ray.wurlod wrote: 42% of all statistics are made up
But one good thing about Connector-Stages is, that they share the same user-interfaces in Server and Parallel Jobs (except that you can't switch the server variant to parallel mode). They are even able to use the same Data-Connection-objects (which was not possible for the different versions of DB2 API Stage for example).
There is a good chance that Connector stages are, in fact, faster than OCI-Stages, because the connectors are optimized to connect to the latest versions of the databases. For example there are options in the Oracle Connector stage to connect to the version 10 or 11 variants of Oracle - which does not seem to change much in the mechanics of the stage, though. If IBM announces that DataStage 9.1 has much better Oracle-throughput than 8.7 this assumes you are using the Oracle Connector in both versions. And it assumes You believe this statistic is part of the 58% Ray did not refer to...
The Oracle OCI-Stage was developed for Oracle 9i and no further development is carried on by IBM regarding this stage - except necessary bugfixing (hopefully).
"It is not the lucky ones are grateful.
There are the grateful those are happy." Francis Bacon
There are the grateful those are happy." Francis Bacon
-
- Participant
- Posts: 298
- Joined: Tue Aug 26, 2008 12:17 pm