Hi. I'm new to the MaxDB mailing list.
I have a table that I suspect may be corrupt. I'll start with the problem, the symptoms, and what I've attempted so far. Can someone please explain what is happening and give me some suggestions to try next? We have a table called LOGDETAILS. It contains IP accounting information. I need to correct some old logs. To do this I need to update a field called LS_ERROR. Every appropriate UPDATE variant I have tried has resulted in the following error: General error;-9111 POS(1) System error: Move error. Even a query as simple as: UPDATE LOGDETAILS SET LS_ERROR = 3 WHERE LS_PKEY = <any valid key> I then tried imitating an UPDATE query using an atomic DELETE/INSERT pair. This should not even be necessary but, due to time constraints and lack of SAP DB expertise, it became the next in a series of last ditch efforts. That failed, too. The DELETE succeeded but the INSERT resulted in an error about a secondary key. In the SAP DB documentation the terms "secondary key" and "index" seem to be used interchangeably. This is confusing because I would expect indexes to have no bearing on whether or not a record can be inserted. At the most, I expected the database to simply reindex. I then tried an even more abstract approach. Again, it should not even be necessary. I was going to try creating a new table as a copy of the original, shuffling the tables so that the new takes the place of the old, then fixing the table and reapplying the indexes. Unfortunately, the very first step failed. Only 1/4 of the logs were copied to the new table. Here is a copy of the queries and their results: SELECT COUNT(*) FROM LOGDETAILS > 1963593 CREATE TABLE LOGDETAILS_COPY AS SELECT * FROM LOGDETAILS > OK SELECT COUNT(*) FROM LOGDETAILS_COPY > 479158 SELECT COUNT(*) FROM LOGDETAILS > 1963593 I have run out of approaches and I do not understand the reason for the difficulties in the first place. Can someone please tell me why I cannot do any of the operations I have tried? Even better, does anyone know how to fix it so that I can? If not, does anyone have any other suggestions for updating the LS_ERROR field? Thanks. Regards, David Taylor. ________________________________________________ Message sent using ram.net WebMail 2.7.2 -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
