Product

Platform

Operating system

Symptoms

There is a possibility of the Oracle database within the Prinergy system becoming corrupted under specific conditions.

Cause

The Oracle database may become corrupted when any of its datafiles extend onto a 4 GB boundary, that is, if the datafile grows to become 4 GB, 8 GB or 12 GB in size. This is only an issue with Prinergy 2.1 systems running Prinergy 2.1.0.19 and earlier, and Prinergy 2.2 systems running Prinergy 2.2.1.0 and earlier. Prinergy 2.0.7 and earlier versions are not affected by this bug because it was not possible for a datafile to extend onto a 4 GB boundary in those releases.

Solution

The conditions that may result in a corrupted database are relatively rare, but to minimize the chances of encountering this bug, a Prinergy 2.1 system should be updated to 2.1.0.20 as soon as possible. Prinergy 2.2 sites should be updated to at least 2.2.1.1 as soon as possible. Patch 2.1.0.21, and patch 2.2.1.3, once released, have additional changes to further minimize the likelihood of this issue. The Prinergy 2.1.0.20 update is available from the eCentral Downloads page under Prinergy 2.1 Guided Updates and the Prinergy 2.2.1.1 update is available from the eCentral Downloads page under Prinergy 2.2.1.

Technical contact(s)

Simon Chen

Submitted by

Simon Chen

Date submitted

14 Oct 2003