Re: Urgent replication problem

Backup of logical log on primary is not an issue. Even after the backup, logs are still on disk and can be used for sending to secondary. If logs that is required by secondary is not on the primary's disk, secondary will request it from backup and you will see a message in server log. -Ajay Gupta "Bjorn De Waele" <bjornREMTHIS@pandora.Be> wrote in message news:<UpQUc.218475$BL6.10847290@phobos.telenet-ops.be>... > I've been looking in the administrator guide and right now, I've found > something which could declare my problem ! > > In the admin guide, I've read that the logical logs are being sent to the > secondary... as long as they reside on disk ..... But we're running > continuously logical log backup to tape. So we did an ontape -s but our > logical logs are being backed-up still to tape... so when we've copied, > restored and started the secondary, we're about 5 logical logs further. > Could this cause the problem ? Do you need to stop the ontape -c while > you're backing-up and restoring ? > > Thanks a lot ! > > Bjorn > > > "Bjorn De Waele" <bjornREMTHIS@pandora.Be> wrote in message > news:C0PUc.218383$BL6.10847290@phobos.telenet-ops.be... > > Hello everybody, > > > > > > today we brought our dbase down to finetune our onconfig. After it, it > > couldn't get started anymore. So we placed our old onconfig back. > > > > Everything was fine again except that our secondary stayed in fast > > recovery mode. It was very long so we supposed that our replication was > > corrupt. No problem, we made a new ontape -s and set our replica up > > again. > > But right now we still have the same problem .... Our replica stays in > > fast recovery mode. We're running 9.21 TC3. > > After 3 hours, it was still the same, no activity on the server. > > > > I did some tests with the onstat -p to check disk activity. I resetted > > the activity with onstat -z before the replica thread started (onstat -g > > ath). Once the replica started, my pagewrites went step by step to 84000 > > but there it stands.... nothing happens anymore.... > > > > In onstat -d, I don't see down chunks. > > Onstat -g ath gives me a cond wait for drcb_bqe in dr_secrcv > > > > I think the thread is waiting and waiting ... but I don't know for what ! > > > > I really hope someone could help me out or hint me cause we're running our > > reports on that secondary. > > > > Thanks in advance ! > > > > Bjorn > >