How To Speed Up The Upgrade Process On An Agile Product Lifecycle Management (PLM) System When History Tables Over 50Gb? (Doc ID 2761829.1)

Last updated on MARCH 23, 2021

Applies to:

Oracle Agile PLM Framework - Version 9.3.6.0 and later
Information in this document applies to any platform.

Goal

The Agile History Tables - CHANGE_HISTORY, ADMIN_HISTORY_DETAILS, ITEM_HISTORY, EVENT_HISTORY, A_DW_TXN_LOG are well over 50 GB alone and stall out when trying to import the database across an Network File System (NFS) mount. Need suggestions on how to archive the data in these tables to reduce the size. The remaining tables are less than 16GB when these tables are truncated. Customer is using Automated Upgrade Tool (AUT) with the default setting "sourceEqualsDest = false".

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!

In this Document

Goal

Solution

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

How To Speed Up The Upgrade Process On An Agile Product Lifecycle Management (PLM) System When History Tables Over 50Gb? (Doc ID 2761829.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!