Re: standby db - ora16166 LGWR timed out on Network Server 1 due to buffer full condition
- From: Carel-Jan Engel <cjpengel.dbalert@xxxxxxxxx>
- To: stevenoyle1@xxxxxxxxx
- Date: Wed, 19 Jan 2005 17:47:39 +0100
Can you reproduce it? Aftre the logswitch, will the error messages
reappear? This very much feels like a bug. I do not know it, and have
never seen this behaviour. I'd search the bug-database at Metalink
first. If it isn't resolved in a more recent release I'd file an itar.
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
Issues
On Wed, 2005-01-19 at 14:38, steve noyle wrote:
> yes, the standby is pingable and the RFS process and
> listener are running at the standby.
>
> OS - solaris 8
>
> the only entry in sqlnet.ora on both the primary &
> standby is
> NAMES.DIRECTORY_PATH= (TNSNAMES,HOSTNAME)
>
> v$database on primary shows primary,archivelog,read
> write, maximum performance
>
> v$database on standby shows physical standby,
> archivelog, mounted, maximum performance
>
> When I switched log file, the logfile got applied at
> the standby site almost instantaneously. I created a
> couple of objects on the primary and did verify that
> they got created on the standby.
>
> I've been getting this error when there were no
> activities on the database and yet when I tested
> loading a table yesterday, no error message.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
