.
\nIn the part I we have seen the properties that are imported when you add a database to the configuration, and which are then managed by the broker. Now we will list the properties that are managed by the broker, but whose default value is not imported from the instance parameters.
\n
Here are the properties from primary database where I removed those we have seen in previous Part I:
\n\nDGMGRL> show database verbose demo11;\n...\n Properties:\n...\n DGConnectIdentifier = '//vm112/DEMO12'\n LogXptMode = 'ASYNC'\n RedoRoutes = ''\n DelayMins = '0'\n Binding = 'optional'\n MaxFailure = '0'\n ReopenSecs = '300'\n NetTimeout = '30'\n RedoCompression = 'DISABLE'\n LogShipping = 'ON'\n InconsistentLogXptProps = '(monitor)'\n StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'\n AlternateLocation = ''\n...\nThey are related with log shipping destination. When I enabled the configuration, the LOG_ARCHIVE_DEST have been set with those values:
\n\nSQL> show parameter log_archive_dest_1\n \nNAME TYPE VALUE\n------------------------------------ ----------- ------------------------------\nlog_archive_dest_1 string location=USE_DB_RECOVERY_FILE_\n DEST, valid_for=(ALL_LOGFILES,\n ALL_ROLES)\nlog_archive_dest_2 string service=\"//vm112/DEMO12\", ASYN\n C NOAFFIRM delay=0 optional co\n mpression=disable max_failure=\n 0 max_connections=1 reopen=300\n db_unique_name=\"demo12\" net_t\n imeout=30, valid_for=(online_l\n ogfile,all_roles)\nlog_archive_dest_state_1 string enable\nlog_archive_dest_state_2 string enable\nNow, I manage them from the Data Guard broker:
\n\nDGMGRL> edit database demo12 set property LogXptMode='SYNC';\nProperty \"logxptmode\" updated\nwhich has run the following ALTER SYSTEM:
\n\nALTER SYSTEM SET log_archive_dest_2='service=\"//vm112/DEMO12\"','SYNC AFFIRM delay=0 optional compression=disable max_failure=0 max_connections=1 reopen=300 db_unique_name=\"demo12\" net_timeout=30','valid_for=(online_logfile,all_roles)' SCOPE=BOTH;\nWhen we go to SYNC, the destination is set to SYNC (wait for log shipping) and AFFIRM (wait for log write)
\nHere is the correspondence. The properties change the LOG_ARCHIVE_DEST attributes to set log shipping.
\n| Broker property | \nLOG_ARCHIVE_DEST | \n
|---|---|
| RedoRoutes | \nLOG_ARCHIVE_DEST_n | \n
| DGConnectIdentifier | \nservice= | \n
| LogXptMode | \nSYNC/ASYNC,AFFIRM/NOAFFIRM | \n
| DelayMins | \ndelay= | \n
| Binding | \nMANDATORY/OPTIONAL | \n
| MaxFailure | \nmax_failure= | \n
| ReopenSecs | \nreopen= | \n
| NetTimeout | \nnet_timeout= | \n
| RedoCompression | \ncompression= | \n
| LogShipping | \nLOG_ARCHIVE_DEST_STATE_n | \n
| StandbyArchiveLocation | \nlocation= | \n
| AlternateLocation | \nlocation= | \n
I’ll show that those parameters are not imported when we create a configuration. Here I remove and re-create the configuration and I still have the LOG_ARCHIVE_DEST as SYNC.
\n\nDGMGRL> REMOVE CONFIGURATION;\nRemoved configuration\nDGMGRL> CREATE CONFIGURATION demo11 AS PRIMARY DATABASE IS demo11 CONNECT IDENTIFIER IS '//vm111/DEMO11';\nConfiguration \"demo11\" created with primary database \"demo11\"\nDGMGRL> ADD DATABASE demo12 AS CONNECT IDENTIFIER IS '//vm112/DEMO12';\nDatabase \"demo12\" added\nDGMGRL> ENABLE CONFIGURATION demo11;\nEnabled.\nBut:
\n\nSQL> show parameter log_archive_dest_2\n\nNAME TYPE VALUE\n------------------------------------ ----------- ------------------------------\nlog_archive_dest_2 string service=\"//vm112/DEMO12\", ASYN\n C NOAFFIRM delay=0 optional co\n mpression=disable max_failure=\n 0 max_connections=1 reopen=300\n db_unique_name=\"demo12\" net_t\n imeout=30, valid_for=(online_l\n ogfile,all_roles)\nThe log shipping attributes have been set to the broker properties defaults. This is the main difference from the properties we have seen in Part I.
\nNever change the LOG_ARCHIVE_DEST with ALTER SYSTEM. they are managed by the broker. And don’t forget to set those properties if you re-create the broker configuration.