DIAG  [Oracle][ODBC]Numeric value out of range. (0)
This behavior may occur with no noticeable changes to the environment.
The behavior occurs for very large tables (2.6 billion + rows), and results when the value returned from the ODBC api call exceeds the maximum value returnable via SQL_C_DEFAULT binding, and the error is expected behvior and indicates the value is too large to fit in the bind.
This is a limitation of Microsoft Access.
A potential workaround may be to use DBMS_STATS.SET_TABLE_STATS to alter the data dictionary statistics for the number of rows in the table so that the limit is not exceeded, but should not be undertaken without understanding the impact. Consult with your DBA for further advice.
BUG:3319122 - CALLING SQLSTATISTICS ON VERY LARGE ANALYZED TABLE FAILS WITH MS ACCESS