http://www.oracle.com/technetwork/cn/tutorials/smiley-fsfo-088047-zhs.html

dg_broker_start
dg_broker_config_file1

alter system set dg_broker_start=true scope=both;

[oracle@12crac2 ~]$ ps -ef|grep -i _dmon|grep -v grep
oracle 2699 1 0 06:57 ? 00:00:01 ora_dmon_db1

DGMGRL> show configuration
ORA-16532: Data Guard broker configuration does not exist

DGMGRL> help create
DGMGRL> create configuration 'db' as primary database is db connect identifier is db;
DGMGRL>help add
DGMGRL>add database "SBDB1" as connect identifier is "sbdb1" maintained as physical;
DGMGRL>enable configuration

RSM0 started with pid=48, OS id=34551
ALTER SYSTEM SET log_archive_dest_1='location=USE_DB_RECOVERY_FILE_DEST','valid_for=(ALL_LOGFILES, ALL_ROLES)' SCOPE=BOTH;
ALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='db1';
ALTER SYSTEM SET log_archive_format='%t_%s_%r.dbf' SCOPE=SPFILE SID='db1';
ALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH SID='*';
ALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH SID='*';
ALTER SYSTEM SET log_archive_max_processes=4 SCOPE=BOTH SID='*';
ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH SID='*';

Creating Data Guard Broker Monitor Process (DMON)
04/03/2018 23:26:33
>> Starting Data Guard Broker bootstrap <<
Broker Configuration File Locations:
dg_broker_config_file1 = "/u01/app/oracle/product/11.2.0/dbhome_1/dbs/dr1SBDB1.dat"
dg_broker_config_file2 = "/u01/app/oracle/product/11.2.0/dbhome_1/dbs/dr2SBDB1.dat"
04/03/2018 23:26:38
Broker Configuration: "db"
Protection Mode: Maximum Performance
Fast-Start Failover (FSFO): Disabled, flags=0x0, version=0
Primary Database: db (0x01010000)
Standby Database: SBDB1, Enabled Physical Standby (0x02010000)

DGMGRL> show database sbdb1
Object "sbdb1" was not found
DGMGRL> show database SBDB1
Object "sbdb1" was not found

DGMGRL> show database 'SBDB1'
Database - SBDB1
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 0 seconds (computed 0 seconds ago)
Apply Lag: 0 seconds (computed 0 seconds ago)
Apply Rate: 0 Byte/s
Real Time Query: ON
Instance(s):
SBDB1
Database Status:
SUCCESS

DGMGRL> convert database 'SBDB1' to snapshot standby;
Converting database "SBDB1" to a Snapshot Standby database, please wait...
Database "SBDB1" converted successfully

SQL> select open_mode, database_role, protection_mode,flashback_on from v$database;
OPEN_MODE DATABASE_ROLE PROTECTION_MODE FLASHBACK_ON
-------------------- ---------------- -------------------- ------------------
READ WRITE SNAPSHOT STANDBY MAXIMUM PERFORMANCE **RESTORE POINT ONLY**
SQL> truncate table system.test;
Table truncated.
SQL> select count(*) from system.test;
COUNT(*)
----------
DGMGRL>convet database 'SBDB1' to physical standby;
Unable to connect to database
ORA-12545: Connect failed because target host or object does not exist
Failed.
Warning: You are no longer connected to ORACLE.
Please complete the following steps and reissue the CONVERT command:
shut down instance "SBDB1" of database "SBDB1"
start up and mount instance "SBDB1" of database "SBDB1"

