Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MaxDB - Everything about MaxDB, formerly known as SAP DB
MySQL++ - Programming with the C++ API to MySQL
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
mysql openssl Question
mysql:it 's a db not a dbms how it 's possible?!
Does the binary log enabling affect the MySQL performances?
Strange behavior, Table Level Permission
FULLTEXT query format question
Preventing Duplicate Entries
Comparing and writing out BLOBS
Executing MySQL Commands From Within C Program
Can 't access mysql after kernel upgrade
Mysql 4 0 Oracle Stored Procedure Trigger Conversion
Downgrade Mysql from 4 to 3 23
MySQL Cluster Software
mysql test 4 1 fails with the gis test
ERROR 2002: Can 't connect to local MySQL server through socket
Getting Identity after INSERT
Update one field with more fields from another table
ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
mysql have same function mthod as Oracle decode()
 
Invalid trigger after upgrade from 7.4 to 7.6 (AK Catalog information not fou

Invalid trigger after upgrade from 7.4 to 7.6 (AK Catalog information not fou

2007-01-16       - By Anhaus, Thomas

 Back
Kolja Kleist wrote :

>Hello List,

>After upgrading my database from sapdb 7.4.3.32 to maxdb 7.6.0.34
>I got an error when deleting a row from a specific table:
>AK Catalog information not found

>I found a posting from this list which says that the delete trigger may
have
>a problem.

>But when I try to select the triggers from the db (SELECT DISTINCT
>schemaname FROM domain.triggers WHERE TRIGGERNAME LIKE '%')
>or if I try to drop the trigger I got the same error:

>System error: AK Catalog information not found:0000000000000000007200

>So what should I do now?

>Any help would be nice,

>Regards, Kolja

Unfortunately there's not much you can do. It seems that the migration
process from 7.4.03 to 7.6.0 produced a catalog inconsistency, which
cannot be repaired with the current facilities.  
I recomment to suspend the affected table T, i.e.

RENAME T TO SUSPENDED
CREATE TABLE T LIKE SUSPENDED
INSERT INTO T SELECT * FROM SUSPENDED
DELETE SUSPENDED (if possible)
recreate all views, synonyms, triggers etc. based on T

Best Regards,
Thomas