Oracle错误代码超级大全

ORACLE错误代码超级大全

ORA-00000: normal, successful completion 原因： Normal exit. 解决： None.

ORA-00001: unique constraint (string.string) violated

原因： An UPDATE or INSERT statement attempted to insert a duplicate key. For Trusted Oracle configured in DBMS MAC mode, you may see this message if a duplicate entry exists at a different level.

解决： Either remove the unique restriction or do not insert the key. ORA-00017: session requested to set trace event

原因： The current session was requested to set a trace event by another session. 解决： This is used internally; no action is required. ORA-00018: maximum number of sessions exceeded 原因： All session state objects are in use.

解决： Increase the value of the SESSIONS initialization parameter. ORA-00019: maximum number of session licenses exceeded 原因： All licenses are in use.

解决： Increase the value of the LICENSE MAX SESSIONS initialization parameter. ORA-00020: maximum number of processes (string) exceeded 原因： All process state objects are in use.

解决： Increase the value of the PROCESSES initialization parameter. ORA-00021: session attached to some other process; cannot switch session 原因： The user session is currently used by others.

解决： Do not switch to a session attached to some other process. ORA-00022: invalid session ID; access denied 原因： Either the session specified does not exist or the caller does not have the privilege to access it. 解决： Specify a valid session ID that you have privilege to access, that is either you own it or you have the CHANGE_USER privilege.

ORA-00023: session references process private memory; cannot detach session

原因： An attempt was made to detach the current session when it contains references to process private memory.

解决： A session may contain references to process memory (PGA) if it has an open network connection, a very large context area, or operating system privileges. To allow the detach, it may be necessary to close the session\database links and/or cursors. Detaching a session with operating system privileges is always disallowed.

ORA-00024: logins from more than one process not allowed in single-process mode

原因： Trying to login more than once from different processes for ORACLE started in single-process mode.

解决： Logoff from the other process. ORA-00025: failed to allocate string 原因： Out of memory.

解决： Restart with larger sga heap.

ORA-00026: missing or invalid session ID

第1页

原因： Missing or invalid session ID string for ALTER SYSTEM KILL SESSION. 解决： Retry with a valid session ID. ORA-00027: cannot kill current session

原因： Attempted to use ALTER SYSTEM KILL SESSION to kill the current session. 解决： None.

ORA-00028: your session has been killed

原因： A privileged user has killed your session and you are no longer logged on to the database. 解决： Login again if you wish to continue working. ORA-00029: session is not a user session 原因： The session ID specified in an ALTER SYSTEM KILL SESSION command was not a user session (for example, recursive, etc.). 解决： Retry with a user session ID.

ORA-00030: User session ID does not exist.

原因： The user session ID no longer exists, probably because the session was logged out. 解决： Use a valid session ID.

ORA-00031: session marked for kill

原因： The session specified in an ALTER SYSTEM KILL SESSION command cannot be killed immediately (because it is rolling back or blocked on a network operation), but it has been marked for kill. This means it will be killed as soon as possible after its current uninterruptable operation is done.

解决： No action is required for the session to be killed, but further executions of the ALTER SYSTEM KILL SESSION command on this session may cause the session to be killed sooner. ORA-00032: invalid session migration password

原因： The session migration password specified in a session creation call was invalid (probably too long).

解决： Retry with a valid password (less than 30 chars). ORA-00033: current session has empty migration password

原因： An attempt was made to detach or clone the current session and it has an empty migration password. This is not allowed.

解决： Create the session with a non-empty migration password. ORA-00034: cannot string in current PL/SQL session

