Retry the command without specifying the thread. If desired, the thread can be re–created after the database has been opened.
ORA–01217
log file member belongs to a different redo log file group
Cause
A member of a redo log file group specified in the CREATE CONTROLFILE
command is not part of the same group as the previous members.
Action
Group together the correct members of the redo log file group for the CREATE
CONTROLFILE command.
ORA–01218
log file member is not from the same point–in–time
Cause
A member of a redo log file group specified in the CREATE CONTROLFILE
command is from a different point in time from the previous members. One of the members specified may be an older, possibly a backup copy, version of the redo log.
Action
Find the correct version of the redo log or leave it out of the CREATE
CONTROLFILE command.
ORA–01219
database not open: queries allowed on fixed tables/views only
Cause
A query was issued against an object not recognized as a fixed table or fixed view before the database was opened.
Action
Revise the query to include only fixed objects or open the database.
Oracle7 Server Messages
2 – 105
01100–01250: Oracle Files
ORA–01220
file based sort illegal before database is open
Cause
A query issued against a fixed table or view required a temporary segment for sorting before the database was open. Only in–memory sorts are supported before the database is open.
Action
Rephrase the query to avoid a large sort and increase the SORT_AREA_SIZE
parameter in the initialization parameter file to enable the sort to be done in memory.
ORA–01221
datafile name is not the same file to a background process Cause
When the database writer opens the datafile, it is accessing a different physical file than the foreground doing the recovery. The time–stamp set in the file header by the foreground was not found by the background. It may be that the background process could not read the file at all.
Action
Look in the DBWR trace file for the error it received when attempting to read the file header. Reconfigure the operating system as needed to have the filename successfully access the same file when opened by a
background process.
ORA–01222
MAXINSTANCES of num requires MAXLOGFILES be at least num, not num
Cause
An attempt was made to create a database or control file that does not have room for at least two redo logs per thread of redo. A thread of redo must have two online redo logs in order to be enabled. It does not make sense to allow more redo threads than can be supported by the logs.
Action
Either reduce the MAXINSTANCES argument or increase MAXLOGFILES.
ORA–01223
RESETLOGS must be specified to set a new database name
Cause
The SET database name option was specified to CREATE CONTROLFILE, but RESETLOGS was not specified. The database name can only be changed when opening the database with RESETLOGS.
Action
Either add the RESETLOGS option or drop the SET option to
CREATE CONTROLFILE.
ORA–01224
group number in header name does not match GROUP name
Cause
Group number specified at CREATE CONTROLFILE does not match the group number stored in the header. Most likely the specification is wrong.
Action
Omit the GROUP option or give the correct one.
2 – 106
Oracle7 Server Messages
01100–01250: Oracle Files
ORA–01225
thread number num is greater than MAXINSTANCES num
Cause
The redo log is for a thread greater than the MAXINSTANCES arguments.
Action
Increase the value for MAXINSTANCES and retry the command.
ORA–01226
file header of redo log member is inconsistent with other member Cause
The redo log file member in the accompanying message is for the same group as the previous members, but other fields in the header are different. Either a file header is corrupted, or some file is a member of a deleted redo log.
Action
Correct the redo log member or omit this member from the command.
ORA–01227
log name is inconsistent with other log
Cause