ORA-13852: Tracing for service(module/action) string
is not enabled
Cause:
Attempt to disable a service-level tracing which was never enabled
Action:
Supply correct service(module/action) name
ORA-13853: Tracing for service (module/action) string
is already enabled
Cause:
Attempt to enable a service-level tracing which has been already enabled
Action:
Supply correct service(module/action), or disable and re-enable tracing with
different bind/wait options
ORA-13854: Tracing for service(module/action) string
on instance string is not enabled
Cause:
Attempt to disable a service-level tracing which was never explicitly enabled
on a specific instance
Action:
Supply correct service(module/action) name
ORA-13855: Tracing for service (module/action) string
on instance string is already enabled
Cause:
Attempt to enable a service-level tracing which has been already enabled on a
specific instance
Action:
Supply correct service(module/action), or disable and re-enable tracing with
different bind/wait options
ORA-13856: Service name must be specified
Cause:
Omitting service name while enabling/disabling tracing or aggregation
Action:
Supply the service name
ORA-13857: Invalid module name
Cause:
Module name is too long (exceeding 48 characters)
Action:
Supply correct name
ORA-13858: Invalid action name
Cause:
Action name is too long (exceeding 32 characters)
Action:
Supply correct name
ORA-13859: Action cannot be specified without the
module specification
Cause:
Action name is specified, but the module name is not
Action:
Supply the module name
ORA-13860: Invalid service name
Cause:
Service name is too long (exceeding 64 characters)
Action:
Supply correct name
ORA-13861: Statistics aggregation for client
identifier string is already enabled
Cause:
Attempt to enable a client identifier aggregation which has been already
enabled
Action:
Supply correct client identifier
ORA-13862: Statistics aggregation for client
identifier string is not enabled
Cause:
Attempt to disable a client identifier statistics aggregation which was never
enabled
Action:
Supply correct client identifier
ORA-13863: Statistics aggregation for service(module/action)
string is not enabled
Cause:
Attempt to disable a service-level statistics aggregation which was never
enabled
Action:
Supply correct service(module/action) name
ORA-13864: Statistics aggregation for service
(module/action) string is already enabled
Cause:
Attempt to enable a service-level statistics aggregation which has been already
enabled
Action:
Supply correct service(module/action)
ORA-13865: Module name must be specified
Cause:
Attempt to enable/disable a service-level statistics aggregation without a
module specification
Action:
Supply module name
ORA-13866: Client identifier must be specified
Cause:
Omitting client identifier while enabling/disabling tracing or aggregation
Action:
Supply the client identifier
ORA-13867: Database-wide SQL tracing is already
enabled
Cause:
Attempt to enable a database-level tracing which has been already enabled
Action:
Disable and re-enable tracing with different bind/wait options
ORA-13868: Instance-wide SQL tracing on instance string
is not enabled
Cause:
Attempt to disable a service-level tracing which was never explicitly enabled
on a specific instance
Action:
No action required
ORA-13869: Instance-wide SQL tracing on instance string
is already enabled
Cause:
Attempt to enable an instance-level tracing which has been already enabled on a
specific instance
Action:
Disable and re-enable tracing with different bind/wait options
ORA-13870: Database-wide SQL tracing is not enabled
Cause:
Attempt to disable a database-level tracing which was never enabled
Action:
No action required
ORA-13871: Invalid instance name
Cause:
Instance name is too long (exceeding 16 characters)
Action:
Supply correct name
ORA-13900: missing or invalid parameter string
Cause:
A call to SET_THRESHOLD procedure was either missing a parameter, or the
parameter was invalid.
Action:
Specify a valid value for this parameter.
ORA-13901: Object string was not found.
Cause:
An object name was passed to SET_THRESHOLD procedure that did not map to a
valid object.
Action:
Specify a valid object name.
ORA-13902: The specified file string is not
a data file.
Cause:
The object name was passed to a SET_THRESHOLD procedure that did not map to a
valid data file.
Action:
Specify a valid data file name.
ORA-13903: Invalid combination of string
threshold value and operator.
Cause:
A non-positive number was used for "Blocked User Session Count"
metrics while operator contains equal.
Action:
Use a positive number for the threshold value or use "greater than"
operator.
ORA-13904: The file has been dropped and recreated
during the procedure call.
Cause:
The file on which threshold is specified was dropped and recreated during the
procedure call.
Action:
Retry this operation.
ORA-13905: Critical or warning threshold have
incorrect values
Cause:
The tablespace threshold values can be in the range 0 to 100 only.
Action:
Check the threshold values
ORA-13906: The tablepace is not of the right type.
Cause:
An attempt was made to set a threshold on dictionary-managed tablespaces.
Action:
Check the tablespace type and reissue the command.
ORA-13907: Threshold value is invalid.
Cause:
An attempt was made to specify an invalid value for critical or warning
thresholds.
Action:
Use non-negative integers only for threshold values.
ORA-13908: Invalid combination of metrics id and
object type parameters.
Cause:
An attempt was made to specify an invalid combination of metrics id // and
object type parameters.
Action:
Specify a valid combination of metrics id and object type parameters.
ORA-13909: Invalid combination of threshold value
and operator.
Cause:
An attempt was made to specify an invalid combination of threshold value and
operator.
Action:
Check the operator and threshold values and reissue statement.
ORA-13910: Parameter string cannot be NULL.
Cause:
An attempt was made to call GET_THRESHOLD procedure without a required
parameter.
Action:
Specify a valid value for this parameter.
ORA-13911: Threshold not found
Cause:
The threshold did not exist with the specified threshold key.
Action:
No action required.
ORA-13912: Critical threshold value is less than
warning threshold value.
Cause:
An attempt was made to call SET_THRESHOLD procedure with the critical threshold
value less than the warning threshold value.
Action:
Check the threshold values and reissue the statement.
ORA-13913: The threshold cannot be set when SYSAUX
is offline.
Cause:
SET_THRESHOLD procedure was called when SYSAUX tablespace was offline.
Action:
Call SET_THRESHOLD procedure when SYSAUX is online.
ORA-13914: Threshold notification failed.
Cause:
An error occurred when sending notification for this threshold.
Action:
Make sure you have enough space on SYSAUX tablespace and retry this operation.
ORA-13915: Critical byte based free space threshold
value is greater than warning threshold value.
Cause:
An attempt was made to call SET_THRESHOLD procedure with the bytes based
critical threshold value greater than the warning threshold value.
Action:
Check the threshold values and reissue the statement.
ORA-13916: Invalid value "string"
specified for parameter "string"
Cause:
An invalid value was specified for the the given parameter.
Action:
Correct the value being specified for the parameter.
ORA-13917: Posting system alert with reason_id string
failed with code [string] [string]
Cause:
Connection to the database is dead, or invalid parameter to alert routine.
Action:
If this condition repeats, please contact Oracle Support.
ORA-13918: Updating system alert with reason_id string
failed; previous alert not found
Cause:
System Error: An attempt to update a system alert failed. The alert was
improperly cleared from WRI$_ALERT_OUTSTANDING.
Action:
Do not delete from WRI$_ALERT_OUTSTANDING. If this condition repeats, please
contact Oracle Support.
ORA-13919: Cannot specify values for parameter
"string" and for parameter "string"
Cause:
Can only specify a value for one or the other.
Action:
Pass just one of the parameters.
ORA-13920: Threshold cannot be set when database is
in read-only mode.
Cause:
SET_THRESHOLD procedure was called when database was open in read-only mode.
Action:
Call SET_THRESHOLD procedure when database is open in read/write mode.
ORA-13951: MMON sub-action time limit exceeded
Cause:
MMON sub-action did not complete within the system specified time frame.
Action:
None
ORA-13970: Invalid name of "string"
given
Cause:
Passed an invalid component, report, or transformation name to the framework.
Names must be alphanumeric and can contain the underscore (_) character.
Action:
Try again with a valid name
ORA-13971: string "string"
unknown
Cause:
Passed an unknown component, report, or transformation to the framework.
Action:
Give a different name
ORA-13972: string "string"
unknown for string "string"
Cause:
An object with the first name is unknown within the naming scope of the second
name
Action:
Change the parameters passed in or register the proper object
ORA-13973: string unknown for string
"string"
Cause:
An object is unknown within the given naming scope
Action:
Change the parameters passed in or register the proper object
ORA-13974: string with name "string"
already exists
Cause:
An object with the given name already exists
Action:
Give a different name
ORA-13975: string with name "string"
already exists for string "string"
Cause:
An object with the first name already exists within the naming scope of the
second name
Action:
Give a different name
ORA-13976: Improperly-formed report tag
Cause:
The top-level report tag was not built properly
Action:
Make sure that the report tag is built using the common tag library function
ORA-13977: Invalid content type
Cause:
An invalid content type was passed to the register format API
Action:
Correct your code to use the values in dbmsrep.sql
ORA-13978: Invalid reference string parameter or
value
Cause:
An invalid parameter/value was passed to a dbms_report API
Action:
Ensure that the parameter names and values are alphanumeric.
ORA-13979: Filename too long
Cause:
An invalid file name was passed to STORE_FILE
Action:
Ensure that the filename is less than 500 bytes
ORA-13980: Invalid file URL
Cause:
A URL with invalid syntax was provided, either directly to the function or via
an XML IMPORT or INCLUDE.
Action:
Check the URL.
ORA-13981: Invalid file URL or path prefix
Cause:
Either a URL or path prefix with invalid syntax was provided.
Action:
Check the URL
ORA-13982: Could not find file at URL provided
Cause:
The file requested could not be found in the given location.
Action:
Check the URL provided.
ORA-13983: Missing <body> tag from HTML
Cause:
An HTML document was passed to the function missing its <body> tag.
Action:
Check the HTML source.
ORA-13984: Invalid reference string
Cause:
The given reference string could not be parsed.
Action:
Check the reference string syntax.
ORA-13985: Invalid URL provided to servlet
Cause:
An invalid URL was provided to the servlet.
Action:
Check the URL.
ORA-13986: Error \string received from XPath
engine
Cause:
An error was received from the xpath library during an xpath operation.
Action:
Check xmlerr.h to understand the cause of the error.
ORA-13987: Invalid input to build common <string>
tag
Cause:
Invalid input was given when attempting to build a common tag.
Action:
Check the function input to make sure all necessary information is given.
ORA-13988: Invalid input given to variable argument
list report function.
Cause:
An invalid parameter was provided to one of the report framework variable
argument list functions.
Action:
Check the function input and try again.
ORA-13989: Invalid input given to structured
argument list report function.
Cause:
An invalid parameter was provided to one of the report framework structured
argument list functions.
Action:
Check the function input and try again.
ORA-13990: Invalid tag name given to common tag
callout function.
Cause:
This is an internal Server Manageability Error
Action:
Contact Oracle Support Services
ORA-14000: only one LOCAL clause may be specified
Cause:
CREATE INDEX statement contained more than one LOCAL clause
Action:
Specify LOCAL option at most once
ORA-14001: LOCAL clause contradicts previosly
specified GLOBAL clause
Cause:
CREATE INDEX statement contained a GLOBAL clause and a LOCAL clause
Action:
Specify LOCAL or GLOBAL clause, but not both
ORA-14002: only one GLOBAL clause may be specified
Cause:
CREATE INDEX statement contained more than one GLOBAL clause
Action:
Specify GLOBAL option at most once
ORA-14003: GLOBAL clause contradicts previosly
specified LOCAL clause
Cause:
CREATE INDEX statement contained a LOCAL clause and a GLOBAL clause
Action:
Specify GLOBAL or LOCAL clause, but not both
ORA-14004: missing PARTITION keyword
Cause:
keyword PARTITION missing
Action:
supply missing keyword
ORA-14005: missing RANGE keyword
Cause:
keyword RANGE missing
Action:
supply missing keyword
ORA-14006: invalid partition name
Cause:
a partition name of the form <identifier> is expected but not present.
Action:
enter an appropriate partition name.
ORA-14007: missing LESS keyword
Cause:
keyword LESS missing
Action:
supply missing keyword
ORA-14008: missing THAN keyword
Cause:
keyword THAN missing
Action:
supply missing keyword
ORA-14009: partition bound may not be specified for
a LOCAL index partition
Cause:
while parsing a CREATE INDEX statement to create a LOCAL partitioned index,
<partition-description> of one of partitions was found to contain VALUES
LESS THAN clause which is illegal since a LOCAL index inherits partition bounds
from its base table
Action:
remove all VALUES LESS THAN clauses from descriptions of LOCAL index partitions
ORA-14010: this physical attribute may not be
specified for an index partition
Cause:
unexpected option was encountered while parsing physical attributes of an index
partition; valid options for Range or Composite Range partitions are INITRANS,
MAXTRANS, TABLESPACE, STORAGE, PCTFREE; only TABLESPACE may be specified for
Hash partitions
Action:
remove invalid option(s) from the list of physical attributes of an index
partition
ORA-14011: names assigned to resulting partitions
must be distinct
Cause:
Names of partitions resulting from splitting of an existing table or index
partition are not distinct
Action:
rename resulting partition(s) to ensure that their names are distinct and
different from those of any other partition of the table or index
ORA-14012: resulting partition name conflicts with
that of an existing partition
Cause:
Name of a partition resulting from splitting of an existing table or index
partition is identical to that of some other existing partition of that table
or index
Action:
rename resulting partition(s) to ensure that their names are distinct and
different from those of any other partition of the table or index
ORA-14013: duplicate partition name
Cause:
Name of a partition of a table or index being created is not unique
Action:
rename partition(s) to ensure that their names are unique among partitions of
the table or index being created
ORA-14014: maximum number of partitioning columns
is 16
Cause:
number of columns in a partitioning column list exceeded the legal limit of 16
Action:
modify partitioning column list so that it consists of at most 16 columns
ORA-14015: too many partition descriptions
Cause:
CREATE TABLE or CREATE INDEX contained too many partition descriptions; maximum
number of partitions is 1048575 (1024K-1).
Action:
Reduce number of partitions to not exceed 1048575 (1024K -1).
ORA-14016: underlying table of a LOCAL partitioned
index must be partitioned
Cause:
User attempted to create a LOCAL partitioned index on a non-partitioned table
which is illegal. Only GLOBAL indices (partitioned or otherwise) may be created
on a non-partitioned table.
Action:
Correct the statement and reenter
ORA-14017: partition bound list contains too many
elements
Cause:
Partition bound list contained more elements than there are partitioning
columns
Action:
Ensure that the number of elements in partition bound list is equal to the
number of partitioning columns of the table or index
ORA-14018: partition bound list contains too few
elements
Cause:
Partition bound list contained fewer elements than there are partitioning
columns
Action:
Ensure that the number of elements in partition bound list is equal to the
number of partitioning columns of the table or index
ORA-14019: partition bound element must be one of:
string, datetime or interval literal, number, or MAXVALUE
Cause:
Partition bound list contained an element of invalid type (i.e. not a number,
non-empty string, datetime or interval literal, or MAXVALUE)
Action:
Ensure that all elements of partition bound list are of valid type
ORA-14020: this physical attribute may not be
specified for a table partition
Cause:
unexpected option was encountered while parsing physical attributes of a table
partition; valid options for Range or Composite Range partitions are INITRANS,
MAXTRANS, TABLESPACE, STORAGE, PCTFREE, and PCTUSED; only TABLESPACE may be
specified for Hash partitions
Action:
remove invalid option(s) from the list of physical attributes of a table
partition
ORA-14021: MAXVALUE must be specified for all columns
Cause:
In the VALUES LESS THAN clause for the highest (last) partition of a GLOBAL
index, MAXVALUE must be specified for all columns
Action:
Ensure that VALUES LESS THAN clause for the last partition of a GLOBAL index
has MAXVALUE specified for all columns
ORA-14022: creation of LOCAL partitioned cluster
indices is not supported
Cause:
An attempt was made to create a LOCAL partitioned cluster index, which is
currently illegal
Action:
Remove LOCAL along with <partition description>s, if any, from the CREATE
INDEX statement.
ORA-14023: creation of GLOBAL partitioned cluster
indices is not supported
Cause:
An attempt was made to create a GLOBAL partitioned cluster index, which is
currently illegal
Action:
Remove PARTITION BY RANGE clause along with <partition description>s from
the CREATE INDEX statement.
ORA-14024: number of partitions of LOCAL index must
equal that of the underlying table
Cause:
User attempted to create a LOCAL partitioned index with a number of partitions
which is different from that of the underlying table.
Action:
Correct the CREATE INDEX statement to specify a correct number of partitions
ORA-14025: PARTITION may not be specified for a
materialized view or a materialized view log
Cause:
PARTITION option was encountered while parsing a definition of a materialized
view or a materialized view log
Action:
Ensure that a definition of a MATERIALIZED VIEW does not include invalid
options
ORA-14026: PARTITION and CLUSTER clauses are
mutually exclusive
Cause:
definition of a table contained both PARTITION and CLUSTER clauses which is
illegal
Action:
Remove one of the conflicting clauses
ORA-14027: only one PARTITION clause may be
specified
Cause:
CREATE TABLE statement contained more than one PARTITION clause
Action:
Specify PARTITION option at most once
ORA-14028: missing AT or VALUES keyword
Cause:
keyword AT or VALUES missing
Action:
supply missing keyword
ORA-14029: GLOBAL partitioned index must be
prefixed
Cause:
partitioning columns of a global partitioned index must form a prefix of the
index' key columns
Action:
Ensure that the GLOBAL partitioned index being created is prefixed
ORA-14030: non-existent partitioning column in
CREATE TABLE statement
Cause:
Partitioning column specified in CREATE TABLE statement is not one of columns
of the table being created.
Action:
Ensure that all columns in the partitioning column list are columns of the
table being created.
ORA-14031: partitioning column may not be of type
LONG or LONG RAW
Cause:
Partitioning column specified by the user was of type LONG or LONG RAW, which
is illegal.
Action:
Ensure that no partitioning column is of type LONG or LONG RAW.
ORA-14032: partition bound of partition number string
is too high
Cause:
High bound of the partition whose number (partitions are numbered starting with
1) is displayed in this message did not collate lower than that of the
following partition, which is illegal.
Action:
Ensure that high bound of every partition (except for the last one) collates
lower than that of a following partition.
ORA-14036: partition bound value too large for
column
Cause:
Length of partition bound value is longer than that of the corresponding
partitioning column.
Action:
Ensure that lengths of high bound values do not exceed those of corresponding
partitioning columns
ORA-14037: partition bound of partition "string"
is too high
Cause:
High bound of the partition whose name (explicitly specified by the user) is
displayed in this message did not collate lower than that of the following
partition, which is illegal.
Action:
Ensure that high bound of every partition (except for the last one) collates
lower than that of a following partition.
ORA-14038: GLOBAL partitioned index must be
prefixed
Cause:
User attempted to create a GLOBAL non-prefixed partitioned index which is
illegal
Action:
If the user, indeed, desired to create a non-prefixed index, it must be created
as LOCAL; otherwise, correct the list of key and/or partitioning columns to
ensure that the index is prefixed
ORA-14039: partitioning columns must form a subset
of key columns of a UNIQUE index
Cause:
User attempted to create a UNIQUE partitioned index whose partitioning columns
do not form a subset of its key columns which is illegal
Action:
If the user, indeed, desired to create an index whose partitioning columns do
not form a subset of its key columns, it must be created as non-UNIQUE;
otherwise, correct the list of key and/or partitioning columns to ensure that
the index' partitioning columns form a subset of its key columns
ORA-14041: partition bound may not be specified for
resulting partitions
Cause:
while parsing an ALTER {TABLE|INDEX} SPLIT PARTITION statement,
<partition-description> of a resulting partition was found to contain
VALUES LESS THAN clause which is illegal
Action:
remove VALUES LESS THAN clause from the description(s) of partitions resulting
from splitting an existing table or index partition
ORA-14042: partition bound may not be specified for
a partition being moved, modified or rebuilt
Cause:
while parsing an ALTER {TABLE|INDEX} MODIFY PARTITION, ALTER TABLE MOVE
PARTITION, or ALTER INDEX REBUILD PARTITION statement, description of new
physical attributes of the partition being moved, modified, or rebuilt was
found to contain VALUES LESS THAN clause which is illegal
Action:
remove VALUES LESS THAN clause from the description of new attributes of the
partition being moved, modified, or rebuilt
ORA-14043: only one partition may be added
Cause:
ALTER TABLE ADD PARTITION contained descriptions of more than one partition to
be added
Action:
Ensure that the statement contains exactly one partition definition and that it
does not contain any commas
ORA-14044: only one partition may be moved
Cause:
ALTER TABLE MOVE PARTITION contained descriptions of more than one partition to
be moved
Action:
Ensure that the statement describes exactly one partition to be moved and that
it does not contain any commas
ORA-14045: only one partition may be modified
Cause:
ALTER TABLE|INDEX MODIFY PARTITION contained descriptions of more than one partition
to be modified
Action:
Ensure that the statement describes exactly one partition to be modified and
that it does not contain any commas
ORA-14046: a partition may be split into exactly
two new partitions
Cause:
ALTER TABLE|INDEX SPLIT PARTITION did not contain descriptions of exactly two
new partitions into which an existing table or index partition was to be split
Action:
Ensure that the statement describes exactly two partition into which an
existing partition is to be split
ORA-14047: ALTER TABLE|INDEX RENAME may not be
combined with other operations
Cause:
ALTER TABLE or ALTER INDEX statement attempted to combine a RENAME operation
with some other operation which is illegal
Action:
Ensure that RENAME operation is the sole operation specified in ALTER TABLE or
ALTER INDEX statement;
ORA-14048: a partition maintenance operation may
not be combined with other operations
Cause:
ALTER TABLE or ALTER INDEX statement attempted to combine a partition
maintenance operation (e.g. MOVE PARTITION) with some other operation (e.g. ADD
PARTITION or PCTFREE which is illegal
Action:
Ensure that a partition maintenance operation is the sole operation specified
in ALTER TABLE or ALTER INDEX statement; operations other than those dealing
with partitions, default attributes of partitioned tables/indices or specifying
that a table be renamed (ALTER TABLE RENAME) may be combined at will
ORA-14049: invalid ALTER TABLE MODIFY PARTITION
option
Cause:
An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, BACKUP,
ALLOCATE EXTENT, or DEALLOCATE UNUSED was specified in an ALTER TABLE MODIFY
PARTITION statement for a Range or Composite Range partition.
Action:
Specify only legal options.
ORA-14050: invalid ALTER INDEX MODIFY PARTITION
option
Cause:
An option other than INITRANS, MAXTRANS, STORAGE, or DEALLOCATE UNUSED was
specified in an ALTER INDEX MODIFY PARTITION statement.
Action:
Specify only legal options.
ORA-14051: invalid ALTER MATERIALIZED VIEW option
Cause:
An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or BACKUP
was specified in an ALTER MATERIALIZED VIEW statement.
Action:
Specify only legal options.
ORA-14052: partition-extended table name syntax is
disallowed in this context
Cause:
User attempted to use partition-extended table name syntax in illegal context
(i.e. not in FROM-clause or INSERT, DELETE, or UPDATE statement)
Action:
Avoid use of partition-extended table name in contexts other those mentioned
above.
No hay comentarios:
Publicar un comentario