![]() |
Dbvisit home |
|
#1
|
|||
|
|||
|
We have had a situation over the weekend whereby the normal log switching of every 10 minutes on the primary database seemed to stop. We got lots of errors (same one repeated) such as :
201207290348 - Unable to find log file after 114 times. MAX_TIMES_TRIED (10) exceeded. Log sequence 2529 thread 1 still not on standby site. Dbvisit Standby terminated. Return code = 409 Two days later it seemed to 'start again' without any manual intervention. Neither the Oracle alert log nor the dbvisit hist log seem give any indication as to why this has happened. There was no outage and no logs lost. Potentially however if we had lost the primary then we could have lost 2 days worth of data. Has anyone else experienced this ? |
|
#2
|
|||
|
|||
|
Hi Peter,
What mechanism are you using to schedule the running of Dbvisit Standby? |
![]() |
| Tags |
| archive logging stopped |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|