Product

Platform

Intel

Operating system

Windows 2000

Error

Symptoms

You wish to perform a Prinergy 1.1 to 2.0 upgrade, but the database is extremely large. The customer cannot have the system down for a very lengthy upgrade, and they are willing to remove ALL the job history in the database to speed up the export/import of the database.

Cause

Solution

Before starting the Prinergy 1.1 to 2.0 upgrade procedure, you can remove the job history from the database. (You must remove the history from the database BEFORE the upgrade script exports the database.)

** NOTE** Ensure you have a current and valid backup of the database before attempting to remove the job history.

To destroy the job history in Prinergy 1.1, truncate the history tables.

At an SQL Prompt run:

SQL> truncate table DBCS_HistLogDetailObject;

SQL> truncate table DBCS_HistLogDetail;

SQL> truncate table DBCS_HistLogAction;

These SQL statements only delete the data in the tables. It leaves the indexes and table itself in tact.

For Prinergy 2.0 systems, you must disable constraints, truncate the tables then re-enable the constraints:

SQL> alter table DBCS_HISTLOGDETAIL modify constraint FK_DBCS_HIS_REF_4731_DBCS_HIS disable;

SQL> alter table DBCS_HISTLOGDETAILOBJECT modify constraint FK_DBCS_HIS_REF_28914_DBCS_HIS disable;

SQL> truncate table DBCS_HistLogDetailObjectOld;

SQL> truncate table DBCS_HistLogDetailObject;

SQL> truncate table DBCS_HistLogDetail;

SQL> truncate table DBCS_HistLogAction;

SQL> alter table DBCS_HISTLOGDETAIL modify constraint FK_DBCS_HIS_REF_4731_DBCS_HIS enable validate;

SQL> alter table DBCS_HISTLOGDETAILOBJECT modify constraint FK_DBCS_HIS_REF_28914_DBCS_HIS enable validate;

Permanent fix:

See also

Keywords

oracle

Technical contact(s)

Stan Yoshida

Submitted by

Amy Chan

Date submitted

17 Sep 2001