sql error -750
Posted in 2003
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL, Platform-Specific Issues
Dear all,
OS: Solaris 2.6
IDS: 7.31.UC2
Problem:
SQL statement error number -750.
Invalid distribution format found for sn
I have shopfloor application (with multiple executable
4gl programs) running on the IDS database engine
(7.31.UC2). Some of the 4gl programs always hitting
the sql error -750 on those highly used tables. I know
one of the method to resolve the error is to re-build
the data distribution by running update statistics. I
have a script to run the update statistics for all the
tables with the following format.
update statistics low for table <tabname> dropdistributions;
update statistics medium for table <tabname>distributions only;
Although the above update statistis method is running
on daily basic, but the programs still hitting the
-750 error.
Is there other method to resolve the error?? Any
recommendation and advise are highly appreciated.
Thanks & regards,
Miyaki
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
sending to informix-list
miyaki wrote:
> OS: Solaris 2.6
> IDS: 7.31.UC2
> Problem:
> SQL statement error number -750.
> Invalid distribution format found for sn
>
> I have shopfloor application (with multiple executable
> 4gl programs) running on the IDS database engine
> (7.31.UC2). Some of the 4gl programs always hitting
> the sql error -750 on those highly used tables. I know
> one of the method to resolve the error is to re-build
> the data distribution by running update statistics. I
> have a script to run the update statistics for all the
> tables with the following format.
>
> update statistics low for table <tabname> drop> distributions;
> update statistics medium for table <tabname>> distributions only;
>
> Although the above update statistis method is running
> on daily basic, but the programs still hitting the
> -750 error.
>
> Is there other method to resolve the error?? Any
> recommendation and advise are highly appreciated.
You are too many revisions behind for comfort - upgrade to 7.31.UDx
for a sufficiently large value of x (about 5 or 6, IIRC).
Whether that will resolve this particular problem or not I'm not sure,
but there's at least a reasonable chance it will, and the upgrade is
highly desirable for other reasons too.
--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2003.04 -- http://dbi.perl.org/