Just saw you mentioned up there that you're on HP-UX...that would be /var/adm/syslog/syslog.log On Tue, Mar 23, 2010 at 2:22 PM, Benjamin <anangwe@gmail.com> wrote:
mostly hardware!
else try these i hope it works
In order to correct this error, try to eliminate the *lasterror* first, as this might be one of the causes for this error (except when *lasterror* is 0).
Also, try rerunning the command referenced in the SQL causing error to see if the problem reoccurs.
If the process is infected with 11 and the problem can be reproduced, try and correct it as follows:
1.
If the SQL causing error is a compiled object such as a stored procedure, trigger, or view, drop and recreate the object. 2.
If the SQL causing error is ad hoc rather than a compiled object, moving the data may fix the problem. Use one of these options: -
Select the table data into a new table, drop the old table, and rename the new table to the old table name. -
Bulk copy the affected table out, drop and re-create the table, and bulk copy back in. This is the most efficient solution for a very large table.
If moving the data corrects the problem, the data may have been corrupt. Be aware that moving corrupted data can lead to a data loss.
Check your hardware error log as this error can be caused by hardware failure as well.
_______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------ Skunkworks Server donations spreadsheet
http://spreadsheets.google.com/ccc?key=0AopdHkqSqKL-dHlQVTMxU1VBdU1BSWJxdy1f... ------------ Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke