DB2/LUW events.bin files in db2dump

Tony Moore

DB2/LUW events.bin files in db2dump
Could someone answer what would have generated these type files in my
/home/<db2instance>/sqllib/db2dump directory?

DBACRD.20140429114924.000.SQLP.GENERAL.events.bin
DBACRD.20140429114924.000.SQLP.HADR.events.bin
DBACRD.20140429114924.000.SQLP.HIGHFREQ.events.bin
DBACRD.20140429114924.000.SQLP.SHREDDER_LOW.events.bin
DBACRD.20140429114924.000.SQLP.SHREDDER_MASTER.events.bin
DBACRD.20140429114924.000.SQLP.SHREDDER_WORKER.events.bin

...this is a DB2/LUW V10.5 system running on AIX.

I would assume, since there are several instance of these, all timstamped
on 4/29 or older, I can remove them, but you know what happens when you
assume.

Thanks!

Tony Moore
DB2 Mainframe Dinosaur

Philip Gunning

DB2/LUW events.bin files in db2dump
(in response to Tony Moore)
Any type of severe error could have caused them. Take a look at the db2diag.log around the time of the dumps to see if you can discern what caused them. If you can tie them to something that someone did or ran, look at that further. If you can't tie to anything specifically, keep around for awhile to see if it reoccurs. If so open PMR, if not safely delete them after a period of time. PG

Sent from my iPhone
Www.philipkgunning.com
IBM Champion for Information Management
DB2-L Hall of Fame
Former DB2-L List owner and Admin
www.philipkgunning.com/askmrdb2

> On Jun 20, 2014, at 2:16 PM, Tony Moore <[login to unmask email]> wrote:
>
> Could someone answer what would have generated these type files in my /home/<db2instance>/sqllib/db2dump directory?
>
> DBACRD.20140429114924.000.SQLP.GENERAL.events.bin
> DBACRD.20140429114924.000.SQLP.HADR.events.bin
> DBACRD.20140429114924.000.SQLP.HIGHFREQ.events.bin
> DBACRD.20140429114924.000.SQLP.SHREDDER_LOW.events.bin
> DBACRD.20140429114924.000.SQLP.SHREDDER_MASTER.events.bin
> DBACRD.20140429114924.000.SQLP.SHREDDER_WORKER.events.bin
>
> ...this is a DB2/LUW V10.5 system running on AIX.
>
> I would assume, since there are several instance of these, all timstamped on 4/29 or older, I can remove them, but you know what happens when you assume.
>
> Thanks!
>
> Tony Moore
> DB2 Mainframe Dinosaur
>
> Site Links: View post online View mailing list online Start new thread via email Unsubscribe from this mailing list Manage your subscription
> ** ** ** Attend the 2014 EMEA IDUG DB2 Tech Conference ** ** **
> ---> Prague, Czech Republic, 9 - 14 November, 2014 <---
> www.bit.ly/IDUGEMEA2014
>
> Use of this email content is governed by the terms of service at:
> http://www.idug.org/p/cm/ld/fid=2

Krishna Murakonda

RE: DB2/LUW events.bin files in db2dump
(in response to Tony Moore)

My observation, these events.bin files generated after fix pack update on CDC replication enabled system. CDC causing the alerts generated at db2dump.

Solution: Check the permission on CDC replicated replicated tables and perform full refresh.

 

Krishna Murakonda

Nadir Doctor

DB2/LUW events.bin files in db2dump
(in response to Krishna Murakonda)
Hi Krishna,

It seems that you have replied to an initial thread which is more than 3
years old and can therefore be closed now.


Best Regards,
Nadir



On Mon, Sep 4, 2017 at 10:58 PM, Krishna Murakonda <[login to unmask email]>
wrote:

> My observation, these events.bin files generated after fix pack update on
> CDC replication enabled system. CDC causing the alerts generated at db2dump.
>
> Solution: Check the permission on CDC replicated replicated tables and
> perform full refresh.
>
>
>
> Krishna Murakonda
>
> -----End Original Message-----
>