Release 8.0
A54625_01
 Library |
 Product |
 Contents |
| Oracle8
Error Messages Release 8.0 A54625_01 |
|
This section lists messages generated when the National Language Support feature of Oracle is accessed.
Cause: An invalid NLS initialization parameter was specified.
Action: Check the syntax and spelling of the parameter. Enter the correct parameter into the initialization parameter file.
Cause: The character set specified in the CREATE DATABASE command does not exist on the system.
Action: Refer to your Oracle operating system-specific documentation for more information about character sets on the system. Use a valid character set in the CREATE DATABASE command.
Cause: An invalid parameter or value was entered in the NLS parameter string in a SQL function.
Action: Check the syntax of the function and the parameters. Enter the command again using the correct syntax and valid values.
Cause: An attempt was made to use the CONVERT function to convert between two character sets, and the requested conversion is not possible due to unavailability of one or both character sets.
Action: Use character sets available on the system in the CONVERT function.
Cause: One of the following:
Action: Strings declared with NCHAR or NCHAR VARYING do not interoperate with strings declared with CHAR or VARCHAR2. Use TRANSLATE() function to explicitly convert one to the other.
Cause: There are two possible causes: Either an attempt was made to issue an ALTER SESSION statement with an invalid NLS parameter or value; or the NLS_LANG environment variable contains an invalid language, territory, or character set.
Action: Check the syntax of the ALTER SESSION command and the NLS parameter, correct the syntax and retry the statement, or specify correct values in the NLS_LANG environment variable. For more information about the syntax of the ALTER SESSION command, see the index entry on "ALTER SESSION command" in Oracle8 Server SQL Reference.
Cause: An attempt was made to create a database on an ASCII-based machine using an EBCDIC-based character set or vice versa. This is not permitted.
Action: Create the database using either ASCII-based or EBCDIC-based character sets, depending on what is supported by the hardware. Refer to your Oracle operating system-specific documentation for more information about the type of character set supported.
This section lists some of the messages generated during a parallel query or parallel index creation.
Cause: The load on the system is too high to perform parallel queries.
Action: Re-enter the statements serially or wait until the system load is reduced.
Cause: A parallel query server encountered an exception as described in the accompanying message(s).
Action: Correct the error described in the accompanying message.
Cause: A parallel query server was unable to communicate with the server coordinating the parallel query.
Action: Check for operating system or network errors and retry the statement. If this problem persists, contact customer support.
Cause: A parallel query server was unable to communicate with another server involved in the parallel query.
Action: Check for operating system or network errors and retry the statement. If this problem persists, contact customer support.
Cause: Process information for a parallel query server thread cannot be found.
Action: Check for operating system errors and retry the statement. If this problem persists, contact customer support.
Cause: The PMON process is cleaning up the process because a parallel query server terminated unexpectedly.
Action: Check for operating system errors and retry the statement. If this problem persists, contact customer support.
Cause: This is an internal error that is not usually issued.
Action: Contact customer support.
Cause: This is an internal error that is not usually issued.
Action: Contact customer support.
Cause: An attempt was made, using the ALTER SYSTEM command, to set CACHE_INSTANCES or SCAN_INSTANCES to a value greater than the number of available instances.
Action: See the accompanying message for the allowable maximum value or set SCAN_INSTANCES or CACHE_INSTANCES to ALL.
Cause: An attempt was made to set CACHE_INSTANCES or SCAN_INSTANCES using the ALTER SYSTEM command while the database was mounted in exclusive mode.
Action: Only set CACHE_INSTANCES or SCAN_INSTANCES when the database is mounted in PARALLEL or SHARED mode.
Cause: An attempt was made to set the PARALLEL_MAX_SERVERS initialization parameter to a value higher than the maximum allowed by the system.
Action: See the accompanying message for the allowable maximum value.
Cause: An attempt was made to set the PARALLEL_WIN_SERVERS initialization parameter to a value higher than PARALLEL_MAX_SERVERS.
Action: See the accompanying message for the allowable maximum value.
Cause: PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in a CREATE TABLE, CREATE CLUSTER, CREATE INDEX, ALTER TABLE, ALTER CLUSTER statement, or a RECOVER command.
Action: Specify PARALLEL or NOPARALLEL only once.
Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CREATE CLUSTER, CREATE INDEX, ALTER TABLE, ALTER CLUSTER statement, or a RECOVER command.
Action: Specify a value greater than 0 or specify default parallelism using PARALLEL with no degree or using DEGREE DEFAULT within a PARALLEL clause.
Cause: CACHE was specified more than once, NOCACHE was specified more than once, or CACHE and NOCACHE, were specified in a CREATE TABLE, CREATE CLUSTER, CREATE INDEX, ALTER TABLE, ALTER CLUSTER, or a RECOVER command.
Action: Specify CACHE or NOCACHE only once.
Cause: PARALLEL parameter specifying number of instances must be a positive integer or DEFAULT.
Action: Specify a positive integer or DEFAULT for INSTANCES if parallelism across instances is desired.
Cause: You tried to attempt an operation that requires the parallel query option.
Action: Enable the parallel query option.
Cause: An unrecognized option was specified with a PARALLEL clause.
Action: Specify any combination of DEGREE {<n> | DEFAULT } and INSTANCE { <n> | DEFAULT } within the PARALLEL clause.
Cause: The PARALLEL clause was specified without an option.
Action: Specify any combination of DEGREE { <n> | DEFAULT } and INSTANCE { <n> | DEFAULT } within the PARALLEL clause.
Cause: An invalid value for DEGREE was specified within a PARALLEL clause.
Action: Specify a positive integer or DEFAULT.
Cause: An invalid value for INSTANCES was specified within a PARALLEL clause.
Action: Specify a positive integer or DEFAULT.
Cause: DEGREE or INSTANCE was specified more than once within a PARALLEL clause.
Action: Specify the option only once.
Cause: Either an ALTER DATABASE RECOVER command was specified with the DEGREE DEFAULT option in a PARALLEL clause or another command was specified with no option in the PARALLEL clause.
Action: Specify an explicit degree of parallelism.
Cause: An ALTER DATABASE RECOVER command was specified with the INSTANCES DEFAULT option.
Action: Specify an explicit value for INSTANCES or omit the INSTANCES option if single instance recovery is desired.
Cause: An ALTER DATABASE RECOVER command was specified without the DEGREE option.
Action: Specify an explicit degree of parallelism.
Cause: Parallel query server was hung and subsequently killed.
Action: Re-execute query and report suspicious events noted in the trace file to customer support if error persists.
Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than minimum slaves were acquired.
Action: Either re-execute query with lower PARALLEL_MIN_PERCENT or wait until some running queries are completed, thus freeing up slaves.
For more information about the PARALLEL_MIN_PERCENT parameter, see the index entry on "PARALLEL_MIN_PERCENT parameter" in Oracle8 Server SQL Reference.
Cause: PDML transaction cannot be started because a distributed transaction is in progress.
Action: Change the DML statement to exclude updates to remote tables and reexecute the statement.
Cause: Parallel statement failed because all itls in the current block are occupied by siblings of the same transaction.
Action: Increase MAXTRANS of the block or reduce the degree of parallelism for the statement. Reexecute the statement. Report suspicious events in trace file to Oracle support representative if error persists.
Cause: After executing a parallel INSERT/UPDATE/DELETE statement, a command other than COMMIT or ROLLBACK was issued.
Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
Cause: After executing an INSERT statement with an APPEND hint, a command other than COMMIT or ROLLBACK was issued.
Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
Cause: After executing a query on a global v$ fixed view, one or more instances failed to allocate a slave to process query.
Action: To allow results to be returned by sucessfully allocated slaves, execute ALTER SESSION SET ALLOW_PARTIAL_SN_RESULTS=TRUE statement, or check parameters of instances.
Cause: The coordinator's instance must be a member of the PARALLEL_INSTANCE_GROUP in which this operation will be run.
Action: Either add the coordinator's instance to the current PARALLEL_INSTANCE_GROUP or change PARALLEL_INSTANCE_GROUP.
Cause: The instance group name is too long.
Action: Either shorten the name or get rid of the instance group.
Cause: There must be at least one instance in the OPS_ADMIN_GROUP in order to execute a query on global views.
Action: Change the value of OPS_ADMIN_GROUP.
Cause: Multi Statement Parallel DML restriction violated.
Action: Once a table has been modified in parallel, no more read or modification statements are allowed on that table, within the same transaction. Rewrite the transaction, or brake it up into two transactions.
Cause: Multi Statement Parallel DML restriction violated.
Action: Once a table has been modified, no parallel modification operations are allowed on that table, within the same transaction. Rewrite the transaction or break it up into two transactions.
Cause: Multi Statement Parallel DML restriction violated
Action: Distributed accesses may not be performed after a PDML statement has been issued in a transaction. Commit/rollback the PDML transaction first, and then perform the distributed access, or do it before the first PDML statement in the transaction.
This section lists some of the messages that can be returned when the Spatial Data option is enabled.
Cause: The specified dimension is either smaller than 1 or greater than the number of dimensions encoded in the HHCODE.
Action: Make sure that the dimension number is between 1 and the maximum number of dimensions encoded in the HHCODE.
Cause: The number of dimensions in two HHCODEs involved in a binary HHCODE operation do not match.
Action: Make sure that the number of dimensions in the HHCODEs match.
Cause: The specified level is either smaller than 1 or greater than the maximum level encoded in an HHCODE.
Action: Verify that all levels are between 1 and the maximum number of levels encoded in the HHCODE.
Cause: The specifed range for a dimension is invalid.
Action: Make sure that the lower bound (lb) is less than the upper bound (ub).
Cause: The buffer size for a function is not valid.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: An error occured in a recursively called HHCODE function.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: The cell identifier is either less than 0 or greater that (2^ndim - 1).
Action: Make sure that the cell identifier is between 0 and (2^ndim - 1).
Cause: A character that is not in the range [0-9] or [A-Fa-f] was detected.
Action: Verify that all characters in a string are in [0-9] or [A-Fa-f].
Cause: Part of specified date format is invalid.
Action: Verify that the date format is valid.
Cause: The specified date string has a bad component or does not match the specified format string.
Action: Make sure that the components of the date string are valid and that the date and format strings match.
Cause: An invalid number of arguments was specified for an HHCODE function.
Action: Verify the syntax of the function call.
Cause: A specifed dimension value is outside the range defined for that dimension.
Action: Make sure that all values to be encoded are within the defined dimension range.
Cause: An invalid window type was specifed.
Action: Valid window types are RANGE, PROXIMITY, POLYGON.
Cause: A topology was specified that was not INTERIOR or BOUNDARY.
Action: Make sure that INTERIOR or BOUNDARY is used to describe an HHCODE's topology.
Cause: A topology identifier outside the range of 1 to 8 was specified
Action: Specify a topology in the range of 1 to 8.
Cause: The number of values used to define the window does not correspond to the window type.
Action: Verify that the number of values used to defined the window is correct for the window type and number of dimensions.
Cause: The partition common code was not correctly decoded.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: The shape of a 2-D line partition could not be determined.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: The specified distance type is invalid.
Action: The only supported distance functions are EUCLID and MANHATTAN.
Cause: Vertex coordinates lie outside the valid range for specified dimension
Action: Re-define vertex coordinates within specified boundaries
Cause: A vertex coordinate has a NULL value
Action: Re-define vertex coordinate to have non-NULL value
Cause: The coordinates defining a geometric element are not connected
Action: Re-define coordinates for the geometric element
Cause: The coordinates defining a polygonal geometric element represent crossing segments
Action: Re-define coordinates for the polygon
Cause: An interior element of a geometric object interacts with the exterior element of that object
Action: Re-define coordinates for the geometric elements
Cause: The coordinates defining a polygonal geometric element represent less than three segments
Action: Re-define the coordinates for the polygon
Cause: The coordinates defining a polygonal geometric element represents an open polygon
Action: Re-define the coordinates of the polygon
Cause: The <layer>_SDOINFO table contains an invalid geometric element type
Action: Re-define the geometric element type in the <layer>_SDOINFO table
Cause: The <layer>_SDOINFO table does not contain the specified GID
Action: Verify that the correct layer name and GID were specified
Cause: The Spatial Data Option INFO table contains a geometric object (GID) which has no elements defined in the Spatial Data Option GEOMETRY table.
Action: Add elements for the geometric object to the Spatial Data Option GEOMETRY table.
Cause: The Spatial Data Option GEOMETRY table contains a geometric object (GID) which has no geometry information defined in the Spatial Data Option INFO table.
Action: Add geometry information for the geomtric object to the Spatial Data Option INFO table or drop and re-create the geometric object.
Cause: This is an internal error.
Action: Contact World Wide Support.
Cause: This is an undocumented error.
Action: Please refer to the user documentation for an explanation of this error.
Cause: This is an undocumented error.
Action: Please refer to the user documentation for an explanation of this error.
Cause: This is an undocumented error.
Action: Please refer to the user documentation for an explanation of this error.
Cause: This is an undocumented error.
Action: Please refer to the user documentation for an explanation of this error.
Cause: The specified spatial table does not exist.
Action: Check the Spatial Data option data dictionary to make sure that the table is registered.
Cause: The specified spatial table is registered in the Spatial Data data dictionary.
Action: Remove the existing table from the Spatial Data option data dictionary or use a different name.
Cause: The specified spatial table is not partitioned.
Action: Check the Spatial Data option data dictionary and make sure that a high water mark is set.
Cause: The specified spatial table does not have a partition key defined.
Action: Check the Spatial Data option data dictionary and make sure that the table is partitioned.
Cause: The specified count mode is not valid.
Action: Alter the count mode. Valid count modes are ESTIMATE or EXACT.
Cause: The specified Oracle table does not exist.
Action: Check the Oracle7 data dictionary and make sure that the table exists.
Cause: The specified tablespace does not exist.
Action: Check the Oracle7 data dictionary and make sure that the specified tablespace exists and that there is a space quota defined on it.
Cause: The specified tablespace is already allocated to the spatial table.
Action: Allocate another tablespace name to the table.
Cause: The specified tablespace is not allocated to the specified spatial table.
Action: Allocate the tablespace to the spatial table.
Cause: The specified partition does not exist.
Action: Verify the name of the partition by checking the Spatial Data option data dictionary.
Cause: Identical source and target tablespaces were specified when trying to move partition.
Action: Specify different source and target tablespaces if you wish to move a partition.
Cause: The creation of a child partition failed.
Action: Check for other errors that accompany this error and correct them first.
Cause: This is an internal error.
Action: Document messages and contact Oracle Worldwide Support.
Cause: The specified column is already defined for the spatial table.
Action: Use a different column name.
Cause: This is an internal error.
Action: Document messages and contact Oracle Worldwide Support.
Cause: A partition key is already set for the spatial table.
Action: Only one partition key can be specified per spatial table.
Cause: This is an internal error.
Action: Document messages and contact Oracle Worldwide Support.
Cause: This is an internal error.
Action: Document messages and contact Oracle Worldwide Support.
Cause: The dimension definitions could not be found for the specified column.
Action: Make sure that the specified column is a spatial column.
Cause: The specified spatial column does not exist.
Action: Verify that the specified column is a spatial column by checking the Spatial Data option data dictionary.
Cause: This is an internal error.
Action: Document messages and contact Oracle Worldwide Support.
Cause: This is an internal error.
Action: Document messages and contact Oracle Worldwide Support.
Cause: This is an internal error.
Action: Document messages and contact Oracle Worldwide Support.
Cause: This is an internal error.
Action: Document messages and contact Oracle Worldwide Support.
Cause: This is an internal error.
Action: Document messages and contact Oracle Worldwide Support.
Cause: The specified target type is not valid.
Action: Substitute a valid target type. Valid target types are TABLE or VIEW.
Cause: The RANGE window specified is not correctly defined.
Action: A RANGE window is defined by specifying the lower and upper boundary of each dimension as a pair of values (e.g.: lower_bound1,upper_bound1,lower_bound2,upper_bound2,...). There should be an even number of values.
Cause: The PROXIMITY window specified is not correctly defined.
Action: A PROXIMITY window is defined by specifying a center point and a radius. The center point is defined by ND values. There should be ND+1 values.
Cause: The POLYGON window specified is not correctly defined.
Action: A POLYGON window is defined by specifying N pairs of values that represent the vertices of the polygon. There should be an even number of values.
Cause: This is an internal error.
Action: Document messages and contact Oracle Worldwide Support.
Cause: This is an internal error.
Action: Document messages and contact Oracle Worldwide Support.
Cause: The partition name substitution variable name was not found in the SQL filter.
Action: The substitution variable name must be in the SQL filter to indicate where that partition name should be placed.
Cause: This is an internal error.
Action: Document messages and contact Oracle Worldwide Support.
Cause: This is an internal error.
Action: Document messages and contact Oracle Worldwide Support.
Cause: This is an internal error.
Action: Document messages and contact Oracle Worldwide Support.
Cause: Operation failed to insert a record into the exception table
Action: Fix any other errors reported.
Cause: Operation failed to insert a record into the exception table.
Action: Fix any other errors reported.
Cause: Specified HHCODE type is not valid.
Action: Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE.
Cause: The highwater mark must be greater than or equal to zero.
Action: Make sure that the highwater mark is an integer greater than or equal to zero.
Cause: The precision specified is out of range.
Action: The precision must be an integer greater than or equal to zero.
Cause: The number of dimensions specified is out of range.
Action: The number of dimension must be between 1 and 32.
Cause: The specified table has rows in it.
Action: Make sure that the table to be registered is empty.
Cause: Specified Oracle error was encountered.
Action: Correct the Oracle error.
Cause: The specified object does not exist.
Action: Verify that the specified object exists.
Cause: The specified table already exists.
Action: Drop the specified table.
Cause: This is an internal error.
Action: Contact World Wide Support.
Cause: SDO was unable to determine the geometry type for the specified geometry.
Action: Verify that the information in the <layer>_SDOINFO table exists and is valid.
Cause: The geometry type in the <layer>_SDOINFO table is unsupported.
Action: Modify the geometry type to be one of the supported types.
Cause: This is an internal error.
Action: Contact World Wide Support.
Cause: This is an internal error.
Action: Contact World Wide Support.
Cause: This is an internal error.
Action: Contact World Wide Support.
Cause: This is an internal error.
Action: Contact World Wide Support.
Cause: This is an internal error.
Action: Contact World Wide Support.
Cause: This is an internal error.
Action: Contact World Wide Support.
Cause: The geometry type in the <layer>_SDOINFO table is unsupported.
Action: Modify the geometry type to be one of the supported types.
Cause: This is an internal error.
Action: Contact World Wide Support.
Cause: SDO was unable to compute a supercell for the specified geometry.
Action: Verify the geometry. Note any additional messages and report the problem to World Wide Support.
Cause: This is an internal error.
Action: Contact World Wide Support.
Cause: This is an internal error.
Action: Contact World Wide Support.
Cause: This is an internal error.
Action: Contact World Wide Support.
Cause: This is an internal error.
Action: Contact World Wide Support.
Cause: This is an internal error.
Action: Contact World Wide Support.
|
 Copyright © 1997 Oracle Corporation. All Rights Reserved. |
|
