DGMGRL> connect sys/oracle@dbsalve;

DGMGRL> show configuration;

ERROR
DGMGRL> show configuration verbose;

FastStartFailoverThreshold      ='120'
OperationTimeout                ='30'
FastStartFailoverLagLimit       ='30'
CommunicationTimeout            ='180'
ObserverReconnect               ='0'
FastStartFailoverAutoReinstate  ='TRUE'
FastStartFailoverPmyShutdown    ='TRUE'
BystandersFollowRoleChange      ='ALL'
ObserverOverride                ='FALSE'
ExternalDestination1            =''
ExternalDestination2            =''
PrimaryLostWriteAction          ='CONTINUE'

ERROR

SQL> startup mount;

SQL> set linesize 1000
col name format a10;
col db_unique_name format a10;
col open_mode format a20;
col protection_mode format a20;
col database_role format a20;
col switchover_status format a20;
SQL> SELECTNAME,OPEN_MODE,PROTECTION_MODE,DATABASE_ROLE,SWITCHOVER_STATUS,DB_UNIQUE_NAMEFROM V$DATABASE;
NAME          OPEN_MODE                   PROTECTION_MODE      DATABASE_ROLE   SWITCHOVER_STATUS    DB_UNIQUE_
------------------------------ -------------------- ---------------------------------------- ----------
DBMAST      MOUNTED              MAXIMUMAVAILABILITY PRIMARY                    NOT ALLOWED                DBMAST

DGMGRL> connect sys/oracle@DBMAST;

DGMGRL> show configuration verbose;

FastStartFailoverThreshold      ='120'
OperationTimeout                ='30'
FastStartFailoverLagLimit       ='30'
CommunicationTimeout            ='180'
ObserverReconnect               = '0'
FastStartFailoverAutoReinstate  ='TRUE'
FastStartFailoverPmyShutdown    ='TRUE'
BystandersFollowRoleChange      ='ALL'
ObserverOverride                ='FALSE'
ExternalDestination1            =''
ExternalDestination2            =''
PrimaryLostWriteAction          ='CONTINUE'

[oracle@DB-MASTERtrace]pwd
/u01/app/software/oracle/diag/rdbms/dbmast/DBMAST/trace
[oracle@DB-MASTER trace]ll drcDBMAST.log
-rw-r----- 1 oracle oinstall 2.1M 4月  25 15:25 drcDBMAST.log
04/25/2016 14:33:23
>> Starting Data Guard Brokerbootstrap <<
Broker Configuration File Locations:
dg_broker_config_file1 ="/u01/app/software/oracle/product/11.2.0/db_1/dbs/dr1DBMAST.dat"
dg_broker_config_file2 ="/u01/app/software/oracle/product/11.2.0/db_1/dbs/dr2DBMAST.dat"
04/25/2016 14:33:27
DMON Registering serviceDBMAST_DGB with listener(s)
Broker Configuration:       "DG_BROKER_SALVE"
Protection Mode:           Maximum Availability
Fast-Start Failover (FSFO): Enabled, flags=0x40051, version=2
Primary Database:          DBSALVE (0x01010000)
Standby Database:          DBMAST, Enabled Physical Standby (FSFO target) (0x02010000)
04/25/2016 14:33:31
Failed to connect to remote databaseDBSALVE. Error is ORA-12541
Failed to send message to site DBSALVE.Error code is ORA-12541.
database DBMAST unable to contact primarydatabase for version check; status ORA-12541
completing bootstrap of this database
Creating process RSM0
04/25/2016 14:33:34
SQL Execution error=604, sql=[ALTERDATABASE MOUNT]. See error stack below.

Failed to mount standby database.
Apply Instance for Database DBMAST set toDBMAST
Database Resource SetState Error (16746)
SQL Execution error=604, sql=[ALTERDATABASE RECOVER MANAGED STANDBY DATABASE THROUGH ALL SWITCHOVER DISCONNECT USING CURRENT LOGFILE]. See error stack below.

Failed to connect to remote databaseDBSALVE. Error is ORA-12541
Failed to send message to site DBSALVE.Error code is ORA-12541.
Command EDIT DATABASE DBMAST SET PROPERTYActualApplyInstance = DBMAST completed
04/25/2016 15:18:57
Site DBSALVE returned ORA-16665.
04/25/2016 15:19:12
Site DBSALVE returned ORA-16665.
04/25/2016 15:19:27
Site DBSALVE returned ORA-16665.
04/25/2016 15:19:42
Site DBSALVE returned ORA-16665.
04/25/2016 15:19:57
Site DBSALVE returned ORA-16665.
04/25/2016 15:20:12
Site DBSALVE returned ORA-16665.
04/25/2016 15:20:27
Site DBSALVE returned ORA-16665.
04/25/2016 15:20:42
Site DBSALVE returned ORA-16665.
04/25/2016 15:20:57
Site DBSALVE returned ORA-16665.
04/25/2016 15:21:12
Site DBSALVE returned ORA-16665.
04/25/2016 15:21:27
Site DBSALVE returned ORA-16665.
04/25/2016 15:21:43
Site DBSALVE returned ORA-16665.
04/25/2016 15:22:37

***********************************************************************
Fatal NI connect error 12514, connectingto:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.0.202)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=DBSALVE_DGB)(CID=(PROGRAM=oracle)(HOST=DB-MASTER)(USER=oracle))))
VERSION INFORMATION:
TNSfor Linux: Version 11.2.0.4.0 - Production
TCP/IPNT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production