原因： An attempt was made to issue a commit or rollback from a PL/SQL object (procedure, function, package) in a session that has this disabled (by \session disable commit in procedure\

解决： Enable commits from PL/SQL in this session, or do not attempt to use commit or rollback in PL/SQL when they are disabled in the current session.

ORA-00036: maximum number of recursive SQL levels (string) exceeded

原因： An attempt was made to go more than the specified number of recursive SQL levels. 解决： Remove the recursive SQL, possibly a recursive trigger.

ORA-00037: cannot switch to a session belonging to a different server group 原因： An attempt was made to switch to a session in a different server group. This is not allowed. 解决： Make sure the server switches to a session that belongs to its server group. ORA-00038: Cannot create session: server group belongs to another user 原因： An attempt was made to create a non-migratable session in a server group that is owned by

第2页

a different user.

解决： 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 logins 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-00040: active time limit exceeded - call aborted

原因： The Resource Manager SWITCH_TIME limit was exceeded.

解决： Reduce the complexity of the update or query, or contact your database administrator for more information.

ORA-00041: active time limit exceeded - session terminated

原因： The Resource Manager SWITCH_TIME limit was exceeded.

解决： Reduce the complexity of the update or query, or contact your database administrator for more information.

ORA-00042: Unknown Service name string

原因： An attempt was made to use an invalid application service.

解决： Use a valid service name from SERVICE$ or add a new service using the DBMS_SERVICE package.

ORA-00050: operating system error occurred while obtaining an enqueue

原因： Could not obtain the operating system resources necessary to cover an oracle enqueue. This is normally the result of an operating system user quota that is too low.

解决： Look up the operating system error in your system documentation and perform the needed action.

ORA-00051: timeout occurred while waiting for a resource 原因： Usually due to a dead instance.

解决： Check for any dead, unrecovered instances and recover them. ORA-00052: maximum number of enqueue resources (string) exceeded 原因： Ran out of enqueue resources.

解决： Increase the value of the ENQUEUE_RESOURCES initialization parameter. ORA-00053: maximum number of enqueues exceeded 原因： Ran out of enqueue state objects.

解决： Increase the value of the ENQUEUES initialization parameter. ORA-00054: resource busy and acquire with NOWAIT specified 原因： Resource interested is busy. 解决： Retry if necessary.

ORA-00055: maximum number of DML locks exceeded 原因： Ran out of DML lock state objects.

解决： Increase the value of the DML_LOCKS initialization parameter and warm start. ORA-00056: DDL lock on object \ 原因： An attempt was made to acquire a DDL lock that is already locked. 解决： This happens if you attempt to drop a table that has parse locks on it. ORA-00057: maximum number of temporary table locks exceeded

原因： The number of temporary tables equals or exceeds the number of temporary table locks.

第3页

Temporary tables are often created by large sorts.

解决： Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and warm start.

ORA-00058: DB_BLOCK_SIZE must be string to mount this database (not string)

原因： DB_BLOCK_SIZE initialization parameter is wrong for the database being mounted. It does not match the value used to create the database.

解决： Fix the value of the DB_BLOCK_SIZE parameter or mount a database that matches the value.

ORA-00059: maximum number of DB_FILES exceeded

原因： The value of the DB_FILES initialization parameter was exceeded. 解决： Increase the value of the DB_FILES parameter and warm start. ORA-00060: deadlock detected while waiting for resource

原因： Transactions deadlocked one another while waiting for resources.

解决： Look at the trace file to see the transactions and resources involved. Retry if necessary. ORA-00061: another instance has a different DML_LOCKS setting 原因： The shared instance being started is using DML locks, and the running instances are not, or vice-versa.

解决： Ensure that all instances\as non-zero.

ORA-00062: DML full-table lock cannot be acquired; DML_LOCKS is 0

原因： The instance was started with DML_LOCKS = 0, and the statement being executed needs a full-table lock (S, X, or SSX).

解决： Restart the instance with DML_LOCKS not equal to zero, and reexecute the statement. ORA-00063: maximum number of log files exceeded string

原因： The number of log files specificied exceeded the maximum number of log files supported in this release. 解决： Re-create the control file with the highest number of log files no greater than the maximum supported in this release.

ORA-00064: object is too large to allocate on this O/S (string,string)

原因： An initialization parameter was set to a value that required allocating more contiguous space than can be allocated on this operating system. 解决： Reduce the value of the initialization parameter. ORA-00065: initialization of FIXED_DATE failed

原因： The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss. 解决： Make sure the initialization parameter is in the correct date format. ORA-00067: invalid value string for parameter string; must be at least string 原因： The value for the initialization parameter is invalid. 解决： Choose a value as indicated by the message.

ORA-00068: invalid value string for parameter string, must be between string and string 原因： The value for the initialization parameter is invalid. 解决： Choose a value as indicated by the message.

ORA-00069: cannot acquire lock -- table locks disabled for string

原因： A command was issued that tried to lock the table indicated in the message. Examples of commands that can lock tables are: LOCK TABLE, ALTER TABLE ... ADD (...), and so on.

第4页

解决： Use the ALTER TABLE ... ENABLE TABLE LOCK command, and retry the command. ORA-00070: command string is not valid

原因： An invalid debugger command was specified. 解决： Type HELP to see the list of available commands. ORA-00071: process number must be between 1 and string 原因： An invalid process number was specified. 解决： Specify a valid process number. ORA-00072: process \ 原因： An invalid process was specified. 解决： Specify a valid process.

ORA-00073: command string takes between string and string argument(s) 原因： An incorrect number of arguments was specified. 解决： Specify the correct number of arguments. Type HELP to see the list of commands and their syntax.

ORA-00074: no process has been specified 原因： No debug process has been specified. 解决： Specify a valid process.

ORA-00075: process \

原因： The specified process was not logged on to the current instance. 解决： Specify a valid process. ORA-00076: dump string not found

原因： An attempt was made to invoke a dump that does not exist. 解决： Type DUMPLIST to see the list of available dumps. ORA-00077: dump string is not valid

原因： An attempt was made to invoke an invalid dump. 解决： Try another dump.

ORA-00078: cannot dump variables by name

原因： An attempt was made to dump a variable by name on a system that does not support this feature.

解决： Try the PEEK command.

ORA-00079: variable string not found

原因： An attempt was made to dump a variable that does not exist. 解决： Use a valid variable name.

ORA-00080: invalid global area specified by level string 原因： An attempt was made to dump an invalid global area.

解决： Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. Use to dump global area as well as bytes for every pointer; must be a multiple of 4. ORA-00081: address range [string, string) is not readable

原因： An attempt was made to read/write an invalid memory address range. 解决： Try another address or length.

ORA-00082: memory size of string is not in valid set of [1], [2], [4]stringstringstringstringstring 原因： An invalid length was specified for the POKE command. 解决： Use a valid length (either 1, 2, 4, or possibly 8). ORA-00083: warning: possibly corrupt SGA mapped

第5页

原因： Even though there may be SGA corruptions, the SGA was mapped. 解决： Use the DUMPSGA command to dump the SGA. ORA-00084: global area must be PGA, SGA, or UGA

原因： An attempt was made to dump an invalid global area. 解决： Specify either PGA, SGA, or UGA. ORA-00085: current call does not exist

原因： An invalid attempt was made to dump the current call heap. 解决： Wait until the process starts a call. ORA-00086: user call does not exist

原因： An invalid attempt was made to dump the user call heap. 解决： Wait until the process starts a call.

ORA-00087: command cannot be executed on remote instance

原因： Cluster database command issued for non cluster database ORADEBUG command. 解决： Issue the command without the cluster database syntax. ORA-00088: command cannot be executed by shared server 原因： Debug command issued on shared server.

解决： Reissue the command using a dedicated server.

ORA-00089: invalid instance number in ORADEBUG command

原因： An invalid instance number was specified in a cluster database ORADEBUG command. 解决： Reissue the command with valid instance numbers.

ORA-00090: failed to allocate memory for cluster database ORADEBUG command 原因： Could not allocate memory needed to execute cluster database oradebug. 解决： Reissue the command on each instance with single-instance oradebug. ORA-00091: LARGE_POOL_SIZE must be at least string

原因： The value of LARGE_POOL_SIZE is below the minimum size. 解决： Increase the value of LARGE_POOL_SIZE past the minimum size.

ORA-00092: LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC

原因： The value of LARGE_POOL_SIZE is less than the value of LARGE_POOL_MIN_ALLOC.

解决： Increase the value of LARGE_POOL_SIZE past the value of LARGE_POOL_MIN_ALLOC.

ORA-00093: %s must be between string and string 原因： The parameter value is not in a valid range.

解决： Modify the parameter value to be within the specified range. ORA-00094: %s requires an integer value 原因： The parameter value is not an integer.

解决： Modify the parameter value to be an integer.

ORA-00096: invalid value string for parameter string, must be from among string 原因： The value for the initialization parameter is invalid. 解决： Choose a value as indicated by the message.

ORA-00097: use of Oracle SQL feature not in SQL92 string Level 原因： Usage of Oracle\解决： none

ORA-00100: no data found

第6页

原因： An application made reference to unknown or inaccessible data.

解决： Handle this condition within the application or make appropriate modifications to the application code. NOTE: If the application uses Oracle-mode SQL instead of ANSI-mode SQL, ORA-01403 will be generated instead of ORA-00100.

ORA-00101: invalid specification for system parameter DISPATCHERS 原因： The syntax for the DISPATCHERS parameter is incorrect. 解决： Refer to the manual for correct syntax.

ORA-00102: network protocol string cannot be used by dispatchers

原因： The network specified in DISPATCHERS does not have the functionality required by the dispatchers.

解决： Refer to the manual on network protocols supported by the dispatchers. ORA-00103: invalid network protocol; reserved for use by dispatchers

原因： The network specified in the SQL*Net connect string is reserved for use by the dispatchers.

解决： Specify other network protocols in the connection string.

ORA-00104: deadlock detected; all public servers blocked waiting for resources

原因： All available public servers are servicing requests that require resources locked by a client which is unable to get a public server to release the resources. 解决： Increase the limit for the system parameter MAX_SHARED_SERVERS as the system will automaticaly start up new servers to break the deadlock until the number of servers reaches the value specified in MAX_SHARED_SERVERS. ORA-00105: too many dispatcher configurations

原因： Too many dispatcher configurations have been specified. No more can be added. 解决： Consolidate the dispatcher configurations if possible.

ORA-00106: cannot startup/shutdown database when connected to a dispatcher

原因： An attempt was made to startup/shutdown database when connected to a shared server via a dispatcher.

解决： Re-connect as user INTERNAL without going through the dispatcher. For most cases, this can be done by connect to INTERNAL without specifying a network connect string. ORA-00107: failed to connect to ORACLE listener process

原因： Most likely due to the fact that ORACLE listener has not been started.

解决： Start ORACLE listener if it has not been started. Or else contact your ORACLE representative.

ORA-00108: failed to set up dispatcher to accept connection asynchronously

原因： Most likely due to the fact that the network protocol used by the the dispatcher does not support aynchronous operations.

解决： Contact your ORACLE representative.

ORA-00109: invalid value for attribute string: string

原因： The value specified for the attribute was incorrect. 解决： Refer to the manual for the proper values.

ORA-00110: invalid value string for attribute string, must be between string and string 原因： The value specified for the attribute was incorrect. 解决： Specify a value within the range allowed. ORA-00111: invalid attribute string

第7页

原因： The specified attribute was not recognized.

解决： Refer to the manual for the proper keyword to use to specify a dispatcher attribute. ORA-00112: value of string is null

原因： The attribute was specified with no value. 解决： Specify a non-null value.

ORA-00113: protocol name string is too long

原因： A protocol name specified in the DISPATCHERS system parameter is too long. 解决： Use a valid protocol name for the DISPATCHERS value.

ORA-00114: missing value for system parameter SERVICE_NAMES

原因： No value was specified for the SERVICE_NAMES system parameter, nor for the DB_NAME parameter.

解决： Add an SERVICE_NAMES or DB_NAME definition to the INIT.ORA file. By default, SERVICE_NAMES is the value of DB_NAME unless SERVICE_NAMES is explicitly specified. ORA-00115: connection refused; dispatcher connection table is full

原因： A connection request was refused by a dispatcher because the dispatcher cannot support any more connections.

解决： Connect to a different dispatcher, or use a dedicated server. ORA-00116: SERVICE_NAMES name is too long

原因： A service name specified in the SERVICE_NAMES system parameter is too long. 解决： Use a shorter name in the SERVICE_NAMES value (<= 255 chars). ORA-00117: PROTOCOL, ADDRESS or DESCRIPTION must be specified 原因： PROTOCOL, ADDRESS or DESCRIPTION was not specified.

解决： Use one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.

ORA-00118: Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified 原因： More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified.

解决： Use only one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.

ORA-00119: invalid specification for system parameter string 原因： The syntax for the specified parameter is incorrect.

解决： Refer to the Oracle Reference Manual for the correct syntax. ORA-00122: cannot initialize network configuration 原因： ORACLE could not initialize SQL*Net version 2. 解决： Check the error stack for detailed information. ORA-00123: idle public server terminating

原因： Too many idle servers were waiting on the common queue. 解决： This error is used internally, no action is required. ORA-00125: connection refused; invalid presentation

原因： The PRESENTATION in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.

解决： Correct the PRESENTATION specified in the TNS address. ORA-00126: connection refused; invalid duplicity

原因： The DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.

第8页

解决： Correct the DUPLICITY specified in the TNS address. ORA-00127: dispatcher string does not exist

原因： There is currently no dispatcher running with the specified name.

解决： Retry with a name of the form \ORA-00128: this command requires a dispatcher name 原因： Wrong syntax for ALTER SYSTEM SHUTDOWN

解决： Use correct syntax: ALTER SYSTEM SHUTDOWN [ IMMEDIATE ] \ORA-00129: listener address validation failed \

原因： An error was encountered while validating the listener address. 解决： Resolve error or contact your ORACLE representative. ORA-00130: invalid listener address \

原因： The listener address specification is not valid.

解决： Make sure that all fields in the listener address (protocol, port, host, key, ...) are correct. ORA-00131: network protocol does not support registration \ 原因： The specified protocol does not support async notification.

解决： Refer to the manual for information on supported network protocols. ORA-00132: syntax error or unresolved network name \ 原因： Listener address has syntax error or cannot be resolved.

解决： If a network name is specified, check that it corresponds to an entry in TNSNAMES.ORA or other address repository as configured for your system. Make sure that the entry is syntactically correct.

ORA-00133: value of string is too long

原因： The value specified for the attribute was too long.

解决： Use shorter names and keywords or remove unneeded blanks. ORA-00134: invalid DISPATCHERS specification #string

原因： The syntax for the n-th DISPATCHERS specification was incorrect. 解决： Refer to the Oracle Reference Manual for the correct syntax. ORA-00150: duplicate transaction ID

原因： Attempted to start a new transaction with an ID already in use by an existing transaction. 解决： Check your application. ORA-00151: invalid transaction ID

原因： The specified transaction ID does not correspond to an existing valid transaction. 解决： Check your application.

ORA-00152: current session does not match requested session

原因： The current session is not the same as the session that was passed into a upixado() call. 解决： Check your application.

ORA-00153: internal error in XA library

原因： The XA library could not access thread-specific pointers. 解决： Contact customer support.

ORA-00154: protocol error in transaction monitor

原因： The transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended.

解决： Contact the transaction monitor customer support.

ORA-00155: cannot perform work outside of global transaction

第9页

原因： The application tried to perform some work on either an Oracle 7.3 server or an Oracle8 server with local transactions disabled while outside of a global transaction.

解决： Check if the application is connected to an Oracle 7.3 server. The Transaction monitor must not return a NULL XID on an AX_REG call when the resource manager is Oracle 7.3. If the application is connected to an Oracle8 server, either set nolocal=f in the xa_open string or start a global transaction prior to attempting the work.

ORA-00160: global transaction length string is greater than maximum (string)

原因： An external global transaction ID with a too large length field was passed in. 解决： Report the problem to your external transaction coordinator vendor.

ORA-00161: transaction branch length string is illegal (maximum allowed string)

原因： An external transaction branch ID with a length either too large or 0 was passed in. 解决： Report the problem to your external transaction coordinator vendor. ORA-00162: external dbid length string is greater than maximum (string) 原因： An external database name with too large a length field was passed in. 解决： Report the problem to your external transaction coordinator vendor.

ORA-00163: internal database name length string is greater than maximum (string) 原因： An internal database name with a too large length field was passed in. 解决： Report the problem to your external transaction coordinator vendor.

ORA-00164: distributed autonomous transaction disallowed within migratable distributed transaction

原因： A request was made by the application to start a distributed autonomous transaction when the application was in a migratable distributed transaction.

解决： Roll back or commit the current distributed transaction first.

ORA-00165: migratable distributed autonomous transaction with remote operation is not allowed 原因： A request was made by the application to start a migratable distributed autonomous transaction with remote operation. 解决： none

ORA-00166: remote/local nesting level is too deep 原因： Too many remote table operations required a reverse trip back to the local site, for example to execute a local function on a remote table.

解决： Rearrange the query or co-locate the functions with the tables. ORA-00200: control file could not be created

原因： It was not possible to create the control file.

解决： Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again.

ORA-00201: control file version string incompatible with ORACLE version string 原因： The control file was created by incompatible software.

解决： Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release. ORA-00202: control file: \

原因： This message reports the name file involved in other messages. 解决： See associated error messages for a description of the problem. ORA-00203: using the wrong control files

原因： The mount ID in the control file is not the same as the mount ID in the control file used by

第10页

the first instance to mount this database. The control files are for the same database but they are not the same files. Most likely one instance is using a backup control file. 解决： Check that the correct control files were specified.

ORA-00204: error in reading (block string, # blocks string) of control file 原因： A disk I/O failure was detected on reading the control file.

解决： Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk.

ORA-00205: error in identifying control file, check alert log for more info 原因： The system could not find a control file of the specified name and size.

解决： Check that ALL control files are online and that they are the same files that the system created at cold start time.

ORA-00206: error in writing (block string, # blocks string) of control file 原因： A disk I/O failure was detected on writing the control file.

解决： Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk.

ORA-00207: control files are not for the same database

原因： The database ID in the control file is not the same as the database ID in the control file used by the first instance to mount this database. Most likely one of the mounts used the wrong control file or there are two databases with the same name.

解决： Check that the control file is for the correct database and is not an old version. ORA-00208: number of control file names exceeds limit of string

原因： An attempt was made to use more control files than Oracle supports.

解决： Shut down Oracle. Reduce the number of control files specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle. Delete usused files. ORA-00209: control file blocksize mismatch, check alert log for more info

原因： The block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter.

解决： Look at the alert log for more information. ORA-00210: cannot open the specified control file 原因： Cannot open the control file.

解决： Check to make sure the control file exists and is not locked by some other program. ORA-00211: control file does not match previous control files

原因： A control file was specified that belongs to another database. 解决： Find and install the correct control file.

ORA-00212: block size string below minimum required size of string bytes

原因： The block size specified was too small. Space for the system overhead is required. 解决： Specify a larger block size and retry the operation.

ORA-00213: cannot reuse control file; old file size string, string required

原因： To reuse a control file, it must be the same size as the one previously used.

解决： Either do not specify REUSE, or specify a matching combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE statement.

ORA-00214: control file \ 原因： An inconsistent set of control files, datafiles/logfiles, and redo files was used.

第11页

解决： Use a consistant set of control files, datafiles/logfiles, and redo log files. That is, all the files must be for the same database and from the same time period. ORA-00215: must be at least one control file

原因： No control file is specified or the control file specified does not exist. 解决： Specify at least one valid control file and retry the operation. ORA-00216: control file could not be resized for migration from 8.0.2

原因： The control file created by release 8.0.2 was missing some record types. These record types are automatically added by resizing the control file during mount. The resize has failed.

解决： 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-00217: control file could not be resized for new record types

原因： 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.

解决： 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 \ 原因： 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 an incorrect setting of DB_BLOCK_SIZE, or else might indicate that the control file has either been corrupted or belongs to a different database.

解决： Restore a good copy of the control file. If the control file is known to be clean set the DB_BLOCK_SIZE to match control file headers block size value.

ORA-00219: required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks)

原因： An invocation of CREATE DATABASE or CREATE CONTROLFILE was executed specifying a combination of parameters that would require the control file size in blocks to exceed the maximum allowable value.

解决： In the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses.

ORA-00220: control file not mounted by first instance, check alert log for more info

原因： The specified control file has a different mount ID than the other control files that are being mounted. This means that the first instance to mount the database did not use this control file.

解决： Find and install the correct control file. ORA-00221: error on write to control file

原因： An error occurred when writing to one or more of the control files. 解决： See accompanying messages.

ORA-00222: operation would reuse name of a currently mounted control file

原因： The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of the specified

第12页

currently mounted control file.

解决： Retry the operation with a different filename. ORA-00223: convert file is invalid or incorrect version

原因： An Oracle7 to Oracle8 convert file contains invalid data or was created with an different version of the migration utility. This error can also be caused by incorrect ORACLE_HOME environment variable when ALTER DATABASE CONVERT command is issued.

解决： 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 the Oracle8 RDBMS executable and that the ORACLE_HOME environment variable is properly set.

ORA-00224: control file resize attempted with illegal record type (string)

原因： An attempt was made to expand or shrink the control file by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter.

解决： Use a value for the RECORD_TYPE parameter that specifies a valid record type other than type 0 (valid range is 1-16).

ORA-00225: expected size string of control file differs from actual size string

原因： The expected size of the control file as stored in its header was different than the actual operating system file size. This usually indicates that the control file was corrupted. 解决： Restore a good copy of the control file.

ORA-00226: operation disallowed while alternate control file open

原因： The attempted operation could not be executed at this time because this process had an alternate control file open for fixed table access.

解决： Retry the operation after calling cfileUseCurrent.

ORA-00227: corrupt block detected in control file: (block string, # blocks string)

原因： A block header corruption or checksum error was detected on reading the control file. 解决： Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command.

ORA-00228: length of alternate control file name exceeds maximum of string

原因： The specified filename, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum filename length for this operating system. 解决： Retry the operation with a shorter filename.

ORA-00229: operation disallowed: already hold snapshot control file enqueue

原因： The attempted operation cannot be executed at this time because this process currently holds the snapshot control file enqueue.

解决： Retry the operation after calling cfileUseCurrent to release the snapshot control file enqueue.

ORA-00230: operation disallowed: snapshot control file enqueue unavailable

原因： The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue.

解决： Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates.

ORA-00231: snapshot control file has not been named

原因： During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no filename for the snapshot control file had previously been specified.

解决： Specify a name for the snapshot control file by calling cfileSetSnapshotName.

第13页

ORA-00232: snapshot control file is nonexistent, corrupt, or unreadable

原因： The snapshot control file was found to be nonexistent, corrupt, or unreadable during an invocation of cfileUseSnapshot.

解决： Call cfileMakeAndUseSnapshot again (or for the first time). ORA-00233: copy control file is corrupt or unreadable 原因： The specified copy control file was found to be corrupt or unreadable during an invocation of cfileUseCopy.

解决： Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same filename that was specified for cfileUseCopy. ORA-00234: error in identifying or opening snapshot or copy control file

原因： A snapshot or copy control file of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy.

解决： Re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively.

ORA-00235: control file fixed table inconsistent due to concurrent update

原因： Concurrent update activity on a control file caused a query on a control file fixed table to read inconsistent information. 解决： Retry the operation.

ORA-00236: snapshot operation disallowed: mounted control file is a backup

原因： Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted control file is a backup control file. 解决： Mount a current control file and retry the operation.

ORA-00237: snapshot operation disallowed: control file newly created 原因： An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made. 解决： Mount a current control file and retry the operation.

ORA-00238: operation would reuse a filename that is part of the database

原因： The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that is currently part of the database.

解决： Retry the operation with a different filename. ORA-00250: archiver not started

原因： An attempt was made to stop automatic archiving, but the archiver process was not running.

解决： No action required.

ORA-00251: LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string string 原因： The destination specified by the LOG_ARCHIVE_DUPLEX_DEST parameter is the same as the destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command.

解决： Specify a different destination for parameter LOG_ARCHIVE_DUPLEX_DEST, or specify a different destination with the ALTER SYSTEM command. ORA-00252: log string of thread string is empty, cannot archive

原因： A log must be used for redo generation before it can be archived. The specified redo log was not been used since it was introduced to the database. However it is possible that instance death during a log switch left the log empty.

第14页

解决： Empty logs do not need to be archived. Do not attempt to archive the redo log file. ORA-00253: character limit string exceeded by archive destination string string

原因： The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command was too long.

解决： Retry the ALTER SYSTEM command using a string shorter than the limit specified in the error message.

ORA-00254: error in archive control string \

原因： The specified archive log location is invalid in the archive command or the LOG_ARCHIVE_DEST initialization parameter.

解决： Check the archive string used to make sure it refers to a valid online device. ORA-00255: error archiving log string of thread string, sequence # string 原因： An error occurred during archiving.

解决： Check the accompanying message stack for more detailed information. If the online log is corrupted, then the log can be cleared using the UNARCHIVED option. This will make any existing backups useless for recovery to any time after the log was created, but will allow the database to generate redo.

ORA-00256: cannot translate archive destination string string

原因： The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated.

解决： Check the accompanying message stack for more detailed information. Then, retry the ALTER SYSTEM command using a different string.

ORA-00257: archiver error. Connect internal only, until freed.

原因： The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is the destination device is out of space to store the redo log file.

解决： Check archiver trace file for a detailed description of the problem. Also verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving.

ORA-00258: manual archiving in NOARCHIVELOG mode must identify log 原因： The database is in NOARCHIVELOG mode and a command to manually archive a log did not specify the log explicitly by sequence number, group number or filename.

解决： Specify log by filename, by group number or by thread and sequence number.

ORA-00259: log string of open instance string (thread string) is the current log, cannot archive 原因： An attempt was made to archive the current log of an open thread. This is not allowed because the redo log file may still be in use for the generation of redo entries.

解决： Force a log switch in the instance where the thread is open. If no instances are open, open the database so that instance recovery can recover the thread.

ORA-00260: cannot find online log sequence string for thread string

原因： The log sequence number supplied to the archival command does not match any of the online logs for the thread. The log might have been reused for another sequence number, it might have been dropped, the sequence number might be greater than the current log sequence number, or the thread might not have any logs.

解决： Check the ARCHIVE statement, then specify a valid log sequence number. Specify a valid log sequence number.

第15页

filename was specified

解决： Specify the correct redo log file; then retry the operation. ORA-00311: cannot read header from archived log

原因： An I/O error occurred when attempting to read the log file header from the specified archived redo log file.

解决： Other messages will accompany this message. See the associated messages for the appropriate action to take.

ORA-00312: online log string thread string: \

原因： This message reports the filename for details of another message.

解决： Other messages will accompany this message. See the associated messages for the appropriate action to take.

ORA-00313: open failed for members of log group string of thread string 原因： The online log cannot be opened. May not be able to find file. 解决： See accompanying errors and make log available.

ORA-00314: log string of thread string, expected sequence# string doesn\ 原因： The online log is corrupted or is an old version. 解决： Find and install correct version of log or reset logs.

ORA-00315: log string of thread string, wrong thread # string in header 原因： The online log is corrupted or is an old version. 解决： Find and install correct version of log or reset logs.

ORA-00316: log string of thread string, type string in header is not log file 原因： The online log is corrupted or is an old version. 解决： Find and install correct version of log or reset logs. ORA-00317: file type string in header is not log file 原因： This is not an archived log file. 解决： Find the correct file and try again.

ORA-00318: log string of thread string, expected file size string doesn\

原因： On header read the file size indicated in the control file did not match the file size contained in the log file.

解决： Restore correct file or reset logs.

ORA-00319: log string of thread string has incorrect log reset status

原因： Check of log file header at database open found that an online log has log reset data that is different from the control file. The log is probably an incorrectly restored backup. 解决： Restore correct file or reset logs.

ORA-00320: cannot read file header from log string of thread string 原因： The file is not available. 解决： Restore the log file.

ORA-00321: log string of thread string, cannot update log file header 原因： Cannot write to the log file. 解决： Restore the access to the file.

ORA-00322: log string of thread string is not current copy

原因： Check of log file header at database open found that an online log appears to be an incorrectly restored backup.

解决： Restore correct file or reset logs.

第21页

ORA-00323: Current log of thread string not useable and all others need archiving

原因： Attempt to open thread failed because it is necessary to switch redo generation to another online log, but all the other logs need to be archived before they can be used. 解决： Archive the logs for the thread then retry open.

ORA-00324: log file \too long, string characters exceeds string limit

原因： the translated name for a log file is too long.

解决： Choose a untranslated name that yields a shorter translated name. ORA-00325: archived log for thread string, wrong thread # string in header

原因： The archived log is corrupted or for another thread. Can not use the log for applying redo. 解决： Find correct archived log.

ORA-00326: log begins at change string, need earlier change string

原因： The archived log supplied for recovery was generated after the log that is needed. Can not yet use the log for applying redo. 解决： Find correct archived log.

ORA-00327: log string of thread string, physical size string less than needed string

原因： A log file has shrunk in size. This is likely to have been caused by operator or operating system error.

解决： Restore the log file from backup. If backup is not available, drop this 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

原因： The archived log supplied for recovery was generated before the log that is needed. Can not use the log for applying redo. 解决： Find correct archived log.

ORA-00329: archived log begins at change string, need change string 原因： The archived log is not the correct log. An earlier log is needed. 解决： Restore the correct log file.

ORA-00330: archived log ends at change string, need change string 原因： The archived log is not the correct log. A later log is needed. 解决： Restore the correct log file.

ORA-00331: log version string incompatible with ORACLE version string 原因： The log was written by incompatible version of Oracle.

解决： Recover the database with the compatible software, shut it down cleanly, then restart with current software.

ORA-00332: archived log is too small - may be incompletely archived

原因： 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.

解决： Get a complete version of this log and use it for recovery. There should either be an online version of it or a copy that was successfully archived. ORA-00333: redo log read error block string count string

原因： An IO error occurred while reading the log described in the accompanying error. 解决： Restore accessibility to file, or get another copy of the file. ORA-00334: archived log: \

第22页

原因： Reporting filename for details of another error 解决： See associated error messages

ORA-00335: online log string: No log with this number, log does not exist 原因： Reporting filename for details of another error 解决： See associated error messages

ORA-00336: log file size string blocks is less than minimum string blocks 原因： The log file size as specified in create database is too small. 解决： Increase the log file size.

ORA-00337: log file \

原因： An attempt to add a log found neither an existing file nor a size for creating the file. 解决： Specify a size for the log file.

ORA-00338: log string of thread string is more recent than control file

原因： The control file change sequence number in the log file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough.

解决： Use the current control file or do backup control file recovery to make the control file current. Be sure to follow all restrictions on doing a backup control file recovery. ORA-00339: archived log does not contain any redo 原因： The archived log is not the correct log. It is a copy of a log file that has never been used for redo generation, or was an online log being prepared to be the current log. 解决： Restore the correct log file.

ORA-00340: IO error processing online log string of thread string 原因： An IO error occurred on the named online log.

解决： Restore accessibility to file, or restore file from backup.

ORA-00341: log string of thread string, wrong log # string in header

原因： The internal information in an online log file does not match the control file. 解决： Restore correct file or reset logs.

ORA-00342: archived log does not have expected resetlogs SCN string

原因： Recovery was given a log that does not belong to current incarnation or one of the parent incarnation. There should be another log that contains the correct redo. 解决： Supply the correct log file.

ORA-00343: too many errors, log member closed

原因： The maximum number of errors on this log member has been exceeded.

解决： Correct the underlying problem by referring to the other error messages found with this one.

ORA-00344: unable to re-create online log \

原因： An I/O failure occurred when attempting to re-create an online as part of either ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR LOGFILE command. 解决： Correct the file/device as indicated by accompanying errors. ORA-00345: redo log write error block string count string 原因： An IO error has occurred while writing the log

解决： Correct the cause of the error, and then restart the system. If the log is lost, apply media/incomplete recovery.

第23页

ORA-00346: log member marked as STALE 原因： A log file member no longer is complete.

解决： Correct the underlying problem by referring to the other error messages found with this one.

ORA-00347: log string of thread string, expected block size string doesn\

原因： On header read the blocksize indicated in the control file did not match the blocksize contained in the log file.

解决： Restore correct file or reset logs.

ORA-00348: single-process redo failure. Must abort instance

原因： A failure occurred during a critical portion of the log code during single process operation. This error does not occur during normal multi-process operation. 解决： Shutdown abort and warmstart the database. ORA-00349: failure obtaining block size for \

原因： The operating system was unable to determine the blocksize for the given filename.

解决： Consult the accompanying error message, and correct the device or specify another filename.

ORA-00350: log string of instance string (thread string) needs to be archived

原因： The command cannot be done because the log has not been archived, and media recovery has been enabled.

解决： Archive the log or disable media recovery. If the command supports an UNARCHIVED option then it can be used. However this may result in making backups unuseable, and forcing the drop of some offline files.

ORA-00351: recover-to time invalid

原因： The time specified in a recover-until statement must be after January 1st 1988. 解决： Specify a time after January 1st 1988.

ORA-00352: all logs for thread string need to be archived - cannot enable 原因： Attempting to enable a thread with all logs needing to be archived, and media recovery has been enabled. There is no log that can be made the new current log for the thread. 解决： Archive a log for the thread or disable media recovery.

ORA-00353: log corruption near block string change string time string

原因： Some type of redo log corruption has been discovered. This error describes the location of the corruption. Accompanying errors describe the type of corruption.

解决： 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 原因： The block header on the redo block indicated by the accompanying error, is not reasonable. 解决： 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 problem 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 database.

ORA-00355: change numbers out of order

原因： A change number found in the redo log is lower than a previously encountered change number. The log is corrupted in some way. The corruption may be at the earlier change or at this one.

第24页

解决： 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

原因： A change record in the redo log contains lengths that do not add up to a consistent value. The log is corrupted in some way.

解决： 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

原因： An add logfile or add logfile member command would result in a log with too many members. The number of members is set when the database is created. 解决： Use fewer log file members.

ORA-00358: Too many file members specified, the maximum is string

原因： A create or alter statement specified too many members in a parenthesised file list. 解决： Specify a number of file members that is within the port-defined limit. ORA-00359: logfile group string does not exist

原因： An add logfile member or drop logfile request specified a logfile group number that does not exist.

解决： Check the configuration of the log files and reissue the command. ORA-00360: not a logfile member: string

原因： A filename was given to drop logfile member that is not a part of the database, or which is a data file.

解决： Supply a valid logfile member name.

ORA-00361: cannot remove last log member string for group string

原因： An attempt has been made to remove the last member of a log file group. 解决： If desired, delete the entire log, by using DROP LOGFILE. ORA-00362: member is required to form a valid logfile in group string

原因： A request to drop a logfile member was denied because it would remove data required to form a complete logfile.

解决： If desired, delete the entire log (after archiving if required), by using DROP LOGFILE; ORA-00363: log is not the archived version

原因： d by failing to list the current log of an enabled thread in a CREATE CONTROLFILE command.

解决： 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

原因： An i/o error occurred when attempting to write the header to a log member that is being added to an existing group.

解决： See accompanying errors. Fix problem or use another file. ORA-00365: the specified log is not the correct next log

原因： The specified log failed to pass checks to ensure it corresponds to the log that was just applied. This is probably the result of using a log that was generated against a cold backup image of the database.

解决： Find the log that was generated by this copy of the database and give that filename to

第25页

recovery.

ORA-00366: log string of thread string, checksum error in the file header

原因： The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted 解决： Find and install correct version of log or reset logs. ORA-00367: checksum error in log file header

原因： The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted 解决： Find the correct file and try again.

ORA-00368: checksum error in redo log block

原因： The redo block indicated by the accompanying error, is not vaild. It has a checksum that does not match the block contents.

解决： Restore correct file or reset logs.

ORA-00369: Current log of thread string not useable and other log being cleared

原因： 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 need to be archived before they can be used. 解决： If the ALTER DATABASE CLEAR LOGFILE command is still active then wait for it to complete. Otherwise reissue the CLEAR command. If there are other online logs for the thread, that are not being cleared, then archive the logs.

ORA-00370: potential deadlock during kcbchange operation

原因： Error code used internally by software. Should never be reported 解决： Treat as internal error. See error 600.

ORA-00371: not enough shared pool memory, should be atleast string bytes 原因： Init.ora parameter shared_pool_size is too small 解决： Increase the parameter value

ORA-00372: file string cannot be modified at this time

原因： 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.

解决： check the status of the file and its tablespace

ORA-00373: online log version string incompatible with ORACLE version string

原因： The online log was written by incompatible version of Oracle. Can occur when the log file was created by either a new or older version of Oracle.

解决： Recover the database with the compatible software, shut it down cleanly, then restart with current software.

ORA-00374: parameter db_block_size = string invalid ; must be a multiple of string in the range [string..string]

原因： invalid value for db_block_size parameter 解决： adjust parameter and restart

ORA-00375: unable to get default db_block_size

原因： the system was unable to determine the default db_block_size

解决： see accompanying system specific error. As a workaround, specify the blocksize in the INIT.ORA file.

ORA-00376: file string cannot be read at this time

第26页

原因： attempting to read from a file that is not readable. Most likely the file is offline. 解决： Check the state of the file. Bring it online

ORA-00377: Frequent backups of file string causing write operation to stall

原因： Backups are occurring too frequently on this file. Each time a new backup is started for a file, any writes which have been previously issued (but not completed) have to be re-issued. If hot backups are started very, very frequently, it is possible that some writes will be re-issued repeatedly and never complete.

解决： Increase the interval between begin hot-backup commands for this file. ORA-00378: buffer pools cannot be created as specified

原因： Either the number of buffers or the number of lru latches is too small to satisfy the specified buffer pool configuration.

解决： Either increase the number of buffers and/or number of lru latches or configure smaller buffer pools.

ORA-00379: no free buffers available in buffer pool string for block size stringK

原因： All buffers in the specified buffer pool for the specified block size are in use and no free buffers are available.

解决： Increase the number of buffers in the specified pool for the specified block size ORA-00380: cannot specify db_stringk_cache_size since stringK is the standard block size

原因： User specified the parameter db_nk_cache_size (where n is one of 2,4,8,16,32), while the standard block size for this database is equal to n Kbytes. This is illegal.

解决： Specify the standard block size cache using db_cache_size (DEFAULT pool) (and db_recycle_cache_size, db_keep_cache_size if additional buffer pools are required). Do NOT use the corresponding db_nk_cache_size parameter for the standard block size.

ORA-00381: cannot use both new and old parameters for buffer cache size specification

原因： User specified one or more of { db_cache_size , db_recycle_cache_size, db_keep_cache_size, db_nk_cache_size (where n is one of 2,4,8,16,32), db_cache_advice } AND one or more of { db_block_buffers, buffer_pool_keep , buffer_pool_recycle }. This is illegal. 解决： Use EITHER the old (pre-Oracle_8.2) parameters OR the new ones. Don\old size parameters are specified in the parameter file, you may want to replace them with new parameters since the new parameters can be modified dynamically and allow you to configure additional caches for additional block sizes. Cache advisory can only be enabled with the new cache parameters.

ORA-00382: %s not a valid block size, valid range [string..string]

原因： User specified a value for db_nk_cache_size where n is one of {2, 4, 8, 16, 32}, but nk is not a valid block size for this platform.

解决： Remove corresponding parameter from the \ORA-00383: DEFAULT cache for blocksize string cannot be reduced to zero

原因： User attempted to reduce db_cache_size to zero, or attempted to to reduce db_K_cache_size to zero while there were still online tablespaces with blocksize K. Note that since the SYSTEM tablespace cannot be taken offline, it is always illegal to set db_cache_size to zero.

解决： Offline any tablespaces with the corresponding blocksize and then perform the operation again.

ORA-00384: Insufficient memory to grow cache

第27页

原因： The system could not allocate sufficient memory to grow the cache to the specified size. 解决： Attempt a smaller increase in the value of the parameter.

ORA-00385: cannot enable Very Large Memory with new buffer cache parameters

原因： User specified one or more of { db_cache_size , db_recycle_cache_size, db_keep_cache_size, db_nk_cache_size (where n is one of 2,4,8,16,32) } AND use_indirect_data_buffers is set to TRUE. This is illegal.

解决： Very Large Memory can only be enabled with the old (pre-Oracle_8.2) parameters. ORA-00386: use_indirect_data_buffers not supported

原因： The system could not allocate sufficient memory to grow the cache to the specified size. 解决： Attempt a smaller increase in the value of the parameter.

ORA-00390: log string of thread string is being cleared, cannot become current log

原因： An attempt to switch to a new online log for the redo thread failed because no reusable log could be found. This log is being cleared and will be useable when the clearing completes. The command that began the clearing may have terminated without completing the clearing.

解决： If the clear command is still executing then wait for its completion. If it terminated then reissue the clear command, or drop the log.

ORA-00391: All threads must switch to new log format at the same time

原因： An attempt to switch the current log of a single thread is not allowed because the compatiblity requirements force a new log format version number. When changing log formats, all threads must switch to the new format at the same time.

解决： Open the database to cause the coordinated log switch. If that is not possible then return to the same software version and compatibility setting last used to open the database. ORA-00392: log string of thread string is being cleared, operation not allowed

原因： An operation encountered this online log in the middle of being cleared. The command that began the clearing may have terminated without completing the clearing.

解决： If the clear command is still executing then wait for its completion. If it terminated then reissue the clear command, or drop the log.

ORA-00393: log string of thread string is needed for recovery of offline datafiles

原因： Log cannot be cleared because the redo in it is needed to recover offline datafiles. It has not been archived so there is no other copy available. If the log is cleared the tablespaces containing the files will have to be dropped.

解决： Archive the log then repeat the clear command. If archiving is not possible, and dropping the tablespaces is acceptible, then add the clause UNRECOVERABLE DATAFILE at the end of the clear command.

ORA-00394: online log reused while attempting to archive it

原因： It has been detected that an online log that is being archived has been reused 解决： Cannot archive the logfile anymore since it has been overwritten ORA-00395: online logs for the clone database must be renamed

原因： A clone database open forces logfile renaming to avoid overwriting the primary logfiles 解决： Rename the logfiles manually or using the log_file_name_convert initialization parameter ORA-00396: error string required fallback to single-pass recovery

原因： The indicated error caused two-pass instance or crash recovery to fail. Recovery was retried with an alternate (slower) method to avoid the error.

解决： Correct the cause of the indicated error (also recorded) so that future instance or crash

第28页

recovery can succeed with the two-pass algorithm. This usually requires making more main memory available to the recovery process.

ORA-00397: instance recovery process terminated with error 原因： The foreground process doing instance recovery died.

解决： Check the foreground trace file for the cause of recovery failure. ORA-00398: abort thread recovery due to reconfiguration

原因： Global enqueue service reconfiguration occurred during instance/crash recovery. 解决： This is used internally, no action is required. ORA-00399: corrupt change description in redo log

原因： A change vector in the redo log failed validation checks.

解决： Do recovery with a good version of the log or do time based recovery up to the indicated time.

ORA-00400: invalid release value string for parameter string

原因： The release level given for the specified init parameter is invalid. 解决： Correct the parameter value in the parameter file and retry.

ORA-00401: the value for parameter string is not supported by this release 原因： The value specified cannot be supported by this release of the software.

解决： Choose an appropriate value, or remove the parameter value to use the default value. ORA-00402: database changes by release string cannot be used by release string

原因： Changes have been made to the database that require a newer software release or that violate the compatibility parameters.

解决： Use a version of the software that can understand the changes or relax the compatibility requirements in the init file.

ORA-00403: %s (string) is not the same as other instances (string)

原因： Another instance has set the compatible or compatible no recovery parameters differently than this instance.

解决： Change the parameters of the current instance to match other instances already running. ORA-00404: Convert file not found: \

原因： The file used for converting the database from V7 to V8 could not be found.

解决： Verify that the migration process has been started on this database and that the convert filename is accessable.

ORA-00405: compatibility type \

原因： Reporting a type associated with another error. 解决： See accompanying error

ORA-00406: COMPATIBLE parameter needs to be string or greater

原因： The COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter.

解决： Shutdown and startup with a higher compatibility setting.

ORA-00407: rolling upgrade from release string.string to string.string is not allowed

原因： Another instance executing software at a different point release already has the database mounted.

解决： Shutdown all instances then startup with the new software. ORA-00408: parameter string is set to TRUE

第29页

原因： Reporting the parameter that resulted in the compatibility error. 解决： Shutdown and startup with a higher compatibility setting.

ORA-00409: COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT

原因： This is due to migrating from an older release of Oracle with tablespaces created using AUTO SEGMENT SPACE MANAGEMENT. To open the database, the COMPATIBLE parameter needs to be set to the specified value.

解决： Shutdown and startup with the specified compatibility setting.

ORA-00437: ORACLE feature is not licensed. Contact Oracle Corp. for assistance 原因： ORACLE feature is not licensed. 解决： Contact ORACLE for assistance. ORA-00438: %s Option not installed

原因： The specified option is not installed. 解决： Purchase and install the option. ORA-00439: feature not enabled: string 原因： The specified feature is not enabled. 解决： Do not attempt to use this feature.

ORA-00443: background process \ 原因： The specified process did not start.

解决： Ensure that the executable image is in the correct place with the correct protections, and that there is enough memory.

ORA-00444: background process \

原因： Usually due to a bad (or non-existent) background process image. 解决： Get a good background process image.

ORA-00445: background process \ 原因： The specified process did not start after the specified time. 解决： Ensure that the background did not die and leave a trace file. ORA-00446: background process started when not expected

原因： The background process specified started up AFTER the RDBMS was already running. 解决： If nobody at your site started the process, then this is an internal error. ORA-00447: fatal error in background process

原因： One of the background processes died unexpectedly. 解决： Warm start the system.

ORA-00448: normal completion of background process

原因： One of the background processes completed normally (i.e. exited). The background process thinks that somebody asked it to exit. 解决： Warm start the system.

ORA-00449: background process \

原因： A foreground process needing service from a background process has discovered the process died.

解决： Consult the error code, and the trace file for the process. ORA-00450: background process \ 原因： The specified process did not start.

解决： Consult the error code, and the trace file for the process.

第30页

ORA-00451: foreground process died unexpectedly

原因： The foreground process for the new connection did not start. 解决： Reconnect to Oracle.

ORA-00452: foreground process unexpectedly terminated with error string 原因： The foreground process for the new connection did not start. 解决： Reconnect to Oracle.

ORA-00453: backgroud process \

原因： The background process that was being messaged was dead or its incarnation was invalid. 解决： Restart the background process.

ORA-00469: CKPT process terminated with error 原因： The checkpoint process died 解决： Warm start instance

ORA-00470: LGWR process terminated with error 原因： The log writer process died 解决： Warm start instance

ORA-00471: DBWR process terminated with error 原因： The database writer process died 解决： Warm start instance

ORA-00472: PMON process terminated with error 原因： The process cleanup process died 解决： Warm start instance

ORA-00473: ARCH process terminated with error 原因： The archive process died 解决： Warm start instance

ORA-00474: SMON process terminated with error 原因： The system cleanup process died 解决： Warm start instance

ORA-00475: TRWR process terminated with error 原因： The system tracing process died 解决： Warm start instance

ORA-00476: RECO process terminated with error

原因： The distributed transaction (two-phase commit) recovery process died. 解决： Warm start instance

ORA-00477: SNP* process terminated with error 原因： A materialized view refresh process died 解决： PMON will restart SNP process shortly. If SNP process does not get started, contact Oracle support.

ORA-00478: SMON process terminated due to error string

原因： SMON was unable to service the requests due to error in cleanup of resources 解决： Warm start instance

ORA-00479: RVWR process terminated with error string 原因： The RVWR process died 解决： Warm start instance

ORA-00480: LCK* process terminated with error

第31页

原因： A system lock process died 解决： Warm start instance

ORA-00481: LMON process terminated with error

原因： The global enqueue service monitor process died 解决： Warm start instance

ORA-00482: LMD* process terminated with error 原因： A global enqueue service daemon process died 解决： Warm start instance

ORA-00483: During shutdown a process abnormally terminated

原因： One of the background processes did not exit normally at or near the time of shutdown. 解决： Use shutdown abort.

ORA-00484: LMS* process terminated with error 原因： A global cache service process died 解决： Warm start instance

ORA-00485: DIAG process terminated with error string 原因： A global diagnostic process died 解决： Wait for process to restart

ORA-00486: ASMB process terminated with error 原因： An ASM background process died.

解决： Warm start instance. Also check that ASM Instance is running. ORA-00487: CTWR process terminated with error 原因： The change tracking process died 解决： Warm start instance

ORA-00488: RBAL process terminated with error 原因： The ASM rebalance coordinator process died. 解决： Warm start instance.

ORA-00489: ARB* process terminated with error 原因： An ASM rebalance worker process died. 解决： Wait for process to restart.

ORA-00490: PSP process terminated with error 原因： The process spawner died 解决： Warm start instance

ORA-00566: cannot request processor group - NUMA not enabled

原因： Cannot start process in a requested processor group when the NUMA feature is disabled. 解决： Start the process without requesting a NUMA processor group.

ORA-00567: Requested processor group string is too large (maximum string) 原因： The process could not be started in the requested processor group. 解决： Start the process in another processor group.

ORA-00568: Maximum number of interrupt handlers exceeded 原因： User specified too many ^c handlers 解决： Remove some old handlers.

ORA-00569: Failed to acquire global enqueue.

原因： A prior error occurred on one of the instances in the cluster. Typically errors are caused by shared pool resource contention.

第32页

解决： 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_SERVERS initialization parameters.

ORA-00600: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string] 原因： This is the generic internal error number for Oracle program exceptions. This indicates that a process has encountered an exceptional condition.

解决： Report as a bug - the first argument is the internal error number ORA-00601: cleanup lock conflict

原因： PMON process runs into lock conflict trying to recovery processes 解决： This is trapped internally, no action necessary ORA-00602: internal programming exception 原因： Internal programming exception 解决： Report as bug

ORA-00603: ORACLE server session terminated by fatal error 原因： An ORACLE server session is in an unrecoverable state.

解决： Login to ORACLE again so a new server session will be created ORA-00604: error occurred at recursive SQL level string

原因： An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables).

解决： If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support.

ORA-00606: Internal error code

原因： A call to deferred upi functions was made in non deferred mode 解决： Report as a bug.

ORA-00607: Internal error occurred while making a change to a data block

原因： An internal error or memory exception occurred while Oracle was applying redo to a data block.

解决： call Oracle Support

ORA-00608: testing error [string] [string] [string] [string] [string] 原因： Internal error reserved for testing. 解决： call Oracle Support

ORA-00609: could not attach to incoming connection

原因： Oracle process could not answer incoming connection

解决： If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support.

ORA-00610: Internal error code

原因： Oracle process started too late

解决： This error should never be seen by the customer. Contact Oraclce Support ORA-00701: object necessary for warmstarting database cannot be altered

原因： Attempt to alter or drop a database object (table, cluster, or index) which are needed for warmstarting the database. 解决： None.

第33页

ORA-00702: bootstrap verison \

原因： The reading version of the boostrap is incompatible with the current bootstrap version. 解决： Restore a version of the software that is compatible with this bootstrap version. ORA-00703: maximum number of row cache instance locks exceeded 原因： There are not enough row cache enqueues.

解决： Increase the row cache enqueue parameter and warm start the system. ORA-00704: bootstrap process failure

原因： Failure in processing bootstrap data - see accompanying error. 解决： Contact your customer support representative.

ORA-00705: inconsistent state during start up; shut down the instance, then restart it 原因： A previous attempt to start an instance was terminated. 解决： Shut down the instance completely, then restart it. ORA-00706: error changing format of file \

原因： An attempt to change the block0 format of the specified file failed because the file is read-only or offline.

解决： Make the file read-write or bring the file online and set the BLK0_FMTCHG event. ORA-00710: new tablespace name is the same as the old tablespace name

原因： An attempt to rename a tablespace failed because the new name is the same as the old name.

解决： No action required.

ORA-00711: new tablespace name is invalid

原因： An attempt to rename a tablespace failed because the new name is invalid. 解决： Choose a valid new name and retry the command. ORA-00712: cannot rename system tablespace

原因： An attempt to rename the system tablespace failed. 解决： No action required.

ORA-00720: ALTER DATABASE RESET COMPATIBILITY command has been de-supported 原因： ALTER DATABASE RESET COMPATIBILITY command has been de-supported since Oracle 10i.

解决： No action required.

ORA-00721: changes by release string cannot be used by release string

原因： An attempt to import a tablespace failed because the tablespace contains changes that require a newer software release or that violate the compatibility parameters.

解决： Use a version of the software that can understand the changes or relax the compatibility requirements in the initialization parameter file. ORA-00722: Feature \

原因： Reporting name of the feature for details of another error. 解决： See associated error message.

ORA-00723: Initialization parameter COMPATIBLE must be explicitly set

原因： Oracle detected that the initialization parameter COMPATIBLE was not explicitly specified, and the compatibility of the database is lower than the default value of the COMPATIBLE parameter. In order to use the new compatible setting, the intialization parameter must be explicitly set by the user.

解决： Explicitly set the value of COMPATIBLE parameter either in PFILE or SPFILE,

第34页

whichever is used.

ORA-00724: ALTER DATABASE CONVERT command has been de-supported

原因： ALTER DATABASE CONVERT command has been de-supported since Oracle 10i. 解决： No action required.

ORA-00740: datafile size of (string) blocks exceeds maximum file size 原因： The user specified datafile size exceeded maximum file size.

解决： Please check REFERENCE for maximum size. Reduce the size and retry. ORA-00741: logfile size of (string) blocks exceeds maximum logfile size 原因： The user specified logfile size exceeded maximum logfile size.

解决： Please check REFERENCE for maximum size. Reduce the size and retry. ORA-00750: database has been previously mounted and dismounted

原因： The instance has already mounted and dismounted the database, which is only allowed once in its lifetime.

解决： Shut down the database.

ORA-00820: Specified value of sga_max_size is too small, needs to be at least stringM

原因： The specified value of sga_max_size is too small for the SGA to accommodate all of the necessary SGA components such as the log buffer, buffer pools, shared pool, etc.

解决： Set sga_max_size to the recommended value or reduce the values of any SGA component size parameters you have specified.

ORA-00821: Specified value of sga_target stringM is too small, needs to be at least stringM

原因： The specified value of sga_target is too small for the SGA to accommodate all of the necessary SGA components such as the log buffer, buffer pools, shared pool, etc.

解决： Set sga_target to the recommended value or reduce the values of any SGA component size parameters you have specified.

ORA-00822: MMAN process terminated with error 原因： The Memory Management process died. 解决： Warm start instance

ORA-00823: Specified value of sga_target greater than sga_max_size 原因： The specified value of sga_target is greater than sga_max_size.

解决： Increase sga_max_size to match up with sga_target or decrease sga_target to match up with sga_maxsize.

ORA-00824: cannot set sga_target due to existing internal settings, see alert log for more information

原因： Unable to set sga_target due to current parameter settings. 解决： See alert log for more information.

ORA-00825: cannot set db_block_buffers if sga_target set 原因： sga_target set with db_block_buffers set.

解决： Do not set sga_target or use new cache parameters and do not use db_block_buffers which is a old cache parameter.

ORA-00826: cannot set sga_target for an ASM instance 原因： sga_target set for an ASM instance. 解决： Do not set sga_target.

ORA-00827: could not shrink sga_target to specified value

原因： Attempted to shrink the SGA to the specified value but did not succeed because the SGA

第35页

components could not be shrunk as they were already at their minimum sizes.

解决： Do not set sga_target to a value below the current value without first shrinking the individual SGA components.

ORA-00828: specified value of shared_pool_reserved_size inconsistent with internal settings 原因： Unable to set shared_pool_reserved_size to specified value if sga_target set, either because the specified value is too small, or because it is too large for the current internal size of shared pool. More details can be found in the alert log.

解决： If possible, do not set shared_pool_reserved_size without setting shared_pool_size if sga_target set. Examine the alert log for information about current internal size of shared pool, and valid range of values for shared_pool_reserved_size.

ORA-00830: cannot set statistics_level to BASIC with auto-tune SGA enabled

原因： The user attempted to set statistics_level to BASIC with auto-tune SGA enabled which cannot be done because auto-tune SGA cannot work with statistics_level set to BASIC. 解决： Disable auto-tune SGA and try setting the statistics_level to BASIC again. ORA-00832: no streams pool created and cannot automatically create one

原因： A database feature which needs STREAMS SGA was being used, however, the streams_pool_size parameter was not defined and the value of db_cache_size was too small to permit an automatic transfer of SGA to the streams pool from the buffer cache. 解决： Please set the parameter streams_pool_size or set sga_target. ORA-00910: specified length too long for its datatype

原因： for datatypes CHAR and RAW, the length specified was > 2000; otherwise, the length specified was > 4000.

解决： use a shorter length or switch to a datatype permitting a longer length such as a VARCHAR2, LONG CHAR, or LONG RAW ORA-00911: invalid character

原因： identifiers may not start with any ASCII character other than letters and numbers. $#_ are also allowed after the first character. Identifiers enclosed by doublequotes may contain any character other than a doublequote. Alternative quotes (q\cannot use spaces, tabs, or carriage returns as delimiters. For all other contexts, consult the SQL Language Reference Manual.

解决： none

ORA-00912: input parameter too long

原因： one of your input strings was too long 解决： shorten the input parameter length ORA-00953: missing or invalid index name

原因： An index name of the form [ . ] is expected but not present. If OIDINDEX clause, index name must be 解决： Enter an appropriate index name.

ORA-00956: missing or invalid auditing option

原因： AUDIT or NOAUDIT statement contains an invalid auditing option. 解决： Use a valid option.

ORA-00960: ambiguous column naming in select list

原因： A column name in the order-by list matches more than one select list columns. 解决： Remove duplicate column naming in select list.

第36页

ORA-00962: too many group-by / order-by expressions

原因： The group-by or order-by column list contain more than 1000 expressions. 解决： Use 1000 or less expressions in the group-by or order-by list. ORA-00964: table name not in FROM list

原因： The table name referred in the select list is not specified in the from list.

解决： Make sure the name is correctly specified and matches one of the names in the from list. ORA-00965: column aliases not allowed for \

原因： The statement is trying to alias the * expression in the select list which is not legal. 解决： Remove the alias.

ORA-00972: identifier is too long

原因： An identifier with more than 30 characters was specified. 解决： Specify at most 30 characters.

ORA-00976: LEVEL, PRIOR, or ROWNUM not allowed here

原因： LEVEL, PRIOR, or ROWNUM is being specified at illegal location. 解决： Remove LEVEL, PRIOR, or ROWNUM. ORA-00977: duplicate auditing option

原因： AUDIT or NOAUDIT statement specifies an option more than once

解决： Either use ALL with no other auditing options or make sure no option is listed more than once.

ORA-00981: cannot mix table and system auditing options

原因： Table and system-wide auditing options were specified in the same AUDIT or NOAUDIT statement.

解决： You must issue table and system options in separate statements. ORA-00983: cannot audit or noaudit SYS user actions

原因： An attempt was made to AUDIT or NOAUDIT SYS user actions. 解决： Execute the statement again with a valid user.

ORA-00991: only MAC privileges may be granted to procedures

原因： Object privileges or non-MAC system privileges were granted to the procedure. 解决： Only grant MAC privileges using the PROCEDURE clause. ORA-01002: fetch out of sequence

原因： This error means that a fetch has been attempted from a cursor which is no longer valid. Note that a PL/SQL cursor loop implicitly does fetches, and thus may also cause this error. There are a number of possible causes for this error, including: 1) Fetching from a cursor after the last row has been retrieved and the ORA-1403 error returned. 2) If the cursor has been opened with the FOR UPDATE clause, fetching after a COMMIT has been issued will return the error. 3) Rebinding any placeholders in the SQL statement, then issuing a fetch before reexecuting the statement.