ALTER DATABASE CONVERT TO PHYSICAL STANDBY (SBDB1)
Killing 3 processes with pids 3013,3017,3019 (all RFS) in order to disallow current and future RFS connections. Requested by OS process 3025
Flashback Restore Start
Flashback Restore Complete
Drop guaranteed restore point
Guaranteed restore point dropped
Clearing standby activation ID 1736364983 (0x677ed3b7)
The primary database controlfile was created using the
'MAXLOGFILES 192' clause.
There is space for up to 188 standby redo logfiles
Use the following SQL commands on the standby database to create
standby redo logfiles that match the primary database:
ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl5.f' SIZE 52428800;
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Clearing online redo logfile 1 /u01/app/oracle/oradata/SBDB1/SBDB1/onlinelog/o1_mf_1_fd4wmho5_.log
Clearing online log 1 of thread 1 sequence number 3
Clearing online redo logfile 1 complete
Clearing online redo logfile 2 /u01/app/oracle/oradata/SBDB1/SBDB1/onlinelog/o1_mf_2_fd4wmjq3_.log
Clearing online log 2 of thread 1 sequence number 4
Clearing online redo logfile 2 complete
Completed: alter database convert to physical standby
Wed Apr 04 01:15:50 2018
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Assigned to RFS process 3029
RFS[3]: Selected log 5 for thread 1 sequence 70 dbid 1729483220 branch 965667412
Wed Apr 04 01:16:11 2018
RFS[4]: Assigned to RFS process 3031
RFS[4]: Selected log 6 for thread 1 sequence 69 dbid 1729483220 branch 965667412
Wed Apr 04 01:16:11 2018
Expanded controlfile section 11 from 28 to 203 records
Requested to grow by 175 records; added 7 blocks of records
Archived Log entry 29 added for thread 1 sequence 69 ID 0x6715d4d4 dest 1:
Wed Apr 04 01:16:13 2018
ARC2: Becoming the active heartbeat ARCH
Wed Apr 04 01:17:13 2018
alter database open
Data Guard Broker initializing...

SQL> select open_mode, database_role, protection_mode,flashback_on from v$database;
OPEN_MODE DATABASE_ROLE PROTECTION_MODE FLASHBACK_ON
-------------------- ---------------- -------------------- ------------------
READ ONLY WITH APPLY PHYSICAL STANDBY MAXIMUM PERFORMANCE NO
SQL> select count(*) from system.test;
COUNT(*)
----------
15386

DGMGRL> show database verbose 'SBDB1';
Database - SBDB1
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 0 seconds (computed 1 second ago)
Apply Lag: 0 seconds (computed 1 second ago)
Apply Rate: 0 Byte/s
Real Time Query: ON

DGMGRL> enable fast_start failover
Error: ORA-16651: requirements not met for enabling fast-start failover
Failed.
DGMGRL> exit
[oracle@12crac2 ~]$ oerr ora 16651
16651, 0000, "requirements not met for enabling fast-start failover"
// *Cause: The attempt to enable fast-start failover could not be completed
// because one or more requirements were not met:
// - The Data Guard configuration must be in either MaxAvailability
// or MaxPerformance protection mode.
// - The LogXptMode property for both the primary database and
// the fast-start failover target standby database must be
// set to SYNC if the configuration protection mode is set to
// MaxAvailability mode.
// - The LogXptMode property for both the primary database and
// the fast-start failover target standby database must be
// set to ASYNC if the configuration protection mode is set to
// MaxPerformance mode.
// - The primary database and the fast-start failover target standby
// database must both have flashback enabled.
// - No valid target standby database was specified in the primary
// database FastStartFailoverTarget property prior to the attempt
// to enable fast-start failover, and more than one standby
// database exists in the Data Guard configuration.

DGMGRL> enable fast_start failover
Enabled.
DGMGRL> show configuration
Configuration - db
Protection Mode: MaxAvailability
Databases:
db - Primary database
Warning: ORA-16819: fast-start failover observer not started
SBDB1 - (*) Physical standby database
Warning: ORA-16819: fast-start failover observer not started
Fast-Start Failover: ENABLED
Configuration Status:
WARNING
[oracle@12crac2 ~]$ oerr ora 16819
16819, 0000, "fast-start failover observer not started"
// *Cause: The observer for fast-start failover was not started. As a
// result, fast-start failover could not happen in the case of
// a primary database failure.
// *Action: Start the fast-start failover observer by using, for example, the
// DGMGRL START OBSERVER command.

DGMGRL> start observer
Observer started

DGMGRL> show configuration
Configuration - db
Protection Mode: MaxAvailability
Databases:
db - Primary database
SBDB1 - (*) Physical standby database
Fast-Start Failover: ENABLED
Configuration Status:
SUCCESS
3.3 switchover

DGMGRL> switchover to 'SBDB1';
Performing switchover NOW, please wait...
Operation requires a connection to instance "SBDB1" on database "SBDB1"
Connecting to instance "SBDB1"...
Connected.
New primary database "SBDB1" is opening...
Operation requires startup of instance "db1" on database "db"
Starting instance "db1"...
Unable to connect to database
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Failed.
Warning: You are no longer connected to ORACLE.
Please complete the following steps to finish switchover:
start up instance "db1" of database "db"

