Hello all This is only a report of a problem and the solution to that problem (we've found the latter in that mailing list, too).
We executed some changes of the catalog of a table. Which manipulation effectively caused the final problem we can't reproduce anymore. The result was that any trial to remove the added column or to modify the datatype of it caused the following error: -9205 POS(1) System error: AK Catalog information not found:0000000000000DCC006100 Here is a list of the manipulations done before: - alter table <tabname> add <colname, datadef...> - alter table <tabname> modify <colname default null> - alter table <tabname> column <colname, datadef[same datadefinition as above]> - update <tablename> set <colname>=(another query) The problem could be solved by the execution of the statement CHECK TABLE <tabname> CATALOG Best regards, G. Matter -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
