Oracle数据库之错误代码第三章
ORA-00600:internal error code,arguments:[num],[?],[?],[?],[?]
产生原因：这种错误通常为ORACLE的内部错误，只对OSS和ORACLE开发有用。ORA-600的错误经常伴随跟踪文件的状态转储(系统状态和进程状态)，系统状态存储将包括ORACLE RDBMS持有的当前对象的信息，进程状态转储则将显示特殊进程持有的对象，当进程符合了某错误条件时，经常是由于一些信息取自它持有的一个块，如果我们知道这些错误进程持有的块，就容易跟踪问题的来源。
解决方法：一般来说出现这个错误我们本身是无法解决的，只有从提高系统本身各方面来解决这个内部问题，如增加硬件设备，调整系统性能，使用OPS(当然OPS从某种意义上说并不是一种好的解决方式)等。ORA-600错误的第一个变量用于标记代码中错误的位置(代码中的每个部分的第一变量都不一样)，从第二个到第五个变量显示附加信息，告诉OSS代码在哪里出现了错误。
一个报错例子如下：
ORA-00600: internal error code, arguments: [1237], [], [], [], [], [], [], []
相应的英文如下：
Cause:This is a catchall internal error message for Oracle program exceptions.It indicates that a process
has met a low-level,unexpected condition.Various causes of this message include:
Time-outs(超时)
File corruption(文件太老)
Failed data checks in memory(内存检索失败)
Hardware,memory,or I/O errors(硬件、内存或者磁盘错误)
Incorrectly restored files(错误的重建文件)
ORA-03113：end-of-file on communication channel
产生原因：通讯不正常结束，从而导致通讯通道终止
解决方法：
1>.检查是否有服进程不正常死机，可从alert.log得知
2>.检查sql*Net Driver是否连接到ORACLE可执行程序
3>.检查服务器网络是否正常，如网络不通或不稳定等
4>.检查同一个网上是否有两个同样名字的节点
5>.检查同一个网上是否有重复的IP地址
相应的英文如下：
Cause:An unexpected end-of-file was processed on the communication channel.The problem could not behandled by the Net8,two task,software.This message could occur if the shadow two-task process associated
with a Net8 connect has terminated abnormally,or if there is a physical failure of the interprocesscommunication vehicle,that is,the network or server machine went down.
Action:If this message occurs during a commection attempt,check the setup files for the appropriate Net8driver and confirm Net8 software is correctly installed on the server.If the message occurs after aconnection is well established,and the error is not due to a physical failure,check if a trace file was
generated on the server at failure time.Existence of a trace file may suggest an Oracle internal errorthat requires the assistance of customer support.
ORA-00942:table or view does not exist
产生原因：这是由于装载的表或视图不存在，多半是CATEXP.SQL还没有运行，无法执行Export视图,如果CATEXP.SQL已经运行，则可能是版本错误。
解决方法：因为Import和Export共享的一些视图是通过运行CATEXP.SQL来装载的(它们具有相同的视图)，并不生成单独的CATEXP.SQL，因而造成视图与Export代码不同步，较难保持彼此之间的兼容，用户就必须建立自己的Export应用，从而避免ORA-00942的错误。
相应的英文如下：
Cause:The table or view entered does not exist,a synonym that is jnot allowed here was used,or a view wasreferenced where a table is required.Existing user tables and views can be listed by querying the data
dictionary.Certain privileges may required to access the table.If an application returned this message,thetable the application tried to access does not exist in the database,or the application does not haveaccess to it.
Action:Check each of the following:
The spelling of the table or view name.
That a view is not specified where a table is required
That an existing table or view name exists.
Contact the database administrator if the table needs to be created or if user or application priviledes are required to access the table.
Also, if attempting to access a table or view in another schema,make certain thecorrect schema is referenced and that access to the object is granted.
ORA-01598:rollback segment “name” is not online
Cause:The rollback segment was taken offline either manually or by SMON.
Action:Check the status of the rollback segment in DBA_ROLLBACK_SEGS.
ORA-1636: rollback segment “name” is already online
Cause:A rollback segment can only be used by one instance and an instance is trying to bring a rollback
segment online that is already in use.
Action:Check that the values set in the initialization parameter file for p
arameters
ROLLBACK_SEGMENTS,ROLLBACK_SEGMENT_INITIAL,and ROLLBACK_SEGMENT_COUNT are correctly set for the instance whiththe problem,Also check that the instance is using the correct initialization parameter file.Make sure you are not confused about the difference between private and public rollback segments.See the Oracle8 Server Administrator's Guide for more information about using rollback segments in paraller mode.
上述错误均为我们在使用回滚段时比较常见的问题，ORA-01598指明当前使用的回滚段的状态为“not online”，不能使用，将它改为“online”状态即可使用;ORA-01636指明当前回滚段已经为“online”状态，可以直接使用，不用再集合它。
ORA-1636 signalled during: alter rollback segment rb00 online
我们在做统计时还可能遇到下述问题：一个rollback segment的状态为”Needs Recovery”的现象，这是由于ORACLE回退一个事物表中的没有提交的事物时失败所造成的。通常原因为一个datafile或者tablespace是在offline的状态或者一个undo的目标被破坏或者rollback segment被破坏。解决的办法是将所有的tablespace和datafile都置为online状态，如果不能解决则做下面的工作：
1>.在initsid.ora中加入event=”10015 trace name context forever lever10”;
2>.shutdown数据库然后重启;
3>.在$ORACLE_HOME/rdbms/log下，找到startup时生成的trace file;
4>.在trace文件中，找到下列信息“error recovery tx(#,#) object #”;
5>.根据object#(与sys.dba_objects表中的object_id相同)在sys.dba_objects表中查出该object的名字;
6>.将该object drop掉;
7>.在init.ora文件中将该rollback segment放回rollback_segments参数中，删除event;8>.shutdown数据库然后重启。此时”Needs Recovery”的问题应该是完全解决了，否则就是rollback segment被破坏了。
ORA-01688:unable to extend table name.name partition NAME by NUM in tablespace NAME
产生原因：指定的tablespace空间已经被占用满，无法扩展。
解决方法：
使用“ALTER TABLESPACE ADD DATAFILE”命令增加文件系统文件和原始分区，或者增加INITIAL的大小(如：alter tablespace CDRS101 default storage(next 500M pctincrease 1))应该能够解决，否则就是有人使用你的表空间上创建了一个比较大的数据文件导致你的表空间不够用。
一个报错例子如下：
ORA-1688: unable to extend table RMMCDR.LOCAL_CDR partition LOCAL_CDR101 by 460800 in tablespace CDRS101
相应的英文如下：
Cause:An extent could not be allocated for a table segment in tablespace
Action:Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the specified tablespace
在整理Oracle数据库的期间，如果对代码出现错误的情况比较多的话，一定得好好找到问题所在，这样才能有效的解决问题。如果喜欢，可以收藏爱站技术频道网站。
