Azure cloud oracle11.2.0.4 dataguard archive log transmission 1034 details

1, after the establishment of dataguard, archive log transmission but to view the master database on the log tail-fdataoraclediagrdbmstest_m1powerdestracealert_powerdes.log, the display information is as follows: SunMay0800: 34: 172016error10341_edloggingontothestandbyping [ARC

1. After the slave uard is set up, the archive log cannot be transferred to view the log tail-f/data/oracle/diag/rdbms/test_m1/powerdes/trace/alert_powerdes.log on the master database, the following information is displayed: Sun May 08 00:34:17 2016 Error 1034 logged ed logging on to the standby PING [ARC

1. archive log cannot be transferred after the deployment uard is set up.

View the logs on the master database.

Tail-f/data/oracle/diag/rdbms/test_m1/powerdes/trace/alert_powerdes.log. The following information is displayed:

Sun May 08 00:34:17 2016

Error 1034 removed ed logging on to the standby

PING [ARC2]: Heartbeat failed to connect to standby 'test _ m2'. Error is1034.

2. tnsping earch_m2 is successful.

[Oracle @ azure_test_dbm1_3_111 admin] $ tnsping test_m3 TNS Ping Utility for Linux: Version 11.2.0.4.0-Production on 08-MAY-2016 09:13:42 Copyright (c) 1997,201 3, Oracle. All rights reserved. Used parameter files: Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.3.112) (PORT = 1521) (CONNECT_DATA = (SERVICE_NAME = test_m2 ))) OK (0 msec) [Oracle @ azure_test_dbm1_3_111 admin] $

3. Go to the standby database of standby and Check service_name. We can see that service_names is indeed test_m2.

It seems that service_name is useless, as shown below:

[Oracle @ azure_test_dbm1_3_112 admin] $ rlwrap sqlplus/as sysdba SQL * Plus: Release 11.2.0.4.0 Production on Sun May 8 09:15:27 2016 Copyright (c) 1982,201 3, Oracle. All rights reserved. Connected: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0-64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> show parameter name; NAME TYPE VALUE ----------------------------------------------------------------------------- Cell_offloadgroup_name string Db_file_name_convert string/oracle/app/oracle/oradata/pow Erdes,/oracle/app/oracle/orad Ata/powerdes Db_name string powerdes Db_unique_name string test_m2 Global_names boolean FALSE Instance_name string powerdes Lock_name_space string Log_file_name_convert string/data/oracle/oradata/powerdes, /Data/oracle/oradata/pwerdes NAME TYPE VALUE ----------------------------------------------------------------------------- Processor_group_name string Service_names string test_m2 SQL>

Source blog address: http://blog.csdn.net/mchdba/article/details/51344246. Thank you!

4. An error is reported when you log on to the master database and standby database through sqlplus.

# Sqlplus logon Error [Oracle @ azure_test_dbm1_3_111 admin] $ sqlplus sys/testsys @ test_m2 as sysdba SQL * Plus: Release 11.2.0.4.0 Production on Sun May 8 09:19:48 2016 Copyright (c) 1982,201 3, Oracle. All rights reserved. ERROR: ORA-12514: TNS: listener does not currently know of service requested in connect Descriptor Enter user-name: # Standby database sqlplus logon Error [Oracle @ azure_test_dbm1_3_112 admin] $ sqlplus sys/testsys @ test_m2 as sysdba SQL * Plus: Release 11.2.0.4.0 Production on Sun May 8 09:18:39 2016 Copyright (c) 1982,201 3, Oracle. All rights reserved. ERROR: ORA-12514: TNS: listener does not currently know of service requested in connect Descriptor Enter user-name:

All reports error: ORA-12514: TNS: listener does not currently know of service requested in connect descriptor, this problem is generally involved in tnsnames. ora inside the service_name is not correct.

5. Replace service_name to solve the problem.

Recall the creation process of the standby database. When I first built the database dbca, the service_name was set to powerdes. When I configured the replica uard, I modified the parameter file initpowerdes. ora, which has new settings *. db_unique_name = test_m2, create spfile frompfile again; then start the database with the new parameter file, and then we can see that service_names has changed to test_m2, and I am in tnsnames. the new service_names name test_m2 is set in ora, and the new test_m2 does not take effect. The error ORA-12514 is reported.

Therefore, I want to replace test_m2 with the original powerdes, and there are two places to change, one is listener. ora, one is tnsnames. ora, master database and slave database standby database must be modified as follows:

# Modify one file tnsnames. ora in the master database of the master database # Tnsnames. ora File [Oracle @ azure_test_dbm1_3_111 admin] $ vim tnsnames. ora Test_m2 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.3.112) (PORT = 1521 )) ) (CONNECT_DATA = (SERVICE_NAME = powerdes) ) ) # The standby database needs to modify two files: listener. ora and tnsnames. ora. # Listener. ora File [Oracle @ azure_test_dbm1_3_112 admin] $ vim listener. ora SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = PLSExtProc) (ORACLE_HOME =/oracle/app/oracle/product/11.2.0/dbhome_1) (PROGRAM = extproc) ) (SID_DESC = (SID_NAME = powerdes) (ORACLE_HOME =/oracle/app/oracle/product/11.2.0/dbhome_1) ) ) ADR_BASE_LISTENER =/oracle/app/oracle # Tnsnames. ora File [Oracle @ azure_test_dbm1_3_112 admin] $ vim tnsnames. ora Test_m2 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.3.112) (PORT = 1521 )) ) (CONNECT_DATA = (SERVICE_NAME = powerdes) ) )

After the configuration is modified, restart the lsnrctl listening service and log on to test_m2 with sqlplus in the slave database. The logon is successful:

[Oracle @ azure_test_dbm1_3_112 admin] $ sqlplus sys/testsys @ test_m2 as sysdba SQL * Plus: Release 11.2.0.4.0 Production on Sun May 8 09:34:51 2016 Copyright (c) 1982,201 3, Oracle. All rights reserved. Connected: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0-64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL>

Go back to the background alert log of the master database, and you will find that there are records that have started to transfer archived logs:

......

**************************************** **************************

LGWR: Setting 'active' archival fordestination LOG_ARCHIVE_DEST_2

**************************************** **************************

LGWR: Standby redo logfile selected toarchive thread 1 sequence 26

LGWR: Standby redo logfile selected forthread 1 sequence 26 for destination LOG_ARCHIVE_DEST_2

Thread 1 advanced to log sequence 26 (LGWRswitch)

Current log #2 seq #26 mem #0:/oracle/app/oracle/oradata/powerdes/redo02.log

Sun May 08 01:12:22 2016

Archived Log entry 22 added for thread 1 sequence 25 ID 0xcf7feffa dest 1:

ARC0: Standby redo logfile selected forthread 1 sequence 25 for destination LOG_ARCHIVE_DEST_2

Destination LOG_ARCHIVE_DEST_2 isSYNCHRONIZED

......

PS: the problem is strange here. The last time service_name was changed to test_m2 in the new parameter file, the archive logs were transferred to the standby database standby. However, this time the original service_name must be kept. It seems that there are other mysteries here. You need to explore it clearly.