Implementing Data Guard - Expert Consolidation in Oracle Database 12c - page 348

30 (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
31 )
32 (DESCRIPTION =
33 (ADDRESS = (PROTOCOL = TCP)(HOST = server1.example.com ) ( PORT = 1521 ))
34 )
35 )
36 ADR_BASE_LISTENER = /u01/app/grid
37 ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER = ON
[grid@server1 admin]$

The additional information to be added starts in line 3. Grid Infrastructure does not add database services
statically by default. As you can see the global database name is set to the service name you got from the static
connect identifier. If you are using a database domain (initialization parameter db_domain ) then add the domain
after the ${ORACLE_SID}_DGMGRL , for example CDB1DCA_DGMGRL.example.com . Do not forget to reload the listener for
the changes to take effect. Careful though with instances that register dynamically with the listener: it could take a
little while until they announce their presence again. You might want to run “alter system register” on these and/or
perform the operation during a quieter period. Before you continue with the other listeners you should do a quick
connection test. Launch sqlplus, then connect as sys@ staticConnectionIdentifier as sysdba. If you are told you are
connected, chances are high that the Broker can connect to the database as well.

Standby file management
The management of data files has to be automated. By default the DBA is responsible for managing data files on
the standby databases which have previously been added to the primary database. The addition of a new file to the
primary database generates redo as well. The same statement is then executed on the standby database, and thanks
to Oracle Managed Files or the file name conversion parameters in the initialization file the file is created in the
correct location with automatic standby file management.
Before you change the standby file management on all databases, primary and standby alike, you should quickly
check if your file name conversion parameters are set.

■ Note Skip this test if you are using Oracle managed Files and your disk group names are identical.

The two file-system based databases used in the earlier example should have file name and log file name
conversion parameters set in both directions. In the example the primary database did not have name conversion
parameters set, which has been rectified:

DGMGRL> show database "CDBFSDCB" dbFileNameConvert
DbFileNameConvert = '/u01/oradata/CDBFSDCA, /u01/oradata/CDBFSDCB'
DGMGRL> show database "CDBFSDCB" logFileNameConvert
LogFileNameConvert = '/u01/oradata/CDBFSDCA, /u01/oradata/CDBFSDCB'
DGMGRL> edit database "CDBFSDCA" set property
> dbFileNameConvert = '/u01/oradata/CDBFSDCB, /u01/oradata/CDBFSDCA';
Warning: ORA-16675: database instance restart required for property value modification
to take effect