Tracing not turned on.
Tnserror struct:
ns main err code: 12564

ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Mon Apr 25 15:22:37 2016
NSV0 started with pid=24, OS id=1956

(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.0.202)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=DBSALVE_DGB)(CID=(PROGRAM=oracle)(HOST=DB-MASTER)(USER=oracle))))

DGMGRL> REINSTATE DATABASE 'DBMAST';

SQL> SELECTNAME,OPEN_MODE,PROTECTION_MODE,DATABASE_ROLE,SWITCHOVER_STATUS,DB_UNIQUE_NAMEFROM V$DATABASE;
NAME           OPEN_MODE                   PROTECTION_MODE      DATABASE_ROLE   SWITCHOVER_STATUS    DB_UNIQUE_
---------- -------------------- ---------------------------------------- -------------------- ----------
DBMAST       MOUNTED              MAXIMUMAVAILABILITY PHYSICALSTANDBY  RECOVERY NEEDED      DBMAST

DGMGRL> show configuration ;

DGMGRL>

SQL> alter system set log_archive_dest_state_2=enablescope=both;

SQL> alter database recover managed standby databasedisconnect from session;
SQL> SELECTNAME,OPEN_MODE,PROTECTION_MODE,DATABASE_ROLE,SWITCHOVER_STATUS,DB_UNIQUE_NAMEFROM V$DATABASE;
NAME           OPEN_MODE                   PROTECTION_MODE      DATABASE_ROLE   SWITCHOVER_STATUS    DB_UNIQUE_
---------- -------------------- ---------------------------------------- -------------------- ----------
DBMAST       MOUNTED              MAXIMUMAVAILABILITY PHYSICAL STANDBY   SWITCHOVER  PENDING   DBMAST

DGMGRL> connect sys/oracle@DBSALVE

DGMGRL> show configuration;

ERROR

DGMGRL> STOP OBSERVER

SQL> select fs_failover_status from v$database;
FS_FAILOVER_STATUS
------------------------------------------------------------------
DISABLED
SQL> shutdown immediate;

SQL> startup mount;

Total System Global Area 446775296 bytes
Fixed Size                2254104 bytes
Variable Size                  360712936 bytes
Database Buffers            79691776 bytes
Redo Buffers                    4116480 bytes

REINSTATE
DGMGRL> show configuration;

ERROR
DGMGRL> reinstate database 'DBMAST';

DGMGRL> show configuration;

ERROR

SQL> SELECTNAME,OPEN_MODE,PROTECTION_MODE,DATABASE_ROLE,SWITCHOVER_STATUS,DB_UNIQUE_NAMEFROM V$DATABASE;
NAME           OPEN_MODE                   PROTECTION_MODE      DATABASE_ROLE   SWITCHOVER_STATUS    DB_UNIQUE_
---------- -------------------- ---------------------------------------- -------------------- ----------
DBMAST       READ ONLY WITH APPLY MAXIMUM AVAILABILITYPHYSICAL STANDBY   NOT ALLOWED                DBMAST

DGMGRL> stop OBSERVER;

DGMGRL> show configuration;

SUCCESS

Error Id: ORA-01100

Title: database already mounted

Description:

database already mounted

Action:

none

Cause:

A database is already mounted in this instance.

Error Id: ORA-16636

Title: Fast-Start Failover target standby in error state, cannot stop observer

Description:

Fast-Start Failover target standby in error state, cannot stop observer

Action:

Additional information about this failure is recorded in the Data Guard broker log file for the primary database. This information helps you identify the reason why the target standby database was unable to participate in the STOP OBSERVER operation. You may correct the problem that is indicated by that information and retry the operation. Alternatively, you may forcibly disable Fast-Start Failover while connected to the primary database using the DISABLE FAST_START FAILOVER FORCE command in the DGMGRL CLI. You can then stop the observer regardless of the current state of the target standby database.

Cause:

A STOP OBSERVER operation could not be completed when Fast-Start Failover was enabled because the target standby database could not participate in the STOP OBSERVER operation.

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-16575

Title: request terminated at broker discretion

Description:

request terminated at broker discretion

Action:

There is no action to be taken.

Cause:

This status is returned when the broker terminates a user- initiated request. The broker will terminate all other current and pending requests when it begins processing a failover request. These other requests are terminated with this status.

Error Id: ORA-01665

Title: control file is not a standby control file

Description:

control file is not a standby control file

Action:

Create a standby control file before attempting to use the database as a standby database.

Cause:

Attempting to mount, recover or activate a standby database without a standby control file.

Error Id: ORA-16825

Title: Fast-Start Failover and other errors or warnings detected for the database

Description:

Fast-Start Failover and other errors or warnings detected for the database

Action:

Check the StatusReport monitorable property of the database specified.

Cause:

The broker has detected multiple errors or warnings for the database. At least one of the detected errors or warnings may prevent a Fast-Start Failover from occurring.

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-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-12541

Title: TNS:no listener

Description:

TNS:no listener

Action:

Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange). Start the listener on the remote machine.

Cause:

The connection request could not be completed because the listener is not running.

Error Id: ORA-00604

Title: error occurred at recursive SQL level string

Description:

error occurred at recursive SQL level string

Action:

If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support.

Cause:

An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables).

Error Id: TNS-12564

Title: TNS:connection refused

Description:

TNS:connection refused

Action:

Not normally visible to the user. For further details, turn on tracing and reexecute the operation.

Cause:

The connect request was denied by the remote user (or TNS software).

-- 来自：