解决： 1) Do not issue a fetch statement after the last row has been retrieved - there are no more rows to fetch. 2) Do not issue a COMMIT inside a fetch loop for a cursor that has been opened FOR UPDATE. 3) Reexecute the statement after rebinding, then attempt to fetch again. ORA-01010: invalid OCI operation

原因： One of the following: 1) You attempted an invalid OCI operation. 2) You are using an Oracle client application linked with version 7.1 (or higher) libraries, the environment variable ORA_ENCRYPT_LOGIN is set to TRUE, and you attempted to connect to a version 7.0 (or lower)

第37页

Oracle Server. 3) You are connected to a version 7.1 (or higher) Oracle Server, the initialization parameter DBLINK_ENCRYPT_LOGIN is set to TRUE, and you attempted to use a database link pointing to a version 7.0 (or lower) Oracle Server. 4) You are connected to a version 9.0.2(or higher) Oracle Server and you attempted to use a database link pointing to a version 9.0.1(or lower) Oracle Server for distributed autonomous transaction. 解决： For the above causes: 1) Do not use the invalid OCI operation. 2) If you do not wish to use encrypted connect passwords in your distributed database, set ORA_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted connect passwords, you must upgrade all Oracle Servers to version 7.1 (or higher). 3) If you do not wish to use encrypted database links in your distributed database, set DBLINK_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted database links, you must upgrade all Oracle Servers to version 7.1 (or higher). 4) Do not attempt distributed autonomous transaction on version 9.0.1(or lower) Oracle Server. ORA-01016: This function can be called only after a fetch 原因： Cursor in an invalid state.

