ora-600[12333]错误小结及跟踪方法
来源:互联网 发布:计算机专业书推荐 知乎 编辑:程序博客网 时间:2024/05/20 18:45
该错误,是当服务器接收到无法识别的网络代码或请求时引起Oracle发出的告警 ,主要原因来自于网络,
与Oracle 本身没有关系。
如果该错误持续出现,建议用以下代码进行跟踪,有可能是病毒引发的:
===========================================
create table
SYSTEM.login_info
( logindatetime date,
LogoffDateTime Date,
LoggedUser Varchar2(30),
SESSIONID Number,
TERMINAL varchar2(20),
ip varchar2(16),
PROGRAM varchar2(20)
);
--------------------------------------------------------------------
CREATE OR REPLACE TRIGGER logoff_audit Before LOGOFF ON DATABASE
BEGIN
insert into system.login_info
select
'',sysdate,user,sys_context('USERENV','SESSIONID'),sys_context('USERENV'
,'TERMINAL'),utl_inaddr.get_host_address, program from v$session where logon_time = (select
logindatetime from SYSTEM.login_info where SESSIONID=
sys_context('USERENV','SESSIONID'));
END;
---------------------------------------------------------------------
CREATE OR REPLACE TRIGGER logon_audit AFTER LOGON ON DATABASE
BEGIN
insert into system.login_info
select sysdate,null,user,sys_context('USERENV','SESSIONID'),sys_context(
'USERENV','TERMINAL'),utl_inaddr.get_host_address,program from v$session;
END;
==============================================================
其他可能原因:
Typically the ORA-600 [12333] itself is not the problem,
It may be a chance of the underlying network problems
This is usually a client side related issue and is not normally related to server. It is a communications issue and not related to the version of the RDBMS. Thats why you do have this errors intermittently only.
Most occurances of ORA-600 [12333] just means that something has
gone wrong in the communication between the client and the server processes. Often, this could be the result of an abnormal condition (a process is inadvertently killed, or a database shuts down)
The error indicates a protocol communications mismatch
<Note:112660.1>
PURPOSE
-------
This paper describes one known reason of frequent occurence of ORA-600 [12333]
errors.
NOTE: There may exist many other issues however.
SCOPE & APPLICATION
-------------------
Support Analysts and DBAs.
ORA-600 [12333] in case of termination of user sessions
-------------------------------------------------------
ORA-600 [12333] may occur in case of abnormal termination of user
sessions, eg. shutdown immediate, forced disconnections etc.
Frequent ORA-600 [12333] in case of using resource limit
--------------------------------------------------------
Using user profiles and resource_limit=true may cause frequent ORA-600 [12333]occurence. We may also see many SNIPPED session in V$SESSION. For those ones resources are not freed until any server related action is taken at the client side. It seems that ORA-600 [12333] appears while sending ORA-1012 or ORA-2396 messages to the client process.
If we really have to use user profiles to enforce resource limit policies(especially idle time) we'd better proactively remove such sessions.
For now, the only found way preventing from ORA-600 [12333] occurence
caused by resource_limit issue is killing processes related to SNIPPED sessions at OS level. This implies it is applicable only to the DEDICATED server processes. Killing shadow processes for SNIPPED sessions is explained in <Note:96170.1>.
NOTE: Killing shadow processes only decreases the likehood of ORA-600 [12333] occurence. It is a workaround.
Couple of suggestion
=======================
1)Check the network errors, their should be any errors or protocol mismatch
2)Check the NLS settings on client as well as server side settings
ORA_NLS (ORA_NLS32, ORA_NLS33) Environment Variables.
Article-ID: <Note:77442.1>
Title: ORA_NLS (ORA_NLS32, ORA_NLS33) Environment Variables
3)NO users should disconnect abnormally.
与Oracle 本身没有关系。
如果该错误持续出现,建议用以下代码进行跟踪,有可能是病毒引发的:
===========================================
create table
SYSTEM.login_info
( logindatetime date,
LogoffDateTime Date,
LoggedUser Varchar2(30),
SESSIONID Number,
TERMINAL varchar2(20),
ip varchar2(16),
PROGRAM varchar2(20)
);
--------------------------------------------------------------------
CREATE OR REPLACE TRIGGER logoff_audit Before LOGOFF ON DATABASE
BEGIN
insert into system.login_info
select
'',sysdate,user,sys_context('USERENV','SESSIONID'),sys_context('USERENV'
,'TERMINAL'),utl_inaddr.get_host_address, program from v$session where logon_time = (select
logindatetime from SYSTEM.login_info where SESSIONID=
sys_context('USERENV','SESSIONID'));
END;
---------------------------------------------------------------------
CREATE OR REPLACE TRIGGER logon_audit AFTER LOGON ON DATABASE
BEGIN
insert into system.login_info
select sysdate,null,user,sys_context('USERENV','SESSIONID'),sys_context(
'USERENV','TERMINAL'),utl_inaddr.get_host_address,program from v$session;
END;
==============================================================
其他可能原因:
Typically the ORA-600 [12333] itself is not the problem,
It may be a chance of the underlying network problems
This is usually a client side related issue and is not normally related to server. It is a communications issue and not related to the version of the RDBMS. Thats why you do have this errors intermittently only.
Most occurances of ORA-600 [12333] just means that something has
gone wrong in the communication between the client and the server processes. Often, this could be the result of an abnormal condition (a process is inadvertently killed, or a database shuts down)
The error indicates a protocol communications mismatch
<Note:112660.1>
PURPOSE
-------
This paper describes one known reason of frequent occurence of ORA-600 [12333]
errors.
NOTE: There may exist many other issues however.
SCOPE & APPLICATION
-------------------
Support Analysts and DBAs.
ORA-600 [12333] in case of termination of user sessions
-------------------------------------------------------
ORA-600 [12333] may occur in case of abnormal termination of user
sessions, eg. shutdown immediate, forced disconnections etc.
Frequent ORA-600 [12333] in case of using resource limit
--------------------------------------------------------
Using user profiles and resource_limit=true may cause frequent ORA-600 [12333]occurence. We may also see many SNIPPED session in V$SESSION. For those ones resources are not freed until any server related action is taken at the client side. It seems that ORA-600 [12333] appears while sending ORA-1012 or ORA-2396 messages to the client process.
If we really have to use user profiles to enforce resource limit policies(especially idle time) we'd better proactively remove such sessions.
For now, the only found way preventing from ORA-600 [12333] occurence
caused by resource_limit issue is killing processes related to SNIPPED sessions at OS level. This implies it is applicable only to the DEDICATED server processes. Killing shadow processes for SNIPPED sessions is explained in <Note:96170.1>.
NOTE: Killing shadow processes only decreases the likehood of ORA-600 [12333] occurence. It is a workaround.
Couple of suggestion
=======================
1)Check the network errors, their should be any errors or protocol mismatch
2)Check the NLS settings on client as well as server side settings
ORA_NLS (ORA_NLS32, ORA_NLS33) Environment Variables.
Article-ID: <Note:77442.1>
Title: ORA_NLS (ORA_NLS32, ORA_NLS33) Environment Variables
3)NO users should disconnect abnormally.
- ora-600[12333]错误小结及跟踪方法
- ORA-14452错误及解決方法
- ORA-14452错误及解決方法
- 目标跟踪理论方法小结
- 目标跟踪理论方法小结 .
- 目标跟踪理论方法小结
- 目标跟踪理论方法小结
- 目标跟踪理论方法小结
- 目标跟踪理论方法小结
- 使用errorstack跟踪ORA-01438错误
- ORA-00020错误处理及修改process的方法
- oracle数据库恢复方法及ORA-01991错误的解决
- ora-01178及ORA-01511错误
- ora-12514错误及解决
- ORA-00911错误及解决方法
- ora-02069 错误处理方法
- 使用ERRORSTACK进行错误跟踪及诊断
- 使用ErrorStack进行错误跟踪及诊断
- 三国演义清规诫律:不可娶美貌女子
- 为对话框程序加上Accelerator(快捷键)
- 在Tomcat下JSP、Servlet和JavaBean环境的配置(转)
- 删除指定目录下的所有文件的java类
- [GDI+]如何将一个彩色图像转换成黑白图像
- ora-600[12333]错误小结及跟踪方法
- [GDI+] ColorMatrix 彩色矩阵
- 缥缈带给我们什么!
- 使用MFC Extension Dll 封装界面类的内部实现
- oracle+jsp中blob类型存储大文本问题解决方法
- 有一天,爸妈会变老(转)
- 如何检测系统是否已经运行了相同的程序。
- Rawether Does NOT Allow Multiple Applications To Receive The Same Packet
- QQ游戏外挂制作教程 (对对碰)