The problem may not be with the redo log listed because all that can be detected is that there is an inconsistency...

Pokaż mi serce nie opętane zwodniczymi marzeniami, a pokażę ci człowieka szczęśliwego.

All redo log files listed in the command must be the current versions of the online redo logs.
Action
Find the correct online redo logs or use the RESETLOGS option.
ORA–01228
SET DATABASE option required to install seed database
Cause
The SET DATABASE option was not included in the CREATE CONTROLFILE
command when installing a seed database. The database does not have a database ID because it is intended to be installed at multiple sites, and each site needs to be a different database with its own database ID. Both the SET
DATABASE and RESETLOGS options must be specified to create the control file for this database.
Action
Retry the command with the SET DATABASE and RESETLOGS options.
ORA–01229
datafile name is inconsistent with logs
Cause
The datafile in the accompanying message is inconsistent with the contents of the redo logs given in the CREATE CONTROLFILE command. The most likely cause is that one or more of the online redo logs was missing from the command. It is also possible that one or more of the redo logs is an old copy rather than the current version. All online redo log files must be listed in the command and must be the current versions of the online redo logs.
Action
Retry the command with the correct online redo logs or use the
RESETLOGS option.
Oracle7 Server Messages
2 – 107
01100–01250: Oracle Files
ORA–01230
cannot make read only – file name is offline
Cause
An attempt to make a tablespace read–only encountered an offline file.
Action
Bring the file online and retry the operation.
ORA–01231
cannot make read write – file name is offline
Cause
An attempt to make a tablespace read–write encountered an offline file.
Action
Bring the file online and retry the operation.
ORA–01232
cannot start online backup – file name is read only Cause
An attempt to start an online backup encountered a read–only file.
Action
Read–only files do not need to be set into online backup mode. Start the backup without using the BEGIN BACKUP command.
ORA–01233
file name is read only – cannot recover using backup control file Cause
An attempt to do media recovery using a backup control file encountered a read–only file. Typically, read–only files do not need to be recovered. However, if the recovery is using a backup control file, all online files must be recovered.
Action
Take the read–only file offline and bring the tablespace online only after opening the database. Ensure that the backup control file was in use when the currently read–only file was read–write. If such a control file is unavailable, you may be able to re–create it using the CREATE CONTROLFILE command.
2 – 108
Oracle7 Server Messages
01400–01489: SQL Execution
01400–01489: SQL Execution
This section lists messages generated during SQL execution.
ORA–01400
primary key or mandatory (NOT NULL) column is missing or NULL
during insert
Cause
When inserting or updating rows, a value for a column defined as NOT NULL
was not specified.
Action
Specify a value for each NOT NULL column or modify the table definition to allow NULL values in columns now defined as NOT NULL.
ORA–01401
inserted value too large for column
Cause
The value entered is larger than the maximum width defined for the column.
Action
Enter a value smaller than the column width or use the MODIFY option with ALTER TABLE to expand the column width.
ORA–01402
view WITH CHECK OPTION where–clause violation
Cause
An INSERT or UPDATE statement was attempted on a view created with the CHECK OPTION. This would have resulted in the creation of a row that would not satisfy the view’s WHERE clause.
Action
Examine the view’s WHERE clause in the dictionary table VIEWS. If the current view does not have the CHECK OPTION, then its FROM clause must reference a second view that is defined using the CHECK OPTION. The second view’s WHERE clause must also be satisfied by any INSERT or UPDATE
statements. To insert the row, it may be necessary to insert it directly into the underlying table, rather than through the view.
ORA–01403
no data found
Cause