The Year 2038 problem (also called Y2038 or Y2k38 or Unix Y2K) relates to representing time in many digital systems as the number of seconds passed since 00:00:00 UTC on 1 January 1970 and storing it as a signed 32-bit integer. Such implementations cannot encode times after 03:14:07 UTC on 19 January 2038.

Similar to the Y2K problem, the Year 2038 problem is caused by insufficient capacity used to represent time.

https://communities.actian.com/s/article/Working-with-Ingresdate-Date-Fields

Date values can range from 01-jan-0001 to 31-dec-9999. Time intervals can range from -9999(min) years to +9999(max) years within the specified range of Date values.

SQL functions have been updated to ensure OpenROAD continues to operate as expected beyond 03:14:07 UTC on 19 January 2038. The SQL functions _date4(), _date(), date_part(), _bintim() now return INTEGER8 instead of an INTEGER4.