DGMGRL> show configuration
Configuration - db
Protection Mode: MaxAvailability
Databases:
SBDB1 - Primary database
db - (*) Physical standby database
Fast-Start Failover: ENABLED
Configuration Status:
SUCCESS

DGMGRL> switchover to db
Performing switchover NOW, please wait...
Operation requires a connection to instance "db1" on database "db"
Connecting to instance "db1"...
Connected.
New primary database "db" is opening...
Operation requires startup of instance "SBDB1" on database "SBDB1"
Starting instance "SBDB1"...

edit database 'SBDB1' set property DelayMins=1 ;

ALTER SYSTEM SET log_archive_dest_2='service="sbdb1"','LGWR ASYNC NOAFFIRM delay=1 optional compression=disable max_failure=0 max_connections=1 reopen=300 db_unique_name="SBDB1" net_timeout=30','valid_for=(all_logfiles,primary_role)' SCOPE=BOTH;
ALTER SYSTEM SWITCH ALL LOGFILE start (db1)
ALTER SYSTEM SWITCH ALL LOGFILE complete (db1)

edit database 'SBDB1' set property LogXptMode=sync;

ALTER SYSTEM SET log_archive_dest_2='service="sbdb1"','LGWR SYNC AFFIRM delay=1 optional compression=disable max_failure=0 max_connections=1 reopen=300 db_unique_name="SBDB1" net_timeout=30','valid_for=(all_logfiles,primary_role)' SCOPE=BOTH;

DGMGRL> show configuration
ORA-16541: database is not enabled

[oracle@12crac1 dbs]$ oerr ora 16541
16541, 00000, "database is not enabled"
// *Cause: The database specified in the request was not enabled.
// *Action: Select an enabled database and reissue the request.

DGMGRL> show configuration
Configuration - db
Protection Mode: MaxAvailability
Databases:
db - Primary database
Warning: ORA-16792: configurable property value is inconsistent with database setting
SBDB1 - Physical standby database
Warning: ORA-16792: configurable property value is inconsistent with database setting
Fast-Start Failover: DISABLED

DGMGRL> edit database db set property LogFileNameConvert='/u01/app/oracle/oradata/SBDB1/,+data';
Property "logfilenameconvert" updated
DGMGRL> edit database db set property DbFileNameConvert='/u01/app/oracle/oradata/SBDB1/,+data';
Property "dbfilenameconvert" updated
DGMGRL> edit database 'SBDB1' set property DbFileNameConvert='+data,/u01/app/oracle/oradata/SBDB1/';
Property "dbfilenameconvert" updated
DGMGRL> edit database 'SBDB1' set property LogFileNameConvert='+data,/u01/app/oracle/oradata/SBDB1/';
Property "logfilenameconvert" updated
DGMGRL> enable configuration
DGMGRL> show configuration
Configuration - db
Protection Mode: MaxAvailability
Databases:
db - Primary database
SBDB1 - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
5.2 ora-16820
DGMGRL> show configuration
Configuration - db
Protection Mode: MaxAvailability
Databases:
SBDB1 - Primary database
Error: ORA-16820: fast-start failover observer is no longer observing this database
db - (*) Physical standby database
Error: ORA-16820: fast-start failover observer is no longer observing this database
Fast-Start Failover: ENABLED
Configuration Status:
ERROR

DGMGRL> show configuration
Configuration - db
Protection Mode: MaxAvailability
Databases:
SBDB1 - Primary database
Error: ORA-16820: fast-start failover observer is no longer observing this database
db - (*) Physical standby database (disabled)
ORA-16661: the standby database needs to be reinstated
Fast-Start Failover: ENABLED
Configuration Status:
ERROR

SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-16649: possible failover to another database prevents this database from
being opened

SQL> select database_role,FLASHBACK_ON from v$database;
DATABASE_ROLE FLASHBACK_ON
PRIMARY YES
DGMGRL> show configuration
ORA-16795: the standby database needs to be re-created

DGMGRL> reinstate database db
Reinstating database "db", please wait...
Reinstatement of database "db" succeeded

DGMGRL> show configuration
Configuration - 1
Protection Mode: MaxPerformance
Databases:
prod2 - Primary database
standby - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
ORA-16610: command "Broker operation" in progress
DGM-17017: unable to determine configuration status

