Selecting the Appropriate ODI IKM to Optimize Tablespace and Rollback Segment Resources for Very Large Datasets (Doc ID 423859.1)

Last updated on JULY 30, 2024

Applies to:

Oracle Data Integrator - Version 4.1.01.05 and later
Oracle Data Integrator on Marketplace - Version 1.0.2 and later
Data Integration Platform Cloud Classic - Version 17.3.5 and later
Oracle Data Integrator Cloud Service - Version 17.1.3 and later
Information in this document applies to any platform.

Goal

In the case of loading large datasets with Oracle Data Integrator (ODI), is it possible to use partial commits on subsets of the source Datastore in order to avoid extremely large transaction log tablespaces?

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Selecting the Appropriate ODI IKM to Optimize Tablespace and Rollback Segment Resources for Very Large Datasets (Doc ID 423859.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!