Product

Kodak^® Prinergy^® Connect^™, version 4.x

Operating system

• Microsoft^® Windows^® 2000 Server
• Microsoft Windows Server^® 2003

Error

Oracle^® 10 migration error: ORA-01841: (full) year must be between -4713 and +9999, and not be 0
ORA-06512: at “PRINERGY.DBCS_UTCTIMECONVERTER”, line 464

Rehost Tool error: Found invalid dates in Oracle 8 database. These must be fixed or else the migration will fail. Cannot continue.

Prinergy 4.x PreCheck.exe error: Invalid dates found in database. Upgrading to the next Prinergy version will most likely fail unless this is fixed.

Symptoms

You upgrade the Prinergy 4.x system, using either the PPU tool or the Prinergy Rehost tool. The Oracle software upgrade fails and the error message appears in the LoadCreoObjects log file (possibly multiple times).

After you run Prinergy 4.x PreCheck.exe, the error message Invalid dates found in database. Upgrading to the next Prinergy version will most likely fail unless this is fixed. appears.

Cause

One or both of the following tables contains invalid dates:

• dbcs_ArchiveFile table, in the ArchiveFileModifiedDTM field
• dbcs_RegisteredFile table, in the RegFileLastModDTM field

If either of these fields contains the date stamp 0/0/0000 in any row, the upgrade fails.

Note: The Prinergy 4.x software and the Oracle 10g software store time stamps as Universal Time (UTC). This avoids time and date problems between time zones, where a Prinergy system spans several time zones or is in a hub-and-spoke configuration.

Solution

Locate and correct the invalid dates.

Caution: This procedure directly modifies customer data. If you do not thoroughly understand the procedure, stop now. Contact a Remote Product Specialist or the equivalent for your region to confirm that you should perform this procedure.

1. Open a command-prompt window, and run the following SQL commands (connect as prinergy/araxi):

SQL> alter session set NLS_DATE_FORMAT='DD-MON-YYYY';

SQL> select count(*) from prinergy.dbcs_ArchiveFile where ArchiveFileModifiedDTM < '01-JAN-1910';

SQL> select count(*) from prinergy.dbcs_RegisteredFile where RegFileLastModDTM < '01-JAN-1910';

SQL> select count(*) from prinergy.dbcs_RegisteredFile where REGFILECREATEDTM < '01-JAN-1910';

SQL> select count(*) from prinergy.dbcs_subpageelmnt where GENERATELAYEREDSPEDTM < '01-JAN-1910';

2. If the commands return any entries, run the following SQL commands:

SQL> update prinergy.dbcs_ArchiveFile set ArchiveFileModifiedDTM = '01-JAN-1910' where ArchiveFileModifiedDTM < '01-JAN-1910';

SQL> update prinergy.dbcs_RegisteredFile set RegFileLastModDTM = '01-JAN-1910' where RegFileLastModDTM < '01-JAN-1910';

SQL> update prinergy.dbcs_RegisteredFile set REGFILECREATEDTM = '01-JAN-1910' where REGFILECREATEDTM < '01-JAN-1910';

SQL> update prinergy.dbcs_subpageelmnt set GENERATELAYEREDSPEDTM = '01-JAN-1910' where GENERATELAYEREDSPEDTM < '01-JAN-1910';

SQL> commit;

3. Run the upgrade again. If you are using the Prinergy Rehost tool to upgrade, you must remove Oracle 10g first. For details, see the Prinergy Rehost Tool documentation.

See also

Using the Prinergy Primary Server Rehost Tool Version 2.1

Keywords

installation, Oracle, PreCheck, upgrades, rehosting

Technical contact(s)

Submitted by

Date submitted

01 Feb 2008