ORACLE RAC TO RAC DG搭建過程中可能遇到的問題

    在ORACLE DataGuard部署過程中，如果操作不規範，可能遇到很多想不到的問題。有些問題是配置引數不到位，有些

是操作不規範遺漏導致。

    問題一

    主庫複製備庫到備機時，rman遠端登陸主庫作為複製的目標庫rman無法登陸備機備庫，就是下面的命令執行報錯：

rman target sys/oracle@dg_orclp auxiliary sys/oracle@dg_orcls

問題原始是從庫的TNS配置不規範，缺少(UR=A)，示例配置

DG_ORCLS =

  (DESCRIPTION =

    (ADDRESS_LIST =

      (ADDRESS = (PROTOCOL = TCP)(HOST = 172.10.101.36)(PORT = 1521))

      (LOAD_BALANCE = off)

    )

    (CONNECT_DATA =

      (SERVER = DEDICATED)

      (SERVICE_NAME =DG_ORCLS)

      ( UR=A )

    )

  )

    問題二

    主庫複製備庫到備機時，rman執行duplicat的時，duplicat過程執行報錯 ORA-17629&ORA-17627&ORA-17629 ：

RMAN> duplicate target database for standby from active database nofilenamecheck;

Starting Duplicate Db at 2019-03-10 11:38:4

allocated channel: ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: SID=1811 instance=orcl1 device type=DISK

contents of Memory Script:

{

   backup as copy reuse

   targetfile  '/oracle/app/oracle/product/11.2.0/dbs/orapworcl1' auxiliary format 

 '/oracle/app/oracle/product/11.2.0/dbs/orapworcl1'   ;

}

executing Memory Script

Starting backup at 2019-03-10 11:38:43

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=4533 instance=orcl1 device type=DISK

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of Duplicate Db command at 03/10/2019 11:38:45

RMAN-05501: aborting duplication of target database

RMAN-03015: error occurred in stored script Memory Script

RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/10/2019 11:38:45

ORA-17629: Cannot connect to the remote database server

ORA-17627: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

ORA-17629: Cannot connect to the remote database server

RMAN> 

這個問題比較有趣，配置好TNS後，透過ttnsping和sqlplus sys/oracle@to_orcl as sysdba都正常，就是rman的

dumplicat進行從庫的複製時報錯。該問題的原因是備庫的TNS配置中的服務名和主庫備庫中的log_archive_config='

dg_config=()'引數中配置的服務名不一致導致，或者是主庫以alter system方式修改了log_archive_config='dg_config'

，資料庫沒有重啟，因為log_archive_config引數是靜態引數，需要重啟資料庫服務才能生效。    

    問題三

    在備機透過rman複製主庫的時，rman複製過程報錯： RMAN-03009&ORA-17628 ：

Starting backup at 2019-03-10 12:56:20

using channel ORA_DISK_1

channel ORA_DISK_1: starting datafile copy

input datafile file number=00003 name=+DGSYSTEM/orcl/datafile/undotbs1.261.876856357

output file name=+DGSYSTEM/orcl/datafile/undotbs1.340.1002545783 tag=TAG20190310T124734

channel ORA_DISK_1: datafile copy complete, elapsed time: 00:02:55

channel ORA_DISK_1: starting datafile copy

input datafile file number=00004 name=+DGSYSTEM/orcl/datafile/undotbs2.263.876856383

RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/10/2019 12:59:21

ORA-17628: Oracle error 19505 returned by remote Oracle server

continuing other job steps,  job failed will not be re-run

該問題十分嚴重，透過job failed will not be re-run可以得知，此次的DG複製完全失敗了。此問題的原因是存放資料檔案

相關的ASM磁碟組空間耗盡導致的，因此，在DG主備庫開始配置之前，一定要評估好備庫的儲存並規劃好，避免這種因存

