Data Guard remove/create configuration Tips
Oracle Database Tips by Donald BurlesonDecember 10, 2015
Upgrading to Oracle10g Data Guard
with remove configuration and create configuraton
Upgrading to Oracle10g database software in a
Data Guard environment involves the following activities:
If the Data Guard configuration is managed
by Data Guard broker, the broker configuration needs to be
removed using the existing version of database software. In
other words, remove the Oracle9i configuration before upgrading
to Oracle10g. Execute the following remove command after connecting to
any site in the configuration using DGMGRL to remove the
Install Oracle10g database software. The
Data Guard feature is not available with the Standard edition,
so the Enterprise edition must be installed. Additionally,
install Oracle Enterprise Manager (OEM) 10.1 in order to manage
the configuration using Data Guard Manager GUI interface, which
is tightly integrated with OEM.
The primary and standby databases should be
upgraded to Oracle10g. The log management services should be
stopped during the primary database upgrade. All of the redo
logs generated during the database upgrade should be applied
manually on each standby database. For more information on
upgrading to Oracle10g, refer to the documentation, "Oracle
Database Upgrade Guide 10g Release 1(10.1)".
Update the initialization parameter files
or server parameter files on the primary database and all the
standby databases to include the parameter db_unique_name.
The database unique name must be identical on all the databases
in a configuration.
Once all the databases in the Data Guard
configuration are upgraded to Oracle10g, the broker
configuration file will have to be created in order to manage
Data H]Guard with the Data Guard broker. Execute the following
create configuration command,
connecting to the primary database using DGMGRL, to recreate the
broker configuration file and to add standby databases:
CREATE CONFIGURATION '<ConfigName>' AS PRIMARY DATABASE IS
'<Primary Database Name>' CONNECT IDENTIFIER IS <Service
ADD DATABASE '<Oracle instance
Name>' AS CONNECT IDENTIFIER
IS <Service Name> MAINTAINED AS PHYSICAL;
Data Guard architecture has been fine tuned in
Oracle10g to support some of the previously unsupported features.
These architectural modifications have primarily been around log
management services. Moreover, the integration of Data Guard
technology and Flashback database has resulted in a couple of useful
techniques available to database administrators. This section looks
further into these changes and their impact.