Hi, While Holger is away, does anyone know how I can get around this crash?
As the notes below explain (especially the first one) we are issuing an "update stat * estimate", and when we do we repeatedly (though not every time) get a kernel.exe crash. Once everything is loaded in the base tables, only our metrics table changes much over time - all our printing is captured there, so it can change dramatically. Also, the explain for the query we commonly execute involves only an index scan and a join on key column. Will this be seriously affected if we take out the update stat altogether? Cheers, David ---------------------- Forwarded by David Hay/Lex/Lexmark on 28/07/2003 02:38 PM --------------------------- "Becker, Holger" <[EMAIL PROTECTED]> on 18/07/2003 12:14:55 PM To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject: RE: Database Crash Hi David, until now we couldn't exclude any thing also the other activities on your database because we don't know what happened exactly. The update stat command changes some catalog informations and so it have to be logged to be "rollbackable". The trace shows that while writing the before and after image a log error happened and this will result in an emergency shutdown. My next reply will reach you in two weeks. Kind regards, Holger SAP Labs Berlin > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Freitag, 18. Juli 2003 16:44 > To: Becker, Holger > Subject: RE: Database Crash > > > > Hi Holger, > > Thanks for the quick reply! > > Will try that. There was lots of other database activity > going on at the > time, including some of the tables being locked exclusively. > Will this > affect the update stat? I thought I read that it wouldn't, > but could well > be wrong. > > Could you explain further on what you mean by "update > statistic command and > logging"? Is the logging affecting the update stat command? We have > logging set to "auto overwrite on". > > Many thanks, > > David > > > > > > "Becker, Holger" <[EMAIL PROTECTED]> on 18/07/2003 10:34:40 AM > > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> > cc: > Subject: RE: Database Crash > > > Hi David, > > sure, I'll tell the log developer to keep you up to date. > > But as I wrote it seems to be a problem with update statistic > command and logging perhaps it could be a workaround to change > your update stat behavior. > > In the vtrace I saw an "updtat statistics * estimate". > Try it with an update statistics * estimate sample 10 percent. > > Kind regards, > Holger > SAP Labs Berlin > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Freitag, 18. Juli 2003 16:21 > > To: Becker, Holger > > Subject: RE: Database Crash > > > > > > > > Hi Holger, > > > > Thanks for the note. > > > > We are in some time crunch with solving this. Would there be > > any way you > > could have someone else monitor the issue while you're gone > > and let us know > > an update as soon as it becomes available? > > > > many thanks, > > > > David > > > > > > > > > > "Becker, Holger" <[EMAIL PROTECTED]> on 18/07/2003 09:36:06 AM > > > > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> > > cc: > > Subject: RE: Database Crash > > > > > > Hello David, > > > > no problem with direct mail but for the next two weeks > > im on vacation so my answers will come with some delay. > > > > Now to your question. > > > > The provided knldiag and trace.txt shows a log error > > at update statistics command. It seems to be a unknown bug. > > I've forwarded your mail to our log developers. > > > > I think they will contact you if they need further information > > and of course let you know if they find the bug. > > > > Best regards, > > Holger > > SAP Labs Berlin > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Sent: Donnerstag, 17. Juli 2003 21:05 > > > To: Becker, Holger > > > Subject: Database Crash > > > > > > > > > Hi Holger, > > > > > > I guess zip file was too big the first time - took out log > > and trying > > > again! > > > > > > Cheers, > > > > > > David > > > (See attached file: dbm.zip) > > > ---------------------- Forwarded by David Hay/Lex/Lexmark on > > > 17/07/2003 > > > 03:05 PM --------------------------- > > > > > > > > > David Hay > > > 17/07/2003 11:22 AM > > > > > > To: "Becker, Holger" <[EMAIL PROTECTED]> > > > cc: > > > > > > Subject: Database Crash (Document link: David Hay) > > > > > > Hi Holger, > > > > > > Apologies for contacting you "off list" - not sure who to > > > send these files > > > to - we are seeing the database kernal just suddenly crashing > > > - and you've > > > been very helpful in the past. > > > > > > I turned vtrace on, and have extracted it into trace.txt in > > > attached zip > > > file, along with other files I thought you might need. > > > > > > Would really appreciate your help - can't see anything > > > obvious, and not > > > sure where to go next. > > > > > > Please let me know if you need more information. > > > > > > Cheers, > > > > > > David > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
