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 and the Export view cannot be executed. If CATEXP. SQL is already running, it may be a version error.
Solution: because some views shared by Import and Export run CATEXP. SQL to load (they have the same view) and do not generate a separate CATEXP. so that the view and Export code is not synchronized, it is difficult to maintain compatibility between each other, the user must establish their own Export application, so as to avoid ORA-00942 errors.
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 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.
The preceding errors are common issues when using rollback segments. The ORA-01598 specifies that the currently used rollback segments are in the not online status and cannot be used, change it to the online status for use; The ORA-01636 indicates that the current rollback segment is already in the online status and can be used directly without gathering 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, this is because ORACLE fails to roll back a transaction that has not been committed in a transaction table. Generally, the reason is that a datafile or tablespace is in the offline status, an undo target is damaged, or a rollback segment is damaged. The solution is to set all tablespace and datafile to the online status. If it cannot be solved, do the following: 1>. in initsid. add event = "10015 trace name context forever lever 10" to ora; 2>. shut down the database and restart it. 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 # (with sys. the object_id in the dba_objects table is the same) in sys. the name of the object in the dba_objects table; 6>. drop this object; 7>. in init. add the rollback segment to the rollback_segments parameter in the ora file and delete the eve Nt; 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 ADD file system files and original partitions, or increase the INITIAL size (for example, alter tablespace CDRS101 default storage (next 500 M pctincrease 1 )) it should be able to solve the problem. Otherwise, someone will use your tablespace to create a large data file, resulting in insufficient space usage.
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
