Data Guard Broker 19c
Hi,
In an earlier version of Data Guard, when the broker had problems, one of the automatic answers I got from support was to recreate the broker configuration.
In other words:
But in my case, using Active Data Guard with Far Sync, with many fine-tuned configurations, it was not so convenient. I had a number of ways I tried to be efficient:
In an earlier version of Data Guard, when the broker had problems, one of the automatic answers I got from support was to recreate the broker configuration.
In other words:
- Drop the configuration.
- Create the configuration.
But in my case, using Active Data Guard with Far Sync, with many fine-tuned configurations, it was not so convenient. I had a number of ways I tried to be efficient:
- I could write down all broker commands - to be able to run them again next time.
- For versions 11.2.0.4 and 12.1.0.2, I found a way to query the broker and re-create a current configuration creation script (Extract Data Guard Commands).
- I also had some issues trying to Drop/remove Far-Sync Configurations from broker 12.1.
- On version 12.2.0.1, I found out that the broker metadata was changed, so I had to update my previous script for Extract Data Guard Commands on Oracle 12.2.
- Finally on Oracle 19c, there will be new commands to export and import a broker configuration 😊
dgmgrl> export configuration to ‘meta.xml’Here is a full listing, shown at Oracle OpenWorld 2018, of new features promised to be in Oracle 19c:
dgmgrl> import configuration from ‘meta.xml’
Comments
Post a Comment