The Oracle tutorial being looked at is: analysis and resolution of Oracle Common error codes (iii). Ora-00600:internal error code,arguments:[num],[?],[?],[?],[?]
Reason: This error is usually an internal error of Oracle and is only useful for OSS and Oracle development. ORA-600 errors often accompany the state dump of the trace file
(System State and process State), the system state store will include information about the current object held by the Oracle RDBMS, and the process state dump will show the special process hold
Some objects, when the process conforms to an error condition, is often due to some information taken from a block it holds, if we know that these error processes hold
block, it is easy to track the source of the problem.
Workaround: In general, this error can not be solved by itself, only by improving the system itself to solve this internal problem, such as adding hardware
Device, adjust system performance, use OPS (of course OPS is not a good solution in a sense) and so on. The first variable of the ORA-600 error is used to mark the
The wrong position in the code (the first variable in each part of the code is different), the second to the fifth variable displays additional information telling the OSS where the code is
There was a mistake.
An example of an error is as follows:
Ora-00600:internal error code, arguments: [1237], [], [], [], [], [], [], []
The corresponding English is as follows:
Cause:this is a catchall internal the error message for the 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 (files too old)
Failed data checks in memory (memory retrieval failed)
Hardware,memory,or I/O errors (Hardware, memory, or disk error)
Incorrectly restored files (wrong rebuild file)
Ora-03113:end-of-file on communication channel
Cause: Communication is terminated abnormally, resulting in communication channel termination
Solution: 1> Check if there is a service process abnormal panic, can be learned from the Alert.log
2> Check sql*net driver is connected to an Oracle executable
3> Check that the server network is normal, such as network or unstable
4>: Check if there are two nodes with the same name on the same web
5>: Check if there is a duplicate IP address on the same web
The corresponding English is as follows:
Cause:an unexpected End-of-file is processed on the communication channel. The problem could not being
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 on the server. If the message occurs a
Connection is-Established,and the error is isn't due to a physical failure,check if a trace file was
Generated on the server in 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
Reason: This is because the loaded table or view does not exist, most of the catexp.sql is not yet running, unable to perform the export view, if Catexp.sql has been shipped
Row, it may be a version error.
Workaround: Because some views of import and export shares are loaded by running Catexp.sql (they have the same view), they do not generate separate
Catexp.sql, resulting in the view and export code is not synchronized, more difficult to maintain compatibility between each other, users must establish their own export applications, so
Avoid ORA-00942 errors.
The corresponding English is as follows:
Cause:the table or view entered does not exist,a synonym this is jnot allowed this is, used,or a view was
Referenced where a table is required. Existing user tables and views can is listed by querying the data
Dictionary. Certain privileges may required to access the table. If A application returned this message,the
Table the application tried to access does not exist in the Database,or the application does
Access to it.
Action:check each of the following:
The spelling of the table or view name.
That's a view isn't specified where a table is required
That is existing table or view name exists.
Contacts the database administrator if the table needs to is created or if user or application Priviledes
are required to access the table.
Also, if attempting to access a table or view into 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 the 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 being used by one instance and an instance to trying A bring
Segment online is already in use.
Action:check that's values set in the initialization parameter file for parameters
Rollback_segments,rollback_segment_initial,a
[1] [2] Next page
The Oracle tutorial being looked at is: analysis and resolution of Oracle Common error codes (iii). nd rollback_segment_count are correctly set for the instance
Whiththe problem,also Check that this instance is using the correct initialization parameter file. Make sure
You are are not confused about the difference between private and public rollback segments. The Oracle8
Server Administrator ' s Guide for more information about using rollback segments in Paraller mode.
All of the above errors are common to us when using rollback segments, ORA-01598 indicate that the status of the rollback segment currently in use is "not online" and does not allow
To use, change it to a "online" state, ORA-01636 indicates that the current rollback segment is already in the "online" state and can be used directly without having to assemble
It.
ORA-1636 signalled during:alter rollback segment rb00 Online
We may also encounter the following problems when doing statistics: a rollback segment status of "Needs Recovery", which is due to the Oracle fallback
The failure of an object in a table that is not committed. Usually the reason for a datafile or tablespace is in the state of offline or a
The target of undo is destroyed or rollback segment is destroyed. The solution is to put all the tablespace and datafile into the online state, if
Do not solve the following work: 1> add event= to Initsid.ora "10015 Trace name Context forever lever
2>.shutdown database and then restart; 3> under $oracle_home/rdbms/log, locate the trace file;4> generated at startup;. In the trace file
, locate the following information "Error recovery TX (#,#) object #"; 5> based on object# (same as sys.dba_objects in object_id table)
Sys.dba_objects the name of the object in the table, 6> Drop the object off; 7> the rollback segment back in the Init.ora file
Rollback_segments parameter, delete the Event;8>.shutdown database and reboot. At this point, the problem of "Needs Recovery" should be completely resolved
, otherwise the rollback segment was destroyed.
Ora-01688:unable to extend table Name.name partition name by NUM in Tablespace name
Reason: The specified tablespace space has been occupied and cannot be extended.
Workaround: Use the ALTER tablespace add datafile command to increase the file system files and raw partitions, or to increase the size of the initial, such as:
Alter tablespace CDRS101 default storage (next 500M pctincrease 1)) should be able to resolve otherwise someone is using your table space
A larger data file was created to cause your table space to be insufficient.
An example of an error is as follows:
Ora-1688:unable to extend table RMMCDR. LOCAL_CDR partition local_cdr101 by 460800 in Tablespace CDRS101
The corresponding English is as follows:
Cause:an extent could is allocated for a table segment in Tablespace
Action:use the ALTER tablespace ADD datafile statement to the specified tablespace
prev [1] [2]
