-
Title
Show compare: ERROR: Runtime: stat(): 75: Value too large for defined data type -
Description
When checking the progress of a compare session using "show compare", receive the below error.
Example:
(host:port#)> show compare
Host: hostname
ERROR: Runtime: stat(): 75: Value too large for defined data type -
Cause
SharePlex is a 32 bit application using 32 bit function, which is stat function. So limitation of it is 2 Gb. When compare repairing big tables, the *.sql generated by compare may exceed 2Gb. When the *.sql file generated by compare is bigger than 2Gb, compare returns ERROR: Runtime: stat(): 75: Value too large for defined data type
-
Resolution
sp_ctrl> compare <comand> nosqllog
Example:
sp_ctrl (hostname:port#)> compare table SOURCEOWNER.TABLENAME to TARGETEOWNER.TABLENAME target TARGET_HOSTNAME@o.TARGET_SID where "COLNAME in ('6027632','6027648')" nosqllog
Note: Using the nosqllog option, the big *.sql file will not be generated. This option is recommended when running compare/repair for a big table with lots of rows are OOS. Optionally, can fix the out of sync for a big table, using the copy command. -
Additional Information
The file size or the i-node number is larger than the maximum value that can be represented in the stat structure pointed to by the Buffer parameter. The error found from truss command is EOVERFLOW. SharePlex compare uses stat structure , which is 32 bit function.
The difference between 64 bit and 32 bit for stat function:
The stat64, lstat64, and fstat64 subroutines are similar to the stat, lstat, fstat subroutines except that they return file information in a stat64 structure instead of a stat structure. The information is identical except that the st_size field is defined to be a 64-bit size. This allows stat64, lstat64, and fstat64 to return file sizes which are greater than OFF_MAX (2 gigabytes minus 1). SharePlex is a 32 bit application using 32 bit function, which is stat function. So limitation of it is 2 G.