Analysis and Solution of common ORACLE error codes (3)
Analysis and Solution of common ORACLE error codes (3)
The ORACLE tutorial is: Analysis and Solution of common ORACLE error codes (3 ). ORA-00600: internal error code, arguments: [num], [?], [?], [?], [?]
Cause: this error is usually an internal ORACLE error and is only useful for OSS and ORACLE development. ORA-600 errors are often accompanied by State dump of the trace file
(System status and Process status), the system status storage will include information about the current object held by oracle rdbms, and the process status dump will display the special process holding
Some objects, when a process meets an error condition, are often taken from a block it holds because of some information. If we know that these error processes hold
Block, it is easy to track the source of the problem.
Solution: in general, this error cannot be solved. We only need to improve the system to solve this internal problem, such as adding hardware.
Device, adjust system performance, and use OPS (of course, OPS is not a good solution in a sense. The first variable for ORA-600 errors is used
Mark the error location in the Code (the first variable in each part of the code is different), and the second to fifth variables display additional information to tell the OSS code where
Error.
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 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 Upload uption (the File is too old)
Failed data checks in memory (memory retrieval Failed)
Hardware, memory, or I/O errors (Hardware, memory, or disk error)
Incorrectly restored files (incorrect reconstruction file)
ORA-03113: end-of-file on communication channel
Cause: the communication ends abnormally, resulting in the termination of the communication channel.
Solution: 1> check whether the server process is abnormal or not. You can learn from alert. log
2>. Check whether the SQL * Net Driver is connected to the ORACLE executable program.
3>. Check whether the server network is normal, for example, the network is disconnected or unstable.
4>. check whether there are two nodes with the same name on the same network.
5>. Check whether duplicate IP addresses exist on the same network.
The corresponding English is as follows:
Cause: An unexpected end-of-file was processed on the communication channel. The problem cocould not be
Handled by the Net8, two task, software. This message cocould 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
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 balance of customer support.
ORA-00942: table or view does not exist
Cause: this is because the mounted table or view does not exist. Most of the reason is that CATEXP. SQL is not running yet and the Export view cannot be executed. If CATEXP. SQL has been run
Line, it may be a version error.
Solution: because some views shared by Import and Export are loaded by running CATEXP. SQL (they have the same view), they are not generated separately.
As a result, the view and Export Code are not synchronized, and it is difficult to maintain compatibility with each other. You must create your own Export application.
Avoid errors in the 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,
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,
[1]
The ORACLE tutorial is: Analysis and Solution of common ORACLE error codes (3 ). Nd 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.
The above errors are common issues when using rollback segments, and the ORA-01598 specifies that the currently used rollback segments are in the not online status and cannot
Use, change it to the "online" status to be used; the ORA-01636 indicates that the current rollback segment is already in the "online" status, can be used directly, no need to set
It.
ORA-1636 signalled during: alter rollback segment rb00 online
We may also encounter the following problems during statistics: the status of a rollback segment is "Needs Recovery", which is due to ORACLE rollback.
This error is caused by the failure of a non-committed transaction in a transaction table. Generally, a datafile or tablespace is in offline status or
The undo target is damaged or the rollback segment is damaged. The solution is to set all tablespace and datafile to online. If
Do the following: 1>. Add event = "10015 trace name context forever lever to initsid. ora
10 "; 2>. Shut down the database and restart; 3>. Locate the trace file generated when startup under $ ORACLE_HOME/rdbms/log; 4>. In the trace file
Find the following information: "error recovery tx (#, #) object #"; 5>. According to object # (same as object_id in sys. dba_objects table) in
Check the name of the object in the sys. dba_objects table; 6>. drop the object; 7>. Put the rollback segment back in the init. ora file.
In the rollback_segments parameter, delete event; 8>. Shut down the database and restart it. In this case, the "Needs Recovery" problem should be completely solved.
Otherwise, the rollback segment is damaged.
ORA-01688: unable to extend table name. name partition NAME by NUM in tablespace NAME
Cause: the specified tablespace is full and cannot be expanded.
Solution: run the "alter tablespace add datafile" command to increase the file system file and original partition, or increase the INITIAL size (for example:
Alter tablespace CDRS101 default storage (next 500 M pctincrease 1) should be able to solve the problem, otherwise someone will use your tablespace
You have created a large data file on it, which causes your tablespace 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 cocould 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
[2]
