Friday 4 February 2022

Tracing Oracle Data Guard

 Tracing can also be enabled in dataguard using the parameter "Log_Archive_Trace"


The values can be set using DG-Broker (if configured) or at SQL prompt as below.



     // Tracing primary site 



DGMGRL> edit database 'primary_db_name' set property LogArchiveTrace='1';



    // Tracing standby site



DGMGRL> edit database 'standby_db_name' set property LogArchiveTrace='1';




Also this parameter can be set by issuing a SQL statement :

SQL> ALTER SYSTEM SET LOG_ARCHIVE_TRACE=1;



dgmgrl  -debug / shutdown command  will shutdown instance, generate trace file and then exit. Tracefiles will be generated in the specific dump location.


Values for LOG_ARCHIVE_TRACE are described in table bellow:


LevelMeaning
0Disables archived redo log tracing (default setting)
1Tracks archiving of log files
2Tracks archive status by archive log file destination
4Tracks archive operational phase
8Tracks archive log destination activity
16Tracks detailed archive log destination activity
32Tracks archive log destination parameter modifications
64Tracks ARCn process state activity
128Tracks FAL server process activity
256Tracks RFS Logical Client
512Tracks LGWR redo shipping network activity
1024Tracks RFS physical client
2048Tracks RFS/ARCn ping heartbeat
4096Tracks real-time apply activity
8192Tracks Redo Apply activity (media recovery or physical standby)

No comments:

Post a Comment