FATAL ERROR IN TWO-TASK SERVER: error = 12152

数据库:9206

今天一DB出现error:

*** 2009-01-13 14:47:37.622
*** SESSION ID:(120.2) 2009-01-13 14:47:37.603
FATAL ERROR IN TWO-TASK SERVER: error = 12152
*** 2009-01-13 14:47:37.622
ksedmp: internal or fatal error
Current SQL statement for this session:
SELECT CHILDID, PARENTID, MESSAGEHANDLE, CHILDCLASS, PRIORITY, ACCESSLEVEL, CREATEDATE, STATUS, ISEROTIC, ISPOLITICAL FROM TB_KONA_P
ARENTCHILD WHERE CHILDID = :1

.....


last wait for 'SQL*Net break/reset to client' blocking sess=0x0 seq=2536 wait_time=3

......

> oerr ora 12152
12152, 00000, "TNS:unable to send break message"
// *Cause: Unable to send break message. Connection probably disconnected.
// *Action: Reestablish connection. If the error is persistent, turn
// on tracing and reexecute the operation.
经过metalink查询,这是oracle一个未公布的bug:3816595。
Cause
The client application died (or dropped the connection) before the server
process could send the break/reset message back, and that prevented the server
process from exiting gracefully. This caused the server trace file to be dumped.
Solution
This issue has been reported and fixed via non-published bug:3816595
This issue is fixed in 9.2.0.8 (Server Patch Set),10.1.0.5 (Server Patch Set),10.2.0.1 (Base Release)

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/28419/viewspace-604029/,如需转载,请注明出处,否则将追究法律责任。

转载于:http://blog.itpub.net/28419/viewspace-604029/

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
这个错误是由于在执行 `kubeadm config images pull` 命令时无法从指定的镜像仓库中拉取镜像引起的。具体报错信息显示了以下内容: ``` failed to pull image "registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0": output: E0715 01:48:45.987722 1704 remote_image.go:171] "PullImage from image service failed" err="rpc error: code = Unknown desc = failed to pull and unpack image \"registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0\": failed to resolve reference \"registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0\": failed to do request: Head \"https://registry.aliyuncs.com/v2/google_containers/kube-apiserver/manifests/v1.25.0\": dial tcp: lookup registry.aliyuncs.com on 10.0.0.2:53: read udp 10.0.0.81:55655->10.0.0.2:53: i/o timeout" image="registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0" time="2023-07-15T01:48:45-04:00" level=fatal msg="pulling image: rpc error: code = Unknown desc = failed to pull and unpack image \"registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0\": failed to resolve reference \"registry.aliyuncs.com/google_containers/kube-apiserver:v1.25.0\": failed to do request: Head \"https://registry.aliyuncs.com/v2/google_containers/kube-apiserver/manifests/v1.25.0\": dial tcp: lookup registry.aliyuncs.com on 10.0.0.2:53: read udp 10.0.0.81:55655->10.0.0.2:53: i/o timeout" , error: exit status 1 ``` 错误信息中提到了以下几个关键点: 1. `failed to resolve reference`:无法解析镜像引用,可能是由于网络问题导致无法访问指定的镜像仓库。 2. `dial tcp: lookup registry.aliyuncs.com on 10.0.0.2:53: read udp 10.0.0.81:55655->10.0.0.2:53: i/o timeout`:在解析镜像仓库地址时发生了 I/O 超时的错误。 根据这些信息,我推测可能有以下原因导致了这个问题: 1. 网络连接问题:可能是由于网络连接不稳定或者存在防火墙等限制,导致无法访问指定的镜像仓库。你可以尝试检查网络连接是否正常,以及是否有任何网络限制。 2. DNS 解析问题:可能是由于 DNS 解析失败导致无法解析指定的镜像仓库地址。你可以尝试检查 DNS 配置是否正确,并且能够正常解析该镜像仓库地址。 希望这些信息能帮助到你解决问题。如果有任何进一步的疑问,请随时提问。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值