• 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 be
    handled 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 interprocess
    communication 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 Net8
    driver and confirm Net8 software is correctly installed on the server.If the message occurs after a
    connection 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 error
    that 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 was
    referenced 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,the
    table the application tried to access does not exist in the database,or the application does not have
    access 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 parameters
    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 lever
    10”;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




    版权声明: 原创作品,答应转载,转载时请务必以超链接情势标明文章 原始起因 、作者信息和本声明。否则将追究法令责任。

  • 相关阅读:
    “介绍一下自己吧”——记2020BUAA软工团队介绍和采访
    [no code][scrum meeting] Alpha 7
    [no code][scrum meeting] Alpha 6
    [no code][scrum meeting] Alpha 5
    [no code][scrum meeting] Alpha 4
    [no code][scrum meeting] Alpha 3
    [no code][scrum meeting] Alpha 2
    [no code][scrum meeting] Alpha 1
    [no_code]团队贡献分分配规则
    [no_code]团队任务拆解Alpha
  • 原文地址:https://www.cnblogs.com/zgqjymx/p/1975882.html
Copyright © 2020-2023  润新知