drcx: cannot open configuration file "/home/oracle/broker/standby2.data"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
08/02/2018 10:52:38
drcx: cannot open configuration file "/home/oracle/broker/standby1.dat"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
DMON Registering service standby_DGB with listener(s)
08/02/2018 10:52:41

dgmgrl>disable configuration;
sql>alter system set dg_broker_start=false;
sys@standby>alter system set dg_broker_config_file1='/home/oracle/broker/standby1.dat';
sys@standby>alter system set dg_broker_config_file2='/home/oracle/broker/standby2.dat';
DGMGRL> enable configuration
DGMGRL> show configuration
Configuration - 1
Protection Mode: MaxPerformance
Databases:
prod2 - Primary database
standby - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS

Error Id: ORA-16651

Title: requirements not met for enabling Fast-Start Failover

Description:

requirements not met for enabling Fast-Start Failover

Action:

Retry the attempted command after correcting the issue: - Set the Data Guard configuration to MaxAvailability protection mode. - Ensure that the LogXptMode property for both the primary database and the Fast-Start Failover target standby database are SYNC. - Ensure that both the primary database and the Fast-Start Failover target standby database have flashback enabled. - Set the primary database’s FastStartFailoverTarget property to the db_unique_name value of the desired target standby database add the desired target standby database’s FastStartFailoverTarget property to the db_unique_name value of the primary database.

Cause:

The attempt to enable Fast-Start Failover could not be completed because one or more requirements have not been met: - The Data Guard configuration must be in MaxAvailability protection mode. - The LogXptMode property for both the primary database and the Fast-Start Failover target standby database must be SYNC. - The primary database and the Fast-Start Failover target standby database must both have flashback enabled. - No valid target standby database was specified in the primary database’s FastStartFailoverTarget property prior to the attempt to enable Fast-Start Failover, and more than one standby database exists in the Data Guard configuration.

Error Id: ORA-16649

Title: database will open after Data Guard broker has evaluated Fast-Start Failover status

Description:

database will open after Data Guard broker has evaluated Fast-Start Failover status

Action:

No action is normally required. The Data Guard broker will continue opening the database after determining a Fast-Start failover did not occur. If there is a chance that a Fast-Start Failover did occur, the database will remain in the mounted state and will not open. In this case, check the target standby to see if a role transition took place.

Cause:

The database is being opened while Fast-Start failover is enabled. The message indicates that the Data Guard broker will first determine if conditions are suitable for opening; that is, a Fast-Start failover did not occur while the database was unavailable.

Error Id: ORA-16661

Title: the standby database needs to be reinstated

Description:

the standby database needs to be reinstated

Action:

Use the DGMGRL REINSTATE DATABASE command or Enterprise Manager to reinstate the database. If the target database has flashback enabled and it has sufficient flashback logs, the database will be reinstated as a standby database for the current primary database.

Cause:

A switchover or failover operatione has caused this database to require reinstatement.

Error Id: ORA-16541

Title: site is not enabled

Description:

site is not enabled

Action:

Select an enabled site and reissue the request.

Cause:

The site specified in the request was not enabled.

Error Id: ORA-16532

Title: Data Guard broker configuration does not exist

Description:

Data Guard broker configuration does not exist

Action:

Create a Data Guard broker configuration prior to issuing other requests.

Cause:

A broker operation was requested that requires an already existing broker configuration.

Error Id: ORA-16525

Title: the Data Guard broker is not yet available

Description:

the Data Guard broker is not yet available

Action:

If the broker has not been started, set DG_BROKER_START to true and allow the broker to finish initializing before making the request. If the broker failed to start, check the Data Guard log for possible errors. Otherwise, retry the operation.

Cause:

The Data Guard broker process has not yet been started, is initializing, or has failed to start.

Error Id: ORA-27037

Title: unable to obtain file status

Description:

unable to obtain file status

Action:

check errno

Cause:

stat system call returned an error, additional information indicates which function encountered the error

Error Id: ORA-16820

Title: Fast-Start Failover observer is no longer observing this database

Description:

Fast-Start Failover observer is no longer observing this database

Action:

Check the reason why the observer cannot contact this database. If the problem cannot be corrected, stop the current observer by connecting to the Data Guard configuration and issue the DGMGRL "STOP OBSERVER" command. Then restart the observer on another node. You may use the DGMGRL "START OBSERVER" command to start the observer on the other node.

