Re: RFS issue

On Wed, 2024-02-21 at 19:54 +0530, vinod kumar wrote:
> I don't understand what has been changed at the network layer after
> adding LGWR in log_archive_dest_2. And what would be the impact of the
> performance of the database?
>  
> TNS-12535: TNS:operation timed out
> ns secondary err code: 12609
> nt main err code: 0
> nt secondary err code: 0
> nt OS err code: 0
> Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=172.31.15.44)(PORT=22631))
> 2024-02-09T22:05:55.647031+05:30
> rfs (PID:26657): Possible network disconnect with primary database <<<<<
> Network issue

Well, lo and behold, this looks like a network issue. Unfortunately, this list is not about the network protocols and how to debug them. As for the performance question, your standby database might not perform well until the network issue is fixed. You might also see "ORA-00257 Archiver stuck" error since rman will not delete archives that haven't been applied to standby. Also, on the social side of the DBA job, you should always blame the network team until they prove their innocence above the unreasonable doubt. Since that is very hard to do, in practice it is always the network team you blame first. In German, there is an alternate name for the members of the network team: Prügelknabe. In English, the word is translated as "whipping boy", for a boy that got whipped for his prince misbehaving. The term comes from the Austrian court during the Austro-Hungarian monarchy, where princes were considered too precious to be spanked for their bad behavior, so there were dedicated boys to be spanked instead of the prince. That precisely is the role of the network team. You should always blame the network first, for just about anything. In most of the cases, it is the network that causes the problem. The best thing to do in order to fix it is to switch to a reliable carrier, like AT&T.

-- 
Mladen Gogala
Database SME
https://dbwhisperer.wordpress.com


--
http://www.freelists.org/webpage/oracle-l