OGG-01028問題處理記錄
OGG-01028問題處理記錄
參考:
http://blog.itpub.net/26277071/viewspace-713360/
1、環境:
OGG版本:11.1.1
OS:suse 10 sp4 x64
DB:oracle 10.2.0.5 RAC x64
2、原因:由於讀取不到歸檔日誌,導致抽取失敗,重新掛載歸檔日誌後,抽取到下一個日誌時報OGG-01028錯誤,錯誤內容如下:
2017-12-14 16:33:26 ERROR OGG-01028 Record position (SeqNo: 11845, RBA: 2064, SCN: 3628.259323944 (155824006
73832)) is beyond end of recovery (SeqNo: 11844, RBA: 40830128, SCN: 3628.255608022 (15582396957910), Timestamp:
2017-12-09 16:18:58.000000).
3、查資料分析:
Ans:- It the hitting with the bug 12330566 and the fix will be available only with 11.2 version only. Till that time you need to wait and the workaround is to use BR BROFF refer doc:- OGG Extract abends with OGG-01028 Record position is beyond end of recovery (Doc ID 1335470.1)
4、問題解決執行過程:
檢視BR檔案
oracle@ptdb02:/ogg/11.1/BR/EXT_S1> pwd
/ogg/11.1/BR/EXT_S1
oracle@ptdb02:/ogg/11.1/BR/EXT_S1> ls -l
total 40
-rw-rw---- 1 oracle oinstall 65536 2017-12-09 16:42 CP.EXT_S1.000004442
-rw-rw---- 1 oracle oinstall 65536 2017-04-12 18:51 PO.EXT_S1.0140659.0000000
drwxrwxr-x 2 oracle oinstall 4096 2014-12-12 18:35 stale
編輯抽取程式引數
edit param ext_s1
引數檔案新增
BR BROFF
重啟抽取程式
start ext_s1
報如下錯誤
2017-12-14 20:13:28 ERROR OGG-00446 Could not find archived log for sequence 7234 thread 1 under default des
tinations SQL <select to_char(first_time, 'YYYY-MM-DD') from gv$log_history where sequence# = :ora_seqno and thr
ead# = :ora_thead>, error retrieving redo file name for sequence 7234, archived = 1, use_alternate = 0Not able t
o establish initial position for sequence 7234, rba 54123536.
2017-12-14 20:13:28 ERROR OGG-01668 PROCESS ABENDING.
檢視歸檔日誌:1節點儲存歸檔日誌最老為7663,時間為2017-5-1日的;
指定時間點,重新抽取;
1. First of all, the Extract process was stopped with the force option.
GGSCI 4> send extract ext_s1, forcestop
2. The start position of the Extract process was altered to the beginning of the long running transaction.
GGSCI 5> alter extract ext_s1, begin 2017-12-09 16:18:58
3. The extract process was started.
GGSCI 4> start extract ext_s1
4. Sure enough, the Extract process was reinitialized and continued to process the backlog.
GGSCI 5> info ext_s1, detail
檢視狀態正常。
參考:
http://blog.itpub.net/26277071/viewspace-713360/
1、環境:
OGG版本:11.1.1
OS:suse 10 sp4 x64
DB:oracle 10.2.0.5 RAC x64
2、原因:由於讀取不到歸檔日誌,導致抽取失敗,重新掛載歸檔日誌後,抽取到下一個日誌時報OGG-01028錯誤,錯誤內容如下:
2017-12-14 16:33:26 ERROR OGG-01028 Record position (SeqNo: 11845, RBA: 2064, SCN: 3628.259323944 (155824006
73832)) is beyond end of recovery (SeqNo: 11844, RBA: 40830128, SCN: 3628.255608022 (15582396957910), Timestamp:
2017-12-09 16:18:58.000000).
3、查資料分析:
Ans:- It the hitting with the bug 12330566 and the fix will be available only with 11.2 version only. Till that time you need to wait and the workaround is to use BR BROFF refer doc:- OGG Extract abends with OGG-01028 Record position is beyond end of recovery (Doc ID 1335470.1)
4、問題解決執行過程:
檢視BR檔案
oracle@ptdb02:/ogg/11.1/BR/EXT_S1> pwd
/ogg/11.1/BR/EXT_S1
oracle@ptdb02:/ogg/11.1/BR/EXT_S1> ls -l
total 40
-rw-rw---- 1 oracle oinstall 65536 2017-12-09 16:42 CP.EXT_S1.000004442
-rw-rw---- 1 oracle oinstall 65536 2017-04-12 18:51 PO.EXT_S1.0140659.0000000
drwxrwxr-x 2 oracle oinstall 4096 2014-12-12 18:35 stale
編輯抽取程式引數
edit param ext_s1
引數檔案新增
BR BROFF
重啟抽取程式
start ext_s1
報如下錯誤
2017-12-14 20:13:28 ERROR OGG-00446 Could not find archived log for sequence 7234 thread 1 under default des
tinations SQL <select to_char(first_time, 'YYYY-MM-DD') from gv$log_history where sequence# = :ora_seqno and thr
ead# = :ora_thead>, error retrieving redo file name for sequence 7234, archived = 1, use_alternate = 0Not able t
o establish initial position for sequence 7234, rba 54123536.
2017-12-14 20:13:28 ERROR OGG-01668 PROCESS ABENDING.
檢視歸檔日誌:1節點儲存歸檔日誌最老為7663,時間為2017-5-1日的;
指定時間點,重新抽取;
1. First of all, the Extract process was stopped with the force option.
GGSCI 4> send extract ext_s1, forcestop
2. The start position of the Extract process was altered to the beginning of the long running transaction.
GGSCI 5> alter extract ext_s1, begin 2017-12-09 16:18:58
3. The extract process was started.
GGSCI 4> start extract ext_s1
4. Sure enough, the Extract process was reinitialized and continued to process the backlog.
GGSCI 5> info ext_s1, detail
檢視狀態正常。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/29519108/viewspace-2148731/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 一次線上問題處理過程記錄
- pyinstaller打包cx_Oracle庫問題處理記錄Oracle
- 記憶體分配問題處理記憶體
- OGG-01028錯誤處理
- 【問題處理】MySQL忘記root密碼的處理辦法MySql密碼
- Oracle排程作業引起的空間驟增問題處理記錄Oracle
- 記錄django-rest-framework處理微信支付notify_url遇到的問題DjangoRESTFramework
- 【問題備忘錄】記一次DNS解析異常現象處理DNS
- 使用air實現熱過載時遇到的問題處理方式記錄AI
- 將磁碟誤掛載到根分割槽下的問題處理記錄
- MySql資料庫ibtmp1檔案增長問題處理記錄MySql資料庫
- Linux記憶體異常問題處理Linux記憶體
- Docker問題記錄Docker
- 處理問題的方法
- perl中文處理問題
- 漢字處理問題?
- xml處理的問題XML
- 貨品問題處理
- [git] git問題處理Git
- 記錄Laravel異常處理類Laravel
- php redis 處理websocket聊天記錄PHPRedisWeb
- 由於目錄變更引起的資料服務無法啟動的問題處理記錄
- 記一次處理達夢慢SQL問題SQL
- openGauss資料庫xlog目錄滿問題處理資料庫
- jQuery 遇到問題記錄jQuery
- Oracle DBA 問題記錄Oracle
- 技術問題記錄
- golang json處理問題GolangJSON
- 併發問題處理方式
- ASMCMD處理問題一則ASM
- mysql的處理能力問題MySql
- RMAN處理split block問題BloC
- mysql問題處理兩則MySql
- Oracle啟動問題處理Oracle
- mysql 問題處理二則MySql
- Oracle壞塊問題處理Oracle
- 資料處理--pandas問題
- 異常處理 - Go 學習記錄Go