{"id":18449,"date":"2021-01-26T09:03:49","date_gmt":"2021-01-26T09:03:49","guid":{"rendered":"https:\/\/dbtut.com\/?p=18449"},"modified":"2021-01-26T09:07:33","modified_gmt":"2021-01-26T09:07:33","slug":"how-to-create-data-guard-broker-configuration","status":"publish","type":"post","link":"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/","title":{"rendered":"How To Create Data Guard Broker Configuration"},"content":{"rendered":"

In this article, we will create data guard broker configuration. You can see the overview of data guard broker in the article named “What is Oracle Data Guard Broker<\/a>“.<\/p>\n

Our current data guard environment is as follows;<\/p>\n[Primary Side]\n

[oracle@primary1 ~]$ srvctl config database -d primary\r\nDatabase unique name: primary\r\nDatabase name: primary\r\nOracle home: \/u01\/app\/oracle\/product\/11.2.0\/db_1\r\nOracle user: oracle\r\nSpfile: +DATA\/primary\/spfileprimary.ora\r\nDomain: \r\nStart options: open\r\nStop options: immediate\r\nDatabase role: PRIMARY\r\nManagement policy: AUTOMATIC\r\nServer pools: primary\r\nDatabase instances: primary1,primary2\r\nDisk Groups: DATA\r\nMount point paths: \r\nServices: \r\nType: RAC\r\nDatabase is administrator managed<\/pre>\n
[Primary-1] SQL> set linesize 500\r\n[Primary-1] SQL> select d.open_mode, d.database_role, a.database_mode, a.recovery_mode, a.protection_mode from v$archive_dest_status a, v$database d where a.database_mode <> 'UNKNOWN';\r\n\r\nOPEN_MODE          DATABASE_ROLE    DATABASE_MODE             RECOVERY_MODE                        PROTECTION_MODE\r\n-------------------- ---------------- --------------- ----------------------- --------------------------------------       ------------------------------------------\r\nREAD WRITE           PRIMARY                   OPEN                                   IDLE                                                  MAXIMUM PERFORMANCE\r\nREAD WRITE           PRIMARY                   MOUNTED-STANDBY        MANAGED REAL TIME APPLY      MAXIMUM PERFORMANCE\r\nREAD WRITE           PRIMARY                   OPEN                                   LOGICAL REAL TIME APPLY          MAXIMUM PERFORMANCE\r\n<\/pre>\n[Physical Standby Side]\n
[oracle@standby1 ~]$ srvctl config database -d standby\r\nDatabase unique name: standby\r\nDatabase name: primary\r\nOracle home: \/u01\/app\/oracle\/product\/11.2.0\/db_1\r\nOracle user: oracle\r\nSpfile: +DATA\/STANDBY\/PARAMETERFILE\/spfilestandby.ora\r\nDomain: \r\nStart options: mount\r\nStop options: immediate\r\nDatabase role: PHYSICAL_STANDBY\r\nManagement policy: AUTOMATIC\r\nServer pools: standby\r\nDatabase instances: primary1,primary2\r\nDisk Groups: DATA,FRA\r\nMount point paths: \r\nServices: \r\nType: RAC\r\nDatabase is administrator managed<\/pre>\n
[Physical-1] SQL> set linesize 500\r\n[Physical-1] SQL> select d.open_mode, d.database_role, a.database_mode, a.recovery_mode, a.protection_mode from v$archive_dest_status a, v$database d where a.database_mode <> 'UNKNOWN';\r\n\r\nOPEN_MODE                        DATABASE_ROLE       DATABASE_MODE        RECOVERY_MODE                       PROTECTION_MODE\r\n-------------------- ---------------- --------------- ----------------------- --------------------\r\nREAD ONLY WITH APPLY    PHYSICAL STANDBY   OPEN_READ-ONLY        MANAGED REAL TIME APPLY   MAXIMUM PERFORMANCE\r\n<\/pre>\n[Logical Standby Side]\n
[oracle@logical1 ~]$ srvctl config database -d logical\r\nDatabase unique name: logical\r\nDatabase name: primary\r\nOracle home: \/u01\/app\/oracle\/product\/11.2.0\/db_1\r\nOracle user: oracle\r\nSpfile: +DATA\/LOGICAL\/PARAMETERFILE\/spfilelogical.ora\r\nDomain: \r\nStart options: open\r\nStop options: immediate\r\nDatabase role: PHYSICAL_STANDBY\r\nManagement policy: AUTOMATIC\r\nServer pools: logical\r\nDatabase instances: primary1,primary2\r\nDisk Groups: DATA,FRA\r\nMount point paths: \r\nServices: \r\nType: RAC\r\nDatabase is administrator managed<\/pre>\n
[Logical-1] SQL> set linesize 500\r\n[Logical-1] SQL> select d.open_mode, d.database_role, a.database_mode, a.recovery_mode, a.protection_mode from v$archive_dest_status a, v$database d where a.database_mode <> 'UNKNOWN';\r\n\r\nOPEN_MODE          DATABASE_ROLE    DATABASE_MODE     RECOVERY_MODE                   PROTECTION_MODE\r\n-------------------- ---------------- --------------- ----------------------- ---------------------------------------------------------------------------\r\nREAD WRITE           LOGICAL STANDBY  OPEN                            LOGICAL REAL TIME APPLY   MAXIMUM PERFORMANCE<\/pre>\n
Create Data Guard Broker Configuration<\/p>\n
Step1:<\/h3>\n
Stop Redo Apply Services on Standby Database
\n[Physical-1]\n
SQL> alter database recover managed standby database cancel;\r\n\r\nDatabase altered.\r\n<\/pre>\n[Standby-1]\n
Fri Jan 13 10:00:28 2017\r\nalter database recover managed standby database cancel\r\nFri Jan 13 10:00:28 2017\r\nMRP0: Background Media Recovery cancelled with status 16037\r\nErrors in file \/u01\/app\/oracle\/diag\/rdbms\/standby\/primary1\/trace\/primary1_pr00_14588.trc:\r\nORA-16037: user requested cancel of managed recovery operation\r\nFri Jan 13 10:00:28 2017\r\nManaged Standby Recovery not using Real Time Apply\r\nRecovery interrupted!\r\nRecovered data files to a consistent state at change 4416720\r\nFri Jan 13 10:00:29 2017\r\nReconfiguration started (old inc 9, new inc 11)\r\nList of instances:\r\n 1 2 (myinst: 1) \r\n Global Resource Directory frozen\r\n Communication channels reestablished\r\n Master broadcasted resource hash value bitmaps\r\n Non-local Process blocks cleaned out\r\nFri Jan 13 10:00:29 2017\r\n LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived\r\nFri Jan 13 10:00:29 2017\r\n LMS 1: 0 GCS shadows cancelled, 0 closed, 0 Xw survived\r\n Set master node info \r\n Submitted all remote-enqueue requests\r\n Dwn-cvts replayed, VALBLKs dubious\r\n All grantable enqueues granted\r\n Submitted all GCS remote-cache requests\r\n Fix write in gcs resources\r\nReconfiguration complete\r\nFri Jan 13 10:00:29 2017\r\nBlock change tracking service stopping.\r\nStopping background process CTWR\r\nFri Jan 13 10:00:30 2017\r\nMRP0: Background Media Recovery process shutdown (primary1)\r\nManaged Standby Recovery Canceled (primary1)\r\nCompleted: alter database recover managed standby database cancel\r\n<\/pre>\n[Standby-2]\n
Fri Jan 13 10:00:23 2017\r\nManaged Standby Recovery not using Real Time Apply\r\nFri Jan 13 10:00:24 2017\r\nReconfiguration started (old inc 9, new inc 11)\r\nList of instances:\r\n 1 2 (myinst: 2) \r\n Global Resource Directory frozen\r\n Communication channels reestablished\r\nFri Jan 13 10:00:24 2017\r\n * domain 0 valid = 1 according to instance 1 \r\n Master broadcasted resource hash value bitmaps\r\n Non-local Process blocks cleaned out\r\nFri Jan 13 10:00:24 2017\r\n LMS 1: 0 GCS shadows cancelled, 0 closed, 0 Xw survived\r\nFri Jan 13 10:00:24 2017\r\n LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived\r\n Set master node info \r\n Submitted all remote-enqueue requests\r\n Dwn-cvts replayed, VALBLKs dubious\r\n All grantable enqueues granted\r\n Submitted all GCS remote-cache requests\r\n Fix write in gcs resources\r\nReconfiguration complete\r\n<\/pre>\n[Physical-2]\n
SQL> alter database recover managed standby database cancel;\r\nalter database recover managed standby database cancel\r\n*\r\nERROR at line 1:\r\nORA-16136: Managed Standby Recovery not active\r\n<\/pre>\n
The reason of ORA-16136: Managed Standby Recovery not active is that log apply services are running on one instance.
\n[Logical-1]\n
 SQL> alter database stop logical standby apply;\r\nalter database stop logical standby apply\r\n*\r\nERROR at line 1:\r\nORA-16283: operation not permitted on non-apply instance\r\n<\/pre>\n
The reason of ORA-16283: operation not permitted on non-apply instance is that log apply services are running on one instance. If it is not running on Logical-1, it must be running on the other node.
\n[Logical-2]\n
SQL> alter database stop logical standby apply;\r\n\r\nDatabase altered.<\/pre>\n[Logical-2] –>ALERT LOG<\/p>\n
Fri Jan 13 09:55:51 2017\r\nalter database stop logical standby apply\r\nFri Jan 13 09:55:52 2017\r\nLOGSTDBY Analyzer process AS00 server id=0 pid=58 OS id=19087 stopped\r\nFri Jan 13 09:55:52 2017\r\nLOGSTDBY Apply process AS05 server id=5 pid=63 OS id=19111 stopped\r\nFri Jan 13 09:55:52 2017\r\nLOGSTDBY Apply process AS02 server id=2 pid=60 OS id=19095 stopped\r\nFri Jan 13 09:55:52 2017\r\nLOGSTDBY Apply process AS03 server id=3 pid=61 OS id=19103 stopped\r\nFri Jan 13 09:55:52 2017\r\nLOGSTDBY Apply process AS04 server id=4 pid=62 OS id=19107 stopped\r\nFri Jan 13 09:55:52 2017\r\nLOGSTDBY Apply process AS01 server id=1 pid=59 OS id=19091 stopped\r\nFri Jan 13 09:55:52 2017\r\nLOGMINER: session#=1 (Logical_Standby$), preparer MS02 pid=57 OS id=19083 sid=79 stopped\r\nFri Jan 13 09:55:52 2017\r\nLOGMINER: session#=1 (Logical_Standby$), builder MS01 pid=56 OS id=19079 sid=17 stopped\r\nFri Jan 13 09:55:52 2017\r\nLOGMINER: session#=1 (Logical_Standby$), reader MS00 pid=55 OS id=19075 sid=200 stopped\r\nFri Jan 13 09:55:52 2017\r\nLOGSTDBY status: ORA-16128: User initiated stop apply successfully completed\r\nCompleted: alter database stop logical standby apply<\/pre>\n
Step2:<\/h3>\n
Since I use RAC structure, I move Broker Configuration files to Shared area (ASM) where all instances can be read.
\nI want to create one to DATA and the other to FRA in terms of being a backup. That’s why I’m creating a directory in DATA and FRA.<\/p>\n
[grid@primary2 ~]$ asmcmd\r\nASMCMD> ls\r\nDATA\/\r\nFRA\/\r\nOCR_VOTE\/\r\nASMCMD> cd data\r\nASMCMD> ls\r\nPRIMARY\/\r\nASMCMD> cd PRIMARY\r\nASMCMD> ls\r\nCHANGETRACKING\/\r\nCONTROLFILE\/\r\nDATAFILE\/\r\nONLINELOG\/\r\nPARAMETERFILE\/\r\nTEMPFILE\/\r\nspfileprimary.ora\r\nASMCMD> mkdir BROKER_CONF_FILE\r\nASMCMD> ls\r\nBROKER_CONF_FILE\/\r\nCHANGETRACKING\/\r\nCONTROLFILE\/\r\nDATAFILE\/\r\nONLINELOG\/\r\nPARAMETERFILE\/\r\nTEMPFILE\/\r\nspfileprimary.ora\r\nASMCMD> cd BROKER_CONF_FILE\r\nASMCMD> ls\r\nASMCMD> pwd\r\n+data\/PRIMARY\/BROKER_CONF_FILE\r\nASMCMD> cd +FRA\r\nASMCMD> ls\r\nPRIMARY\/\r\nASMCMD> cd PRIMARY\r\nASMCMD> ls\r\nARCHIVELOG\/\r\nONLINELOG\/\r\nASMCMD> mkdir BROKER_CONF_FILE\r\nASMCMD> ls\r\nARCHIVELOG\/\r\nBROKER_CONF_FILE\/\r\nONLINELOG\/\r\nASMCMD> cd BROKER_CONF_FILE\r\nASMCMD> pwd\r\n+FRA\/PRIMARY\/BROKER_CONF_FILE\r\n<\/pre>\n
Set parameters to new locations.<\/p>\n
[Primary-1] SQL> alter system set dg_broker_config_file1='+data\/PRIMARY\/BROKER_CONF_FILE\/dr1primary.dat' scope=both sid='*';\r\n\r\nSystem altered.\r\n\r\n[Primary-1] SQL> alter system set dg_broker_config_file2='+FRA\/PRIMARY\/BROKER_CONF_FILE\/dr2primary.dat' scope=both sid='*';\r\n\r\nSystem altered.\r\n<\/pre>\n
Start the DMON process and check the locations of the configuration files.<\/p>\n
[Primary-1] SQL> alter system set dg_broker_start=TRUE scope=both sid='*';\r\n\r\nSystem altered.<\/pre>\n
[oracle@primary1 ~]$ ps -ef | grep dmon\r\noracle    3623     1  0 10:07 ?        00:00:00 ora_dmon_primary1\r\n<\/pre>\n
[Primary-1] SQL> show parameter dg_broker_config_file\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\ndg_broker_config_file1               string      +data\/PRIMARY\/BROKER_CONF_FILE\/dr1primary.dat\r\ndg_broker_config_file2               string      +FRA\/PRIMARY\/BROKER_CONF_FILE\/dr2primary.dat\r\n<\/pre>\n
Apply these processes in the same way in Physical and Logical Standbys.<\/p>\n
Step3:<\/h3>\n
Clear LOG_ARCHIVE_DEST_n parameters with SERVICE attribute in all instances.<\/p>\n
[Primary-1] SQL> column name format a30 \r\n[Primary-1] SQL> column value format a94\r\n[Primary-1] SQL> set linesize 9000\r\n[Primary-1] SQL> select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\n\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=primary\r\nlog_archive_dest_2             SERVICE=standby SYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=standby\r\nlog_archive_dest_3             SERVICE=logical SYNC REOPEN=15 valid_for=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=logical\r\n\r\n[Primary-1] SQL> alter system set log_archive_dest_2='' scope=both sid='*';\r\n\r\nSystem altered.\r\n\r\n[Primary-1] SQL> alter system set log_archive_dest_3='' scope=both sid='*';\r\n\r\nSystem altered.\r\n<\/pre>\n
I am running it in a single instance in RAC structure. With the sid = ‘*’ command, I make the parameter change in all instances.<\/p>\n
[Physical-1] SQL> column name format a30\r\n[Physical-1] SQL> column value format a94\r\n[Physical-1] SQL> select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\n\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=standby\r\nlog_archive_dest_2             SERVICE=primary SYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=primary\r\n\r\n[Physical-1] SQL> alter system set log_archive_dest_2='' scope=both sid='*';\r\n\r\nSystem altered.\r\n<\/pre>\n
[Logical-1] SQL> column name format a30\r\n[Logical-1] SQL> column value format a94\r\n[Logical-1] SQL> select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\n\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=logical\r\n\r\n\r\n[Logical-1] SQL> alter system set dg_broker_start=TRUE scope=both sid='*';\r\n\r\nSystem altered.\r\n<\/pre>\n
Connect to DGMGRL from Primary Database and login with SYS user.<\/p>\n
[oracle@primary1 ~]$ dgmgrl\r\nDGMGRL for Linux: Version 11.2.0.4.0 - 64bit Production\r\n\r\nCopyright (c) 2000, 2009, Oracle. All rights reserved.\r\n\r\nWelcome to DGMGRL, type \"help\" for information.\r\nDGMGRL> connect sys\/Passw0rd4\r\nConnected.\r\n<\/pre>\n
If we were using 12c, we would be logging in with the “sysdg” user. But there is no such user in 11g.
\nFor this reason, we will do our transactions with the SYS user. We only have a SYS user in Password File.<\/p>\n
[Primary-1] SQL> select * from v$pwfile_users;\r\n\r\nUSERNAME                       SYSDB SYSOP SYSAS\r\n------------------------------ ----- ----- -----\r\nSYS                            TRUE  TRUE  FALSE\r\n<\/pre>\n
In 12c, in addition to SYS, there are users such as SYSDG, SYSBACKUP for security reasons.<\/p>\n
\"\"<\/p>\n
Step5:<\/h3>\n
Create Broker Configuration<\/p>\n
DGMGRL> show configuration\r\nORA-16532: Data Guard broker configuration does not exist\r\n\r\nConfiguration details cannot be determined by DGMGRL\r\nDGMGRL> create configuration 'Broker_Configuration' as primary database is 'primary' connect identifier is primary;\r\nConfiguration \"DG_Configuration\" created with primary database \"primary\"\r\nDGMGRL> 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\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nDISABLED\r\n<\/pre>\n
Step6:<\/h3>\n
Add Physical Standby Database to the configuration.<\/p>\n
DGMGRL> add database 'standby' as connect identifier is standby;\r\nDatabase \"standby\" added\r\nDGMGRL> 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\r\nFast-Start Failover: DISABLED\r\n\r\nConfiguration Status:\r\nDISABLED\r\n<\/pre>\n
Step7:<\/h3>\n
Add Logical Standby Database to the configuration.<\/p>\n
DGMGRL> add database 'logical' as connect identifier is logical;\r\nDatabase \"logical\" added\r\nDGMGRL> 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\nDISABLED\r\n<\/pre>\n
Step8:<\/h3>\n
Make instance and database level checks before the broker configuration is enabled.<\/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\nDISABLED\r\n<\/pre>\n
DGMGRL> show database verbose primary<\/pre>\n
“Database:primary” => Indicates DB_UNIQUE_NAME.
\n“Role:PRIMARY” =>Indicates DB Role.
\n“Intended State:OFFLINE” => Indicates the status of Redo Transport services. OFFLINE indicates that there is no transport operation at the moment. The reason is that LOG_ARCHIVE_DEST_n parameters are deleted before Broker Configuration.
\nInstance(s):
\nprimary1
\nprimary2<\/p>\n
Properties:
\n“DGConnectIdentifier = ‘primary'” => It searches for this name in the tnsnames.ORA file and tries to connect with that information.
\nObserverConnectIdentifier = ”
\nLogXptMode = ‘ASYNC’ => Indicates how Redo Transport mode is. It can be SYNC, ASYNC or FASTSYNC.
\nDelayMins = ‘0’
\nBinding = ‘optional’ => Indicates whether the Redo destination is MANDATORY or OPTIONAL.
\nMANDATORY: = It must be written to that location. If it cannot be written, it stops the system from working because it will not overwrite ONLINE REDO LOG files.
\nMaxFailure = ‘0’ => It specifies the maximum number of sequential archive file errors before Redo Transport Services stops trying to transmit archive redo log files to the standby database.
\nMaxConnections = ‘1’ => It indicates how many processes an ARCH process will perform its operations in parallel.
\nReopenSecs = ‘300’ => Specifies how many seconds after the ARCn process will try the next connect attempt for the destination where it fails to connect.
\nNetTimeout = ’30’ => Indicates that the LGWR process will continue its normal operation after how many seconds it does not receive feedback from Oracle Net Services.
\nRedoCompression = ‘DISABLE’ => It allows Redo to be sent by compression. Subject to an extra license. It makes tremendous compression.
\nLogShipping = ‘ON’ => It is the equivalent of the LOG_ARCHIVE_DEST_STATE_n parameter. ON = ENABLE, OFF = DEFER
\nPreferredApplyInstance = ”
\nApplyInstanceTimeout = ‘0’
\nApplyParallel = ‘AUTO’
\nLsbyASkipTxnCfgPr = ‘0,0,0’
\nLsbyDSkipTxnCfgPr = ‘0,0,0’
\nLsbyASkipCfgPr = ”
\nLsbyDSkipCfgPr = ”
\nLsbyASkipErrorCfgPr = ”
\nLsbyDSkipErrorCfgPr = ”
\nLsbyMaxEventsRecorded = ‘0’
\nLsbyPreserveCommitOrder = ”
\nLsbyRecordSkipErrors = ”
\nLsbyRecordSkipDdl = ”
\nLsbyRecordAppliedDdl = ”
\nStandbyFileManagement = ‘AUTO’
\nArchiveLagTarget = ‘0’ => It specifies how many seconds the Log Switch operation will be performed without waiting for the Online Redo Log to fill.
\nLogArchiveMaxProcesses = ‘8’
\nLogArchiveMinSucceedDest = ‘1’
\nDbFileNameConvert = ‘standby, primary’
\nLogFileNameConvert = ‘standby, primary’
\nFastStartFailoverTarget = ”
\nInconsistentProperties = ‘(monitor)’
\nInconsistentLogXptProps = ‘(monitor)’
\nSendQEntries = ‘(monitor)’
\nLogXptStatus = ‘(monitor)’
\nRecvQEntries = ‘(monitor)’
\nLsbyParameters = ‘(monitor)’
\nLsbySkipTxnTable = ‘(monitor)’
\nLsbySkipTable = ‘(monitor)’
\nLsbyFailedTxnInfo = ‘(monitor)’
\nApplyLagThreshold = ‘0’ => Allows Apply Lag to throw a warning error above the specified threshold.
\nTransportLagThreshold = ‘0’ => Allows Transport Lag to throw a warning error above the specified threshold.
\nTransportDisconnectedThreshold = ’30’ => Throws a warning error when communication is broken for the time specified by the Primary Database of Standby database or Far Sync instances.
\nSidName(*)
\nStaticConnectIdentifier(*)
\nStandbyArchiveLocation(*)
\nAlternateLocation(*) => If it fails to send archives to the location specified in StandbyArchiveLocation, alternatively the location to send archives is specified.
\nLogArchiveTrace(*)
\nLogArchiveFormat(*)
\nLsbyMaxSga(*)
\nLsbyMaxServers(*)
\nTopWaitEvents(*)
\n(*) – Please check specific instance for the property value<\/p>\n
Database Status:
\nDISABLED => Indicates that the Configuration is not enabled.<\/p>\n
DGMGRL> show instance verbose primary1 on database primary\r\n\r\nInstance 'primary1' of database 'primary'\r\n\r\n  Host Name: primary1.tivibulab.local\r\n  PFILE:     \r\n  Properties:\r\n    SidName                         = 'primary1'\r\n    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=172.20.42.23)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=primary_DGMGRL)(INSTANCE_NAME=primary1)(SERVER=DEDICATED)))'\r\n    StandbyArchiveLocation          = 'USE_DB_RECOVERY_FILE_DEST'\r\n    AlternateLocation               = ''\r\n    LogArchiveTrace                 = '0'\r\n    LogArchiveFormat                = '%t_%s_%r.arc'\r\n    LsbyMaxSga                      = '0'\r\n    LsbyMaxServers                  = '0'\r\n    TopWaitEvents                   = '(monitor)'\r\n\r\nInstance Status:\r\nDISABLED<\/pre>\n
DGMGRL> show instance verbose primary1 on database standby\r\n\r\nInstance 'primary1' of database 'standby'\r\n\r\n  Host Name: standby1.tivibulab.local\r\n  PFILE:     \r\n  Properties:\r\n    SidName                         = 'primary1'\r\n    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=172.20.42.27)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=standby_DGMGRL)(INSTANCE_NAME=primary1)(SERVER=DEDICATED)))'\r\n    StandbyArchiveLocation          = 'USE_DB_RECOVERY_FILE_DEST'\r\n    AlternateLocation               = ''\r\n    LogArchiveTrace                 = '0'\r\n    LogArchiveFormat                = '%t_%s_%r.arc'\r\n    TopWaitEvents                   = '(monitor)'\r\n\r\nInstance Status:\r\nDISABLED<\/pre>\n
DGMGRL> show instance verbose primary1 on database logical\r\n\r\nInstance 'primary1' of database 'logical'\r\n\r\n  Host Name: logical1.tivibulab.local\r\n  PFILE:     \r\n  Properties:\r\n    SidName                         = 'primary1'\r\n    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=172.20.42.43)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=logical_DGMGRL)(INSTANCE_NAME=primary1)(SERVER=DEDICATED)))'\r\n    StandbyArchiveLocation          = 'USE_DB_RECOVERY_FILE_DEST'\r\n    AlternateLocation               = ''\r\n    LogArchiveTrace                 = '0'\r\n    LogArchiveFormat                = '%t_%s_%r.arc'\r\n    LsbyMaxSga                      = '0'\r\n    LsbyMaxServers                  = '0'\r\n    TopWaitEvents                   = '(monitor)'\r\n\r\nInstance Status:\r\nDISABLED<\/pre>\n
Step9:<\/h3>\n
Enable the configuration.<\/p>\n
DGMGRL> enable configuration\r\nEnabled.<\/pre>\n[Primary-1]–> ALERT LOG<\/p>\n
********************************************************************\r\nLGWR: Resetting 'active' archival for destination LOG_ARCHIVE_DEST_3\r\n********************************************************************\r\nFri Jan 13 10:42:23 2017\r\nALTER SYSTEM SET log_archive_dest_2='service=\"standby\"','LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_connections=1 reopen=300 db_unique_name=\"standby\" net_timeout=30','valid_for=(all_logfiles,primary_role)' SCOPE=BOTH;\r\nFri Jan 13 10:42:23 2017\r\nNSA3 started with pid=67, OS id=10785 \r\nThread 1 advanced to log sequence 379 (LGWR switch)\r\n  Current log# 1 seq# 379 mem# 0: +DATA\/primary\/onlinelog\/group_1.261.932222811\r\n******************************************************************\r\nLGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2\r\n******************************************************************\r\nLNS: Standby redo logfile selected for thread 1 sequence 379 for destination LOG_ARCHIVE_DEST_2\r\nFri Jan 13 10:42:27 2017\r\nArchived Log entry 1384 added for thread 1 sequence 378 ID 0x697b7314 dest 1:\r\nFri Jan 13 10:42:53 2017\r\nThread 1 cannot allocate new log, sequence 380\r\nCheckpoint not complete\r\n  Current log# 1 seq# 379 mem# 0: +DATA\/primary\/onlinelog\/group_1.261.932222811\r\nFri Jan 13 10:42:56 2017\r\nALTER SYSTEM SET log_archive_dest_3='service=\"logical\"','LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_connections=1 reopen=300 db_unique_name=\"logical\" net_timeout=30','valid_for=(all_logfiles,primary_role)' SCOPE=BOTH;\r\nALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='primary1';\r\nALTER SYSTEM SET log_archive_format='%t_%s_%r.arc' SCOPE=SPFILE SID='primary1';\r\nALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET log_archive_max_processes=8 SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET db_file_name_convert='standby','primary' SCOPE=SPFILE;\r\nALTER SYSTEM SET log_file_name_convert='standby','primary' SCOPE=SPFILE;\r\nALTER SYSTEM ARCHIVE LOG\r\nFri Jan 13 10:42:56 2017\r\nNSA3 started with pid=35, OS id=10906 \r\nThread 1 advanced to log sequence 380 (LGWR switch)\r\n  Current log# 2 seq# 380 mem# 0: +DATA\/primary\/onlinelog\/group_2.262.932222811\r\n******************************************************************\r\nLGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_3\r\n******************************************************************\r\nFri Jan 13 10:43:00 2017\r\nLNS: Standby redo logfile selected for thread 1 sequence 380 for destination LOG_ARCHIVE_DEST_2\r\nArchived Log entry 1388 added for thread 1 sequence 379 ID 0x697b7314 dest 1:\r\nLNS: Standby redo logfile selected for thread 1 sequence 380 for destination LOG_ARCHIVE_DEST_3\r\nFri Jan 13 10:43:07 2017\r\nARC4: Standby redo logfile selected for thread 1 sequence 379 for destination LOG_ARCHIVE_DEST_3\r\n<\/pre>\n[Standby-2] —> ALERT LOG<\/p>\n
Fri Jan 13 10:42:14 2017\r\nNSV0 started with pid=54, OS id=13418 \r\nFri Jan 13 10:42:18 2017\r\nRSM0 started with pid=56, OS id=13431 \r\nALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='primary2';\r\nALTER SYSTEM SET log_archive_format='%t_%s_%r.arc' SCOPE=SPFILE SID='primary2';\r\nALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET log_archive_max_processes=8 SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET db_file_name_convert='primary','standby' SCOPE=SPFILE;\r\nALTER SYSTEM SET log_file_name_convert='primary','standby' SCOPE=SPFILE;\r\nALTER SYSTEM SET fal_server='primary' SCOPE=BOTH;\r\nALTER DATABASE RECOVER MANAGED STANDBY DATABASE  THROUGH ALL SWITCHOVER DISCONNECT  USING CURRENT LOGFILE\r\nAttempt to start background Managed Standby Recovery process (primary2)\r\nFri Jan 13 10:42:23 2017\r\nMRP0 started with pid=57, OS id=13436 \r\nMRP0: Background Managed Standby Recovery process started (primary2)\r\nFri Jan 13 10:42:23 2017\r\nArchived Log entry 605 added for thread 2 sequence 240 ID 0x697b7314 dest 1:\r\nFri Jan 13 10:42:27 2017\r\nArchived Log entry 606 added for thread 1 sequence 378 ID 0x697b7314 dest 1:\r\n started logmerger process\r\nFri Jan 13 10:42:28 2017\r\nManaged Standby Recovery starting Real Time Apply\r\nFri Jan 13 10:42:29 2017\r\nReconfiguration started (old inc 11, new inc 13)\r\nList of instances:\r\n 1 2 (myinst: 2) \r\n Global Resource Directory frozen\r\n Communication channels reestablished\r\nFri Jan 13 10:42:29 2017\r\n * domain 0 valid = 1 according to instance 1 \r\n Master broadcasted resource hash value bitmaps\r\n Non-local Process blocks cleaned out\r\nFri Jan 13 10:42:29 2017\r\n LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived\r\nFri Jan 13 10:42:29 2017\r\n LMS 1: 0 GCS shadows cancelled, 0 closed, 0 Xw survived\r\n Set master node info \r\n Submitted all remote-enqueue requests\r\n Dwn-cvts replayed, VALBLKs dubious\r\n All grantable enqueues granted\r\n Submitted all GCS remote-cache requests\r\n Fix write in gcs resources\r\nReconfiguration complete\r\nParallel Media Recovery started with 4 slaves\r\nFri Jan 13 10:42:30 2017\r\nBlock change tracking file is current.\r\nStarting background process CTWR\r\nFri Jan 13 10:42:30 2017\r\nCTWR started with pid=61, OS id=13465 \r\nBlock change tracking service is active.\r\nWaiting for all non-current ORLs to be archived...\r\nAll non-current ORLs have been archived.\r\nMedia Recovery Log +FRA\/standby\/archivelog\/2017_01_13\/thread_2_seq_240.441.933158543\r\nMedia Recovery Log +FRA\/standby\/archivelog\/2017_01_13\/thread_1_seq_378.424.933158547\r\nFri Jan 13 10:42:31 2017\r\nCompleted: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE  THROUGH ALL SWITCHOVER DISCONNECT  USING CURRENT LOGFILE\r\nMedia Recovery Waiting for thread 2 sequence 241\r\nFri Jan 13 10:42:32 2017\r\nPrimary database is in MAXIMUM PERFORMANCE mode\r\nRFS[5]: Assigned to RFS process 13499\r\nRFS[5]: Selected log 5 for thread 1 sequence 379 dbid 1769705496 branch 932222810\r\nFri Jan 13 10:42:35 2017\r\nPrimary database is in MAXIMUM PERFORMANCE mode\r\nRFS[6]: Assigned to RFS process 13506\r\nRFS[6]: Selected log 8 for thread 2 sequence 242 dbid 1769705496 branch 932222810\r\nFri Jan 13 10:42:36 2017\r\nRFS[7]: Assigned to RFS process 13510\r\nRFS[7]: Selected log 9 for thread 2 sequence 241 dbid 1769705496 branch 932222810\r\nFri Jan 13 10:42:36 2017\r\nArchived Log entry 607 added for thread 2 sequence 241 ID 0x697b7314 dest 1:\r\nMedia Recovery Log +FRA\/standby\/archivelog\/2017_01_13\/thread_2_seq_241.423.933158557\r\nMedia Recovery Waiting for thread 1 sequence 379 (in transit)\r\nRecovery of Online Redo Log: Thread 1 Group 5 Seq 379 Reading mem 0\r\n  Mem# 0: +DATA\/standby\/onlinelog\/group_5.267.932283683\r\n  Mem# 1: +FRA\/standby\/onlinelog\/group_5.260.932283683\r\nMedia Recovery Waiting for thread 2 sequence 242 (in transit)\r\nRecovery of Online Redo Log: Thread 2 Group 8 Seq 242 Reading mem 0\r\n  Mem# 0: +DATA\/standby\/onlinelog\/group_8.270.932283685\r\n  Mem# 1: +FRA\/standby\/onlinelog\/group_8.263.932283685\r\nFri Jan 13 10:43:06 2017\r\nRFS[5]: Selected log 6 for thread 1 sequence 380 dbid 1769705496 branch 932222810\r\nFri Jan 13 10:43:06 2017\r\nArchived Log entry 608 added for thread 1 sequence 379 ID 0x697b7314 dest 1:\r\nFri Jan 13 10:43:06 2017\r\nMedia Recovery Waiting for thread 1 sequence 380 (in transit)\r\nRecovery of Online Redo Log: Thread 1 Group 6 Seq 380 Reading mem 0\r\n  Mem# 0: +DATA\/standby\/onlinelog\/group_6.268.932283683\r\n  Mem# 1: +FRA\/standby\/onlinelog\/group_6.261.932283683\r\nFri Jan 13 10:43:09 2017\r\nRFS[6]: Selected log 9 for thread 2 sequence 243 dbid 1769705496 branch 932222810\r\nFri Jan 13 10:43:09 2017\r\nArchived Log entry 609 added for thread 2 sequence 242 ID 0x697b7314 dest 1:\r\nMedia Recovery Waiting for thread 2 sequence 243 (in transit)\r\nRecovery of Online Redo Log: Thread 2 Group 9 Seq 243 Reading mem 0\r\n  Mem# 0: +DATA\/standby\/onlinelog\/group_9.271.932283685\r\n  Mem# 1: +FRA\/standby\/onlinelog\/group_9.264.932283685\r\n<\/pre>\n[Logical-2]—> ALERT LOG<\/p>\n
Fri Jan 13 10:42:04 2017\r\nNSV0 started with pid=51, OS id=1107 \r\nFri Jan 13 10:42:09 2017\r\nRSM0 started with pid=55, OS id=1122 \r\nALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='primary2';\r\nALTER SYSTEM SET log_archive_format='%t_%s_%r.arc' SCOPE=SPFILE SID='primary2';\r\nLOGSTDBY: APPLY_UNSET: MAX_EVENTS_RECORDED\r\nLOGSTDBY: APPLY_UNSET: PRESERVE_COMMIT_ORDER\r\nLOGSTDBY: APPLY_UNSET: RECORD_SKIP_ERRORS\r\nLOGSTDBY: APPLY_UNSET: RECORD_SKIP_DDL\r\nLOGSTDBY: APPLY_UNSET: RECORD_APPLIED_DDL\r\nALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET log_archive_max_processes=8 SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH SID='*';\r\nALTER SYSTEM SET db_file_name_convert='logical','primary' SCOPE=SPFILE;\r\nALTER SYSTEM SET log_file_name_convert='primary','logical' SCOPE=SPFILE;\r\nALTER SYSTEM SET fal_server='primary','standby' SCOPE=BOTH;\r\nLOGSTDBY: APPLY_UNSET: MAX_EVENTS_RECORDED\r\nLOGSTDBY: APPLY_UNSET: PRESERVE_COMMIT_ORDER\r\nLOGSTDBY: APPLY_UNSET: RECORD_SKIP_ERRORS\r\nLOGSTDBY: APPLY_UNSET: RECORD_SKIP_DDL\r\nLOGSTDBY: APPLY_UNSET: RECORD_APPLIED_DDL\r\nLOGSTDBY: APPLY_UNSET: MAX_SGA\r\nLOGSTDBY: APPLY_UNSET: MAX_SERVERS\r\nALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE\r\nALTER DATABASE START LOGICAL STANDBY APPLY (primary2)\r\nwith optional part\r\nIMMEDIATE\r\nAttempt to start background Logical Standby process\r\nFri Jan 13 10:42:14 2017\r\nLSP0 started with pid=59, OS id=1136 \r\nCompleted: ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE\r\nLOGMINER: Parameters summary for session# = 1\r\nLOGMINER: Number of processes = 3, Transaction Chunk Size = 201\r\nLOGMINER: Memory Size = 30M, Checkpoint interval = 150M\r\nLOGMINER: SpillScn 4415076, ResetLogScn 925702\r\nLOGMINER: summary for session# = 1\r\nLOGMINER: StartScn: 0 (0x0000.00000000)\r\nLOGMINER: EndScn: 0 (0x0000.00000000)\r\nLOGMINER: HighConsumedScn: 4415069 (0x0000.00435e5d)\r\nLOGMINER: session_flag: 0x1\r\nLOGMINER: Read buffers: 16\r\nLOGMINER: Memory LWM: limit 10M, LWM 24M, 80%\r\nLOGMINER: Memory Release Limit: 1M\r\nFri Jan 13 10:42:15 2017\r\nLOGMINER: session#=1 (Logical_Standby$), reader MS00 pid=60 OS id=1140 sid=20 started\r\nFri Jan 13 10:42:15 2017\r\nLOGMINER: session#=1 (Logical_Standby$), builder MS01 pid=61 OS id=1144 sid=86 started\r\nFri Jan 13 10:42:15 2017\r\nLOGMINER: session#=1 (Logical_Standby$), preparer MS02 pid=62 OS id=1148 sid=143 started\r\nLOGMINER: Begin mining logfile for session 1 thread 1 sequence 378, +DATA\/logical\/onlinelog\/group_6.274.932894839\r\nFri Jan 13 10:42:15 2017\r\nLOGSTDBY Analyzer process AS00 started with server id=0 pid=63 OS id=1152\r\nFri Jan 13 10:42:15 2017\r\nLOGSTDBY Apply process AS02 started with server id=2 pid=65 OS id=1162\r\nLOGMINER: Begin mining logfile for session 1 thread 2 sequence 240, +FRA\/logical\/foreign_archivelog\/primary\/2017_01_13\/thread_2_seq_240.499.933158535\r\nFri Jan 13 10:42:15 2017\r\nLOGSTDBY Apply process AS03 started with server id=3 pid=66 OS id=1168\r\nFri Jan 13 10:42:15 2017\r\nLOGSTDBY Apply process AS01 started with server id=1 pid=64 OS id=1156\r\nFri Jan 13 10:42:15 2017\r\nLOGSTDBY Apply process AS04 started with server id=4 pid=67 OS id=1172\r\nFri Jan 13 10:42:15 2017\r\nLOGSTDBY Apply process AS05 started with server id=5 pid=68 OS id=1176\r\nLOGMINER: Alternate logfile found.  Transition to mining archived logfile for session 1 thread 1 sequence 378, +FRA\/logical\/foreign_archivelog\/primary\/2017_01_13\/thread_1_seq_378.548.933158539\r\nLOGMINER: End   mining logfile for session 1 thread 2 sequence 240, +FRA\/logical\/foreign_archivelog\/primary\/2017_01_13\/thread_2_seq_240.499.933158535\r\nFri Jan 13 10:42:56 2017\r\nPrimary database is in MAXIMUM PERFORMANCE mode\r\nRFS[1]: Assigned to RFS process 1317\r\nRFS[1]: Selected log 5 for thread 1 sequence 380 dbid 1769705496 branch 932222810\r\nFri Jan 13 10:42:59 2017\r\nPrimary database is in MAXIMUM PERFORMANCE mode\r\nRFS[2]: Assigned to RFS process 1357\r\nRFS[2]: Selected log 8 for thread 2 sequence 243 dbid 1769705496 branch 932222810\r\nFri Jan 13 10:42:59 2017\r\nRFS[3]: Assigned to RFS process 1361\r\nRFS[3]: Selected log 9 for thread 2 sequence 242 dbid 1769705496 branch 932222810\r\nFri Jan 13 10:42:59 2017\r\nRFS LogMiner: Registered logfile [+FRA\/logical\/foreign_archivelog\/primary\/2017_01_13\/thread_2_seq_242.549.933158579] to LogMiner session id [1]\r\nFri Jan 13 10:43:04 2017\r\nRFS[4]: Assigned to RFS process 1366\r\nRFS[4]: Selected log 6 for thread 1 sequence 379 dbid 1769705496 branch 932222810\r\nFri Jan 13 10:43:04 2017\r\nRFS LogMiner: Registered logfile [+FRA\/logical\/foreign_archivelog\/primary\/2017_01_13\/thread_1_seq_379.552.933158585] to LogMiner session id [1]\r\nFri Jan 13 10:43:04 2017\r\nLOGMINER: Begin mining logfile for session 1 thread 2 sequence 241, +FRA\/logical\/foreign_archivelog\/primary\/2017_01_13\/thread_2_seq_241.551.933158583\r\nLOGMINER: End   mining logfile for session 1 thread 1 sequence 378, +FRA\/logical\/foreign_archivelog\/primary\/2017_01_13\/thread_1_seq_378.548.933158539\r\nLOGMINER: Begin mining logfile for session 1 thread 1 sequence 379, +FRA\/logical\/foreign_archivelog\/primary\/2017_01_13\/thread_1_seq_379.552.933158585\r\nLOGMINER: End   mining logfile for session 1 thread 2 sequence 241, +FRA\/logical\/foreign_archivelog\/primary\/2017_01_13\/thread_2_seq_241.551.933158583\r\nLOGMINER: Begin mining logfile for session 1 thread 2 sequence 242, +FRA\/logical\/foreign_archivelog\/primary\/2017_01_13\/thread_2_seq_242.549.933158579\r\nLOGMINER: End   mining logfile for session 1 thread 1 sequence 379, +FRA\/logical\/foreign_archivelog\/primary\/2017_01_13\/thread_1_seq_379.552.933158585\r\nLOGMINER: Begin mining logfile for session 1 thread 1 sequence 380, +DATA\/logical\/onlinelog\/group_5.273.932894839\r\nLOGMINER: End   mining logfile for session 1 thread 2 sequence 242, +FRA\/logical\/foreign_archivelog\/primary\/2017_01_13\/thread_2_seq_242.549.933158579\r\nLOGMINER: Begin mining logfile for session 1 thread 2 sequence 243, +DATA\/logical\/onlinelog\/group_8.276.932894841\r\nFri Jan 13 10:45:59 2017\r\nThread 2 advanced to log sequence 48 (LGWR switch)\r\n  Current log# 4 seq# 48 mem# 0: +DATA\/logical\/onlinelog\/group_4.272.932899829\r\n  Current log# 4 seq# 48 mem# 1: +FRA\/logical\/onlinelog\/group_4.259.932899829\r\nFri Jan 13 10:46:01 2017\r\nArchived Log entry 117 added for thread 2 sequence 47 ID 0xc0660c72 dest 1:\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<\/pre>\n
From now on, we have to make all Parameter changes in the Data Guard Environment through the Broker. Otherwise the Broker may not work properly.<\/p>\n
Step10:<\/h3>\n
Check the status of LOG_ARCHIVE_DEST_n parameters after the broker is ENABLED.<\/p>\n
[Primary-1] SQL> column name format a30\r\n[Primary-1] SQL> column value format a94\r\n[Primary-1] SQL> set linesize 9000\r\n[Primary-1] SQL> select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=primary\r\nlog_archive_dest_2             service=\"standby\", LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_\r\n                               connections=1 reopen=300 db_unique_name=\"standby\" net_timeout=30, valid_for=(all_logfiles,prim\r\n                               ary_role)\r\n\r\nlog_archive_dest_3             service=\"logical\", LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_\r\n                               connections=1 reopen=300 db_unique_name=\"logical\" net_timeout=30, valid_for=(all_logfiles,primary_role)<\/pre>\n
[Physical-1] SQL> column name format a30\r\n[Physical-1] SQL> column value format a94\r\n[Physical-1] SQL> set linesize 9000\r\n[Physical-1] SQL> select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=standby<\/pre>\n
[Logical-1] SQL> column name format a30\r\n[Logical-1] SQL> column value format a94\r\n[Logical-1] SQL> set linesize 9000\r\n[Logical-1] SQL> select name, value from v$parameter where lower(name) like '%log_archive_dest%' and lower(name) not like '%log_archive_dest_state%' and value is not null;\r\nNAME                           VALUE\r\n------------------------------ ----------------------------------------------------------------------------------------------\r\nlog_archive_dest_1             LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=logical<\/pre>\n
[Primary-1] SQL> show parameter log_archive_config\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\nlog_archive_config                   string      dg_config=(primary,standby,logical)<\/pre>\n
[Physical-1] SQL> show parameter log_archive_config\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\nlog_archive_config                   string      dg_config=(standby,primary,logical)<\/pre>\n
[Logical-1] SQL> show parameter log_archive_config\r\n\r\nNAME                                 TYPE        VALUE\r\n------------------------------------ ----------- ------------------------------\r\nlog_archive_config                   string      dg_config=(logical,primary,standby)<\/pre>\n
As you can see, LOG_ARCHIVE_DEST_2 and LOG_ARCHIVE_DEST_3 parameters, which were deleted before the Broker Configuration was created, were re-set with Default values. This is to enable Redo-Transport. It also offers us great convenience so that we can see the settings after the Broker Configuration is removed.<\/p>\n
Step11:<\/h3>\n
Check everything is OK.<\/p>\n
[Primary-2] SQL> select table_name from dba_tables where owner='TEST';\r\n\r\nTABLE_NAME\r\n------------------------------\r\nJOBS_YEDEK\r\nJOB_HISTORY_YEDEK\r\nEMPLOYEES_YEDEK<\/pre>\n
[Physical-1] SQL> select table_name from dba_tables where owner='TEST';\r\n\r\nTABLE_NAME\r\n------------------------------\r\nJOBS_YEDEK\r\nJOB_HISTORY_YEDEK\r\nEMPLOYEES_YEDEK<\/pre>\n
[Logical-1] SQL> select table_name from dba_tables where owner='TEST';\r\n\r\nTABLE_NAME\r\n------------------------------\r\nEMPLOYEES_YEDEK\r\nJOBS_YEDEK\r\nJOB_HISTORY_YEDEK<\/pre>\n
[Primary-2] SQL> drop table test.JOBS_YEDEK;\r\n\r\nTable dropped.\r\n\r\n[Primary-2] SQL> select table_name from dba_tables where owner='TEST';\r\n\r\nTABLE_NAME\r\n------------------------------\r\nJOB_HISTORY_YEDEK\r\nEMPLOYEES_YEDEK<\/pre>\n
[Physical-1] SQL> select table_name from dba_tables where owner='TEST';\r\n\r\nTABLE_NAME\r\n------------------------------\r\nJOB_HISTORY_YEDEK\r\nEMPLOYEES_YEDEK<\/pre>\n
[Logical-1] SQL> select table_name from dba_tables where owner='TEST';\r\n\r\nTABLE_NAME\r\n------------------------------\r\nEMPLOYEES_YEDEK\r\nJOB_HISTORY_YEDEK<\/pre>\n
I stopped Redo-Apply before starting Broker Configurations, and then I saw that the dropped table was gone from Standby even though I never opened it. This is because while enabling Broker Configuration, it also launches Redo-Apply. We can see this with the following query.<\/p>\n
[Primary-2] SQL> select DATABASE_MODE, RECOVERY_MODE, PROTECTION_MODE from v$archive_dest_status;\r\n\r\nDATABASE_MODE       RECOVERY_MODE                       PROTECTION_MODE\r\n--------------- ----------------------- --------------------\r\nOPEN                             IDLE                                                MAXIMUM PERFORMANCE\r\nOPEN_READ-ONLY     MANAGED REAL TIME APPLY     MAXIMUM PERFORMANCE\r\nOPEN                             LOGICAL REAL TIME APPLY        MAXIMUM PERFORMANCE<\/pre>\n
Step12:<\/h3>\n
Configuration can be managed not only from the Primary Database, but from all instances in the Broker Environment. The reason is that the configuration file is in all Instances and the DMONs in the instances communicate with each other for the changes to be made and the files are updated.<\/p>\n
[oracle@logical1 ~]$ dgmgrl\r\nDGMGRL for Linux: Version 11.2.0.4.0 - 64bit Production\r\n\r\nCopyright (c) 2000, 2009, Oracle. All rights reserved.\r\n\r\nWelcome to DGMGRL, type \"help\" for information.\r\nDGMGRL> connect sys\/Passw0rd4\r\nConnected.\r\nDGMGRL> show configuration\r\n;\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<\/pre>\n
[oracle@standby2 ~]$ dgmgrl\r\nDGMGRL for Linux: Version 11.2.0.4.0 - 64bit Production\r\n\r\nCopyright (c) 2000, 2009, Oracle. All rights reserved.\r\n\r\nWelcome to DGMGRL, type \"help\" for information.\r\nDGMGRL> connect sys\/Passw0rd4\r\nConnected.\r\nDGMGRL> 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<\/pre>\n
<\/div>\n
<\/path><\/svg><\/i> \"Loading\"<\/p>\n
<\/div>\n","protected":false},"excerpt":{"rendered":"
In this article, we will create data guard broker configuration. You can see the overview of data guard broker in the article named “What is Oracle Data Guard Broker“. Our current data guard environment is as follows; [Primary Side] [oracle@primary1 ~]$ srvctl config database -d primary Database unique name: primary Database name: primary Oracle home: …<\/p>\n
<\/div>\n
<\/path><\/svg><\/i> \"Loading\"<\/p>\n
<\/div>\n","protected":false},"author":484,"featured_media":18459,"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":[10363,10362,10361,10360],"class_list":["post-18449","post","type-post","status-publish","format-standard","has-post-thumbnail","","category-oracle","tag-ora-16136","tag-ora-16136-managed-standby-recovery-not-active","tag-ora-16283","tag-ora-16283-operation-not-permitted-on-non-apply-instance"],"aioseo_notices":[],"yoast_head":"\nHow To Create Data Guard Broker Configuration - Database Tutorials<\/title>\n<meta name=\"description\" content=\"In this article, we will create data guard broker configuration in 12c and 11g.\" \/>\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\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How To Create Data Guard Broker Configuration - Database Tutorials\" \/>\n<meta property=\"og:description\" content=\"In this article, we will create data guard broker configuration in 12c and 11g.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/\" \/>\n<meta property=\"og:site_name\" content=\"Database Tutorials\" \/>\n<meta property=\"article:published_time\" content=\"2021-01-26T09:03:49+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-01-26T09:07:33+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/01\/brokerconfiguration.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"712\" \/>\n\t<meta property=\"og:image:height\" content=\"425\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\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=\"21 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/\"},\"author\":{\"name\":\"Onur ARDAHANLI\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6\"},\"headline\":\"How To Create Data Guard Broker Configuration\",\"datePublished\":\"2021-01-26T09:03:49+00:00\",\"dateModified\":\"2021-01-26T09:07:33+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/\"},\"wordCount\":1051,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/01\/brokerconfiguration.jpg\",\"keywords\":[\"ORA-16136\",\"ORA-16136: Managed Standby Recovery not active\",\"ORA-16283\",\"ORA-16283: operation not permitted on non-apply instance\"],\"articleSection\":[\"ORACLE\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/\",\"url\":\"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/\",\"name\":\"How To Create Data Guard Broker Configuration - Database Tutorials\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/01\/brokerconfiguration.jpg\",\"datePublished\":\"2021-01-26T09:03:49+00:00\",\"dateModified\":\"2021-01-26T09:07:33+00:00\",\"description\":\"In this article, we will create data guard broker configuration in 12c and 11g.\",\"breadcrumb\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#primaryimage\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/01\/brokerconfiguration.jpg\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/01\/brokerconfiguration.jpg\",\"width\":712,\"height\":425},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/dbtut.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How To Create Data Guard Broker Configuration\"}]},{\"@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":"How To Create Data Guard Broker Configuration - Database Tutorials","description":"In this article, we will create data guard broker configuration in 12c and 11g.","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\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/","og_locale":"en_US","og_type":"article","og_title":"How To Create Data Guard Broker Configuration - Database Tutorials","og_description":"In this article, we will create data guard broker configuration in 12c and 11g.","og_url":"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/","og_site_name":"Database Tutorials","article_published_time":"2021-01-26T09:03:49+00:00","article_modified_time":"2021-01-26T09:07:33+00:00","og_image":[{"width":712,"height":425,"url":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/01\/brokerconfiguration.jpg","type":"image\/jpeg"}],"author":"Onur ARDAHANLI","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Onur ARDAHANLI","Est. reading time":"21 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#article","isPartOf":{"@id":"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/"},"author":{"name":"Onur ARDAHANLI","@id":"https:\/\/dbtut.com\/#\/schema\/person\/7fcd466cd0d347ec64aaa48f18f780c6"},"headline":"How To Create Data Guard Broker Configuration","datePublished":"2021-01-26T09:03:49+00:00","dateModified":"2021-01-26T09:07:33+00:00","mainEntityOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/"},"wordCount":1051,"commentCount":0,"publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/01\/brokerconfiguration.jpg","keywords":["ORA-16136","ORA-16136: Managed Standby Recovery not active","ORA-16283","ORA-16283: operation not permitted on non-apply instance"],"articleSection":["ORACLE"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/","url":"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/","name":"How To Create Data Guard Broker Configuration - Database Tutorials","isPartOf":{"@id":"https:\/\/dbtut.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#primaryimage"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/01\/brokerconfiguration.jpg","datePublished":"2021-01-26T09:03:49+00:00","dateModified":"2021-01-26T09:07:33+00:00","description":"In this article, we will create data guard broker configuration in 12c and 11g.","breadcrumb":{"@id":"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#primaryimage","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/01\/brokerconfiguration.jpg","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/01\/brokerconfiguration.jpg","width":712,"height":425},{"@type":"BreadcrumbList","@id":"https:\/\/dbtut.com\/index.php\/2021\/01\/26\/how-to-create-data-guard-broker-configuration\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/dbtut.com\/"},{"@type":"ListItem","position":2,"name":"How To Create Data Guard Broker Configuration"}]},{"@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\/18449","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=18449"}],"version-history":[{"count":0,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/18449\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media\/18459"}],"wp:attachment":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media?parent=18449"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/categories?post=18449"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/tags?post=18449"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}