back
Oracle® Database 11g / 12c / 18c error codes ORA-12700-ORA-19400
- ORA-12700: invalid NLS parameter value ([string])
- ORA-12701: CREATE DATABASE character set is not known
- ORA-12702: invalid NLS parameter [string] used in SQL function
- ORA-12703: this character set conversion is not supported
- ORA-12704: character set mismatch
- ORA-12705: Cannot access NLS data files or invalid environment specified
- ORA-12706: this CREATE DATABASE character set is not allowed
- ORA-12707: error while getting create database NLS parameter [string]
- ORA-12708: error while loading create database NLS parameter [string]
- ORA-12709: error while loading create database character set
- ORA-12710: CREATE CONTROLFILE character set is not known
- ORA-12711: this CREATE CONTROLFILE character set is not allowed
- ORA-12712: new character set must be a superset of old character set
- ORA-12713: Character data loss in NCHAR/CHAR conversion
- ORA-12714: invalid national character set specified
- ORA-12715: invalid character set specified
- ORA-12716: Cannot ALTER DATABASE CHARACTER SET when CLOB data exists
- ORA-12717: Cannot issue ALTER DATABASE NATIONAL CHARACTER SET when NCLOB, NCHAR or NVARCHAR2 data exists
- ORA-12718: operation requires connection as SYS
- ORA-12719: operation requires database is in RESTRICTED mode
- ORA-12720: operation requires database is in EXCLUSIVE mode
- ORA-12721: operation cannot execute when other sessions are active
- ORA-12722: regular expression internal error
- ORA-12723: regular expression too complex
- ORA-12724: regular expression corrupt
- ORA-12725: unmatched parentheses in regular expression
- ORA-12726: unmatched bracket in regular expression
- ORA-12727: invalid back reference in regular expression
- ORA-12728: invalid range in regular expression
- ORA-12729: invalid character class in regular expression
- ORA-12730: invalid equivalence class in regular expression
- ORA-12731: invalid collation class in regular expression
- ORA-12732: invalid interval value in regular expression
- ORA-12733: regular expression too long
- ORA-12734: Instant Client Light: unsupported client national character set [string]
- ORA-12735: Instant Client Light: unsupported client character set [string]
- ORA-12736: Instant Client Light: unsupported server national character set [string]
- ORA-12737: Instant Client Light: unsupported server character set [string]
- ORA-12738: Express Instant Client: unsupported client national character set [string]
- ORA-12739: Express Instant Client: unsupported client character set [string]
- ORA-12740: Express Instant Client: unsupported server national character set [string]
- ORA-12741: Express Instant Client: unsupported server character set [string]
- ORA-12800: system appears too busy for parallel query execution
- ORA-12801: error signaled in parallel query server [string]
- ORA-12802: parallel query server lost contact with coordinator
- ORA-12803: parallel query server lost contact with another server
- ORA-12804: parallel query server appears to have died
- ORA-12805: parallel query server died unexpectedly
- ORA-12806: could not get background process to hold enqueue
- ORA-12807: process queue could not receive parallel query message
- ORA-12808: cannot set [string]_INSTANCES greater than number of instances [string]
- ORA-12809: cannot set [string]_INSTANCES when mounted in exclusive mode
- ORA-12810: PARALLEL_MAX_SERVERS must be less than or equal to [string]
- ORA-12811: PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, [string]
- ORA-12812: only one PARALLEL or NOPARALLEL clause may be specified
- ORA-12813: value for PARALLEL or DEGREE must be greater than 0
- ORA-12814: only one CACHE or NOCACHE clause may be specified
- ORA-12815: value for INSTANCES must be greater than 0
- ORA-12817: parallel query option must be enabled
- ORA-12818: invalid option in PARALLEL clause
- ORA-12819: missing options in PARALLEL clause
- ORA-12820: invalid value for DEGREE
- ORA-12821: invalid value for INSTANCES
- ORA-12822: duplicate option in PARALLEL clause
- ORA-12823: default degree of parallelism may not be specified here
- ORA-12824: INSTANCES DEFAULT may not be specified here
- ORA-12825: explicit degree of parallelism must be specified here
- ORA-12826: hung parallel query server was killed
- ORA-12827: insufficient parallel query slaves available
- ORA-12828: Can''t start parallel transaction at a remote site
- ORA-12829: Deadlock - itls occupied by siblings at block [string] of file [string]
- ORA-12830: Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE
- ORA-12831: Must COMMIT or ROLLBACK after executing INSERT with APPEND hint
- ORA-12832: Could not allocate slaves on all specified instances
- ORA-12833: Coordinator''s instance not a member of parallel_instance_group
- ORA-12834: Instance group name, '[string]', too long, must be less than string characters
- ORA-12835: No instances are active in the GLOBAL_VIEW_ADMIN_GROUP
- ORA-12838: cannot read/modify an object after modifying it in parallel
- ORA-12839: cannot modify an object in parallel after modifying it
- ORA-12840: cannot access a remote table after parallel/insert direct load txn
- ORA-12841: Cannot alter the session parallel DML state within a transaction
- ORA-12842: Cursor invalidated during parallel execution
- ORA-12843: pdml lock not held properly on the table
- ORA-12844: cluster reconfiguration in progress
- ORA-12845: failed to receive interinstance parallel execution message
- ORA-12850: Could not allocate slaves on all specified instances: [string] needed, [string] allocated
- ORA-12851: PARALLEL_MAX_SERVERS must be greater than or equal to PARALLEL_MIN_SERVERS, [string]
- ORA-12852: PARALLEL_MIN_SERVERS must be less than PROCESSES, [string]
- ORA-12853: insufficient memory for PX buffers: current [string]K, max needed [string]K
- ORA-12854: Parallel query is not supported on temporary LOBs
- ORA-12855: cannot run parallel or insert direct load in a loopback
- ORA-12856: cannot run parallel query on a loopback connection
- ORA-12872: First slave parse gave different plan
- ORA-12899: value too large for column [string] (actual: [string], maximum: [string])
- ORA-12900: must specify a default temporary tablespace for a locally managed database
- ORA-12901: default temporary tablespace must be of TEMPORARY type
- ORA-12902: default temporary tablespace must be SYSTEM or of TEMPORARY type
- ORA-12910: cannot specify temporary tablespace as default tablespace
- ORA-12911: permanent tablespace cannot be temporary tablespace
- ORA-12912: Dictionary managed tablespace specified as temporary tablespace
- ORA-12913: Cannot create dictionary managed tablespace
- ORA-12914: Cannot migrate tablespace to dictionary managed type
- ORA-12915: Cannot alter dictionary managed tablespace to read write
- ORA-12916: cannot shrink permanent or dictionary managed tablespace
- ORA-12918: Invalid tablespace type for default permanent tablespace
- ORA-12919: Can not drop the default permanent tablespace
- ORA-12920: database is already in force logging mode
- ORA-12921: database is not in force logging mode
- ORA-12922: concurrent ALTER DATABASE [NO] FORCE LOGGING command is running
- ORA-12923: tablespace [string] is in force logging mode
- ORA-12924: tablespace [string] is already in force logging mode
- ORA-12925: tablespace [string] is not in force logging mode
- ORA-12926: FORCE LOGGING option already specified
- ORA-12927: RETENTION option already specified
- ORA-12928: ENCRYPTION option already specified
- ORA-12940: Not enough space in DBVerify text buffer
- ORA-12941: DBVerify exception
- ORA-12950: SYSTEM tablespace specified as default permanent tablespace
- ORA-12951: Attempt to change default permanent tablespace to temporary
- ORA-12980: checkpoint option not allowed with SET UNUSED
- ORA-12981: cannot drop column from an object type table
- ORA-12982: cannot drop column from a nested table
- ORA-12983: cannot drop all columns in a table
- ORA-12984: cannot drop partitioning column
- ORA-12985: tablespace '[string]' is read only, cannot drop column
- ORA-12986: columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE
- ORA-12987: cannot combine drop column with other operations
- ORA-12988: cannot drop column from table owned by SYS
- ORA-12989: invalid value for checkpoint interval
- ORA-12990: duplicate option specified
- ORA-12991: column is referenced in a multi-column constraint
- ORA-12992: cannot drop parent key column
- ORA-12993: tablespace '[string]' is offline, cannot drop column
- ORA-12994: drop column option only allowed once in statement
- ORA-12995: no columns in partially dropped state
- ORA-12996: cannot drop system-generated virtual column
- ORA-12997: cannot drop primary key column from an index-organized table
- ORA-13000: dimension number is out of range
- ORA-13001: dimensions mismatch error
- ORA-13002: specified level is out of range
- ORA-13003: the specified range for a dimension is invalid
- ORA-13004: the specified buffer size is invalid
- ORA-13005: recursive HHCODE function error
- ORA-13006: the specified cell number is invalid
- ORA-13007: an invalid HEX character was detected
- ORA-13008: the specified date format has an invalid component
- ORA-13009: the specified date [string] is invalid
- ORA-13010: an invalid number of arguments has been specified
- ORA-13011: value is out of range
- ORA-13012: an invalid window type was specified
- ORA-13013: the specified topology was not INTERIOR or BOUNDARY
- ORA-13014: a topology identifier outside the range of 1 to 8 was specified
- ORA-13015: the window definition is not valid
- ORA-13016: specified topology [string] is invalid
- ORA-13017: unrecognized line partition shape
- ORA-13018: bad distance type
- ORA-13019: coordinates out of bounds
- ORA-13020: coordinate is NULL
- ORA-13021: element not continuous
- ORA-13022: polygon crosses itself
- ORA-13023: interior element interacts with exterior element
- ORA-13024: polygon has less than three segments
- ORA-13025: polygon does not close
- ORA-13026: unknown element type for element [string].[string].[string]
- ORA-13027: unable to read dimension definition from [string]
- ORA-13028: Invalid Gtype in the SDO_GEOMETRY object
- ORA-13029: Invalid SRID in the SDO_GEOMETRY object
- ORA-13030: Invalid dimension for the SDO_GEOMETRY object
- ORA-13031: Invalid Gtype in the SDO_GEOMETRY object for point object
- ORA-13032: Invalid NULL SDO_GEOMETRY object
- ORA-13033: Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
- ORA-13034: Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object
- ORA-13035: Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object
- ORA-13036: Operation [string] not supported for Point Data
- ORA-13037: SRIDs do not match for the two geometries
- ORA-13039: failed to update spatial index for element [string].[string].[string]
- ORA-13040: failed to subdivide tile
- ORA-13041: failed to compare tile with element [string].[string].[string]
- ORA-13042: invalid SDO_LEVEL and SDO_NUMTILES combination
- ORA-13043: failed to read metadata from the _SDOLAYER table
- ORA-13044: the specified tile size is smaller than the tolerance
- ORA-13045: invalid compatibility flag
- ORA-13046: invalid number of arguments
- ORA-13047: unable to determine ordinate count from table _SDOLAYER
- ORA-13048: recursive SQL fetch error
- ORA-13049: unable to determine tolerance value from table _SDODIM
- ORA-13050: unable to construct spatial object
- ORA-13051: failed to initialize spatial object
- ORA-13052: unsupported geometric type for geometry [string].[string]
- ORA-13053: maximum number of geometric elements in argument list exceeded
- ORA-13054: recursive SQL parse error
- ORA-13055: Oracle object [string] does not exist in specified table
- ORA-13060: topology with the name [string] already exists
- ORA-13061: topology with the name [string] does not exist
- ORA-13062: topology IDs do not match in the feature table and the topology
- ORA-13063: relationship information table is missing data for feature table [string]
- ORA-13064: relationship information table has inconsistent data for feature table [string]
- ORA-13065: cannot delete a child layer with a parent layer
- ORA-13066: wrong feature geometry or element type
- ORA-13067: operator requires both parameters from the same topology
- ORA-13068: wrong table or column name in SDO_TOPO_GEOMETRY constructor
- ORA-13108: spatial table [string] not found
- ORA-13109: spatial table [string] exists
- ORA-13110: cannot drop topology with associated topo_geometry tables
- ORA-13111: cannot add topo_geometry layer [string] to topology
- ORA-13112: cannot delete topo_geometry layer [string] from topology
- ORA-13113: invalid tg_layer_id in sdo_topo_geometry constructor
- ORA-13114: [string]_NODE$ table does not exist
- ORA-13115: [string]_EDGE$ table does not exist
- ORA-13116: [string]_FACE$ table does not exist
- ORA-13117: [string]_RELATION$ table does not exist
- ORA-13118: invalid node_id [string]
- ORA-13119: invalid edge_id [string]
- ORA-13120: invalid face_id [string]
- ORA-13121: layer type type mismatch with topo_geometry layer type
- ORA-13122: invalid topo_geometry specified
- ORA-13123: invalid name specified
- ORA-13124: unable to determine column id for column [string]
- ORA-13125: partition key is already set
- ORA-13126: unable to determine class for spatial table [string]
- ORA-13127: failed to generate target partition
- ORA-13128: current tiling level exceeds user specified tiling level
- ORA-13129: HHCODE column [string] not found
- ORA-13135: failed to alter spatial table
- ORA-13136: null common code generated
- ORA-13137: failed to generate tablespace sequence number
- ORA-13138: could not determine name of object [string]
- ORA-13139: could not obtain column definition for [string]
- ORA-13140: invalid target type
- ORA-13141: invalid RANGE window definition
- ORA-13142: invalid PROXIMITY window definition
- ORA-13143: invalid POLYGON window definition
- ORA-13144: target table [string] not found
- ORA-13145: failed to generate range list
- ORA-13146: could not find table substitution variable [string]
- ORA-13147: failed to generate MBR
- ORA-13148: failed to generate SQL filter
- ORA-13149: failed to generate next sequence number for spatial table [string]
- ORA-13150: failed to insert exception record
- ORA-13151: failed to remove exception record
- ORA-13152: invalid HHCODE type
- ORA-13153: invalid high water mark specified
- ORA-13154: invalid precision specified
- ORA-13155: invalid number of dimensions specified
- ORA-13156: table to be registered [string].[string] is not empty
- ORA-13157: Oracle error ORA[string] encountered while [string]
- ORA-13158: Oracle object [string] does not exist
- ORA-13159: Oracle table [string] already exists
- ORA-13181: unable to determine length of column [string]_SDOINDEX.SDO_CODE
- ORA-13182: failed to read element [string].[string].[string]
- ORA-13183: unsupported geometric type for geometry [string].[string]
- ORA-13184: failed to initialize tessellation package
- ORA-13185: failed to generate initial HHCODE
- ORA-13186: fixed tile size tessellation failed
- ORA-13187: subdivision failed
- ORA-13188: cell decode failed
- ORA-13189: recursive SQL parse failed
- ORA-13190: recursive SQL fetch failed
- ORA-13191: failed to read SDO_ORDCNT value
- ORA-13192: failed to read number of element rows
- ORA-13193: failed to allocate space for geometry
- ORA-13194: failed to decode supercell
- ORA-13195: failed to generate maximum tile value
- ORA-13196: failed to compute supercell for element [string].[string].[string]
- ORA-13197: element [string].[string].[string] is out of range
- ORA-13198: Spatial error: [string]
- ORA-13199: [string]
- ORA-13200: internal error [string] in spatial indexing.
- ORA-13201: invalid parameters supplied in CREATE INDEX statement
- ORA-13202: failed to create or insert into the SDO_INDEX_METADATA table
- ORA-13203: failed to read USER_SDO_GEOM_METADATA view
- ORA-13204: failed to create spatial index table
- ORA-13205: internal error while parsing spatial parameters
- ORA-13206: internal error [string] while creating the spatial index
- ORA-13207: incorrect use of the [string] operator
- ORA-13208: internal error while evaluating [string] operator
- ORA-13209: internal error while reading SDO_INDEX_METADATA table
- ORA-13210: error inserting data into the index table
- ORA-13211: failed to tessellate the window object
- ORA-13212: failed to compare tile with the window object
- ORA-13213: failed to generate spatial index for window object
- ORA-13214: failed to compute supercell for window object
- ORA-13215: window object is out of range
- ORA-13216: failed to update spatial index
- ORA-13217: invalid parameters supplied in ALTER INDEX statement
- ORA-13218: max number of supported index tables reached for [string] index
- ORA-13219: failed to create spatial index table [string]
- ORA-13220: failed to compare tile with the geometry
- ORA-13221: unknown geometry type in the geometry object
- ORA-13222: failed to compute supercell for geometry in [string]
- ORA-13223: duplicate entry for [string] in SDO_GEOM_METADATA
- ORA-13224: zero tolerance specified for layer in USER_SDO_GEOM_METADATA
- ORA-13225: specified index table name is too long for a spatial index
- ORA-13226: interface not supported without a spatial index
- ORA-13227: SDO_LEVEL values for the two index tables do not match
- ORA-13228: spatial index create failed due to invalid type
- ORA-13230: failed to create temporary table [string] during R-tree creation
- ORA-13231: failed to create index table [string] during R-tree creation
- ORA-13232: failed to allocate memory during R-tree creation
- ORA-13233: failed to create sequence number [string] for R-tree
- ORA-13234: failed to access R-tree-index table [string]
- ORA-13236: internal error in R-tree processing: [string]
- ORA-13237: internal error during R-tree concurrent updates: [string]
- ORA-13239: sdo_dimensionality not specified during n-d R-tree creation
- ORA-13240: specified dimensionality greater than that of the query mbr
- ORA-13241: specified dimensionality does not match that of the data
- ORA-13243: specified operator is not supported for 3- or higher-dimensional R-tree
- ORA-13249: [string]
- ORA-13250: insufficient privileges to modify metadata table entries
- ORA-13251: duplicate entry [string] in metadata table
- ORA-13260: layer table [string] does not exist
- ORA-13261: geometry table [string] does not exist
- ORA-13262: geometry column [string] does not exist in table [string]
- ORA-13263: column [string] in table [string] is not of type SDO_GEOMETRY
- ORA-13264: geometry identifier column [string] does not exist in table [string]
- ORA-13265: geometry identifier column [string] in table [string] is not of type NUMBER
- ORA-13266: error inserting data into table [string]
- ORA-13267: error reading data from layer table [string]
- ORA-13268: error obtaining dimension from USER_SDO_GEOM_METADATA
- ORA-13269: internal error [string] encountered when processing geometry table
- ORA-13270: OCI error [string]
- ORA-13271: error allocating memory for geometry object
- ORA-13272: geometric object [string] in table [string] is invalid
- ORA-13273: dimension metadata table [string] does not exist
- ORA-13274: operator invoked with non-compatible SRIDs
- ORA-13275: spatial index creation failure on unsupported type
- ORA-13276: internal error [string] in coordinate transformation
- ORA-13278: failure to convert SRID to native format
- ORA-13281: failure in execution of SQL statement to retrieve WKT
- ORA-13282: failure on initialization of coordinate transformation
- ORA-13283: failure to get new geometry object for conversion in place
- ORA-13284: failure to copy geometry object for conversion in place
- ORA-13285: Geometry coordinate transformation error
- ORA-13287: can''t transform unknown gtype
- ORA-13288: point coordinate transformation error
- ORA-13290: the specified unit is not supported
- ORA-13291: conversion error between the specified unit and standard unit
- ORA-13292: incorrect ARC_TOLERANCE specification
- ORA-13293: cannot specify unit for geometry without a georeferenced SRID
- ORA-13294: cannot transform geometry containing circular arcs
- ORA-13295: geometry objects are in different coordinate systems
- ORA-13296: incorrect coordinate system specification
- ORA-13300: single point transform error
- ORA-13303: failure to retrieve a geometry object from a table
- ORA-13304: failure to insert a transformed geometry object in a table
- ORA-13330: invalid MASK
- ORA-13331: invalid LRS segment
- ORA-13332: invalid LRS point
- ORA-13333: invalid LRS measure
- ORA-13334: LRS segments not connected
- ORA-13335: LRS measure information not defined
- ORA-13336: failure in converting standard diminfo/geometry to LRS dim/geom
- ORA-13337: failure in concatenating LRS polygons
- ORA-13338: failure in reversing LRS polygon/collection geometry
- ORA-13339: LRS polygon clipping across multiple rings
- ORA-13340: a point geometry has more than one coordinate
- ORA-13341: a line geometry has fewer than two coordinates
- ORA-13342: an arc geometry has fewer than three coordinates
- ORA-13343: a polygon geometry has fewer than four coordinates
- ORA-13344: an arcpolygon geometry has fewer than five coordinates
- ORA-13345: a compound polygon geometry has fewer than five coordinates
- ORA-13346: the coordinates defining an arc are collinear
- ORA-13347: the coordinates defining an arc are not distinct
- ORA-13348: polygon boundary is not closed
- ORA-13349: polygon boundary crosses itself
- ORA-13350: two or more rings of a complex polygon touch
- ORA-13351: two or more rings of a complex polygon overlap
- ORA-13352: the coordinates do not describe a circle
- ORA-13353: ELEM_INFO_ARRAY not grouped in threes
- ORA-13354: incorrect offset in ELEM_INFO_ARRAY
- ORA-13355: SDO_ORDINATE_ARRAY not grouped by number of dimensions specified
- ORA-13356: adjacent points in a geometry are redundant
- ORA-13357: extent type does not contain 2 points
- ORA-13358: circle type does not contain 3 points
- ORA-13359: extent does not have an area
- ORA-13360: invalid subtype in a compound type
- ORA-13361: not enough sub-elements within a compound ETYPE
- ORA-13362: disjoint sub-element in a compound polygon
- ORA-13363: no valid ETYPE in the geometry
- ORA-13364: layer dimensionality does not match geometry dimensions
- ORA-13365: layer SRID does not match geometry SRID
- ORA-13366: invalid combination of interior exterior rings
- ORA-13367: wrong orientation for interior/exterior rings
- ORA-13368: simple polygon type has more than one exterior ring
- ORA-13369: invalid value for etype in the 4-digit format
- ORA-13370: failure in applying 3D LRS functions
- ORA-13371: invalid position of measure dimension
- ORA-13372: failure in modifying metadata for a table with spatial index
- ORA-13373: invalid line segment in geodetic data
- ORA-13374: SDO_MBR not supported for geodetic data
- ORA-13375: the layer is of type [string] while geometry inserted has type [string]
- ORA-13376: invalid type name specified for layer_gtype parameter
- ORA-13377: invalid combination of elements with orientation
- ORA-13378: invalid index for element to be extracted
- ORA-13379: invalid index for sub-element to be extracted
- ORA-13380: network not found
- ORA-13381: table:[string] not found in network:[string]
- ORA-13382: geometry metadata (table:[string] column:[string]) not found in spatial network:[string]
- ORA-13383: inconsistent network metadata: [string]
- ORA-13384: error in network schema: [string]
- ORA-13385: error in network manager: [string]
- ORA-13386: commit/rollback operation error: [string]
- ORA-13387: sdo_batch_size for array inserts should be in the range [number,number]
- ORA-13388: invalid value for dst_spec parameter
- ORA-13389: unable to compute buffers or intersections in analysis function
- ORA-13390: error in spatial analysis and mining function: [string]
- ORA-13391: [string]
- ORA-13400: duplicate entry for [string] in USER_SDO_GEOR_SYSDATA view
- ORA-13401: duplicate entry for [string] in USER_SDO_GEOR_SYSDATA view
- ORA-13402: the rasterType is null or not supported
- ORA-13403: invalid rasterDataTable specification: [string]
- ORA-13404: invalid ultCoordinate parameter
- ORA-13405: null or invalid dimensionSize parameter
- ORA-13406: null or invalid GeoRaster object for output
- ORA-13407: invalid storage parameter[string]
- ORA-13408: invalid blockSize storage parameter
- ORA-13409: null or invalid pyramidLevel parameter
- ORA-13410: invalid layerNumbers or bandNumbers parameter
- ORA-13411: subset results in null data set
- ORA-13412: invalid scale parameter[string]
- ORA-13413: null or invalid resampling parameter
- ORA-13414: invalid pyramid parameter
- ORA-13415: invalid or out of scope point specification
- ORA-13416: invalid geometry parameter
- ORA-13417: null or invalid layerNumber parameter
- ORA-13418: null or invalid parameter(s) for set functions
- ORA-13419: cannot perform mosaick operation on the specified table column
- ORA-13420: the SRID of the geometry parameter was not null
- ORA-13421: NULL or invalid cell value
- ORA-13422: invalid model coordinate parameter
- ORA-13423: invalid cell coordinate parameter
- ORA-13424: the GeoRaster object is not spatially referenced
- ORA-13425: invalid background filling value parameter
- ORA-13426: invalid window parameter
- ORA-13427: invalid bitmap mask
- ORA-13428: invalid modelCoordinateLocation
- ORA-13429: invalid xCoefficients or yCoefficients parameter(s)
- ORA-13430: the GeoRaster object has null attribute(s)
- ORA-13431: GeoRaster metadata rasterType error
- ORA-13432: NULL or invalid blankCellValue
- ORA-13433: GeoRaster metadata default RGB error
- ORA-13434: GeoRaster metadata cellRepresentation error
- ORA-13435: GeoRaster metadata dimension inconsistent
- ORA-13436: GeoRaster metadata dimensionSize error
- ORA-13437: GeoRaster metadata blocking error
- ORA-13438: GeoRaster metadata pyramid type error
- ORA-13439: GeoRaster metadata pyramid maxLevel error
- ORA-13440: GeoRaster metadata compression type error
- ORA-13441: GeoRaster metadata SRS error: [string]
- ORA-13442: GeoRaster object not registered: [string]
- ORA-13443: null or invalid values in [string]
- ORA-13444: cannot perform mergeLayers operation
- ORA-13445: NULL or invalid NODATA value or value range
- ORA-13446: GeoRaster metadata TRS error
- ORA-13447: GeoRaster metadata BRS error
- ORA-13448: GeoRaster metadata BRS error
- ORA-13449: GeoRaster metadata ULTCoordinate error
- ORA-13450: GeoRaster metadata layerInfo error
- ORA-13451: GeoRaster metadata scaling function error
- ORA-13452: GeoRaster metadata BIN function error
- ORA-13453: GeoRaster metadata layer error
- ORA-13454: GeoRaster metadata is invalid
- ORA-13455: GeoRaster metadata TRS error
- ORA-13456: GeoRaster cell data error: [string]
- ORA-13457: bitmap mask cell data error: [string]
- ORA-13458: GeoRaster metadata SRS error
- ORA-13459: GeoRaster metadata SRS error
- ORA-13460: GeoRaster metadata SRS error
- ORA-13461: the interleaving type is not supported
- ORA-13462: invalid blocking specification
- ORA-13463: error retrieving GeoRaster data: [string]
- ORA-13464: error loading GeoRaster data: [string]
- ORA-13465: null or invalid table or column specification
- ORA-13466: format not appropriate for specified compression method: [string]
- ORA-13467: unsupported GeoRaster metadata specification: [string]
- ORA-13468: invalid blockMBR
- ORA-13469: cannot perform updateRaster operation
- ORA-13470: target and source layers or bands mismatched
- ORA-13471: unable to determine the owner of [string]
- ORA-13472: invalid geometry parameter
- ORA-13473: invalid rasterSpec parameter
- ORA-13474: invalid rasterDataTable name: [string]
- ORA-13475: invalid GeoRaster object for output
- ORA-13476: invalid or out of scope point specification
- ORA-13480: the Source Type is not supported
- ORA-13481: the destination type is not supported
- ORA-13482: GeoRaster object is not initialized for the image
- ORA-13483: insufficient memory for the specified GeoRaster data
- ORA-13484: the file format or compression type is not supported: [string]
- ORA-13485: error occurred during compression or decompression: [string]
- ORA-13486: invalid or insufficient GeoTIFF metadata to georeference the GeoRaster object: [string]
- ORA-13487: SRID not found for source coordinate system metadata
- ORA-13497: [string]
- ORA-13498: [string]
- ORA-13499: [string]
- ORA-13500: SYSAUX DATAFILE clause specified more than once
- ORA-13501: Cannot drop SYSAUX tablespace
- ORA-13502: Cannot rename SYSAUX tablespace
- ORA-13503: Creating SYSAUX tablespace with invalid attributes
- ORA-13504: No SYSAUX datafile clause specified
- ORA-13505: SYSAUX tablespace can not be made read only
- ORA-13506: operation failed due to invalid snapshot range ([string], [string])
- ORA-13509: error encountered during updates to a AWR table
- ORA-13510: invalid RETENTION [string], must be in the range ([string], [string])
- ORA-13511: invalid INTERVAL [string], must be in the range ([string], [string])
- ORA-13514: Metric Capture too close to last capture, group [string]
- ORA-13515: Error encountered during Database Usage Statistics capture
- ORA-13516: AWR Operation failed: [string]
- ORA-13517: Baseline (id = [string]) does not exist
- ORA-13518: Invalid database id ([string])
- ORA-13519: Database id ([string]) exists in the workload repository
- ORA-13520: Database id ([string]) not registered, Status = [string]
- ORA-13521: Unregister operation on local Database id ([string]) not allowed
- ORA-13523: unable to allocate required space for return type
- ORA-13524: error encountered while retrieving baseline information
- ORA-13525: error with computing space usage for sysaux occupant
- ORA-13526: baseline ([string]) does not exist
- ORA-13527: invalid baseline name
- ORA-13528: name ([string]) is already used by an existing baseline
- ORA-13529: Error occurred when flushing AWR table group
- ORA-13530: invalid TOPNSQL [string], must be in the range ([string], [string])
- ORA-13531: SQL Text was purged from AWR before the operation completed
- ORA-13532: SQL ID [string] already exists
- ORA-13533: invalid SQL ID
- ORA-13534: Current SQL count([string]) reached maximum allowed ([string])
- ORA-13535: name ([string]) is already used by an existing baseline template
- ORA-13536: baseline template ([string]) does not exist
- ORA-13537: invalid input for create baseline template ([string], [string])
- ORA-13538: invalid value for baseline expiration ([string])
- ORA-13539: invalid input for modify baseline window size ([string], [string])
- ORA-13540: operation not allowed on system moving window baseline ([string])
- ORA-13541: system moving window baseline size ([string]) greater than retention ([string])
- ORA-13542: baseline ID ([string]) does not exist
- ORA-13543: error encountered while retrieving baseline template information
- ORA-13544: error encountered while automatically generating a baseline
- ORA-13545: invalid baseline template name
- ORA-13546: Error encountered during maintenance of Adaptive Thresholds
- ORA-13547: Unable to drop baseline since it is in use by [string]
- ORA-13548: Unable to find valid snapshot IDs for the inputted baseline time range
- ORA-13549: invalid input for create baseline with time range ([string])
- ORA-13600: error encountered in Advisor [string]
- ORA-13601: The specified Advisor [string] does not exist.
- ORA-13602: The specified parameter [string] is not valid for task or object [string].
- ORA-13603: The specified parameter [string] cannot be fetched as a numeric value for task or object [string].
- ORA-13604: The specified parameter [string] cannot be fetched as a SQL table.
- ORA-13605: The specified task or object [string] does not exist for the current user.
- ORA-13606: the specified task parameter element [string] is out of range for parameter [string].
- ORA-13607: The specified task or object [string] already exists
- ORA-13608: The specified name [string] is invalid.
- ORA-13609: The specified task [string] must be executing to be cancelled or interrupted.
- ORA-13610: The directive [string] does not exist for task [string].
- ORA-13611: The command [string] is not a valid advisor command.
- ORA-13612: The recommendation action [string],[string] is not valid for task [string].
- ORA-13613: The requested operation is not supported for this advisor object.
- ORA-13614: The template [string] is not compatible with the current advisor.
- ORA-13615: The task or object [string] is greater than the maximum allowable length of 30 characters.
- ORA-13616: The current user [string] has not been granted the ADVISOR privilege.
- ORA-13617: The specified task [string] already executing
- ORA-13618: The specified value is not a valid value for procedure argument [string].
- ORA-13619: The procedure argument [string] is greater than the maximum allowable length of [string] characters.
- ORA-13620: The task or object [string] is read-only and cannot be deleted or modified.
- ORA-13621: The task_or object [string] is marked as a template and cannot perform the requested operation.
- ORA-13622: invalid recommendation annotation
- ORA-13623: The recommendation [string] is not valid for task [string].
- ORA-13624: The task [string] is executing and cannot be deleted or modified.
- ORA-13625: [string] is an invalid advisor object type.
- ORA-13626: The specified object [string] is not valid for task [string].
- ORA-13627: Setting of parameter [string] is disallowed until the task is reset.
- ORA-13628: Insufficient privileges to access the task belonging to the specified user
- ORA-13629: The task or object [string] is being used by another operation.
- ORA-13630: The task [string] contains execution results and cannot be executed.
- ORA-13631: The most recent execution of task [string] contains no results.
- ORA-13632: The user cancelled the current operation.
- ORA-13633: The task [string] was interrupted and needs to be resumed.
- ORA-13634: The task [string] needs to be reset before being re-executed.
- ORA-13635: The value provided for parameter [string] cannot be converted to a number.
- ORA-13636: The specified value provided for parameter [string] is not valid for this advisor.
- ORA-13637: Executing or modifying task [string] is disallowed until the task is reset to its initial state.
- ORA-13638: The user interrupted the current operation.
- ORA-13639: The current operation was interrupted because it timed out.
- ORA-13640: The current operation was cancelled because it timed out, and was not in interruptible mode.
- ORA-13641: Task cannot be interrupted yet. You may cancel it instead.
- ORA-13642: The specified [string] [string] provided for [string] cannot be converted to a date. The acceptable date format is [string].
- ORA-13643: The task can not be interrupted or cancelled.
- ORA-13644: The user "[string]" is invalid.
- ORA-13645: The specified execution [string] does not exist for this task.
- ORA-13646: The specified execution [string] already exists
- ORA-13647: Setting of parameter [string] is disallowed during task execution.
- ORA-13648: The specified execution type does not exist for this advisor.
- ORA-13649: The type of execution is not specified for this advisor or task.
- ORA-13650: The specified object does not exist for this execution.
- ORA-13651: The specified list of execution parameters is invalid.
- ORA-13652: Cannot set execution parameters for this advisor
- ORA-13653: The directive with definition id [string] was not found.
- ORA-13654: The directive with instance id of [string] was not found.
- ORA-13655: The directive document contains a syntax error and cannot be loaded.
- ORA-13656: The parameter was not found in directive [string].
- ORA-13657: The filter Xpath specification has invalid syntax.
- ORA-13658: The specified directive already has an instance
- ORA-13659: A directive with domain "[string]" and name "[string]" already exists for advisor [string].
- ORA-13660: A directive instance with the name "[string]" already exists.
- ORA-13661: A directive instance with the name "[string]" was not found.
- ORA-13662: The specified value provided for parameter [string] is not valid for this task.
- ORA-13663: The task [string] contains no results for execution [string].
- ORA-13664: A task-managed "SQL Tuning Set" already exists for task "[string]".
- ORA-13665: Execution names are not correctly ordered.
- ORA-13666: Task ID [string] does not exist.
- ORA-13667: Execution ID [string] does not exist.
- ORA-13668: The current operation was aborted because it was blocking another session.
- ORA-13699: Advisor feature is not currently implemented.
- ORA-13701: Snapshot pair [[string], [string]] seems to be specified in reverse order.
- ORA-13702: Snapshot IDs specified by the range [[string], [string]] are equal.
- ORA-13703: The snapshot pair [[string], [string]] for database_id [string] and instance_id [string] are not found in the current repository.
- ORA-13704: Invalid value "[string]" specified for parameter "[string]".
- ORA-13705: There was a instance shutdown/startup between the snapshots in the range [[string], [string]].
- ORA-13706: Invalid value "[string]" specified for parameter "[string]" in "[string]" analysis mode.
- ORA-13707: Either the start snapshot [string] or the end snapshot [string] is incomplete or missing key statistics.
- ORA-13708: Some snapshots in the range [[string], [string]] were purged before the analysis was complete.
- ORA-13709: Required parameter "[string]" must be set before execution.
- ORA-13710: Parameter "[string]" must have a higher value than parameter "[string]". The values supplied were "[string]" and "[string]" respectively.
- ORA-13711: Some snapshots in the range [[string], [string]] are missing key statistics.
- ORA-13712: Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "[string]" do not match the database version "[string]".
- ORA-13713: Finding name "[string]" does not exist. Look in DBA_ADVISOR_FINDING_NAMES for all valid values
- ORA-13714: "[string]" is not a valid SQL_ID value
- ORA-13715: "[string]" is not recognized by ADDM as a parameter name
- ORA-13716: Diagnostic Package License is needed for using this feature.
- ORA-13717: Tuning Package License is needed for using this feature.
- ORA-13718: Tuning Package License or Real Application Testing Option is needed for using this feature.
- ORA-13750: User "[string]" has not been granted the "ADMINISTER SQL TUNING SET" privilege.
- ORA-13751: "SQL Tuning Set" "[string]" does not exist for owner "[string]" or user "[string]" does not have permission to access the "SQL Tuning Set".
- ORA-13752: User "[string]" must be SYS or must have the "ADMINISTER ANY SQL TUNING SET" privilege.
- ORA-13753: "SQL Tuning Set" "[string]" already exists for user "[string]".
- ORA-13754: "SQL Tuning Set" "[string]" does not exist for user "[string]".
- ORA-13755: invalid "SQL Tuning Set" name
- ORA-13756: Cannot update attribute "[string]".
- ORA-13757: "SQL Tuning Set" "[string]" owned by user "[string]" is active.
- ORA-13758: "SQL Tuning Set" "[string]" owned by user "[string]" is in use.
- ORA-13759: User "[string]" cannot remove reference "[string]".
- ORA-13761: invalid filter
- ORA-13762: The [string] ranking measure is invalid.
- ORA-13763: illegal ranking attribute "[string]"
- ORA-13764: Value "[string]" is illegal as a result percentage.
- ORA-13765: Value "[string]" is illegal for a result limit.
- ORA-13766: A ranking measure is required.
- ORA-13767: End snapshot ID must be greater than begin snapshot ID.
- ORA-13768: Snapshot ID must be between [string] and [string].
- ORA-13769: Snapshots [string] and [string] do not exist.
- ORA-13770: Baseline "[string]" does not exist.
- ORA-13771: cannot obtain exclusive lock [string] on "SQL Tuning Set" "[string]" owned by user "[string]"
- ORA-13772: unexpected deadlock on "SQL Tuning Set" "[string]" owned by user "[string]"
- ORA-13773: insufficient privileges to select data from the cursor cache
- ORA-13774: insufficient privileges to select data from the workload repository
- ORA-13775: inconsistent datatype in input cursor
- ORA-13776: User "[string]" has not been granted the "SELECT" privilege on the "SQL tuning set" DBA views.
- ORA-13777: invalid list of attribute names
- ORA-13778: no new name or owner specified for "SQL Tuning Set"
- ORA-13779: invalid load option
- ORA-13780: SQL statement does not exist.
- ORA-13781: cannot perform test-execute and explain plan operations on the automatic SQL tuning task
- ORA-13783: invalid tuning scope
- ORA-13784: cannot accept SQL profiles for all statements in the "[string]"
- ORA-13785: missing target object for tuning task "[string]"
- ORA-13786: missing SQL text of statement object "[string]" for tuning task "[string]"
- ORA-13787: missing SQL profile for statement object "[string]" for tuning task "[string]"
- ORA-13788: invalid recommendation type
- ORA-13789: invalid process action
- ORA-13790: invalid value for time limit
- ORA-13791: cannot resume a task created to process a single statement
- ORA-13793: invalid comparison metric
- ORA-13794: execution type mismatch
- ORA-13795: missing task execution
- ORA-13796: invalid value [string] specified for problem type
- ORA-13797: invalid SQL Id specified, [string]
- ORA-13798: Parameter [string] cannot be NULL.
- ORA-13799: threshold not found
- ORA-13800: concurrent DDL failure on SQL repository objects
- ORA-13801: invalid value for SQLTUNE_CATEGORY parameter
- ORA-13802: failed to purge SQL Tuning Base entry from sql$
- ORA-13825: missing SQL statement text for create SQL profile
- ORA-13826: empty SQL profile not allowed for create or update SQL profile
- ORA-13827: null or zero length attribute specified in SQL profile collection
- ORA-13828: generated SQL profile name [string] already exists
- ORA-13829: SQL profile named [string] already exists
- ORA-13830: SQL profile with category [string] already exists for this SQL statement
- ORA-13831: SQL profile name specified is invalid
- ORA-13832: category name specified is invalid
- ORA-13833: SQL profile named [string] doesn''t exist
- ORA-13834: name of SQL profile to be cloned must be provided
- ORA-13835: invalid attribute name specified
- ORA-13836: invalid attribute value specified
- ORA-13837: invalid HASH_VALUE
- ORA-13838: invalid ADDRESS value
- ORA-13839: V$SQL row doesn''t exist with given HASH_VALUE and ADDRESS.
- ORA-13840: Concurrent DDL Error in create SQL profile operation.
- ORA-13841: SQL profile named [string] already exists for a different signature/category pair
- ORA-13842: no SELECT privilege on DBA_SQL_PROFILES
- ORA-13843: no SQL profile with name like "[string]" exists for category like "[string]"
- ORA-13844: no new SQL profile name or category specified.
- ORA-13845: invalid SQL profile XML specification provided
- ORA-13850: Tracing for client identifier [string] is not enabled
- ORA-13851: Tracing for client identifier [string] is already enabled
- ORA-13852: Tracing for service(module/action) [string] is not enabled
- ORA-13853: Tracing for service (module/action) [string] is already enabled
- ORA-13854: Tracing for service(module/action) [string] on instance [string] is not enabled
- ORA-13855: Tracing for service (module/action) [string] on instance [string] is already enabled
- ORA-13856: Service name must be specified
- ORA-13857: Invalid module name
- ORA-13858: Invalid action name
- ORA-13859: Action cannot be specified without the module specification
- ORA-13860: Invalid service name
- ORA-13861: Statistics aggregation for client identifier [string] is already enabled
- ORA-13862: Statistics aggregation for client identifier [string] is not enabled
- ORA-13863: Statistics aggregation for service(module/action) [string] is not enabled
- ORA-13864: Statistics aggregation for service (module/action) [string] is already enabled
- ORA-13865: Module name must be specified
- ORA-13866: Client identifier must be specified
- ORA-13867: Database-wide SQL tracing is already enabled
- ORA-13868: Instance-wide SQL tracing on instance [string] is not enabled
- ORA-13869: Instance-wide SQL tracing on instance [string] is already enabled
- ORA-13870: Database-wide SQL tracing is not enabled
- ORA-13871: Invalid instance name
- ORA-13900: missing or invalid parameter [string]
- ORA-13901: Object [string] was not found.
- ORA-13902: The specified file [string] is not a data file.
- ORA-13903: Invalid combination of [string] threshold value and operator.
- ORA-13904: The file has been dropped and recreated during the procedure call.
- ORA-13905: Critical or warning threshold have incorrect values
- ORA-13906: The tablepace is not of the right type.
- ORA-13907: Threshold value is invalid.
- ORA-13908: Invalid combination of metrics id and object type parameters.
- ORA-13909: Invalid combination of threshold value and operator.
- ORA-13910: Parameter [string] cannot be NULL.
- ORA-13911: Threshold not found
- ORA-13912: Critical threshold value is less than warning threshold value.
- ORA-13913: The threshold cannot be set when SYSAUX is offline.
- ORA-13914: Threshold notification failed.
- ORA-13915: Critical byte based free space threshold value is greater than warning threshold value.
- ORA-13916: Invalid value "[string]" specified for parameter "[string]"
- ORA-13917: Posting system alert with reason_id string failed with code [string] [string]
- ORA-13918: Updating system alert with reason_id [string] failed; previous alert not found
- ORA-13919: Cannot specify values for parameter "[string]" and for parameter "[string]"
- ORA-13920: Threshold cannot be set when database is in read-only mode.
- ORA-13951: MMON sub-action time limit exceeded
- ORA-13970: Invalid name of "[string]" given
- ORA-13971: [string] "[string]" unknown
- ORA-13972: [string] "[string]" unknown for [string] "[string]"
- ORA-13973: [string] unknown for [string] "[string]"
- ORA-13974: [string] with name "[string]" already exists
- ORA-13975: [string] with name "[string]" already exists for [string] "[string]"
- ORA-13976: Improperly-formed report tag
- ORA-13977: Invalid content type
- ORA-13978: Invalid reference [string] parameter or value
- ORA-13979: Filename too long
- ORA-13980: Invalid file URL
- ORA-13981: Invalid file URL or path prefix
- ORA-13982: Could not find file at URL provided
- ORA-13983: Missing tag from HTML
- ORA-13984: Invalid reference [string]
- ORA-13985: Invalid URL provided to servlet
- ORA-13986: Error \[string] received from XPath engine
- ORA-13987: Invalid input to build common <[string]> tag
- ORA-13988: Invalid input given to variable argument list report function.
- ORA-13989: Invalid input given to structured argument list report function.
- ORA-13990: Invalid tag name given to common tag callout function.
- ORA-14000: only one LOCAL clause may be specified
- ORA-14001: LOCAL clause contradicts previosly specified GLOBAL clause
- ORA-14002: only one GLOBAL clause may be specified
- ORA-14003: GLOBAL clause contradicts previosly specified LOCAL clause
- ORA-14004: missing PARTITION keyword
- ORA-14005: missing RANGE keyword
- ORA-14006: invalid partition name
- ORA-14007: missing LESS keyword
- ORA-14008: missing THAN keyword
- ORA-14009: partition bound may not be specified for a LOCAL index partition
- ORA-14010: this physical attribute may not be specified for an index partition
- ORA-14011: names assigned to resulting partitions must be distinct
- ORA-14012: resulting partition name conflicts with that of an existing partition
- ORA-14013: duplicate partition name
- ORA-14014: maximum number of partitioning columns is 16
- ORA-14015: too many partition descriptions
- ORA-14016: underlying table of a LOCAL partitioned index must be partitioned
- ORA-14017: partition bound list contains too many elements
- ORA-14018: partition bound list contains too few elements
- ORA-14019: partition bound element must be one of: [string], datetime or interval literal, number, or MAXVALUE
- ORA-14020: this physical attribute may not be specified for a table partition
- ORA-14021: MAXVALUE must be specified for all columns
- ORA-14022: creation of LOCAL partitioned cluster indices is not supported
- ORA-14023: creation of GLOBAL partitioned cluster indices is not supported
- ORA-14024: number of partitions of LOCAL index must equal that of the underlying table
- ORA-14025: PARTITION may not be specified for a materialized view or a materialized view log
- ORA-14026: PARTITION and CLUSTER clauses are mutually exclusive
- ORA-14027: only one PARTITION clause may be specified
- ORA-14028: missing AT or VALUES keyword
- ORA-14029: GLOBAL partitioned index must be prefixed
- ORA-14030: non-existent partitioning column in CREATE TABLE statement
- ORA-14031: partitioning column may not be of type LONG or LONG RAW
- ORA-14032: partition bound of partition number [string] is too high
- ORA-14036: partition bound value too large for column
- ORA-14037: partition bound of partition "[string]" is too high
- ORA-14038: GLOBAL partitioned index must be prefixed
- ORA-14039: partitioning columns must form a subset of key columns of a UNIQUE index
- ORA-14041: partition bound may not be specified for resulting partitions
- ORA-14042: partition bound may not be specified for a partition being moved, modified or rebuilt
- ORA-14043: only one partition may be added
- ORA-14044: only one partition may be moved
- ORA-14045: only one partition may be modified
- ORA-14046: a partition may be split into exactly two new partitions
- ORA-14047: ALTER TABLE|INDEX RENAME may not be combined with other operations
- ORA-14048: a partition maintenance operation may not be combined with other operations
- ORA-14049: invalid ALTER TABLE MODIFY PARTITION option
- ORA-14050: invalid ALTER INDEX MODIFY PARTITION option
- ORA-14051: invalid ALTER MATERIALIZED VIEW option
- ORA-14052: partition-extended table name syntax is disallowed in this context
- ORA-14053: illegal attempt to modify [string] in [string] statement
- ORA-14054: invalid ALTER TABLE TRUNCATE PARTITION option
- ORA-14055: keyword REBUILD in ALTER INDEX REBUILD must immediately follow
- ORA-14056: partition number [string]: sum of PCTUSED and PCTFREE may not exceed 100
- ORA-14057: partition "[string]": sum of PCTUSED and PCTFREE may not exceed 100
- ORA-14058: partition number [string]: INITRANS value must be less than MAXTRANS value
- ORA-14059: partition "[string]": INITRANS value must be less than MAXTRANS value
- ORA-14060: data type or length of a table partitioning column may not be changed
- ORA-14061: data type or length of an index partitioning column may not be changed
- ORA-14062: one or more of table''s partitions reside in a read-only tablespace
- ORA-14063: Unusable index exists on unique/primary constraint key
- ORA-14064: Index with Unusable partition exists on unique/primary constraint key
- ORA-14065: ALLOCATE STORAGE may not be specified for a partitioned table
- ORA-14066: illegal option for a non-partitioned index-organized table
- ORA-14067: duplicate TABLESPACE_NUMBER specification
- ORA-14068: TABLESPACE and TABLESPACE_NUMBER may not be both specified
- ORA-14069: invalid TABLESPACE_NUMBER value
- ORA-14070: option may be specified only for partitioned indices or with REBUILD
- ORA-14071: invalid option for an index used to enforce a constraint
- ORA-14072: fixed table may not be truncated
- ORA-14073: bootstrap table or cluster may not be truncated
- ORA-14074: partition bound must collate higher than that of the last partition
- ORA-14075: partition maintenance operations may only be performed on partitioned indices
- ORA-14076: submitted alter index partition/subpartition operation is not valid for local partitioned index
- ORA-14078: you may not drop the highest partition of a GLOBAL index
- ORA-14079: illegal option for a partition marked Index Unusable
- ORA-14080: partition cannot be split along the specified high bound
- ORA-14081: new partition name must differ from the old partition name
- ORA-14082: new partition name must differ from that of any other partition of the object
- ORA-14083: cannot drop the only partition of a partitioned table
- ORA-14084: you may specify TABLESPACE DEFAULT only for a LOCAL index
- ORA-14085: partitioned table cannot have column with LONG datatype
- ORA-14086: a partitioned index may not be rebuilt as a whole
- ORA-14094: invalid ALTER TABLE EXCHANGE PARTITION option
- ORA-14095: ALTER TABLE EXCHANGE requires a non-partitioned, non-clustered table
- ORA-14096: tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns
- ORA-14097: column type or size mismatch in ALTER TABLE EXCHANGE PARTITION
- ORA-14098: index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
- ORA-14099: all rows in table do not qualify for specified partition
- ORA-14100: partition extended table name cannot refer to a remote object
- ORA-14101: partition extended table name cannot refer to a synonym
- ORA-14102: only one LOGGING or NOLOGGING clause may be specified
- ORA-14103: LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE
- ORA-14104: RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices
- ORA-14105: RECOVERABLE/UNRECOVERABLE may not be specified in this context
- ORA-14106: LOGGING/NOLOGGING may not be specified for a clustered table
- ORA-14107: partition specification is required for a partitioned object
- ORA-14108: illegal partition-extended table name syntax
- ORA-14109: partition-extended object names may only be used with tables
- ORA-14110: partitioning column may not be of type ROWID
- ORA-14111: creation of a GLOBAL partitioned index on clustered tables is not supported
- ORA-14112: RECOVERABLE/UNRECOVERABLE may not be specified for a partition or subpartition
- ORA-14113: partitioned table cannot have column with LOB datatype
- ORA-14114: partitioned table cannot have column with object, REF, nested table, array datatype
- ORA-14115: partition bound of partition number [string] is too long
- ORA-14116: partition bound of partition "[string]" is too long
- ORA-14117: partition resides in offlined tablespace
- ORA-14118: CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION
- ORA-14119: specified partition bound is too long
- ORA-14120: incompletely specified partition bound for a DATE column
- ORA-14121: MODIFY DEFAULT ATTRIBUTES may not be combined with other operations
- ORA-14122: only one REVERSE or NOREVERSE clause may be specified
- ORA-14123: duplicate NOREVERSE clause
- ORA-14124: duplicate REVERSE clause
- ORA-14125: REVERSE/NOREVERSE may not be specified in this context
- ORA-14126: only a may follow description(s) of resulting partitions
- ORA-14128: FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION
- ORA-14129: INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
- ORA-14130: UNIQUE constraints mismatch in ALTER TABLE EXCHANGE PARTITION
- ORA-14131: enabled UNIQUE constraint exists on one of the tables
- ORA-14132: table cannot be used in EXCHANGE
- ORA-14133: ALTER TABLE MOVE cannot be combined with other operations
- ORA-14134: indexes cannot use both DESC and REVERSE
- ORA-14135: a LOB column cannot serve as a partitioning column
- ORA-14136: ALTER TABLE EXCHANGE restricted by fine-grained security
- ORA-14137: Table in partially dropped state, submit DROP TABLE PURGE
- ORA-14138: An unexpected error encountered during drop table operation
- ORA-14139: table [string].[string] is already in read-only mode
- ORA-14140: table [string].[string] is already in read/write mode
- ORA-14141: ALTER INDEX VISIBLE|INVISIBLE may not be combined with other operations
- ORA-14142: ALTER INDEX VISIBLE|INVISIBLE may not be used with certain types of index
- ORA-14143: CREATE INDEX INVISIBLE may not be used with this type of index
- ORA-14150: missing SUBPARTITION keyword
- ORA-14151: invalid table partitioning method
- ORA-14152: invalid number of partitions specified in PARTITIONS clause
- ORA-14153: only one of STORE IN or clause may be specified
- ORA-14154: only one of STORE IN or clause may be specified
- ORA-14155: missing PARTITION or SUBPARTITION keyword
- ORA-14156: invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause
- ORA-14157: invalid subpartition name
- ORA-14158: too many subpartition descriptions
- ORA-14159: duplicate subpartition name
- ORA-14160: this physical attribute may not be specified for a table subpartition
- ORA-14161: subpartition number [string]: sum of PCTUSED and PCTFREE may not exceed 100
- ORA-14162: subpartition "[string]": sum of PCTUSED and PCTFREE may not exceed 100
- ORA-14163: subpartition number [string]: INITRANS value must be less than MAXTRANS value
- ORA-14164: subpartition "[string]": INITRANS value must be less than MAXTRANS value
- ORA-14165: MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations
- ORA-14166: missing INTO keyword
- ORA-14167: only one subpartition may be moved
- ORA-14168: only one subpartition may be modified
- ORA-14169: invalid ALTER TABLE MODIFY SUBPARTITION option
- ORA-14170: cannot specify clause in CREATE TABLE|INDEX
- ORA-14171: cannot specify clause in CREATE|ALTER TABLE
- ORA-14172: invalid ALTER TABLE EXCHANGE SUBPARTITION option
- ORA-14173: illegal subpartition-extended table name syntax
- ORA-14174: only a may follow COALESCE PARTITION|SUBPARTITION
- ORA-14175: a subpartition maintenance operation may not be combined with other operations
- ORA-14176: this attribute may not be specified for a hash partition
- ORA-14177: STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table
- ORA-14178: STORE IN (DEFAULT) clause is not supported for hash partitioned global indexes
- ORA-14183: TABLESPACE DEFAULT can be specified only for Composite LOCAL index
- ORA-14185: incorrect physical attribute specified for this index partition
- ORA-14186: number of sub-partitions of LOCAL index must equal that of the underlying table
- ORA-14187: partitioning method for LOCAL index is inconsistent with that of the underlying table
- ORA-14188: sub-partitioning columns must form a subset of key columns of a UNIQUE index
- ORA-14189: this physical attribute may not be specified for an index subpartition
- ORA-14190: only one ENABLE/DISABLE ROW MOVEMENT clause can be specified
- ORA-14191: ALLOCATE STORAGE may not be specified for Composite Range partitioned object
- ORA-14192: cannot modify physical index attributes of a Hash index partition
- ORA-14193: invalid ALTER INDEX MODIFY SUBPARTITION option
- ORA-14194: only one subpartition may be rebuilt
- ORA-14195: ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object
- ORA-14196: Specified index cannot be used to enforce the constraint.
- ORA-14201: specified subpartition bound is too long
- ORA-14202: subpartition bound of subpartition "[string]" is too high
- ORA-14203: subpartition bound of subpartition "[string]" is too long
- ORA-14204: subpartition bound of subpartition number [string] is too high
- ORA-14205: subpartition bound of subpartition number [string] is too long
- ORA-14206: table is not subpartitioned by List or Range methods
- ORA-14207: maximum number of subpartitioning columns is 16
- ORA-14208: lower-bound subpartition must be specified first
- ORA-14209: subpartitions being merged are not adjacent
- ORA-14210: cannot reuse lower-bound subpartition as resulting subpartition
- ORA-14211: subpartition bound must collate higher than that of the last subpartition
- ORA-14212: subpartition cannot be split along the specified high bound
- ORA-14213: VALUES LESS THAN or AT clause cannot be used for List subpartitioned tables
- ORA-14214: VALUES () cannot be used for Range subpartitioned tables
- ORA-14215: subpartition bound list contains too many elements
- ORA-14216: subpartition bound list contains too few elements
- ORA-14217: VALUES () clause expected
- ORA-14251: Specified subpartition does not exist
- ORA-14252: invalid ALTER TABLE MODIFY PARTITION option for a Hash partition
- ORA-14253: table is not partitioned by Composite Range method
- ORA-14254: cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table
- ORA-14255: table is not partitioned by Range, List, Composite Range or Composite List method
- ORA-14256: invalid resulting partition description(s)
- ORA-14257: cannot move partition other than a Range, List, System, or Hash partition
- ORA-14258: invalid partition description
- ORA-14259: table is not partitioned by Hash method
- ORA-14260: incorrect physical attribute specified for this partition
- ORA-14261: partition bound may not be specified when adding this Hash partition
- ORA-14262: new subpartition name must differ from the old subpartition name
- ORA-14263: new subpartition name must differ from that of any other subpartition of the object
- ORA-14264: table is not partitioned by Composite Range method
- ORA-14265: data type or length of a table subpartitioning column may not be changed
- ORA-14266: data type or length of an index subpartitioning column may not be changed
- ORA-14267: cannot specify PARALLEL clause when adding a (Composite) Range partition
- ORA-14268: subpartition '[string]' of the partition resides in offlined tablespace
- ORA-14269: cannot exchange partition other than a Range,List,System, or Hash partition
- ORA-14270: table is not partitioned by Range, System, Hash or List method
- ORA-14271: table is not partitioned by Composite Range method
- ORA-14272: only a partition with higher bound can be reused
- ORA-14273: lower-bound partition must be specified first
- ORA-14274: partitions being merged are not adjacent
- ORA-14275: cannot reuse lower-bound partition as resulting partition
- ORA-14276: EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table
- ORA-14277: tables in EXCHANGE SUBPARTITION must have the same number of columns
- ORA-14278: column type or size mismatch in EXCHANGE SUBPARTITION
- ORA-14279: index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION
- ORA-14280: all rows in table do not qualify for specified subpartition
- ORA-14281: CHECK constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION
- ORA-14282: FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION
- ORA-14283: UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION
- ORA-14284: one or more of table''s subpartitions reside in a read-only tablespace
- ORA-14285: cannot COALESCE the only partition of this hash partitioned table or index
- ORA-14286: cannot COALESCE the only subpartition of this table partition
- ORA-14287: cannot REBUILD a partition of a Composite Range partitioned index
- ORA-14288: index is not partitioned by Composite Range method
- ORA-14289: cannot make local index partition of Composite Range partitioned table unusable
- ORA-14290: PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
- ORA-14291: cannot EXCHANGE a composite partition with a non-partitioned table
- ORA-14292: Partitioning type of table must match subpartitioning type of composite partition
- ORA-14293: Number of partitioning columns does not match number of subpartitioning columns
- ORA-14294: Number of partitions does not match number of subpartitions
- ORA-14295: column type or size mismatch between partitioning columns and subpartitioning columns
- ORA-14296: Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
- ORA-14297: Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
- ORA-14298: LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
- ORA-14299: total number of partitions/subpartitions exceeds the maximum limit
- ORA-14301: table-level attributes must be specified before partition-level attributes
- ORA-14302: only one list of added-LOB-storage-clauses can be specified in a statement
- ORA-14303: partitions or subpartitions are not in the right order
- ORA-14304: List partitioning method expects a single partitioning column
- ORA-14305: List value '[string]' specified twice in partition '[string]'
- ORA-14306: List value '[string]' specified twice in partitions '[string]', '[string]'
- ORA-14307: partition contains too many list values
- ORA-14308: partition bound element must be one of: [string], datetime or interval literal, number, or NULL
- ORA-14309: Total count of list values exceeds maximum allowed
- ORA-14310: VALUES LESS THAN or AT clause cannot be used with List partitioned tables
- ORA-14311: Expecting VALUES LESS THAN or AT clause
- ORA-14312: Value [string] already exists in partition [string]
- ORA-14313: Value [string] does not exist in partition [string]
- ORA-14314: resulting List partition(s) must contain atleast 1 value
- ORA-14315: cannot merge a partition with itself
- ORA-14316: table is not partitioned by List method
- ORA-14317: cannot drop the last value of partition
- ORA-14318: DEFAULT partition must be last partition specified
- ORA-14319: DEFAULT cannot be specified with other values
- ORA-14320: DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT
- ORA-14321: cannot add/drop values to DEFAULT partition
- ORA-14322: DEFAULT partition already exists
- ORA-14323: cannot add partition when DEFAULT partition exists
- ORA-14324: values being added already exist in DEFAULT partition
- ORA-14325: only LOCAL indexes may be specified in this clause
- ORA-14326: Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause
- ORA-14327: Some index [sub]partitions could not be rebuilt
- ORA-14329: domain index [sub]partitions cannot be renamed in this clause
- ORA-14330: Cannot drop a partition of a global hash-partitioned index
- ORA-14400: inserted partition key does not map to any partition
- ORA-14401: inserted partition key is outside specified partition
- ORA-14402: updating partition key column would cause a partition change
- ORA-14403: cursor invalidation detected after getting DML partition lock
- ORA-14404: partitioned table contains partitions in a different tablespace
- ORA-14405: partitioned index contains partitions in a different tablespace
- ORA-14406: updated partition key is beyond highest legal partition key
- ORA-14407: partitioned table contains subpartitions in a different tablespace
- ORA-14408: partitioned index contains subpartitions in a different tablespace
- ORA-14409: inserted partition key is outside specified subpartition
- ORA-14411: The DDL cannot be run concurrently with other DDLs
- ORA-14450: attempt to access a transactional temp table already in use
- ORA-14451: unsupported feature with temporary table
- ORA-14452: attempt to create, alter or drop an index on temporary table already in use
- ORA-14453: attempt to use a LOB of a temporary table, whose data has alreadybeen purged
- ORA-14454: attempt to reference temporary table in a referential integrity constraint
- ORA-14455: attempt to create referential integrity constraint on temporary table
- ORA-14456: cannot rebuild index on a temporary table
- ORA-14457: disallowed Nested Table column in a Temporary table
- ORA-14458: attempt was made to create a temporary table with INDEX organization
- ORA-14459: missing GLOBAL keyword
- ORA-14460: only one COMPRESS or NOCOMPRESS clause may be specified
- ORA-14461: cannot REUSE STORAGE on a temporary table TRUNCATE
- ORA-14462: cannot TRUNCATE temporary table in an autonomous transaction which is already in use by the parent transaction
- ORA-14463: OPERATIONS keyword not specified
- ORA-14464: Compression Type not specified
- ORA-14500: LOCAL option not valid without partition name
- ORA-14501: object is not partitioned
- ORA-14503: only one partition name can be specified
- ORA-14504: syntax not supported for analyze
- ORA-14505: LOCAL option valid only for partitioned indexes
- ORA-14506: LOCAL option required for partitioned indexes
- ORA-14507: partition corrupt. all rows do not fall within partition bounds
- ORA-14508: specified VALIDATE INTO table not found
- ORA-14509: specified VALIDATE INTO table form incorrect
- ORA-14510: can specify VALIDATE INTO clause only for partitioned tables
- ORA-14511: cannot perform operation on a partitioned object
- ORA-14512: cannot perform operation on a clustered object
- ORA-14513: partitioning column may not be of object datatype
- ORA-14514: LOCAL option not valid without subpartition name
- ORA-14515: only one aubpartition name can be specified
- ORA-14516: subpartition corrupt. all rows do not fall within subpartition bounds
- ORA-14517: subpartition of index ''[string].[string]'' is in unusable state
- ORA-14518: partition contains rows corresponding to values being dropped
- ORA-14519: Conflicting tablespace blocksizes for string string: Tablespace string block size string [string] conflicts with previously specified/implied tablespace string block size string [string]
- ORA-14520: Tablespace string block size [string] does not match existing object block size [string]
- ORA-14521: Default tablespace string block size [string] for string string does not match existing string block size [string]
- ORA-14522: Partition-level default tablespace string block size [string] for string string does not match existing string block size [string]
- ORA-14523: Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]
- ORA-14530: row mismatches found in table [string].[string] and index [string].[string]
- ORA-14551: cannot perform a DML operation inside a query
- ORA-14552: cannot perform a DDL, commit or rollback inside a query or DML
- ORA-14553: cannot perform a lob write operation inside a query
- ORA-14554: cannot perform requested operation during database startup
- ORA-14601: Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template
- ORA-14602: SUBPARTITION TEMPLATE is legal only for a composite partitioned table
- ORA-14603: [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables
- ORA-14604: During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified
- ORA-14605: Name missing for subpartition / lob segment in template
- ORA-14606: Tablespace was specified for previous subpartitions in template but is not specified for [string]
- ORA-14607: Tablespace was not specified for previous subpartitions in template but is specified for [string]
- ORA-14608: Tablespace was specified for the previous lob segments of column [string] in template but is not specified for [string]
- ORA-14609: Tablespace was not specified for the previous lob segments of column [string] in template but is specified for [string]
- ORA-14610: Lob attributes not specified for lob column [string] for subpartition [string]
- ORA-14611: Duplicate subpartition name [string] in template
- ORA-14612: Duplicate lob segment name [string] for lob column [string] in template
- ORA-14613: Attempt to generate name from parent name [string] and template name [string] failed as the combine named would have been longer than allowed
- ORA-14614: List value '[string]' specified twice in subpartition '[string]'
- ORA-14615: List value '[string]' specified twice in subpartitions '[string]', '[string]'
- ORA-14616: table is not subpartitioned by List method
- ORA-14617: cannot add/drop values to DEFAULT subpartition
- ORA-14618: cannot drop the last value of subpartition
- ORA-14619: resulting List subpartition(s) must contain at least 1 value
- ORA-14620: DEFAULT subpartition already exists
- ORA-14621: cannot add subpartition when DEFAULT subpartition exists
- ORA-14622: Value [string] already exists in subpartition [string]
- ORA-14623: Value [string] does not exist in subpartition [string]
- ORA-14624: DEFAULT subpartition must be last subpartition specified
- ORA-14625: subpartition contains rows corresponding to values being dropped
- ORA-14626: values being added already exist in DEFAULT subpartition
- ORA-14627: Invalid operation was specified on a GLOBAL partitioned index
- ORA-14628: specification of bounds is inconsistent with LIST method
- ORA-14629: cannot drop the only subpartition of a partition
- ORA-14630: subpartition resides in offlined tablespace
- ORA-14631: the partition bounds do not match the subpartition bounds of the partition
- ORA-14632: cannot specify PARALLEL clause when adding a List subpartition
- ORA-14633: Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table
- ORA-14634: Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table
- ORA-14635: only one resulting subpartition can be specified for MERGE SUBPARTITIONS
- ORA-14636: only 2 resulting subpartition can be specified for SPLIT SUBPARTITION
- ORA-14637: cannot merge a subpartition with itself
- ORA-14638: cannot MERGE subpartitions in different Range Composite partitions
- ORA-14639: SUBPARTITIONS clause can be specfied only for Hash, Composite Range Hash table/partition
- ORA-14640: add/coalesce index partition operation is valid only for hash partitioned global indexes
- ORA-14641: STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition
- ORA-14642: Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
- ORA-14643: Hakan factor mismatch for tables in ALTER TABLE EXCHANGE PARTITION
- ORA-14644: table is not subpartitioned by Hash method
- ORA-14645: STORE IN clause cannot be specified for Range List objects
- ORA-14646: Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes
- ORA-14650: operation not supported for reference-partitioned tables
- ORA-14651: reference partitioning constraint is not supported
- ORA-14652: reference partitioning foreign key is not supported
- ORA-14653: parent table of a reference-partitioned table must be partitioned
- ORA-14654: number of partitions of reference-partitioned table must equal that of the parent table
- ORA-14655: reference partitioning constraint not found
- ORA-14656: cannot drop the parent of a reference-partitioned table
- ORA-14657: cannot cascade row migration to reference-partitioned child table
- ORA-14658: specified dependent table is not affected by this operation
- ORA-14659: Partitioning method of the parent table is not supported
- ORA-14660: parent table of a reference-partitioned table cannot be index-organized
- ORA-14661: row movement must be enabled
- ORA-14662: row movement cannot be enabled
- ORA-14663: reference partitioning parent key is not supported
- ORA-14700: Object(s) owned by SYS cannot be locked by non-SYS user
- ORA-14701: partition-extended name or bind variable must be used for DMLs on tables partitioned by the System method
- ORA-14702: The partition number is invalid or out-of-range
- ORA-14703: The AFTER clause can be used to ADD PARTITION only to a System Partitioned table.
- ORA-14704: Create table as select disallowed for SYSTEM patitioned tables
- ORA-14750: Range partitioned table with INTERVAL clause has more than one column
- ORA-14751: Invalid data type for partitioning column of an interval partitioned table
- ORA-14752: Interval expression is not a constant of the correct type
- ORA-14753: Interval cannot be zero
- ORA-14754: Interval [string] is too long
- ORA-14755: Invalid partition specification for FOR VALUES clause.
- ORA-14756: Table is not partitioned by Interval method.
- ORA-14757: Table is already a range partitioned table
- ORA-14758: Last partition in the range section cannot be dropped
- ORA-14759: SET INTERVAL is not legal on this table.
- ORA-14760: ADD PARTITION is not permitted on Interval partitioned objects
- ORA-14761: MAXVALUE partition cannot be specified for Interval partitioned objects
- ORA-14762: Domain index creation on interval partitioned tables is not permitted
- ORA-14763: Unable to resolve FOR VALUES clause to a partition number
- ORA-14764: FOR VALUES clause cannot be specified for only one partition
- ORA-14765: Cannot create a partition while doing a create index
- ORA-14766: Unable to obtain a stable metadata snapshot
- ORA-14767: Cannot specify this interval with existing high bounds
- ORA-14801: Hash composite partitioning is not supported
- ORA-14802: Specified operation is not permitted on Hash composite partitioned objects
- ORA-14803: partition bound may not be specified for hash subpartitioned tables
- ORA-15000: command disallowed by current instance type
- ORA-15001: diskgroup "[string]" does not exist or is not mounted
- ORA-15002: parameter LOCK_NAME_SPACE exceeds limit of [string] characters
- ORA-15003: diskgroup "[string]" already mounted in another lock name space
- ORA-15004: alias "[string]" does not exist
- ORA-15005: name "[string]" is already used by an existing alias
- ORA-15006: template "[string]" does not exist
- ORA-15007: name is already used by an existing template
- ORA-15008: cannot drop system template
- ORA-15009: ASM disk "[string]" does not exist
- ORA-15010: name '[string]' is already used by an existing ASM disk
- ORA-15011: failure group "[string]" does not exist in diskgroup "[string]"
- ORA-15012: ASM file '[string]' does not exist
- ORA-15013: diskgroup "[string]" is already mounted
- ORA-15014: path '[string]' is not in the discovery set
- ORA-15015: Specified path '[string]' conflicts with path '[string]'
- ORA-15016: inconsistent respecification of path '[string]'
- ORA-15017: diskgroup "[string]" cannot be mounted
- ORA-15018: diskgroup cannot be created
- ORA-15019: discovered duplicate path '[string]' for '[string]'
- ORA-15020: discovered duplicate ASM disk "[string]"
- ORA-15021: parameter "[string]" is not valid in [string] instance
- ORA-15023: reached maximum allowable number of disks [string]
- ORA-15024: discovered duplicately numbered ASM disk [string]
- ORA-15025: could not open disk '[string]'
- ORA-15026: disk '[string]' is not an ASM disk
- ORA-15027: active use of diskgroup "[string]" precludes its dismount
- ORA-15028: ASM file '[string]' not dropped; currently being accessed
- ORA-15029: disk '[string]' is already mounted by this instance
- ORA-15030: diskgroup name "[string]" is in use by another diskgroup
- ORA-15031: disk specification '[string]' matches no disks
- ORA-15032: not all alterations performed
- ORA-15033: disk '[string]' belongs to diskgroup "string"
- ORA-15034: disk '[string]' does not require the FORCE option
- ORA-15035: no disks belong to diskgroup "[string]"
- ORA-15036: disk '[string]' is truncated
- ORA-15037: disk '[string]' is smaller than mimimum of string MBs
- ORA-15038: disk '[string]' size mismatch with diskgroup [string] [string] [string]
- ORA-15039: diskgroup not dropped
- ORA-15040: diskgroup is incomplete
- ORA-15041: diskgroup space exhausted
- ORA-15042: ASM disk "[string]" is missing
- ORA-15043: ASM disk "[string]" is not a diskgroup member
- ORA-15044: ASM disk '[string]' is incorrectly named
- ORA-15045: ASM file name '[string]' is not in reference form
- ORA-15046: ASM file name '[string]' is not in single-file creation form
- ORA-15047: ASM file name '[string]' is not in multiple-file creation form
- ORA-15048: ASM internal files cannot be deleted
- ORA-15049: diskgroup "[string]" contains [string] error(s)
- ORA-15050: disk "[string]" contains [string] error(s)
- ORA-15051: file '[string]' contains string error(s)
- ORA-15052: ASM file name '[string]' is not in diskgroup "string"
- ORA-15053: diskgroup "[string]" contains existing files
- ORA-15054: disk "[string]" does not exist in diskgroup "[string]"
- ORA-15055: unable to connect to ASM instance
- ORA-15056: additional error message
- ORA-15057: specified size of [string] MB is larger than actual size of [string] MB
- ORA-15058: disk '[string]' belongs to an incompatible diskgroup
- ORA-15059: invalid device type for ASM disk
- ORA-15060: template "[string]" does not exist
- ORA-15061: ASM operation not supported [string]
- ORA-15062: ASM disk is globally closed
- ORA-15063: ASM discovered an insufficient number of disks for diskgroup "[string]"
- ORA-15064: communication failure with ASM instance
- ORA-15065: hash collision for diskgroup names '[string]' and '[string]'
- ORA-15066: offlining disk "[string]" may result in a data loss
- ORA-15067: command or option incompatible with diskgroup redundancy
- ORA-15068: maximum number of diskgroups [string] already mounted
- ORA-15069: ASM file '[string]' not accessible; timed out waiting for lock
- ORA-15070: maximum number of files [string] exceeded in diskgroup "[string]"
- ORA-15071: ASM disk "[string]" is already being dropped
- ORA-15072: command requires at least [string] failure groups, discovered only [string]
- ORA-15073: diskgroup [string] is mounted by another ASM instance
- ORA-15074: diskgroup [string] requires rebalance completion
- ORA-15075: disk(s) are not visible cluster-wide
- ORA-15076: Emulating I/O errors on the OSM disk
- ORA-15077: could not locate ASM instance serving a required diskgroup
- ORA-15078: ASM diskgroup was forcibly dismounted
- ORA-15079: ASM file is closed
- ORA-15080: synchronous I/O operation to a disk failed
- ORA-15081: failed to submit an I/O operation to a disk
- ORA-15082: ASM failed to communicate with database instance
- ORA-15083: failed to communicate with ASMB background process
- ORA-15084: ASM disk "[string]" is offline and cannot be dropped.
- ORA-15090: handle [string] is not a valid descriptor
- ORA-15091: operation incompatible with open handle in this session
- ORA-15092: I/O request size [string] is not a multiple of logical block size [string]
- ORA-15093: buffer only contains [string] bytes, I/O requested is [string] bytes
- ORA-15094: attempted to write to file opened in read only mode
- ORA-15095: reached maximum ASM file size ([string] GB)
- ORA-15096: lost disk write detected
- ORA-15097: cannot SHUTDOWN ASM instance with connected RDBMS instance
- ORA-15098: file type not recognized by ASM instance
- ORA-15099: disk '[string]' is larger than maximum size of string MBs
- ORA-15100: invalid or missing diskgroup name
- ORA-15101: no action specified
- ORA-15102: invalid POWER expression
- ORA-15103: conflicting or duplicate REPAIR options
- ORA-15104: conflicting CONTENTS options
- ORA-15105: missing or invalid FAILGROUP name
- ORA-15106: missing or invalid operating system disk locator [string]
- ORA-15107: missing or invalid ASM disk name
- ORA-15108: missing or invalid template name
- ORA-15109: conflicting protection attributes specified
- ORA-15110: no diskgroups mounted
- ORA-15111: conflicting or duplicate STRIPE options
- ORA-15112: no diskgroups currently mounted
- ORA-15113: alias name '[string]' refers to a directory
- ORA-15114: missing or invalid ASM file name
- ORA-15115: missing or invalid ASM disk size specifier
- ORA-15116: invalid combination of ALTER DISKGROUP options
- ORA-15117: command only operates on one diskgroup
- ORA-15120: ASM file name '[string]' does not begin with the ASM prefix character
- ORA-15121: ASM file name '[string]' contains an invalid diskgroup name
- ORA-15122: ASM file name '[string]' contains an invalid file number
- ORA-15123: ASM file name '[string]' contains an invalid incarnation number
- ORA-15124: ASM file name '[string]' contains an invalid alias name
- ORA-15125: ASM file name '[string]' contains an invalid template name
- ORA-15126: component within ASM file name '[string]' exceeds maximum length
- ORA-15127: ASM file name '[string]' cannot use templates
- ORA-15128: ASM file name '[string]' exceeds maximum length string
- ORA-15129: entry '[string]' does not refer to a valid directory
- ORA-15130: diskgroup "[string]" is being dismounted
- ORA-15131: block [string] of file [string] in diskgroup [string] could not be read
- ORA-15132: block [string] of file [string] in diskgroup [string] could not be written
- ORA-15133: instance recovery required for diskgroup [string]
- ORA-15150: instance lock mode '[string]' conflicts with other ASM instance(s)
- ORA-15151: missing or invalid version number for rolling migration
- ORA-15152: cluster in rolling upgrade
- ORA-15153: cluster not in rolling upgrade
- ORA-15154: cluster rolling upgrade incomplete
- ORA-15155: version incompatible with the cluster
- ORA-15156: cluster in rolling upgrade from version [string] to [string]
- ORA-15157: rolling migration is not allowed
- ORA-15158: rolling upgrade prevented by [string]
- ORA-15160: rolling migration internal fatal error in module [string],[string]
- ORA-15161: invalid SYS_CLUSTER_PROPERTIES parameter
- ORA-15162: cluster in rolling downgrade
- ORA-15163: cluster not in rolling downgrade
- ORA-15164: cluster rolling downgrade incomplete
- ORA-15166: cluster in rolling downgrade from version [string] to [string]
- ORA-15168: rolling downgrade prevented by [string]
- ORA-15169: destination '[string]' is a subdirectory of '[string]'
- ORA-15170: cannot add entry '[string]' in directory '[string]'
- ORA-15171: invalid syntax in the alias path after '[string]'
- ORA-15173: entry '[string]' does not exist in directory '[string]'
- ORA-15175: cannot create alias for diskgroup metadata file '[string]'
- ORA-15176: file '[string]' already has an alias associated with it
- ORA-15177: cannot operate on system aliases
- ORA-15178: directory '[string]' is not empty; cannot drop this directory
- ORA-15179: missing or invalid alias name
- ORA-15180: could not open dynamic library string, error [string]
- ORA-15181: symbol [string] not found in library string, error [string]
- ORA-15182: ASMLIB [string] version mismatch, ORACLE version [string]
- ORA-15183: ASMLIB initialization error [string]
- ORA-15184: ASMLIB error could not be determined [string] [string]
- ORA-15185: could not close dynamic library string, error [string]
- ORA-15186: ASMLIB error function = [string], error = [string], mesg = [string]
- ORA-15192: invalid ASM disk header [string] [string] [string] [string] [string]
- ORA-15196: invalid ASM block header [string:string] [string] [string] [string] [string != string]
- ORA-15197: suppressing [string] additional ASM messages
- ORA-15198: operation [string] is not yet available
- ORA-15200: initialization parameter [string] ([string]) is not a power of two
- ORA-15201: disk [string] contains a valid RDBMS file
- ORA-15202: cannot create additional ASM internal change segment
- ORA-15203: diskgroup [string] contains disks from an incompatible version of ASM
- ORA-15204: database version [string] is incompatible with diskgroup [string]
- ORA-15205: requested mirror side unavailable
- ORA-15206: duplicate diskgroup [string] specified
- ORA-15210: conflicting or duplicate PERMISSION options
- ORA-15211: conflicting or duplicate OWNERSHIP options
- ORA-15212: missing or invalid OWNER or GROUP name
- ORA-15213: command operates on only one attribute
- ORA-15214: missing or invalid attribute specification
- ORA-15215: missing or invalid user name
- ORA-15216: missing or invalid user group name
- ORA-15217: missing or invalid timeout value after DROP AFTER
- ORA-15218: timeout value exceeded range
- ORA-15219: conflicting or duplicate ZONE options
- ORA-15220: invalid file attribute specification
- ORA-15221: ASM operation requires compatible.asm of [string] or higher
- ORA-15230: diskgroup '[string]' does not require the FORCE option
- ORA-15231: advancing diskgroup compatibility would exclude connected clients
- ORA-15232: cannot advance diskgroup compatibility due to offline disks
- ORA-15233: cannot advance diskgroup compatibility due to [string]
- ORA-15234: target RDBMS compatibility ([string]) exceeds ASM compatibility ([string])
- ORA-15235: diskgroup [string] mount mode conflicts with existing mount
- ORA-15236: diskgroup [string] mounted in restricted mode
- ORA-15237: attribute [string] cannot be set in CREATE DISKGROUP
- ORA-15238: [string] is not a valid value for attribute [string]
- ORA-15239: allocation unit size higher than [string] requires RDBMS compatibility [string]
- ORA-15240: attribute name [string] is invalid
- ORA-15241: attribute [string] is read only
- ORA-15242: could not set attribute [string]
- ORA-15243: [string] is not a valid version number
- ORA-15244: new compatibility setting less than current [string]
- ORA-15245: ASM disk [string] is already being brought online
- ORA-15246: cannot bring ASM disk [string] both online and then offline in the same statement
- ORA-15247: cannot specify both WAIT and NOWAIT options in the same statement
- ORA-15248: ASM attributes feature not enabled
- ORA-15249: could not locate ASM attribute [string]
- ORA-15250: insufficient diskgroup space for rebalance completion
- ORA-15251: only restricted mount is allowed in the ASM instance
- ORA-15281: not all specified disks were brought ONLINE
- ORA-15282: ASM disk "[string]" is not visible cluster-wide
- ORA-15283: ASM operation requires compatible.rdbms of [string] or higher
- ORA-15284: ASM terminated ALTER DISKGROUP ONLINE
- ORA-15285: disk '[string]' violates disk group attribute string
- ORA-15286: could not set disk group attribute [string] due to offline disks
- ORA-15287: could not set disk group attribute [string] due to incompatible disks
- ORA-15288: disk(s) require disk group attribute [string] clause
- ORA-15289: ASM disk [string] cannot be resized beyond [string] M
- ORA-15290: operation not permitted on offline disk [string]
- ORA-15291: ASM could not add disk "[string]" to disk group "[string]"
- ORA-15292: Disk name [string] is being used by another disk
- ORA-15293: operation disallowed by ASM_POWER_LIMIT
- ORA-15294: SYSASM privilege not allowed on database instance
- ORA-15295: FINE striping not allowed for the Staleness Registry
- ORA-15450: invalid volume name specifier
- ORA-15451: missing or invalid volume size specifier
- ORA-15452: missing or invalid stripe width specifier
- ORA-15453: invalid STRIPE_COLUMNS specifier
- ORA-15454: ALTER DISKGROUP ALL cannot use single volume names
- ORA-15455: FORCE option cannot be used when specifying ALL volumes
- ORA-15456: missing or invalid volume usage specifier
- ORA-15457: first letter of the volume name is not alphabetic
- ORA-15458: invalid character in volume name
- ORA-15459: STRIPE_WIDTH of [string] is not a power of two
- ORA-15460: volume name '[string]' is already in use
- ORA-15461: STRIPE_WIDTH of [string] bytes is less than the minimum of [string] bytes
- ORA-15462: STRIPE_WIDTH of [string] bytes is greater than the maximum of [string] bytes
- ORA-15463: volume size of [string]K is less then the minimum of [string]M
- ORA-15464: STRIPE_COLUMNS of [string] is greater than the maximum of [string]
- ORA-15465: STRIPE_COLUMNS of [string] is less than the minimum of [string]
- ORA-15466: volume name '[string]' does not exist
- ORA-15467: volume operation is already in progress
- ORA-15468: operation not permitted; volume '[string]' currently being accessed
- ORA-15469: VBG process terminated with error
- ORA-15470: VDBG process terminated with error
- ORA-15471: volume redundancy incompatible with diskgroup redundancy
- ORA-15472: volume library cannot be loaded. Platform may not support volume creation.
- ORA-15473: access to a volume''s storage through an unsupported interface
- ORA-15474: volume name is greater than [string] characters
- ORA-15475: usage [string] is greater than [string] characters
- ORA-15476: resize of OFS volume must use OFS resize command
- ORA-15477: cannot communicate with the volume driver
- ORA-15478: OFSC process terminated with error
- ORA-15479: diskgroup version incompatible with ASM volumes
- ORA-15480: error reported in the ASM volume driver
- ORA-15481: missing or invalid volume mountpath specifier
- ORA-15482: failed to create/remove path to volume device file
- ORA-15501: cannot start workload capture on instance [string]
- ORA-15502: cannot stop workload capture on instance [string]
- ORA-15503: cannot startup instance when procedures in "DBMS_WORKLOAD_CAPTURE" or "DBMS_WORKLOAD_REPLAY" are in the middle of their execution
- ORA-15504: cannot start workload capture because instance [string] not present in RESTRICTED SESSION mode
- ORA-15505: cannot start workload capture because instance [string] encountered errors while accessing directory "[string]"
- ORA-15506: cannot prepare instance [string] for replay
- ORA-15507: cannot start workload replay on instance [string]
- ORA-15508: cannot cancel workload replay on instance [string]
- ORA-15509: workload replay has been cancelled
- ORA-15510: cannot perform operation when "STATISTICS_LEVEL" is "BASIC"
- ORA-15511: cannot process workload capture because no user sessions were recorded
- ORA-15512: directory "[string]" does not contain a valid processed workload capture
- ORA-15513: cannot access the input directory
- ORA-15514: cannot find a match for the remote procedure call during replay
- ORA-15515: error while replaying remote procedure call: "[string].[string].[string]"
- ORA-15516: parallel preprocessing worker hit error ORA-[string]
- ORA-15517: cannot start parallel preprocessing worker
- ORA-15518: parallel preprocessing encountered an unexpected error
- ORA-15551: workload replay client cannot connect to database server
- ORA-15552: workload replay client cannot login to database server
- ORA-15553: workload replay client cannot execute the DBMS_WORKLOAD_REPLAY package
- ORA-15554: cannot start workload replay client because the database server is not in PREPARE mode
- ORA-15555: workload replay client encountered unexpected error: "[string]"
- ORA-15556: invalid input specified to the workload replay client
- ORA-15557: workload replay client cannot access the replay directory or the database version do not match the preprocessing one
- ORA-15558: replay thread encountered unexpected error
- ORA-15559: workload replay client cannot open workload capture file
- ORA-15560: workload replay client cannot access the work directory
- ORA-15561: workload replay client cannot connect to the remapped connection with conn_id : [string]
- ORA-15562: workload replay client cannot read the DBA_WORKLOAD_CONNECTION_MAP view
- ORA-15563: workload replay client cannot spawn new threads
- ORA-15564: contents of the replay directory provided to the workload replay client do not match with the replay directory provided to the database server
- ORA-15566: workload replay client cannot replay user call in the current version
- ORA-15590: encountered an incomplete workload capture file
- ORA-15601: Invalid value specified for parameter "[string]"
- ORA-15602: Parameter "[string]" cannot be NULL.
- ORA-15603: Action cannot be performed when database is in read-only mode.
- ORA-15604: Initialization parameters prevent client from being enabled.
- ORA-15605: "[string]" is not a Maintenance Window
- ORA-16000: database open for read-only access
- ORA-16001: database already open for read-only access by another instance
- ORA-16002: database already open for read-write access by another instance
- ORA-16003: standby database is restricted to read-only access
- ORA-16004: backup database requires recovery
- ORA-16005: database requires recovery
- ORA-16006: audit_trail destination incompatible with database open mode
- ORA-16007: invalid backup control file checkpoint
- ORA-16008: indeterminate control file checkpoint
- ORA-16009: remote archive log destination must be a STANDBY database
- ORA-16011: Archivelog Remote File Server process in Error state
- ORA-16012: Archive log standby database identifier mismatch
- ORA-16013: log [string] sequence# [string] does not need archiving
- ORA-16014: log [string] sequence# [string] not archived, no available destinations
- ORA-16015: log [string] sequence# [string] not archived, media recovery disabled
- ORA-16016: archived log for thread [string] sequence# [string] unavailable
- ORA-16017: cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination
- ORA-16018: cannot use [string] with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST
- ORA-16019: cannot use [string] with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST
- ORA-16020: less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST
- ORA-16021: session [string] destination cannot be the same as session [string] destination
- ORA-16022: LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL
- ORA-16023: system [string] destination cannot be the same as session [string] destination
- ORA-16024: parameter [string] cannot be parsed
- ORA-16025: parameter [string] contains repeated or conflicting attributes
- ORA-16026: parameter [string] contains an invalid attribute value
- ORA-16027: parameter [string] is missing a destination option
- ORA-16028: new [string] causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires
- ORA-16029: cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations
- ORA-16030: session specific change requires a LOG_ARCHIVE_DEST_n destination
- ORA-16031: parameter [string] destination [string] exceeds [string] character limit
- ORA-16032: parameter [string] destination [string] cannot be translated
- ORA-16033: parameter [string] destination cannot be the same as parameter [string] destination
- ORA-16034: FROM parameter is incompatible with MANAGED recovery
- ORA-16035: missing required keyword [string]
- ORA-16036: invalid MANAGED recovery CANCEL option
- ORA-16037: user requested cancel of managed recovery operation
- ORA-16038: log [string] sequence# [string] cannot be archived
- ORA-16039: RFS request version mismatch
- ORA-16040: standby destination archive log file is locked
- ORA-16041: Remote File Server fatal error
- ORA-16042: user requested cancel immediate of managed recovery operation
- ORA-16043: managed recovery session canceled
- ORA-16044: destination [string] attribute cannot be specified at session level
- ORA-16045: circular archive log destination dependency chain
- ORA-16046: Archive log destination failed due to failed dependent destination
- ORA-16047: DGID mismatch between destination setting and standby
- ORA-16050: destination exceeded specified quota size
- ORA-16051: parameter [string] contains an invalid delay time
- ORA-16052: DB_UNIQUE_NAME attribute is required
- ORA-16053: DB_UNIQUE_NAME [string] is not in the Data Guard Configuration
- ORA-16055: FAL request rejected
- ORA-16056: backup control file archival requires proper syntax
- ORA-16057: DGID from server not in Data Guard configuration
- ORA-16058: standby database instance is not mounted
- ORA-16059: Log file is empty or invalid next available block
- ORA-16060: Log file is current
- ORA-16061: Log file status has changed
- ORA-16062: DGID from standby not in Data Guard configuration
- ORA-16063: remote archival is enabled by another instance
- ORA-16064: remote archival is disabled by another instance
- ORA-16065: remote archival disabled at standby destination
- ORA-16066: remote archival disabled
- ORA-16067: activation identifier mismatch in archive log [string]
- ORA-16068: redo log file activation identifier mismatch
- ORA-16069: Archive Log standby database activation identifier mismatch
- ORA-16070: parameter [string] contains an invalid REGISTER attribute value
- ORA-16071: dependency archived log file not found [string]
- ORA-16072: a minimum of one standby database destination is required
- ORA-16073: archiving must be enabled
- ORA-16074: ARCH processes must be active
- ORA-16075: standby database destination mismatch
- ORA-16076: unknown standby database destination
- ORA-16078: media recovery disabled
- ORA-16079: standby archival not enabled
- ORA-16080: invalid LogMiner session [string] for APPLY
- ORA-16081: insufficient number of processes for APPLY
- ORA-16082: logical standby is not initialized correctly
- ORA-16083: LogMiner session has not been created
- ORA-16084: an apply engine is already running
- ORA-16086: standby database does not contain available standby log files
- ORA-16087: graceful switchover requires standby or current control file
- ORA-16088: archive log has not been completely archived
- ORA-16089: archive log has already been registered
- ORA-16090: archive log to be replaced not created by managed standby process
- ORA-16091: dependent archive log destination already archived
- ORA-16092: dependent archive log destination is not active
- ORA-16093: dependent archive log destination is not LGWR-enabled
- ORA-16094: database shutdown during archival operation
- ORA-16095: Dependent destination removal for inactivation
- ORA-16098: inaccessible standby database forced shutdown to protect primary
- ORA-16099: internal error ORA-00600 occurred at standby database
- ORA-16100: not a valid Logical Standby database
- ORA-16101: a valid start SCN could not be found
- ORA-16102: remote information is not available on the specified primary
- ORA-16103: Logical Standby apply must be stopped to allow this operation
- ORA-16104: Invalid Logical Standby parameter
- ORA-16105: Logical Standby is already running in background
- ORA-16107: all log data from primary has been processed
- ORA-16108: database is no longer a standby database
- ORA-16109: failed to apply log data from previous primary
- ORA-16110: user procedure processing of logical standby apply DDL
- ORA-16111: log mining and apply setting up
- ORA-16112: log mining and apply stopping
- ORA-16113: applying change to table or sequence [string]
- ORA-16114: applying DDL transaction with commit SCN [string]
- ORA-16115: [string]\% of LogMiner dictionary loading is done
- ORA-16116: no work available
- ORA-16117: processing
- ORA-16119: building transaction at SCN [string]
- ORA-16120: dependencies being computed for transaction at SCN [string]
- ORA-16121: applying transaction with commit SCN [string]
- ORA-16122: applying large dml transaction at SCN [string]
- ORA-16123: transaction [string] [string] [string] is waiting for commit approval
- ORA-16124: transaction [string] [string] [string] is waiting on another transaction
- ORA-16125: large transaction [string] [string] [string] is waiting for more data
- ORA-16126: loading table or sequence [string]
- ORA-16127: stalled waiting for additional transactions to be applied
- ORA-16128: User initiated stop apply successfully completed
- ORA-16129: unsupported dml encountered
- ORA-16130: supplemental log information is missing from log stream
- ORA-16131: An error occurred during a Terminal Recovery of the standby.
- ORA-16132: An error occurred during activation of the standby.
- ORA-16133: Datafile [string] has incorrect terminal recovery stamp.
- ORA-16134: invalid MANAGED recovery FINISH option
- ORA-16135: Invalid LOG_ARCHIVE_CONFIG modification while in protected mode
- ORA-16136: Managed Standby Recovery not active
- ORA-16138: end of log stream not received from primary
- ORA-16139: media recovery required
- ORA-16140: standby online logs have not been recovered
- ORA-16143: RFS connections not allowed during or after terminal recovery
- ORA-16145: archival for thread# [string] sequence# [string] in progress
- ORA-16146: standby destination control file enqueue unavailable
- ORA-16147: standby database referenced by multiple archive log destinations
- ORA-16148: user requested expiration of managed recovery operation
- ORA-16150: FINISH recovery performed on another, older standby database
- ORA-16151: Managed Standby Recovery not available
- ORA-16152: standby database is in ''no-data-loss'' protected mode
- ORA-16154: suspect attribute: [string]
- ORA-16156: LGWR archive log dependency not allowed if database is standby protected
- ORA-16157: media recovery not allowed following successful FINISH recovery
- ORA-16159: Cannot change protected standby destination attributes
- ORA-16160: Cannot change protected standby database configuration
- ORA-16161: Cannot mix standby and online redo log file members for group [string]
- ORA-16162: Cannot add new standby databases to protected configuration
- ORA-16163: LGWR network server host attach error
- ORA-16164: LGWR network server host detach error
- ORA-16165: LGWR failed to hear from network server
- ORA-16166: LGWR network server failed to send remote message
- ORA-16167: LGWR network server could not switch to non-blocking mode
- ORA-16168: LGWR network server could not switch to blocking mode
- ORA-16169: LGWR network server invalid parameters
- ORA-16170: Terminal recovery may have left the database in an inconsistent state
- ORA-16171: RECOVER...FINISH not allowed due to gap for thr [string], seq [string]-[string]
- ORA-16172: archive logs detected beyond Terminal End-Of-Redo
- ORA-16173: incompatible archival network connections active
- ORA-16174: user requested thread/sequence termination of managed recovery
- ORA-16175: cannot shut down database when media recovery is active
- ORA-16176: background dictionary build cannot be running
- ORA-16177: media recovery is not required
- ORA-16178: Cannot specify remote destinations in archivelog manual mode
- ORA-16179: incremental changes to "[string]" not allowed with SPFILE
- ORA-16180: number of processes specified is too large
- ORA-16181: SGA specified for Logical Standby is too large
- ORA-16182: Internal error on internal channel during remote archival
- ORA-16184: DB_UNIQUE_NAME [string] hashes to the same value as DB_UNIQUE_NAME [string]
- ORA-16185: REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG mutually exclusive
- ORA-16186: Modifying LOG_ARCHIVE_CONFIG requires SID=''*'' qualifier
- ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
- ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
- ORA-16191: Primary log shipping client not logged on standby
- ORA-16192: Primary and standby network integrity mismatch
- ORA-16193: Primary and standby network encryption mismatch
- ORA-16194: Modifying DB_UNIQUE_NAME requires SID=''*'' qualifier
- ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
- ORA-16196: database has been previously opened and closed
- ORA-16197: Invalid DB_UNIQUE_NAME parameter specification
- ORA-16198: Timeout incurred on internal channel during remote archival
- ORA-16199: Terminal recovery failed to recover to a consistent point
- ORA-16200: Skip procedure requested to skip statement
- ORA-16201: Skip procedure requested to apply statement
- ORA-16202: Skip procedure requested to replace statement
- ORA-16203: Unable to interpret skip procedure return values
- ORA-16204: DDL successfully applied
- ORA-16205: DDL skipped due to skip setting
- ORA-16206: database already configured as Logical Standby database
- ORA-16207: Logical standby dictionary build not permitted.
- ORA-16208: Logical standby dictionary build failed to start.
- ORA-16209: Logical standby dictionary build failed to complete.
- ORA-16210: Logical standby coordinator process terminated with error
- ORA-16211: unsupported record found in the archived redo log
- ORA-16212: number of processes specified for SQL Apply is too great
- ORA-16213: ddl encountered, stopping apply engine
- ORA-16214: apply stalled for apply delay
- ORA-16215: history metadata inconsistency
- ORA-16216: Log stream sequence error
- ORA-16217: prepare to switchover has not completed
- ORA-16218: This database is already preparing to switch over.
- ORA-16219: This database is not preparing to switch over.
- ORA-16220: no failed transaction found
- ORA-16221: history table synchronization error
- ORA-16222: automatic Logical Standby retry of last action
- ORA-16223: DDL skipped, unsupported in current version
- ORA-16224: Database Guard is enabled
- ORA-16225: Missing LogMiner session name for Streams
- ORA-16226: DDL skipped due to lack of support
- ORA-16227: DDL skipped due to missing object
- ORA-16228: Insufficient recovery for logical standby
- ORA-16229: PDML child [string] [string] [string] for parent [string] [string] [string] cannot be skipped.
- ORA-16230: committing transaction [string] [string] [string]
- ORA-16232: adding Logical Standby skip entry for table [string].[string]
- ORA-16233: The table [string].[string] is unsupported now
- ORA-16234: restarting to reset Logical Standby apply
- ORA-16235: DDL skipped because import has occurred
- ORA-16236: Logical Standby metadata operation in progress
- ORA-16237: SGA specified for Logical Standby is too small
- ORA-16238: attempt to use version 9 log
- ORA-16239: IMMEDIATE option not available without standby redo logs
- ORA-16240: Waiting for logfile (thread# [string], sequence# [string])
- ORA-16241: Waiting for gap logfile (thread# [string], sequence# [string])
- ORA-16242: Processing logfile (thread# [string], sequence# [string])
- ORA-16243: paging out [string] bytes of memory to disk
- ORA-16246: User initiated abort apply successfully completed
- ORA-16247: DDL skipped on internal schema
- ORA-16248: RFS connections not permitted during Terminal Apply
- ORA-16249: Terminal apply failed to complete during failover
- ORA-16250: Failed to acquire starting scn of new log stream
- ORA-16251: LSP1 Background Build not permitted
- ORA-16252: Rebuild operation not permitted
- ORA-16253: Logical Standby cannot start due to incomplete terminal apply
- ORA-16254: change db_name to [string] in the client-side parameter file (pfile)
- ORA-16255: Log Auto Delete conflicts with another LogMiner session
- ORA-16256: Failure to complete standby redo logfile archival after failover
- ORA-16257: Switchover initiated stop apply successfully completed
- ORA-16258: marking index unusable due to a constraint violation
- ORA-16259: Switchover to logical standby requires a log archive destination
- ORA-16260: Waiting to replace partial or corrupt logfile (thread# [string], sequence# [string])
- ORA-16261: Identification key mismatch for table "[string]"."[string]".
- ORA-16262: Invalid value specified for Logical Standby parameter
- ORA-16263: Dynamic parameters can only be set on SQL apply instance
- ORA-16264: invalid value for PREPARE_SERVERS parameter
- ORA-16265: Unsupported PL/SQL procedure encountered
- ORA-16266: Cannot instantiate a Logical Standby from another Logical Standby
- ORA-16267: Cannot instantiate a Logical Standby during a switchover
- ORA-16268: user procedure processing of logical standby apply PL/SQL
- ORA-16269: PL/SQL procedure skipped due to failure on primary database
- ORA-16270: PL/SQL procedure skipped due to unmaintained standby objects
- ORA-16271: PL/SQL successfully applied
- ORA-16272: PL/SQL procedure skipped due to skip setting
- ORA-16273: invalid value for APPLY_SERVERS parameter
- ORA-16274: failure to perform DDL on all RAC instances
- ORA-16275: prior failed CTAS detected and pre-existing table dropped
- ORA-16276: specified database link does not correspond to primary database
- ORA-16277: specified table is not supported by logical standby database
- ORA-16278: specified table has a multi-object skip rule defined
- ORA-16279: Supplied dblink must have CONNECT, RESOURCE, and SELECT_CATALOG_ROLE roles
- ORA-16280: cannot change master key on a logical standby database
- ORA-16281: missing identification key for table "[string]"."[string]".
- ORA-16282: operation not permitted during rolling upgrade
- ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST
- ORA-16401: archivelog rejected by RFS
- ORA-16402: ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support
- ORA-16403: shutdown in progress - remote connection is not permitted
- ORA-16406: Primary and standby database software version mismatch
- ORA-16407: Standby database is in the future of the archive log
- ORA-16408: Incompatible archival Redo Branch lineage
- ORA-16409: Archive log switchover reference number mismatch
- ORA-16411: ONDEMAND archival requires active managed recovery operation
- ORA-16412: ONDEMAND archival requires active SQL apply operation
- ORA-16413: Unsupported database type for ONDEMAND archivelog destinations
- ORA-16416: Switchover target is not synchronized with the primary
- ORA-16417: Activation occurred after recovery from standby redo log files; a full database backup is required
- ORA-16419: Snapshot standby must be converted from physical standby
- ORA-16420: fast-start failover target cannot be converted to snapshot standby
- ORA-16424: Terminal recovery cannot start due to GAP on Physical Standby
- ORA-16425: Terminal recovery branch [string] older than target branch [string]
- ORA-16426: log requested by recovery is not the correct log
- ORA-16427: Potential archive log gap too large to service
- ORA-16431: Cannot expand control file
- ORA-16432: inconsistent set of terminal logs detected
- ORA-16433: The database has not been opened in read-write mode
- ORA-16438: Switchover to primary cannot be executed at this time
- ORA-16501: the Data Guard broker operation failed
- ORA-16502: the Data Guard broker operation succeeded with warnings
- ORA-16504: the Data Guard configuration already exists
- ORA-16505: site ID is invalid
- ORA-16506: out of memory
- ORA-16507: unrecognized request identifier
- ORA-16509: request timed out
- ORA-16513: maximum requests exceeded
- ORA-16514: request was not found
- ORA-16516: current state is invalid for the attempted operation
- ORA-16523: operation requires the client to connect to instance "[string]"
- ORA-16524: unsupported operation
- ORA-16525: the Data Guard broker is not yet available
- ORA-16526: unable to allocate task element
- ORA-16527: unable to allocate broker SGA memory
- ORA-16528: unable to allocate PGA memory
- ORA-16530: invalid buffer or length
- ORA-16532: Data Guard broker configuration does not exist
- ORA-16534: no more requests accepted
- ORA-16535: CRS is preventing execution of a broker operation
- ORA-16541: database is not enabled
- ORA-16544: modifying DG_BROKER_START requires SID=''*'' qualifier
- ORA-16545: unable to get response
- ORA-16546: missing or invalid value
- ORA-16547: cannot disable or delete the primary database
- ORA-16548: database not enabled
- ORA-16549: invalid [string]
- ORA-16550: truncated result
- ORA-16551: short [string] copied
- ORA-16552: an error occurred when generating the CLIENT OPERATION table
- ORA-16555: database is not active
- ORA-16556: observer version mismatch
- ORA-16557: database is already in use
- ORA-16558: database specified for switchover is not a standby database
- ORA-16561: cannot remove an active instance
- ORA-16568: cannot set property [string]
- ORA-16569: Data Guard configuration is not enabled
- ORA-16570: database needs restart
- ORA-16571: Data Guard configuration file creation failure
- ORA-16572: Data Guard configuration file not found
- ORA-16573: attempt to change or access configuration file for an enabled broker configuration
- ORA-16574: switchover disallowed when required databases are shut down
- ORA-16575: request terminated at broker discretion
- ORA-16576: failed to update Data Guard configuration file
- ORA-16577: corruption detected in Data Guard configuration file
- ORA-16578: failed to read Data Guard configuration file
- ORA-16582: cannot change instance-specific property
- ORA-16586: cannot change database property with EDIT INSTANCE command
- ORA-16587: ambiguous object specified to Data Guard broker
- ORA-16589: Data Guard broker detected network transfer error
- ORA-16594: DMON background process is not running
- ORA-16595: process [string] failed to terminate
- ORA-16596: database not part of the Data Guard broker configuration
- ORA-16597: Data Guard broker detects two or more primary databases
- ORA-16598: Data Guard broker detected a mismatch in configuration
- ORA-16599: Data Guard broker detected a stale configuration
- ORA-16600: not connected to target standby database for failover
- ORA-16602: database must be disabled to perform this operation
- ORA-16603: Data Guard broker detected a mismatch in configuration ID
- ORA-16606: unable to find property "[string]"
- ORA-16607: one or more databases have failed
- ORA-16608: one or more databases have warnings
- ORA-16609: database is being disabled
- ORA-16610: command "[string]" in progress
- ORA-16611: command aborted at user request
- ORA-16612: [string] value too long for attribute "[string]"
- ORA-16613: initialization in progress for database
- ORA-16614: Data Guard broker configuration is disabled
- ORA-16617: unknown object identifier specified in request
- ORA-16619: health check timed out
- ORA-16620: one or more databases could not be reached for a delete operation
- ORA-16621: database name for ADD DATABASE must be unique
- ORA-16622: two or more broker database objects resolve to the same database
- ORA-16623: database detected role change
- ORA-16624: broker protocol version mismatch detected
- ORA-16625: cannot reach the database
- ORA-16626: failed to enable specified database
- ORA-16627: operation disallowed since no standby databases would remain to support protection mode
- ORA-16628: broker protection mode inconsistent with the database setting
- ORA-16629: database reports a different protection level from the protection mode
- ORA-16630: database property has been deprecated
- ORA-16631: operation requires shutdown of database or instance "[string]"
- ORA-16632: instance being added to database profile
- ORA-16633: the only instance of the database cannot be removed
- ORA-16635: network connection failed during transmission
- ORA-16636: fast-start failover target standby in error state, cannot stop observer
- ORA-16637: an instance failed to access the Data Guard broker configuration
- ORA-16638: could not get the instance status
- ORA-16639: specified instance inactive or currently unavailable
- ORA-16640: CRS warns that multiple instances may still be running
- ORA-16642: DB_UNIQUE_NAME mismatch
- ORA-16643: unable to determine location of broker configuration files
- ORA-16644: apply instance not available
- ORA-16645: unexpected new instance interrupted current operation
- ORA-16646: fast-start failover is disabled
- ORA-16647: could not start more than one observer
- ORA-16648: a new observer registered with identifier [string]
- ORA-16649: possible failover to another database prevents this database being opened
- ORA-16650: command incompatible when fast-start failover is enabled
- ORA-16651: requirements not met for enabling fast-start failover
- ORA-16652: fast-start failover target standby database is disabled
- ORA-16653: failed to reinstate database
- ORA-16654: fast-start failover is enabled
- ORA-16655: specified target standby database invalid
- ORA-16656: Data Guard broker detected role change
- ORA-16657: reinstatement of database in progress
- ORA-16658: unobserved fast-start failover configuration
- ORA-16659: failover operation in progress
- ORA-16660: fast-start failover operation attempted in absence of a broker configuration
- ORA-16661: the standby database needs to be reinstated
- ORA-16662: network timeout when contacting a database
- ORA-16664: unable to receive the result from a database
- ORA-16665: timeout waiting for the result from a database
- ORA-16666: unable to initiate fast-start failover on a standby database
- ORA-16667: request Data Guard broker client to reissue command
- ORA-16668: operation invalid on fast-start failover target database
- ORA-16700: the standby database has diverged from the primary database
- ORA-16701: Data Guard broker command failed
- ORA-16702: Data Guard broker command warning
- ORA-16703: cannot set property while the database is enabled
- ORA-16704: cannot modify a read-only property
- ORA-16706: no resource guard is available
- ORA-16707: the value of the property [string] is invalid, valid values are [string]
- ORA-16708: the state supplied to broker is invalid
- ORA-16709: standby archived log location settings conflict with database recovery area
- ORA-16713: the Data Guard broker command timed out
- ORA-16714: the value of property [string] is inconsistent with the database setting
- ORA-16715: redo transport-related property [string] of standby database "[string]" is inconsistent
- ORA-16716: clearing parameter LOG_ARCHIVE_DEST failed
- ORA-16717: clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed
- ORA-16718: failed to locate database
- ORA-16719: unable to query V$ARCHIVE_DEST fixed view
- ORA-16720: no LOG_ARCHIVE_DEST_n initialization parameters available
- ORA-16721: unable to set LOG_ARCHIVE_DEST_n initialization parameters
- ORA-16722: unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters
- ORA-16723: setting AlternateLocation property conflicts with the redo transport setting
- ORA-16727: cannot close database
- ORA-16728: consistency check for property [string] found [string] error
- ORA-16729: validation of value for property [string] found [string] error
- ORA-16730: error executing DBMS_LOGSTDBY.SKIP_TXN procedure
- ORA-16731: error executing DBMS_LOGSTDBY.UNSKIP_TXN procedure
- ORA-16732: error executing DBMS_LOGSTDBY.SKIP procedure
- ORA-16733: error executing DBMS_LOGSTDBY.UNSKIP procedure
- ORA-16734: error executing DBMS_LOGSTDBY.SKIP_ERROR procedure
- ORA-16735: error executing DBMS_LOGSTDBY.UNSKIP_ERROR procedure
- ORA-16736: unable to find the destination entry of standby database "[string]" in V$ARCHIVE_DEST
- ORA-16737: the redo transport service for standby database "[string]" has an error
- ORA-16738: redo transport service for database "[string]" is not running
- ORA-16739: redo transport service for standby database "[string]" is running
- ORA-16740: redo transport service for standby database "[string]" incorrectly set to ALTERNATE
- ORA-16741: the destination parameter of standby database "[string]" has incorrect syntax
- ORA-16742: the standby database "[string]" has exhausted its quota
- ORA-16743: cannot determine status of redo transport service for standby database "[string]"
- ORA-16744: the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full
- ORA-16745: unable to add DB_UNIQUE_NAME "[string]" into the DG_CONFIG list because it is full
- ORA-16746: Data Guard broker cannot mount the database
- ORA-16747: logical standby database guard could not be turned on
- ORA-16748: Data Guard broker cannot open the primary database
- ORA-16749: switchover to logical standby database failed
- ORA-16750: failed to activate logical standby database
- ORA-16751: failed to switchover to physical standby database
- ORA-16753: Data Guard broker cannot open standby database
- ORA-16754: failed to activate physical standby database
- ORA-16755: failed to set initialization parameter
- ORA-16757: unable to get this property''s value
- ORA-16758: the specified apply instance is not running
- ORA-16759: cannot start SQL Apply with initial SCN
- ORA-16760: cannot start SQL Apply
- ORA-16761: cannot stop SQL Apply
- ORA-16762: invalid database state
- ORA-16763: redo transport service for a standby database is running
- ORA-16764: redo transport service to a standby database is not running
- ORA-16765: Redo Apply is running
- ORA-16766: Redo Apply is stopped
- ORA-16767: SQL Apply is running
- ORA-16768: SQL Apply is stopped
- ORA-16769: the physical standby database is open read-only
- ORA-16770: Redo Apply not started since physical standby database is opening
- ORA-16771: failover to a physical standby database failed
- ORA-16772: switchover to a standby database failed
- ORA-16773: cannot start Redo Apply
- ORA-16774: cannot stop Redo Apply
- ORA-16775: target standby database in broker operation has potential data loss
- ORA-16776: health check of the redo transport service failed
- ORA-16777: unable to find the destination entry of a standby database in V$ARCHIVE_DEST
- ORA-16778: redo transport error for one or more databases
- ORA-16779: the destination parameter of a database is set incorrectly
- ORA-16780: a database has exhausted its archived redo log storage quota
- ORA-16781: cannot determine status of redo transport service for standby database
- ORA-16782: instance not open for read and write access
- ORA-16783: instance [string] not open for read and write access
- ORA-16784: database name specified by Dependency property is incorrect
- ORA-16785: the database is in NOARCHIVELOG mode
- ORA-16786: unable to access Data Guard broker metadata
- ORA-16788: unable to set one or more database configuration property values
- ORA-16789: standby redo logs not configured
- ORA-16790: the value of the configurable property is invalid
- ORA-16791: unable to check the existence of the standby redo logs
- ORA-16792: configurable property value is inconsistent with database setting
- ORA-16793: logical standby database guard is off
- ORA-16794: database guard is on for primary database
- ORA-16795: the standby database needs to be re-created
- ORA-16796: one or more properties could not be imported from the database
- ORA-16797: database is not using a server parameter file
- ORA-16798: unable to complete terminal recovery on the standby database
- ORA-16799: Redo Apply is not running
- ORA-16800: redo transport service for a standby database incorrectly set to ALTERNATE
- ORA-16801: redo transport-related property is inconsistent with database setting
- ORA-16802: downgrading redo transport mode from SYNC disallowed
- ORA-16803: unable to query a database table or fixed view
- ORA-16804: one or more configuration properties in metadata have invalid values
- ORA-16805: change of LogXptMode property violates overall protection mode
- ORA-16806: supplemental logging is not turned on
- ORA-16807: unable to change database protection mode
- ORA-16808: primary database is not open
- ORA-16809: multiple warnings detected for the database
- ORA-16810: multiple errors or warnings detected for the database
- ORA-16811: apply instance not recorded by the Data Guard broker
- ORA-16812: log apply service not running on apply instance recorded by the broker
- ORA-16813: log apply service not running on apply instance [string] recorded by the broker
- ORA-16814: incorrect redo transport setting for AlternateLocation for standby database
- ORA-16815: incorrect redo transport setting for AlternateLocation for standby database "[string]"
- ORA-16816: incorrect database role
- ORA-16817: unsynchronized fast-start failover configuration
- ORA-16818: fast-start failover suspended
- ORA-16819: fast-start failover observer not started
- ORA-16820: fast-start failover observer is no longer observing this database
- ORA-16821: logical standby database dictionary not yet loaded
- ORA-16822: new primary database not yet ready for standby database reinstatement
- ORA-16823: redo transport mode is incompatible for current operation
- ORA-16824: multiple warnings, including fast-start failover-related warnings, detected for the database
- ORA-16825: multiple errors or warnings, including fast-start failover-related errors or warnings, detected for the database
- ORA-16826: apply service state is inconsistent with the DelayMins property
- ORA-16827: Flashback Database is disabled
- ORA-16828: invalid value specified for REDO_TRANSPORT_USER initialization parameter
- ORA-16829: fast-start failover configuration is lagging
- ORA-16830: primary isolated from fast-start failover partners longer than FastStartFailoverThreshold seconds: shutting down
- ORA-16831: operation disallowed on this standby database type
- ORA-16950: Remote mapped cursors are not supported by this feature.
- ORA-16951: Too many bind variables supplied for this SQL statement.
- ORA-16952: Failed to bind this SQL statement.
- ORA-16953: Type of SQL statement not supported.
- ORA-16954: SQL parse error.
- ORA-16955: Unknown error during SQL analyze.
- ORA-16956: Only SELECT or DML statements are supported for test execute.
- ORA-16957: SQL Analyze time limit interrupt
- ORA-16958: DML statements running parallel are not supported for test execute.
- ORA-16959: Statement type has been disabled for SQL Analyze
- ORA-16960: SQL Analyze could not reproduce the desired plan.
- ORA-16961: SQL statement with SQL patch is ignored
- ORA-17500: ODM err:[string]
- ORA-17501: logical block size [string] is invalid
- ORA-17502: ksfdcre:[string] Failed to create file [string]
- ORA-17503: ksfdopn:[string] Failed to open file [string]
- ORA-17504: ksfddel:Failed to delete file [string]
- ORA-17505: ksfdrsz:[string] Failed to resize file to size [string] blocks
- ORA-17506: I/O Error Simulation
- ORA-17507: I/O request size [string] is not a multiple of logical block size
- ORA-17508: I/O request buffer ptr is not alligned
- ORA-17509: Attempt to do i/o beyond block1 offset
- ORA-17510: Attempt to do i/o beyond file size
- ORA-17512: Block Verification Failed
- ORA-17610: file '[string]' does not exist and no size specified
- ORA-17611: ksfd: file '[string]' cannot be accessed, global open closed
- ORA-17612: Failed to discover Oracle Disk Manager library, return value [string]
- ORA-17613: Failed to initialize Oracle Disk Manager library: [string]
- ORA-17618: Unable to update block 0 to version 10 format
- ORA-17619: max number of processes using I/O slaves in a instance reached
- ORA-17620: failed to register the network adapter with Oracle Disk Manager library: [string]
- ORA-17621: failed to register the memory with Oracle Disk Manager library
- ORA-17622: failed to deregister the memory with Oracle Disk Manager library
- ORA-17624: Failed to delete directory [string]
- ORA-17626: ksfdcre: [string] file exists
- ORA-17627: [string]
- ORA-17628: Oracle error [string] returned by remote Oracle server
- ORA-17629: Cannot connect to the remote database server
- ORA-17630: Mismatch in the remote file protocol version client [string] server [string]
- ORA-17631: dbname '[string]' specified by remote server does not match the instance name '[string]'
- ORA-17632: file '[string]' is a formatted ASM disk
- ORA-18000: invalid outline name
- ORA-18001: no options specified for ALTER OUTLINE
- ORA-18002: the specified outline does not exist
- ORA-18003: an outline already exists with this signature
- ORA-18004: outline already exists
- ORA-18008: cannot find OUTLN schema
- ORA-18009: one or more outline system tables do not exist
- ORA-18010: command missing mandatory CATEGORY keyword
- ORA-18015: invalid source outline signature
- ORA-19000: missing RELATIONAL keyword
- ORA-19001: Invalid storage option specified
- ORA-19002: Missing XMLSchema URL
- ORA-19003: Missing XML root element name
- ORA-19004: Duplicate XMLType OBJECT RELATIONAL storage option
- ORA-19005: Duplicate XMLType LOB storage option
- ORA-19006: XMLType TYPE storage option not appropriate for storage type
- ORA-19007: Schema [string] does not match expected [string].
- ORA-19008: Invalid version of the XMLType
- ORA-19009: Missing XMLSchema keyword
- ORA-19010: Cannot insert XML fragments
- ORA-19011: Character [string] buffer too small
- ORA-19012: Cannot convert XML fragment to the required datatype
- ORA-19013: Cannot create VARRAY columns containing XMLType
- ORA-19015: Invalid XML tag identifier ([string])
- ORA-19016: attributes cannot occur after element specifications
- ORA-19017: Attributes can only be simple scalars
- ORA-19018: Invalid character in XML tag '[string]'
- ORA-19019: Invalid context passed to DBMS_XMLGEN.GETXML
- ORA-19020: invalid dereference of XMLType columns
- ORA-19023: The first argument to UPDATEXML operator has to be an XMLTYPE
- ORA-19024: Cursor expression must be named
- ORA-19025: EXTRACTVALUE returns value of only one node
- ORA-19026: EXTRACTVALUE can only retrieve value of leaf node
- ORA-19028: Invalid ADT parameter passed to toObject() function
- ORA-19029: Cannot convert the given XMLType to the required type
- ORA-19030: Method invalid for non-schema based XML Documents.
- ORA-19031: XML element or attribute [string] does not match any in type [string].[string]
- ORA-19032: Expected XML tag [string] got [string]
- ORA-19033: schema specified in the XML document does not match the schema parameter
- ORA-19034: Type not supported during schema generation
- ORA-19035: Invalid select item of the query in newContextFromHierarchy()
- ORA-19036: Invalid query result set in newContextFromHierarchy()
- ORA-19037: XMLType result can not be a fragment
- ORA-19038: Invalid opertions on query context
- ORA-19039: Keyword [string] reserved for future use
- ORA-19040: Element [string] does not match expected [string].
- ORA-19041: Comment data cannot contain two consecutive ''-''s
- ORA-19042: Enclosing tag [string] cannot be xml in any case combination
- ORA-19043: Multiply nested XMLROOT function disallowed
- ORA-19044: character length specified for XMLSerialize is too small.
- ORA-19045: character set id specified for XMLSerialize not valid
- ORA-19100: PASSING or RETURNING keyword expected
- ORA-19101: CONTENT keyword expected
- ORA-19102: XQuery [string] literal expected
- ORA-19103: VALUE keyword keyword
- ORA-19104: invalid XQueryX: missing attribute [string]
- ORA-19105: invalid XQueryX: expected text node - got [string]
- ORA-19106: invalid XQueryX: expected [string] - got [string]
- ORA-19107: invalid XQueryX - unsupported construct - [string]
- ORA-19108: WHITESPACE keyword expected
- ORA-19109: RETURNING keyword expected
- ORA-19110: unsupported XQuery expression
- ORA-19111: error during evaluation of the XQuery expression
- ORA-19112: error raised during evaluation: [string]
- ORA-19113: trace function called during evaluation: [string]
- ORA-19114: XPST0003 - error during parsing the XQuery expression: [string]
- ORA-19115: too many context items specified
- ORA-19116: too many xmlspace declarations
- ORA-19117: XQST0070 - invalid redefinition of predefined namespace prefix '[string]'
- ORA-19118: XQST0066 - duplicate default namespace definition - [string]
- ORA-19121: duplicate attribute definition - [string]
- ORA-19122: unsupported XQuery declaration
- ORA-19123: FORG0003: fn:zero-or-one() called with a sequence containing more than one item
- ORA-19124: FORG0004: fn:one-or-more() called with a sequence containing no items
- ORA-19125: FORG0005: fn:exactly-one() called with a sequence containing zero or more than one item
- ORA-19126: XQuery extension expression contains neither a pragma that is recognized by the implementation nor an expression enclosed in curly braces
- ORA-19127: XQST0067: XQST0067: A static error is raised if a Prolog contains more than one construction declaration
- ORA-19128: XQST0068: A static error is raised if a Prolog contains more than one boundary-space declaration
- ORA-19129: XQST0069: A static error is raised if a Prolog contains more than one empty order declaration
- ORA-19130: XQST0070: A static error is raised if the predefined namespace prefix xml or xmlns is redeclared by a namespace declaration or namespace declaration attribute
- ORA-19131: XQST0071: A static error is raised if the namespace declaration attributes of a direct element constructor do not have distinct names
- ORA-19132: XQDY0072: It is a dynamic error if the result of the content expression of a computed comment constructor contains two adjacent hyphens or ends with a hyphen
- ORA-19133: XQST0073: It is a static error if the graph of module imports contains a cycle (that is, if there exists a sequence of modules M1 ... Mn such that each Mi imports Mi+1 and Mn imports M1), unless all the modules in the cycle share a common namespace
- ORA-19134: XQDY0074: It is a dynamic error if the value of the name expression in a computed element constructor cannot be converted to an expanded QName (for example, because it contains a namespace prefix not found in statically known namespaces.)
- ORA-19135: XQST0075: An implementation that does not support the Validation Feature must raise a static error if it encounters a validate expression
- ORA-19136: XQST0076: It is a static error if a collation subclause in an order by clause of a FLWOR expression does not identify a collation that is present in statically known collations
- ORA-19137: XQST0079: It is a static error if an extension expression contains neither a pragma that is recognized by the implementation nor an expression enclosed in curly braces
- ORA-19138: The target type of a cast or castable expression must be an atomic type that is in the in-scope schema types and is not xs:NOTATION or xs:anyAtomicType, optionally followed by the occurrence indicator "?"; otherwise a static error is raised
- ORA-19139: XPST0081: It is a static error if a QName used in a query contains a namespace prefix that cannot be expanded into a namespace URI by using the statically known namespaces
- ORA-19140: XPST0083: It is a static error if the target type of a cast expression or constructor function is xs:QName or a type derived from xs:QName or xs:NOTATION, and the argument of the cast expression or constructor function is not a [string] literal
- ORA-19141: XQDY0084: It is a dynamic error if the element validated by a validate statement does not have a top-level element declaration in the in-scope element declarations, if validation mode is strict
- ORA-19142: FONC0001 = FONC0001: undefined context item
- ORA-19143: XQTY0086: It is a type error if the typed value of a copied element or attribute node is namespace-sensitive when construction mode is preserve and copy-namespaces mode is no-preserve
- ORA-19145: XQST0087: It is a static error if the encoding specified in a Version Declaration does not conform to the definition of EncName specified in [XML 1.0]
- ORA-19146: XQST0088: It is a static error if the literal that specifies the target namespace in a module import or a module declaration is of zero length
- ORA-19147: XQST0089: It is a static error if a variable bound in a for clause of a FLWOR expression, and its associated positional variable, do not have distinct names (expanded QNames)
- ORA-19148: XQST0090: It is a static error if a character reference does not identify a valid character in the version of XML that is in use
- ORA-19149: XQDY0091: An implementation may raise a dynamic error if an xml:id error, as defined in [XML ID], is encountered during construction of an attribute named xml:id
- ORA-19150: XQDY0092: An implementation may raise a dynamic error if a constructed attribute named xml:space has a value other than preserve or default
- ORA-19151: XQST0093: It is a static error to import a module M1 if there exists a sequence of modules M1 ... Mi ... M1 such that each module directly depends on the next module in the sequence (informally, if M1 depends on itself through some chain of module dependencies.)
- ORA-19152: FOCH0001 = FOCH0001: codepoint not valid
- ORA-19153: FOCH0002: unsupported collation
- ORA-19154: FOCH0003: unsupported normalization form
- ORA-19155: FOCH0004: collation does not support collation units
- ORA-19156: FODC0001: no context document
- ORA-19157: FODC0002: error retrieving resource
- ORA-19158: FODC0004: invalid argument to fn:collection()
- ORA-19159: FODC0005: invalid argument to fn:doc
- ORA-19160: XPST0003 - syntax error: invalid variable name [string]
- ORA-19161: XPTY0004 - XQuery type mismatch: invalid argument type '[string]' for function '[string]'
- ORA-19162: XPTY0004 - XQuery type mismatch: invalid argument types '[string]', '[string]' for function '[string]'
- ORA-19163: XPTY0004 - XQuery type mismatch: argument type mismatch: expected - '[string]' got - '[string]' for function '[string]'
- ORA-19164: XQST0085 - It is a static error if the namespace URI in a namespace declaration attribute is a zero-length [string], and the implementation does not support [XML Names 1.1].
- ORA-19165: FONS0003: no prefix defined for namespace
- ORA-19166: FONS0003: FONS0004: no namespace found for prefix
- ORA-19167: FONS0005: base uri not defined in the static context
- ORA-19168: FORG0002: invalid argument to fn:resolve-uri()
- ORA-19169: FORG0006: invalid argument type in '[string]'
- ORA-19171: FORG0007: invalid argument to aggregate function
- ORA-19172: FORG0008: both arguments to fn:dateTime have a specified timezone
- ORA-19173: FORG0009: error in resolving a relative URI against a base URI in fn:resolve-uri
- ORA-19174: FORX0001: invalid regular expression flags
- ORA-19175: FORX0002: invalid regular expression
- ORA-19176: FORX0003: regular expression matches zero-length [string]
- ORA-19177: FORX0004: invalid replacement [string]
- ORA-19178: FOTY0001: type error
- ORA-19179: FOTY0011: Type error. Context item is not a node
- ORA-19180: FOTY0012: argument node does not have a typed value
- ORA-19181: FOTY0014: type exception
- ORA-19182: FORT0001: invalid number of parameters
- ORA-19183: FOTY0002: type definition not found
- ORA-19184: FOTY0021: invalid node type
- ORA-19185: FOAR0002: numeric operation overflow/unflow
- ORA-19186: FOCA0001: input value too large for decimal
- ORA-19187: FOCA0002: invalid lexical value
- ORA-19188: FOCA0003: input value too large for integer
- ORA-19189: FOCA0005: NaN supplied as float/double value
- ORA-19190: FOER0000: Unidentified error
- ORA-19191: FOAR0001: division by zero
- ORA-19192: XQST0047: It is a static error if multiple module imports in the same Prolog specify the same target namespace
- ORA-19193: XQST0045: It is a static error if the function name in a function declaration is in one of the following namespaces: http://www.w3.org/XML/1998/namespace, http://www.w3.org/2001/XMLSchema, http://www.w3.org/2001/XMLSchema-instance, http://www.w3.org/2005/04/xpath-functions, http://www.w3.org/2005/04/xpath-datatypes
- "">ORA-19194: XQDY0026: It is a dynamic error if the result of the content expression of a computed processing instruction constructor contains the [string] "?>"
- ORA-19200: Invalid column specification
- ORA-19201: Datatype not supported
- ORA-19202: Error occurred in XML processing[string]
- ORA-19203: Error occurred in DBMS_XMLGEN processing[string]
- ORA-19204: Non-scalar value '[string]' is marked as XML attribute
- ORA-19205: Attribute '[string]' qualifies a non-scalar value in the select list
- ORA-19206: Invalid value for query or REF CURSOR parameter
- ORA-19207: scalar parameter [string] of XMLELEMENT cannot have an alias.
- ORA-19208: parameter [string] of function [string] must be aliased
- ORA-19209: invalid or unsupported formatting argument
- ORA-19210: column '[string]', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table '[string]'
- ORA-19211: column '[string]', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
- ORA-19212: no key columns specified before call to DBMS_XMLSTORE.updateXML()
- ORA-19221: XPST0001 - XQuery static context component [string] not initialized
- ORA-19222: XPDY0002 - XQuery dynamic context component [string] not initialized
- ORA-19223: XPST0003 - syntax error in XQuery expression
- ORA-19224: XPTY0004 - XQuery static type mismatch: expected - [string] got - [string]
- ORA-19225: XPST0005 - XQuery static type error: expected non empty type got empty sequence
- ORA-19226: XPTY0006 - XQuery dynamic type mismatch: expected [string] got [string]
- ORA-19227: XPTY0007 - fn:data function is applied to a node (type ([string])) whose type annotation denotes a complex type with non-mixed complex content.
- ORA-19228: XPST0008 - undeclared identifier: prefix '[string]' local-name '[string]'
- ORA-19229: XQST0009 - schema import not supported
- ORA-19230: XPST0010 - unsupported axis [string]
- ORA-19232: XQST0012 - imported schemas violate validity rules
- ORA-19233: XQST0013 - invalid pragma
- ORA-19234: XQST0014 - invalid or unsupported must-understand extension
- ORA-19235: XQST0015 - unsupported must-understand extension
- ORA-19236: XQST0016 - module declaration or import not supported
- ORA-19237: XPST0017 - unable to resolve call to function - [string]:[string]
- ORA-19238: XPTY0018 - It is a type error if the result of the last step in a path expression contains both nodes and atomic values
- ORA-19239: XPTY0019 - It is a type error if the result of an step (other than the last step) in a path expression contains an atomic value
- ORA-19240: XPTY0020 - context item must be node in an axis expression
- ORA-19241: XPDY0021 - cast to type [string] failed
- ORA-19242: XQST0022 - namespace declaration attribute must be a literal
- ORA-19243: XQTY0023 - invalid document node content in element constructor
- ORA-19244: XQTY0024 - invalid attribute node in element constructor
- ORA-19245: XQDY0025 - duplicate attribute name [string]
- ORA-19246: validation failed - element [string] not found in in-scope element declarations
- ORA-19247: XQDY0027 - validation error
- ORA-19248: XQTY0028 - invalid node in document constructor
- ORA-19249: XQDY0029 - value does not match facet of the target type
- ORA-19250: XQTY0030 - too many values to validate expression
- ORA-19251: XQST0031 - unsupported query version
- ORA-19252: XQST0032 - too many declarations for base URI
- ORA-19253: XQST0033 - too many declarations for namespace prefix [string]
- ORA-19254: XQST0034 - too many declarations for function [string]
- ORA-19255: XQST0035 - too many declarations of [string] in imported schemas
- ORA-19256: XQST0036 - missing type definitions in imported module
- ORA-19257: XQST0037 - function or variable [string] in module already defined
- ORA-19258: XQST0038 - unsupported or duplicate default collation specified
- ORA-19259: XQST0039 - duplicate parameter name [string] in function declaration
- ORA-19260: XQST0040 - invalid namespace node in element constructor
- ORA-19261: XQDY0041 - non empty URI in QName
- ORA-19262: XQST0042 - namespace constructor not inside an element constructor
- ORA-19263: XQST0043 - duplicate namespace prefix [string]
- ORA-19264: XQDY0044 - invalid namespace in attribute constructors
- ORA-19265: XQST0045 - invalid or unknown prefix [string] in function declaration
- ORA-19266: XQST0046 - invalid URI
- ORA-19267: module [string] not found
- ORA-19268: XQST0048 - namespace [string] does not match target namespace [string]
- ORA-19269: XQST0049 - variable [string] defined multiple times
- ORA-19270: XPDY0050 - treat failed - expected [string] got [string]
- ORA-19271: XPST0051 - invalid atomic type definition
- ORA-19272: XQDY0052 - invalid atomic value in attribute or element constructor
- ORA-19273: XQST0053 - empty [string] in namespace declaration
- ORA-19274: XQST0054 - variable initialization failed due to circularity
- ORA-19275: XQST0055 - schema path [string] not found in list of in-scope schema definitions
- ORA-19276: XPST0005 - XPath step specifies an invalid element/attribute name: ([string])
- ORA-19277: XPST0005 - XPath step specifies an item type matching no node: ([string])
- ORA-19278: Invalid value: ([string]) for type: ([string])
- ORA-19279: XPTY0004 - XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence
- ORA-19280: XQuery dynamic type mismatch: expected atomic value - got node
- ORA-19281: XQST0055 - It is a static error if a Prolog contains more than one copy-namespaces declaration
- ORA-19282: XQST0068 - It is a static error if a Prolog contains more than one xmlspace declaration
- ORA-19283: XQST0031 - It is a static error if the version number specified in a version declaration is not supported by the implementation.
- ORA-19284: Encoding specification in version declaration not supported
- ORA-19285: FODC0002 - error retrieving resource
- ORA-19286: XPST0017 - unable to resolve call to function - [string]
- ORA-19287: XPST0017 - invalid number of arguments to function - [string]:[string]
- ORA-19288: XPST0017 - invalid number of arguments to function - [string]
- ORA-19289: XQST0034 - function [string]:[string] declared or defined multiple times
- ORA-19290: XQST0069 - more than one empty order declaration declared in the prolog
- ORA-19291: XPST0081 - specified QName cannot be expanded into a namespace URI
- ORA-19292: XQST0057: It is a static error if a schema import binds a namespace prefix but does not specify a target namespace other than a zero-length [string]
- ORA-19293: XQST0058: It is a static error if multiple schema imports specify the same target namespace
- ORA-19294: XQST0059: It is a static error if an implementation is unable to process a schema or module import by finding a schema or module with the specified target namespace
- ORA-19295: XQST0060: It is a static error if the name of a function in a function declaration is not in a namespace (expanded QName has a null namespace URI)
- ORA-19296: XQDY0061: It is a dynamic error if the operand of a validate expression is a document node whose children do not consist of exactly one element node and zero or more comment and processing instruction nodes, in any order
- ORA-19297: XQDY0064: It is a dynamic error if the value of the name expression in a computed processing instruction constructor is equal to "XML" (in any combination of upper and lower case
- ORA-19298: XQST0065: A static error is raised if a Prolog contains more than one ordering mode declaration
- ORA-19299: XQST0066: A static error is raised if a Prolog contains more than one default element/type namespace declaration, or more than one default function namespace declaration
- ORA-19300: Error occurred in uri processing[string]
- ORA-19320: Host name not specified in HTTP URL
- ORA-19321: Could not open HTTP connection to host ([string]): port ([string])
- ORA-19322: An error occurred while reading from host ([string]): port ([string])
- ORA-19323: Invalid url [string]
- ORA-19330: Type '[string]'.'[string]' not installed. Please install the type before using the CREATE_DBURI operator
- ORA-19331: Last argument to CREATE_DBURI operator must be a column
- ORA-19332: Invalid column in the CREATE_DBURI operator
- ORA-19333: Invalid flags for the CREATE_DBURI operator
- ORA-19334: Invalid column specification for CREATE_DBURI operator
- ORA-19335: Invalid format type object
- ORA-19336: Missing XML root element
- ORA-19361: ONLINE option not allowed with this type of index
- ORA-19371: invalid update option
- ORA-19372: invalid update condition
- ORA-19373: invalid staging table or tablespace
- ORA-19374: invalid staging table
- ORA-19375: no CREATE TABLE privilege on schema "[string]"
- ORA-19376: no privileges on tablespace provided or tablespace is offline
- ORA-19377: no "SQL Tuning Set" with name like "[string]" exists for owner like "[string]"
- ORA-19378: invalid mode
- ORA-19379: invalid time_limit or repeat_interval
- ORA-19380: invalid plan filter
- ORA-19381: cannot create staging table in SYS schema
- ORA-19384: cannot pack into staging table from previous version
- ORA-19385: staging table is empty
- ORA-19386: target object already exists for tuning task "[string]"
- ORA-19387: "SQL Tuning Set" "[string]" belongs to another tuning task
- ORA-19388: operation not supported for "SQL Tuning Set" type
- ORA-19400: System type conflict with object SYS.[string]