Why in dataguard standby side RFS, LNS, LGWR or ARCn generate large trace file without any errors or issues

Why in dataguard standby side RFS, LNS, LGWR or ARCn generate large trace file without any errors or issues?

My standby database side i observed trace files for rfs process are growing in GBs always.
its due to parameter log_archive_trace value set in instance level in standby side.

if log_archive_trace value set for non zero, the trace files size will grow. resolution is to set it to  zero value.

In my case, i can see the value is 255.

SQL> show parameter log_archive_trace

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
log_archive_trace                    integer     255

i set it to 0, its fixed the proble,.

SQL> alter system set log_archive_trace=0 scope=both;

System altered.

if you are using DB brocker. set this value also to consistent in instance level and DG brocker level.

DGMGRL> show instance 'ORCL' 'LogArchiveTrace';

  LogArchiveTrace = '255'

DGMGRL> edit instance 'ORCL' SET PROPERTY 'LogArchiveTrace'=0;

Property "LogArchiveTrace" updated

DGMGRL> show instance 'ORCL' 'LogArchiveTrace';

  LogArchiveTrace = '0'

OPatch failed with error code 2

When i check the patch conflict for a patch, got below error.

]$opatch prereq CheckConflictAgainstOHWithDetail -ph ./
Oracle Interim Patch Installer version 12.2.0.1.6
Copyright (c) 2020, Oracle Corporation.  All rights reserved.

PREREQ session

Oracle Home       : /u01/oracle/product/12.2.0.1/dbhome_1
Central Inventory : /u01/oracle/oraInventory
   from           : /u01/oracle/product/12.2.0.1/dbhome_1/oraInst.loc
OPatch version    : 12.2.0.1.6
OUI version       : 12.2.0.1.4
Log file location : /u01oracle/product/12.2.0.1/dbhome_1/cfgtoollogs/opatch/opatch2020-07-11_14-10-25PM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

Prereq "checkConflictAgainstOHWithDetail" is not executed.

The details are:
Unable to create Patch Object.
Exception occured : /u01/oracle/psu/30783641/30886680/etc/config/actions.xml with Version field of the component "delete" in actions file cannot be <null> or empty. Please check patch metadata.

OPatch failed with error code 2

Solution:

its due to OPatch version is not compatible for the patch you are trying to apply. download latest opatch utility from metalink and unzip in ORACLE_HOME location. you can download latest OPatch  here

In my case, Opatch version is 12.2.0.1.6 but in patch read me file mentioned it required 12.2.0.1.19 or later 

after adding new OPatch version issue is resolved.