Prev: Error accessing Package SYSLH203
Next: Result set from ADMIN_CMD
From: soccertl on 25 Oct 2006 19:01
We have had a couple situations where DB/2 died due to someone sending
one of the DB/2 processes a kill 9. When this occurs, DB/2 goes down
and I noticed in the db2dump directory some files called
db2eventlog.000 and db2eventlog.000.crash. I renamed one of them to
00000000.evt and tried to run db2evmon against it but get the following
error:

Reading /home/hdbuser/sqllib/db2dump/00000000.evt ...
ERROR: Unexpected Memory model specified for trace in:
/home/hdbuser/sqllib/db2dump

Are these files not really event logs? Does anyone know anything about
them or what they might be? They are unreadable.

From: Larry on 25 Oct 2006 19:08
I don't know, but it's not a good idea to kill db2 by issuance of a kill
-9.

Larry Edelstein

soccertl wrote:

> We have had a couple situations where DB/2 died due to someone sending
> one of the DB/2 processes a kill 9. When this occurs, DB/2 goes down
> and I noticed in the db2dump directory some files called
> db2eventlog.000 and db2eventlog.000.crash. I renamed one of them to
> 00000000.evt and tried to run db2evmon against it but get the following
> error:
>
> Reading /home/hdbuser/sqllib/db2dump/00000000.evt ...
> ERROR: Unexpected Memory model specified for trace in:
> /home/hdbuser/sqllib/db2dump
>
> Are these files not really event logs? Does anyone know anything about
> them or what they might be? They are unreadable.
>
From: soccertl on 25 Oct 2006 20:08

Larry wrote:
> I don't know, but it's not a good idea to kill db2 by issuance of a kill
> -9.
>
> Larry Edelstein
>
> soccertl wrote:
>
> > We have had a couple situations where DB/2 died due to someone sending
> > one of the DB/2 processes a kill 9. When this occurs, DB/2 goes down
> > and I noticed in the db2dump directory some files called
> > db2eventlog.000 and db2eventlog.000.crash. I renamed one of them to
> > 00000000.evt and tried to run db2evmon against it but get the following
> > error:
> >
> > Reading /home/hdbuser/sqllib/db2dump/00000000.evt ...
> > ERROR: Unexpected Memory model specified for trace in:
> > /home/hdbuser/sqllib/db2dump
> >
> > Are these files not really event logs? Does anyone know anything about
> > them or what they might be? They are unreadable.
> >

Well, I know. We are not killing db2. We can't figure out where that is
coming from. I was just wondering if those event logs could help us
track what was occurring at the time this happened.

From: shenanwei on 25 Oct 2006 21:51
those 2 files is not parable by db2 event monitor. It is for db2
technical support.
soccertl wrote:
> Larry wrote:
> > I don't know, but it's not a good idea to kill db2 by issuance of a kill
> > -9.
> >
> > Larry Edelstein
> >
> > soccertl wrote:
> >
> > > We have had a couple situations where DB/2 died due to someone sending
> > > one of the DB/2 processes a kill 9. When this occurs, DB/2 goes down
> > > and I noticed in the db2dump directory some files called
> > > db2eventlog.000 and db2eventlog.000.crash. I renamed one of them to
> > > 00000000.evt and tried to run db2evmon against it but get the following
> > > error:
> > >
> > > Reading /home/hdbuser/sqllib/db2dump/00000000.evt ...
> > > ERROR: Unexpected Memory model specified for trace in:
> > > /home/hdbuser/sqllib/db2dump
> > >
> > > Are these files not really event logs? Does anyone know anything about
> > > them or what they might be? They are unreadable.
> > >
>
> Well, I know. We are not killing db2. We can't figure out where that is
> coming from. I was just wondering if those event logs could help us
> track what was occurring at the time this happened.

From: soccertl on 26 Oct 2006 10:26

shenanwei(a)gmail.com wrote:
> those 2 files is not parable by db2 event monitor. It is for db2
> technical support.
> soccertl wrote:
> > Larry wrote:
> > > I don't know, but it's not a good idea to kill db2 by issuance of a kill
> > > -9.
> > >
> > > Larry Edelstein
> > >
> > > soccertl wrote:
> > >
> > > > We have had a couple situations where DB/2 died due to someone sending
> > > > one of the DB/2 processes a kill 9. When this occurs, DB/2 goes down
> > > > and I noticed in the db2dump directory some files called
> > > > db2eventlog.000 and db2eventlog.000.crash. I renamed one of them to
> > > > 00000000.evt and tried to run db2evmon against it but get the following
> > > > error:
> > > >
> > > > Reading /home/hdbuser/sqllib/db2dump/00000000.evt ...
> > > > ERROR: Unexpected Memory model specified for trace in:
> > > > /home/hdbuser/sqllib/db2dump
> > > >
> > > > Are these files not really event logs? Does anyone know anything about
> > > > them or what they might be? They are unreadable.
> > > >
> >
> > Well, I know. We are not killing db2. We can't figure out where that is
> > coming from. I was just wondering if those event logs could help us
> > track what was occurring at the time this happened.

Ah, ok. Thanks. That explains it.

 | 
Pages: 1
Prev: Error accessing Package SYSLH203
Next: Result set from ADMIN_CMD