ORA-01571: redo version string incompatible with ORACLE version string
Cause: This software version can not read the current redo logs, and either crash recovery is required or there are offline database files that need media recovery. If a file name is listed then it needs media recovery.
Action: Shutdown and startup using the compatible software. Do any required media recovery, and open the database. Shutdown and then startup using current software. If the file is going to be dropped then take it offline with the DROP option to skip this check.
ORA-01572: rollback segment ‘string’ cannot be brought online, string extents exceeded
Cause: The number of extents in the rollback segment exceeds the hard limit. It cannot be brought online for writing.
Action: Drop and recreate the rollback segment.
ORA-01573: shutting down instance, no further change allowed
Cause: Some process tries to make changes while the db is being shutdown
ORA-01574: maximum number of concurrent transactions exceeded
Cause: the limit on the number of concurrent transactions has been hit
Action: shutdown the system, increase the INIT.ORA parameter ‘transactions’ , and then restart the system.
ORA-01575: timeout waiting for space management resource
Cause: failed to acquire necessary resource to do space management.
Action: Retry the operation.
ORA-01576: The instance string is not enabled
Cause: The thread associated with instance is not enabled.
Action: Enable the thread associated with the instance using ALTERR DATABASE ENABLE INSTANCE command.
ORA-01577: cannot add log file ‘string’ – file already part of database
Cause: During CREATE or ALTERR DATABASE, a file being added is already part of the database.
Action: Use a different file name.
ORA-01578: ORACLE data block corrupted (file # string, block # string)
Cause: The data block indicated was corrupted, mostly due to software errors.
Action: Try to restore the segment containing the block indicated. This may involve dropping the segment and recreating it. If there is a trace file, report the errors in it to your ORACLE representative.
ORA-01579: write error occurred during recovery
Cause: A write error occurred during recovery
Action: Consult trace files for the nature of the write error, and correct error.
ORA-01580: error creating control backup file string
Cause: An operating system error occurred while attempting to create a control file backup.
Action: Check the error stack for more detailed information
Above are list of Oracle Database Errors or Warnings from Error ORA-01571 to ORA-01580 received while performing certain operation against Oracle Database or related products.
What are Oracle Database Error Messages?
Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.
Hope this was helpful.
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.