ORA-14284: one or more of table's subpartitions
reside in a read-only tablespace
Cause:
User issued ALTER TABLE statement attempting to modify an existing VARCHAR2 (or
VARCHAR) column to be of type CHAR (or CHARACTER), increase length of an
existing CHAR (or CHARACTER) column, or add a column with user-specified
default for a table one or more subpartitions of which reside in read-only tablespaces,
which is illegal
Action:
Avoid performing aformentioned operations on a partitioned table one or more
subpartitions of which reside in read-only tablespaces
ORA-14285: cannot COALESCE the only partition of
this hash partitioned table or index
Cause:
A COALESCE PARTITION command was issued when there is only one partition in the
table or index, which is illegal
Action:
Ensure that there is at least one partition. Drop the table or index to remove
all partitions.
ORA-14286: cannot COALESCE the only subpartition of
this table partition
Cause:
A COALESCE SUBPARTITION command was issued when there is only one subpartition
in the partition which is illegal
Action:
Ensure that there is at least one subpartition. Drop partition to remove all
subpartitions.
ORA-14287: cannot REBUILD a partition of a
Composite Range partitioned index
Cause:
User attempted to rebuild a partition of a Composite Range partitioned index
which is illegal
Action:
REBUILD the index partition, a subpartition at a time
ORA-14288: index is not partitioned by Composite
Range method
Cause:
The index in a partition or subpartition maintenance operation (ALTER INDEX
MODIFY [SUBPARTITION|DEFAULT ATTRIBUTES FOR PARTITION] or ALTER INDEX REBUILD
SUBPARTITION command must be partitioned by Composite Range method
Action:
None
ORA-14289: cannot make local index partition of
Composite Range partitioned table unusable
Cause:
User attempted to rebuild a partition of a Composite Range partitioned index
which is illegal
Action:
None
ORA-14290: PRIMARY KEY constraint mismatch in ALTER
TABLE EXCHANGE [SUB]PARTITION
Cause:
The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE
[SUB]PARTITION statement have different PRIMARY KEY constraints.
Action:
Ensure that the two tables do not have PRIMARY KEY constraints defined on any
column or disable all PRIMARY KEY constraints on both tables. Then retry the
operation.
ORA-14291: cannot EXCHANGE a composite partition
with a non-partitioned table
Cause:
A composite partition can only be exchanged with a partitioned table.
Action:
Ensure that the table being exchanged is partitioned or that that the partition
being exchanged is non-composite.
ORA-14292: Partitioning type of table must match
subpartitioning type of composite partition
Cause:
When exchanging a partitioned table with a composite partition the partitioning
type of the table must match the subpartitioning type of the composite
partition.
Action:
Ensure that the partitioning type of partitioned table is the same as the subpartitioning
type of the composite partition.
ORA-14293: Number of partitioning columns does not
match number of subpartitioning columns
Cause:
When exchanging a partitioned table with a composite partition the number of
partitioning columns of the table must match the number of subpartitioning
columns of the composite partition.
Action:
Ensure that the number of partitioning columns in the partitioned table is the
same as the number of subpartitioning columns in the the composite partition.
ORA-14294: Number of partitions does not match
number of subpartitions
Cause:
When exchanging a partitioned table with a composite partition the number of
partitions of the table must match the number of subpartitions of the composite
partition.
Action:
Ensure that the number of partitions in the partitioned table is the same as
the number of subpartitions in the the composite partition.
ORA-14295: column type or size mismatch between
partitioning columns and subpartitioning columns
Cause:
When exchanging a partitioned table with a composite partition the type and
size of the partitioning columns of the table must match the type and size of
the subpartitioning columns of the composite partition.
Action:
Ensure that the type and size of the partitioning columns of the partitioned is
the same as the type and size of the subpartitioning columns of the composite
partition.
ORA-14296: Table block size mismatch in ALTER TABLE
EXCHANGE [SUB]PARTITION
Cause:
The block sizes of the two tables specified in the ALTER TABLE EXCHANGE
[SUB]PARTITION statement are different. For index organized tables, either the
block sizes of the index or the overflow (or both) do not match.
Action:
Ensure that the block sizes of the tables involved in the ALTER TABLE EXCHANGE
[SUB]PARTITION statement are the same. For index organized tables, ensure that
the block sizes of both the index and the overflow of the two tables match.
ORA-14297: Index block size mismatch in ALTER TABLE
EXCHANGE [SUB]PARTITION
Cause:
The block sizes of a pair of indexes being exchanged in the ALTER TABLE
EXCHANGE [SUB]PARTITION statement are different.
Action:
Ensure that the block sizes of the corresponding pairs of indexes that need to
be exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same.
ORA-14298: LOB column block size mismatch in ALTER
TABLE EXCHANGE [SUB]PARTITION
Cause:
The block sizes of a pair of corresponding LOB columns of the two tables
specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different.
Action:
Ensure that the block sizes of corresponding pairs of LOB columns of the tables
involved in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same.
ORA-14299: total number of partitions/subpartitions
exceeds the maximum limit
Cause:
The total number of combined fragments specified in partitions /subpartitions
exceeds 1048575.
Action:
Reissue the statement with fewer number of fragments
ORA-14301: table-level attributes must be specified
before partition-level attributes
Cause:
While processing an ALTER TABLE ADD COLUMN statement, table-level attributes of
LOB columns were encountered after processing partition-level attributes of LOB
columns or while processing CREATE TABLE statement, table-level attributes of
LOB columns were encountered after processing partition descriptions.
Action:
Modify the SQL statement to specify table-level attributes prior to
partition-level attributes or partition descriptions; then retry the statement.
ORA-14302: only one list of
added-LOB-storage-clauses can be specified in a statement
Cause:
While parsing an ALTER TABLE ADD COLUMN statement, one list of
added-LOB-storage-clauses was parsed when another list of
added-LOB-storage-clauses was encountered. There cannot be more than one list
of added-LOB-storage-clauses in a statement; all added-LOB-storage-clauses must
be combined into one list.
Action:
Combine all of the lists of added-LOB-storage-clauses into one list and retry
the statement.
ORA-14303: partitions or subpartitions are not in
the right order
Cause:
User attempted to rebuild a partition of a Composite Range partitioned index
which is illegal
Action:
Re-order the partitions or subpartitions in the added LOB storage clause by
partition or subpartition DDL order, and retry the statement.
ORA-14304: List partitioning method expects a
single partitioning column
Cause:
number of columns in a partitioning column list exceeded the legal limit of 1
for List partitioned objects
Action:
modify partitioning column list so that it consists of at most 1 column
ORA-14305: List value 'string' specified
twice in partition 'string'
Cause:
A list value cannot be specified more that once
Action:
Remove one of the specifications of the value
ORA-14306: List value 'string' specified
twice in partitions 'string', 'string'
Cause:
A list value cannot be specified more that once
Action:
Remove one of the specifications of the value
ORA-14307: partition contains too many list values
Cause:
Partition list contains more than 524288 list values
Action:
Reduce the number of values to not exceed 524288 values
ORA-14308: partition bound element must be one of:
string, datetime or interval literal, number, or NULL
Cause:
Partition bound list contained an element of invalid type (i.e. not a number,
non-empty string, datetime or interval literal, or NULL)
Action:
Ensure that all elements of partition bound list are of valid type
ORA-14309: Total count of list values exceeds
maximum allowed
Cause:
Partitioned object contains more than 524288 list values
Action:
Reduce number of values to less than 524288.
ORA-14310: VALUES LESS THAN or AT clause cannot be
used with List partitioned tables
Cause:
VALUES LESS THAN or AT clause can be used only with Range partitioned tables
Action:
Use VALUES (<value list>) clause with List partitioned tables
ORA-14311: Expecting VALUES LESS THAN or AT clause
Cause:
VALUES (<value list>) clause can be used only with List partitioned
tables
Action:
Use VALUES LESS THAN clause with Range partitioned tables
ORA-14312: Value string already exists in
partition string
Cause:
One of the list values in the ADD PARTITION or ADD VALUES statement already
exists in another partition
Action:
Remove the duplicate value from the statement and try again
ORA-14313: Value string does not exist in
partition string
Cause:
One of the list values in the SPLIT PARTITION or DROP VALUES statement does not
exist in the partition
Action:
Remove the value from the statement and try again
ORA-14314: resulting List partition(s) must contain
atleast 1 value
Cause:
After a SPLIT/DROP VALUE of a list partition, each resulting partition(as
applicable) must contain at least 1 value
Action:
Ensure that each of the resulting partitions contains atleast 1 value
ORA-14315: cannot merge a partition with itself
Cause:
The same partition name was specified twice for the merge operation
Action:
Re-submit operation with 2 distinct partition names
ORA-14316: table is not partitioned by List method
Cause:
ALTER TABLE ADD|DROP VALUES can only be performed on List partitioned objects
Action:
Re-issue the command against a List partitioned object.
ORA-14317: cannot drop the last value of partition
Cause:
ALTER TABLE DROP VALUES tried to drop the last value of the partition
Action:
Cannot execute the command, unless two or more values exist for partition
ORA-14318: DEFAULT partition must be last partition
specified
Cause:
A partition description follows the one describing the default partition
Action:
Ensure that the DEFAULT partition is the last partition description
ORA-14319: DEFAULT cannot be specified with other
values
Cause:
DEFAULT keyword has been specified along with other values when specifying the
values for a list partition
Action:
Ensure that if DEFAULT is specified, it is the only value specified
ORA-14320: DEFAULT cannot be specified for ADD/DROP
VALUES or SPLIT
Cause:
DEFAULT keyword has been specified when doing a ADD VALUES or DROP VALUES or
SPLIT partition or subpartition.
Action:
Ensure that DEFAULT is not specified for ADD/DROP VALUES or SPLIT
partition/subpartition operation.
ORA-14321: cannot add/drop values to DEFAULT
partition
Cause:
A ADD/DROP VALUES operation is being done on the default partition
Action:
Ensure that ADD/DROP VALUES is not done on the DEFAULT partition
ORA-14322: DEFAULT partition already exists
Cause:
A partition already exists with DEFAULT value
Action:
None
ORA-14323: cannot add partition when DEFAULT
partition exists
Cause:
An ADD PARTITION operation cannot be executed when a partition with DEFAULT
values exists
Action:
Issue a SPLIT of the DEFAULT partition instead
ORA-14324: values being added already exist in
DEFAULT partition
Cause:
An ADD VALUE operation cannot be executed because the values being added exist
in the DEFAULT partition
Action:
Issue a SPLIT of the DEFAULT partition and then MERGE the split partition into
the partition to which values need to be added
ORA-14325: only LOCAL indexes may be specified in
this clause
Cause:
A global index has been specified in the UPDATE INDEXES (..) clause
Action:
Only specify local indexes when using this clause
ORA-14326: Primary index on an IOT, DOMAIN and LOB
indexes may not be specified in the UPDATE INDEXES clause
Cause:
A Primary index on an IOT, DOMAIN or LOB index has been specified in the UPDATE
INDEXES (..) clause
Action:
Do not specify any of these indexes when using this clause
ORA-14327: Some index [sub]partitions could not be
rebuilt
Cause:
The first phase (partition DDL and index [sub]partition placement) completed
successfully. During the second phase, some of the index [sub]partitions could
not be rebuilt.
Action:
.
ORA-14329: domain index [sub]partitions cannot be
renamed in this clause
Cause:
The user tried to rename a domain index [sub]partition in the UPDATE INDEXES
clause of a ALTER TABLE MOVE [SUB]PARTITION operation. This is not allowed.
Action:
Leave the name blank or use the same name.
ORA-14330: Cannot drop a partition of a global
hash-partitioned index
Cause:
An attempt was made to drop a partition of a hash-partitioned global index.
Action:
Try COALESCE PARTITION instead.
ORA-14400: inserted partition key does not map to
any partition
Cause:
An attempt was made to insert a record into, a Range or Composite Range object,
with a concatenated partition key that is beyond the concatenated partition
bound list of the last partition -OR- An attempt was made to insert a record
into a List object with a partition key that did not match the literal values
specified for any of the partitions.
Action:
Do not insert the key. Or, add a partition capable of accepting the key, Or add
values matching the key to a partition specification
ORA-14401: inserted partition key is outside
specified partition
Cause:
the concatenated partition key of an inserted record is outside the ranges of
the two concatenated partition bound lists that delimit the partition named in
the INSERT statement
Action:
do not insert the key or insert it in another partition
ORA-14402: updating partition key column would
cause a partition change
Cause:
An UPDATE statement attempted to change the value of a partition key column
causing migration of the row to another partition
Action:
Do not attempt to update a partition key column or make sure that the new
partition key is within the range containing the old partition key.
ORA-14403: cursor invalidation detected after
getting DML partition lock
Cause:
cursor invalidation was detected after acquiring a partition lock during an
INSERT, UPDATE, DELETE statement. This error is never returned to user, because
is caught in opiexe() and the DML statement is retried.
Action:
nothing to be done, error should never be returned to user
ORA-14404: partitioned table contains partitions in
a different tablespace
Cause:
An attempt was made to drop a tablespace which contains tables whose partitions
are not completely contained in this tablespace
Action:
find tables with partitions which span the tablespace being dropped and some
other tablespace(s). Drop these tables or move partitions to a different
tablespace
ORA-14405: partitioned index contains partitions in
a different tablespace
Cause:
An attempt was made to drop a tablespace which contains indexes whose
partitions are not completely contained in this tablespace, and which are
defined on the tables which are completely contained in this tablespace.
Action:
find indexes with partitions which span the tablespace being dropped and some
other tablespace(s). Drop these indexes, or move the index partitions to a
different tablespace, or find the tables on which the indexes are defined, and
drop (or move) them.
ORA-14406: updated partition key is beyond highest
legal partition key
Cause:
At attempt was made to update a record with a concatenated partition key that
is beyond the concatenated partition bound list of the last partition.
Action:
Do not update the key. Or, add a partition capable of accepting the key.
ORA-14407: partitioned table contains subpartitions
in a different tablespace
Cause:
An attempt was made to drop a tablespace which contains tables whose
subpartitions are not completely contained in this tablespace
Action:
find tables with subpartitions which span the tablespace being dropped and some
other tablespace(s). Drop these tables or move subpartitions to a different
tablespace
ORA-14408: partitioned index contains subpartitions
in a different tablespace
Cause:
An attempt was made to drop a tablespace which contains indexes whose
subpartitions are not completely contained in this tablespace, and which are
defined on the tables which are completely contained in this tablespace.
Action:
find indexes with subpartitions which span the tablespace being dropped and
some other tablespace(s). Drop these indexes, or move the index partitions to a
different tablespace, or find the tables on which the indexes are defined, and
drop (or move) them.
ORA-14409: inserted partition key is outside
specified subpartition
Cause:
the concatenated partition key of an inserted record is outside the ranges of
the two concatenated subpartition bound lists that delimit the subpartition
named in the INSERT statement
Action:
do not insert the key or insert it in another subpartition
ORA-14411: The DDL cannot be run concurrently with
other DDLs
Cause:
Another conflicting DDL was already running.
Action:
Retry after the conflicting DDL has finished.
ORA-14450: attempt to access a transactional temp
table already in use
Cause:
An attempt was made to access a transactional temporary table that has been
already populated by a concurrent transaction of the same session.
Action:
do not attempt to access the temporary table until the concurrent transaction
has committed or aborted.
ORA-14451: unsupported feature with temporary table
Cause:
An attempt was made to create an IOT, specify physical attributes, specify
partition or parallel clause.
Action:
do not do that.
ORA-14452: attempt to create, alter or drop an
index on temporary table already in use
Cause:
An attempt was made to create, alter or drop an index on temporary table which
is already in use.
Action:
All the sessions using the session-specific temporary table have to truncate
table and all the transactions using transaction specific temporary table have
to end their transactions.
ORA-14453: attempt to use a LOB of a temporary
table, whose data has alreadybeen purged
Cause:
An attempt was made to use LOB from a temporary table whose data has been
dropped either because table was transaction-specific and transaction has
commited or aborted, table was truncated or session which created this LOB has
ended.
Action:
This LOB locator is invalid and cannot be used.
ORA-14454: attempt to reference temporary table in
a referential integrity constraint
Cause:
An attempt was made to reference temporary table in a referencial integrity
constraint. This is not supported.
Action:
Use triggers.
ORA-14455: attempt to create referential integrity
constraint on temporary table
Cause:
An attempt was made to create a referential integrity constraint on a temporary
table. This is not supported.
Action:
Use triggers.
ORA-14456: cannot rebuild index on a temporary
table
Cause:
An attempt was made to rebuild an index on a temp table.
Action:
The index data is anyway lost at end of session/transaction.
ORA-14457: disallowed Nested Table column in a
Temporary table
Cause:
An attempt made to create a Nested Table column in a temporary table. This is
not supported.
Action:
Do not specify these datatypes for temporary tables.
ORA-14458: attempt was made to create a temporary
table with INDEX organization
Cause:
An attempt was made to create an Index Organized Temporary table. This is not
supported.
Action:
Create the table with HEAP organization and the primary key.
ORA-14459: missing GLOBAL keyword
Cause:
keyword GLOBAL is missing while creating temporary table.
Action:
supply keyword.
ORA-14460: only one COMPRESS or NOCOMPRESS clause
may be specified
Cause:
COMPRESS was specified more than once, NOCOMPRESS was specified more than once,
or both COMPRESS and NOCOMPRESS were specified.
Action:
specify each desired COMPRESS or NOCOMPRESS clause option only once.
ORA-14461: cannot REUSE STORAGE on a temporary
table TRUNCATE
Cause:
REUSE STORAGE was specified with TRUNCATE on a temporary table. This is
unsupported as it is meaningless.
Action:
Specify DROP STORAGE instead (which is the default).
ORA-14462: cannot TRUNCATE temporary table in an autonomous
transaction which is already in use by the parent transaction
Cause:
An attempt was made to TRUNCATE a temporary table in an autonomous transaction
which is already in use by the parent transaction.
Action:
Make sure the temporary table is not being used by the parent transaction
before trying to TRUNCATE in an autonomous transaction.
ORA-14463: OPERATIONS keyword not specified
Cause:
OPERATIONS keyword was not specified in the Compression Clause.
Action:
specify OPERATIONS in the Compression Clause.
ORA-14464: Compression Type not specified
Cause:
Compression Type was not specified in the Compression Clause.
Action:
specify Compression Type in the Compression Clause.
ORA-14500: LOCAL option not valid without partition
name
Cause:
Incorrect syntax specified
Action:
Retry the command
ORA-14501: object is not partitioned
Cause:
Table or index is not partitioned. Invalid syntax.
Action:
Retry the command with correct syntax.
ORA-14503: only one partition name can be specified
Cause:
More than one partition name has been specified for analyze
Action:
Specify one partition name.
ORA-14504: syntax not supported for analyze
Cause:
A partition/subpartition number or bind variable has been used
Action:
Specify a valid partition/subpartition name.
ORA-14505: LOCAL option valid only for partitioned
indexes
Cause:
Incorrect syntax specified
Action:
Retry the command
ORA-14506: LOCAL option required for partitioned
indexes
Cause:
Incorrect syntax specified
Action:
Retry the command
ORA-14507: partition corrupt. all rows do not fall
within partition bounds
Cause:
The partition contains rows which should really be in some other partition.
Possibly due to an exchange partition without validation
Action:
Delete rows in partition which do not qualify
ORA-14508: specified VALIDATE INTO table not found
Cause:
The specified table either does not exist or user does not have the proper
privleges.
Action:
Specify the correct table to use.
ORA-14509: specified VALIDATE INTO table form
incorrect
Cause:
The specified table does not have the proper field definitions.
Action:
Specify the correct table to use. See utlvalid.sql for more information.
ORA-14510: can specify VALIDATE INTO clause only
for partitioned tables
Cause:
The VALIDATE INTO has been specified for a non partitioned table or cluster or
index.
Action:
Use syntax correctly
ORA-14511: cannot perform operation on a
partitioned object
Cause:
An attempt was made to perform an operation that is not allowed on partitioned
tables or indexes.
Action:
Retry the command with correct syntax.
ORA-14512: cannot perform operation on a clustered
object
Cause:
An attempt was made to perform an operation that is not allowed on clustered
tables or indexes.
Action:
Retry the command with correct syntax.
ORA-14513: partitioning column may not be of object
datatype
Cause:
Partitioning column specified by the user was an object datatype (object, REF,
nested table, array) which is illegal.
Action:
Ensure that no partitioning column is an object datatype.
ORA-14514: LOCAL option not valid without
subpartition name
Cause:
Incorrect syntax specified
Action:
Retry the command
ORA-14515: only one aubpartition name can be
specified
Cause:
More than one subpartition name has been specified for analyze
Action:
Specify one subpartition name.
ORA-14516: subpartition corrupt. all rows do not
fall within subpartition bounds
Cause:
The subpartition contains rows which should really be in some other
subpartition. Possibly due to an exchange subpartition without validation
Action:
Delete rows in subpartition which do not qualify
ORA-14517: subpartition of index 'string.string'
is in unusable state
Cause:
An attempt has been made to access an index subpartition that has been marked
unusable by a direct load or by a DDL operation
Action:
REBUILD the unusable index subpartition
ORA-14518: partition contains rows corresponding to
values being dropped
Cause:
table partition contains rows for the values being dropped.
Action:
DELETE all rows for the values being dropped and reissue statement
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]
Cause:
An attempt has been made to create a partitioned object in a manner that would
require the partitioned object to span tablespaces of more than one block size.
Action:
Ensure that all tablespaces specified in the DDL command for the given object
as well as any tablespaces implicitly assigned to partitions or subpartitions
of the object being created are all of the same block size.
ORA-14520: Tablespace string block size [string]
does not match existing object block size [string]
Cause:
A DDL statement was issued that would require a tablespace of a block size
different from the block size of the specified partitioned object to be
assigned either: (1) As the object's default tablespace (or one of the object's
partition-level default tablespaces, if composite partitioning is being used)
OR (2) To one of the object's partitions/subpartitions.
Action:
Specify a tablespace of the same block size as the partitioned object.
ORA-14521: Default tablespace string block
size [string] for string string does not match existing string
block size [string]
Cause:
A DDL statement was issued that would require creation of a new
partition/subpartition in the object-level default tablespace of an existing
partitioned object. However, the object-level default tablespace block size
does not match the block size of the partitioned object.
Action:
Either (1) Modify the default tablespace of the partitioned object to a
tablespace of the same block size as the object and then retry the DDL command,
OR (2) Ensure that tablespaces of the correct block size are specified for all
new partitions/subpartitions being created.
ORA-14522: Partition-level default tablespace string
block size [string] for string string does not match
existing string block size [string]
Cause:
A DDL statement was issued that would require creation of a new subpartition in
one of the partition-level default tablespaces of an existing composite
partitioned object. However, the partition-level default tablespace block size
does not match the block size of the partitioned object.
Action:
Either (1) Modify the partition-level default tablespace of the appropriate
partition of the partitioned object to a tablespace of the same block size as
the object and then retry the DDL command, OR (2) Ensure that tablespaces of
the correct block size are specified for all new subpartitions being created.
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]
Cause:
A DDL statement was issued that would require a partition/subpartition of a
local index/LOB column to be co-located with the corresponding
partition/subpartition of the base table. However, this is not possible because
the block sizes of the table and the LOB column/local index are different.
Action:
Either (1) Specify an object-level default tablespace (or partition-level
default tablespace for the appropriate partition, if composite partitioning is
used) for the partitioned local index/LOB column and then retry the DDL
command, OR (2) Ensure that tablespaces of the correct block size are specified
for all new partitions/subpartitions being created. Also ensure that neither of
TABLESPACE DEFAULT and STORE IN (DEFAULT) is specified for a local index whose
block size does not match that of the base table.
ORA-14530: row mismatches found in table string.string
and index string.string
Cause:
rows in table and index inconsistent
Action:
run complete analyze to determine corrupt rows
ORA-14551: cannot perform a DML operation inside a
query
Cause:
DML operation like insert, update, delete or select-for-update cannot be
performed inside a query or under a PDML slave.
Action:
Ensure that the offending DML operation is not performed or use an autonomous
transaction to perform the DML operation within the query or PDML slave.
ORA-14552: cannot perform a DDL, commit or rollback
inside a query or DML
Cause:
DDL operations like creation tables, views etc. and transaction control
statements such as commit/rollback cannot be performed inside a query or a DML
statement.
Action:
Ensure that the offending operation is not performed or use autonomous
transactions to perform the operation within the query/DML operation.
ORA-14553: cannot perform a lob write operation
inside a query
Cause:
A lob write operation cannot be performed inside a query or a PDML slave.
Action:
Ensure that the offending lob write operation is not performed or use an
autonomous transaction to perform the operation within the query or PDML slave.
No hay comentarios:
Publicar un comentario