User`s guide

A-4 Oracle Database User's Guide
Action: If the error cannot be identified as one caused by a disk malfunction, then
either contact the System Administrator, or contact your Oracle Support Services
Representative.
ORA-05022: read block outside of file
Cause: An attempt was made to read a block of an Oracle Database file that does
not exist (block number < 1 or > file size). This is an internal error and should not
normally occur.
Action: Contact your Oracle Support Services Representative.
ORA-05023: file close failed
Cause: The attempt to close an Oracle Database file failed. This is an internal error
and should not normally occur.
Action: Contact your Oracle Support Services Representative.
ORA-05025: sfccf:file mismatch. Trying to reuse a file with different size
Cause: When trying to reuse a database file, the file size specified differs from the
actual size of the existing file.
Action: Specify the correct file size (remember to subtract one logical block for the
implicit header block), or leave the size unspecified, or use a different file name if
you want to create a larger or smaller database file.
ORA-05026: file does not exist
Cause: An attempt was made to access a database file which no longer exists.
Action: Contact your database administrator who may know why this error has
occurred. If your database administrator cannot find the cause of the problem,
then contact your Oracle Support Services Representative.
ORA-05027: file does exist
Cause: When attempting to create a new file, the file is found to exist and not be
empty.
Action: If the error occurred in a create database , then retry with the reuse
option. Otherwise use a different file name or check whether the file can be erased.
ORA-05028: file is not a dbfile
Cause: The database (or log, or control) file to be opened does not contain the
proper identification for such a file.
Action: Check for wrong file specification.
ORA-05029: illegal use-option
Cause: Internal error. Function sfccf was called with an illegal option.
Action: Contact your Oracle Support Services Representative.
ORA-05030: SID not defined
Cause: When the system identification was required (typically, to substitute the
"?" in names, for example, in file names set by the initialization file), it was not yet
defined. This could be caused by a missing
ORAENV file or a missing ORASID in
that file.
Action: Ensure that the ORAENV file definition is correct and re-run the program.
ORA-05031: SID translation failure
Cause: The system identification is syntactically incorrect.