- 浏览: 80053 次
- 性别:
- 来自: 北京
最新评论
-
streamsong:
王雨尘 写道
的确是说索引是排序的,我漏掉啦
我们为什么要用索引,用索引为什么比不用索引快 -
heerwa:
...
我们为什么要用索引,用索引为什么比不用索引快 -
liulanghan110:
那么用索引为什么会提高性能呢?因为索引(以B树索引为例)是树状 ...
我们为什么要用索引,用索引为什么比不用索引快 -
王雨尘:
我们为什么要用索引,用索引为什么比不用索引快 -
pangpang514:
居然和强哥合影过。。。。佩服!
我们为什么要用索引,用索引为什么比不用索引快
此文转载 http://space.itpub.net/13558130 mydbalife的文章
ora-600是Oracle对于一些内部错误的一个统一的错误号(类似的还有ora-7445)。要判断ora-600错误具体的类型,一般要根据其第一个参数来区分。一个ora-600的例子如下:
ORA-00600: internal error code, arguments: [15700], [3], [0x1DDE1AAB0], [], [], [], [], []
其中15700代表这个错误的具体类型,这是和并行查询相关的一个内部错误,后面的几个参数则是该错误的一些具体参数,不同类型的错误,参数的意义也不尽相同。
ora-600一共有两大类,一类的错误类型以数字标识,另外一类则以字符串标识。数字表示不同的内核层,而字符串则是具体的函数或者模块名。在Metalink的Doc ID: 175982.1中,oracle列举了这两类错误的详细信息,转录在这里以供需要是查询:
数字类型的Ora-600
1 | Service Layer |
The service layer has within it a variety of service related components which are associated with in memory related activities in the SGA such as, for example : the management of Enqueues, System Parameters, System state objects (these objects track the use of structures in the SGA by Oracle server processes), etc.. In the main, this layer provides support to allow process communication and provides support for locking and the management of structures to support multiple user processes connecting and interacting within the SGA.
Note : vos – Virtual Operating System provides features to support the functionality above. As the name suggests it provides base functionality in much the same way as is provided by an Operating System.
|
|||||||||||||||||||||||||||||||||||||||||||||
2000 | Cache Layer |
Where errors are generated in this area, it is advisable to check whether the error is repeatable and whether the error is perhaps associated with recovery or undo type operations; where this is the case and the error is repeatable, this may suggest some kind of hardware or physical issue with a data file, control file or log file. The Cache layer is responsible for making the changes to the underlying files and well as managing the related memory structures in the SGA.
Note :rcvindicates recovery. It is important to remember that the Oracle cache layer is effectively going through the same code paths as used by the recovery mechanism.
It is important to consider when the error occurred and the context in which the error was generated. If the error does not reproduce, it may be an in memory issue. |
|||||||||||||||||||||||||||||||||||||||||||||
4000 | Transaction Layer |
Primarily the transaction layer is involved with maintaining structures associated with the management of transactions. As with the cache layer , problems encountered in this layer may indicate some kind of issue at a physical level. Thus it is important to try and repeat the same steps to see if the problem recurs.
It is important to try and determine what the object involved in any reproducible problem is. Then |
|||||||||||||||||||||||||||||||||||||||||||||
6000 | Data Layer |
The data layer is responsible for maintaining and managing the data in the database tables and indexes. Issues in this area may indicate some kind of physical issue at the object level and therefore, it is important to try and isolate the object and then perform. an anlayze on the object to validate its structure.
Again, it is important to try and determine what the object involved in any reproducible problem is. |
|||||||||||||||||||||||||||||||||||||||||||||
12000 | User/Oracle Interface & SQL Layer Components |
This layer governs the user interface with the Oracle server. Problems generated by this layer usually indicate : some kind of presentation or format error in the data received by the server, i.e. the client may have sent incomplete information; or there is some kind of issue which indicates that the data is received out of sequence
You should try and repeat the issue and with the use of sql trace , try and isolate where exactly the issue may be occurring within the application. |
|||||||||||||||||||||||||||||||||||||||||||||
14000 | System Dependent Component internal error values |
This layer manages interaction with the OS. Effectively it acts as the glue which allows the Oracle server to interact with the OS. The types of operation which this layer manages are indicated as follows.
|
|||||||||||||||||||||||||||||||||||||||||||||
15000 |
security/dac, security/logon security/ldap |
local user access validation; challenge / response activity for remote access validation; auditing operation; any activities associated with granting and revoking of privileges; validation of password with external password file |
|||||||||||||||||||||||||||||||||||||||||||||
15100 | dict/sqlddl | this component manages operations associated with creating, compiling (altering), renaming, invalidating, and dropping procedures, functions, and packages. | |||||||||||||||||||||||||||||||||||||||||||||
15160 | optim/cbo | cost based optimizer layer is used to determine optimal path to the data based on statistical information available on the relevant tables and indexes. | |||||||||||||||||||||||||||||||||||||||||||||
15190 | optim/cbo | cost based optimizer layer. Used in the generation of a new index to determine how the index should be created. Should it be constructed from the table data or from another index. | |||||||||||||||||||||||||||||||||||||||||||||
15200 | dict/shrdcurs | used to in creating sharable context area associated with shared cursors | |||||||||||||||||||||||||||||||||||||||||||||
15230 | dict/sqlddl | manages the compilation of triggers | |||||||||||||||||||||||||||||||||||||||||||||
15260 |
dict/dictlkup dict/libcache |
dictionary lookup and library cache access | |||||||||||||||||||||||||||||||||||||||||||||
15400 | server/drv | manages alter system and alter session operations | |||||||||||||||||||||||||||||||||||||||||||||
15410 | progint/if | manages compilation of pl/sql packages and procedures | |||||||||||||||||||||||||||||||||||||||||||||
15500 | dict/dictlkup | performs dictionary lookup to ensure semantics are correct | |||||||||||||||||||||||||||||||||||||||||||||
15550 |
sqlexec/execsvc sqlexec/rowsrc |
hash join execution management; parallel row source management |
|||||||||||||||||||||||||||||||||||||||||||||
15600 | sqlexec/pq | component provides support for Parallel Query operation | |||||||||||||||||||||||||||||||||||||||||||||
15620 | repl/snapshots | manages the creation of snapshot or materialized views as well as related snapshot / MV operations | |||||||||||||||||||||||||||||||||||||||||||||
15640 | repl/defrdrpc | layer containing various functions for examining the deferred transaction queue and retrieving information | |||||||||||||||||||||||||||||||||||||||||||||
15660 | jobqs/jobq | manages the operation of the Job queue background processes | |||||||||||||||||||||||||||||||||||||||||||||
15670 | sqlexec/pq | component provides support for Parallel Query operation | |||||||||||||||||||||||||||||||||||||||||||||
15700 | sqlexec/pq | component provides support for Parallel Query operation; specifically mechanism for starting up and shutting down query slaves | |||||||||||||||||||||||||||||||||||||||||||||
15800 | sqlexec/pq | component provides support for Parallel Query operation | |||||||||||||||||||||||||||||||||||||||||||||
15810 | sqlexec/pq | component provides support for Parallel Query operation; specifically functions for creating mechanisms through which Query co-ordinator can communicate with PQ slaves; | |||||||||||||||||||||||||||||||||||||||||||||
15820 | sqlexec/pq | component provides support for Parallel Query operation | |||||||||||||||||||||||||||||||||||||||||||||
15850 | sqlexec/execsvc | component provides support for the execution of SQL statements | |||||||||||||||||||||||||||||||||||||||||||||
15860 | sqlexec/pq | component provides support for Parallel Query operation | |||||||||||||||||||||||||||||||||||||||||||||
16000 | loader | sql Loader direct load operation; | |||||||||||||||||||||||||||||||||||||||||||||
16150 | loader | this layer is used for ‘C’ level call outs to direct loader operation; | |||||||||||||||||||||||||||||||||||||||||||||
16200 | dict/libcache | this is part of library Cache operation. Amongst other things it manages the dependency of SQL objects and tracks who is permitted to access these objects; | |||||||||||||||||||||||||||||||||||||||||||||
16230 | dict/libcache | this component is responsible for managing access to remote objects as part of library Cache operation; | |||||||||||||||||||||||||||||||||||||||||||||
16300 | mts/mts | this component relates to MTS (Multi Threaded Server) operation | |||||||||||||||||||||||||||||||||||||||||||||
16400 | dict/sqlddl | this layer contains functionality which allows tables to be loaded / truncated and their definitions to be modified. This is part of dictionary operation; | |||||||||||||||||||||||||||||||||||||||||||||
16450 | dict/libcache | this layer layer provides support for multi-instance access to the library cache; this functionality is applicable therefore to OPS environments; | |||||||||||||||||||||||||||||||||||||||||||||
16500 | dict/rowcache | this layer provides support to load / cache Oracle’s dictionary in memory in the library cache; | |||||||||||||||||||||||||||||||||||||||||||||
16550 | sqlexec/fixedtab | this component maps data structures maintained in the Oracle code to fixed tables such that they can be queried using the SQL layer; | |||||||||||||||||||||||||||||||||||||||||||||
16600 | dict/libcache | this layer performs management of data structures within the library cache; | |||||||||||||||||||||||||||||||||||||||||||||
16651 | dict/libcache | this layer performs management of dictionary related information within library Cache; | |||||||||||||||||||||||||||||||||||||||||||||
16701 | dict/libcache | this layer provides library Cache support to support database creation and forms part of the bootstrap process; | |||||||||||||||||||||||||||||||||||||||||||||
17000 | dict/libcache | this is the main library Cache manager. This Layer maintains the in memory representation of cached sql statements together will all the necessary support that this demands; | |||||||||||||||||||||||||||||||||||||||||||||
17090 | generic/vos | this layer implementations error management operations: signalling errors, catching errors, recovering from errors, setting error frames, etc.; | |||||||||||||||||||||||||||||||||||||||||||||
17100 | generic/vos | Heap manager. The Heap manager manages the storage of internal data in an orderly and consistent manner. There can be many heaps serving various purposes; and heaps within heaps. Common examples are the SGA heap, UGA heap and the PGA heap. Within a Heap there are consistency markers which aim to ensure that the Heap is always in a consistent state. Heaps are use extensively and are in memory structures – not on disk. |
|||||||||||||||||||||||||||||||||||||||||||||
17200 | dict/libcache | this component deals with loading remote library objects into the local library cache with information from the remote database. | |||||||||||||||||||||||||||||||||||||||||||||
17250 | dict/libcache | more library cache errors ; functionality for handling pipe operation associated with dbms_pipe | |||||||||||||||||||||||||||||||||||||||||||||
17270 | dict/instmgmt | this component manages instantiations of procedures, functions, packages, and cursors in a session. This provides a means to keep track of what has been loaded in the event of process death; |
|||||||||||||||||||||||||||||||||||||||||||||
17300 | generic/vos | manages certain types of memory allocation structure. This functionality is an extension of the Heap manager. | |||||||||||||||||||||||||||||||||||||||||||||
17500 | generic/vos | relates to various I/O operations. These relate to async i/o operation, direct i/o operation and the management of writing buffers from the buffer cache by potentially a number of database writer processes; | |||||||||||||||||||||||||||||||||||||||||||||
17625 | dict/libcache | additional library Cache supporting functions | |||||||||||||||||||||||||||||||||||||||||||||
17990 | plsql | plsql ’standard’ package related issues | |||||||||||||||||||||||||||||||||||||||||||||
18000 | txn/lcltx | transaction and savepoint management operations | |||||||||||||||||||||||||||||||||||||||||||||
19000 | optim/cbo | cost based optimizer related operations | |||||||||||||||||||||||||||||||||||||||||||||
20000 | ram/index | bitmap index and index related errors. | |||||||||||||||||||||||||||||||||||||||||||||
20400 | ram/partnmap | operations on partition related objects | |||||||||||||||||||||||||||||||||||||||||||||
20500 | server/rcv | server recovery related operation | |||||||||||||||||||||||||||||||||||||||||||||
21000 |
repl/defrdrpc, repl/snapshot, repl/trigger |
replication related features | |||||||||||||||||||||||||||||||||||||||||||||
23000 | oltp/qs | AQ related errors. | |||||||||||||||||||||||||||||||||||||||||||||
24000 | dict/libcache | operations associated with managing stored outlines | |||||||||||||||||||||||||||||||||||||||||||||
25000 | server/rcv | tablespace management operations |
发表评论
-
将博客搬至CSDN
2013-12-06 15:49 56将博客搬至CSDN -
博客地址更换通知
2012-09-29 09:23 605自2011年8月,博客使用新地址www.dbdream.org ... -
如何追踪其他SESSION会话信息
2012-02-21 20:35 1293今天测试说在加载条目数据、校验数据和质检数据的时候很慢, ... -
SHM不足导致导致数据库宕机
2012-02-21 20:17 1248今天早上到办公室,开发说测试环境应用程序挂掉,看日志说是连接不 ... -
PCTFREE和PCTUSED及将LOB存到行外
2012-02-17 11:14 1443今天的ADDM报告建议重建存放图片的表并增大PCTFREE,这 ... -
SGA_TARGET大于SGA_MAX_SIZE的真实案例
2012-02-17 11:05 1359今天在给库户数据库健康检查的时候,发现个很奇怪的问题,S ... -
利用闪回、logmnr找回误删除的数据
2011-10-25 23:54 1258朋友遇到了非常经典的ORACLE事故——误删除,开发人员告诉他 ... -
ORACLE随机取数据
2011-10-25 23:53 921目前负责的这个数字化项目,需要开发个质检工具,实现每次随机取2 ... -
oracle将一行拆分为多行
2011-10-12 00:51 2144客户的业务涉及大量的图片信息,之前这些图片信息只在数据库里存着 ... -
ORA-01034、ORA-27101和ORA-28056错误解决方法
2011-10-11 00:40 2242今天登录数据库的时候遇到了ORA-01034和ORA-2710 ... -
查看某个用户下的所有空表
2011-10-09 15:01 1052今天在群里有人问如何 ... -
SQL*LOADER加载图片、TXT
2011-10-09 15:02 1089朋友打电话问我如何利 ... -
oracle10gR2新特性--透明加密(TDE)
2011-10-09 15:02 1950从10gR2开始,oracle推出了透明数据加密技术(Tran ... -
NAMES.DIRECTORY_PATH客户端连接参数
2011-10-08 22:38 3858今天在做oracle10gR2新特性透明加密(TDE)的时候, ... -
tnsping通却连接不上数据库
2011-10-08 22:26 2429今天在Windows XP上装可个11gR2数据库,却出现个很 ... -
ORACLE字符集检查工具CSSCAN
2011-10-08 22:22 1798我们在创建数据库的时候,通常会把字符集设置为ZHS16GBK, ... -
SQL*LOADER和外部表加载
2011-10-08 22:17 1331最近一直在用SQL*LOADER加载数据,用外部表也可以实现, ... -
创建本地Duplicate数据库
2011-10-08 22:14 1029Duplicate是RMAN的一个组成部分,利用Duplica ... -
由ACOUG、云和恩墨主办的”Oracle技术嘉年华(OTN China Tour 2011)“活动已经正式拉开帷幕。
2011-09-01 12:00 787由ACOUG、云和恩墨主办的”Oracle技术嘉年华(OTN ... -
enq: TX - row lock contention
2011-07-19 17:52 1125今天,收到客户的邮件说上周每天早上10点多,数据库都会有很多锁 ...
相关推荐
win764bit plsql 登录oracle11g ora-12154 问题汇总.pdf
Oracle Exception汇总(自定义Oracle异常) 使用方法举例: Exception When no_data_found then Dbms_output.put_line(‘no_data_found’); ACCESS_INTO_NULL 为对象赋值前必需初始化对象。对应ORA-06530错误。 CASE...
1 由于ARCHIVE挂起导致数据库挂死 2 NIT文件中SGA区设置太大,导致内存不够用,数据库和系统都挂死 3 由于临时表空间无法扩展导致数据库被挂起 4由于未打补丁导致RMAN...27 由于OS层问题导致数据库ORA-600错误 .....
ASM实例+ASM数据库安装(Win8+Ora10) 1 第一篇 创建未格式化的磁盘分区 1 1.1 打开压缩卷窗口 1 1.2 输入卷大小 3 1.3 选择挂载目录 4 1.4 格式化分区选项 5 1.5汇总信息 6 1.6分区完成后磁盘情况 7 1.7挂载目录...
1、ORA-12541:TNS:没有监听器 原因:没有启动监听器或者监听器损坏。若是前者,使用命令net start OracleOraHome10gTNSListener(名字可能有出入)即可;如果是后者,则使用“Net Configuration Assistant”工具向导之...
数据库体系结构:结构组件汇总 1-19 小结 1-20 2 配置 Oracle Recovery Manager 课程目标 2-2 备份和恢复:概述 2-3 Oracle Recovery Manager 的功能 2-4 Oracle Recovery Manager 组件 2-6 配置 RMAN 的...
数据库体系结构:结构组件汇总 1-19 小结 1-20 2 配置 Oracle Recovery Manager 课程目标 2-2 备份和恢复:概述 2-3 Oracle Recovery Manager 的功能 2-4 Oracle Recovery Manager 组件 2-6 配置 RMAN 的...
数据库常见问题汇总 很多常见的ora错误解决方案
分2个压缩包 <br/>10g Doc Library.chm(总目录) ┃ ┣━Dict ┃ ┃ ┃ ┣━Ora 10G SQLPLUS_Ref.chm ┃ ┃ ┃ ┣━Ora 10G SQL Reference.chm ┃ ┃ ┃ ┣━Ora 10G Err_Msg....
分2个压缩包 <br/>10g Doc Library.chm(总目录) ┃ ┣━Dict ┃ ┃ ┃ ┣━Ora 10G SQLPLUS_Ref.chm ┃ ┃ ┃ ┣━Ora 10G SQL Reference.chm ┃ ┃ ┃ ┣━Ora 10G Err_Msg....
Vue汇总示例 一个Vue + Rollup Boilerplate,以及rxjs和ora rxjs帮助,可以生成漂亮的CLI输出。 git clone https://github.com/jonataswalker/vue-rollup-example.git cd vue-rollup-example npm install npm run ...
我通过OBOC却连不上数据库,请问应该如何配置? 答:PB提供了与当前流行的大型数据库如Oracle、Informix、Sybase等的专用接口,连接时无需通过ODBC。配置步骤具体如下: 1. 首先要通过SQL*Net配置数据库别名。...
教程名称:ORACLE自学入门文档汇总课程目录:【】Oracle RAC 11g实战指南【】ORACLE_DBA数据库管理员教程【】ORACLE_PLSQL学习总结(基础)【】ORACLE_PLSQL学习总结(提高)【】ORACLE_SQL性能优化(全)【】oracle...
四种算法来实现这个目的: 第一种: Array.prototype.unique1 = function () { var n = []; //一个新的临时数组 for (var i = 0; i < this.length; i++) //遍历当前数组 ... //如果当前数组的第i已经保存进了...
一、执行任务时有表空间的问题 二、单表消费oracle数据库表中有Binary_FLOAT字段 三、读取oracle数据到hive出现null值 四、读取ora
3.3 数据仓库:统计、汇总、决策支持。select 执行较多,要求执行select速度要快 3.4 通用:介于在事务处理和数据仓库之间。 我们在安装时需要考虑:两条跨数据库的执行语句问题。比如:在分别对2个数据库中的表进行...