Shulou(Shulou.com)05/31 Report--

This article mainly introduces the problems that may be encountered in the process of oracle 11.2.0.4 DataGuard Broker configuration, which has a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let the editor take you to know about it.

1. Alarm log warning of master and slave libraries caused by improper setting of archive parameter log_archive_dest_2

Problem phenomenon:

Main library

Web Apr 11 14:17:16 2018

RFS [85]: Assigned to RFS proess 28893

RFS [85]: Database mount ID mismatch [0x59764e70:0x5976ad14] (1500925552 0x59764e70:0x5976ad14 1500949780)

RFS [85]: Client instance is standby database instead of primary

RFS [85]: Not using real application clusters

Prepare the library

Web Apr 11 14:12:16 2018

PING [ARC2]: Heartbeat failed to connect to standby 'dbprimary'. Error is 16009.

Handling method (MOS document ID 1450132.1):

Prepare for database execution

Alter system set log_archive_dest_state_2=defer scope=both sid='*'

Or

Alter system set log_archive_dest_2='service=dbstandby arch sync valid_for= (online_logfiles,primary_role) db_unique_name=orcls' scope=both sid='*'

2. The DDL cannot synchronize to the slave database due to the inconsistent data file path of the master and slave database and the improper setting of db_file_name_convert and log_file_name_convert parameters.

Problem phenomenon:

Main library alarm log

ORA-01111:name for data file 5 is unknown-rename to correct file

ORA-01110: data file 5:'/ opt/oracle/product/11.2.0.4/db/dbs/UNNAMED00005

Ora-01157: cannot identify/lock data file 5-see DBWR trace file

ORA-01111: name for data file 5 is unknow-rename to correct file

ORA-01110: data file 5:'/ opt/oracle/product/11.2.0.4/db/dbs/UNNAMED00005

How to handle it:

The master and slave libraries check the convert parameters

SQL > show parameter convert

NAME TYPE VALUE

-

_ convert_set_to_join bollean FALSE

Db_file_name_convert string / opt/oracle/oradata/,/opt/oracle/oradata/

Log_file_name_convert string / opt/oracle/oradata/,/opt/oracle/oradata/

DGMGRL checks the DG mapping parameters of the master and slave libraries

DGMGRL > show configuration

Configuration-dgb_p

Protection Mode:Maxperformance

Databases:

Orcl-Primary database

Warning:ORA-16792: configurable property value is inconsistent with database setting

Orcls-Physical standby database

Warning:ORA-16792: configurable property value is inconsistent with database setting

Fast-Start Failover:DISABLED

DGMGRL > show database ORCL

Database-orcl

Role: PRIMARY

Intended State:TRANSPORT-ON

Instance (s):

Orcl

Warning:ORA-16714:the value of property DbFileNameConvert is inconsistent with the database setting

Database Status:

WARNING

-- View the specific DbFileNameConvert parameter values through the verbose parameter

Show database VERBOSE ORCL

Prepare for database execution

Alter database recover managed standby database cancel

Alter database create datafile'/ opt/oracle/product/11.2.0.4/db/dbs/UNNAMED00005' as'/ opt/oracle/oradata/test01.dbf'

Prepare the library to restart the log application process

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION

Add it to the startup parameter file of the master and slave library, and then regenerate the spfile

* .db_file_name_convert='/opt/oracle/oradata','/opt/oracle/oradata'

DGMGRL console execution

DGMGRL > edit database orcl set property DbFileNameConvert ='/ opt/oracle/oradata/,/opt/oracle/oradata/'

3. When configuring oracle dg, the db_unique_name of the master and slave database cannot be the same, otherwise the standby database cannot be added and an error is reported.

Problem phenomenon:

Error adding standby library to DGMGRL console

DGMGRL > add database orcls as connect identifier is dbstandby maintained as physical

Error: ORA-16642: DB_UNIQUE_NAME mismatch.

How to handle it:

Modify the db_unique_name value in the slave startup pfile (add without this parameter) is different from the db_unique_name value in the main library

Regenerate spfile and restart backup library

4. Sys users cannot log in to the master and slave libraries through the tns service name when they go to the slave through the rman duplicate master library.

Problem phenomenon:

[oracle@centdgpri ~] $tnsping dbprimary

TNS Ping Utility for Linux: Version 11.2.0.4.0-Production on 16-APR-2018 00:35:27

Copyright (c) 1997, 2013, Oracle. All rights reserved.

Used parameter files:

Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION= (ADDRESS_LIST= (ADDRESS= (PROTOCOL = TCP) (HOST=centdgpri) (PORT=1521)) (CONNECT_DATA= (SID=orcl) (SERVER=DEDICATED)

OK (160 msec)

[oracle@centdgpri ~] $sqlplus "sys/WaterH2o@dbprimary as sysdba"

SQL*Plus: Release 11.2.0.4.0 Production on Mon Apr 16 00:36:46 2018

Copyright (c) 1982, 2013, Oracle. All rights reserved.

ERROR:

ORA-01017: invalid username/password; logon denied

Problem handling:

Confirm that the sys password is correct

The following SQL queries the main database for no data

SELECT * FROM V$PWFILE_USERS

The user of the main library oracle executes the following command. The file name of orapwd is orapw$ORACLE_SID, and the path is $ORACLE_HOME/dbs, otherwise the generated file is invalid.

Orapwd file=$ORACLE_HOME/dbs/orapw$ORACLE_SID password=WaterH2o entries=30 force=y

Check again to confirm

5. In the use of oracle DG Broke-related ADG features, the master and slave libraries are required to open flashbacks, but the secondary libraries of oracle rman duplicate clones do not automatically open flashbacks.

You need to pay attention when turning on the flashback function for the standby library.

Stop the logging process

Recover managed standby database cancel

Create a flashback directory

Mkdir-p / opt/oracle/flash_recovery_area

Set database flashback parameters

Alter system set db_recovery_file_dest_size=10g

Alter system set db_recovery_file_dest='/opt/oracle/flash_recovery_area'

Turn on the database flashback function

Alter database flashback on

Confirm that the database flashback is open

Select name,db_unique_name,flashback_on from v$database

Thank you for reading this article carefully. I hope the article "what are the problems that may be encountered in the process of oracle 11.2.0.4 DataGuard Broker configuration" shared by the editor will be helpful to you. At the same time, I also hope you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.