Oracle Database Error Message Codes and Their Description from ORA-00221 to ORA-00250

ORA-00221: error on write to control file
Cause: An error occurred when writing to one or more of the control files.
Action: See accompanying messages.

 


ORA-00222: operation would reuse name of a currently mounted control file
Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of the specified currently mounted control file.
Action: Retry the operation with a different filename.

ORA-00223: convert file is invalid or incorrect version
Cause: An Oracle7 to Oracle8 convert file contains invalid data or was created with an different version of the migration utility. This error can also be caused by incorrect ORACLE_HOME environment variable when ALTER DATABASE CONVERT command is issued.
Action: Use a correct version of the convert file or regenerate it with the migration utility. Make sure that the migration utility is the same version as the Oracle8 RDBMS executable and that the ORACLE_HOME environment variable is properly set.

 

ORA-00224: control file resize attempted with illegal record type (string)
Cause: An attempt was made to expand or shrink the control file by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter.
Action: Use a value for the RECORD_TYPE parameter that specifies a valid record type other than type 0 (valid range is 1-16).

 

ORA-00225: expected size string of control file differs from actual size string
Cause: The expected size of the control file as stored in its header was different than the actual operating system file size. This usually indicates that the control file was corrupted.
Action: Restore a good copy of the control file.

 

ORA-00226: operation disallowed while alternate control file open
Cause: The attempted operation could not be executed at this time because this process had an alternate control file open for fixed table access.
Action: Retry the operation after calling cfileUseCurrent.

 

ORA-00227: corrupt block detected in control file: (block string, # blocks string)
Cause: A block header corruption or checksum error was detected on reading the control file.
Action: Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command.

 

ORA-00228: length of alternate control file name exceeds maximum of string
Cause: The specified filename, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum filename length for this operating system.
Action: Retry the operation with a shorter filename.

 

ORA-00229: operation disallowed: already hold snapshot control file enqueue
Cause: The attempted operation cannot be executed at this time because this process currently holds the snapshot control file enqueue.
Action: Retry the operation after calling cfileUseCurrent to release the snapshot control file enqueue.

 

ORA-00230: operation disallowed: snapshot control file enqueue unavailable
Cause: The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue.
Action: Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates.

 

ORA-00231: snapshot control file has not been named
Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no filename for the snapshot control file had previously been specified.
Action: Specify a name for the snapshot control file by calling cfileSetSnapshotName.

 

ORA-00232: snapshot control file is nonexistent, corrupt, or unreadable
Cause: The snapshot control file was found to be nonexistent, corrupt, or unreadable during an invocation of cfileUseSnapshot.
Action: Call cfileMakeAndUseSnapshot again (or for the first time).

 

ORA-00233: copy control file is corrupt or unreadable
Cause: The specified copy control file was found to be corrupt or unreadable during an invocation of cfileUseCopy.
Action: Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same filename that was specified for cfileUseCopy.

 

ORA-00234: error in identifying or opening snapshot or copy control file
Cause: A snapshot or copy control file of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy.
Action: Re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively.

 

ORA-00235: control file read without a lock inconsistent due to concurrent update
Cause: Concurrent update activity on a control file caused a process to read inconsistent information from the control file without a lock.
Action: Retry the operation.

 

ORA-00236: snapshot operation disallowed: mounted control file is a backup
Cause: Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted control file is a backup control file.
Action: Mount a current control file and retry the operation.

 

ORA-00237: snapshot operation disallowed: control file newly created
Cause: An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made.
Action: Mount a current control file and retry the operation.

 

ORA-00238: operation would reuse a filename that is part of the database
Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that is currently part of the database.
Action: Retry the operation with a different filename.

ORA-00239: timeout waiting for control file enqueue: held by ‘string’ for more than string seconds
Cause: The specified process waited the maximum allowed time for the control file enqueue.
Action: Restart the blocking instance indicated in the incident trace file or reboot the blocking node.

 

ORA-00240: control file enqueue held for more than string seconds
Cause: The current process did not release the control file enqueue within the maximum allowed time.
Action: Reissue any commands that failed and contact Oracle Support Services with the incident information.

 

ORA-00250: archiver not started
Cause: An attempt was made to stop automatic archiving, but the archiver process was not running.
Action: No action required.

About Mehmet Salih Deveci

I am Founder of SysDBASoft IT and IT Tutorial and Certified Expert about Oracle & SQL Server database, Goldengate, Exadata Machine, Oracle Database Appliance administrator with 10+years experience.I have OCA, OCP, OCE RAC Expert Certificates I have worked 100+ Banking, Insurance, Finance, Telco and etc. clients as a Consultant, Insource or Outsource.I have done 200+ Operations in this clients such as Exadata Installation & PoC & Migration & Upgrade, Oracle & SQL Server Database Upgrade, Oracle RAC Installation, SQL Server AlwaysOn Installation, Database Migration, Disaster Recovery, Backup Restore, Performance Tuning, Periodic Healthchecks.I have done 2000+ Table replication with Goldengate or SQL Server Replication tool for DWH Databases in many clients.If you need Oracle DBA, SQL Server DBA, APPS DBA,  Exadata, Goldengate, EBS Consultancy and Training you can send my email adress [email protected].-                                                                                                                                                                                                                                                 -Oracle DBA, SQL Server DBA, APPS DBA,  Exadata, Goldengate, EBS ve linux Danışmanlık ve Eğitim için  [email protected] a mail atabilirsiniz.

Leave a Reply

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