oracle error - ORA-00220: control file not mounted by first instance, check alert log for more info

ORA-00220:	control file not mounted by first instance, check alert log for more info
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.

oracle error - ORA-00219: required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks)

ORA-00219:	required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks)
Cause:	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:	In the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses

ORA-00218:	block size string of control file 'string' does not match DB_BLOCK_SIZE (string)
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.
Action:	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.