ORA-01041: internal error. hostdef extension doesn t exist
Cause: Pointer to hstdef extension in hstdef is null.
Action: Report as a bug
Cause: Pointer to hstdef extension in hstdef is null.
Action: Report as a bug
Monday 9 January 2012
ORA-01040: invalid character in password; logon denied
ORA-01040: invalid character in password; logon denied
Cause: There are multibyte characters in the password or some characters in the password are not in US7ASCII range.
Action: Resubmit password with valid characters.
Cause: There are multibyte characters in the password or some characters in the password are not in US7ASCII range.
Action: Resubmit password with valid characters.
ORA-01039: insufficient privileges on underlying objects of the view
ORA-01039: insufficient privileges on underlying objects of the view
Cause: Attempting to explain plan on other people s view without the necessary privileges on the underlying objects of the view.
Action: Get necessary privileges or do not perform the offending operation.
Cause: Attempting to explain plan on other people s view without the necessary privileges on the underlying objects of the view.
Action: Get necessary privileges or do not perform the offending operation.
ORA-01038: cannot write database file version string with ORACLE version string
ORA-01038: cannot write database file version string with ORACLE version string
Cause: 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.
Action: 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.
Cause: 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.
Action: 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.
ORA-01037: maximum cursor memory exceeded
ORA-01037: maximum cursor memory exceeded
Cause: Attempting to process a complex sql statement which consumed all available memory of the cursor.
Action: Simplify the complex sql statement.
Cause: Attempting to process a complex sql statement which consumed all available memory of the cursor.
Action: Simplify the complex sql statement.
ORA-01036: illegal variable name or number
ORA-01036: illegal variable name or number
Cause: Unable to find bind context on user side
Action: Make sure that the variable being bound is in the sql statement.
Cause: Unable to find bind context on user side
Action: Make sure that the variable being bound is in the sql statement.
ORA-01035: ORACLE only available to users with RESTRICTED SESSION privilege
ORA-01035: ORACLE only available to users with RESTRICTED SESSION privilege
Cause: Logins are disallowed because an instance started in restricted mode. Only users with RESTRICTED SESSION system privilege can log on.
Action: Request that Oracle be restarted without the restricted option or obtain the RESTRICTED SESSION system privilege.
Cause: Logins are disallowed because an instance started in restricted mode. Only users with RESTRICTED SESSION system privilege can log on.
Action: Request that Oracle be restarted without the restricted option or obtain the RESTRICTED SESSION system privilege.
ORA-01034: ORACLE not available
ORA-01034: ORACLE not available
Cause: Oracle was not started up. Possible causes include the following:
Action: 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.
Cause: Oracle was not started up. Possible causes include the following:
Action: 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-01033: ORACLE initialization or shutdown in progress
ORA-01033: ORACLE initialization or shutdown in progress
Cause: An attempt was made to log on while Oracle is being started up or shutdown.
Action: Wait a few minutes. Then retry the operation.
Cause: An attempt was made to log on while Oracle is being started up or shutdown.
Action: Wait a few minutes. Then retry the operation.
ORA-01032: no such userid
ORA-01032: no such userid
Cause: This is an internal error message related to Export or Import.
Action: Contact customer support.
Cause: This is an internal error message related to Export or Import.
Action: Contact customer support.
ORA-01031: insufficient privileges
ORA-01031: insufficient privileges
Cause: 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.
Action: 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.
Cause: 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.
Action: 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-01030: SELECT ... INTO variable does not exist
ORA-01030: SELECT ... INTO variable does not exist
Cause: The SELECT... INTO specified in the bind call does not correspond to a variable in the SQL statement.
Action: If it is not possible to correct the statement, call customer support.
Cause: The SELECT... INTO specified in the bind call does not correspond to a variable in the SQL statement.
Action: If it is not possible to correct the statement, call customer support.
ORA-01029: internal two task error
ORA-01029: internal two task error
Cause: Received a request to send the long again when there is no long
Action: Report as a bug
Cause: Received a request to send the long again when there is no long
Action: Report as a bug
ORA-01028: internal two task error
ORA-01028: internal two task error
Cause: Received send long message but don t have the cursor context.
Action: Report as a bug.
Cause: Received send long message but don t have the cursor context.
Action: Report as a bug.
ORA-01027: bind variables not allowed for data definition operations
ORA-01027: bind variables not allowed for data definition operations
Cause: An attempt was made to use a bind variable in a SQL data definition operation.
Action: Such bind variables are not allowed.
Cause: An attempt was made to use a bind variable in a SQL data definition operation.
Action: Such bind variables are not allowed.
ORA-01026: multiple buffers of size lamp;gt; 4000 in the bind list
ORA-01026: multiple buffers of size lamp;gt; 4000 in the bind list
Cause: More than one long buffer in the bind list.
Action: Change the buffer size to be less than 4000 for the bind variable bound to a normal column.
Cause: More than one long buffer in the bind list.
Action: Change the buffer size to be less than 4000 for the bind variable bound to a normal column.
ORA-01025: UPI parameter out of range
ORA-01025: UPI parameter out of range
Cause: An integer parameter to a upi function is out of range.
Action: This usually indicates an error in a tool built on top of the oracle dbms. Report the error to your customer support representative.
Cause: An integer parameter to a upi function is out of range.
Action: This usually indicates an error in a tool built on top of the oracle dbms. Report the error to your customer support representative.
ORA-01023: Cursor context not found (Invalid cursor number)
ORA-01023: Cursor context not found (Invalid cursor number)
Cause: The cursor number is not a valid open cursor.
Action: Make sure that the cursor is open.
Cause: The cursor number is not a valid open cursor.
Action: Make sure that the cursor is open.
ORA-01022: database operation not supported in this configuration
ORA-01022: database operation not supported in this configuration
Cause: The attempted database operation does not conform to the user programming interface (UPI) for the two communicating ORACLE servers.
Action: 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.
Cause: The attempted database operation does not conform to the user programming interface (UPI) for the two communicating ORACLE servers.
Action: 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-01019: unable to allocate memory in the user side
ORA-01019: unable to allocate memory in the user side
Cause: The user side memory allocator returned error.
Action: Increase the processes heap size or switch to the old set of calls.
Cause: The user side memory allocator returned error.
Action: Increase the processes heap size or switch to the old set of calls.
ORA-01016: This function can be called only after a fetch
ORA-01016: This function can be called only after a fetch
Cause: Cursor in an invalid state.
Action: Make sure that the oci or upi function is called after fetch.
Cause: Cursor in an invalid state.
Action: Make sure that the oci or upi function is called after fetch.
ORA-01010: invalid OCI operation
ORA-01010: invalid OCI operation
Cause: 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) 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.
Action: 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.
Cause: 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) 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.
Action: 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-00991: only MAC privileges may be granted to procedures
ORA-00991: only MAC privileges may be granted to procedures
Cause: Object privileges or non-MAC system privileges were granted to the procedure.
Action: Only grant MAC privileges using the PROCEDURE clause.
Cause: Object privileges or non-MAC system privileges were granted to the procedure.
Action: Only grant MAC privileges using the PROCEDURE clause.
ORA-00983: cannot audit or noaudit SYS user actions
ORA-00983: cannot audit or noaudit SYS user actions
Cause: An attempt was made to AUDIT or NOAUDIT SYS user actions.
Action: Execute the statement again with a valid user.
Cause: An attempt was made to AUDIT or NOAUDIT SYS user actions.
Action: Execute the statement again with a valid user.
ORA-00981: cannot mix table and system auditing options
ORA-00981: cannot mix table and system auditing options
Cause: Table and system-wide auditing options were specified in the same AUDIT or NOAUDIT statement.
Action: You must issue table and system options in separate statements.
Cause: Table and system-wide auditing options were specified in the same AUDIT or NOAUDIT statement.
Action: You must issue table and system options in separate statements.
ORA-00977: duplicate auditing option
ORA-00977: duplicate auditing option
Cause: AUDIT or NOAUDIT statement specifies an option more than once
Action: Either use ALL with no other auditing options or make sure no option is listed more than once.
Cause: AUDIT or NOAUDIT statement specifies an option more than once
Action: Either use ALL with no other auditing options or make sure no option is listed more than once.
ORA-00976: LEVEL, PRIOR, or ROWNUM not allowed here
ORA-00976: LEVEL, PRIOR, or ROWNUM not allowed here
Cause: LEVEL, PRIOR, or ROWNUM is being specified at illegal location.
Action: Remove LEVEL, PRIOR, or ROWNUM.
Cause: LEVEL, PRIOR, or ROWNUM is being specified at illegal location.
Action: Remove LEVEL, PRIOR, or ROWNUM.
ORA-00972: identifier is too long
ORA-00972: identifier is too long
Cause: An identifier with more than 30 characters was specified.
Action: Specify at most 30 characters.
Cause: An identifier with more than 30 characters was specified.
Action: Specify at most 30 characters.
ORA-00965: column aliases not allowed for *
ORA-00965: column aliases not allowed for *
Cause: The statement is trying to alias the * expression in the select list which is not legal.
Action: Remove the alias.
Cause: The statement is trying to alias the * expression in the select list which is not legal.
Action: Remove the alias.
ORA-00964: table name not in FROM list
ORA-00964: table name not in FROM list
Cause: The table name referred in the select list is not specified in the from list.
Action: Make sure the name is correctly specified and matches one of the names in the from list.
Cause: The table name referred in the select list is not specified in the from list.
Action: Make sure the name is correctly specified and matches one of the names in the from list.
ORA-00962: too many group-by or order-by expressions
ORA-00962: too many group-by or order-by expressions
Cause: The group-by or order-by column list contain more than 1000 expressions.
Action: Use 1000 or less expressions in the group-by or order-by list.
Cause: The group-by or order-by column list contain more than 1000 expressions.
Action: Use 1000 or less expressions in the group-by or order-by list.
ORA-00960: ambiguous column naming in select list
ORA-00960: ambiguous column naming in select list
Cause: A column name in the order-by list matches more than one select list columns.
Action: Remove duplicate column naming in select list.
Cause: A column name in the order-by list matches more than one select list columns.
Action: Remove duplicate column naming in select list.
ORA-00956: missing or invalid auditing option
ORA-00956: missing or invalid auditing option
Cause: AUDIT or NOAUDIT statement contains an invalid auditing option.
Action: Use a valid option.
Cause: AUDIT or NOAUDIT statement contains an invalid auditing option.
Action: Use a valid option.
ORA-00953: missing or invalid index name
ORA-00953: missing or invalid index name
Cause: An index name of the form ( lamp;lt;lamp;nbsp;identifierlamp;gt; . ( lamp;lt;lamp;nbsp;identifierlamp;gt; is expected but not present. If OIDINDEX clause, index name must be lamp;lt;lamp;nbsp;identifierlamp;gt;
Action: Enter an appropriate index name.
Cause: An index name of the form ( lamp;lt;lamp;nbsp;identifierlamp;gt; . ( lamp;lt;lamp;nbsp;identifierlamp;gt; is expected but not present. If OIDINDEX clause, index name must be lamp;lt;lamp;nbsp;identifierlamp;gt;
Action: Enter an appropriate index name.
ORA-00912: input parameter too long
ORA-00912: input parameter too long
Cause: one of your input strings was too long
Action: shorten the input parameter length
Cause: one of your input strings was too long
Action: shorten the input parameter length
ORA-00911: invalid character
ORA-00911: invalid character
Cause: 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.
Action: none
Cause: 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.
Action: none
ORA-00910: specified length too long for its datatype
ORA-00910: specified length too long for its datatype
Cause: for datatypes CHAR and RAW, the length specified was lamp;gt; 2000; otherwise, the length specified was lamp;gt; 4000.
Action: use a shorter length or switch to a datatype permitting a longer length such as a VARCHAR2, LONG CHAR, or LONG RAW
Cause: for datatypes CHAR and RAW, the length specified was lamp;gt; 2000; otherwise, the length specified was lamp;gt; 4000.
Action: use a shorter length or switch to a datatype permitting a longer length such as a VARCHAR2, LONG CHAR, or LONG RAW
ORA-00832: no streams pool created and cannot automatically create one
ORA-00832: no streams pool created and cannot automatically create one
Cause: 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.
Action: Please set the parameter streams_pool_size or set sga_target.
Cause: 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.
Action: Please set the parameter streams_pool_size or set sga_target.
ORA-00830: cannot set statistics_level to BASIC with auto-tune SGA enabled
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.
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.
ORA-00828: specified value of shared_pool_reserved_size inconsistent with internal settings
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.
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-00827: could not shrink sga_target to specified value
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.
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-00826: cannot set sga_target for an ASM instance
ORA-00826: cannot set sga_target for an ASM instance
Cause: sga_target set for an ASM instance.
Action: Do not set sga_target.
Cause: sga_target set for an ASM instance.
Action: Do not set sga_target.
ORA-00825: cannot set db_block_buffers if sga_target set
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.
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-00824: cannot set sga_target due to existing internal settings, see alert log for more information
ORA-00824: cannot set sga_target due to existing internal settings, see alert log for more information
Cause: Unable to set sga_target due to current parameter settings.
Action: See alert log for more information.
Cause: Unable to set sga_target due to current parameter settings.
Action: See alert log for more information.
ORA-00823: Specified value of sga_target greater than sga_max_size
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.
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-00822: MMAN process terminated with error
ORA-00822: MMAN process terminated with error
Cause: The Memory Management process died.
Action: Warm start instance
Cause: The Memory Management process died.
Action: Warm start instance
ORA-00821: Specified value of sga_target stringM is too small, needs to be at least stringM
ORA-00821: Specified value of sga_target stringM 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.
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-00820: Specified value of sga_max_size is too small, needs to be at least stringM
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.
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-00750: database has been previously mounted and dismounted
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.
Cause: The instance has already mounted and dismounted the database, which is only allowed once in its lifetime.
Action: Shut down the database.
ORA-00741: logfile size of (string) blocks exceeds maximum logfile size
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.
Cause: The user specified logfile size exceeded maximum logfile size.
Action: Please check REFERENCE for maximum size. Reduce the size and retry.
ORA-00740: datafile size of (string) blocks exceeds maximum file size
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.
Cause: The user specified datafile size exceeded maximum file size.
Action: Please check REFERENCE for maximum size. Reduce the size and retry.
ORA-00724: ALTER DATABASE CONVERT command has been de-supported
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.
Cause: ALTER DATABASE CONVERT command has been de-supported since Oracle 10i.
Action: No action required.
ORA-00723: Initialization parameter COMPATIBLE must be explicitly set
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.
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-00722: Feature string
ORA-00722: Feature string
Cause: Reporting name of the feature for details of another error.
Action: See associated error message.
Cause: Reporting name of the feature for details of another error.
Action: See associated error message.
ORA-00721: changes by release string cannot be used by release string
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.
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-00720: ALTER DATABASE RESET COMPATIBILITY command has been de-supported
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.
Cause: ALTER DATABASE RESET COMPATIBILITY command has been de-supported since Oracle 10i.
Action: No action required.
ORA-00712: cannot rename system tablespace
ORA-00712: cannot rename system tablespace
Cause: An attempt to rename the system tablespace failed.
Action: No action required.
Cause: An attempt to rename the system tablespace failed.
Action: No action required.
ORA-00711: new tablespace name is invalid
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.
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-00710: new tablespace name is the same as the old tablespace name
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.
Cause: An attempt to rename a tablespace failed because the new name is the same as the old name.
Action: No action required.
ORA-00706: error changing format of file string
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.
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.
Subscribe to:
Posts (Atom)