Error Code
ORA-00220
Description
Control File not mounted by first instance, check alert log for more info
Cause
Possible cause of this error is, 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
To fix this issue, find and install the correct control file.
reference
Sunday, April 21, 2013
ORA-00219 Required Control File Size Exceeds Maximum Allowable Size
Error Code
ORA-00219
Description
Required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks).
Cause
Possible cause of this error is, an invocation of CREATE DATABASE or CREATE CONTROLFILE was executed specifying a combination of parameters that would require the control file size in blocks to exceed the maximum allowable value.
Action
To fix this issue, in the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses.
reference
ORA-00219
Description
Required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks).
Cause
Possible cause of this error is, an invocation of CREATE DATABASE or CREATE CONTROLFILE was executed specifying a combination of parameters that would require the control file size in blocks to exceed the maximum allowable value.
Action
To fix this issue, in the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses.
reference
ORA-00218 Block Size String of Control File 'string' does not match DB_BLOCK_SIZE
Error Code
ORA-00218
Description
Block size string of control file 'string' does not match DB_BLOCK_SIZE (string)
Cause
Possible cause of this error is, the block size as stored in the control file header is different from the value of the initialization parameter DB_BLOCK_SIZE. This might be due to an incorrect setting of DB_BLOCK_SIZE, or else might indicate that the control file has either been corrupted or belongs to a different database.
Action
To fix this issue, restore a good copy of the control file. If the control file is known to be clean set the DB_BLOCK_SIZE to match control file headers block size value.
reference
ORA-00218
Description
Block size string of control file 'string' does not match DB_BLOCK_SIZE (string)
Cause
Possible cause of this error is, the block size as stored in the control file header is different from the value of the initialization parameter DB_BLOCK_SIZE. This might be due to an incorrect setting of DB_BLOCK_SIZE, or else might indicate that the control file has either been corrupted or belongs to a different database.
Action
To fix this issue, restore a good copy of the control file. If the control file is known to be clean set the DB_BLOCK_SIZE to match control file headers block size value.
reference
ORA-00217 Control File could not be Resized for New Record Types
Error Code
ORA-00217
Description
Control file could not be resized for new record types
Cause
Possible cause of this error is, the control file was missing some new record types supported by this release. These record types are automatically added by resizing the contol file during mount. The resize has failed.
Action
To fix this issue, look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.
reference
ORA-00217
Description
Control file could not be resized for new record types
Cause
Possible cause of this error is, the control file was missing some new record types supported by this release. These record types are automatically added by resizing the contol file during mount. The resize has failed.
Action
To fix this issue, look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.
reference
ORA-00216 Control File could not be Resized for Migration
Error Code
ORA-00216
Description
Control file could not be resized for migration from 8.0.2
Cause
Possible cause of this error is, the control file created by release 8.0.2 was missing some record types. These record types are automatically added by resizing the control file during mount. The resize has failed.
Action
To fix this issue, look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.
reference
ORA-00216
Description
Control file could not be resized for migration from 8.0.2
Cause
Possible cause of this error is, the control file created by release 8.0.2 was missing some record types. These record types are automatically added by resizing the control file during mount. The resize has failed.
Action
To fix this issue, look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.
reference
Subscribe to:
Posts (Atom)