DDR Log Snooping ...

IDS 11.50.fc5 Aix 5.3 DDR Log Snooping - DDRBLOCK ... My engine crashed this evening ... and a big ER update had been being processed. When the engine was brought back up, after the logical recovery the above started. I've checked onstat -g ddr and onstat -g rcm ... I can see things moving through the output changing .. ie. number of log records and such .. My question is, can I somehow find where in the process it is? It's been running for about 4 hours. I'm trying to determine if I should just kill the engine and restart it without ER, 'oninit -D', and then rebuild the replication ... or just let this go, hoping it finishes soon. One other item, the log that it began snooping in was about 6.5 hours before the crash. Thanks for the help ... Peter Peter Logan Senior Database Administrator Phone: 616/878-8309

You could just bring ER down (cdr stop) followed by cdr cleanstart. And then run cdr check --repair. Alternatively you could add chunks to the stable queue. Sent from my iPad On Jun 12, 2013, at 4:47 AM, "Peter_Logan@spartanstores.com" <Peter_Logan@spartanstores.com> wrote: > IDS 11.50.fc5 > Aix 5.3 > > DDR Log Snooping - DDRBLOCK ... > > My engine crashed this evening ... and a big ER update had been being > processed. When the engine was brought back up, after the logical > recovery the above started. I've checked onstat -g ddr and onstat -g rcm > .... I can see things moving through the output changing .. ie. number of > log records and such .. My question is, can I somehow find where in the > process it is? It's been running for about 4 hours. I'm trying to > determine if I should just kill the engine and restart it without ER, > 'oninit -D', and then rebuild the replication ... or just let this go, > hoping it finishes soon. One other item, the log that it began snooping > in was about 6.5 hours before the crash. > > Thanks for the help ... > > Peter > > Peter Logan > Senior Database Administrator > Phone: 616/878-8309 > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >

Thanks .. I'll remember that for the next time something like this happens ... Peter Logan Senior Database Administrator Phone: 616/878-8309 From: "Madison Pruet" <mpruet@us.ibm.com> To: ids@iiug.org, Date: 06/12/2013 08:56 AM Subject: Re: DDR Log Snooping ... [30510] Sent by: ids-bounces@iiug.org You could just bring ER down (cdr stop) followed by cdr cleanstart. And then run cdr check --repair. Alternatively you could add chunks to the stable queue. Sent from my iPad On Jun 12, 2013, at 4:47 AM, "Peter_Logan@spartanstores.com" <Peter_Logan@spartanstores.com> wrote: > IDS 11.50.fc5 > Aix 5.3 > > DDR Log Snooping - DDRBLOCK ... > > My engine crashed this evening ... and a big ER update had been being > processed. When the engine was brought back up, after the logical > recovery the above started. I've checked onstat -g ddr and onstat -g rcm > .... I can see things moving through the output changing .. ie. number of > log records and such .. My question is, can I somehow find where in the > process it is? It's been running for about 4 hours. I'm trying to > determine if I should just kill the engine and restart it without ER, > 'oninit -D', and then rebuild the replication ... or just let this go, > hoping it finishes soon. One other item, the log that it began snooping > in was about 6.5 hours before the crash. > > Thanks for the help ... > > Peter > > Peter Logan > Senior Database Administrator > Phone: 616/878-8309 > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.