oracle官方文档的解释 ORA-00600: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string] Cause: This is the generic internal error number for Oracle program exceptions. This indicates that a process has encountered an exceptional condition. Action: Report as a bug - the first argument is the internal error number
你看看这篇文章： http://wayne.72pines.com/page/2/ora-00600 [1236] & ora-00600 [16365] & ora-04031 2007年11月2号问题描述：开发人员报告数据库时快时慢，下午应用报错，系统死掉，现场重启库。分析：alert日志：Thu Nov 01 08:39:12 2007 Errors in file e:\oracle\admin\gbbcrm\udump\gbbcrm_s000_3688.trc: ORA-00600: 内部错误代码，参数: [1236], [], [], [], [], [], [], []Thu Nov 01 08:40:00 2007 Errors in file e:\oracle\admin\gbbcrm\udump\gbbcrm_s000_3688.trc: ORA-00600: 内部错误代码，参数: [1236], [], [], [], [], [], [], []Errors in file e:\oracle\admin\gbbcrm\udump\gbbcrm_s002_4232.trc: ORA-00600: 内部错误代码，参数: [16365], [0x1D6F1A30], [0], [4], [], [], [], []Fri Nov 02 13:41:29 2007 Error 600 trapped in 2PC on transaction 20.0.2. Cleaning up. Error stack returned to user: ORA-00600: 内部错误代码，参数: [16365], [0x1D6F1A30], [0], [4], [], [], [], [] 应用报错：ORA-04031: 无法分配 8132 字节的共享内存 (”large pool”，”unknown object”，”cursor work he”，”qesaQBInit:buffer”)metalink中用600那个工具搜索了一下，找到两篇相关文档：138354.1106607.1说的基本都是关于共享服务器连接模式下的错误，再看看应用抛的04031，问题确认基本出在应用连数据库的模式问题上了，用lsnrct service确认，果然共享连接占大比例，目前把应用修改成专用的再观察一段。
ORA-600 [1236], ORA-31085 Dropping an User [ID 416431.1] --------------------------------------------------------------------------------
Modified 22-FEB-2007 Type PROBLEM Status PUBLISHED In this Document Symptoms Cause Solution References-------------------------------------------------------------------------------- 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: 9.2 - 10g This problem can occur on any platform.Symptoms Drop user fails with: ORA-600[4046] ORA-31085: schema "XDh1jUheYAR5PgNAgAILJCxg==" already registered Trace file generated by the ORA-600[1236] shows this stack: ktcrab qm_init_first_db_us e_pass1 qm_init_sga_pass1 qm_init_uga qmtsDropUser Cause Based on the ORA-31085: schema "XDh1jUheYAR5PgNAgAILJCxg==" already registeredthe user is registered with XDB.SolutionUsing Note 263438.1 you will have to get the user unregistered and then try to drop it.This could be also because of an improperly installed XDB environment.If you don't use XDB you can try to : - deinstall XDB - drop user cascadeReferences BUG:4698445 - WHEN DROPPING THE SYSMAN USER, AN INTERNAL ERROR OCCURS ORA-600 NOTE:263438.1 - How to Delete a Registered XML Schema Owned by Another User NOTE:243554.1 - How to Deinstall and Reinstall XML Database (XDB)-------------------------------------------------------------------------------- Related-------------------------------------------------------------------------------- Products --------------------------------------------------------------------------------Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition Keywords -------------------------------------------------------------------------------- ORA-31085; ORA-600[1236] Errors -------------------------------------------------------------------------------- ORA-31085; ORA-600[1236] Back to topRate this document Article Rating Rate this document Excellent Good Poor
Did this document help you? Yes No Just browsing
How easy was it to find this document? Very easy Somewhat easy Not easy Comments Provide some feedback
Cancel
How to Delete a Registered XML Schema Owned by Another User [ID 263438.1] --------------------------------------------------------------------------------
Modified 04-FEB-2010 Type BULLETIN Status PUBLISHED Checked for relevance on 05-Feb-2010PURPOSE -------This article explains how to delete a registered XML schema owned by another database user. SCOPE & APPLICATION -------------------XML Developers and DBA's. How to Delete a Registered XML Schema Owned by Another User -----------------------------------------------------------
Following working example provides a steps by step test as well as an explanation for deleting a schema that is owned by another user:1. Create 2 users:SQL> create user xml1 identified by xml1;
User created.
SQL> create user xml2 identified by xml2;
User created.2. Grant permissions:
SQL> grant connect, resource to xml1;
Grant succeeded.
SQL> grant connect, resource, dba to xml2;
Grant succeeded.3. Connect user 2 and register a schema:SQL> conn xml2/xml2 Connected.
SQL> DECLARE acctschema VARCHAR2(2000) := ''; BEGIN DBMS_XMLSCHEMA.RegisterSchema('http://otn.oracle.com/account.xsd',acctschema, TRUE, TRUE, FALSE, TRUE, FALSE, 'XML1' ); END; /PL/SQL procedure successfully completed.NOTE: In the register schema syntax, XML1 is specified as the owner of the schema.3. User XML2 (who has DBA privileges) has registered a schema as XML1. How can user XML2 delete this XML Schema owned by the user XML1? The following will fail with errors:SQL> conn xml2/xml2 Connected. SQL> begin dbms_xmlschema.deleteSchema('http://otn.oracle.com/account.xsd',dbms_xmlschema.DELETE_CASCADE_FORCE); end; / ORA-31000: Resource 'http://otn.oracle.com/account.xsd' is not an XDB schema document ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 0 ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 1004. To delete the schema, the fully qualified name will need to be used for the deleteSchema schema name argument. The fully qualified form of a schema URL has a well-known prefix and the user name within it. For example, if user XML1 owns the schema http://otn.oracle.com/account.xsd, The fully qualified name would be: "http://xmlns.oracle.com/xdb/schemas/XML1/otn.oracle.com/account.xsd The following sql will delete the schema: SQL> begin dbms_xmlschema.deleteSchema('http://xmlns.oracle.com/xdb/schemas/XML1/otn.oracle.com/account.xsd',dbms_xmlschema.DELETE_CASCADE_FORCE); end; /
PL/SQL procedure successfully completed.RELATED DOCUMENTS ----------------- Oracle9i XML Database Developer's Guide - Oracle XML DB Release 2 (9.2) Related-------------------------------------------------------------------------------- Products --------------------------------------------------------------------------------Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition Keywords -------------------------------------------------------------------------------- XDB Errors -------------------------------------------------------------------------------- ORA-31000 Back to top
ORA-00600: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
Cause: This is the generic internal error number for Oracle program exceptions. This indicates that a process has encountered an exceptional condition.
Action: Report as a bug - the first argument is the internal error number
http://wayne.72pines.com/page/2/ora-00600 [1236] & ora-00600 [16365] & ora-04031
2007年11月2号问题描述：开发人员报告数据库时快时慢，下午应用报错，系统死掉，现场重启库。分析：alert日志：Thu Nov 01 08:39:12 2007
Errors in file e:\oracle\admin\gbbcrm\udump\gbbcrm_s000_3688.trc:
ORA-00600: 内部错误代码，参数: [1236], [], [], [], [], [], [], []Thu Nov 01 08:40:00 2007
Errors in file e:\oracle\admin\gbbcrm\udump\gbbcrm_s000_3688.trc:
ORA-00600: 内部错误代码，参数: [1236], [], [], [], [], [], [], []Errors in file e:\oracle\admin\gbbcrm\udump\gbbcrm_s002_4232.trc:
ORA-00600: 内部错误代码，参数: [16365], [0x1D6F1A30], [0], [4], [], [], [], []Fri Nov 02 13:41:29 2007
Error 600 trapped in 2PC on transaction 20.0.2. Cleaning up.
Error stack returned to user:
ORA-00600: 内部错误代码，参数: [16365], [0x1D6F1A30], [0], [4], [], [], [], []
应用报错：ORA-04031: 无法分配 8132 字节的共享内存 (”large pool”，”unknown object”，”cursor work he”，”qesaQBInit:buffer”)metalink中用600那个工具搜索了一下，找到两篇相关文档：138354.1106607.1说的基本都是关于共享服务器连接模式下的错误，再看看应用抛的04031，问题确认基本出在应用连数据库的模式问题上了，用lsnrct service确认，果然共享连接占大比例，目前把应用修改成专用的再观察一段。
数据库什么版本的？ 有升级过没？楼主用什么用户来删除用户的？按下面的方法试试：1)SQL> shutdown immediate
2)SQL> startup migrate
3)SQL> spool patch.log
4)SQL> @?/rdbms/admin/catpatch
5)SQL> spool off
------------------------------------------------------------------------------
Blog： http://blog.csdn.net/tianlesoftware
网上资源： http://tianlesoftware.download.csdn.net
相关视频：http://blog.csdn.net/tianlesoftware/archive/2009/11/27/4886500.aspx
DBA1 群：62697716(满); DBA2 群：62697977
数据库是Oracle92,没有升级过！
sys!
Modified 22-FEB-2007 Type PROBLEM Status PUBLISHED In this Document
Symptoms
Cause
Solution
References--------------------------------------------------------------------------------
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: 9.2 - 10g
This problem can occur on any platform.Symptoms
Drop user fails with:
ORA-600[4046]
ORA-31085: schema "XDh1jUheYAR5PgNAgAILJCxg==" already registered Trace file generated by the ORA-600[1236] shows this stack: ktcrab qm_init_first_db_us e_pass1 qm_init_sga_pass1 qm_init_uga qmtsDropUser Cause
Based on the ORA-31085: schema "XDh1jUheYAR5PgNAgAILJCxg==" already registeredthe user is registered with XDB.SolutionUsing Note 263438.1 you will have to get the user unregistered and then try to drop it.This could be also because of an improperly installed XDB environment.If you don't use XDB you can try to :
- deinstall XDB
- drop user cascadeReferences
BUG:4698445 - WHEN DROPPING THE SYSMAN USER, AN INTERNAL ERROR OCCURS ORA-600
NOTE:263438.1 - How to Delete a Registered XML Schema Owned by Another User
NOTE:243554.1 - How to Deinstall and Reinstall XML Database (XDB)--------------------------------------------------------------------------------
Related--------------------------------------------------------------------------------
Products
--------------------------------------------------------------------------------Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition
Keywords
--------------------------------------------------------------------------------
ORA-31085; ORA-600[1236]
Errors
--------------------------------------------------------------------------------
ORA-31085; ORA-600[1236]
Back to topRate this document Article Rating
Rate this document
Excellent
Good
Poor
Did this document help you?
Yes
No
Just browsing
How easy was it to find this document?
Very easy
Somewhat easy
Not easy
Comments
Provide some feedback
Cancel
Modified 04-FEB-2010 Type BULLETIN Status PUBLISHED
Checked for relevance on 05-Feb-2010PURPOSE
-------This article explains how to delete a registered XML schema owned by another database user.
SCOPE & APPLICATION
-------------------XML Developers and DBA's.
How to Delete a Registered XML Schema Owned by Another User
-----------------------------------------------------------
Following working example provides a steps by step test as well as an explanation for deleting a schema that is owned by another user:1. Create 2 users:SQL> create user xml1 identified by xml1;
User created.
SQL> create user xml2 identified by xml2;
User created.2. Grant permissions:
SQL> grant connect, resource to xml1;
Grant succeeded.
SQL> grant connect, resource, dba to xml2;
Grant succeeded.3. Connect user 2 and register a schema:SQL> conn xml2/xml2
Connected.
SQL> DECLARE
acctschema VARCHAR2(2000) := '';
BEGIN
DBMS_XMLSCHEMA.RegisterSchema('http://otn.oracle.com/account.xsd',acctschema,
TRUE, TRUE, FALSE, TRUE, FALSE, 'XML1' );
END;
/PL/SQL procedure successfully completed.NOTE: In the register schema syntax, XML1 is specified as the owner of the schema.3. User XML2 (who has DBA privileges) has registered a schema as XML1. How can user XML2 delete this XML Schema owned by the user XML1?
The following will fail with errors:SQL> conn xml2/xml2
Connected.
SQL> begin
dbms_xmlschema.deleteSchema('http://otn.oracle.com/account.xsd',dbms_xmlschema.DELETE_CASCADE_FORCE);
end;
/ ORA-31000: Resource 'http://otn.oracle.com/account.xsd' is not an XDB schema document
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 0
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 1004. To delete the schema, the fully qualified name will need to be used for the deleteSchema schema name argument.
The fully qualified form of a schema URL has a well-known prefix and the user name within it. For example, if user XML1 owns the schema http://otn.oracle.com/account.xsd, The fully qualified name would be: "http://xmlns.oracle.com/xdb/schemas/XML1/otn.oracle.com/account.xsd
The following sql will delete the schema: SQL> begin
dbms_xmlschema.deleteSchema('http://xmlns.oracle.com/xdb/schemas/XML1/otn.oracle.com/account.xsd',dbms_xmlschema.DELETE_CASCADE_FORCE);
end;
/
PL/SQL procedure successfully completed.RELATED DOCUMENTS
----------------- Oracle9i XML Database Developer's Guide - Oracle XML DB
Release 2 (9.2)
Related--------------------------------------------------------------------------------
Products
--------------------------------------------------------------------------------Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition
Keywords
--------------------------------------------------------------------------------
XDB
Errors
--------------------------------------------------------------------------------
ORA-31000
Back to top