Error during Check In: E03020003: Database error [Oracle][ODBC]Numeric value out of range.

Products

• CA Harvest Software Change Manager
• CA Harvest Software Change Manager - OpenMake Meister

Issue/Introduction

Harvest User cannot perform Commit to Repository from the WorkArea. Here is an example of the error from the CASCM.log file:
 
E03020003: Database error [Oracle][ODBC]Numeric value out of range.
SQLSTATE=22003.
I00060079: Check in summary: Total: 1; Success: 0; Failed: 0; Not Processed: 1.
E03060019: Process Execute failed. Process Name: Check In.
E03060019: Process Execute failed. Process Name: Check In.
Resource - <filename> - is not managed.
E03020054: The package named <packagename> is being used by Checkin. Client: /pt_HClient://<clienthostname>/5696 Server: /pt_HServer://<serverhostname>/5564
E03020141: Checkin Process aborted; could not change package status.
I00060079: Check in summary: Total: 0; Success: 0; Failed: 0; Not Processed: 0.
E03060019: Process Execute failed. Process Name: Check In.
Resource - <filename> - is not managed.

Environment

Release : 13.0.3 and up

Component : CA Harvest Software Change Manager

Cause

We increased the HServer logging level to 5, reproduced the problem and then reviewed log files. We found the query that throws this kind of error we are seeing is this one:
-- BindInteger 1:  815500
-- BindInteger 2:  1188
-- BindString 3:  Y
-- BindInteger 4:  916
-- BindString 5:  ve-ve-ve-
-- BindTimestamp 6:  NULL   <---- Notice that this value should NOT be "NULL"
-- BindTimestamp 7:  2020/06/09 11:55:29
-- BindString 8:  
-- BindInteger 9:  0
-- BindBlob 10:  <Total Size 916> 
-- START: 2020/06/16 10:40:41 999  DB Connect#: 70  SINCE LAST SQL: 215 
 
   INSERT INTO HARVERSIONDATA (VERSIONDATAOBJID, DATASIZE,
       COMPRESSED, COMPDATASIZE, FILEACCESS, MODIFYTIME,
        CREATETIME, DCB, TEXTFILE, VERSIONDATA) VALUES ( ?,
        ?, ?, ?, ?, ?, ?, ?, ?, ?) 
 
-- RETURN CODE: DB_FAIL
[Oracle][ODBC]Numeric value out of range.
SQLSTATE=22003
 
It appears to not be picking up the timestamp on the file it’s trying to check in.

We went back to Windows Explorer and looked at the properties for this file and can see that the "Modified" timestamp column is empty for this file.  This would confirm the root cause.

Resolution

The user reported that when he tried the transaction again at a later time, it succeeded, but we're not sure why. 

The other alternatives would be to "touch" the file so that the Modified timestamp is set to a valid value, or to create a zip file containing the file with this problem and then check in the zip file instead.

On Linux and Unix the command to update the modified timestamp on a file is

touch filename.ext

On Windows, if you want to update the date stamp of a file without actually changing the contents of the file, use the following command at the command prompt:

copy /b filename.ext +,,

(where filename.ext is your file's name). The +,, is a special flag to copy telling it to simply update the date/time on the file.