With the aid of additional information kindly provided by Christian I was able to reproduce the problem. The fix will be contained in one of the next MaxDB versions. As a workaround you should drop all tables having triggers manually, before you drop the corresponding schema.
Best regards, Thomas Thomas Anhaus mailto: [EMAIL PROTECTED] www.sap.com Sitz der Gesellschaft/Registered Office: Walldorf, Germany Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, Léo Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner Registergericht/Commercial Register Mannheim No HRB 350269 Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Christian Ullrich > Sent: Freitag, 23. März 2007 15:55 > To: [email protected] > Subject: Re: Kernel crash (access violation) with 7.6.0.34 > > * Christian Ullrich wrote: > > > I'm running MaxDB 7.6.0.34 (Win32) on Windows 2003. When running a > > long(ish) series of statements from SQL Studio, the kernel crashes, > > > I'll be glad to provide the statements leading to this crash, > > In a new instance, the initial schema load (that's what I was trying > to do) works fine, and the database structure is completely intact > afterwards. If I then simply drop the schema I've been working in, the > kernel crashes. > > By trying to drop as few objects manually as possible before dropping > the schema, I've found that my two triggers (INSERT and UPDATE for the > same table) seem to cause the problem. I can drop the schema > only after > removing the triggers first. If I drop the schema with the triggers on > the table, er, boom. > > Is this a known bug? > > -- > Christian Ullrich > > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