解决： Make sure that the oci/upi function is called after fetch. ORA-01019: unable to allocate memory in the user side 原因： The user side memory allocator returned error.

解决： Increase the processes heap size or switch to the old set of calls. ORA-01022: database operation not supported in this configuration

原因： The attempted database operation does not conform to the user programming interface (UPI) for the two communicating ORACLE servers.

解决： You may need to upgrade one or more of your ORACLE servers or re-link your user side application with new libraries. Report the problem to Worldwide Customer Support. ORA-01023: Cursor context not found (Invalid cursor number) 原因： The cursor number is not a valid open cursor. 解决： Make sure that the cursor is open. ORA-01025: UPI parameter out of range

原因： An integer parameter to a upi function is out of range.

解决： This usually indicates an error in a tool built on top of the oracle dbms. Report the error to your customer support representative.

ORA-01026: multiple buffers of size > 4000 in the bind list 原因： More than one long buffer in the bind list.

解决： Change the buffer size to be less than 4000 for the bind variable bound to a normal column.

ORA-01027: bind variables not allowed for data definition operations

原因： An attempt was made to use a bind variable in a SQL data definition operation. 解决： Such bind variables are not allowed. ORA-01028: internal two task error

原因： Received send long message but don\解决： Report as a bug.

ORA-01029: internal two task error

