Friday May 30, 2014

Looking for Cutting-Edge Data Integration: 2014 Excellence Awards

2014 Oracle Excellence Awards Data Integration

It is nomination time!!!

This year's Oracle Fusion Middleware Excellence Awards will honor customers and partners who are creatively using various products across Oracle Fusion Middleware. Think you have something unique and innovative with one or a few of our Oracle Data Integration products?

We would love to hear from you! Please submit today.

The deadline for the nomination is June 20, 2014.

What you win:

  • An Oracle Fusion Middleware Innovation trophy

  • One free pass to Oracle OpenWorld 2014

  • Priority consideration for placement in Profit magazine, Oracle Magazine, or other Oracle publications & press release

  • Oracle Fusion Middleware Innovation logo for inclusion on your own Website and/or press release

Let us reminisce a little…

For details on the 2013 Data Integration Winners:

Royal Bank of Scotland’s Market and International Banking and The Yalumba Wine Company, check out this blog post: 2013 Oracle Excellence Awards for Fusion Middleware Innovation… and the Winners for Data Integration are…

and for details on the 2012 Data Integration Winners:

Raymond James and Morrisons, check out this blog post: And the Winners of Fusion Middleware Innovation Awards in Data Integration are… 

Now to view the 2013 Winners (for all categories).

We hope to honor you!

Here's what you need to do: 

Click here to submit your nomination today.  And just a reminder: the deadline to submit a nomination is 5pm Pacific Time on June 20, 2014.

Wednesday May 21, 2014

Zero Downtime Consolidation to Oracle Database 12c: Webcast Recap

As companies move to private cloud implementations to increase agility and reduce costs, and start their plans with consolidating their databases, a major question arises: how do we move our systems without causing major disruption to the business. At the end, the most important systems that need to move to this new architecture are the ones that cannot tolerate extensive downtime for any reason. In last week’s webcast “Zero Downtime Consolidation to Oracle Database 12c with Oracle GoldenGate 12c” we tackled this specific dilemma that IT organizations face. The webcast is now available on demand via the link above in case you missed it last week.

In the webcast, we started discussing the benefits companies achieve when they consolidate to a private database cloud, critical database capabilities to deliver database as a service, and a quick overview Oracle Database 12c features that enable private database clouds deployments. Nick Wagner, director of product management for Oracle Database High Availability, talked about the new Global Data Services feature in Oracle Database Maximum Availability Architecture (MAA) as well. Global Data Services helps organizations to handle challenges involved with managing multiple database replicas across different sites. The product manages database replicas of Active Data Guard and Oracle GoldenGate products, and offers workload balancing to maximize performance as well as intelligent handling of outages using all available replicas. Nick also discussed the database features available for upgrading, migrating, and consolidating into Oracle Database 12c and when it makes sense to use Oracle GoldenGate for these efforts.

After Nick, Chai Pydimukkala from senior director of product management for GoldenGate discussed some of the key new features of Oracle GoldenGate 12c for Oracle Database and its expanding heterogeneity that supports consolidation from all major databases. Chai continued his presentation with GoldenGate’s solution architecture for zero downtime consolidation and explained how it minimizes risk with failback option as well as via the phased migration option by running old and new environments concurrently.

Chai also gave an example on how Oracle Active Data Guard customers can seamlessly use GoldenGate for a zero downtime migration without affecting their standby system for high ongoing high availability and disaster recoery. After customer examples we had a long Q&A section. For the full presentation and Q&A with the experts you can watch the on-demand version of the webcast via the following link.

Zero Downtime Consolidation to Oracle Database 12c with Oracle GoldenGate 12c

In the rest of this blog post, I provided  answers to some of the questions we could not take in the live event. 

1) Additional difference in features between GoldenGate 11g and 12c?

Please take a look at our previous blog posts below where we discussed many of the new features of GoldenGate 12c.

· Advanced Replication for The Masses – Oracle GoldenGate 12c for the Oracle Database.

· GoldenGate 12c - What is Coordinated Delivery?

· GoldenGate 12c - Coordinated Delivery Example

· Oracle GoldenGate 12c - Announcing Support for Microsoft and IBM

You can also listen to our podcast: Unveiling Oracle GoldenGate 12c

More comprehensive information can be found in the webcast replay  Introducing Oracle GoldenGate 12c: Extreme Performance Simplified or GoldenGate 12c resource kit.

