ORA-12792: Network transfer operation aborted due to TTC error 12543.

RMAN Active duplicate hung with ORA-12792: Network transfer operation aborted due to TTC error 12543

KB160250

Summary

Creation of standby using RMAN active duplicate hung with below errors seen on primary alert log :

2024-03-23T04:45:47.593662-04:00

Errors in file /u01/app/oracle/diag/rdbms/test_shk_iad/test/trace/test_ora_65670.trc:

ORA-12792: Network transfer operation aborted due to TTC error 12543.

2024-03-23T04:48:35.527422-04:00

Solution

Please follow below action plan to modify the iptables on both primary & standby and retry the active duplicate :

1.) Save iptables

sudo su -

iptables-save > /home/oracle/iptables.orig

2.) List iptables

iptables -L --line-numbers

3.) Delete following lines from below chains :

Chain INPUT (policy ACCEPT)

12 REJECT all -- anywhere anywhere reject-with icmp-host-prohibited

Chain FORWARD (policy ACCEPT)

1 REJECT all -- anywhere anywhere reject-with icmp-host-prohibited

4.) Below commands will be used for deletion :

iptables -D INPUT <number from first col from above output belonging to the reject-with icmp-host-prohibited >

iptables -D FORWARD <number from first col from above output belonging to the reject-with icmp-host-prohibited >

Example :

iptables -D INPUT 12

iptables -D FORWARD 1

4.) Verify if rules have been deleted :

iptables -L --line-numbers

5.) Retry the creation of standby.

6.) Below step to restore should be done only after standby is created.

Restore the default rules:

iptables-restore /tmp/iptables.orig

Reload and check if the previous rules are as a default

systemctl reload iptables.service

systemctl status iptables.service

Attachments :

Cause

This is known issue in DB System and this was being investigated in below mentioned bug by Development :

Bug 35470978 - ORCHESTRATIONS WHERE RMAN IS INVOLVED ARE FAILING WITH ORA-12792: NETWORK TRANSFER OPERATION ABORTED DUE TO TTC E

But bug got closed since issue was resolved with the workaround as mentioned below after which customer didn't comeback.

相关推荐
奇树谦19 小时前
《现代 Key-Value 数据库原理:从 B+Tree 到 LSM Tree》-第三篇:LMDB 深度解析二
数据库·oracle·lsm-tree
提笔了无痕19 小时前
Agent 上下文管理详解、Context设计与构建
数据库·oracle·agent·context
沉下去,苦磨练!19 小时前
Human‑in‑the‑Loop
数据库·oracle
小黑技术栈20 小时前
web前端基础到入门——14day
前端·数据库·oracle
todoitbo2 天前
把发票台账接进 Codex:KingbaseES MCP 的一次只读风险排查实践
数据库·oracle·codex·kingbasees·mcp
暗暗别做白日梦2 天前
CompletableFuture 并发统计
网络·数据库·oracle
TDengine (老段)2 天前
TDengine 认证与权限 — 用户、角色、RBAC
大数据·数据库·物联网·oracle·时序数据库·tdengine·涛思数据
晴天¥2 天前
记一次Oracle集群归档日志爆满之后如何处理(涉及ASM磁盘的增添。有坑必踩)
数据库·oracle
Hoxy.R2 天前
记录一次Oracle 19c RAC iSCSI会话反复重连:comm error (1020) 原因定位与解决
数据库·oracle
sky_8106132 天前
Oracle ERP 各模块业务管理功能及底层表说明
数据库·oracle