原因： Received a request to send the long again when there is no long 解决： Report as a bug

ORA-01030: SELECT ... INTO variable does not exist

第38页

原因： The SELECT... INTO specified in the bind call does not correspond to a variable in the SQL statement.

解决： If it is not possible to correct the statement, call customer support. ORA-01031: insufficient privileges

原因： An attempt was made to change the current username or password without the appropriate privilege. This error also occurs if attempting to install a database without the necessary operating system privileges. When Trusted Oracle is configure in DBMS MAC, this error may occur if the user was granted the necessary privilege at a higher label than the current login.

解决： Ask the database administrator to perform the operation or grant the required privileges. For Trusted Oracle users getting this error although granted the the appropriate privilege at a higher label, ask the database administrator to regrant the privilege at the appropriate label. ORA-01032: no such userid

原因： This is an internal error message related to Export/Import. 解决： Contact customer support.

ORA-01033: ORACLE initialization or shutdown in progress

原因： An attempt was made to log on while Oracle is being started up or shutdown. 解决： Wait a few minutes. Then retry the operation. ORA-01034: ORACLE not available

原因： Oracle was not started up. Possible causes include the following: - The SGA requires more space than was allocated for it.

- The operating-system variable pointing to the instance is improperly defined.

解决： Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. If Oracle has been initialized, then on some operating systems, verify that Oracle was linked correctly. See the platform specific Oracle documentation.