2) Does GoldenGate have a term license that customer can purchase for migration purposes?

We do offer 1 year license that customer can be used for this purposes.

3) Is there a Oracle Tutorial on configuring and testing Zero downtime upgrade using GoldenGate?

Here is a high level outline/tutorial for the migration. It will require some knowledge of how to setup GoldenGate and configuration.

Oracle GoldenGate Best Practice: Oracle Migrations and Upgrades 9i and up

A more broad discussion of this topic can be found in the following white paper. Zero Downtime Database Upgrades using Oracle GoldenGate 12c

4) If the number of updates to the database is very high, does GoldenGate give some kind of compression to transfer the Trail Files and be up to date with the changes?

Oracle GoldenGate does provide support of compress of change data in the Trail File to better the transfer throughput from source to target with the usage of COMPRESS and COMPRESSTHRESHOLD. 


{host_name | IP_address}

{, MGRPORT port | PORT port}



[, ENCRYPT algorithm [KEYNAME key_name]]

[, PARAMS collector_parameters]


[, TCPBUFSIZE bytes]


[, TIMEOUT seconds]


This option is valid for online or batch Capture processes and any Oracle GoldenGate initial-load method that uses Trails. Compresses outgoing blocks of records to reduce bandwidth requirements. Oracle GoldenGate decompresses the data before writing it to the Trail. COMPRESS typically results in compression ratios of at least 4:1 and sometimes better. However, compressing data can consume CPU resources.


This option is valid for online or batch Capture processes and any Oracle GoldenGate initial-load method that uses trails. Sets the minimum block size for which compression is to occur. Valid values are from 0 and through 28000. The default is 1,000 bytes.

5) Can the Source system utilize 12C GoldenGate for DML/DDL capture and target system utilize GoldenGate 11g?

Yes.  You can replicate from a higher version of GoldenGate to a lower version using FORMAT RELEASE option. 

FORMAT RELEASE <major>.<minor>

In the on demand replay of the webcast you will find more questions answered by our product management experts. So make sure to watch the on demand webcast as well.

Thursday May 15, 2014

Oracle Data Integrator Webcast Archives

Have you missed some of our Oracle Data Integrator (ODI) Product Management Webcasts?

Don’t worry – we do record and post these webcasts for your viewing pleasure. Recent topics include Oracle Data Integrator (ODI) and Oracle GoldenGate Integration, BigData Lite, the Oracle Warehouse Builder (OWB) Migration Utility, the Management Pack for Oracle Data Integrator (ODI), along with other various themes focused on Oracle Data Integrator (ODI) 12c. We run these webcasts monthly, so please check back regularly.

You can find the Oracle Data Integrator (ODI) Webcast Archives here.

And for a bit more detail:

The webcasts are publicized on the ODI OTN Forum if you want to view them live.  You will find the announcement at the top of the page, with the title and details for the upcoming webcast.

Thank you – and happy listening!

Monday May 12, 2014

Check it out – BI Apps is now available!

As of May 8, 2014, Oracle Business Intelligence (BI) Applications is available on the Oracle Software Delivery Cloud (eDelivery), and on the Oracle BI Applications OTN page. This is the second major release on the 11g code line leveraging the power of Oracle Data Integrator (ODI), and certified with the latest version of Oracle BI Foundation For more details on this release and what’s new – check it out!

Friday May 09, 2014

What's New in Oracle GoldenGate 12c for DB2 LUW

