Oracle7 Server Messages
13000-13199: Spatial Data Option
ORA-13000 dimension number is out of range
| Cause: | The specified dimension is either smaller than one 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. | |
For more information about the Spatial Data option, see
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13001 dimensions mismatch error
| 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. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13002 specified level is out of range
| 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. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13003 the specified range for a dimension is invalid
| Cause: | The specified range for a dimension is invalid. | |
| Action: | Make sure that the lower bound (lb) is less than the upper bound (ub). | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13004 the specified buffer size is invalid
| Cause: | The buffer size for a function is not valid. | |
| Action: | This is an internal error. Contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13005 recursive HHCODE function error
| Cause: | An error occurred in a recursively called HHCODE function. | |
| Action: | This is an internal error. Contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13006 the specified cell number is invalid
| 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). | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13007 an invalid HEX character was detected
| 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]. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13008 the specified date format has an invalid component
| Cause: | Part of specified date format is invalid. | |
| Action: | Verify that the date format is valid. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13009 the specified date string is invalid
| 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. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13010 an invalid number of arguments has been specified
| Cause: | An invalid number of arguments was specified for an HHCODE function. | |
| Action: | Verify the syntax of the function call. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13011 value is out of range
| Cause: | A specified 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. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13012 an invalid window type was specified
| Cause: | An invalid window type was specified. | |
| Action: | Valid window types are RANGE, PROXIMITY, POLYGON. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13013 the specified topology was not INTERIOR or BOUNDARY
| 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. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13014 a topology identifier outside the range of 1 to 8 was specified
| Cause: | A topology identifier outside the range of 1 to 8 was specified | |
| Action: | Specify a topology in the range of 1 to 8. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13015 the window definition is not valid
| 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. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13016 bad partition definition
| Cause: | The partition common code was not correctly decoded. | |
| Action: | This is an internal error. Contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13017 unrecognized line partition shape
| Cause: | The shape of a 2-D line partition could not be determined. | |
| Action: | This is an internal error. Contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13018 bad distance type
| Cause: | The specified distance type is invalid. | |
| Action: | The only supported distance functions are EUCLID and MANHATTAN. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13100 badly formed request frame
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13101 partition name datatype should be varchar2
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13102 reply pipe name datatype should be varchar2
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13103 failed to acknowledge on pipe name due to timeout
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13104 failed to send reply on pipe name due to timeout
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13105 buffer overflow encountered on pipe name
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13106 acknowledgment on pipe name interrupted
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13107 reply on pipe name interrupted
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13108 spatial table name not found
| Cause: | The specified spatial table does not exist. | |
| Action: | Check the Spatial Data option data dictionary to make sure that the table exists. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13109 spatial table name exists
| Cause: | The specified spatial table exists. | |
| Action: | Drop the existing table or use a different name. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13110 spatial table name is not partitioned
| 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. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13111 spatial table name has no partition key defined
| 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. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13112 invalid count mode name
| Cause: | The specified count mode is not valid. | |
| Action: | Alter the count mode. Valid count modes are ESTIMATE or EXACT. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13113 Oracle table name does not exists
| Cause: | The specified Oracle table does not exist. | |
| Action: | Check the Oracle7 data dictionary and make sure that the table exists. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13114 tablespace name not found
| Cause: | The specified tablespace does not exist. | |
| Action: | Check the Spatial Data option data dictionary and make sure that the specified tablespace exists and that there is a space quota defined on it. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13115 tablespace name is already allocated
| Cause: | The specified tablespace is already allocated to the spatial table. | |
| Action: | Allocate another tablespace name to the table. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13116 tablespace name is not allocated to table name
| Cause: | The specified tablespace is not allocated to the specified spatial table. | |
| Action: | Allocate the tablespace to the spatial table. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13117 partition name not found
| Cause: | The specified partition does not exist. | |
| Action: | Verify the name of the partition by checking the Spatial Data option data dictionary. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13118 partition name is offline
| Cause: | The specified partition is offline. | |
| Action: | Bring the partition online and then retry the operation. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13119 source and target tablespaces are identical
| 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. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13120 SD*POD is not listening on pipe name
| Cause: | There is no partition operation daemon listening on the specified pipe. | |
| Action: | Start a daemon listening on the pipe by using the LISTEN command line option of SD*POD. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13121 failed to create child partition
| Cause: | The creation of a child partition failed. | |
| Action: | Check for other errors that accompany this error and correct them first. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13122 child partition name not found
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13123 column name is already defined
| Cause: | The specified column is already defined for the spatial table. | |
| Action: | Use a different column name. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13124 unable to determine column id for column name
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13125 partition key is already set
| Cause: | A partition key is already set for the spatial table. | |
| Action: | Only one partition key can be specified per spatial table. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13126 unable to determine class for spatial table name
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13127 failed to generate target partition
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13128 failed to identify dimensions for column name
| Cause: | The dimension definitions could not be found for the specified column. | |
| Action: | Make sure that the specified column is a spatial column. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13129 HHCODE column name not found
| 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. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13130 timed out waiting for reply on name
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13131 record in pipe name is too big
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13132 pipe read on name was interrupted
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13133 archive request failed
| Cause: | The request to archive a partition failed. | |
| Action: | Check the log file and correct any errors indicated. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13134 restore request failed
| Cause: | The request to restore a partition failed. | |
| Action: | Check the log file and correct any errors indicated. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13135 duplicate offline path
| Cause: | The offline path specified is already being used by another spatial table. | |
| Action: | Use a different offline path. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13136 null common code generated
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13138 could not determine name of object name
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13139 could not obtain column definition for name
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13140 invalid target type
| Cause: | The specified target type is not valid. | |
| Action: | Substitute a valid target type. Valid target types are TABLE or VIEW. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13141 invalid RANGE window definition
| 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. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13142 invalid PROXIMITY window definition
| 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. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13143 invalid POLYGON window definition
| 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. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13144 target table name not found
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13145 failed to generate range list
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13146 could not find table substitution variable name
| 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. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13147 failed to generate MBR
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13148 failed to generate SQL filter
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13149 failed to generate next sequence number for spatial table name
| Cause: | This is an internal error. | |
| Action: | Document messages and contact Oracle Worldwide Support. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13150 failed to insert exception record
| Cause: | Operation failed to insert a record into the exception table | |
| Action: | Fix any other errors reported. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13152 invalid HHCODE type
| Cause: | Specified HHCODE type is not valid. | |
| Action: | Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13197 only MDSYS can execute name
| Cause: | You tried to execute a restricted procedure. | |
| Action: | Only MDSYS can execute the specified partition. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.
ORA-13198 Oracle error ORAname encountered
| Cause: | Specified Oracle error was encountered. | |
| Action: | Correct the Oracle error. | |
For more information about the Spatial Data option, see Oracle7 Spatial Data Option Reference and Administrator's Guide.