ORA-01035: ORACLE only available to users with RESTRICTED SESSION privilege

原因： Logins are disallowed because an instance started in restricted mode. Only users with RESTRICTED SESSION system privilege can log on.

解决： Request that Oracle be restarted without the restricted option or obtain the RESTRICTED SESSION system privilege.

ORA-01036: illegal variable name/number 原因： Unable to find bind context on user side

解决： Make sure that the variable being bound is in the sql statement. ORA-01037: maximum cursor memory exceeded

原因： Attempting to process a complex sql statement which consumed all available memory of the cursor.

解决： Simplify the complex sql statement.

ORA-01038: cannot write database file version string with ORACLE version string 原因： Attempting to write datafile headers in an old format. The new format can not be used until after the database has been verified as being compatible with this software version.

解决： Open the database to advance to the new file formats, then repeat the operation. If the operation is required before the database can be opened, then use the previous software release to do the operation.

第39页

ORA-01039: insufficient privileges on underlying objects of the view

原因： Attempting to explain plan on other people%underlying objects of the view.

解决： Get necessary privileges or do not perform the offending operation. ORA-01040: invalid character in password; logon denied

原因： There are multibyte characters in the password or some characters in the password are not in US7ASCII range.

解决： Resubmit password with valid characters.

ORA-01041: internal error. hostdef extension doesn\ 原因： Pointer to hstdef extension in hstdef is null. 解决： Report as a bug

