{"id":48988,"date":"2022-06-03T15:15:10","date_gmt":"2022-06-03T15:15:10","guid":{"rendered":"https:\/\/dbtut.com\/?p=48988"},"modified":"2022-06-03T15:19:27","modified_gmt":"2022-06-03T15:19:27","slug":"monitoring-the-environment","status":"publish","type":"post","link":"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/","title":{"rendered":"Monitoring The Environment"},"content":{"rendered":"

In today’s article, I will tell you about Data Guard Broker – Monitoring The Environment.<\/p>\n

After installing the Data Guard Environment and enabling the Broker Configuration, we need to check the operability of the system. Below are the DGMGRL commands to make these checks.<\/p>\n[Commands run from DGMGRL are all run from Primary-1 by connecting to DGMGRL]\n

1. Our first check query is to query the entire configuration.<\/p>\n

DGMGRL> show configuration\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n    standby - Physical standby database\r\n    logical - Logical standby database\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n<\/pre>\n
From here;<\/p>\n
Protection Mode,<\/p>\n
Which DBs are included in the Broker Environment,<\/p>\n
The status of Fast-Start-Failover,<\/p>\n
We can see the general status of the configuration.<\/p>\n
2. General checks can be made at the database level.<\/p>\n
DGMGRL> show database primary;\r\n\r\nDatabase - primary\r\n\r\n  Role:            PRIMARY\r\n  Intended State:  TRANSPORT-ON\r\n  Instance(s):\r\n    primary1\r\n    primary2\r\n\r\nDatabase Status:\r\nSUCCESS\r\n<\/pre>\n
From here;<\/p>\n
We learn the status of Redo Transport services.<\/p>\n
We learn the status of the database.<\/p>\n
DGMGRL> show database standby;\r\n\r\nDatabase - standby\r\n\r\n  Role:            PHYSICAL STANDBY\r\n  Intended State:  APPLY-ON\r\n  Transport Lag:   0 seconds (computed 2 seconds ago)\r\n  Apply Lag:       0 seconds (computed 2 seconds ago)\r\n  Apply Rate:      517.00 KByte\/s\r\n  Real Time Query: ON\r\n  Instance(s):\r\n    primary1 (apply instance)\r\n    primary2\r\n\r\nDatabase Status:\r\nSUCCESS\r\n<\/pre>\n
DGMGRL> show database logical;\r\n\r\nDatabase - logical\r\n\r\n  Role:            LOGICAL STANDBY\r\n  Intended State:  APPLY-ON\r\n  Transport Lag:   0 seconds (computed 1 second ago)\r\n  Apply Lag:       4 seconds (computed 1 second ago)\r\n  Apply Rate:      862.71 MByte\/s\r\n  Instance(s):\r\n    primary1v\r\n    primary2 (apply instance)\r\n\r\nDatabase Status:\r\nSUCCESS\r\n<\/pre>\n
From here;<\/p>\n
The role of databases,<\/p>\n
Whether or not Redo-Apply is active,<\/p>\n
Redo and Transport Lag information,<\/p>\n
Whether Real-Time-Query (Active Data Guard) is active for the Physical Standby Database,<\/p>\n
On which instances the Apply Services are running,<\/p>\n
We learn information about the status of databases.<\/p>\n
3. If Database or Configuration status is ERROR, we create an error condition to see the parameters to be checked.<\/p>\n
While the Broker Configuration is ENABLE, we are changing the parameters from SQLPLUS.<\/p>\n
[Primary-2] SQL> show parameter log_archive_dest_state_3\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\nlog_archive_dest_state_3             string      ENABLE\r\nlog_archive_dest_state_30            string      enable\r\nlog_archive_dest_state_31            string      enable\r\n[Primary-2] SQL> alter system set log_archive_dest_state_2=DEFER scope=both sid='*';\r\n\r\nSystem altered.\r\n<\/pre>\n
We are querying the Broker Configuration.<\/p>\n
DGMGRL> show configuration\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n      Error: ORA-16764: redo transport service to a standby database is not running\r\n\r\n    standby - Physical standby database\r\n    logical - Logical standby database\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nERROR\r\n<\/pre>\n
4. The error may not always be obvious as above. Below are the parameters we will look at in such cases.<\/p>\n
We’re looking at the broker’s logs.<\/p>\n
[oracle@primary2 ~]$ tail -100f \/u01\/app\/oracle\/diag\/rdbms\/primary\/primary2\/trace\/drcprimary2.log \r\n\r\n01\/16\/2017 10:12:02\r\nRedo transport problem detected: redo transport to database 'standby' is unexpectedly offline: DEFERRED\r\n<\/pre>\n
Note: It appears from the Error that the LOG_ARCHIVE_DEST_STATE_2 parameter is DEFERred.<\/p>\n
We can see the error with the “StatusReport” property without looking at the log.<\/p>\n
DGMGRL> show database primary 'StatusReport';\r\nSTATUS REPORT\r\n       INSTANCE_NAME   SEVERITY ERROR_TEXT\r\n            primary1      ERROR ORA-16738: redo transport service for database \"standby\" is not running\r\n            primary2      ERROR ORA-16738: redo transport service for database \"standby\" is not running\r\n<\/pre>\n
We also question other properties related to transport services.<\/p>\n
DGMGRL> show database primary 'LogXptStatus';\r\nLOG TRANSPORT STATUS\r\nPRIMARY_INSTANCE_NAME STANDBY_DATABASE_NAME               STATUS \r\n            primary1              standby                      \r\n            primary1              logical                      \r\n            primary2              standby                      \r\n            primary2              logical                      \r\n\t\r\nDGMGRL> show database primary 'InconsistentProperties';\r\nINCONSISTENT PROPERTIES\r\n   INSTANCE_NAME        PROPERTY_NAME         MEMORY_VALUE         SPFILE_VALUE         BROKER_VALUE \r\n   \r\nDGMGRL> Show database primary 'InconsistentLogXptProps';\r\nINCONSISTENT LOG TRANSPORT PROPERTIES\r\n   INSTANCE_NAME         STANDBY_NAME        PROPERTY_NAME         MEMORY_VALUE         BROKER_VALUE<\/pre>\n
LogXptStatus: Shows Transport Errors caught by all instances in the Primary Database.<\/p>\n
InconsistentProperties: Lists if there is an inconsistent situation in the broker configuration and database settings.<\/p>\n
InconsistentLogXptProps: Lists the inconsistencies between the Broker configuration and Redo Transport settings of parameters related to Redo Transport in Standby Databases.<\/p>\n
5. Suppose there are many log switch operations until the error is noticed. In this case, we can see which archive files are not processed as follows.<\/p>\n
We are doing the Log Switch operation for testing.<\/p>\n
[Primary-2] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n\r\n[Primary-2] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n\r\n[Primary-2] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n\r\n[Primary-2] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n<\/pre>\n
We check the Sequence numbers on the Primary and Standby sides.<\/p>\n
[Primary-2] SQL> select max(sequence#),thread# from v$archived_log group by thread#;\r\n\r\nMAX(SEQUENCE#)    THREAD#\r\n-------------- ----------\r\n           572          1\r\n           332          2\r\n<\/pre>\n
[Physical-2] SQL> select max(sequence#),thread# from v$archived_log group by thread#;\r\n\r\nMAX(SEQUENCE#)    THREAD#\r\n-------------- ----------\r\n           572          1\r\n           329          2\r\n<\/pre>\n
[Logical-2] SQL> SELECT max(sequence#),thread#,applied FROM dba_logstdby_log group by thread#, applied;\r\n\r\nMAX(SEQUENCE#)    THREAD# APPLIED\r\n-------------- ---------- --------\r\n           572          1 YES\r\n           332          2 YES\r\n<\/pre>\n
It is seen that some archives do not go to the Physical Standby side. These archives are seen by querying the “SendQEntries” property.<\/p>\n
DGMGRL> show database primary 'SendQEntries';\r\nPRIMARY_SEND_QUEUE\r\n        STANDBY_NAME       STATUS          RESETLOGS_ID           THREAD              LOG_SEQ       TIME_GENERATED       TIME_COMPLETED    FIRST_CHANGE#     NEXT_CHANGE#       SIZE (KBs) \r\n             standby                 ARCHIVED        932222810                2                          330                  01\/16\/2017 10:55:27  01\/16\/2017 10:55:35          6074895          6074922                8 \r\n             standby                 ARCHIVED        932222810                2                           331                 01\/16\/2017 10:55:35  01\/16\/2017 10:55:37          6074922          6074929                1 \r\n             standby                ARCHIVED        932222810                2                           332                  01\/16\/2017 10:55:37  01\/16\/2017 10:55:40          6074929          6074940                1 \r\n                                            CURRENT         932222810                1                           573                  01\/16\/2017 10:55:34                                                  6074936                                         2515 \r\n                                            CURRENT        932222810                 2                            333                  01\/16\/2017 10:55:40                                                  6074940                                          2967 \r\n<\/pre>\n
In the STATUS column here,<\/p>\n
CURRENT: Shows the Redo Log where currently writing is done.<\/p>\n
ARCHIVED: Indicates that online Redo Log’s writing process is completed, local archive is created but archive is not sent to standby side.<\/p>\n
NOT_ARCHIVED: Indicates that the online Redo Log’s writing process has been completed, but the local archive has not yet been retrieved.<\/p>\n
We ENABLE the DEFERRED LOG_ARCHIVE_DEST_STATE_2 parameter and query the status of the configuration.<\/p>\n
[Primary-1] SQL> alter system set log_archive_dest_state_2=enable scope=both sid='*';\r\n\r\nSystem altered.\r\n<\/pre>\n
DGMGRL> show configuration\r\n\r\nConfiguration - Broker_Configuration\r\n\r\n  Protection Mode: MaxPerformance\r\n  Databases:\r\n    primary - Primary database\r\n    standby - Physical standby database\r\n    logical - Logical standby database\r\n\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nSUCCESS\r\n<\/pre>\n
[Primary-2] SQL> select max(sequence#),thread# from v$archived_log group by thread#;\r\n\r\nMAX(SEQUENCE#)    THREAD#\r\n-------------- ----------\r\n           573          1\r\n           333          2\r\n<\/pre>\n
[Physical-2] SQL> select max(sequence#),thread# from v$archived_log group by thread#;\r\n\r\nMAX(SEQUENCE#)    THREAD#\r\n-------------- ----------\r\n           573          1\r\n           333          2\r\n<\/pre>\n
[Logical-2] SQL> SELECT max(sequence#),thread#,applied FROM dba_logstdby_log group by thread#, applied;\r\n\r\nMAX(SEQUENCE#)    THREAD# APPLIED\r\n-------------- ---------- --------\r\n           573          1 YES\r\n           333          2 YES\r\n<\/pre>\n
DGMGRL> show database primary 'SendQEntries';\r\nPRIMARY_SEND_QUEUE\r\n        STANDBY_NAME       STATUS     RESETLOGS_ID           THREAD              LOG_SEQ       TIME_GENERATED       TIME_COMPLETED    FIRST_CHANGE#     NEXT_CHANGE#       SIZE (KBs) \r\n                          CURRENT        932222810                1                  574  01\/16\/2017 11:21:41                               6080641                                36 \r\n                          CURRENT        932222810                2                  334  01\/16\/2017 11:21:45                               6080637                                32 \r\n<\/pre>\n
6. We first set up a test environment to learn about the property, where we can see which archives that come to the standby side are not APPLY. Then the relevant property is queried.<\/p>\n
On the logic side, we question the status of Redo -Apply.<\/p>\n
DGMGRL> show database logical;\r\n\r\nDatabase - logical\r\n\r\n  Role:            LOGICAL STANDBY\r\n  Intended State:  APPLY-ON\r\n  Transport Lag:   0 seconds (computed 1 second ago)\r\n  Apply Lag:       0 seconds (computed 1 second ago)\r\n  Apply Rate:      -939900928 Byte\/s\r\n  Instance(s):\r\n    primary1\r\n    primary2 (apply instance)\r\n\r\nDatabase Status:\r\nSUCCESS\r\n<\/pre>\n
For double control, a table is created on the Primary side and it is seen whether it goes to the Standby sides.<\/p>\n
[Primary-2] SQL> select table_name from dba_tables where owner='TEST';\r\n\r\nTABLE_NAME\r\n------------------------------\r\nEMPLOYEES_YEDEK\r\nLOCATIONS_YEDEK\r\nREGIONS_YEDEK\r\n<\/pre>\n
[Physical-2] SQL> select table_name from dba_tables where owner='TEST';\r\n\r\nTABLE_NAME\r\n------------------------------\r\nEMPLOYEES_YEDEK\r\nLOCATIONS_YEDEK\r\nREGIONS_YEDEK\r\n<\/pre>\n
[Logical-2] SQL> select table_name from dba_tables where owner='TEST';\r\n\r\nTABLE_NAME\r\n------------------------------\r\nREGIONS_YEDEK\r\nEMPLOYEES_YEDEK\r\nLOCATIONS_YEDEK\r\n<\/pre>\n
[Primary-2] SQL> create table test.departments_yedek as select * from hr.departments;\r\n\r\nTable created.\r\n\r\n[Primary-2] SQL> select table_name from dba_tables where owner='TEST';\r\n\r\nTABLE_NAME\r\n------------------------------\r\nEMPLOYEES_YEDEK\r\nLOCATIONS_YEDEK\r\nREGIONS_YEDEK\r\nDEPARTMENTS_YEDEK\r\n<\/pre>\n
[Physical-2] SQL> select table_name from dba_tables where owner='TEST';\r\n\r\nTABLE_NAME\r\n------------------------------\r\nEMPLOYEES_YEDEK\r\nLOCATIONS_YEDEK\r\nREGIONS_YEDEK\r\nDEPARTMENTS_YEDEK\r\n<\/pre>\n
[Logical-2] SQL> select table_name from dba_tables where owner='TEST';\r\n\r\nTABLE_NAME\r\n------------------------------\r\nREGIONS_YEDEK\r\nEMPLOYEES_YEDEK\r\nLOCATIONS_YEDEK\r\nDEPARTMENTS_YEDEK\r\n<\/pre>\n
On the logic side, we stop the Redo-Apply service.<\/p>\n
DGMGRL> edit database logical set state='APPLY-OFF';\r\nSucceeded.\r\n<\/pre>\n[Logical-1]—>ALERT LOG<\/p>\n
01\/16\/2017 12:16:53\r\nEDIT DATABASE logical SET STATE = APPLY-OFF\r\n01\/16\/2017 12:16:55\r\nCommand EDIT DATABASE logical SET STATE = APPLY-OFF completed\r\n<\/pre>\n
We are performing the Log Switch process so that archive logs can be created.<\/p>\n
[Primary-2] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n\r\n[Primary-2] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n\r\n[Primary-2] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n\r\n[Primary-2] SQL> alter system switch logfile;\r\n\r\nSystem altered.\r\n<\/pre>\n
We are querying the Redo Apply status of the Logical Database.<\/p>\n
DGMGRL> show database logical\r\n\r\nDatabase - logical\r\n\r\n  Role:            LOGICAL STANDBY\r\n  Intended State:  APPLY-OFF\r\n  Transport Lag:   0 seconds (computed 1 second ago)\r\n  Apply Lag:       39 seconds (computed 1 second ago)\r\n  Apply Rate:      (unknown)\r\n  Instance(s):\r\n    primary1\r\n    primary2 (apply instance)\r\n\r\nDatabase Status:\r\nSUCCESS\r\n<\/pre>\n
We learn which archives are not applied.<\/p>\n
DGMGRL> show database logical 'RecvQEntries';\r\nSTANDBY_RECEIVE_QUEUE\r\n              STATUS     RESETLOGS_ID           THREAD              LOG_SEQ       TIME_GENERATED       TIME_COMPLETED    FIRST_CHANGE#     NEXT_CHANGE#       SIZE (KBs) \r\n   PARTIALLY_APPLIED        932222810                1                  575  01\/16\/2017 12:08:19  01\/16\/2017 12:19:01          6089898          6091869              420 \r\n   PARTIALLY_APPLIED        932222810                2                  336  01\/16\/2017 12:08:22  01\/16\/2017 12:18:55          6089892          6091799              900 \r\n         NOT_APPLIED        932222810                2                  337  01\/16\/2017 12:18:55  01\/16\/2017 12:19:02          6091799          6091851               32 \r\n         NOT_APPLIED        932222810                2                  338  01\/16\/2017 12:19:02  01\/16\/2017 12:19:05          6091851          6091863                3 \r\n         NOT_APPLIED        932222810                2                  339  01\/16\/2017 12:19:05  01\/16\/2017 12:19:09          6091863          6091873                3 \r\n<\/pre>\n
The SQLPLUS command of the above DGMGRL query is below.<\/p>\n
[Logical-2] SQL> SELECT max(sequence#),thread#,applied FROM dba_logstdby_log group by thread#, applied;\r\n\r\nMAX(SEQUENCE#)    THREAD# APPLIED\r\n-------------- ---------- --------\r\n           575          1 CURRENT\r\n           574          1 YES\r\n           339          2 NO\r\n           335          2 YES\r\n           336          2 CURRENT\r\n<\/pre>\n
7. We learn the Transaction that causes Log Apply services to stop in Logical Standby Database as follows.<\/p>\n
\tDGMGRL> show database logical 'LsbyFailedTxnInfo';\r\n\t  LsbyFailedTxnInfo = ''\r\n<\/pre>\n
8. In the Logical Standby Database, the processes used by Log Apply services and the MAX_SGA information are learned as follows.<\/p>\n
\tDGMGRL> show database logical 'LsbyParameters';\r\n\t  LsbyParameters = 'MAX_SGA=30###MAX_SERVERS=14###MAX_EVENTS_RECORDED=10000###PRESERVE_COMMIT_ORDER=TRUE###RECORD_SKIP_ERRORS=Y###RECORD_SKIP_DDL=Y###RECORD_APPLIED_DDL=N'\r\n\t\r\n\t\r\n<\/pre>\n
9. We see TopWaitEvents as follows.<\/p>\n
\tDGMGRL> show instance primary1 'TopWaitEvents' on database primary;\r\n\tTOP SYSTEM WAIT EVENTS\r\n\t               Event                                          Wait Time \r\n\t   rdbms ipc message                             1503759311 \r\n\t    class slave wait                                   297257530 \r\n\tSQL*Net message from client            148557969 \r\n\t  gcs remote message                           84543254 \r\n\t      DIAG idle wait                                  84519976 \r\n<\/pre>\n
\tDGMGRL> show instance primary1 'TopWaitEvents' on database standby;\r\n\tTOP SYSTEM WAIT EVENTS\r\n\t               Event            Wait Time \r\n\t   rdbms ipc message            810213291 \r\n\t    class slave wait            311501944 \r\n\tparallel recovery slave next change            104565552 \r\n\t  gcs remote message             52278608 \r\n\t      DIAG idle wait             52247124 \r\n<\/pre>\n
\tDGMGRL> show instance primary1 'TopWaitEvents' on database logical;\r\n\tTOP SYSTEM WAIT EVENTS\r\n\t               Event            Wait Time \r\n\t   rdbms ipc message           1409929720 \r\n\t    class slave wait            135264994 \r\n\tSQL*Net message from client            132785675 \r\n\twait for unread message on broadcast channel             88204824 \r\n\t  gcs remote message             88160985 \r\n<\/pre>\n
This information is fetched from V$SYSTEM_EVENT View.<\/p>\n
10. With the example below, we can see the situations where the broker configuration file and the SPFILE parameter file are inconsistent with each other.<\/p>\n
We are querying the Broker Configuration.<\/p>\n
\tDGMGRL> show configuration\r\n\t\r\n\tConfiguration - Broker_Configuraiton\r\n\t\r\n\t  Protection Mode: MaxPerformance\r\n\t  Databases:\r\n\t    primary - Primary database\r\n\t      Warning: ORA-16809: multiple warnings detected for the database\r\n\t\r\n\t    standby - Physical standby database\r\n\t    logical - Logical standby database\r\n\t\r\n\tFast-Start Failover: DISABLED\r\n\t\r\n\tConfiguration Status:\r\n\tWARNING\r\n\t\r\n<\/pre>\n
We question what is causing the error.<\/p>\n
\t\r\n\tDGMGRL> show database primary 'StatusReport';\r\n\tSTATUS REPORT\r\n\t       INSTANCE_NAME   SEVERITY ERROR_TEXT\r\n\t            primary1    WARNING ORA-16714: the value of property LogArchiveTrace is inconsistent with the database setting\r\n\t            primary2    WARNING ORA-16714: the value of property LogArchiveTrace is inconsistent with the database setting\r\n<\/pre>\n
We compare the values of the LogArchiveTrace parameter with the Broker configuration file in the Database.<\/p>\n
\tDGMGRL> show database primary 'InconsistentProperties';\r\n\tINCONSISTENT PROPERTIES\r\n\t   INSTANCE_NAME        PROPERTY_NAME         MEMORY_VALUE         SPFILE_VALUE         BROKER_VALUE \r\n\t        primary1      LogArchiveTrace                    6                    0                    0 \r\n\t        primary2      LogArchiveTrace                    6                    0                    0\r\n<\/pre>\n
We also check if this is the case by checking the values of the parameters.<\/p>\n
\t\r\n\tDGMGRL> show instance primary1 'LogArchiveTrace' on database primary;\r\n\t  LogArchiveTrace = '0'\r\n\t  \r\n\t**********\r\n\t[Primary-1] SQL> show parameter log_archive_trace\r\n\t\r\n\tNAME                                 TYPE        VALUE\r\n\t------------------------------------ ----------- ------------------------------\r\n\tlog_archive_trace                    integer     6\r\n<\/pre>\n
We reset the parameter value in the Database.<\/p>\n
\t[Primary-1] SQL> alter system set log_archive_trace=0 scope=both sid='*';\r\n\t\r\n\tSystem altered.\r\n\t\r\n<\/pre>\n
We check if the configuration is healthy.<\/p>\n
\t\r\n\t[Primary-1] SQL> show parameter log_archive_trace\r\n\t\r\n\tNAME                                 TYPE        VALUE\r\n\t------------------------------------ ----------- ------------------------------\r\n\tlog_archive_trace                    integer     0\r\n\t\r\n\tDGMGRL> show configuration\r\n\t\r\n\tConfiguration - Broker_Configuraiton\r\n\t\r\n\t  Protection Mode: MaxPerformance\r\n\t  Databases:\r\n\t    primary - Primary database\r\n\t    standby - Physical standby database\r\n\t    logical - Logical standby database\r\n\t\r\n\tFast-Start Failover: DISABLED\r\n\t\r\n\tConfiguration Status:\r\n\tSUCCESS\r\n\t\r\n\tDGMGRL> show database primary 'StatusReport';\r\n\tSTATUS REPORT\r\n\t       INSTANCE_NAME   SEVERITY ERROR_TEXT\r\n\t\r\n<\/pre>\n
 <\/p>\n
<\/div>\n
<\/path><\/svg><\/i> \"Loading\"<\/p>\n
<\/div>\n","protected":false},"excerpt":{"rendered":"
In today’s article, I will tell you about Data Guard Broker – Monitoring The Environment. After installing the Data Guard Environment and enabling the Broker Configuration, we need to check the operability of the system. Below are the DGMGRL commands to make these checks. [Commands run from DGMGRL are all run from Primary-1 by connecting …<\/p>\n
<\/div>\n
<\/path><\/svg><\/i> \"Loading\"<\/p>\n
<\/div>\n","protected":false},"author":484,"featured_media":49005,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[4],"tags":[],"class_list":["post-48988","post","type-post","status-publish","format-standard","has-post-thumbnail","","category-oracle"],"aioseo_notices":[],"a3_pvc":{"activated":true,"total_views":139,"today_views":0},"yoast_head":"\nMonitoring The Environment - Database Tutorials<\/title>\n<meta name=\"description\" content=\"In today's article, I will tell you about Data Guard Broker - Monitoring The Environment. After installing the Data Guard Environment and\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Monitoring The Environment - Database Tutorials\" \/>\n<meta property=\"og:description\" content=\"In today's article, I will tell you about Data Guard Broker - Monitoring The Environment. After installing the Data Guard Environment and\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/\" \/>\n<meta property=\"og:site_name\" content=\"Database Tutorials\" \/>\n<meta property=\"article:published_time\" content=\"2022-06-03T15:15:10+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-06-03T15:19:27+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/06\/Ekran-goruntusu-2022-06-03-181324.png\" \/>\n\t<meta property=\"og:image:width\" content=\"777\" \/>\n\t<meta property=\"og:image:height\" content=\"352\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Onur ARDAHANLI\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Onur ARDAHANLI\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/\"},\"author\":{\"name\":\"Onur ARDAHANLI\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6\"},\"headline\":\"Monitoring The Environment\",\"datePublished\":\"2022-06-03T15:15:10+00:00\",\"dateModified\":\"2022-06-03T15:19:27+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/\"},\"wordCount\":718,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/06\/Ekran-goruntusu-2022-06-03-181324.png\",\"articleSection\":[\"ORACLE\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/\",\"url\":\"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/\",\"name\":\"Monitoring The Environment - Database Tutorials\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/06\/Ekran-goruntusu-2022-06-03-181324.png\",\"datePublished\":\"2022-06-03T15:15:10+00:00\",\"dateModified\":\"2022-06-03T15:19:27+00:00\",\"description\":\"In today's article, I will tell you about Data Guard Broker - Monitoring The Environment. After installing the Data Guard Environment and\",\"breadcrumb\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#primaryimage\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/06\/Ekran-goruntusu-2022-06-03-181324.png\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/06\/Ekran-goruntusu-2022-06-03-181324.png\",\"width\":777,\"height\":352},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/dbtut.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Monitoring The Environment\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/dbtut.com\/#website\",\"url\":\"https:\/\/dbtut.com\/\",\"name\":\"Database Tutorials\",\"description\":\"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux\",\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/dbtut.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/dbtut.com\/#organization\",\"name\":\"dbtut\",\"url\":\"https:\/\/dbtut.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"width\":223,\"height\":36,\"caption\":\"dbtut\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6\",\"name\":\"Onur ARDAHANLI\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g\",\"caption\":\"Onur ARDAHANLI\"},\"url\":\"https:\/\/dbtut.com\/index.php\/author\/onurardahanli\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Monitoring The Environment - Database Tutorials","description":"In today's article, I will tell you about Data Guard Broker - Monitoring The Environment. After installing the Data Guard Environment and","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/","og_locale":"en_US","og_type":"article","og_title":"Monitoring The Environment - Database Tutorials","og_description":"In today's article, I will tell you about Data Guard Broker - Monitoring The Environment. After installing the Data Guard Environment and","og_url":"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/","og_site_name":"Database Tutorials","article_published_time":"2022-06-03T15:15:10+00:00","article_modified_time":"2022-06-03T15:19:27+00:00","og_image":[{"width":777,"height":352,"url":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/06\/Ekran-goruntusu-2022-06-03-181324.png","type":"image\/png"}],"author":"Onur ARDAHANLI","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Onur ARDAHANLI","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#article","isPartOf":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/"},"author":{"name":"Onur ARDAHANLI","@id":"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6"},"headline":"Monitoring The Environment","datePublished":"2022-06-03T15:15:10+00:00","dateModified":"2022-06-03T15:19:27+00:00","mainEntityOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/"},"wordCount":718,"commentCount":0,"publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/06\/Ekran-goruntusu-2022-06-03-181324.png","articleSection":["ORACLE"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/","url":"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/","name":"Monitoring The Environment - Database Tutorials","isPartOf":{"@id":"https:\/\/dbtut.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#primaryimage"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/06\/Ekran-goruntusu-2022-06-03-181324.png","datePublished":"2022-06-03T15:15:10+00:00","dateModified":"2022-06-03T15:19:27+00:00","description":"In today's article, I will tell you about Data Guard Broker - Monitoring The Environment. After installing the Data Guard Environment and","breadcrumb":{"@id":"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#primaryimage","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/06\/Ekran-goruntusu-2022-06-03-181324.png","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2022\/06\/Ekran-goruntusu-2022-06-03-181324.png","width":777,"height":352},{"@type":"BreadcrumbList","@id":"https:\/\/dbtut.com\/index.php\/2022\/06\/03\/monitoring-the-environment\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/dbtut.com\/"},{"@type":"ListItem","position":2,"name":"Monitoring The Environment"}]},{"@type":"WebSite","@id":"https:\/\/dbtut.com\/#website","url":"https:\/\/dbtut.com\/","name":"Database Tutorials","description":"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux","publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/dbtut.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/dbtut.com\/#organization","name":"dbtut","url":"https:\/\/dbtut.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","width":223,"height":36,"caption":"dbtut"},"image":{"@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6","name":"Onur ARDAHANLI","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ecd20c3e1374ced4e1aefc82101cce4cd437be8fd957d1be3d106668b8a1b990?s=96&d=mm&r=g","caption":"Onur ARDAHANLI"},"url":"https:\/\/dbtut.com\/index.php\/author\/onurardahanli\/"}]}},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/48988","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/users\/484"}],"replies":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/comments?post=48988"}],"version-history":[{"count":0,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/48988\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media\/49005"}],"wp:attachment":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media?parent=48988"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/categories?post=48988"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/tags?post=48988"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}