How to Solve :
Oracle database error code ORA-00218 – block size string of control file string does not match DB_BLOCK_SIZE (string)
Oracle Database Error Code ORA-218 Description :
block size string of control file string does not match DB_BLOCK_SIZE (string)
Error Cause:
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.
How to Solve :
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.
Filed under: How to Solve, Oracle 10g, Oracle 11g, Oracle 9i, Oracle Error Codes Etiketler: ora - 218, 00218, 218, about oracle ORA-00218 error, block size string of control file string does not match DB_BLOCK_SIZE (string), help ORA-00218 about, How to Solve Oracle Database Error ORA-00218, ORA-00218 error code, ORA-00218 problem, Oracle 9i 10g 11g, Oracle Database Server Error Messages, Oracle Error Codes, oracle number 218 error code, oracle ORA-00218 example
1 Comment
1 Comment
Recent Entries
- Oracle database error code ORA-29959 – error in the execution of the string routine for one or more of the index partitions
- Oracle database error code ORA-31601 – Function string cannot be called now that fetch has begun.
- Oracle database error code ORA-29958 – fatal error occurred in the execution of ODCIINDEXCREATE routine
- Oracle database error code ORA-31600 – invalid input value string for parameter string in function string
- Oracle database error code ORA-29957 – cannot create a function-based domain index on a string table
- Oracle database error code ORA-31604 – invalid string parameter “string” for object type string in function string
- Oracle database error code ORA-29961 – too many warnings occurred in the execution of ODCIIndex DDL routine
Search Oracle Error Codes and Descriptions:
1 Comment Already
Similar Errors
Please Leave Your Comments Below