ORA-01042: detaching a session with open cursors not allowed

原因： An attempt was made to detach a seesio n which had open cursors. 解决： Close all the cursors before detaching the session.

ORA-01043: user side memory corruption [string], [string], [string], [string] 原因： The application code corrupted some of the usr memory used by oracle 解决： Make sure that the application code is not overwriting memory.

ORA-01044: size string of buffer bound to variable exceeds maximum string

原因： An attempt was made to bind a buffer whose total size would exceed the maximum size allowed. Total array size for arrays is calculated as: (element_size)*(number of elements) 解决： Reduce buffer size.

ORA-01045: user string lacks CREATE SESSION privilege; logon denied

原因： A connect was attempted to a userid which does not have create session privilege. 解决： Grant the user CREATE SESSION privilege.

ORA-01048: Couldn\ 原因： The procedure user specified in deferred RPC doesn\

解决： Check to make sure that the procedure exists and is visible to the replication process. ORA-01049: Bind by name is not spupportted in streamed RPC 原因： A newer version of server is talking with this version requesting an operation not supported in this version. 解决： none

ORA-01051: deferred rpc buffer format invalid

原因： The deferred rpc data in sys.def$_call is corrupted. 解决： Contact your customer support representive.

ORA-01052: required destination LOG_ARCHIVE_DUPLEX_DEST is not specified

原因： A valid destination for parameter LOG_ARCHIVE_DUPLEX_DEST was not specified when parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was set to two.

解决： Either specify a value for parameter LOG_ARCHIVE_DUPLEX_DEST, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to one. ORA-01058: internal New Upi interface error

原因： Attempt to delete non existant hstdef extension. 解决： Report as a bug.

ORA-01059: parse expected before a bind or execute 原因： The client application attempted to bind a variable or execute a cursor opened in a PL/SQL

第40页

block before the statement was parsed.

解决： Ensure the statement is parsed before a bind or execute. ORA-01060: array binds or executes not allowed

原因： The client application attempted to bind an array of cursors or attempted to repeatedly execute against a PL/SQL block with a bind variable of type cursor. 解决： Bind a single cursor or execute the PL/SQL block once.

ORA-01061: cannot start up a V8 server using a V7 client application

原因： You are using an Oracle client application linked with version 7 (or lower) libraries and you attempted to start up a V8 (or higher) server.

解决： Use a client application linked with V8 (or higher) libraries.60 ORA-01062: unable to allocate memory for define buffer

原因： Exceeded the maximum buffer size for current plaform 解决： Use piecewise fetch with a smaller buffer size ORA-01070: Using an old version of Oracle for the server 原因： Using pre 7.0.10.1 version of oracle for server 解决： Upgrade server to post 7.0.10.1 version

ORA-01071: cannot perform operation without starting up ORACLE 原因： Obvious 解决： none

ORA-01072: cannot stop ORACLE; ORACLE not running 原因： Obvious 解决： none

ORA-01073: fatal connection error: unrecognized call type 原因： An illegal internal operation was attempted. 解决： Contact your customer support representative.

ORA-01074: cannot shut down ORACLE; inside a login session - log off first 原因： Obvious 解决： none

ORA-01075: you are currently logged on 原因： Attempt to login while logged in. 解决： none

ORA-01076: multiple logons per process not yet supported 原因： Obvious 解决： none

ORA-01077: background process initialization failure

原因： Failure during initialization of ORACLE background processes.

解决： Further diagnostic information should be in the error stack or in the trace file. ORA-01078: failure in processing system parameters

原因： Failure during processing of INIT.ORA parameters during system startup. 解决： Further diagnostic information should be in the error stack.

ORA-01079: ORACLE database was not properly created, operation aborted 原因： There was an error when the database or control file was created. 解决： s to recreate the database or a new control file. ORA-01080: error in shutting down ORACLE

第41页

原因： Failure during system shutdown.

解决： Further diagnostic information should be in the error stack. ORA-01081: cannot start already-running ORACLE - shut it down first 原因： Obvious 解决： none

ORA-01082: \

原因： \ORACLE without the transaction processing option.

解决： Remove it from INIT.ORA file or set it to \

ORA-01083: value of parameter \

原因： The value of the given parameter is required to be the same for all instances in the cluster database configuration. ROW_LOCKING and SERIALIZABLE are 2 examples. 解决： Change the value of the parameter in INIT.ORA file to match that of other cluster database instances.

ORA-01084: invalid argument in OCI call

原因： The failing OCI call contains an argument with an invalid value.

解决： Use valid argument values. For more information, see the Programmer\Guide to the Oracle Call Interfaces and the appropriate programming language supplement. ORA-01085: preceding errors in deferred rpc to \

原因： Errors were encountered when the named procedure was executed as a deferred remoted procedure call.

解决： Correct the cause of the preceding errors. ORA-01086: savepoint \

原因： Trying to roll back to a save point that was never established. 解决： none

ORA-01088: cannot shut down ORACLE while active processes exist 原因： Users are still logged into the instance.

解决： Either wait for all users to logoff or use SHUTDOWN IMMEDIATE. ORA-01089: immediate shutdown in progress - no operations are permitted

原因： The SHUTDOWN IMMEDIATE command was used to shut down a running ORACLE instance, so your operations have been terminated.

解决： Wait for the instance to be restarted, or contact your DBA. ORA-01090: shutdown in progress - connection is not permitted

原因： The SHUTDOWN command was used to shut down a running ORACLE instance, so you cannot connect to ORACLE.

解决： Wait for the instance to be restarted, or contact your DBA. ORA-01091: failure during startup force 原因： Unable to destroy the old SGA.

解决： Manually remove the old SGA and reissue the STARTUP command ORA-01092: ORACLE instance terminated. Disconnection forced

原因： The instance this process was connected to was terminated abnormally, probably via a shutdown abort. This process was forced to disconnect from the instance.

解决： Examine the alert log for more details. When the instance has been restarted, retry action. ORA-01093: ALTER DATABASE CLOSE only permitted with no sessions connected

第42页

原因： There is at least one more session other than the current one logged into the instance. ALTER DATABASE CLOSE is not permitted.

解决： Find the other sessions and log them out and resubmit the command ORA-01095: DML statement processed zero rows

原因： During a call to OTEX, an update, delete, or insert statement being executed processed zero rows. The execution of statements by OTEX was halted at this point. 解决： none

ORA-01096: program version (string) incompatible with instance (string)

原因： A program is trying to connect to an instance using a different version of code than the database was started with. This is not allowed.

解决： Either relink the program with the same version as the database or restart the database using the old version of code.

ORA-01097: cannot shutdown while in a transaction - commit or rollback first 原因： Obvious 解决： none

ORA-01099: cannot mount database in SHARED mode if started in single process mode 原因： Obvious 解决： none

ORA-01100: database already mounted

原因： A database is already mounted in this instance. 解决： none

ORA-01101: database being created currently mounted by some other instance

原因： Some other instance has the database of same name currently mounted and you are trying to create it.

解决： Either change the database name or shutdown the other instance. ORA-01102: cannot mount database in EXCLUSIVE mode

原因： Some other instance has the database mounted exclusive or shared. 解决： Shutdown other instance or mount in a compatible mode. ORA-01103: database name \

原因： The database name in the control file does not match your database name. 解决： Either find the correct control file or change your database name. ORA-01104: number of control files (string) does not equal string 原因： The number of control files used by this instance disagrees with the number of control files in an existing instance.

解决： Check to make sure that all control files are listed.

ORA-01105: mount is incompatible with mounts by other instances

原因： An attempt to mount the database discovered that another instance mounted a database by the same name, but the mount is not compatible. Additional errors are reported explaining why. 解决： See accompanying errors.

ORA-01106: database must be closed before dismounting 原因： Obvious 解决： none

ORA-01107: database must be mounted for media recovery

原因： An attempt to perform media recovery was made but the database is not mounted.

第43页

解决： Mount the database.

ORA-01108: file string is in backup or media recovery

原因： Either media recovery is actively being applied to the file, or it is being backed up while the database is in NOARCHIVELOG mode. It cannot be used for normal database access or crash recovery.

解决： Complete or cancel the media recovery session or backup. ORA-01109: database not open

原因： A command was attempted that requires the database to be open. 解决： Open the database and try the command again ORA-01110: data file string: \

原因： Reporting file name for details of another error 解决： See associated error message

ORA-01111: name for data file string is unknown - rename to correct file

原因： The data file was missing from a CREATE CONTROLFILE command or backup control file recovery was done with a control file that was saved before the file was created. 解决： Rename the MISSING file to the name of the real file. ORA-01112: media recovery not started

原因： An attempt to continue media recovery is being made but media recovery was not started. 解决： None.

ORA-01113: file string needs media recovery

原因： An attempt was made to online or open a database with a file that is in need of media recovery.

解决： First apply media recovery to the file.

