oracle時間格式記錄異常導致OGG複製程式報錯
1. GoldenGate程式RSC00022出現ABENDED現象:
REPLICAT ABENDED RSC00022 00:00:06 03:52:53
2. 經檢查discardfile檔案發現問題出在以下update語句報錯:
2011-11-10 14:29:17 WARNING OGG-00869 OCI Error ORA-01850: hour must be between 0 and 23 (status = 1850), SQL
_SB_YZPZ" SET "PZ_XH" = :a1,"NSRNBM" = :a2,"PZZL_DM" = :a3,"GLWSH_XH" = :a4,"LSNSR_DM" = :a5,"ZSDLFS_DM" = :a6,"SB_RQ" = :a7,"SBFS_D
M" = :a8,"SBSX_DM" = :a9,"RJ_XH" = :a10,"ZZZLJSRY>.
Problem replicating DB_SBZS.T_SCYW to DB_SC.T_SCYW
Mapping problem with compressed key update record (target format)...
*
SB_RQ = 2001-06-11 35:00:00
SBFS_DM = 10
SBSX_DM = 0
RJ_XH = 0
ZZZLJSRY_DM = NULL
3. 如上所示SB_RQ的時間格式有問題SB_RQ = 2001-06-11 35:00:00,導致報錯ORA-01850: hour must be between 0 and 23
經檢查源表,發現該表PZ_XH = 2004010022368370的記錄確實有問題:
SQL> select to_char(PZ_XH),TO_CHAR(SB_RQ,'yyyymmdd hh:mi:ss') from DB_SBZS.T_SCYW
2 where pz_xh='2007090146478387' or pz_xh='2004010022368370';
TO_CHAR(PZ_XH) TO_CHAR(SB_RQ,'YYYYMMDDHH:MI:S
---------------------------------------- ------------------------------
2004010022368370 00000000 00:00:00
2007090146478387 20070903 12:00:00
SQL> select SB_RQ from DB_SBZS.T_SCYW where pz_xh='2007090146478387' or pz_xh='2004010022368370';
SB_RQ
-----------
2001-6-11
2007-9-3
4.解決思路:源SB_RQ = 2001-06-11 35:00:00的記錄更新為正常後,目標端應用程式即可恢復正常
start replicat RSX00028 skiptransaction ----跳過出錯記錄
delete DB_SC.T_SCYW where pz_xh='2007090146478387'; ----刪除本地記錄
insert into DB_SC.T_SCYW select * from DB_SBZS.T_SCYW@DB_LINK where pz_xh='2007090146478387'; ----重新插回記錄
REPLICAT ABENDED RSC00022 00:00:06 03:52:53
2. 經檢查discardfile檔案發現問題出在以下update語句報錯:
2011-11-10 14:29:17 WARNING OGG-00869 OCI Error ORA-01850: hour must be between 0 and 23 (status = 1850), SQL
M" = :a8,"SBSX_DM" = :a9,"RJ_XH" = :a10,"ZZZLJSRY>.
Problem replicating DB_SBZS.T_SCYW to DB_SC.T_SCYW
Mapping problem with compressed key update record (target format)...
*
SB_RQ = 2001-06-11 35:00:00
SBFS_DM = 10
SBSX_DM = 0
RJ_XH = 0
ZZZLJSRY_DM = NULL
3. 如上所示SB_RQ的時間格式有問題SB_RQ = 2001-06-11 35:00:00,導致報錯ORA-01850: hour must be between 0 and 23
經檢查源表,發現該表PZ_XH = 2004010022368370的記錄確實有問題:
SQL> select to_char(PZ_XH),TO_CHAR(SB_RQ,'yyyymmdd hh:mi:ss') from DB_SBZS.T_SCYW
2 where pz_xh='2007090146478387' or pz_xh='2004010022368370';
TO_CHAR(PZ_XH) TO_CHAR(SB_RQ,'YYYYMMDDHH:MI:S
---------------------------------------- ------------------------------
2004010022368370 00000000 00:00:00
2007090146478387 20070903 12:00:00
SQL> select SB_RQ from DB_SBZS.T_SCYW where pz_xh='2007090146478387' or pz_xh='2004010022368370';
SB_RQ
-----------
2001-6-11
2007-9-3
4.解決思路:源SB_RQ = 2001-06-11 35:00:00的記錄更新為正常後,目標端應用程式即可恢復正常
start replicat RSX00028 skiptransaction ----跳過出錯記錄
delete DB_SC.T_SCYW where pz_xh='2007090146478387'; ----刪除本地記錄
insert into DB_SC.T_SCYW select * from DB_SBZS.T_SCYW@DB_LINK where pz_xh='2007090146478387'; ----重新插回記錄
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/29468144/viewspace-1079332/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- MySQL 網路導致的複製報錯案例MySql
- OGG 表結構變化導致同步異常
- OGG相關的CPATURE導致SYSAUX表空間異常暴增處理UX
- ORACLE OGG引數修改引起佇列檔案異常導致抽取程式無法啟動Oracle佇列
- 配置OGG到MYSQL複製時登陸MYSQL報錯解決MySql
- 009-時間不同步導致Sentinel監控異常
- ogg複製程式報ORA-01438錯誤處理
- 記 Laravel Observer 導致 Redis 佇列異常LaravelServerRedis佇列
- OGG 複製程式拆分
- 容器網路防火牆狀態異常導致丟包排查記錄防火牆
- 異常程式導致大量資源佔用
- UE4 記憶體寫壞導致異常崩潰問題記錄記憶體
- mysql臨時表空間不夠導致主從複製失敗MySql
- Oracle RAC啟動因CTSS導致的異常Oracle
- oracle goldengate ddl 操作導致複製程式abended處理案例OracleGo
- 【北亞資料恢復】異常斷電導致Oracle資料庫報錯的oracle資料恢復資料恢復Oracle資料庫
- 伺服器架構導致的SEO收錄異常伺服器架構
- 時區不一致導致spring應用異常Spring
- Cancel 刪除 正在使用的臨時表空間的操作 將導致異常
- 一次線上JVM記憶體異常排查 -- 物件之間的複製JVM記憶體物件
- 當機導致slave異常分析
- Oracle不正規操作導致drop表空間drop使用者報錯ora38301(記錄,未解決)Oracle
- 360衛士阻止程式建立,導致各種異常
- 從原始碼分析JSONObject因版本差異導致toString格式異常問題原始碼JSONObject
- Oracle 資料庫不一致導致異常的恢復Oracle資料庫
- HA異常導致oracle資料庫無法啟動Oracle資料庫
- 異常連線導致的記憶體洩漏排查記憶體
- MySQL8.0的一個bug導致複製延時MySql
- ogg12 oracle to oracle 雙向DDL複製Oracle
- GDI資源洩漏導致的程式異常的解析
- ogg 併發複製程式自阻塞
- ASP.NET 執行緒導致w3wp.exe異常 而開啟VS實時偵錯程式ASP.NET執行緒
- Goldengate的複製程式出錯OGG-01296Go
- 模擬oracle rac節點異常時如何保持ogg正常執行Oracle
- CoreDNS解析異常記錄DNS
- crontab設定導致的伺服器程式異常問題伺服器
- cv::Mat轉QImage導致影像色彩異常
- 序列異常導致災備端應用異常處理一則