Action: A server group is owned by the first user who logs into a server in
the server group in non-migratable mode. All subsequent non-migratable mode logi
ns must be made by the user who owns the server group. To have a different user
login in non-migratable mode, the ownership of the server group will have to be
changed. This can be done by logging off all current sessions and detaching from
all existing servers in the server group and then having the new user login to
become the new owner.
ORA-00039: error during periodic action
Cause: An unexpected error occurred while executing a periodically invoked
Action: Check the error stack for detailed error information.
ORA-00040: active time limit exceeded - call aborted
Cause: The Resource Manager SWITCH_TIME limit was exceeded.
Action: Reduce the complexity of the update or query, or contact your databa
se administrator for more information.
ORA-00041: active time limit exceeded - session terminated
Cause: The Resource Manager SWITCH_TIME limit was exceeded.
Action: Reduce the complexity of the update or query, or contact your databa
se administrator for more information.
ORA-00042: Unknown Service name string
Cause: An attempt was made to use an invalid application service.
Action: Use a valid service name from SERVICE$ or add a new service using th
e DBMS_SERVICE package.
ORA-00043: remote operation failed
Cause: Execution of the inter-instance operation failed.
Action: Check the status of the target instance. The operation may have part
ially executed. Verify the result of the intended operation.
ORA-00044: timed_statistics must be TRUE when statistics_level is not BASIC
Cause: The user attempted to set timed_statistics to FALSE when statistics_l
evel was not BASIC. timed_statistics is required to be TRUE to collect meaningfu
l statistics when statistics_level is set to TYPICAL or ALL.
Action: Either set timed_statistics to TRUE or set statistics_level to BASIC
.
ORA-00050: operating system error occurred while obtaining an enqueue
Cause: Could not obtain the operating system resources necessary to cover an
oracle enqueue. This is normally the result of an operating system user quota t
hat is too low.
Action: Look up the operating system error in your system documentation and
perform the needed action.
ORA-00051: timeout occurred while waiting for a resource
Cause: Usually due to a dead instance.
Action: Check for any dead, unrecovered instances and recover them.
ORA-00052: maximum number of enqueue resources (string) exceeded
Cause: Ran out of enqueue resources.
Action: Increase the value of the ENQUEUE_RESOURCES initialization parameter
.
ORA-00053: maximum number of enqueues exceeded
Cause: Ran out of enqueue state objects.
Action: Increase the value of the ENQUEUES initialization parameter.
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
Action: Make sure the initialization parameter is in the correct date format
.
ORA-00066: SID string contains an illegal character
Cause: The specified SID contains an illegal character which cannot occur in
an SPFILE setting. Illegal characters include ,#"'=() and whitespace.
Action: Use a SID that does not contain a special character or whitespace.
ORA-00067: invalid value string for parameter string; must be at least string
Cause: The value for the initialization parameter is invalid.
Action: Choose a value as indicated by the message.
ORA-00068: invalid value string for parameter string, must be between string and
string
Cause: The value for the initialization parameter is invalid.
Action: Choose a value as indicated by the message.
ORA-00069: cannot acquire lock -- table locks disabled for string
Cause: A command was issued that tried to lock the table indicated in the me
ssage. Examples of commands that can lock tables are: LOCK TABLE, ALTER TABLE ..
. ADD (...), and so on.
Action: Use the ALTER TABLE ... ENABLE TABLE LOCK command, and retry the com
mand.
ORA-00070: command string is not valid
Cause: An invalid debugger command was specified.
Action: Type HELP to see the list of available commands.
ORA-00071: process number must be between 1 and string
Cause: An invalid process number was specified.
Action: Specify a valid process number.
ORA-00072: process "string" is not active
Cause: An invalid process was specified.
Action: Specify a valid process.
ORA-00073: command string takes between string and string argument(s)
Cause: An incorrect number of arguments was specified.
Action: Specify the correct number of arguments. Type HELP to see the list o
f commands and their syntax.
ORA-00074: no process has been specified
Cause: No debug process has been specified.
Action: Specify a valid process.
ORA-00075: process "string" not found in this instance
Cause: The specified process was not logged on to the current instance.
Action: Specify a valid process.
ORA-00076: dump string not found
Cause: An attempt was made to invoke a dump that does not exist.
Action: Type DUMPLIST to see the list of available dumps.
ORA-00077: dump string is not valid
Cause: An attempt was made to invoke an invalid dump.
Action: Try another dump.
ORA-00078: cannot dump variables by name
Cause: An attempt was made to dump a variable by name on a system that does
not support this feature.
CREATE CONTROLFILE script dumped to the trace file to create a new control file
.
ORA-00217: control file could not be resized for new record types
Cause: The control file was missing some new record types supported by this
release. These record types are automatically added by resizing the contol file
during mount. The resize has failed.
Action: Look in the alert log for the reason that the resize has failed. If
indicated in the alert log, give the control file more space. Otherwise, use the
CREATE CONTROLFILE script dumped to the trace file to create a new control file
.
ORA-00218: block size string of control file 'string' does not match DB_BLOCK_SI
ZE (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 a
n incorrect setting of DB_BLOCK_SIZE, or else might indicate that the control fi
le has either been corrupted or belongs to a different database.
Action: Restore a good copy of the control file. If the control file is know
n to be clean set the DB_BLOCK_SIZE to match control file headers block size val
ue.
ORA-00219: required control file size (string logical blocks) exceeds maximum al
lowable size (string logical blocks)
Cause: An invocation of CREATE DATABASE or CREATE CONTROLFILE was executed s
pecifying a combination of parameters that would require the control file size i
n blocks to exceed the maximum allowable value.
Action: In the case of CREATE DATABASE or CREATE CONTROLFILE, use a differen
t combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MA
XINSTANCES clauses.
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 co
ntrol 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.
ORA-00221: error on write to control file
Cause: An error occurred when writing to one or more of the control files.
Action: See accompanying messages.
ORA-00222: operation would reuse name of a currently mounted control file
Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP CON
TROLFILE command or to cfileSetSnapshotName matches the name of the specified cu
rrently mounted control file.
Action: Retry the operation with a different filename.
ORA-00223: convert file is invalid or incorrect version
Cause: An Oracle7 to Oracle8 convert file contains invalid data or was creat
ed with an different version of the migration utility. This error can also be ca
used by incorrect ORACLE_HOME environment variable when ALTER DATABASE CONVERT c
ommand is issued.
Action: Use a correct version of the convert file or regenerate it with the
migration utility. Make sure that the migration utility is the same version as t
he Oracle8 RDBMS executable and that the ORACLE_HOME environment variable is pro
perly set.
ORA-00224: control file resize attempted with illegal record type (string)
Cause: An attempt was made to expand or shrink the control file by calling c
Action: Re-enter the command with a numeric argument specifying the degree o
f parallelism desired.
ORA-00292: parallel recovery feature not installed
Cause: A parallel recovery was requested when the parallel recovery option i
s not installed.
Action: Delete the PARALLEL clause from the RECOVER command. Also, delete th
e RECOVERY_PARALLELISM parameter in the initialization file.
ORA-00293: control file out of sync with redo log
Cause: The redo log file and control file are out of sync because a non-curr
ent controle file was specified when the instance was started.
Action: Retry the RECOVER command using the current control file, or retry t
he RECOVER command using the USING BACKUP CONTROLFILE clause.
ORA-00294: invalid archivelog format specifier 'string'
Cause: An invalid format specifier was found in the LOG_ARCHIVE_FORMAT initi
alization parameter. The only characters permitted following the % symbol are s,
S, t, and T.
Action: Correct the initialization file and re-start the instance.
ORA-00295: datafile/tempfile number string is invalid, must be between 1 and str
ing
Cause: An invalid file number was specified.
Action: Specify a valid datafile or tempfile number and retry the operation.
ORA-00296: maximum number of files (string) exceeded for RECOVER DATAFILE LIST
Cause: The RECOVER DATAFILE LIST command specified more datafiles than are a
llowed by the DB_FILES initialization parameter. This error occurs when doing re
covery with Recovery Manager, and the instance has been started with a DB_FILES
parameter specifying fewer datafiles than recovery manager needs to recover to s
atisfy the user's RECOVER command.
Action: Re-start the instance with a higher value for DB_FILES.
ORA-00297: must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START
Cause: The RECOVER DATAFILE START command was issued, but no RECOVER DATAFIL
E LIST commands had been issued. This only happens when doing recovery with Reco
very Manager, and is an internal error in Recovery Manager, because Recovery Man
ager should always issue RECOVER DATAFILE LIST before RECOVER DATAFILE START.
Action: Contact customer support
ORA-00298: Missing or invalid attribute value
Cause: A non-zero integer value is required when the following keyword attri
butes are specified: TIMEOUT, EXPIRE, DELAY, NEXT
Action: Correct the syntax and retry the command.
ORA-00299: must use file-level media recovery on data file string
Cause: The control file does not contain an entry for this file, so block me
dia recovery cannot be done.
Action: Restore the data file and perform file-level media recovery.
ORA-00300: illegal redo log block size string specified - exceeds limit of strin
g
Cause: The specified block size of the redo log is greater than the maximum
block size for the operating system.
Action: Create the redo log on a device with a smaller block size
ORA-00301: error in adding log file 'string' - file cannot be created
Cause: The creation of the redo log file failed
Action: Check: 1) there is enough storage space on the device 2) the name of
generation to another online log, but all the other logs need to be archived bef
ore they can be used.
Action: Archive the logs for the thread then retry open.
ORA-00324: log file 'string' translated name 'string' too long, string character
s exceeds string limit
Cause: the translated name for a log file is too long.
Action: Choose a untranslated name that yields a shorter translated name.
ORA-00325: archived log for thread string, wrong thread # string in header
Cause: The archived log is corrupted or for another thread. Can not use the
log for applying redo.
Action: Find correct archived log.
ORA-00326: log begins at change string, need earlier change string
Cause: The archived log supplied for recovery was generated after the log th
at is needed. Can not yet use the log for applying redo.
Action: Find correct archived log.
ORA-00327: log string of thread string, physical size string less than needed st
ring
Cause: A log file has shrunk in size. This is likely to have been caused by
operator or operating system error.
Action: Restore the log file from backup. If backup is not available, drop t
his log and re-create. If the database was shut down cleanly, no further action
should be required; otherwise incomplete recovery may be required.
ORA-00328: archived log ends at change string, need later change string
Cause: The archived log supplied for recovery was generated before the log t
hat is needed. Can not use the log for applying redo.
Action: Find correct archived log.
ORA-00329: archived log begins at change string, need change string
Cause: The archived log is not the correct log. An earlier log is needed.
Action: Restore the correct log file.
ORA-00330: archived log ends at change string, need change string
Cause: The archived log is not the correct log. A later log is needed.
Action: Restore the correct log file.
ORA-00331: log version string incompatible with ORACLE version string
Cause: The log was written by incompatible version of Oracle.
Action: Recover the database with the compatible software, shut it down clea
nly, then restart with current software.
ORA-00332: archived log is too small - may be incompletely archived
Cause: The log is smaller than the space allocated in it. May be the result
of a shutdown abort while it was being written by the archiver.
Action: Get a complete version of this log and use it for recovery. There sh
ould either be an online version of it or a copy that was successfully archived.
ORA-00333: redo log read error block string count string
Cause: An IO error occurred while reading the log described in the accompany
ing error.
Action: Restore accessibility to file, or get another copy of the file.
ORA-00334: archived log: 'string'
Cause: Reporting filename for details of another error
Action: See associated error messages
ORA-00335: online log string: No log with this number, log does not exist
Cause: Reporting filename for details of another error
Action: See associated error messages
ORA-00336: log file size string blocks is less than minimum string blocks
Cause: The log file size as specified in create database is too small.
Action: Increase the log file size.
ORA-00337: log file 'string' does not exist and no size specified
Cause: An attempt to add a log found neither an existing file nor a size for
creating the file.
Action: Specify a size for the log file.
ORA-00338: log string of thread string is more recent than control file
Cause: The control file change sequence number in the log file is greater th
an the number in the control file. This implies that the wrong control file is b
eing used. Note that repeatedly causing this error can make it stop happening wi
thout correcting the real problem. Every attempt to open the database will advan
ce the control file change sequence number until it is great enough.
Action: Use the current control file or do backup control file recovery to m
ake the control file current. Be sure to follow all restrictions on doing a back
up control file recovery.
ORA-00339: archived log
Cause: The archived
hat has never been used
to be the current log.
Action: Restore the
ORA-00347: log string of thread string, expected block size string doesn't match
string
Cause: On header read the blocksize indicated in the control file did not ma
tch the blocksize contained in the log file.
Action: Restore correct file or reset logs.
ORA-00348: single-process redo failure. Must abort instance
Cause: A failure occurred during a critical portion of the log code during s
ingle process operation. This error does not occur during normal multi-process o
peration.
Action: Shutdown abort and warmstart the database.
ORA-00349: failure obtaining block size for 'string'
Cause: The operating system was unable to determine the blocksize for the gi
ven filename.
Action: Consult the accompanying error message, and correct the device or sp
ecify another filename.
ORA-00350: log string of instance string (thread string) needs to be archived
Cause: The command cannot be done because the log has not been archived, and
media recovery has been enabled.
Action: Archive the log or disable media recovery. If the command supports a
n UNARCHIVED option then it can be used. However this may result in making backu
ps unuseable, and forcing the drop of some offline files.
ORA-00351: recover-to time invalid
Cause: The time specified in a recover-until statement must be after January
1st 1988.
Action: Specify a time after January 1st 1988.
ORA-00352: all logs for thread string need to be archived - cannot enable
Cause: Attempting to enable a thread with all logs needing to be archived, a
nd media recovery has been enabled. There is no log that can be made the new cur
rent log for the thread.
Action: Archive a log for the thread or disable media recovery.
ORA-00353: log corruption near block string change string time string
Cause: Some type of redo log corruption has been discovered. This error desc
ribes the location of the corruption. Accompanying errors describe the type of c
orruption.
Action: Do recovery with a good version of the log or do incomplete recovery
up to the indicated change or time.
ORA-00354: corrupt redo log block header
Cause: The block header on the redo block indicated by the accompanying erro
r, is not reasonable.
Action: Do recovery with a good version of the log or do time based recovery
up to the indicated time. If this happens when archiving, archiving of the prob
lem log can be skipped by clearing the log with the UNARCHIVED option. This must
be followed by a backup of every datafile to insure recoverability of the datab
ase.
ORA-00355: change numbers out of order
Cause: A change number found in the redo log is lower than a previously enco
untered change number. The log is corrupted in some way. The corruption may be a
t the earlier change or at this one.
Action: Do recovery with a good version of the log or do time based recovery
up to the indicated time.
ORA-00356: inconsistent lengths in change description
Cause: A change record in the redo log contains lengths that do not add up t
o a consistent value. The log is corrupted in some way.
Action: Do recovery with a good version of the log or do time based recovery
up to the indicated time.
ORA-00357: too many members specified for log file, the maximum is string
Cause: An add logfile or add logfile member command would result in a log wi
th too many members. The number of members is set when the database is created.
Action: Use fewer log file members.
ORA-00358: Too many file members specified, the maximum is string
Cause: A create or alter statement specified too many members in a parenthes
ised file list.
Action: Specify a number of file members that is within the port-defined lim
it.
ORA-00359: logfile group string does not exist
Cause: An add logfile member or drop logfile request specified a logfile gro
up number that does not exist.
Action: Check the configuration of the log files and reissue the command.
ORA-00360: not a logfile member: string
Cause: A filename was given to drop logfile member that is not a part of the
database, or which is a data file.
Action: Supply a valid logfile member name.
ORA-00361: cannot remove last log member string for group string
Cause: An attempt has been made to remove the last member of a log file grou
p.
Action: If desired, delete the entire log, by using DROP LOGFILE.
ORA-00362: member is required to form a valid logfile in group string
Cause: A request to drop a logfile member was denied because it would remove
data required to form a complete logfile.
Action: If desired, delete the entire log (after archiving if required), by
using DROP LOGFILE;
ORA-00363: log is not the archived version
Cause: d by failing to list the current log of an enabled thread in a CREATE
CONTROLFILE command.
Action: Find the archived version of the log and supply its name. If this is
media recovery immediately following a CREATE CONTROLFILE, be sure the current
log for this thread was included.
ORA-00364: cannot write header to new log member
Cause: An i/o error occurred when attempting to write the header to a log me
mber that is being added to an existing group.
Action: See accompanying errors. Fix problem or use another file.
ORA-00365: the specified log is not the correct next log
Cause: The specified log failed to pass checks to ensure it corresponds to t
he log that was just applied. This is probably the result of using a log that wa
s generated against a cold backup image of the database.
Action: Find the log that was generated by this copy of the database and giv
e that filename to recovery.
ORA-00366: log string of thread string, checksum error in the file header
Cause: The file header for the redo log contains a checksum that does not ma
tch the value calculated from the file header as read from disk. This means the
file header is corrupted
ORA-00369: Current log of thread string not useable and other log being cleared
Cause: Attempt to open thread failed because it is necessary to switch redo
generation to another online log, but all the other logs are being cleared or ne
ed to be archived before they can be used.
Action: If the ALTER DATABASE CLEAR LOGFILE command is still active then wai
t for it to complete. Otherwise reissue the CLEAR command. If there are other on
line logs for the thread, that are not being cleared, then archive the logs.
ORA-00370: potential deadlock during kcbchange operation
Cause: Error code used internally by software. Should never be reported
Action: Treat as internal error. See error 600.
ORA-00371: not enough shared pool memory, should be atleast string bytes
Cause: Init.ora parameter shared_pool_size is too small
Action: Increase the parameter value
ORA-00372: file string cannot be modified at this time
Cause: attempting to modify the contents of a file that cannot be modified.
The file is most likely part of a read only tablespace but may be in the process
of going offline, or the database may be in the process of closing.
Action: check the status of the file and its tablespace
ORA-00373: online log version string incompatible with ORACLE version string
Cause: The online log was written by incompatible version of Oracle. Can occ
ur when the log file was created by either a new or older version of Oracle.
Action: Recover the database with the compatible software, shut it down clea
nly, then restart with current software.
ORA-00374: parameter db_block_size = string invalid ; must be a multiple of stri
ng in the range [string..string]
Cause: invalid value for db_block_size parameter
Action: adjust parameter and restart
ORA-00376: file string cannot be read at this time
Cause: attempting to read from a file that is not readable. Most likely the
file is offline.
Action: Check the state of the file. Bring it online
ORA-00377: Frequent backups of file string causing write operation to stall
Cause: Backups are occurring too frequently on this file. Each time a new ba
ckup is started for a file, any writes which have been previously issued (but no
t completed) have to be re-issued. If hot backups are started very, very frequen
tly, it is possible that some writes will be re-issued repeatedly and never comp
lete.
Action: Increase the interval between begin hot-backup commands for this fil
e.
ORA-00409: COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MAN
AGEMENT
Cause: This is due to migrating from an older release of Oracle with tablesp
aces created using AUTO SEGMENT SPACE MANAGEMENT. To open the database, the COMP
ATIBLE parameter needs to be set to the specified value.
Action: Shutdown and startup with the specified compatibility setting.
ORA-00437: ORACLE feature is not licensed. Contact Oracle Corp. for assistance
Cause: ORACLE feature is not licensed.
Action: Contact ORACLE for assistance.
ORA-00438: string Option not installed
Cause: The specified option is not installed.
Action: Purchase and install the option.
ORA-00439: feature not enabled: string
Cause: The specified feature is not enabled.
Action: Do not attempt to use this feature.
ORA-00443: background process "string" did not start
Cause: The specified process did not start.
Action: Ensure that the executable image is in the correct place with the co
rrect protections, and that there is enough memory.
ORA-00444: background process "string" failed while starting
Cause: Usually due to a bad (or non-existent) background process image.
Action: Get a good background process image.
ORA-00445: background process "string" did not start after string seconds
Cause: The specified process did not start after the specified time.
Action: Ensure that the background did not die and leave a trace file.
ORA-00446: background process started when not expected
Cause: The background process specified started up AFTER the RDBMS was alrea
dy running.
Action: If nobody at your site started the process, then this is an internal
error.
ORA-00447: fatal error in background process
Cause: One of the background processes died unexpectedly.
Action: Warm start the system.
ORA-00448: normal completion of background process
Cause: One of the background processes completed normally (i.e. exited). The
background process thinks that somebody asked it to exit.
Action: Warm start the system.
ORA-00449: background process 'string' unexpectedly terminated with error string
Cause: A foreground process needing service from a background process has di
scovered the process died.
Action: Consult the error code, and the trace file for the process.
ORA-00450: background process 'string' did not start
Cause: The specified process did not start.
Action: Consult the error code, and the trace file for the process.
ORA-00451: foreground process died unexpectedly
Cause: The foreground process for the new connection did not start.
Action: Reconnect to Oracle.
Cause: Cannot start process in a requested processor group when the NUMA fea
ture is disabled.
Action: Start the process without requesting a NUMA processor group.
ORA-00567: Requested processor group string is too large (maximum string)
Cause: The process could not be started in the requested processor group.
Action: Start the process in another processor group.
ORA-00568: Maximum number of interrupt handlers exceeded
Cause: User specified too many ^c handlers
Action: Remove some old handlers.
ORA-00569: Failed to acquire global enqueue.
Cause: A prior error occurred on one of the instances in the cluster. Typica
lly errors are caused by shared pool resource contention.
Action: Check for and resolve prior errors on all instances in the cluster.
If there is shared pool resource contention, increase the SHARED_POOL_SIZE, DML_
LOCKS, PROCESSES, TRANSACTIONS, CLUSTER_DATABASE_INSTANCES and PARALLEL_MAX_SERV
ERS initialization parameters.
ORA-00600: internal error code, arguments: [string], [string], [string], [string
], [string], [string], [string], [string], [string], [string], [string], [string
]
Cause: This is the generic internal error number for Oracle program exceptio
ns. This indicated that a process encountered an exceptional condition.
Action: Report as a bug - the first argument is the internal error number.
ORA-00601: cleanup lock conflict
Cause: PMON process runs into lock conflict trying to recovery processes
Action: This is trapped internally, no action necessary
ORA-00602: internal programming exception
Cause: Internal programming exception
Action: Report as bug
ORA-00603: ORACLE server session terminated by fatal error
Cause: An ORACLE server session was in an unrecoverable state.
Action: Login to ORACLE again so a new server session will be created
ORA-00604: error occurred at recursive SQL level string
Cause: An error occurred while processing a recursive SQL statement (a state
ment applying to internal dictionary tables).
Action: If the situation described in the next error on the stack can be cor
rected, do so; otherwise contact Oracle Support.
ORA-00606: Internal error code
Cause: A call to deferred upi functions was made in non deferred mode
Action: Report as a bug.
ORA-00607: Internal error occurred while making a change to a data block
Cause: An internal error or memory exception occurred while Oracle was apply
ing redo to a data block.
Action: call Oracle Support
ORA-00608: testing error [string] [string] [string] [string] [string]
Cause: Internal error reserved for testing.
Action: call Oracle Support
ORA-00609: could not attach to incoming connection
Cause: Oracle process could not answer incoming connection
Action: If the situation described in the next error on the stack can be cor
rected, do so; otherwise contact Oracle Support.
ORA-00610: Internal error code
Cause: Oracle process started too late
Action: This error should never be seen by the customer. Contact Oraclce Sup
port
ORA-00700: soft internal error, arguments: [string], [string], [string], [string
], [string], [string], [string], [string]
Cause: Internal inconsitency that will not crash a process
Action: Report as a bug - the first argument is the internal error.
ORA-00701: object necessary for warmstarting database cannot be altered
Cause: Attempt to alter or drop a database object (table, cluster, or index)
which are needed for warmstarting the database.
Action: None
ORA-00702: bootstrap verison 'string' inconsistent with version 'string'
Cause: The reading version of the boostrap is incompatible with the current
bootstrap version.
Action: Restore a version of the software that is compatible with this boots
trap version.
ORA-00703: maximum number of row cache instance locks exceeded
Cause: There are not enough row cache enqueues.
Action: Increase the row cache enqueue parameter and warm start the system.
ORA-00704: bootstrap process failure
Cause: Failure in processing bootstrap data - see accompanying error.
Action: Contact your customer support representative.
ORA-00705: inconsistent state during start up; shut down the instance, then rest
art it
Cause: A previous attempt to start an instance was terminated.
Action: Shut down the instance completely, then restart it.
ORA-00706: error changing format of file 'string'
Cause: An attempt to change the block0 format of the specified file failed b
ecause the file is read-only or offline.
Action: Make the file read-write or bring the file online and set the BLK0_F
MTCHG event.
ORA-00710: new tablespace name is the same as the old tablespace name
Cause: An attempt to rename a tablespace failed because the new name is the
same as the old name.
Action: No action required.
ORA-00711: new tablespace name is invalid
Cause: An attempt to rename a tablespace failed because the new name is inva
lid.
Action: Choose a valid new name and retry the command.
ORA-00712: cannot rename system tablespace
Cause: An attempt to rename the system tablespace failed.
Action: No action required.
ORA-00720: ALTER DATABASE RESET COMPATIBILITY command has been de-supported
Cause: ALTER DATABASE RESET COMPATIBILITY command has been de-supported sinc
e Oracle 10i.
Action: Do not set MEMORY_TARGET to a value below the current value without
first shrinking the individual memory components.
ORA-00847: MEMORY_TARGET/MEMORY_MAX_TARGET and LOCK_SGA cannot be set together
Cause: MEMORY_TARGET/MEMORY_MAX_TARGET was set to a non-zero value and LOCK_
SGA was also set
Action: Do not set MEMORY_TARGET or MEMORY_MAX_TARGET if LOCK_SGA is set to
TRUE.
ORA-00848: STATISTICS_LEVEL cannot be set to BASIC with SGA_TARGET or MEMORY_TAR
GET
Cause: STATISTICS_LEVEL of BASIC was incompatible with SGA_TARGET and MEMORY
_TARGET.
Action: Fix the incompatible parameter setting. Set STATISTICS_LEVEL to TYPI
CAL or ALL to use SGA_TARGET or MEMORY_TARGET.
ORA-00849: SGA_TARGET string cannot be set to more than MEMORY_MAX_TARGET string
.
Cause: SGA_TARGET value was more than MEMORY_MAX_TARGET value.
Action: Set SGA_TARGET to be less than MEMORY_MAX_TARGET.
ORA-00850: PGA_AGGREGATE_TARGET string cannot be set to more than MEMORY_MAX_TAR
GET string.
Cause: PGA_AGGREGATE_TARGET value was more than MEMORY_MAX_TARGET value.
Action: Set PGA_AGGREGATE_TARGET to be less than MEMORY_MAX_TARGET.
ORA-00851: SGA_MAX_SIZE string cannot be set to more than MEMORY_TARGET string.
Cause: SGA_MAX_SIZE value was more than MEMORY_TARGET value.
Action: Set SGA_MAX_SIZE to be less than MEMORY_TARGET.