Oracle Database Errors or Warnings from Error ORA-00166 to ORA-00210

SQLServerF1

ORA-00166: remote/local nesting level is too deep
Cause: Too many remote table operations required a reverse trip back to the local site, for example to execute a local function on a remote table.
Action: Rearrange the query or co-locate the functions with the tables.
ORA-00200: control file could not be created
Cause: It was not possible to create the control file.
Action: Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again.
ORA-00201: control file version string incompatible with ORACLE version string
Cause: The control file was created by incompatible software.
Action: Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release.
ORA-00202: control file: ‘string’
Cause: This message reports the name file involved in other messages.
Action: See associated error messages for a description of the problem.

ORA-00203: using the wrong control files
Cause: The mount ID in the control file is not the same as the mount ID in the control file used by the first instance to mount this database. The control files are for the same database but they are not the same files. Most likely one instance is using a backup control file.
Action: Check that the correct control files were specified.
ORA-00204: error in reading (block string, # blocks string) of control file
Cause: A disk I/O failure was detected on reading the control file.
Action: Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk.
ORA-00205: error in identifying control file, check alert log for more info
Cause: The system could not find a control file of the specified name and size.
Action: Check that ALL control files are online and that they are the same files that the system created at cold start time.
ORA-00206: error in writing (block string, # blocks string) of control file
Cause: A disk I/O failure was detected on writing the control file.
Action: Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk.

ORA-00207: control files are not for the same database
Cause: The database ID in the control file is not the same as the database ID in the control file used by the first instance to mount this database. Most likely one of the mounts used the wrong control file or there are two databases with the same name.
Action: Check that the control file is for the correct database and is not an old version.
ORA-00208: number of control file names exceeds limit of string
Cause: An attempt was made to use more control files than Oracle supports.
Action: Shut down Oracle. Reduce the number of control files specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle. Delete usused files.
ORA-00209: control file blocksize mismatch, check alert log for more info
Cause: The block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter.
Action: Look at the alert log for more information.
ORA-00210: cannot open the specified control file
Cause: Cannot open the control file.
Action: Check to make sure the control file exists and is not locked by some other program.

Above are list of Oracle Database Errors or Warnings from Error ORA-00166 to ORA-00210 received while performing certain operation against Oracle Database or related products.

What are Oracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database.  Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *