ORA-00227 : corrupt block detected in controlfile: (block string, # blocks string)

Saturday, March 22nd, 2008

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.

Popularity: 10% [?]

ORA-00226 : operation disallowed while alternate controlfile open

Saturday, March 22nd, 2008

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.

Popularity: 2% [?]

ORA-00224 : controlfile resize attempted with illegal record type (string)

Saturday, March 22nd, 2008

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 to 16).

Popularity: 2% [?]

ORA-00221 : error on write to controlfile

Saturday, March 22nd, 2008

Cause : An error occurred when writing to one or more of the control files.
Action: See accompanying messages.

Popularity: 4% [?]

ORA-00220 : controlfile not mounted by first instance, check alert log for more info

Saturday, March 22nd, 2008

Cause : The specified control file has a different mount ID than the other control files that are being mounted. This means that the first instance to mount the database did not use this control file.
Action : Find and install the correct control file.

Popularity: 9% [?]

ORA-00216 : controlfile could not be resized for migration from 8.0.2

Saturday, March 22nd, 2008

Cause : Control files created by release 8.0.2 were missing some records. These records are automatically added by resizing the control file when attempting to run a later release. The resize failed.
Action: Look in the alert log for the reason that the resize failed. If it can be fixed by giving the control file more space, then do that. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.

Popularity: 2% [?]

ORA-00208 : number of controlfile names exceeds limit of string

Saturday, March 22nd, 2008

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 unused files.

Popularity: 3% [?]

ORA-00206 : error in writing (block string, # blocks string) of controlfile

Friday, March 21st, 2008

Cause : A disk I/O failure was detected on writing to the control file.
Action : Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If it is online, then look for operating system reasons for Oracle’s inability to write to the disk or control file. See the Oracle8i
Administrator’s Guide for information on recovering from the loss of a control file. See also your operation system-specific Oracle documentation.

Popularity: 3% [?]

ORA-00205 : error in identifying controlfile, check alert log for more info

Friday, March 21st, 2008

Cause : The system could not find a control file of the specified name and size.
Action : One of the following:
- Check that the proper control file name is referenced in the CONTROL_FILES initialization parameter in the initialization parameter file and try again.
- When using mirrored control files, that is, more than one control file is referenced in the initialization parameter file, remove the control file name listed in the message from the initialization parameter file and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file with a new file name in the initialization parameter file.

Popularity: 14% [?]

ORA-00204 : error in reading (block string, # blocks string) of controlfile

Friday, March 21st, 2008

Cause : A disk I/O failure was detected on reading the control file.
Action : Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If it is online, then look for operating system reasons for Oracle’s inability to read the disk or control file. See the Oracle8i Administrator’s
Guide for information on recovering from the loss of a control file. See also your operation system-specific Oracle documentation.

Popularity: 5% [?]

Close
E-mail It