ORA-00600: Internal Error Code, Arguments: [Num], [?], [?], [?], [?] Cause: This error is usually an internal error of Oracle, which is useful for OSS and Oracle development. ORA-600 errors often accompany the status dump of the file (system status and process status), the system status store will include information of the current object held by Oracle RDBMS, and the process status dump will display objects held by special processes. When the process meets a wrong condition, it is often because some information taken from the one of its holding, if we know the blocks held by these error processes, it is easy to track the source of the problem. Workaround: In general, this error is unable to solve. Only from improving the system itself to solve this internal problem, if the hardware device, adjust system performance, use OPS (of course OPS speaks in a sense and Not a good solution), etc. The first variable of ORA-600 errors is used to mark the wrong position in the code (the first variable of each portion in the code is different), from the second to the fifth variable display additional information, tell the OSS code Where there is a mistake.
An error example is as follows: ORA-00600: Internal Error Code, Arguments: [1237], [], [], [], [], [], [], [] The corresponding English is as follows: 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 (timeout) file corruption (too old file) Failed data checks in memory (RAM Retrieval failure) Hardware, Memory, OR I / O Errors (hardware, memory, or disk error) Incorrectly Restored Files ORA-03113: End-of-file on Communication Channel Cause: Communication is not ending, thus Causes the communication channel to stop the solution: 1>. Check if there is a service process is not normal to crash, you can know from Alert.log 2>. Check if SQL * NET DRIVER is connected to Oracle executable 3>. Check if the server network is normal. If the network is not accepted or unstable, etc. 4>. Check if there are two nodes of the same name on the same online. Check if there is a repetitive IP address on the same online as follows: cause: an undepected 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 MA chine 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 Cause: This is due to the loaded table or view does not exist, mostly catexp.sql has not yet run, unable to execute the export view, if catexp.sql has run,
It may be a version error. Workaround: Some views shared by Import and Export are loaded by running catexp.sql (they have the same view), and do not generate separate catexp.sql, thus causing the view and the export code as sync, it is difficult to keep each other. Between compatibility, users must establish their own Export apps, thereby avoiding errors of ORA-00942. The corresponding English is as follows:
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 requiredThat 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 onlineCause: 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 onlineCause: 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. These errors are all common problems when using the rollback segment, and ORA-01598 indicates the current repayment segment. The status is "not online", can not be used, change it to "Online" status; ORA-01636 indicates that the current rolling segment is already "Online" status, you can use it directly, no need to set it again. ORA-1636 SIGNALLED DURING: ALTER ROLLBACK Segment RB00 Online We may also encounter the following problems: a phenomenon of "Needs Recovery" statistics, which is due to Oracle Retreat No Submit It is caused by failure when things. Usually, a DataFile or TableSpace is a state in OFFLINE or a UNDO target is destroyed or Rollback Segment is destroyed. The solution is to set all the tablespace and datafile to the ONLINE state. If you don't solve it, do the following work: 1>. Add Event = "10015 Trace Name Context Forever Lever 10" in INITSID.ORA; 2> .shutdown The database is then restarted; 3>. Under $ oracle_home / rdbms / log, find the trace file generated when Startup; 4>. In the trace file, find the following information "Error Recovery TX (#, #) Object #"; 5> According to Object # (same as Object_ID in the sys.dba_objects table), the name of the object is isolated in the sys.dba_objects table; 6>. Object Drop dropped; 7>. In the init.ora file, the Rollback Segment will be Play back in the Rollback_SEGMENTS parameter, delete the event; 8> .shutdown database and restart. The problem with "Needs Recovery" at this time should be completely solved, otherwise the Rollback Segment is destroyed. ORA-01688: UNABLE TO EXTEND TABLE NAME.NAME Partition Name By Num in TableSpace Name Generative Cause: The specified TableSpace space has been occupied and cannot be expanded.
