Error Code
ORA-00222
Description
Operation would reuse name of a currently mounted control file
Cause
Possible cause of this error is, 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
To fix this issue, Retry the operation with a different filename.
reference
Programming Tutorials on XHTML, CSS, JavaScript, JQuery, JSON, Python, Django, Amazon Web Services, ASP.NET, Web Forms, and SQL
Sunday, April 21, 2013
ORA-00221 Error on Write to Control File
Error Code
ORA-00221
Description
Error on write to control file
Cause
Possible cause of this error is, an error occurred when writing to one or more of the control files.
Action
To fix this issue, see accompanying messages.
reference
ORA-00221
Description
Error on write to control file
Cause
Possible cause of this error is, an error occurred when writing to one or more of the control files.
Action
To fix this issue, see accompanying messages.
reference
ORA-00220 Control File not Mounted by First Instance
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
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
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
Subscribe to:
Posts (Atom)