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