Cause:

A previously started observer was no longer actively observing this database. A significant amount of time elapsed since this database last heard from the observer. Possible reasons were: - The node where the observer was running was not available. - The network connection between the observer and this database was not available. - Observer process was terminated unexpectedly.

Error Id: ORA-16819

Title: Fast-Start Failover observer not started

Description:

Fast-Start Failover observer not started

Action:

Start the Fast-Start Failover observer by using, for example, the DGMGRL START OBSERVER command.

Cause:

The observer for Fast-Start Failover was not started. As a result, Fast-Start Failover could not happen in the case of a primary database failure.

Error Id: ORA-16797

Title: database is not using a server parameter file

Description:

database is not using a server parameter file

Action:

Issue CREATE SPFILE=’..’ FROM PFILE=’...’" command to create a server parameter file and then restart the database to use it.

Cause:

The database is not using a server parameter file or the resource guard was unable to access the server parameter file.

Error Id: ORA-16795

Title: database resource guard detects that database re-creation is required

Description:

database resource guard detects that database re-creation is required

Action:

Re-create (or flash back) the standby database. Connect to the primary database in the broker configuration and reenable broker management of that database. At this point you may connect to that standby database and resume issuing client commands. Alternatively, many client commands that cannot be completed at the standby database when in this error state can be completed successfully when issued to the primary database. In this case, simply reconnect to the primary database and retry the command.

Cause:

In the act of failover or switchover, the database resource guard may have detected that re-creation of the database is necessary. This occurs when the database resource guard recognizes a situation in which the database in question cannot be a viable standby database for the new primary database. Until this error status is resolved for this database, information about this database and the broker configuration to which it belongs is unavailable to a broker client that is connected to this database. Therefore, all commands directed by that client to this database cannot be completed.

Error Id: ORA-16792

Title: configuration property value is inconsistent with database setting

Description:

configuration property value is inconsistent with database setting

Action:

Query property the InconsistentProperties on the database or check the Data Guard broker log to find which properties are set inconsistently. Reset these properties to make them consistent with the database settings. Alternatively, enable the database or the entire configuration to allow the configuration property settings to be propagated to to the initialization parameters.

Cause:

The values of one or more configuration properties were inconsistent with database in-memory settings or server parameter file settings. This may happen by altering initialization parameters directly instead of altering property values using Data Guard broker.

Error Id: ORA-12545

Title: Connect failed because target host or object does not exist

Description:

Connect failed because target host or object does not exist

Action:

Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect parameter is the node name. Ensure that the executable for the server exists (perhaps "oracle" is missing.) If the protocol is TCP/IP, edit the TNSNAMES.ORA file to change the host name to a numeric IP address and try again.

Cause:

The address specified is not valid, or the program being connected to does not exist.

Error Id: ORA-12514

Title: TNS:listener does not currently know of service requested in connect descriptor

Description:

TNS:listener does not currently know of service requested in connect descriptor

Action:

- Wait a moment and try to connect a second time. - Check which services are currently known by the listener by executing: lsnrctl services <listener name> - Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener. - If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener. - Check for an event in the listener.log file.

Cause:

The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.

Error Id: TNS-12545

Title: Connect failed because target host or object does not exist

Description:

Connect failed because target host or object does not exist

Action:

Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect parameter is the node name. Ensure that the executable for the server exists (perhaps "oracle" is missing.) If the protocol is TCP/IP, edit the TNSNAMES.ORA file to change the host name to a numeric IP address and try again.

Cause:

The address specified is not valid, or the program being connected to does not exist.

Error Id: TNS-12514

Title: TNS:listener does not currently know of service requested in connect descriptor

Description:

TNS:listener does not currently know of service requested in connect descriptor

Action:

- Wait a moment and try to connect a second time. - Check which services are currently known by the listener by executing: lsnrctl services <listener name> - Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener. - If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener. - Check for an event in the listener.log file.

Cause:

The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.

Error Id: TNS-00515

Title: Connect failed because target host or object does not exist

Description:

Connect failed because target host or object does not exist

Action:

Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect parameter is the node name. Ensure that the executable for the server exists (perhaps "oracle" is missing.)

Cause:

The address specified is not valid, or the program being connected to does not exist.

-- 来自：