Re: standby db - ora16166 LGWR timed out on Network Server 1 due to buffer full condition

  • From: Carel-Jan Engel <cjpengel.dbalert@xxxxxxxxx>
  • To: Patty.Charlebois@xxxxxxxxxxxxxx
  • Date: Thu, 20 Jan 2005 22:41:57 +0100

Sad to hear they stopped the project.
I did about 30 successfull DG installations so far. I've seen this
before, Oracle consultants with weird thoughts of causes of problems. I
wasn't there at that moment, so I cannot really judge his conclusions,
but ignorance and lack of experience appear to be very often the cause
of this. DG has lots of features to handle exactly the problem you
described. I ran it on a 1 Mb WAN connection....
Best regards, Carel-Jan

Best regards,

Carel-Jan Engel

If you think education is expensive, try ignorance. (Derek Bok)

Upcoming appearances: 

      * Jan 27, 2005: London, UKOUG Unix SIG: Data Guard Best Practices 
      * Feb 9-10, 2005: Denver, RMOUG Training Days: Data Guard
        Performance Issues 
      * Mar 6-10, 2005: Dallas, Hotsos Symposium: Data Guard Performance

On Thu, 2005-01-20 at 18:59, Patty.Charlebois@xxxxxxxxxxxxxx wrote:

> Not sure that this has anything to do with your problem but we were
> getting the same error message on our primary site when we put a logical
> standby into production in November.
> We had an Oracle consultant on-site helping us with our implementation and
> he determined that the error was occurring because we did not have a
> dedicated network connection between the primary and standby servers. The
> shared network resource did not have available bandwith for the primary to
> ship the archive log data in the buffer to the standby server.  In our
> case this hung up our production database :(.
> We never did do anymore investigation to prove the guy right or wrong
> because the next day they pulled the plug on the Data Guard project.
> Patty


Other related posts: