Overblog Suivre ce blog
Editer la page Administration Créer mon blog
/ / /

Erreurs ORA-00601 à ORA-00830 Cause et Action


ORA-00601 ORA-00601: cleanup lock conflict
Cause PMON process runs into lock conflict trying to recovery processes
Action This is trapped internally, no action necessary

ORA-00602 ORA-00602: internal programming exception
Cause Internal programming exception
Action Report as bug

ORA-00603 ORA-00603: ORACLE server session terminated by fatal error
Cause An ORACLE server session is in an unrecoverable state.
Action Login to ORACLE again so a new server session will be created

ORA-00604 ORA-00604: error occurred at recursive SQL level string
Cause An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables).
Action If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support.

ORA-00606 ORA-00606: Internal error code
Cause A call to deferred upi functions was made in non deferred mode
Action Report as a bug.

ORA-00607 ORA-00607: Internal error occurred while making a change to a data block
Cause An internal error or memory exception occurred while Oracle was applying redo to a data block.
Action call Oracle Support

ORA-00608 ORA-00608: testing error [string] [string] [string] [string] [string]
Cause Internal error reserved for testing.
Action call Oracle Support

ORA-00701 ORA-00701: object necessary for warmstarting database cannot be altered
Cause Attempt to alter or drop a database object (table, cluster, or index) which are needed for warmstarting the database.
Action None.

ORA-00702 ORA-00702: bootstrap verison 'string' inconsistent with version 'string'
Cause The reading version of the boostrap is incompatible with the current bootstrap version.
Action Restore a version of the software that is compatible with this bootstrap version.

ORA-00703 ORA-00703: maximum number of row cache instance locks exceeded
Cause There are not enough row cache enqueues.
Action Increase the row cache enqueue parameter and warm start the system.

ORA-00704 ORA-00704: bootstrap process failure
Cause Failure in processing bootstrap data - see accompanying error.
Action Contact your customer support representative.

ORA-00705 ORA-00705: inconsistent state during start up; shut down the instance, then restart it
Cause A previous attempt to start an instance was terminated.
Action Shut down the instance completely, then restart it.

ORA-00706 ORA-00706: error changing format of file 'string'
Cause An attempt to change the block0 format of the specified file failed because the file is read-only or offline.
Action Make the file read-write or bring the file online and set the BLK0_FMTCHG event.

ORA-00710 ORA-00710: new tablespace name is the same as the old tablespace name
Cause An attempt to rename a tablespace failed because the new name is the same as the old name.
Action No action required.

ORA-00711 ORA-00711: new tablespace name is invalid
Cause An attempt to rename a tablespace failed because the new name is invalid.
Action Choose a valid new name and retry the command.

ORA-00712 ORA-00712: cannot rename system tablespace
Cause An attempt to rename the system tablespace failed.
Action No action required.

ORA-00720 ORA-00720: ALTER DATABASE RESET COMPATIBILITY command has been de-supported
Cause ALTER DATABASE RESET COMPATIBILITY command has been de-supported since Oracle 10i.
Action No action required.

ORA-00721 ORA-00721: changes by release string cannot be used by release string
Cause An attempt to import a tablespace failed because the tablespace contains changes that require a newer software release or that violate the compatibility parameters.
Action Use a version of the software that can understand the changes or relax the compatibility requirements in the initialization parameter file.

ORA-00722 ORA-00722: Feature "string"
Cause Reporting name of the feature for details of another error.
Action See associated error message.

ORA-00723 ORA-00723: Initialization parameter COMPATIBLE must be explicitly set
Cause 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.
Action Explicitly set the value of COMPATIBLE parameter either in PFILE or SPFILE, whichever is used.

ORA-00724 ORA-00724: ALTER DATABASE CONVERT command has been de-supported
Cause ALTER DATABASE CONVERT command has been de-supported since Oracle 10i.
Action No action required.

ORA-00740 ORA-00740: datafile size of (string) blocks exceeds maximum file size
Cause The user specified datafile size exceeded maximum file size.
Action Please check REFERENCE for maximum size. Reduce the size and retry.

ORA-00741 ORA-00741: logfile size of (string) blocks exceeds maximum logfile size
Cause The user specified logfile size exceeded maximum logfile size.
Action Please check REFERENCE for maximum size. Reduce the size and retry.

ORA-00750 ORA-00750: database has been previously mounted and dismounted
Cause The instance has already mounted and dismounted the database, which is only allowed once in its lifetime.
Action Shut down the database.

ORA-00820 ORA-00820: Specified value of sga_max_size is too small, needs to be at least stringM
Cause 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.
Action Set sga_max_size to the recommended value or reduce the values of any SGA component size parameters you have specified.

ORA-00821 ORA-00821: Specified value of sga_target is too small, needs to be at least stringM
Cause 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.
Action Set sga_target to the recommended value or reduce the values of any SGA component size parameters you have specified.

ORA-00822 ORA-00822: MMAN process terminated with error
Cause The Memory Management process died.
Action Warm start instance

ORA-00823 ORA-00823: Specified value of sga_target greater than sga_max_size
Cause The specified value of sga_target is greater than sga_max_size.
Action Increase sga_max_size to match up with sga_target or decrease sga_target to match up with sga_maxsize.

ORA-00824 ORA-00824: cannot set sga_target due to existing internal settings
Cause Unable to set sga_target due to current parameter settings.
Action See alert log for more information.

ORA-00825 ORA-00825: cannot set db_block_buffers if sga_target set
Cause sga_target set with db_block_buffers set.
Action 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 ORA-00826: cannot set sga_target for an ASM instance
Cause sga_target set for an ASM instance.
Action Do not set sga_target.

ORA-00827 ORA-00827: could not shrink sga_target to specified value
Cause Attempted to shrink the SGA to the specified value but did not succeed because the SGA components could not be shrunk as they were already at their minimum sizes.
Action Do not set sga_target to a value below the current value without first shrinking the individual SGA components.

ORA-00828 ORA-00828: specified value of shared_pool_reserved_size inconsistent with internal settings
Cause 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.
Action 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 ORA-00830: cannot set statistics_level to BASIC with auto-tune SGA enabled
Cause 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.
Action Disable auto-tune SGA and try setting the statistics_level to BASIC again.

Partager cette page

Repost 0
Published by