Oracle GoldenGate 12c ( for IBM DB2 LUW was released on April 24, 2014. The new version delivers the following new features: 

  • DB2 10.1 and 10.5: this includes the extended row size support for DB2 LUW v10.5 with FETCHCOLS.
  • Adaptive Compression: the new parameter ALLOWTABLECOMPRESSION is added for DB2 v9.7 to support compressed tables. From DB2 v10.1 onwards, this parameter doesn't need to be specified.
  • Coordinated Delivery (Replicat):  the coordinated delivery is supported. 

For more information, please refer to Oracle GoldenGate 12c for DB2 LUW  Installation and Configuration documentation

User Interface and Terminology Changes in ODI 12c - Part 3

In the first and second blog post in this series we have covered many of the UI changes made in ODI 12c. In this third blog post we will finish describing some of the improvements made at the Mapping level.


A couple of changes were made in how you set the Journalization (CDC/Changed Data Capture) settings in Data Integrator 12c. To access the ‘Journalized Data Filter’ field you now have to click on a source datastore in the Logical tab of a Mapping and then select the Journalizing panel in the Properties window. You can define the journalization filter there:

The Journalized Data Only checkbox which was previously found in the Diagram tab of an Interface is now available on the Physical tab of a 12c Mapping. To access it, select your Deployment Specification, click on the source datastore and then select the General panel in the Properties window. The Journalized Data Only checkbox is listed at the bottom of this panel, once checked it will move to the top of the panel.

Integration Type

In ODI 12c you can specify an Integration Type for your target datastore, this will filter the list of Integration Knowledge Modules available to you in the Physical tab of your Mappings. You can pick one of the following values: None, Control Append, Incremental Update or Slowly Changing Dimension.

The default setting is Control Append (Insert), set it to a different value to see other IKM types such as Update or Merge.

Setting the Loading Knowledge Modules and Integration Knowledge Modules

To set a Loading Knowledge Module in ODI 11g you had to click on the Source Set boxes and then select an LKM in the Loading Knowledge Module drop-down list.

In ODI 12c you now have to click on the Access Point which corresponds to your source. The corresponding Access Point will typically be found in the Staging Area execution unit and can be recognized by its name which ends with the suffix ‘_AP’. In the following screenshot the source file Datastore is called SRC_SALES_PERSON, to define its LKM I click on its Access Point SRC_SALES_PERSON_AP located in my Staging/Target execution unit. Then I can use the Loading Knowledge Module panel in the Properties window to select the appropriate LKM.

Similarly selecting an Integration Knowledge Module in 11g was done by clicking on the Target box and then using the Integration Knowledge Module drop-down list.

In ODI 12c you can now simply click on one of your Target datastores in the Physical tab of a Mapping and then use the Integration Knowledge Module panel in its Properties window.

Using Multi-technology IKMs

Multi-technology IKMs such as the IKM SQL to File Append are typically used when the Staging Area is not located on the Target technology of a given Mapping. In such cases data has to flow between the Staging and Target servers and a multi-technology IKM can be leveraged to do so. They are also useful when implementing ODI using an old school ETL architecture.

To be able to select multi-technology IKMs in ODI 12c you have to first set the LKM to LKM SQL Multi-Connect on your Access Point(s). If you don’t see them after their import operation is most likely because you are not using the LKM SQL Multi-Connect yet.

Finally you can click on your target datastore and select the multi-technology IKMs you have imported in your project using the Integration Knowledge Module panel:


ODI 12c is using a flow-based declarative design approach which offers more flexibility and capabilities when compared to the ODI 11g Interface design. For example, ODI 12c Mappings now support multiple targets and have Mapping Components such as Pivot or Aggregate which were not previously available.

One of those new Mapping Component called Dataset brings back some of the ODI 11g design elements into ODI 12c Mappings and is very similar in nature to a Dataset (source area) found in an 11g Interface. Datasets are very useful to group sources together and can provide a better Mapping readability. Creating joins, filters and lookups inside a Dataset is done in a similar fashion as in ODI 11g. 

Here is an example of a Mapping using a Dataset Component in ODI 12c, the 3 source datastores are grouped inside a Dataset named Default:

Here is the same example without using a Dataset component, none of the sources are grouped:

Set-Based Operations

Set-based operations such as Minus, Union etc. were performed using multiple Datasets in ODI 11g, each Dataset being linked to each others with a set operation. In ODI 12c Datasets are not required anymore to perform set-based operations instead a new Set Component is provided in the Mapping Components palette.

Temporary Interfaces / Reusable Mappings

Temporary Interfaces were useful in ODI 11g to nest an Interface into another one and generate a sub-select query to optimize performance and avoid staging the data into physical tables. ODI 12c takes the concept to the next level with Reusable Mappings which replace Temporary Interfaces.

In a Reusable Mapping you can encapsulate transformation logic that you are going to reuse in multiple places therefore avoiding duplicating the same code. This logic can be designed using existing Datastores along with Mapping Components but you can also provide a generic Input or Output signature which significantly expands the possibilities of reusing code snippets across various Mappings.

Note that it is not possible to design a target table on the fly in ODI 12c, any table/datastore has to first be defined at the Models level.

Similarly to ODI 11g it is possible to add a Reusable Mapping into a “standard” Mapping and prevent staging the data by generating a sub-select query.

This concludes this blog series about user interface and terminology enhancements made in ODI 12c. Be sure to check out the previous blog posts in this series: Part 1Part 2.

Tuesday May 06, 2014

No Way Out, But to Consolidate

IT teams receive pressures on multiple fronts: Business groups demand new application services delivered faster and continuous, high-quality IT service to support highly dynamic and competitive business operations. In the meanwhile IT teams are asked to reduce costs and improve ROI from existing systems in highly complex and siloed environments.

In the midst of this conundrum, the only way out for IT leadership is to consolidate and leverage cloud architecture. Especially consolidation at the database level and implementing a private database-as-a-service (DBaaS) environment is a transformative approach to delivering database functionality to end users in an agile, efficient, and scalable way.  It helps organizations improve resource utilization, and lower both capital and operational expenditures.

Oracle Database 12c is designed to support database consolidation with many new features for deploying shared database environment. The new multitenant architecture, simplified management capabilities, improvements to security and compliance, along with robust and flexible Maximum Availability Architecture, are only a few of the key differentiators.

While this all sounds good and logical for IT teams, when it comes to moving to a private database cloud, they face yet another major challenge: How do we move our critical systems to a new environment without interrupting our operations. In today’s 24/7 world, especially customer-facing systems cannot tolerate hours or days of downtime. For some of them, even few minutes of downtime can bring high costs to the business. As in each major project, risk involved with moving to a new system is a real deterrent factor too.

Oracle GoldenGate 12c offers the core capabilities to enable this major move to a database as a service environment. With its optimized support for Oracle Database 12c multitenant architecture and heterogeneous data replication capabilities, Oracle GoldenGate allows organizations to avoid business disruption while the systems are moving to a consolidated, DBaaS environment. In addition, Oracle GoldenGate offers a failback option to the old environment, or a phased migration option by running old and new systems simultaneously in active-active mode, to minimize risks. Oracle GoldenGate’s heterogeneity includes all major database vendors and operating systems including SQL Server, DB2 (LUW, z/Os, iSeries), Sybase ASE, HP NonStop and more. 

In our webcast Zero Downtime Consolidation to Oracle Database 12c with Oracle GoldenGate 12c on May 13th 10am PT we will present this solution with specific architecture examples and comparison to other database upgrade options.

Zero Downtime Consolidation to Oracle Database 12c with Oracle GoldenGate 12c

May 13th, 10am PT/ 1pm ET

If your organization needs to improve agility, increase innovation, and reduce costs, I invite you to join this webcast to learn how to remove the risk and business interruption barriers to move to an agile and cost-efficient private database cloud.

User Interface and Terminology Changes in ODI 12c - Part 2

In the first blog post in this series we have covered many of the UI changes made in ODI 12c. In this second blog post we will continue covering some of the changes made at the Mapping level.

Declarative Flow-Based Design

The first major change you are probably going to see when using ODI 12c coming from earlier versions is that we have augmented the ODI Declarative Design concept with Flow-Based elements. The goal has been to take ELT/ETL Mapping design to the next level by providing greater flexibility and advanced features like new Mapping Components while still keeping the Logical and Physical representations separate. What it means in practice is that you can now do more with ODI Mappings such as writing to multiple targets or ordering your transformations the way you want it while still being more productive than you would be in a conventional ETL tool.

As an example I’ve added below a screenshot of an ODI 11g Interface and then a screenshot of its corresponding Mapping in 12c:

Aggregate Functions

In ODI 11g aggregate functions were directly entered in the target datastore mapping expressions and the group by expression was automatically created by ODI.

In ODI 12c aggregates must now be performed using the Aggregate Component which is found in the Mapping Component palette. The Aggregate component allows you to specify manually the group by and having clauses which wasn’t possible in earlier ODI releases.

Using aggregate functions in a target datastore expression will now trigger a Mapping validation error and prevent its execution.


Doing a distinct operation in ODI 11g required checking the ‘Distinct Rows’ checkbox in the Target Properties panel in the Flow tab. In 12c doing a distinct operation is more straightforward and is defined explicitly using the Distinct Component which is available from the Mapping Components palette.


Filters can still be defined in a similar way to ODI 11g by simply drag and dropping a source Datastore attribute into the Diagram area surrounding it. It is also possible to use the new Filter Component from the Mapping Components palette. The Filter Condition is then provided in the Properties of the Filter Component.


Joins are created using the new Join Component from the Mapping Components palette. Outside of a Dataset Component (which we will review later), it is not possible anymore to drag and drop a column from one source Datastore to another one to create a join like in ODI 11g. Once you have added the Join Component into the Mapping diagram you can type the Join expression manually or drag and drop columns/attributes from the source datastores into the Join Component to build the Join expression graphically.

Ordered Joins

If you are using ordered joins in ODI 12c make sure you check the ‘Join Order’ checkbox and provide an order number in the ‘User Defined’ field. If no value is provided in the ‘User Defined’ field the ‘Join Order’ checkbox will automatically be unchecked by ODI. Those fields are available in the Condition panel of a Join Component Properties window as shown below.


The Lookup wizard found in ODI 11g has been replaced by a new Component named Lookup. We also spent some time optimizing the Lookup parameters to make it more intuitive and powerful. It is now, for example, possible to define what happens if there are multiple rows matched or if no records are being matched.

We still have many more enhancements to cover, stay tuned for the last post in this blog series!

Friday May 02, 2014

3 Key Practices For Using Big Data Effectively for Enhanced Customer Experience

As organizations focus on differentiating their offering via superior customer experience, they are looking into ways to leverage big data in this effort. Couple of weeks ago my colleague Pete Schutt and I hosted a webcast on this very topic: Turning Big Data into Real-Time Action for a Greater Customer Experience

In this webcast we talked about 3 key practices to make the most out of big data for improving customer experience, which are:

  1. Know your customer leveraging big data: Leverage all relevant data (internal and external; structured, semi-structured, and unstructured) to understand and predict customers needs & preferences accurately.
  2. Capture, analyze, act on data fast to create value: Achieve accurate insight and take the right action fast so your action can be still relevant to the customer’s situation.
  3. Empower employees & systems with insight & smarter decisions: In this step you ensure that the capability to act right and fast is not limited to a few in the organization, but everyone and every system that interacts and influences customers’ experience.

After explaining why these practices are critical to improving customer experience, we discussed Oracle’s complete big data analytics and management platform, as well as the specific products and architectural approaches to execute on these 3 key areas. We focused particularly on data integration for fast and timely data acquisition and business analytics for real-time insight and action, and how they fit together in a real-time analytics architecture.

You can watch this webcast now on demand via the link below:

Turning Big Data into Real-Time Action for a Greater Customer Experience

In this webcast we received many great questions and I have provided below a few of them along with the answers.

Is real-time action related to the Internet of Things?

Yes, more physical things will be connected to the internet, often wirelessly with RFID tags or other sensors and Java to record where they are and what they are doing (or not doing). The IoT will be more practical by automating the information process from capture to analysis to appropriate and immediate action.

What does Oracle have for real-time mobile analytics?

Oracle BI Mobile App Designer empowers business users to easily create interactive analytical applications on any device without writing a single line of code and to also take action and respond to events in the context of their day-today business activities

Can these real-time systems be managed by business users?

Yes, you need the agility for business owners to be able to respond, experiment, and adapt, in real-time as the environment or consumer behavior changes. The systems have to be intuitive enough for users with the business content and context who can easily visualize, understand, and change the patterns they're looking and the rules that are being enforced.

Can the real-time systems use other statistical models or algorithms?

Yes. Oracle Advanced Analytics offer an enterprise version of R and Oracle RTD can source and publish scores from other advanced analytical models such as R, SAS, or SPSS or others.

Where do we get more information about ODI for big data?

 You can start with Oracle Data Integrator Application Adapter for Hadoop. And also take a look at the  Oracle BigDataLite Virtual Machine, a pre-built environment to get you started on an environment reflecting the core software of Oracle's Big Data Appliance 2.4. BigDataLite is a VirtualBox VM that contains a fully configured Cloudera Hadoop distribution CDH 4.5, an Oracle DB 12c, Oracle's Big Data Connectors, Oracle Data Integrator 12.1.2, and other software. You can use this environment to see ODI 12c in action integrating big data with Oracle DB using ODI's declarative graphical design, efficient EL-T loads, and Knowledge Modules designed to optimize big data integration. 

For GoldenGate, can a target be something other than a database, e.g. queue?

Yes, GoldenGate can deliver database changes into JMS message queues and topics, as well as in flat file format. Oracle GoldenGate Application Adapters would need to be used for those use cases. For low-impact real-time data integration into Hadoop systems customers will need to use the Java Adapter within this GoldenGate Application Adapters license as well.

What other data warehouses can does Oracle support for real-time data integration?

Oracle's data integration offering is heterogeneous for both sources and targets. Both Oracle Data Integrator and Oracle GoldenGate work with non-Oracle data warehouses including Teradata, DB2, Netezza, Greenplum.

I invite you to watch this webcast on demand to hear the details of our solution discussion and the Q&A with the audience. For more information big data integration and analytics you can review Bridging Two Worlds. Big Data and Enterprise Data and Big Data @ Work Turning Customer Interactions into Opportunities.


Thursday May 01, 2014

User Interface and Terminology Changes in ODI 12c - Part 1

Oracle Data Integrator 12c introduces several new exciting and powerful features, for a complete list please look at the New Features Overview document available on OTN. While working on major enhancements we have also made several smaller tweaks to improve the overall user experience. In this blog post series I will describe some of those minor changes, highlighting some of the differences between ODI 11g and ODI 12c. This will help ODI 11g users get up and running quickly with ODI 12c.

Terminology Changes

The following table lists some of the key terminology changes that have been made in ODI 12c when compared to ODI 11g:

Changes at the Model level

Slowly Changing Dimension Behavior

Setting the Slowly Changing Dimension Behavior in ODI 11g was tedious, you had to open individually each column, go to their Description tab and finally set the SCD Behavior.

In ODI 12c you can now simply set the SCD Behavior for all your datastore’s attributes directly from its Attributes panel.

Changes at the Mapping level

Flow Control

The Flow Control settings have been reorganized; the Controls tab found in ODI 11g Interfaces has been removed.

The Check Knowledge Modules can now be selected in the Physical tab of a 12c Mapping: click on one of your target datastores and select the Check Knowledge Module panel in the Properties window.

You will find the constraints checked by Flow Control in the Logical tab of a Mapping. Click on a target datastore and select the Constraints panel in the Properties window as shown below.

The ‘Maximum Number of Errors Allowed’ and ‘Integration Errors as Percentage’ options have also moved to the Logical tab of a Mapping and are found in the Target panel of a target datastore in its Properties window.

Temporary Indexes

Temporary indexes which were previously defined in the Diagram tab of an Interface are now found in the Physical tab of a Mapping. Click on a Component such as Join or Filter in the Physical diagram to access the Temporary Indexes panel in the Properties window and set the Index Type for each of the nodes.


The Quick-Edit panel which was a separate tab in an ODI 11g Interface is replaced by the Attributes panel in a Mapping. You can access it easily: simply click on one of your Target datastores and select the Attributes panel in its Properties window as shown below.

Execution Location

ODI 12c replaces the ‘Execute on’ parameter from ODI 11g with ‘Execute on Hint’. The ‘Execute on Hint’ parameter can be set from the Properties window of all Mapping Components such as Join, Filter or Pivot as you can see below.

This ‘Execute on Hint’ parameter can also be set for specific Expressions from the Attributes panel of a datastore or when selecting a given attribute in the Mapping diagram.

Note that this parameter is a hint and as such it can be overridden by ODI if it finds a better execution location at runtime. Execution location changes made directly in the Physical tab of a Mapping, for example by moving a Filter component from one Execution Unit to another one, will take the precedence over any hints provided in the Logical tab.

Staging Location

In ODI 11g you could set the Staging Area location in the Definition tab of an Interface. In 12c you can set a hint called ‘Staging Location Hint’ in the Logical tab of a Mapping. Similarly to the ‘Execute on Hint’ we saw earlier, it can be overridden in the Physical tab.

You can also set the Staging location explicitly in the Physical tab of a Mapping, the ‘Preset Staging Location’ field is found in the Deployment Specification properties panel as shown below:

There are many more changes to talk about, stay tuned for the second blog post in this series!


Learn the latest trends, use cases, product updates, and customer success examples for Oracle's data integration products-- including Oracle Data Integrator, Oracle GoldenGate and Oracle Enterprise Data Quality


« May 2014 »