ITPub博客

首页 > 数据库 > Oracle > Ksedmp: psdgbt: bind csid (1) does not match session csid (871)

Ksedmp: psdgbt: bind csid (1) does not match session csid (871)

原创 Oracle 作者:bluesshadow 时间:2012-11-05 16:07:59 0 删除 编辑
数据库重启在agent之前的问题


Ksedmp: psdgbt: bind csid (1) does not match session csid (871)

最近数据库一个实例发生故障,数据库挂起,无法连接,但在另一个节点看到状态是打开的,查看本机发现是ORACLE软件目录的lv空间占满,查看告警日志发现是一个用户跟踪日志不停报错,导致跟踪文件增长过大,直到把空间占满导致数据库无法运行,后来上oracle网站查看了下,发出原因是oracle agent所引起,因为数据库或者监听在agent启动之后才启动起来,导致这个故障,解决的办法:先启动数据库实例和监听,然后再启动agent,或者将agent停掉,等数据库和监听启动以后,再启动agent.

附上oracle文档:ID 956222.1

"Ksedmp: psdgbt: bind csid (1) does not match session csid (871) psdgbt: session charset is UTF8 [ID 956222.1]

In this Document


Symptoms

 


Cause

 


Solution


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:

Oracle Server - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.
***Checked for relevance on 17-Jul-2012***

Symptoms

On 10.2.0.1.0 in Production:

the following error occurs:

ERROR
"ksedmp: internal or fatal Error" found in trace file

psdgbt: bind csid (1) does not match session csid (871)
psdgbt: session charset is UTF8

Cause

This is most probably caused by the listener and database not being started yet when the EM agent is started which picks up a wrong character set.

You can check that the issue is happening from the EM agent from trace files, e.g. emagent.trc showing:

PLS-00553: character set name is not recognized

The issue is not always occurring so it might only happen is this case.

Solution

Make sure to start up the database and listener before the EM agent.

 

Normal 0 false 7.8 磅 0 2 false false false EN-US ZH-CN X-NONE

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

请登录后发表评论 登录
全部评论

注册时间:2010-09-27

  • 博文量
    34
  • 访问量
    139712