Is it Acceptable to Hash Partition the ODI Repository Tables to Improve Performances? (Doc ID 2611054.1)

Last updated on AUGUST 07, 2024

Applies to:

Oracle Data Integrator - Version 11.1.1.6.0 and later
Oracle Data Integrator on Marketplace - Version 12.2.1.4.200123 and later
Information in this document applies to any platform.

Goal

A high degree of cluster related wait events (such as gc buffer busy acquire and gc cr block busy) have been noticed during inserts at intervals where a high number of concurrent sessions are inserting into the Oracle Data Integrator (ODI) Work Repository tables:

SNP_SESS_STEP_LV
SNP_SESS_TASK_LOG

Is it acceptable to hash partition these two tables to mitigate the problem?

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.

Is it Acceptable to Hash Partition the ODI Repository Tables to Improve Performances? (Doc ID 2611054.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!