> 下面介紹兩則11.2.0.4 physical standby兩則故障處理

# 1. ORA-1033
## 1.1 報錯
主庫alert日誌報錯如下：
```
Error 1033 received logging on to the standby
PING[ARC1]: Heartbeat failed to connect to standby 'target'. Error is 1033.
Fri Mar 12 09:10:01 2021
```

## 1.2 排查
使用sqlplus使用target tnsnames連線physical standby，
sqlplus sys/password@target as sysdba可以正常連線。

## 1.3 原因
ora 1033發生在physical standby環境中，如果物理備庫狀態正常，一般由於密碼檔案異常導致。

## 1.4 解決
重新將主庫密碼檔案scp至備庫，rename即可解決。

# 2. 未正確配置引數導致備庫redo在開啟應用之後變為源庫磁碟組名稱
## 2.1 問題描述

> 主庫使用ASM，備庫使用檔案系統。
搭建Dataguard之後，在開啟recover managed standby database disconnect from session時，
physical standby logfile位置均變成了+datadg源端主庫磁碟組名稱，未正確rename為備庫路徑。

```

備庫日誌報錯如下：
Errors in file xxx/trace/sid_mrp0_45884.trc:
ORA-00313: open failed for members of log group xx of thread xx
ORA-00312: online log xx thread 1: '+DATADG/sid/onlinelog/group_xx.286.1062779691'
ORA-17503: ksfdopn:2 Failed to open file +DATADG/sid/onlinelog/group_xx.286.1062779691
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-00312: online log 6 thread 1: '+DATADG/sid/onlinelog/group_xx.266.1020201301'
ORA-17503: ksfdopn:2 Failed to open file +DATADG/sid/onlinelog/group_xx.266.1020201301
ORA-15001: diskgroup "DATADG" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
Clearing online redo logfile xx complete
Media Recovery Waiting for thread xx sequence xxxx
Completed: ALTER DATABASE RECOVER  managed standby database disconnect from session

```
備庫日誌位置此時如下：
```
SYS@dg > select * from v$logfile;

GROUP# STATUS     TYPE    MEMBER                                                       IS_
------ ---------- ------- ------------------------------------------------------------ ---
     5 INVALID    ONLINE  +datadg                                                      NO
     2 INVALID    ONLINE  +datadg                                                      NO
     1 INVALID    ONLINE  +datadg                                                      NO
     6 INVALID    ONLINE  +datadg                                                      NO
     6 INVALID    ONLINE  +datadg                                                      NO

```

## 2.2 原因

由於構建備庫時未正確設定log_file_name_convert，也未手動處理physical standby redo logfile物理位置，導致。

## 2.3 解決

1. 主庫
```
-- 先暫時停止源端傳輸。
SYS@src > alter system set log_archive_dest_state_2=defer;
```
2. 備庫

```
--取消日誌應用
SYS@dg > recover managed standby database cancel;

--正確設定log_file_name_convert
SYS@dg > alter system set log_file_name_convert='+DATADG/sid/onlinelog','/oradata' scope=spfile;

```

3. 主庫

```
--主庫備份控制檔案
RMAN> backup current controlfile for standby format '/rman/ctl_bak.bak';

-- 傳輸至備端
$ scp /rman/ctl_bak.bak targt:/rman/
```

4. 備庫

```
--重新恢復控制檔案
RMAN> shutdown immediate;

RMAN> startup nomount;

RMAN> restore controlfile from '/rman/ctl_bak.bak';

--註冊備庫資料檔案並切換
RMAN> catalog start with '/home/oracle/oradata/';

RMAN> switch database to copy;

--確認備庫redo logfile是否正確轉換
SYS@siddg > select * from v$logfile;

GROUP# STATUS     TYPE    MEMBER                                                       IS_
------ ---------- ------- ------------------------------------------------------------ ---
     5            ONLINE  /oradata/group_5.263.984508005                   NO
     2            ONLINE  /oradata/group_2.262.984508005                   NO
     1            ONLINE  /oradata/group_1.261.984508005                   NO
     6            ONLINE  /oradata/group_6.266.1020201301                  NO
     6            ONLINE  /oradata/group_6.286.1062779691                  NO
```

5. 主庫

```
--源端開啟傳輸
SYS@src > alter system set log_archive_dest_state_2=enable;

```

6. 備庫

```
--開啟應用
SYS@dg > alter database open read only;
SYS@dg > alter database recover managed standby database using current logfile disconnect from session;

--觀察備庫alert日誌，會發現會自動最後clear掉logfile，重新在新位置生成logfile
Errors in file xxx.trc:
ORA-00313: open failed for members of log group xx of thread x
ORA-00312: online log xx thread 1: 'path'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log xx thread xx: 'path'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Clearing online redo logfile xx complete

```

END.

Oracle 11.2.0.4 Dataguard兩則故障處理

相關文章