ORA-01114: IO error writing block to file string (block # string)

原因： The device on which the file resides is probably offline. If the file is a temporary file, then it is also possible that the device has run out of space. This could happen because disk space of temporary files is not necessarily allocated at file creation time.

解决： Restore access to the device or remove unnecessary files to free up space. ORA-01115: IO error reading block from file string (block # string) 原因： Device on which the file resides is probably offline 解决： Restore access to the device

ORA-01116: error in opening database file string 原因： Usually the file is not accessible. 解决： Restore the database file.

ORA-01117: adding file \

原因： An attempt was made to add a database file with a block size that is greater than the maximum block size allowed.

解决： Retry the DDL command with a smaller block size.

ORA-01118: cannot add any more database files: limit of string exceeded 原因： There is no more room in the control file for adding database files. 解决： Resize the control file or drop other tablespaces. ORA-01119: error in creating database file \

原因： Usually due to not having enough space on the device. 解决： none

第44页

ORA-01120: cannot remove online database file string 原因： Attempting to drop a datafile when it is online 解决： Take file offline before dropping.

ORA-01121: cannot rename database file string - file is in use or recovery

原因： Attempted to use ALTER DATABASE RENAME to rename a datafile that is online in an open instance or is being recovered.

解决： Close database in all instances and end all recovery sessions. ORA-01122: database file string failed verification check

原因： The information in this file is inconsistent with information from the control file. See accompanying message for reason.

解决： Make certain that the db files and control files are the correct files for this database. ORA-01123: cannot start online backup; media recovery not enabled

原因： An attempt to start backup of an on-line tablespace failed because media recovery is not enabled.

解决： Enable media recovery and retry this operation.

ORA-01124: cannot recover data file string - file is in use or recovery

原因： An attempt to do media recovery found that the file was not available for recovery. Either it is online and the database is open in some instance, or another process is curently doing media recovery on the file.

解决： Do not do media recovery.

ORA-01125: cannot disable media recovery - file string has online backup set

原因： An attempt to disable media recovery found that an online backup is still in progress. 解决： End the backup of the offending tablespace and retry this command.

ORA-01126: database must be mounted in this instance and not open in any instance 原因： Obvious 解决： none

ORA-01127: database name \ 原因： Obvious 解决： none

ORA-01128: cannot start online backup - file string is offline

原因： An attempt to start an online backup found that one of the files is offline. 解决： Bring the offending files online and retry this command or do a cold backup. ORA-01129: user\ 原因： The user\解决： Reassign the default or temporary tablespace.

ORA-01135: file string accessed for DML/query is offline 原因： Attempted to access a data file that is offline 解决： Bring the data file back online

ORA-01136: specified size of file string (string blocks) is less than original size of string blocks 原因： A file size was specified in the AS clause of ALTER DATABASE CREATE DATAFILE, and the size was smaller the the size needed 解决： Create the file with a larger size.

ORA-01137: data file string is still in the middle of going offline

原因： It was not possible to get the lock for a file that is offline when attempting to bring it

第45页

online. The most likely cause is that the lock is still held by the instance that is took it offline. 解决： Wait a bit and try to online the file again.

ORA-01138: database must either be open in this instance or not at all 原因： The requested operation can not be done when the database is mounted but not open in this instance, and another instance has the database open.

解决： Execute the operation in an open instance, open the datbase in this instance, or close the database in the other instances.

ORA-01139: RESETLOGS option only valid after an incomplete database recovery

原因： The RESETLOGS option was given in ALTER DATABASE OPEN, but there has been no incomplete recovery session.

解决： Retry the ALTER DATABASE OPEN without specifying RESETLOGS ORA-01140: cannot end online backup - all files are offline or readonly 原因： All the files were found to be offline or readonly when attempting to end an online backup. 解决： None. Online backup does not need to be ended for this tablespace. ORA-01141: error renaming data file string - new file \ 原因： An attempt to change a data file\with the new name.

解决： Make sure that the data file has been properly renamed by the operating system and retry. ORA-01142: cannot end online backup - none of the files are in backup

原因： None of the files were found to be in online backup when attempting to end an online backup.

解决： None. Online backup does not need to be ended for this tablespace. ORA-01143: cannot disable media recovery - file string needs media recovery

原因： An attempt to disable media recovery found a file that needs media recovery, thus media recovery cannot be disabled.

解决： Recover the offending file or drop the tablespace it belongs to and retry this command. ORA-01144: File size (string blocks) exceeds maximum of string blocks 原因： Specified file size is larger than maximum allowable size value. 解决： Specify a smaller size.

ORA-01145: offline immediate disallowed unless media recovery enabled 原因： ALTER TABLESPACE ... OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE ... OFFLINE is only allowed if database is in ARCHIVELOG mode. 解决： Take tablespace offline normally or shutdown abort. Reconsider your backup strategy. You could do this if you were archiving your logs.

ORA-01146: cannot start online backup - file string is already in backup

原因： When starting an online backup it was noticed that an online backup was already started for one of the data files.

解决： End the first backup before beginning another. ORA-01147: SYSTEM tablespace file string is offline

原因： A file belonging to the SYSTEM tablespace has been marked offline by the DBA. The database cannot be started until all SYSTEM tablespace files are online and openable. 解决： Bring the file online.

ORA-01148: cannot refresh file size for datafile string 原因： An operating system or device error occurred when retrieving the file\

第46页

which the file resides may have been offline. 解决： Restore access to the device.

ORA-01149: cannot shutdown - file string has online backup set

原因： An attempt to shutdown normally found that an online backup is still in progress. 解决： End the backup of the offending tablespace and retry this command. ORA-01150: cannot prevent writes - file string has online backup set 原因： An attempt to make a tablespace read only or offline normal found that an online backup is still in progress. It will be necessary to write the file header to end the backup, but that would not be allowed if this command succeeded.

解决： End the backup of the offending tablespace and retry this command. ORA-01151: use media recovery to recover block, restore backup if needed 原因： Error 1172 occurred.

解决： This is additional information for error 1172.

ORA-01152: file string was not restored from a sufficiently old backup

原因： An incomplete recovery session was started, but an insufficient number of logs were applied to make the database consistent. This file is still in the future of the last log applied. The most likely cause of this error is forgetting to restore the file from a backup before doing incomplete recovery.

解决： Either apply more logs until the database is consistent or restore the database file from an older backup and repeat recovery.

ORA-01153: an incompatible media recovery is active

原因： Attempted to start an incompatible media recovery or open resetlogs during media recovery or RMAN backup . Media recovery sessions are incompatible if they attempt to recover the same data file. Incomplete media recovery or open resetlogs is incompatible with any media recovery. Backup or restore by RMAN is incompatible with open resetlogs

解决： Complete or cancel the other media recovery session or RMAN backup ORA-01154: database busy. Open, close, mount, and dismount not allowed now

原因： Some operation is in progress that expects the opened/mounted state of this instance to remain the same.

解决： Wait for the operation to complete then retry. If attempting to do a shutdown, SHUTDOWN ABORT will work. If this is a shutdown of a standby database that is operating in NO DATA LOSS mode, you must shutdown the primary database first. ORA-01155: the database is being opened, closed, mounted or dismounted

原因： The requested operation needs the instance to be in a particular state but the state is being changed.

解决： Wait for the open, close, mount, or dismount to complete then retry the operation. If necessary, a SHUTDOWN ABORT will always work.

ORA-01156: recovery in progress may need access to files

原因： Either media recovery or instance recovery is in progress. It may need the files this operation is being applied to.

解决： Wait for recovery to complete.

ORA-01157: cannot identify/lock data file string - see DBWR trace file

原因： The background process was either unable to find one of the data files or failed to lock it because the file was already in use. The database will prohibit access to this file but other files will

第47页

be unaffected. However the first instance to open the database will need to access all online data files. Accompanying error from the operating system describes why the file could not be identified. 解决： Have operating system make file available to database. Then either open the database or do ALTER SYSTEM CHECK DATAFILES.

ORA-01158: database string already mounted

原因： Another instance has a database by this name mounted.

解决： Find which instance is still running. Perhaps you have not lost the control files after all. ORA-01159: file is not from same database as previous files - wrong database id 原因： Not all of the files specified in CREATE CONTROLFILE are from the same database. The database ID of this file does not match that from the first file specified. 解决： Please double check the list of files provided to the CREATE ORA-01160: file is not a string

原因： The named file in the DATAFILE or LOGFILE section of the CREATE CONTROLFILE command does not appear to be as stated.

解决： Please double check the mentioned file.

ORA-01161: database name string in file header does not match given name of string

原因： The database name given at the command line does not match the database name found in the file header.

解决： Chance are good that the database name specified at the command line is incorrect. Resolve the descepency, and resubmit the command. If you are attempting to change the database name, be sure to use the SET DATABASE option.

ORA-01162: block size string in file header does not match configured block sizes

原因： CREATE CONTROLFILE discovered that the block size for this file is incompatible with any of the configured cache blocksizes in the INIT.ORA file.

解决： Configure the appropriate cache for this block size using one of the various (db_2k_cache_size, db_4k_cache_size, db_8k_cache_size, db_16k_cache_size, db_32K_cache_size) parameters.

ORA-01163: SIZE clause indicates string (blocks), but should match header string

原因： The size specified in bytes in the SIZE clause of the CREATE CONTROLFILE statement does not equate to the number of blocks recorded in the header. 解决： Specify the correct filename and size ( in bytes ). ORA-01164: MAXLOGFILES may not exceed string

原因： MAXLOGFILES specified on the command line too large. 解决： Resubmit the command with a smaller MAXLOGFILES ORA-01165: MAXDATAFILES may not exceed string

原因： MAXDATAFILES specified on the command line too large. 解决： Resubmit the command with a smaller MAXDATAFILES ORA-01166: file number string is larger than string (string)

原因： File mentioned in CREATE CONTROLFILE has a file number which is larger than that specified for MAXDATAFILES or MAXLOGFILES.

解决： Increase the maximum specified on the command line.

ORA-01167: two files are the same file/group number or the same file

原因： There is an overlap of file numbers in the files specified on the command line or the same

第48页

file is specified twice. If they are not the exact same file then one is likely to be a backup of the other. If they are two members of the same log they must be specified together in a group file spec. This message will also appear if the same control file appears more than once in the control_files parameter in the init.ora file. If this happens, check for additional error messages. 解决： Confirm that the file mentioned is not a repeat of a file already mentioned in the command. If they are different files then omit the earlier backup. If they are members of the same log, insure they are in the same group file specification. If this message appears because of a duplicate control file, check the control_files parameter in the init.ora file and see if a file is specified more than once. If all files names appear to be unique, check to make sure that the actual control files themselves are unique. For example, in UNIX check for a symbolic or a hard link to another control file in the list.

ORA-01168: physical block size string does not match size string of other members

原因： The file is located on a device with a different physical block size than the other members in the group

解决： Use a physical device with matching block size.

ORA-01169: DATAFILE number 1 not found. Must be present

原因： Datafile number 1 was not specified in a CREATE CONTROLFILE command. 解决： Locate datafile number 1 and resubmit the CREATE CONTROLFILE command. ORA-01170: file not found \

原因： ALL datafiles and, if NORESETLOGS, ALL logfiles MUST be accessible by the process for CREATE CONTROLFILE.

解决： The file specified probably contains a typing error. Double check command and the existance of all files and then resubmit.

ORA-01171: datafile string going offline due to error advancing checkpoint

原因： The checkpoint in the file header could not be advanced. See accompanying errors for the reason. The datafile will be taken offline the same as for a write error of a data block.

解决： See accompanying errors for details. Restore access to the file, do media recovery, and bring it back online.

ORA-01172: recovery of thread string stuck at block string of file string 原因： Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery. 解决： Do a RECOVER DATAFILE for the file containing the block. If this does not resolve the problem then restore the file from a backup and recover it.

ORA-01173: data dictionary indicates missing data file from system tablespace

原因： Either the database has been recovered to a point in time in the future of the control file or a datafile from the system tablespace was omitted from the create control file command previously issued.

解决： For the former problem you need to recover the database from a more recent control file. For the latter problem, simply recreate the control file checking to be sure that you include all the datafiles in the system tablespace.

ORA-01174: DB_FILES is string buts needs to be string to be compatible

原因： The maximum number of database files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open. 解决： Change the value of the DB_FILES parameter to be compatible

第49页

ORA-01175: data dictionary has more than the string files allowed by the instance

原因： The data dictionary is found to have more files than that which can be supported by this instance.

解决： Shutdown the instance and restart with a larger number of db_files

ORA-01176: data dictionary has more than the string files allowed by the controlfie

原因： After a CREATE CONTROLFILE, the data dictionary was found to have more datafiles than that supported by the control file.

解决： Recreate the control file with a larger MAXDATAFILES.

ORA-01177: data file does not match dictionary - probably old incarnation

原因： When comparing the control file with the data dictionary after a CREATE CONTROLFILE or OPEN RESETLOGS, it was noted that this datafile was inconsistent with the dictionary. Most likely the file is a backup of a file that was dropped from the database, and the same file number was reused for a new file. It may also be that an incomplete recovery stopped at a time when this file number was used for another datafile.

解决： Do a CREATE CONTROLFILE with the correct file or none at all.

ORA-01178: file string created before last CREATE CONTROLFILE, cannot recreate

原因： Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that existed at the last CREATE CONTROLFILE command. The information needed to recreate the file was lost with the control file that existed when the file was added to the database.

解决： Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created.

ORA-01179: file string does not exist

原因： During datafile recovery, a file was listed which was not part for the database. 解决： Recheck the datafile name. Remember to use double quotes at the SQLDBA command line and remember that the file name is translated in the environment of the SQLDBA. ORA-01180: can not create datafile 1

原因： Attempting to create datafile 1 using ALTER DATABASE CREATE DATAFILE. 解决： Recover file from a backup or recreate database.

ORA-01181: file string created before last known RESETLOGS, cannot recreate

原因： Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that existed before the last known RESETLOGS.

解决： Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created.

ORA-01182: cannot create database file string - file is in use or recovery

原因： Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that is online in an open instance or is being recovered.

解决： Close database in all instances and end all recovery sessions ORA-01183: cannot mount database in SHARED mode

原因： Some other instance has the database mounted exclusive. 解决： Shutdown other instance then mount shared. ORA-01184: logfile group string already exists

原因： An ALTER DATABASE ADD LOGFILE command specified a log number for the new log which is already in use.

解决： Specify a different logfile number, or let the database choose an unused value.

第50页

本文来源：https://www.bwwdw.com/article/utoo.html