儲空間問題導致DG複製失敗的發生。

    問題四

    DG備庫複製完主庫後，備庫alert日誌告警登陸主庫被拒絕，主庫告警日誌提示登陸備庫失敗。

--備庫告警日誌

Thu Mar 14 06:51:40 2019

RFS[252]: Assigned to RFS process 3408762

RFS[252]: Opened log for thread 2 sequence 23863 dbid -2091533043 branch 876856333

Thu Mar 14 06:51:42 2019

2019-03-14 06:51:42 logon denied from 172.10.101.61 5964584 oracle with oracle@orcl01 (TNS V1-V3) ¨C oracle@orcl01 (TNS V1-V3) ===username=

Thu Mar 14 06:51:42 2019

2019-03-14 06:51:42 logon denied from 172.10.101.61 13697046 oracle with oracle@orcl01 (TNS V1-V3) ¨C oracle@orcl01 (TNS V1-V3) ===username=

Thu Mar 14 06:51:43 2019

2019-03-14 06:51:43 logon denied from 172.10.101.61 10486550 oracle with oracle@orcl01 (TNS V1-V3) ¨C oracle@orcl01 (TNS V1-V3) ===username=

Thu Mar 14 06:51:43 2019

2019-03-14 06:51:43 logon denied from 172.10.101.61 7274758 oracle with oracle@orcl01 (TNS V1-V3) ¨C oracle@orcl01 (TNS V1-V3) ===username=

Thu Mar 14 06:51:43 2019

2019-03-14 06:51:43 logon denied from 172.10.101.61 14156172 oracle with oracle@orcl01 (TNS V1-V3) ¨C oracle@orcl01 (TNS V1-V3) ===username=

--主庫告警日誌

Thu Mar 14 09:13:45 2019

Error 1017 received logging on to the standby

------------------------------------------------------------

Check that the primary and standby are using a password file

and remote_login_passwordfile is set to SHARED or EXCLUSIVE, 

and that the SYS password is same in the password files.

returning error ORA-16191

Error 16191 for archive log file 3 to 'TO_standby'

Thu Mar 14 15:49:10 2019

Archived Log entry 203881 added for thread 2 sequence 59940 ID 0x53e28673 dest 1:

Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_nsa2_2753334.trc:

ORA-16191: Primary log shipping client not logged on standby

Thu Mar 14 15:49:10 2019

ARCb: Archival destination is a Primary RAC instance: 'TO_standby'

該問題十分嚴重，會導致備庫同步程式抓取歸檔日誌失敗。但是，導致該問題的原因是主備庫的sys密碼檔案不一致導致，可

能是搭建過程中有人修改了sys密碼，處理該問題的方法比較簡單，從叢集主庫任意節點同步sys密碼檔案即可。

    問題五

    另外，在DG搭建過程中，可能遇到grid或者oracle透過lsnrctl檢視監聽狀態的時候看到很多服務名，其中有很多l類似：

SYS$SYS.KUPC$C_1_20170318000713.ORCL，sys登陸sqlplus，show parameter service可以發現：

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

service_names                        string      SYS$SYS.KUPC$C_1_20170318000713.orcl.US.ORACLE.COM,  

                                                SYS$SYS.KUPC$C_1_20170405000711.orcl.US.ORACLE.COM,

                                                 SYS$SYS.KUPC$S_1_20170314000710.ORCL, 

                                                 SYS$SYS.KUPC$S_1_20170318000713.ORCL,                                                  

                                                 SYS$SYS.KUPC$S_1_20170323000707.ORCL, 

                                                 SYS$SYS.KUPC$S_1_20170331000709.ORCL, 

                                                 SYS$SYS.KUPC$S_1_20170403000701.ORCL,

                                                 SYS$SYS.KUPC$S_1_20170405000711.ORCL, 

                                                 SYS$SYS.KUPC$C_1_20170314000710.ORCL......

導致該問題的原因是expdp或者impdp被異常終端導致，可以重置service_names或者重啟資料庫服務加以解決。