ORA-01841 Error During Check-in after Harvest 14.5 Upgrade
Article ID: 448314
Updated On:
Products
Issue/Introduction
Users experience a database error during check-in operations after upgrading to SCM Harvest 14.5. The error is specific to certain environments, such as remote agent folders or virtualized desktops (e.g., Citrix), while local client installations may function correctly.
Error Message: E03020003: Database error [Oracle][ODBC][Ora]ORA-01841: (full) year must be between -4713 and +9999, and not be 0 SQLSTATE=S1000 E03060019: Process Execute failed. Process Name: Check In.
Environment
- Product: CA Harvest Software Change Manager
- Version: 14.5.x
- Components: New PEC, CAPKI, and ODBC drivers installed during upgrade.
- Operating System: Windows/Linux/Unix
Cause
The ORA-01841 error indicates that the Oracle database is receiving an invalid date or timestamp value. During the check-in process, Harvest attempts to record the file's "Last Modified" timestamp. If the file has a null, corrupted, or incompatible timestamp format at the operating system level, the ODBC driver passes an invalid value to the database, causing the insert into HARVERSIONDATA to fail. This can happen if the Oracle DBMS is experiencing a problem, or (in the case of Linux/Unix) if the Harvest ODBC component was not upgraded successfully.
Resolution
In the case of a problem with the Oracle DBMS, restarting Oracle and then restarting the Harvest broker can often solve the problem.
For Linux/Unix operating systems, it can help to reinstall the Harvest ODBC component
If the problem persists, it will be good to increase the Harvest log level to 5, reproduce the problem, then locate the Harvest log files, open a support case with the Broadcom support team, and provide the *HServer*.log files for review.
Additional Information
Feedback
