ORA-32800: internal error string
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.
ORA-32801: invalid value string for string
Cause: An invalid value was specified for a parameter.
Action: Specify a valid value for the parameter.
ORA-32802: value for string must be string
Cause: An invalid value was specified for a parameter.
Action: Specify the value as indicated by the message.
ORA-32803: value for string cannot be altered
Cause: An attempt was made to alter a value that cannot be altered.
Action: Retry the operation without altering the indicated value.
ORA-32804: invalid value string, string should have form string
Cause: A value specified for a parameter has the incorrect form.
Action: Specify a string of the correct form.
ORA-32805: identifier for string too long, maximum length is string characters
Cause: An identifier string exceeded the maximum allowed length.
Action: Specify a string whose length is less than the maximum allowed length.
ORA-32806: value for string is too long, maximum length is string
Cause: A value exceeded it's maximum allowed length.
Action: Specify a value whose length is less than the maximum allowed length.
ORA-32807: message system link string already exists
Cause: A message system link of the specified name already exists.
Action: Specify a different name.
ORA-32808: message system link string does not exist
Cause: A message system link of the specified name does not exist.
Action: Specify a message system link name that already exists.
ORA-32809: foreign queue string is already registered
19-2 Oracle Database Error Messages
Cause: The foreign queue has already been registered for this message system link
(NAME@MSGLINK).
Action: Specify a different name that is not being used for this message system
link.
ORA-32810: foreign queue string is not registered
Cause: The foreign queue (NAME@MSGLINK) has not been registered for this
message system link.
Action: Specify the name of a registered foreign queue.
ORA-32811: subscriber string already exists
Cause: The specified subscriber identifier already exists.
Action: Specify a different identifier.
ORA-32812: subscriber string does not exist
Cause: The specified subscriber identifier does not exist.
Action: Specify an existing subscriber identifier.
ORA-32813: propagation schedule string already exists
Cause: The specified propagation schedule identifer already exists.
Action: Specify a different identifier.
ORA-32814: propagation schedule string does not exist
Cause: The specified propagation schedule identifier does not exist.
Action: Specify a schedule identifier that already exists.
ORA-32815: message system link string is referenced by a foreign queue
Cause: An attempt was made to remove a message system link currently
referenced by one or more registered foreign queues.
Action: Unregister all foreign queues using this message system link and retry the
operation.
ORA-32816: foreign queue string is referenced by a subscriber or schedule
Cause: An attempt was made to unregister a foreign queue currently referenced
by one or more subscribers or propagation schedules.
Action: Remove all subscribers and propagation schedules using this foreign
queue and retry the operation.
ORA-32817: message system link string is not configured with a log queue for
string
Cause: An attempt was made to add a propagation subscriber but the message
system link was not configured with a log queue for the indicated propagation
type.
Action: Alter the message system link to configure the link with a log queue for
this propagation type.
ORA-32818: AQ queue string does not exist
Cause: An operation was attempted where the specified AQ queue does not exist.
Action: Specify the name of an existing AQ queue.
ORA-32819: AQ queue string must be a normal queue
ORA-32800 to ORA-32857 19-3
Cause: An operation was attempted where the specified AQ queue exists but is
not a normal queue.
Action: Specify the name of an AQ queue which was created as a normal queue
(NORMAL_QUEUE).
ORA-32820: subscriber queue and exception queue must use same message system
link
Cause: An operation was attempted for INBOUND propagation where the
specified subscriber queue and exception queue reference different message
system links.
Action: Specify an exception queue that is a registered foreign queue of the same
message system link as the subscriber queue.
ORA-32821: subscriber queue and exception queue must have same payload type
Cause: An operation was attempted for OUTBOUND propagation where the AQ
queues used for the subscriber queue and exception queue have different payload
types.
Action: Specify an exception queue that has the same payload type as the
subscriber queue.
ORA-32822: subscriber string is marked for removal
Cause: An administration operation was attempted for a subscriber which is
marked for removal. If attempting to remove a subscriber, the Messaging Gateway
agent is not running or is running but unable to remove the subscriber at this time.
Action: Do not issue propagation administration commands for a subscriber for
which removal is pending. Wait for the subscriber to be removed by the agent or
issue REMOVE_SUBSCRIBER with the FORCE option to force the subscriber to be
removed.
ORA-32823: subscriber exists for queue string and destination string
Cause: An attempt was made to create a propagation subscriber when one
already exists for the specified queue and destination pair.
Action: Specify a different queue and destination pair, or remove the subscriber
using that pair and retry the operation.
ORA-32824: schedule exists for source string and destination string
Cause: An attempt was made to create a propagation schedule when one already
exists for the specified source and destination pair.
Action: Specify a different source and destination pair, or remove the schedule
using that pair and retry the operation.
ORA-32825: Messaging Gateway agent has not been started
Cause: An attempt was made to shut down the Messaging Gateway agent when it
is not started.
Action: No action required.
ORA-32826: Messaging Gateway agent has already been started
Cause: An attempt was made to start the Messaging Gateway agent when it is
already started.
Action: No action required.
ORA-32827: Messaging Gateway agent must be shut down
19-4 Oracle Database Error Messages
Cause: An operation was attempted that requires the Messaging Gateway agent
to be shut down.
Action: Issue SHUTDOWN, wait for MGW_GATEWAY view to show a NOT_
STARTED status, and retry the operation. CLEANUP_GATEWAY may need to be
issued to reset the gateway state if the agent fails to shut down after a reasonable
time period.
ORA-32828: Messaging Gateway agent must be running
Cause: An operation was attempted that requires the Messaging Gateway agent
to be started and responsive.
Action: Issue STARTUP, wait for MGW_GATEWAY view to show a RUNNING
status, and retry the operation.
ORA-32829: Messaging Gateway agent cannot be shut down while it is starting
Cause: An attempt was made to shut down the Messaging Gateway agent when it
is in the process of starting and initializing.
Action: Wait for MGW_GATEWAY view to show a RUNNING status and retry
the operation. CLEANUP_GATEWAY may need to be issued to reset the gateway
state if the agent fails to start after a reasonable time period.
ORA-32830: result code string returned by Messaging Gateway agent
Cause: The Messaging Gateway agent terminated abnormally due to an
unexpected error.
Action: Review the Messaging Gateway log file for further information regarding
the problem. Resolve the problem and start the Messaging Gateway agent. Contact
Oracle Support Services if the problem cannot be resolved.
ORA-32831: timed out trying to acquire administration lock
Cause: A timeout occurred when attempting an administration operation. Either
an administration operation was attempted while the Messaging Gateway agent
was starting and initializing, or two administration operations were attempted at
the same time.
Action: Retry the operation. If the Messaging Gateway agent is starting, wait for
MGW_GATEWAY view to show a RUNNING status and retry the operation.
ORA-32832: failure string trying to acquire administration lock
Cause: An unexpected error occurred trying to acquire administration lock.
Action: Retry the operation. Contact Oracle Support Services if the error persists.
ORA-32833: failure string trying to release administration lock
Cause: An unexpected error occurred trying to release administration lock.
Action: Contact Oracle Support Services if the error persists.
ORA-32834: Messaging Gateway agent user has not been set
Cause: A Messaging Gateway agent user has not been configured.
Action: Create a database user having role MGW_AGENT_ROLE and issue DB_
CONNECT_INFO to configure an agent user.
ORA-32835: database user string does not exist
Cause: The specified database user does not currently exist.
Action: Create the user and grant all necessary privileges and roles.
ORA-32800 to ORA-32857 19-5
ORA-32836: database user string must be granted role string
Cause: The specified database user does not have a required role.
Action: Grant the user the indicated role.
ORA-32837: invalid configuration state string
Cause: The specified configuration state is invalid.
Action: Remove and re-create the configured entities. Contact Oracle Support
Services if the problem cannot be identified or resolved.
ORA-32838: exceeded maximum number of properties
Cause: An attempt was made to alter a property list where the number of
properties in the resulting list exceeds the maximum allowed.
Action: Order the elements of the alter list differently so the number of elements
in the resulting list is less than the maximum.
ORA-32839: property string is reserved, names with MGWPROP$_ prefix are not
valid
Cause: An attempt was made to specify a reserved name for a property name.
Action: Use a non-reserved name.
ORA-32840: property name cannot be NULL
Cause: An attempt was made to use NULL for a property name.
Action: Specify a non-NULL name.
ORA-32841: invalid value for property string
Cause: An attempt was made to specify an invalid value for a property.
Action: Specify a valid property value.
ORA-32842: value for property string cannot be altered
Cause: An attempt was made to alter a property that cannot be altered.
Action: Retry the operation without altering the indicated property.
ORA-32843: value for string is outside the valid range of string to string
Cause: A value was specified that is not in the valid range.
Action: Specify a value within the indicated range.
ORA-32844: exceeded maximum number of string values
Cause: An attempt was made to add a value of the specified type but the
maximum number of such values has been reached.
Action: No action required.
ORA-32845: Messaging Gateway agent is already running
Cause: An attempt was made to start the Messaging Gateway agent when an
agent instance is already running.
Action: Shut down the Messaging Gateway agent currently running, verify the
agent process has been terminated, and start the Messaging Gateway agent.
ORA-32846: Messaging Gateway agent cannot be started; status is string
Cause: An attempt to start the Messaging Gateway agent failed due to the
indicated agent status. A BROKEN status indicates a problem that requires user
intervention before the agent can be started.
19-6 Oracle Database Error Messages
Action: Review the MGW_GATEWAY view and the Messaging Gateway log file
for further information. Resolve the problem and start the Messaging Gateway
agent. Contact Oracle Support Services if the problem cannot be resolved.
ORA-32847: operation is not supported on this platform
Cause: An attempt was made to perform an operation that is not supported on
this platform.
Action: Switch to a platform on which the operation is supported.
ORA-32848: foreign queue DOMAIN required for JMS unified connections
Cause: A DOMAIN was not specified when registering a foreign queue for a
messaging system link that is configured to use the JMS unified messaging model.
Action: Specify a non-NULL value for the DOMAIN parameter.
ORA-32849: string cannot be set unless string is set
Cause: An attempt was made to specify a value for a parameter that cannot be set
unless an associated parameter is also set.
Action: Specify a valid value for both parameters, or, do not specify a value for
either parameter.
ORA-32850: agent string does not exist
Cause: The specified Messaging Gateway agent name did not exist.
Action: Specify an existing agent name.
ORA-32851: agent string already exists
Cause: The specified Messaging Gateway agent name already existed.
Action: Specify a different agent name.
ORA-32852: agent string is referenced by a message system link
Cause: An attempt was made to remove a Messaging Gateway agent currently
referenced by one or more message system links.
Action: Remove all message system links associated with this agent and retry the
operation.
ORA-32853: propagation job string does not exist
Cause: The specified propagation job identifier did not exist.
Action: Specify an existing identifier.
ORA-32854: propagation job string already exists
Cause: The specified propagation job identifier already existed.
Action: Specify a different identifier.
ORA-32855: propagation job string is marked for removal
Cause: An administration operation was attempted for a propagation job which is
marked for removal. If attempting to remove a job, the Messaging Gateway agent
is not running or is running but unable to remove the job at this time.
Action: Do not issue propagation administration commands for a job for which
removal is pending. Wait for the job to be removed by the agent, or, issue
REMOVE_JOB with the FORCE option to force the job to be removed.
ORA-32856: operation not supported for propagation job
ORA-32800 to ORA-32857 19-7
Cause: An attempt was made to perform an operation that was not supported for
a propagation job.
Action: Perform the operation using a propagation job procedure.
ORA-32857: propagation job exists for source string and destination string
Cause: An attempt was made to create a propagation job, subscriber, or schedule
when a propagation job already existed for the specified source and destination
pair.
Action: Specify a different source and destination pair, or remove the propagation
job using that pair and retry the operation.
19-8 Oracle Database Error Messages
20
ORA-33000 to ORA-37999 0 2
ORA-33000: (AGOPEN00) AGGMAP workspace object cannot be accessed because
it was compiled by a more recent version of string.
Cause: The AGGMAP was already compiled by a more recent version of the
product than was being used to execute this command.
Action: Recompile the AGGMAP in the current version.
ORA-33002: (XSAGDNGL00) In AGGMAP workspace object, the FLOOR argument
of number must be less than the CEILING argument of number.
Cause: The user specified a floor argument greater than the ceiling argument.
Action: Adjust the floor and ceiling arguments so that the floor is less than the
ceiling. OBSOLETE, please remove this
ORA-33003: (XSAGDIMDROP) workspace object, to be transformed during data
load, must be a base dimension and not otherwise referenced in the AGGMAP.
Cause: The user tried to specify a dimension in a dataflow-related clause in an
aggmap which is already in another RELATION statement, DIMENSION
statement, or possibly dimensioning the AGGMAP, or they specified a composite
or conjoint dimension, or an object which is not a dimension
Action: Remove the conflicting reference or specify a valid object
ORA-33004: (XSAGDNGL01) workspace object is not a relationship array.
Cause: A RELATION clause in the AGGMAP named a workspace object that is
not a relation.
Action: Name a valid self-relation in the RELATION statement.
ORA-33005: (XSAGDIMBREAK) Invalid breakout for dimension workspace object.
Cause: The user specified something that was not a valid dimension or relation on
a BREAKOUTDIM line in an aggmap. This might be because the object was not a
valid relation, was not over the specified dimension or was multidimensional
Action: Use a valid relation instead
ORA-33006: (XSAGDNGL02) The relation workspace object is not related to itself.
Cause: A relation was named in a RELATION clause of the AGGMAP that is not a
self-relation.
Action: Name a valid self-relation in the RELATION statement.
ORA-33008: (XSAGDNGL03) The relation workspace object is not a relation over a
base dimension of AGGMAP workspace object.
20-2 Oracle Database Error Messages
Cause: A relation was named in a RELATION clause of the AGGMAP that is not a
relation for a base dimension of the AGGMAP.
Action: Name a valid self-relation in the RELATION statement, that is, one that
has a dimension that dimensions the AGGMAP.
ORA-33009: (XSAGDNGLPREC) In AGGMAP workspace object, PRECOMPUTE
may only be specified either for the entire AGGMAP or for individual
RELATION statements.
Cause: PRECOMPUTE was specified both as a line in the AGGMAP and on at
least one of the RELATION lines, or it was specified more than once as a line of the
AGGMAP.
Action: Remove either the PRECOMPUTE line, or the PRECOMPUTE
specification for all of the RELATION lines.
ORA-33010: (XSAGDNGL04) Relation workspace object is duplicated in the
AGGMAP workspace object.
Cause: Two RELATION statements in the AGGMAP reference the same relation
object.
Action: Remove the duplicate RELATION statement.
ORA-33012: (XSAGDNGL05) AGGMAP workspace object contains invalid syntax.
Cause: A line in the AGGMAP contains invalid syntax.
Action: Change the line to have valid syntax.
ORA-33014: (XSAGDNGL06) In AGGMAP workspace object, variable operator
workspace object cannot be dimensioned by rollup dimension workspace object.
Cause: Operator variables cannot have the rollup dimension as one of their base
dimensions.
Action: Modify the definition of the operator variable so that the current rollup
dimension is not one of its bases.
ORA-33016: (XSAGDNGL07) In AGGMAP workspace object, workspace object is
not a valid operator or variable name.
Cause: An invalid argument was supplied to the OPERATOR clause in the
relation statement.
Action: Fix the OPERATOR clause so that it specifies either a valid variable name
or a valid operator.
ORA-33018: (XSAGDNGL08) In AGGMAP workspace object, the data type of
workspace object must be TEXT, not string.
Cause: An operator variable was supplied whose data type is not TEXT.
Action: Change the operator clause to reference a TEXT variable.
ORA-33022: (XSAGDNGL10) The measure dimension workspace object must be a
TEXT or ID base dimension that does not dimension AGGMAP workspace
object, but is in the same analytic workspace.
Cause: A MEASUREDIM was supplied in the AGGMAP that was not acceptable.
Action: Modify the MEASUREDIM clause to specify a valid dimension.
ORA-33024: (XSAGDNGL11) AGGMAP workspace object contains duplicate
information.
Cause: The aggmap contains multiple instances of a clause that can only be
specified once.
ORA-33000 to ORA-37999 20-3
Action: Remove the extra clause.
ORA-33026: (XSAGDNGL12) In AGGMAP workspace object, workspace object is
not a valid valueset.
Cause: A line in the AGGMAP contains an invalid element where a valid valueset
is required.
Action: Change the line to have a valid valueset.
ORA-33028: (XSAGDNGL13) In AGGMAP workspace object, workspace object
should be scalar, not a dimensioned valueset.
Cause: A line in the AGGMAP contains a dimensioned valueset where a scalared
valueset is required.
Action: Change the line to have a scalar valueset.
ORA-33030: (XSAGDNGL14) In AGGMAP workspace object, you can have either a
single independent PROTECT statement or PROTECT statements in your
RELATION statements.
Cause: The AGGMAP either specified multiple PROTECT statements not on a
RELATION line, or specified PROTECT statements both independently and on
RELATION lines.
Action: Correct the AGGMAP to have valid syntax.
ORA-33032: (XSAGDNGL15) In AGGMAP workspace object, VALUESET
workspace object must be in extra dimensions of the relation.
Cause: The RELATION phrase contains a VALUESET which is not over the extra
dimension of the RELATION.
Action: Correct the RELATION phrase to contain a valueset over the extra
dimension or not to contain any valueset.
ORA-33034: (XSAGDNGL16) In AGGMAP workspace object, VALUESET
workspace object in PRECOMPUTE phrase must be in the self dimension of the
relation.
Cause: The precompute phrase contains a valueset which is not over the self
dimension of the relation.
Action: Correct the relation phrase to contain a valueset over the self dimension
or not to contain any valueset.
ORA-33036: (XSAGDNGL17) ARGS option workspace object must be a TEXT
variable.
Cause: An ARGS value had a non-text data type.
Action: Use a text variable for ARGS.
ORA-33038: (XSAGDNGL18) In AGGMAP workspace object, RELATION
workspace object contains hierarchy dimensions that are also dimensions of the
AGGMAP.
Cause: Hierarchy dimensions(extra dimensions) of a RELATION in the AGGMAP
are base dimensions of the AGGMAP.
Action: Correct the RELATION not to have hierarchy dimensions(extra
dimensions) which are also base dimensions of the AGGMAP.
ORA-33040: (XSAGDNGL19) In AGGMAP workspace object, VALUESETS
workspace object and workspace object are both over the same hierarchy
dimension.
20-4 Oracle Database Error Messages
Cause: Two or more different VALUESETs over the same hierarchy dimension are
used in the AGGMAP.
Action: Use the same VALUESET for two RELATION phrases or use two different
VALUESETs over two different hierachy dimensions.
ORA-33042: (XSAGDNGL20) In AGGMAP workspace object, VALUESET
workspace object must qualify all relations dimensioned by workspace object.
Cause: A VALUESET over a hierarchy dimension qualifies some RELATIONs but
not all RELATIONs dimensioned by the same hierarchy dimension.
Action: Use the same VALUESET to qualify all the RELATIONs dimensioned by
the same hierarchy dimension.
ORA-33044: (XSAGDNGL21) AGGREGATE operator string requires a WEIGHTBY
clause, but the ARGS clause in AGGMAP workspace object did not specify one.
Cause: The user used an operator which needs weight values but not provided
the weight values.
Action: Provide weight values using a WEIGHTBY cluase.
ORA-33045: (XSAGDNGL51) The AGGREGATE operator string does not require a
weight, but ARGS clause in AGGMAP workspace object specified workspace
object as a weight.
Cause: The ARGS variable specified a weight even though one is not needed.
Action: Modify the ARGS variable so that it does not specify a weight for that
operation.
ORA-33046: (XSAGDNGL22) In AGGMAP workspace object, you can specify only
one SCREENBY clause.
Cause: The AGGMAP contained multiple SCREENBY clauses.
Action: Remove one of the SCREENBY clauses from the AGGMAP.
ORA-33048: (XSAGDNGL23) In AGGMAP workspace object, the relation
workspace object and the relation workspace object are both over the same base
dimension.
Cause: The AGGMAP contains incompatible RELATION statements.
Action: Remove one of the RELATION statements from the AGGMAP.
ORA-33050: (XSAGDNGL24) AGGMAP workspace object cannot be used to
aggregate workspace object, because it is defined in a different analytic
workspace.
Cause: The user attempted to aggregate a variable in another analytic workspace.
Action: Create an AGGMAP in the other analytic workspace to aggregate that
variable.
ORA-33052: (XSAGDNGL25) AGGMAP workspace object is a dimensioned
AGGMAP; it can only be used to aggregate like-dimensioned variables.
Cause: The user attempted to aggregate a variable with different dimensions than
the AGGMAP. This is only possible with undimensioned AGGMAPs.
Action: Create a new undimensioned AGGMAP.
ORA-33058: (XSAGDNGL28) In AGGMAP workspace object, error code string is
greater than the maximum error code of number.
Cause: The user specified an invalid ERRORMASK value.
ORA-33000 to ORA-37999 20-5
Action: Remove the invalid value from the ERRORMASK list.
ORA-33060: (XSAGDNGL29) In AGGMAP workspace object, the value for the
ERRORLOG MAX option must be greater than 0.
Cause: The user specified an ERRORLOG MAX of 0 or a negative number.
Action: Adjust the AGGMAP so that it uses a positive number.
ORA-33062: (XSAGDNGL30) In ALLOCMAP workspace object, WEIGHTBY
option workspace object must be a numerical VARIABLE or FORMULA.
Cause: The WEIGHTBY clause requires numerical VARIABLE or FORMULA but
the user used invalid objects.
Action: Correct the WEIGHTBY cluase to use a valid numerical VARIABLE or
FORMULA.
ORA-33064: (XSAGDNGL31) In AGGMAP workspace object, the hierarchy
dimension QDR workspace object cannot refer to the related dimension of the
relation.
Cause: The user specified an invalid hierarchy dimension qualified data reference.
Action: Adjust the AGGMAP so that it uses a valid dimension value qualified
data reference.
ORA-33066: (XSAGDNGL32) In AGGMAP workspace object, the hierarchy
dimension QDR workspace object must be a hierarchy dimension of the
relation.
Cause: The user specified an invalid qualified data reference for the hierarchy
dimension.
Action: Adjust the AGGMAP so that it uses a valid dimension value qualified
data reference.
ORA-33068: (XSAGDNGL33) In AGGMAP workspace object, the hierarchy
dimension QDR over dimension workspace object must specify a positive
dimension offset.
Cause: The user specified an invalid qualified data reference for the hierarchy
dimension.
Action: Adjust the AGGMAP so that it uses a valid dimension value qualified
data reference.
ORA-33070: (XSAGDNGL34) In AGGMAP workspace object, all QDRs of
dimension workspace object must map to the same dimension position.
Cause: The user specified two conflicting hierarchy dimension qualified data
references.
Action: Adjust the AGGMAP so that it uses a consistent qualified data reference.
ORA-33072: (XSAGDNGL35) In AGGMAP workspace object, the hierarchy
dimension QDR over dimension workspace object must be specified for every
relation dimensioned by that hierarchy dimension.
Cause: Multiple dimensions share the same hierarchy dimension, but it is only
qualified within a subset of the AGGMAP relations.
Action: Adjust the AGGMAP so that it uses consistent qualified data references.
ORA-33074: (XSAGDNGL36) In AGGMAP workspace object, the offset number is
not a valid offset into dimension workspace object.
Cause: The hierarchy dimension offset is an invalid dimension position.
20-6 Oracle Database Error Messages
Action: Adjust the AGGMAP so that it uses valid qualified data references.
ORA-33076: (XSAGDNGL37) In AGGMAP workspace object, the value 'number' is
not a valid value of dimension workspace object.
Cause: The hierarchy dimension offset is an invalid dimension position.
Action: Adjust the AGGMAP so that it uses valid qualified data references.
ORA-33078: (XSAGDNGL39) In AGGMAP workspace object, the hierarchy
dimension QDR workspace object must refer to a dimension.
Cause: The user specified an invalid qualified data reference for the hierarchy
dimension.
Action: Adjust the AGGMAP so that it uses a valid dimension value qualified
data reference.
ORA-33080: (XSAGDNGL40) In AGGMAP workspace object, you cannot reference
dimension workspace object with both a RELATION statement and a
DIMENSION statement.
Cause: The user included both RELATION and DIMENSION statements in the
AGGMAP referring to the same AGGMAP.
Action: Remove one of the conflicting clauses.
ORA-33082: (XSAGDNGL41) In AGGMAP workspace object, the non-dimensioned
valueset workspace object must have a parent QDR in its VALUESET statement
over the VALUESET's base dimension.
Cause: The VALUESET statement specified a scalar valueset but did not include a
qualified data reference to specify the parent.
Action: Add a qualified data reference specifying the parent to the VALUESET
statement.
ORA-33084: (XSAGDNGL42) In AGGMAP workspace object, you cannot qualify
the dimensioned valueset workspace object.
Cause: The VALUESET line referred to a dimensioned valueset.
Action: Use a non-dimensioned valueset to limit the status of the dimensioned
one.
ORA-33086: (XSAGINIT01) AGGMAP workspace object cannot be dimensioned by
a conjoint dimension.
Cause: The specified AGGMAP was dimensioned by a conjoint dimension.
Action: Use the CHGDFN command to change the conjoint to a composite
dimension.
ORA-33092: (XSAGCOMP04) number is not the name of a MODEL in any attached
analytic workspace.
Cause: An invalid model name was attached to an AGGMAP.
Action: Remove the model from the AGGMAP or create a model with that name.
ORA-33094: (XSAGGMAPLIST01) Your expression uses too much execution space.
Eliminate recursion or reduce the levels of nesting.
Cause: formulas likely refer to each other recursively or with a great deal of
depth.
Action: eliminate recursion and flatten formula trees.
ORA-33000 to ORA-37999 20-7
ORA-33098: (APABBR01) A value of '%V' is not valid for the workspace object
option.
Cause: An inappropriate value was specified for the named option.
Action: Set a legal value for the option.
ORA-33100: (APABBR02) Value 'number' is not valid for the workspace object
option.
Cause: An inappropriate value was specified for the named option.
Action: Set a legal value for the option.
ORA-33141: (XSAWFREEZE1) The analytic workspace string is already frozen.
Cause: Attempting to freeze an AW when it is already frozen
Action: Thaw the AW before freezing it again.
ORA-33143: (XSAWFREEZE2) The analytic workspace string must be attached RW
or RX.
Cause: The AW must be updatable to change the freeze state
Action: Reattach AW before freezing or thawing it again.
ORA-33145: (XSAWFREEZE3) Cannot rollback analytic workspace string;
generations are in use.
Cause: One or more generations due to be destroyed as part of a rollback to freeze
command are currently in use.
Action: Get sessions using those generations to detach the AW.
ORA-33147: (XSAWFREEZE4) The analytic workspace string is not frozen.
Cause: You are attempting to "rollback to freeze" an AW that is not frozen.
Action: Only execute this command on a frozen AW.
ORA-33213: (CINSERT06) The target position for MAINTAIN ADD or MAINTAIN
MOVE cannot fall in the range of session-only values.
Cause: The user specified a BEFORE or AFTER clause specifying a position in the
range of SESSION dimension values.
Action: Do not use a position clause, or specify a position before the first
SESSION value.
ORA-33214: (CINSERT02) The workspace object dimension is too large.
Cause: The dimension has too many values.
Action: Deleted values can still take up space in the dimension and cause this
error. Try removing the deleted values by exporting the dimension to EIF and
reimporting it with the REPLACE DELETE option.
ORA-33215: (CINSERT07) You cannot add session-only values to the workspace
object dimension.
Cause: The user tried to add a SESSION dimension value while a spreadsheet
spreadsheet cursor was open.
Action: Try adding the SESSION value while the cursor is not active.
ORA-33217: (CINSERT20) Custom member values cannot be added to concat
dimension workspace object, or to any of its bases, because it is not defined as
UNIQUE.
Cause: Only UNIQUE concat dimensions can have custom member values.
20-8 Oracle Database Error Messages
Action: Use the CHGDFN command to change the concat dimension to UNIQUE
and retry.
ORA-33218: (CINSERT04) %K is not a valid value for the workspace object
dimension. Values for this dimension can have at most number significant digits
after rounding to number decimal places.
Cause: The user attempted to insert a value that had too many digits into a
NUMBER dimension. For instance, the user might have tried to insert the value
99999 (5 digits) into a dimension with data type NUMBER(4).
Action: Use a smaller number for the dimension value, or define a new dimension
with a larger precision and replace the old dimension with the new one.
ORA-33219: (CINSERT05) %K cannot be added to workspace object because it is
already a value of the dependent UNIQUE concat dimension workspace object,
from leaf dimension workspace object.
Cause: A value cannot be added to a dimension if it conflicts with an existing
value in a unique concat dimension containing this dimension.
Action: The concat(s) causing the conflict could be CHGDFNed to NOT UNIQUE,
or either of the duplicate values could be renamed to make them UNIQUE.
ORA-33223: (CMOVE03) You cannot move a session-only dimension value.
Cause: The user named a SESSION dimension value in the MAINTAIN MOVE
command.
Action: Do not try to MAINTAIN MOVE session-only dimension values.
ORA-33247: (CRENAME03) %K is already a value of the dependent UNIQUE
concat dimension workspace object, from leaf dimension workspace object.
Cause: A value cannot be renamed in a dimension if the new value conflicts with
an existing value in a unique concat dimension containing this dimension.
Action: The concat(s) causing the conflict could be CHGDFNed to NOT UNIQUE,
or either of the duplicate values could be changed to make them UNIQUE.
ORA-33260: (DIMSHOW01) Partition number does not exist.
Cause: The DIMSHOW command specified a nonexistent partition.
Action: Specify the name of an existing partition, or remove the PARTITION
qualification from the DIMSHOW command.
ORA-33261: (DIMSHOW02) A partition name may be specified only for a
partitioned variable.
Cause: A PARTITION qualification was provided for an object other than a
partitioned variable.
Action: Remove the PARTITION qualification.
ORA-33262: (DBERR01) Analytic workspace string does not exist.
Cause: The analytic workspace requested does not seem to be in the current
database
Action: Check that you are in the correct schema and have access to the requested
AW.
ORA-33263: Could not create analytic workspace string
Cause: A serious error was encountered while trying to set up the tables for the
named analytic workspace. Possibilities include a tablespace that can't be written
ORA-33000 to ORA-37999 20-9
to, corrupted metadata about which AWs exist, bogus tables with names the code
expects to be able to use, or the remains of a partially removed AW.
Action: There should be another error on the error stack. Consult it to determine
what is causing the problem and remove that table.
ORA-33265: (DBERRBSZ) Analytic workspace string cannot be opened. Tablespace
blocksize number does not match database cache size number.
Cause: The blocksize of the containing tablespace didn't match database cache
size.
Action: Change either size to make them consistent, or set olap_page_pool_size to
0 to allow automatic OLAP pool management when compatibility is greater than
10.2.
ORA-33267: (DBERRRLS) Analytic workspace string cannot be accessed because it
has fine-grained access control applied to it
Cause: An attempt was made to access the specified analytic workspace's LOB
table. The OLAP option detected the table had fine-grained security applied to it.
The OLAP option requires full access to this table to operate correctly.
Action: Remove the fine-grained access control.
ORA-33268: (DBERRTHW) Analytic workspace string cannot be attached with the
THAW option because it was frozen with the NOTHAW option
Cause: An attempt to attach the AW using the thaw option was made; the AW
was frozen using the NOTHAW option.
Action: Either attempt the command again without the THAW option.
ORA-33269: while operating on 'string'
Cause: Error is raised to inform user what object was being worked on when an
error occurred during the creation of an AW. It should always be signaled with
33263
Action: See error#33263
ORA-33270: (DBERR05) Analytic workspace string already exists.
Cause: The AW CREATE command was passed the name of an analytic
workspace that already exists
Action: Specify a different name.
ORA-33271: simulated paging error
Cause: This is an internal error that should never be seen
Action: Contact Oracle technical support
ORA-33273: (XSCHKRLS01) Analytic workspace string has open cursors and cannot
be detached.
Cause: A session attempted to detach an analytic workspace while there are
cursors open against it.
Action: Close the open cursor before attempting to close the analytic workspace.
ORA-33274: (DBERR07) Timed out while trying to lock analytic workspace string
for string.
Cause: A lock operation that was supposed to happen very quickly was taking
too long. It can be due to another session being stopped while holding that lock,
another session crashing while holding that lock, or an internal error.
20-10 Oracle Database Error Messages
Action: If another session is stopped, resume that session to let it release the lock.
If another session has crashed, wait for a few minutes while PMON or SMON
process is recovering that lock. Contact Oracle OLAP Support if none of the
situations above apply.
ORA-33275: Autonomous transaction query of an UPDATEd analytic workspace is
not supported
Cause: The user made attempt to reference an anayltic workspace that has
uncommited updates within an autonomous query.
Action: Either COMMIT or ROLLBACK your uncommited changes, or don't use
an autonomous transaction.
ORA-33278: (DBERR09) Analytic workspace string cannot be attached in RW or
EXCLUSIVE mode until the changes made and updated in MULTI mode are
committed or rolled back.
Cause: There are still changes to this analytic workspace that were updated and
not committed when the workspace was attached in MULTI mode.
Action: Either try attaching the workspace is RO or MULTI mode or commit or
roll back the transaction before trying to attach the workspace in RW or
EXCLUSIVE mode.
ORA-33280: (DBERR10) Analytic workspace string cannot be attached in MULTI
mode until the changes made and updated in RW or EXCLUSIVE mode are
committed or rolled back.
Cause: There are still changes to this analytic workspace that were updated and
not committed when the workspace was attached in RW or EXCLUSIVE mode.
Action: Either try attaching the workspace is RO, RW, or EXCLUSIVE mode or
commit or roll back the transaction before trying to attach the workspace in
MULTI mode.
ORA-33282: (DBERR11) Cannot wait for analytic workspace string to become
available since doing so would cause a deadlock.
Cause: Trying to wait for the workspace to become available caused a deadlock.
Action: Release an analytic workspace that some other user might be waiting for
before proceeding to attach this analytic workspace in this mode.
ORA-33284: (DBERR12) Analytic workspace string cannot be opened in MULTI
mode before converting it by the latest version of string.
Cause: The AW is stored in 9i format.
Action: Convert the AW to a later format
ORA-33288: (DBERR15) Another user has incompatible access to analytic
workspace string, and the wait timeout has expired.
Cause: An attempt to access an analytic workspace conflicted with another user's
access, and the timeout specified has elapsed.
Action: Wait until the conflicting user is done.
ORA-33290: (DBERR17) Analytic workspace string cannot be attached in the mode
you requested because another user has it attached in an incompatible mode.
Cause: An attempt to access an analytic workspace conflicted with another user's
access, and no timeout was specified
Action: Wait until the conflicting user is done.
ORA-33000 to ORA-37999 20-11
ORA-33291: (DBERRSYNC) Analytic workspace string cannto be attached RW until
a RESYNC command has brought it up to the current generation.
Cause: Another session has updated the analytic workspace since it was attached
in the current session.
Action: Execute a RESYNC AW command to bring the analytic workspace up to
the most recent version.
ORA-33292: (DBERR18) Insufficient permissions to access analytic workspace
string using the specified access mode.
Cause: You do not have sufficient permissions to access this analytic workspace in
the desired mode.
Action: Ask the owner of the schema or OLAP DBA to grant you sufficient
permissions to access the {SCHEMA}.AW${AWNAME} table (for example,
SCOTT.AW$FOO table).
ORA-33293: Please use the OLAP command AW TRUNCATE to truncate this table.
Cause: This table is part of an analytic workspace, and the OLAP option needs to
control the truncation of the table.
Action: use the OLAP option to truncate the table.
ORA-33295: (DBERR20) An attached analytic workspace is blocking this command.
Cause: A table cannot be dropped because an analytic workspace based on this
table is being attached.
Action: Look up the session in question in GV$AW_OLAP and kill it.
ORA-33296: (DBERR21) Analytic workspace string can only be attached RO while
tablespace string is READONLY.
Cause: The underlying tablespace of the analytic workspace is in READONLY
status.
Action: Attach the analytic workspace in RO mode or alter the tablespace.
ORA-33297: (DBERR22) Analytic workspace string cannot be opened because it was
last modified by an incompatible version of string.
Cause: The user attempted to attach an old OLAP Services analytic workspace
that cannot be converted by this version of OLAP Services.
Action: Either create a new analytic workspace or try using a version of OLAP
Services compatible with the one that created this analytic workspace.
ORA-33298: (AWUPG01) Analytic workspace string is already in the newest format
allowed by the current compatibility setting
Cause: User ran the DBMS_AW.CONVERT procedure on an analytic workspace
that was created in or previously upgraded to the current compatibility mode.
Action: If upgrading the analytic workspace is necessary, upgrade the database
instance and then re-run DBMS_AW.CONVERT. If the new features offered by
upgrading the analytic workspace are not required, then no action is needed.
ORA-33299: Please use DBMS_AW.AW_RENAME to rename this table.
Cause: This table is part of an analytic workspace, and the OLAP option needs to
control the rename of the table.
Action: use the OLAP option to rename the table.
ORA-33302: (DBVALID01) SEVERE ERROR: Record number multiply used.
20-12 Oracle Database Error Messages
Cause: The AW VALIDATE command has detected an error in the structure of the
analytic workspace. This error will result in the corruption of one or more objects
Action: Export what you can of the analytic workspace.
ORA-33304: (DBVALID02) Note: Record number was allocated but not used. This
can result in wasted space.
Cause: This is a benign message. The AW VALIDATE command found an analytic
workspace has some inaccessible space.
Action: Either nothing, or export and recreate the analytic workspace
ORA-33305: (DBVALID06) Note: Record number was allocated but not used. This
can result in wasted space. (PS number)
Cause: This is a benign message. The AW VALIDATE command found an analytic
workspace has some inaccessible space.
Action: Either nothing, or export and recreate the analytic workspace
ORA-33306: (DBVALID03) The AW VALIDATE command cannot be used with
read-only analytic workspace string.
Cause: The AW VALIDATE command does not support read-only access.
Action: Attach the analytic workspace read/write and try again.
ORA-33308: (DBVALID04) SEVERE ERROR: Record number used but not allocated
Cause: The AW VALIDATE command has detected a problem that will result in
corruption of the analytic workspace. There is no corruption yet.
Action: Export and recreate the analytic workspace.
ORA-33309: (DBVALID05) SEVERE ERROR: Record number used but not allocated
(PS number)
Cause: The AW VALIDATE command has detected a problem that will result in
corruption of the analytic workspace. There is no corruption yet.
Action: Export and recreate the analytic workspace.
ORA-33313: (DELDENT05) workspace object cannot be deleted because it is the
target of an external partition of a partitioned variable.
Cause: User attempted to delete a variable, but some partitioned variable was
defined to use that variable as the target of one of its external partitions.
Action: DELETE the partitioned variable or CHGDFN DROP PARTITION the the
external partition from the partitioned variable, then delete the target variable.
ORA-33315: (XSDELDENTANON) You cannot delete workspace object while
looping over unnamed composite workspace object.
Cause: While looping over the named anonymous composite, an attempt was
made to delete an object which is dimensioned by it.
Action: Delete the object outside of a loop over the dimension.
ORA-33332: (DSSEXIST01) Use the AW command to establish a current analytic
workspace. Then start your current activity again.
Cause: There is no currently active analytic workspace. The command that
generated the error requires an active analytic workspace to operate on.
Action: Execute an AW ATTACH or AW CREATE command to establish an active
workspace.
ORA-33000 to ORA-37999 20-13
ORA-33334: (DSSEXIST04) Analytic workspace string is not attached.
Cause: The specified analytic workspace is currently not attached to the session,
or the name is misspelled.
Action: Attach the analytic workspace with the AW ATTACH command, or
correct the spelling of the name .
ORA-33336: (DSSEXIST04A) Analytic workspace string is not attached.
Cause: The specified analytic workspace is currently not attached to the session,
or the name is misspelled.
Action: Attach the analytic workspace with the AW ATTACH command, or
correct the spelling of the name .
ORA-33338: (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.
Cause: The command requires a non-temporary analytic workspace to operate on.
Action: Specify an analytic workspace other than EXPTEMP.
ORA-33339: You cannot detach analytic workspace string. It is in use by an API
branch.
Cause: The OLAP API is in a branch, and you are not allowed to detach the AW
while the branch is active.
Action: End the branch before detaching the AW.
ORA-33393: (EIFIMPRT01) Object string exists in both the EIF file and the current
analytic workspace.
Cause: An object with the given name was found in both the EIF file and the
current analytic workspace.
Action: Rename the object in the analytic workspace that is causing the name
conflict. If the object named in the error message belongs to a cube or a cube
dimension, rename that cube or cube dimension.
ORA-33409: (EIFEXPRT16) Cannot use the FULLMAPID or RELATIVEMAPID
syntax because NOAPI has been specified.
Cause: An attempt was made to specify FULLMAPID or RELATIVEMAPID
syntax with the NOAPI option.
Action: Either specify the API option instead of NOAPI, or remove the
FULLMAPID or RELATIVEMAPID option.
ORA-33413: (EIFMAKEF01) You cannot export compressed composite workspace
object because one of its bases has limited status or a PERMIT READ
restriction.
Cause: Export of a compressed composite to an EIF file or lob failed because one
or more of the bases had some values that were not in the current status. This can
be caused either by a LIMIT command or a PERMIT READ restriction on the
dimension.
Action: Either set the base dimensions' statuses to ALL and remove their PERMIT
READ programs, or export using the NOAGGR keyword.
ORA-33425: (EIFMAKEF15) CAUTION: Exporting NTEXT objects using string for
the EIF file character set can cause loss of data. To preserve all NTEXT data,
export using the UTF8 character set for the EIF file.
Cause: The user exported an object with data type NTEXT, but the EIF file that
will result from the EXPORT command is not written in Unicode. Because no
non-Unicode file can represent all possible Unicode data, it is possible that some
20-14 Oracle Database Error Messages
data will be lost when converting from the Unicode NTEXT object to the EIF file.
The EIF file will be written in the character set indicated by the "nls_charset"
argument of the EXPORT command, or, if no such argument is present, in the
database character set.
Action: If the user is certain that the contents of the NTEXT object can be
represented in the specified character set, then no action is necessary. Otherwise,
the user can add "nls_charset 'UTF8'" to the EXPORT command string. This will
result in the EIF file being written in UTF8 Unicode, which can represent all the
data contained in NTEXT objects.
ORA-33427: (EIFMAKEF16) CAUTION: NTEXT object workspace object will be
exported with type TEXT.
Cause: User attempted to export an object whose data type is NTEXT, but but the
EIFVERSION option indicates a version of Express / Oracle OLAP that does not
support the NTEXT data type. The object will be exported as a TEXT object
instead.
Action: No action needed.
ORA-33429: (EIFMAKEF17) CAUTION: NTEXT expression will be exported with
type TEXT.
Cause: User attempted to export an expression whose data type is NTEXT, but
but the EIFVERSION option indicates a version of Express / Oracle OLAP that
does not support the NTEXT data type. The expression will be exported as a TEXT
object instead.
Action: No action needed.
ORA-33443: (ESDREAD14) Discarding compiled code for workspace object because
analytic workspace string is not attached.
Cause: A program used an analytic workspace name in a qualified object name.
The named analytic workspace is not attached at program run time.
Action: No action necessary. The program will be automatically recompiled. It is
likely that the recompile will fail with an appropriate exception code, in which
case the signaled condition should be corrected and the program re-run.
ORA-33445: (ESDREAD15) Discarding compiled code for workspace object because
workspace object and workspace object, which were not partition-dependent
when the code was compiled, are now partition-dependent.
Cause: Two variables are "partition-dependent" if they share any external
partition target variables, or if one is the target of an external partition of the other.
If object names referred to non-partition-dependent variables at compile time but
refer to partition-dependent variables in the run-time context, the OLAP DML
program, formula, or model will be automatically recompiled.
Action: None needed.
ORA-33447: (ESDREAD16) Discarding compiled code for workspace object because
workspace object and workspace object, which were partition-dependent when
the code was compiled, are now not partition-dependent.
Cause: Two variables are "partition-dependent" if they share any external
partition target variables, or if one is the target of an external partition of the other.
If object names referred to partition-dependent variables at compile time but refer
to non-partition-dependent variables in the run-time context, the OLAP DML
program, formula, or model will be automatically recompiled.
Action: None needed.
ORA-33000 to ORA-37999 20-15
ORA-33448: (ESDREAD04) Discarding compiled code for workspace object because
number now has string data, whereas it had string data when the code was
compiled.
Cause: The datatype of the specified variable has changed.
Action: None needed.
ORA-33449: (ESDREAD17) Discarding compiled code for workspace object because
the partition method or partition dimension of number has changed since it was
compiled.
Cause: The partitioning method (LIST, RANGE, or CONCAT) or the partition
dimension of the partition template is sufficiently different from what it was when
the code was compiled that the code must be recompiled.
Action: None needed.
ORA-33450: (ESDREAD05) Discarding compiled code for workspace object because
number now has more or fewer dimensions than it had when the code was
compiled.
Cause: The dimensionality of the specified object has changed.
Action: None needed.
ORA-33452: (ESDREAD06) Discarding compiled code for workspace object because
number is now dimensioned by workspace object. It was dimensioned by
workspace object when the code was compiled.
Cause: The dimensionality of the specified object has changed.
Action: None needed.
ORA-33454: (ESDREAD07) Discarding compiled code for workspace object because
number is now string workspace object, whereas it was string workspace object
when the code was compiled.
Cause: The specified object has changed.
Action: None needed.
ORA-33456: (ESDREAD08) Discarding compiled code for workspace object because
number is a(n) string, which string did not expect to find in a compiled program.
Cause: The type of the specified object has changed.
Action: None needed.
ORA-33458: (ESDREAD09) Discarding compiled code for workspace object because
number is now type string, whereas it was type string when the code was
compiled.
Cause: The type of the specified object has changed.
Action: None needed.
ORA-33460: (ESDREAD10) Discarding compiled code for workspace object because
object workspace object is not in analytic workspace string.
Cause: The specified object is not in the same analytic workspace it was in when
the compiled object was compiled.
Action: None needed.
ORA-33462: (ESDREAD10A) Discarding compiled code for workspace object
because object number is not in analytic workspace string.
20-16 Oracle Database Error Messages
Cause: The specified object was not in the same analytic workspace it was when
the compiled object was compiled
Action: None needed.
ORA-33468: (ESDREAD13) Discarding compiled code for workspace object because
number is no longer a surrogate of dimension workspace object.
Cause: When the compiled code was saved, the specified object was a surrogate
of a certain dimension. Now the specified object is a surrogate of a different
dimension.
Action: No action needed; program automatically recompiles.
ORA-33557: (MAINTCHK01) You cannot string values of dimension workspace
object during a loop over it.
Cause: User tried to insert or delete a value of the specified dimension while some
loop over that dimension was active. The loop could be an explicit FOR or
ACROSS loop, or a natural expression evaluation or OLAP_TABLE loop. Also, it
could be a loop over the dimension itself or over a derived dimension (like a
composite or partition template) or dimension alias that includes it. The insert or
delete could be explicitly caused by the MAINTAIN command. It is also possible
that the user attempted to assign a value to a variable or partition dimensioned by
a composite during a loop over that composite using a qualified data reference
(QDR), and that the exception was generated by the engine's attempt to insert a
new position in the composite to hold the new value.
Action: Move the dimension maintenance or QDR-based variable assignment
outside the dimension loop.
ORA-33558: (LOCKCHECK01) The status or contents of the workspace object
dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is
set to value.
Cause: A LIMIT or MAINTAIN was attempted on the named language dimension
while the boolean option LOCK_LANGUAGE_DIMS was set to YES.
Action: SET LOCK_LANGUAGE_DIMS to NO and retry the MAINTAIN or
LIMIT.
ORA-33625: (FRASSIGN02) You cannot use the APPEND keyword with concat
dimension workspace object.
Cause: User used the APPEND keyword on a CONCAT target in a FILEREAD,
SQL FETCH or SQL SELECT command.
Action: APPENDing a value to one of the CONCATs leaves automatically
appends to the CONCAT.
ORA-33733: (xsILPMLTPreOp01) The analytic workspace string cannot be
REVERTed or RESYNCed while the string program is active.
Cause: The AW REVERT and AW RESYNC commands cannot be used on an
analytic workspace that contains a running program.
Action: Execute the command without running the specified program.
ORA-33883: (MAKEDCL36) You cannot use the string attribute when you define an
EXTERNAL partition with an existing target.
Cause: User gave the TEMPORARY keyword in the definition of an external
partition whose target variable was previously defined.
ORA-33000 to ORA-37999 20-17
Action: Any storage characteristics of the external partition are determined by the
target variable. These attributes should be set when the target is defined, not when
the external partition is defined.
ORA-33911: (MAKEDCL29) You cannot define a string in analytic workspace string
because it has not been upgraded to version string.
Cause: User attempted to define an object that requires a certain compatibility
setting in an AW that has not been upgraded to that compatibility level.
Action: Make sure that the database is running in the appropriate compatibility
mode, and upgrade the AW.
ORA-33918: (MAKEDCL33) You cannot define a surrogate of dimension workspace
object because it is a string.
Cause: Not all kinds of dimensions can have surrogates. The user attempted to
define a surrogate of a prohibited kind of dimension.
Action: Do not attempt to define a surrogate on this dimension.
ORA-33920: (MAKEDCL34) The string SURROGATE must have one of the
following data types: ID, NTEXT, TEXT, NUMBER, DATETIME, TIMESTAMP,
or INTEGER.
Cause: The user attempted to define a surrogate without specifying a valid data
type.
Action: Specify the data type (ID, NTEXT, TEXT, NUMBER, or INTEGER) in the
definition of the surrogate.
ORA-33922: (MAKEDCL35) You cannot define a surrogate of dimension workspace
object because it is a time dimension.
Cause: The user attempted to define a surrogate on a dimension that has type
DAY, WEEK, MONTH, or YEAR.
Action: Do not attempt to define a surrogate on this dimension.
ORA-33998: (MODCOMP12) You cannot use both workspace object and workspace
object as model dimensions, because workspace object is a surrogate of
workspace object.
Cause: The user attempted to include both a dimension and its surrogate in the
DIMENSION statement of a model.
Action: Use either the dimension or the surrogate in the DIMENSION statement
of the model, but not both.
ORA-34000: (MODCOMP13) You cannot use both workspace object and workspace
object as model dimensions, because they are both surrogates of dimension
workspace object.
Cause: The user attempted to include two dimension surrogates of the same
dimension in the DIMENSION statement of a model.
Action: Use either of the two surrogates in the DIMENSION statement of the
model, but not both.
ORA-34001: (MODCOMP14) Concat leaf dimension workspace object already is
used in a DIMENSION statement, either explicitly or as a leaf of another concat
dimension.
Cause: Either two concat dimensions which share a common leaf dimension, or a
concat and one of its leaves where both specified in the DIMENSION statement(s).
20-18 Oracle Database Error Messages
Action: Do not specify overlapping concat dimensions, or any leaves of specified
concat dimensions.
ORA-34019: (MSCGADD03) workspace object is not a LIST PARTITION
TEMPLATE.
Cause: User attempted to MAINTAINT ADD or DELETE a list value from a
RANGE or CONCAT partition template.
Action: Partitioning in a RANGE or CONCAT partition template cannot be
changed using the MAINTAIN command.
ORA-34021: (MSCGADD04) You must specify a partition when maintaining
PARTITION TEMPLATE workspace object.
Cause: User attempted to MAINTAINT ADD or DELETE a list value from a LIST
partition template, but didn't specify which partition to add to or delete from.
Action: Specify the partition: maintain (template) add to partition (partitionname)
(values) or maintain (template) delete from partition (partitionname) (values)
ORA-34059: (MSEXECUT12) You cannot delete non session-only dimension values
from unique concat dimension workspace object.
Cause: The user tried to apply MAINTAIN DELETE to a non-SESSION value.
Action: Only use MAINTAIN DELETE to remove SESSION values from a concat
dimension.
ORA-34061: (MSEXECUT11) Session-only values cannot be added to non-unique
concat dimension workspace object, or any of its base dimensions.
Cause: Only UNIQUE concat dimensions can have custom member values.
Action: Use the CHGDFN command to change the concat dimension to UNIQUE
and retry.
ORA-34141: (MXCGPUT00) You cannot use the ASSIGN keyword with
DIMENSION workspace object.
Cause: User used the ASSIGN keyword on a DIMENSION target in a FILEREAD,
SQL FETCH or SQL SELECT command.
Action: To create a new dimension value in a FILEREAD, SQL FETCH or SQL
SELECT command, use the APPEND keyword.
ORA-34143: (MXCGPUT02) You cannot assign values to SURROGATE workspace
object because it is type INTEGER.
Cause: The user attempted to assign a value to a dimension surrogate whose data
type is INTEGER. INTEGER surrogates, like INTEGER dimensions, cannot have
values assigned to them. They can only be referenced by position.
Action: Do not attempt to assign values to an INTEGER surrogate. Values will
automatically appear and disappear from the INTEGER surrogate as positions are
added to or removed from the underlying dimension.
ORA-34145: (MXCGPUT03) You cannot use the APPEND keyword with
SURROGATE workspace object.
Cause: User used the APPEND keyword on a SURROGATE target in a
FILEREAD, SQL FETCH or SQL SELECT command.
Action: To assign a value to a SURROGATE in a FILEREAD, SQL FETCH or SQL
SELECT command, use the ASSIGN keyword.
ORA-33000 to ORA-37999 20-19
ORA-34164: (MXCGVAR01) A dimension used to define a local string variable
cannot be located. Execution cannot continue.
Cause: A local relation or valueset has become invalid, most probably because an
object used by the currently executing program has been deleted.
Action: This is an internal error that should be referred to Oracle technical
support.
ORA-34177: (MXCHGDCL19) number cannot be deleted because one or more
partitioned variables instantiate it.
Cause: User attempted to CHGDFN DELETE a partition template, but some
partitioned variable had data in the partition specified for deletion.
Action: Drop the partitions that are causing the problem, then retry.
ORA-34179: (MXCHGDCL20) workspace object is not a PARTITION TEMPLATE.
Cause: User specified an object that is not a partition template where a partition
template is required.
Action: Supply the name of a partition template.
ORA-34181: (MXCHGDCL21) workspace object is not a partitioned VARIABLE.
Cause: User specified an object that is not a partitioned variable in a place where a
partitioned variable is required.
Action: Supply the name of a partitioned variable.
ORA-34183: (MXCHGDCL22) Partition number already exists.
Cause: User attempted to ADD a partition that already existed to a partitioned
variable.
Action: None required - the partition already exists.
ORA-34210: (MXCHGDCL18) You cannot change workspace object to a dimension
composite because one or more surrogates has been defined for it.
Cause: The user attempted to redefine a conjoint dimension as a composite, but
the conjoint has one or more surrogates defined. A dimension that has surrogates
cannot be redefined as a composite.
Action: Either delete all surrogates for the dimension, or do not attempt to
redefine the dimension as a composite.
ORA-34243: (MXDCL11) You can only use the string keyword when defining a
COMPOSITE.
Cause: User supplied the COMPRESSED keyword when defining an object that
was not a COMPOSITE.
Action: If the intent is to create a compressed composite, make sure that the object
type is COMPOSITE. Otherwise, remove the COMPRESSED keyword from the
command string and rerun.
ORA-34260: (MXDCL25) You cannot use number to dimension a string because it is,
or involves, a dimension composite. Use the composite's bases instead.
Cause: The user attempted to use a COMPOSITE in the dimension list of an object
that does not allow for such dimensions.
Action: Use the base dimensions of the COMPOSITE in the dimension list.
ORA-34276: (MXDCL33) (Precision, Scale) arguments can only be used with a
NUMBER variable or dimension.
20-20 Oracle Database Error Messages
Cause: The user attempted to use NUMBER(Precision) or NUMBER(Precision,
Scale) as the datatype in a definition for some object other than a DIMENSION or
VARIABLE, such as a FORMULA or PROGRAM. This error can also be produced
in cases where a NUMBER data type is not allowed at all.
Action: Use the NUMBER type without specifying a precision or scale. If a
NUMBER data type is not allowed at all, this fix will only change the exception
message to something more specific.
ORA-34279: (MXDCL37) CONCAT can only be used when defining a
DIMENSION.
Cause: The CONCAT keyword was used incorrectly.
Action: Retry the command without the CONCAT keyword.
ORA-34286: (MXDCL53) workspace object cannot be used in this context because it
is a string.
Cause: User specified a dimension composite, conjoint, or partition template in a
place where that kind of dimension is not allowed. For instance, a relation cannot
be dimensioned by a composite, and only a variable can dimensioned by a
partition template.
Action: Usually, the offending dimension can be replaced with its bases. For
instance, a relation cannot be dimensioned by a a composite of PRODUCT and
GEOG, but it can be dimensioned by both PRODUCT and GEOG instead.
ORA-34342: (MXDSS01) IMPORTANT: Analytic workspace string is read-only.
Therefore, you will not be able to use the UPDATE command to save changes to
it.
Cause: This is an informational message that reminds you that you may not save
changes to the specified analytic workspace.
Action: None, unless it was desired to save changes to the analytic workspace. In
that case, detach and reattach the analytic workspace read-write.
ORA-34344: (MXDSS03) Analytic workspace string is not attached.
Cause: The command attempted to operate on an analytic workspace that is not
currently attached, or the name of the analytic workspace is misspelled.
Action: Attach the analytic workspace or correct the spelling.
ORA-34346: (MXDSS04) The string analytic workspace cannot be detached.
Cause: The specified analytic workspace is an internal workspace and may not be
detached by the user.
Action: Specify a different analytic workspace to detach.
ORA-34348: (MXDSS05) string is used only for internal purposes and cannot be
accessed as an analytic workspace.
Cause: The command attempted to operate on an internal analytic workspace
used by the system.
Action: Specify a different analytic workspace.
ORA-34350: (MXDSS06) string is an open analytic workspace.
Cause: The specified analytic workspace is currently in use.
Action: The desired action requires an analytic workspace that is not currently in
use.
ORA-34357: (MXDSS10) string is not an alias of analytic workspace string.
ORA-33000 to ORA-37999 20-21
Cause: User attempted to use AW UNALIAS on a non-existent alias.
Action: Make sure that the command specified the correct analytic workspace and
alias. The alias must have been assigned (using AW ALIAS) during the current
session and must not have been removed by a previous AW UNALIAS or AW
DETACH command.
ORA-34358: (MXDSS14) number other users reading
Cause: Used for AW LIST output formatting when %d > 1
Action: None
ORA-34359: (MXDSS11) string appears twice in the alias list.
Cause: User included the same name twice in the alias list of an AW ALIAS or
AW UNALIAS command.
Action: Remove the duplicate name and try again.
ORA-34360: (MXDSS15) number other users writing
Cause: Used for AW LIST output formatting when %d > 1
Action: None
ORA-34361: (MXDSS12) number other user reading
Cause: Used for AW LIST output formatting when %d == 1
Action: None
ORA-34363: (MXDSS13) number other user writing
Cause: Used for AW LIST output formatting when %d == 1
Action: None
ORA-34374: (MXDSS27) string is not a valid analytic workspace name. Analytic
workspace names must be 26 characters or less, can contain only letters, digits,
and underscores, and cannot begin with a digit.
Cause: a specified AW or ALIAS name was too long or contained invalid
characters.
Action: verify that AW name meets the specified criteria.
ORA-34376: (MXDSS28) string is not a valid analytic workspace name. Analytic
workspace names must be 26 characters or less, can contain only letters, digits,
underscores, and dollar signs, and cannot begin with a digit or dollar sign.
Cause: a specified AW or ALIAS name was too long or contained invalid
characters.
Action: verify that AW name meets the specified criteria.
ORA-34481: (MXMAINT07) You cannot string values of PARTITION TEMPLATE
workspace object.
Cause: User attempted to use the MAINTAIN command with some keyword
other than ADD or DELETE on a partition template.
Action: It is not possible to MAINTAIN a partition template, except to add or
delete values of a partition list.
ORA-34487: (MXMAINT08) You cannot string values of non-unique concat
dimension workspace object.
Cause: The specified MAINTAIN operation can only be applied to UNQUE
concats.
20-22 Oracle Database Error Messages
Action: Use the CHGDFN command to change the concat dimension to UNIQUE
and retry.
ORA-34489: (MXMAINT06) You cannot maintain workspace object because it is a
SURROGATE.
Cause: The user attempted to use the MAINTAIN command on a dimension
surrogate. The MAINTAIN command can only be used with real dimensions, not
surrogates.
Action: Use the MAINTAIN command to modify the underlying dimension of the
surrogate instead.
ORA-34514: (MXOPERR) You cannot string string data in the expression that begins
with 'string'.
Cause: The user attempted an invalid operation.
Action: None
ORA-34647: (MXSQL18) The text expression in a CURSOR FOR TEXT declaration
cannot be NA.
Cause: The text for the SELECT expression in a CURSOR FOR TEXT declaration
was evaluated at compile time as NA.
Action: Specify a text expression that is not NA at the time the program
containing the SQL DECLARE is compiled.
ORA-34656: (MXSQL24) Additional WHERE clause conditions with CURRENT OF
<cursor name> syntax
Cause: A SQL UPDATE or DELETE statement tried to use the CURRENT of
<cursor name> syntax with a WHERE clause containing multiple conditions.
Action: When using the CURRENT OF <cursor name> syntax make sure it is the
only condition in the WHERE clause.
ORA-34658: (MXSQL25) The words CURSOR FOR TEXT must be followed by a
compile-time text expression specifying a SELECT command.
Cause: A SQL DECLARE <csr> CURSOR FOR TEXT command lacked a text
expression, or the expression was otherwise invalid.
Action: Specify a single text expression that can be evaluated at compile time to
yield a SELECT statement
ORA-34719: (NLSCHARSET03) Character data loss in NTEXT/TEXT conversion
Cause: When character set conversion happens between TEXT and NTEXT either
implicitly or explicitly, some characters are lost due to no mapping characters in
the destination character set.
Action: Make sure all the characters can be mapped to destination character set or
set NLS_NCHAR_CONV_EXCP to be FALSE. Note: This message is the OLAP
equivalent of ORA-12713.
ORA-34722: (NLSCHARSET05) CAUTION: Character data loss in character set
conversion from string to string
Cause: Some operation required a string to be converted into a different character
set, but the string contained characters that didn't exist in the new character set.
Action: Choose different character sets.
ORA-34726: (NLSCHARSET06) CAUTION: String truncated during character set
conversion from string to string
ORA-33000 to ORA-37999 20-23
Cause: Some operation required a string to be converted into a different character
set. The string required more bytes in the new encoding, and exceeded some byte
limit on its allowable length, causing some characters to be removed from the end
of the string.
Action: If the byte limit is due to using the ID datatype, consider using the CHAR
datatype instead. If the byte limit is due to the limit of 4000 bytes per line of CHAR
data, break the long line up into multiple lines.
ORA-34731: (NLSSORT01) 'number' is not a valid NLS_SORT specification.
Cause: An unrecognized NLS_SORT value was specified in the SORT command
or the SORT, SORTLINES or UNIQUELINES function.
Action: Specify a supported NLS_SORT value.
ORA-34738: (NOUPDATE) A severe problem has been detected. Analytic
workspace operations have been disabled.
Cause: A previous fatal error has marked the session so that it cannot perform
any UPDATEs
Action: Start a new session
ORA-34761: (NXHANDLEALLO) A decimal overflow occurred during an
ALLOCATE operation. The results are not reliable.
Cause: While performing an ALLOCATE, a decimal overflow occurred
Action: Correct the data or use a higher precision datatype
ORA-34796: (OCI08) SQL host variable number cannot be bound.
Cause: The data type of the host variable is not supported.
Action: Specify only variables of supported types as host variable names.
ORA-34802: (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of
an attached analytic workspace. Current operation canceled.
Cause: ROLLBACK past the UPDATE of one of the attached Analytic Workspaces
was called. The current operation is aborted, and the Analytic Workspace
detached.
Action: Change the called SQL procedure to avoid the ROLLBACK
ORA-34804: (OCI12) The value of SQL host variable number is too long. Use the
WIDE keyword for columns that may exceed number bytes.
Cause: The host variable had a text value longer than the maximum SQL
VARCHAR length
Action: Use the WIDE keyword in the host variable specification, e.g. :WIDE
OLAP_object_name
ORA-34805: (OCI13) Statement number must have at least one host variable.
Cause: Statements prepared with DIRECT=YES must have at least one host
variable.
Action: Add a host variable to the prepared statements declaration.
ORA-34806: (OCI14) Statement number can only be executed within an ACROSS
command.
Cause: Statements prepared with DIRECT=YES must be executed in an ACROSS
command.
Action: Execute the statement within an ACROSS command.
20-24 Oracle Database Error Messages
ORA-34840: (OPCREATE01) The string option must be declared with datatype
string.
Cause: An attempt was made to declare the option with the wrong datatype.
Action: Declare the option with the correct datatype.
ORA-34841: (OPCREATE02) The string option must be declared with the
READONLY attribute.
Cause: An attempt was made to declare the option without the READONLY
attribute.
Action: Declare the option READONLY.
ORA-34859: (PMTUPDAT07) Permission condition for workspace object contains
an expression longer than number bytes and cannot be stored.
Cause: One of the components of the PERMIT condition was too long.
Action: Rewrite the condition to shorten it.
ORA-34871: (PERMIT06) Session-only value 'value' of workspace object has been
deleted because a PERMIT change has revealed a duplicate value.
Cause: Execution of a PERMIT command revealed a permanent dimension or
surrogate value having the same name as the SESSION value.
Action: If the SESSION value is still needed, add it with a different name.
ORA-34896: (PPMONTHS00) At least 12 month names must be given. Only number
were provided.
Cause: There must be at least one name for each month. Not enough names were
provided.
Action: Provide at least 12 names.
ORA-34897: (PPMONTHS01) Blank lines are not allowed in the MONTHNAMES
option.
Cause: There is at least one blank line in the string populating the
MONTHNAMES option. We do not allow blank month names.
Action: Remove the blank line(s) from the string.
ORA-34900: (PPWKDAYS00) At least 7 day names must be given. Only number
were provided.
Cause: There must be at least one name for each day. Not enough names were
provided.
Action: Make sure there are at least 7 names in the string.
ORA-34901: (PPWKDAYS01) Blank lines are not allowed in the DAYNAMES
option.
Cause: There is at least one blank line in the string populating the DAYNAMES
option. We do not allow blank day names.
Action: Remove the blank line(s) from the string.
ORA-35016: (QFCHECK00) The analytic workspace and EIF file definitions of
workspace object have a mismatched type.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
ORA-33000 to ORA-37999 20-25
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35017: (QFCHECK06) The Analytic Workspace and EIF file definitions of
workspace object have different partitioning methods.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35018: (QFCHECK01) The analytic workspace and EIF file definitions of
workspace object have a mismatched data type.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35019: (QFCHECK07) The Analytic Workspace and EIF file definitions of
workspace object have different partition dimensions.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35020: (QFCHECK02) The analytic workspace and EIF file definitions of
workspace object have mismatched dimensioning.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35021: (QFCHECK08) The EIF file definition of workspace object has some
partitions that are not present in the existing Analytic Workspace object.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35022: (QFCHECK03) The analytic workspace and EIF file definitions of
workspace object have a mismatched relation.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35023: (QFCHECK09) The analytic workspace and EIF file definitions of
workspace object have incompatible partition definitions.
20-26 Oracle Database Error Messages
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35024: (QFCHECK04) The analytic workspace and EIF file definitions of
workspace object have mismatched time dimension attributes.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35026: (QFCHECK05) The analytic workspace and EIF file definitions of
workspace object have a mismatched ALIASOF dimension.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35031: (QFSVNS00) The IMPORT command has terminated because of a
defect in the EIF file.
Cause: The EIF file contains a compressed composite with defective aggregation
data.
Action: Recreate the EIF file using the NOAGGR keyword.
ORA-35062: (QFGET01) Duplicate files found for extension number number of EIF
file string.
Cause: IMPORT searched the directories specified in EIFEXTENSIONPATH and
found two EIF extension files with the same name (differing at most by the case
used in the final name component.
Action: Delete, rename or move any files that are not to be read by IMPORT.
ORA-35066: (QFGET03) Extension number number is missing for EIF file string.
Cause: IMPORT searched the directories specified in EIFEXTENSIONPATH and
could not find the appropriately numbered extension file.
Action: Move the missing file into one of the searched directories.
ORA-35071: (QFHEAD06) EIF file string cannot be imported because analytic
workspace string has not been upgraded to version string.
Cause: User attempted to import from an EIF file that was created by a newer
version of the product into an AW that was created by a older version of the
product.
Action: Make sure that the compatibility mode parameter in the init.ora of the
importing instance specifies a version that is at least as high as the parameter was
in the exporting instance. Then, convert the AW to the latest storage format and
reexecute the import command. Alternatively, change the EIFVERSION option of
the exporting instance to a lower number, recreate the EIF file, and import the new
file.
ORA-35074: (QFHEAD02) EIF file string cannot be read by this version of string.
ORA-33000 to ORA-37999 20-27
Cause: The EIF file was created with an internal version number indicating it may
contain objects that are not compatible with the current Oracle OLAP version, or
the EIF file is in an obsolete format.
Action: If possible, set EIFVERSION in the exporting instance to a lower number,
recreate the EIF file, and import the new file.
ORA-35076: (QFHEAD04) CAUTION: The textual data in EIF file string is encoded
in a character set that is not recognized by this version of string.
Cause: IMPORT could not recognize the character set specification in the EIF file.
Action: Check the imported text data. If it was not imported correctly, recreate the
EIF file with a character set supported by the current Oracle version.
ORA-35078: (QFHEAD05) An EIF extension file header for string is not in the
correct format.
Cause: An EIF extension file in multi-file IMPORT did not contain correct header
information.
Action: Check to be sure that EIFEXTENSIONPATH is set correctly and that all
the extension files for the current IMPORT were created by the same EXPORT
command as the main EIF file.
ORA-35095: (QFSVNS01) One or more imported values of fixed-width dimension
workspace object have been truncated.
Cause: The data in the EIF file was exported from a dimension with wider values
than the target dimension will accommodate.
Action: Change the definition of the target dimension, or check to be sure that
multiple values from the target dimension have not become identical during the
import process. This could cause data loss as data from later dimension values
overstores data imported earlier.
ORA-35106: (REGRESS00) The regression was not calculated because of a linear
relationship between your independent variables.
Cause: The values of the specified independent variables are not independent. For
example, one may be a multiple of the other.
Action: Chose independent variables whose values are truly independent of one
another.
ORA-35171: you may not signal error number string with the SIGNAL command
Cause: The user attempted to explicitly signal an invalid error number with the
OLAP DML SIGNAL command
Action: Signal another error number
ORA-35180: (SNSYN103) The format of the OUTFILE command is: OUTFILE
[APPEND] {EOF | TRACEFILE | filename [NOCACHE] [NLS_CHARSET
name]}
Cause: The user specified incorrect syntax for the OUTFILE command.
Action: None
ORA-35276: (SNSYN163) The format of the ALLOCATE command is: ALLOCATE
varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]]
[TARGET tvarname [TARGETLOG logvarname]] [USING aggmap]
Cause: The user used incorrect syntax for the ALLOCATE command.
Action: Correct the calling syntax.
20-28 Oracle Database Error Messages
ORA-35280: (SNSYN165) The format of the AGGREGATE command is:
AGGREGATE varname1 [varname2 varname3 ...] [USING aggmap-name]
[COUNTVAR intvar-name1 [intvar-name2 intvar-name3 ...]] [FUNCDATA]
[FORCEORDER] [PARALLEL #] [{FROM|FROMVAR} fromname [, fromname2
...]]
Cause: The user used incorrect syntax for the AGGREGATE command.
Action: Correct the calling syntax.
ORA-35282: (SNSYN166) The format of the AGGREGATE function is:
AGGREGATE(varname [USING aggmap-name] [COUNTVAR intvar-name]
[FORCECALC] [FORCEORDER] [{FROM|FROMVAR} fromname [, fromname2
...]])
Cause: The user used incorrect syntax for the AGGREGATE function.
Action: Correct the calling syntax.
ORA-35561: (XSRWLD01) Object workspace object is not a valid target.
Cause: An invalid object was specified as a target.
Action: Choose a valid object as a target.
ORA-35562: (SQLIMP01) The SQL IMPORT command will produce number
columns of output, but you have provided number host variables in your INTO
clause.
Cause: The expression is the source query do not match the targets in the INTO
clause.
Action: Make sure the the expressions in the source query match the targets in the
INTO clause.
ORA-35563: (XSRWLD17) Multiple values exist for an attribute of this dimension
member.
Cause: Multiple source table rows containing different values for a dimension
attribute were found. Only the first of the multiple rows has been loaded.
Action: Fix the mapping or remove the rows with conflicting attribute values.
ORA-35564: (XSRWLD02) Cannot convert from the string type to the string type.
Cause: Conversion from source to target is not allowed
Action: Choose a different target datatype
ORA-35565: (XSRWLD03) For object workspace object only APPEND, MATCH or
ASSIGN may be used.
Cause: An incorrect setting was applied to the target
Action: For DIMENSIONs use APPEND or MATCH, for SURROGATEs use
ASSIGN.
ORA-35566: (XSRWLD04) Object workspace object cannot be used with QDRs
Cause: A QDR was placed on a target dimension
Action: Remove the QDR on the target dimension
ORA-35568: (SQLIMP03) The datatype of variable number should be INTEGER,
LONGINTEGER or SHORTINTEGER.
Cause: The target variable was not INTEGER, LONGINTEGER or
SHORTINTEGER.
ORA-33000 to ORA-37999 20-29
Action: The target variable must be INTEGER, LONGINTEGER or
SHORTINTEGER.
ORA-35569: (XSRWLD05) An error was encountered in converting data string to
string in column number.
Cause: The data could not be converted to the target datatype.
Action: Ensure the source data is valid for the target datatype.
ORA-35570: (XSRWLD06) A column value is not a valid member of its target
dimension.
Cause: The source value for a dimension is not an existing member of the
dimension.
Action: Ensure the column value is an existing member of its target dimension.
ORA-35571: (XSRWLD07) The maximum number of load errors has occurred. No
changes from this step were committed to the database.
Cause: The number of load errors exceeded the specified maximum.
Action: Fix the load errors, or increase the maximum number allowed and rerun
the load.
ORA-35572: (XSRWLD08) A column value is not a valid member of its related
dimension.
Cause: The source data for a relation is not a member of the related dimension.
Action: Ensure the source data is a valid member of the related dimension.
ORA-35573: (XSRWLD09) An incoming dimension value is null.
Cause: A source value for a dimension is null.
Action: Ensure the source data for the dimension is not null.
ORA-35578: (SQLOUT11) SQL cursor 'number' cannot be used with CURRENT OF
<cursor name> syntax
Cause: The CURRENT OF <cursor> syntax in the WHERE clause tried to use a
cursor that was not declared with the FOR UPDATE [ of <column name> ] SQL
syntax.
Action: Add the FOR UPDATE [ OF <column name> ] SQL syntax to the cursor
specified.
ORA-35580: (XSRWLD10) An incoming column contains a data type mismatch.
Cause: The data could not be converted to the target datatype.
Action: Ensure the source data is valid for the target datatype.
ORA-35581: (XSRWLD11) You do not have permission to write this value of the
target.
Cause: You do not have sufficient permissions to write to the specified target.
Action: Ask the owner of the schema or OLAP DBA to grant you sufficient
permissions.
ORA-35582: (XSRWLD12) Cannot change the level of dimension member "number"
from "number" to "number" within a single load.
Cause: A dimension member is mapped to more than one level.
Action: Change the mapping so that each dimension member is mapped to only
one level.
20-30 Oracle Database Error Messages
ORA-35583: (XSRWLD13) Cannot change the level of a dimension member within a
single load.
Cause: A dimension member is mapped to more than one level.
Action: Change the mapping so that each dimension member is mapped to only
one level.
ORA-35585: (XSRWLD14) This SQL query generated rejected records.
Cause: Rejected records were generated by this query.
Action: Locate the records that were rejected and resolve the rejection (for
example, data, mapping, and so on).
ORA-35587: (SQLOUT20) The nesting of table functions and SQL commands has
exceeded the maximum of number levels.
Cause: The nesting of table functions with the PREDMLCMD token populated
with an OLAP DML expression that use the embedded SQL support to access
another table function which contains a table functions with the PREDMLCMD
token filled in with an OLAP DML expression that uses the embedded SQL
support.
Action: Reduce the level of nesting between table functions and OLAP DML
embedded SQL support.
ORA-35588: (XSRWLD15) Cannot change the parent of existing dimension member
"number" from "number" to "number" in LOAD RETAIN mode.
Cause: An attempt was made to change the parent of an existing dimension
member in LOAD RETAIN mode.
Action: Fix the mapping or use LOAD [NO] SYNCH mode.
ORA-35589: (XSRWLD16) Cannot change the parent of an existing dimension
member in LOAD RETAIN mode.
Cause: An attempt was made to change the parent of an existing dimension
member in LOAD RETAIN mode.
Action: Fix the mapping or use LOAD [NO] SYNCH mode.
ORA-35749: (VCHEX01) 'character' is not a valid hexadecimal digit.
Cause: The text being converted contains an invalid hexadecimal digit.
Action: Replace the character with a digit in the range 0-9 or A-F.
ORA-35756: (VCTODT02) 'number' is not a valid date because number is out of
range for a year.
Cause: n'%1p'
Action: None
ORA-35810: (XSINPUTERR) The command has requested more input than was
supplied in the command string.
Cause: The command required input that was not supplied in the string.
Action: Reexecute the command with the required input.
ORA-35917: (XSHIDE05) You cannot HIDE model workspace object because the
analytic workspace in which it is defined has not been upgraded to version
string.
Cause: User attempted to apply the HIDE command to a model in an AW that has
not been upgraded to the necessary compatibility level.
ORA-33000 to ORA-37999 20-31
Action: Make sure that the database is running in the appropriate compatibility
mode, and upgrade the AW.
ORA-35952: (XSSPFC01) The string dimension workspace object and the string
dimension workspace object must have the same number of values in status for
SPFCEXEC method number.
Cause: This method requires the named dimensions to have the same number of
values in status, but the user provided statuses of different lengths.
Action: Relimit the dimensions so that their status lengths are the same.
ORA-36017: (XSHIERCK10) The definition of hierarchy workspace object over
number in level number is not star consistent. The collision parents include
number.
Cause: The definition of the hierarchy was not star consistent.
Action: Change the definition of the hierarchy.
ORA-36018: (XSHIERCK02) The format of the HIERCHECK command is:
HIERCHECK relation [STATUS|NOSTATUS|valueset] [MULTIPATH]
[CONSISTENT] [{BALANCED|STAR_CONSISTENT} levelrelation] Or
HIERCHECK aggmap [MULTIPATH] [CONSISTENT]
Cause: The wrong object type was specified.
Action: Change the object to a RELATION or AGGMAP.
ORA-36019: (XSHIERCK11) The format of the HIERSHAPE function is:
HIERSHAPE(relation[(qdr)] {level|ragged|skiplevel|regular} USING levelrel
[INHIERARCHY inhvs] LEVELORDER levelvs)
Cause: The wrong object type or the wrong object definition was specified.
Action: Change the object type or use the correct object definition.
ORA-36020: (XSHIERCK03) The definition of hierarchy workspace object over
number is inconsistent.
Cause: The definition of the hierarchy was inconsistent.
Action: Change the definition of the hierarchy.
ORA-36021: (XSHIERCK12) The format of the HIERCHECK function is:
HIERCHECK(relation [STATUS|NOSTATUS|valueset] [MULTIPATH]
[CONSISTENT] [{BALANCED|STAR_CONSISTENT} levelrelation]) Or
HIERCHECK(aggmap [MULTIPATH] [CONSISTENT])
Cause: The wrong object type was specified.
Action: Change the object to a RELATION or AGGMAP.
ORA-36022: (XSHIERCK04) Valuesets specified in the HIERCHECK command
must be scalar. workspace object is dimensioned.
Cause: The HIERCHECK command specified a dimensioned valueset.
Action: Specify a scalar valueset in its place.
ORA-36024: (XSHIERCK05) Valueset workspace object must contain values of one
of the extra dimensions of relation workspace object.
Cause: The HIERCHECK command specified a valueset over an invalid
dimension.
Action: Specify a valueset containing values of one of the self-relation's extra
dimensions (the dimensions in the relation's dimension list, minus the self-related
dimension itself).
20-32 Oracle Database Error Messages
ORA-36025: (XSHIERCK06) The level dimension of the level relation workspace
object is the same as the relation dimension workspace object.
Cause: The level dimension was the same as the relation dimension.
Action: Change the definition of the level relation.
ORA-36026: (XSHIERCK07) Level relation workspace object is not dimensioned by
relation dimension workspace object.
Cause: The level relation was not dimensioned by the relation dimension.
Action: Change the definition of the level relation.
ORA-36027: (XSHIERCK08) Hierarchy workspace object is not balanced.
Cause: The current hierarchy was not balanced.
Action: Change the hierarchy to balanced.
ORA-36028: (XSHIERCK09) Hierarchy workspace object has multiple paths from
number to number.
Cause: The current hierarchy had multiple paths.
Action: Remove multiple paths from the hierarchy.
ORA-36034: (XSMHIERCK00) One or more loops have been detected in
relationship workspace object over workspace object. The last number of the
items are number.
Cause: A relation was used that had loops in it. There were more items involved
than could be reported.
Action: Correct the relation so that it does not contain loops.
ORA-36035: (XSMHIERCKREL) One or more loops have been detected in
workspace object. number items involved are number.
Cause: A relation was used that had loops in it.
Action: Correct the relation so that it does not contain loops.
ORA-36036: (XSMHIERCK01) One or more loops have been detected in
relationship workspace object over workspace object. The number items
involved are number.
Cause: A relation was used that had loops in it.
Action: Correct the relation so that it does not contain loops.
ORA-36145: (SETPROP01) The property "%1" cannot be set for measure "%2".
Cause: A property name was given that is not one of the allowed properties to be
set.
Action: Specify one of the legal property names.
ORA-36154: (XSMXAGGR01) workspace object is not a data variable.
Cause: An object was specified on the Aggregate command line that was not a
variable
Action: Specify a variable instead
ORA-36155: (XSMXAGGRFROM) workspace object must be a variable or formula
of a similar data type to workspace object to be used with FROM, or a TEXT
variable or formula to be used with FROMVAR.
Cause: The user specified an illegal variable for use with FROM or FROMVAR on
the AGGREGATE command line
ORA-33000 to ORA-37999 20-33
Action: Specify a legal variable instead
ORA-36157: (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you
must also specify the AUTOUPDATE keyword.
Cause: The user specified AUTOCOMMIT but not AUTOUPDATE on the
AGGREGATE command line, which is illegal
Action: Either also specify AUTOUPDATE or don't specify AUTOCOMMIT
ORA-36160: (XSMXAGGR04) You cannot use string on scalar VARIABLE
workspace object.
Cause: The user tried to run the AGGREGATE or AGGCOUNT command or
function on a scalar variable.
Action: Specify a dimensioned variable instead
ORA-36161: (XSAGGRRUVCV) Aggregation variable workspace object cannot have
itself as a COUNTVAR.
Cause: The user specified the same variable as both an aggregation variable and a
COUNTVAR
Action: Specify a different COUNTVAR
ORA-36162: (XSMXAGGR05) COUNTVAR variable workspace object must be of
type INTEGER, not string.
Cause: The user specified a non-INTEGER variable as a COUNTVAR for
aggregation
Action: Redefine the COUNTVAR to be an INTEGER
ORA-36164: (XSMXAGGR07) When using the COUNTVAR clause, the number of
variables to be aggregated (number) must match the number of COUNTVAR
variables (number).
Cause: The user specified a COUNTVAR clause to the AGGREGATE command,
but the number of COUNTVAR variables specified did not match the number of
variables to be aggregated
Action: Specify a separate COUNTVAR for each variable
ORA-36165: (XSAGGCNTPROP) Variable workspace object cannot have both an
AGGCOUNT and the $COUNTVAR property.
Cause: An attempt was made to add the $COUNTVAR property to a variable
which already had an AGGCOUNT, or vice versa.
Action: Delete the already existing $COUNTVAR property or AGGCOUNT first.
ORA-36166: (XSMXAGGR08) workspace object is not a VARIABLE.
Cause: An attempt was made to perform an AGGREGATE or other action on an
object which is not a variable.
Action: Specify a variable instead.
ORA-36167: (XSAGGRFORM) workspace object is an illegal AGGMAP for
aggregating a FORMULA.
Cause: The user attempted to aggregate a FORMULA using an AGGMAP that is
not valid for aggregating FORMULAs. The AGGMAP must specify
PRECOMPUTE(NA) for all relation lines and must not specify any caching.
Action: Correct the AGGMAP so it is legal for aggregating a FORMULA.
20-34 Oracle Database Error Messages
ORA-36168: (XSMXAGGR10) COUNTVAR variable workspace object must have
the same dimensionality as workspace object
Cause: The user specified a COUNTVAR variable which is missing at least one
dimension of the aggregation variable
Action: Specify a COUNTVAR variable which has at least as many base
dimensions as the aggregation variable
ORA-36170: (XSMXAGGR12) The data type of the WEIGHT workspace object must
be numeric or BOOLEAN, not string.
Cause: The user specified a WEIGHT variable or formula which wasn't numeric
or boolean
Action: Specify a numerical or boolean weight instead
ORA-36174: (XSMXAGGR23) workspace object must be either a VARIABLE, a
RELATION or a FORMULA.
Cause: The user specified something that was not a variable, a relation or a
formula as a weight for AGGREGATE
Action: Specify a valid variable, relation or formula instead
ORA-36176: (XSMXAGGR25) Relation workspace object must be a one-dimensional
self-relation to be used as a weight for AGGREGATE.
Cause: The user specified an illegal relation as a weight. The relation might have
been multidimensional, not a self-relation, or not a relation over one of the bases of
the aggregation variable.
Action: Specify a valid self relation over one of the bases of the aggregation
variable.
ORA-36178: (XSAGGR01) To be used with AGGREGATE, AGGMAP workspace
object must be declared with the AGGMAP command.
Cause: The user used the ALLOCMAP command to define the AGGMAP, so the
AGGMAP can only be used with the ALLOCATE command, or the AGGMAP has
no contents attached to it.
Action: Use the AGGMAP command to define the AGGMAP.
ORA-36179: (XSNOAGM) No AGGMAP was specified for VARIABLE workspace
object.
Cause: The user used the AGGREGATE command without specifying an
AGGMAP on the command line, with a variable which had no $AGGMAP
property.
Action: Specify an AGGMAP on the AGGREGATE command line, or add the
$AGGMAP property to the variable in question.
ORA-36180: (XSAGGR08) AGGREGATE cannot function because there is a
permission clause associated with variable workspace object.
Cause: When using AGGREGATE, only simple permissions and permissions on
base dimensions are valid.
Action: Remove the permissions clause from the variable causing problems.
ORA-36181: A VARIABLE cannot have both the $AGGREGATE_FROM and
$AGGREGATE_FROMVAR properties applied to it.
Cause: The user attempted to add both the $AGGREGATE_FROM and
$AGGREGATE_FROMVAR properties to a single variable.
ORA-33000 to ORA-37999 20-35
Action: Remove the existing property before applying the new one.
ORA-36182: (XSAGGR09) Could not locate a value for variable number in measure
dimension workspace object.
Cause: A measure dimension was supplied in the AGGMAP, but a position for
the variable was not found in it.
Action: Add a position for the variable in the measure dimension.
ORA-36184: (XSAGGR10) You do not have sufficient permissions for the variable
workspace object.
Cause: The user lacked the permissions necessary for the aggregation variable.
Action: Remove the restricting permissions from the variable or base dimension.
ORA-36185: (XSAGGR11) workspace object does not have any AGGCOUNT
information.
Cause: User attempted an operation (such as the AVERAGE aggregation operator
or the AGGCOUNT function) that requires a variable to have AGGCOUNT
information on a variable that does not.
Action: Define the variable using the WITH AGGCOUNT clause, or use the
CHGDFN ADD AGGCOUNT command to enable AGGCOUNT for the variable.
ORA-36188: (XSAGGR16) AGGREGATE read a value less than 1 out of
COUNTVAR variable workspace object. Either the values of the COUNTVAR
variable are stored improperly, or there is problem in AGGREGATE. If no one
has modified the values in this COUNTVAR, contact Oracle customer support.
Cause: Either someone improperly changed the COUNTVAR variable, or
AGGREGATE has an error.
Action: Set the COUNTVAR variable to NA before starting AGGREGATE. If you
previously set the COUNTVAR variable to NA, then contact Oracle OLAP
technical support.
ORA-36198: (XSAGGR33) Cannot aggregate over COMPRESSED COMPOSITE
workspace object using AGGMAP workspace object because the operator
variable with more than 1 line dimensions is not supported for bases of a
COMPRESSED COMPOSITE.
Cause: The user specified an aggregation the operator variable with more than 1
line dimensions that is not supported by COMPRESSED COMPOSITES.
Action: Use a MODEL for the calculation, or use an uncompressed COMPOSITE.
ORA-36200: (XSAGGR34) AGGREGATE operator string requires a WEIGHTBY
clause, but ARGS variable workspace object did not specify one.
Cause: The given operator requires a WEIGHT specification, but the ARGS
variable did not supply one.
Action: Modify the ARGS variable to specify a weight for the operation.
ORA-36201: (XSAGGR35) Cannot aggregate workspace object(partition workspace
object) because the subpartition is itself partitioned.
Cause: Attempted to aggregate an intermediate partition of a variable with nested
partitioning.
Action: rerun the aggregate command seperately for each ultimate partition or
just for the variable as a whole
ORA-36202: (XSAGOP01) 'number' is not a valid aggregation operator.
20-36 Oracle Database Error Messages
Cause: An invalid string was provided for an aggregation operator.
Action: Check the spelling of the operator to make sure you are specifying a valid
one.
ORA-36204: (XSAGOP04N) In AGGMAP workspace object, the NAOPERATOR
string must be HFIRST, HLAST or HEVEN.
Cause: An invalid NAOPERATOR was specified.
Action: Specify HFIRST, HLAST or HEVEN.
ORA-36206: (XSAGOP04R) In AGGMAP workspace object, REMOPERATOR string
must be MIN, MAX, FIRST, LAST, HFIRST or HLAST.
Cause: An invalid REMOPERATOR was specified.
Action: Specify one of the legal operators.
ORA-36208: (XSAGOP05N) In AGGMAP workspace object, you can only specify
NAOPERATOR string with the PROPORTIONAL or EVEN operators, not
string.
Cause: The user specified an NAOPERATOR when you were not using
PROPORTIONAL or EVEN.
Action: Remove the NAOPERATOR clause from the RELATION line.
ORA-36210: (XSAGOP05R) In AGGMAP workspace object, you can only specify
the REMOPERATOR string with the PROPORTIONAL, EVEN, or HEVEN
operators, not string.
Cause: The user specified a REMOPERATOR without using PROPORTIONAL,
EVEN, or HEVEN.
Action: Remove the REMOPERATOR clause from the RELATION line.
ORA-36212: (XSAGOP06) In AGGMAP workspace object, you can only specify the
MIN, MAX, FLOOR, and CEILING arguments while using the
PROPORTIONAL operator, not string.
Cause: The user specified MIN, MAX, FLOOR, or CEILING when using an
operator other than PROPORTIONAL.
Action: Remove the incorrect argument from the RELATION line.
ORA-36220: (XSLPDSC01) All dimensions in LIST number are also in the IGNORE
clause.
Cause: One of the dimension lists in the dimension loop descriptor had no base
dimensions except those in the IGNORE list. This leaves no dimensions for
looping over.
Action: Fix the dimension loop descriptor.
ORA-36221: (XSLPDSC02) LIST number and LIST number have different base
dimensions.
Cause: The base dimensions of the dimension lists given in the loop descriptor do
not match.
Action: Ensure that each dimension list has the same set of looping base
dimensions. If necessary, use IGNORE within a lists to discard base dimensions
that should not be looped.
ORA-36222: (XSLPDSC03) duplicate IGNORE or DENSE information for
dimension workspace object
ORA-33000 to ORA-37999 20-37
Cause: An IGNORE or DENSE list in a dimension loop descriptor included the
dimension twice, included two different valuesets of the dimension, or includes
the dimension and a valueset of the dimension.
Action: Only use the dimension or a valueset of the dimension once in an
IGNORE or DENSE list.
ORA-36223: (XSLPDSC04) object workspace object in IGNORE or DENSE list has
illegal type
Cause: An IGNORE or DENSE list in a dimension loop descriptor included and
object that was not a dimension or a valueset, was a conjoint dimension, or was a
dimensioned valueset.
Action: Only use simple dimensions and undimensioned valuesets in the
IGNORE or DENSE list.
ORA-36224: (XSLPDSC05) workspace object is not a loop dimension
Cause: An IGNORE or DENSE list in a dimension loop descriptor referenced a
dimension (or a valueset of a dimension) that was not a base dimension of the
loop dimension list.
Action: Remove the dimension or valueset from the IGNORE or DENSE list.
ORA-36225: (XSLPDSC06) A LOOP AGGMAP list must contain an aggmap object,
followed by one or more variables and/or dimensions.
Cause: An invalid AGGMAP list was specified. Either to few objects were
specified, or an incorrect type of object was used.
Action: Specify a valid AGGMAP list consisting of an aggmap object, followed by
one or more variables and/or dimensions.
ORA-36226: (XSLPDSC07) The syntax of the $LOOP property on formula
workspace object is incorrect.
Cause: Unrecognized contents in the $LOOP property of a formula in the table
function measure list.
Action: Restrict the contents of the $LOOP property to valid elements (other than
OPTIMIZED and MEASURES) of the table function LOOP directive.
ORA-36230: (XSANALYZ00) object workspace object cannot be used in the
ANALYZE command
Cause: An object that cannot be analyzed was used in the ANALYZE command.
Action: Analyze VARIABLES, RELATIONS, DIMENSIONS, or SURROGATES.
ORA-36231: (XSANALYZ01) object workspace object cannot be used in the
INHIERARCHY clause
Cause: An invalid INHIERARCHY object was referenced.
Action: Use either a VALUESET or boolean VARIABLE.
ORA-36232: (XSANALYZ02) a level list was specified when a language dimension
was present
Cause: A level list dimension was specified when a language dimension was
present.
Action: Remove the USING clause.
ORA-36233: (XSANALYZ03) the dimensionality of object workspace object does not
match the ANALYZE command
20-38 Oracle Database Error Messages
Cause: The dimensionality of the object did not match the ANALYZE command
syntax used.
Action: Match the ANALYZE syntax to the dimensionality of the specified object.
ORA-36234: (XSANALYZ04) all objects in the current status of the NAME
dimension must have the same dimensionality when used with the ANALYZE
command
Cause: The dimensionality of at least one of the objects listed in the NAME
dimension does not match the rest of the objects.
Action: Make sure all objects listed in the NAME dimension have the same
dimensionality.
ORA-36236: (XSANALYZ06) the AW format must be 11.0.0.0 or higher to use the
ANALYZE command
Cause: The AW version is less than 11.0.0.0
Action: Make sure the compatible mode is 11.0.0.0 or higher and upgrade the AW
ORA-36237: (XSANALYZ07) analytic workspace string.string must be attached RW
or EXCLUSIVE mode
Cause: The analytic workspace was already attached RO or MULTI mode.
Action: Detach the analytic workspace.
ORA-36238: (XSANALYZ08) object string.string does not exist
Cause: The object name does not exist
Action: Check the spelling and case of the object name
ORA-36258: (XSAGINFO00) When the AGGMAPINFO function is called,
workspace object must be an AGGMAP.
Cause: The AGGMAPINFO function was called with an object that is not an
AGGMAP.
Action: Modify the call to AGGMAPINFO to specify an AGGMAP object.
ORA-36260: (XSAGHIERPART00) Aggregating from partition %J to partition %J
over hierarchy workspace object creates an increase in sparsity.
Cause: In the partition creation / aggmap creation a situation developed such that
when aggregating over a particular dimension of the aggmap a partition boundary
was crossed such that the sparsity of the target partition included dimensions that
were not in the sparsity of the source partition. Since the process of aggregation
always densifies rather than sparsifying this is an extremely suboptimal design
and it is not supported by the aggregate system.
Action: Set up your partitioning such that for any partition boundary the source
and target partitions of the aggregation will always move towards denser
partitions. For any child (c) and any parent (p) where (c) and (p) are in different
partitions it must be the case that the parent partition contains no dimension in the
composite that the child partition does not contain in its composite.
ORA-36261: (XSAGPARTDEP00) Can not Aggregate PARTITION TEMPLATE %J
because the path of aggregation would recursively enter partition %J.
Cause: The partitioning scheme was such that while aggregating there exists a cell
(m) such that both one of its descendants and one of its ancestors are both in the
referenced partition, while (m) is in a different partition.
Action: Change the partitioning scheme.
ORA-33000 to ORA-37999 20-39
ORA-36266: (XSCGMDLAGG00) Invalid context for the AGGREGATION function
Cause: The AGGREGATION function was used outside of the MODEL context.
Action: Use AGGREGATION only in a model.
ORA-36267: (XSCGMDLAGG09) workspace object has no dimensions, so it cannot
have a qualified data reference.
Cause: A dimension qualification was specified for a valueset with no
dimensions.
Action: Remove the qualification.
ORA-36268: (XSCGMDLAGG01) 'string' is not a valid dimension value.
Cause: The AGGREGATION parameter list included a value that does not exist in
the MODEL dimension that contains the target of the AGGREGATION
Action: Specify only values from the appropriate MODEL dimension
ORA-36269: (XSCGMDLAGG10) 'workspace object' does not exist or is not a
dimension.
Cause: A nonexistent or invalid object was specified as a QDR dimension.
Action: Specify existing dimensions only.
ORA-36270: (XSCGMDLAGG03) The parameter list for the AGGREGATION
function includes duplicate values.
Cause: One or more duplicate values appeared in the AGGREGATION parameter
list.
Action: Remove the duplication.
ORA-36271: (XSCGMDLAGG11) workspace object is not in the dimension list of
valueset workspace object.
Cause: A QDR dimension was specified that does not appear in the valueset's
dimension list.
Action: Specify only dimensions in the valueset's dimension list.
ORA-36272: (XSCGMDLAGG04) 'workspace object' is not a valid operator for the
AGGREGATION function.
Cause: An invalid AGGREGATION operator was specified.
Action: Correct the invalid operator.
ORA-36273: (XSCGMDLAGG12) Dimension workspace object appears more than
once in the QDR.
Cause: A dimension was specified more than once in the QDR.
Action: Remove the duplication.
ORA-36274: (XSCGMDLAGG05) The operator used in this equation needs a weight
variable.
Cause: An invalid weight variable was specified.
Action: Correct the invalid weight variable.
ORA-36275: (XSCGMDLAGG13) string is not a valid workspace object.
Cause: A value was specified that does not exist in the QDR dimension.
Action: Specify an existing value.
20-40 Oracle Database Error Messages
ORA-36276: (XSCGMDLAGG06) The current operator does not need a weight
variable.
Cause: A weight variable was specified in a context that does not support it.
Action: Remove the weight variable.
ORA-36278: (XSCGMDLAGG07) workspace object does not exist or is not valueset.
Cause: A nonexistent or invalid object was specified where a valueset is required.
Action: Specify an existing valueset only.
ORA-36280: (XSCGMDLAGG08) Valueset workspace object does not contain values
of any dimension of the current model.
Cause: AGGREGATION specified a valueset of a dimension not listed in a
DIMENSION statement for the current model.
Action: Add the valueset's dimension to the model's DIMENSION list, or choose
a different valueset.
ORA-36290: (EIFMAKEF14) You cannot export object workspace object, because
EIFVERSION is set to number. That version does not support string strings.
Cause: The user tried to export a NUMBER dimension to an EIF file with the
EIFVERSION option set to a number less than 80000. Versions previous to that
eversion do not support NUMBER dimensions.
Action: A NUMBER dimension cannot be used in a version of older than 9.2.0. If
ORA-36312: (PHYS00) workspace object must be a dimension, dimensioned
variable or relation.
Cause: The user specified an invalid OLAP object while attempting to use the
PHYSICAL function
Action: Specify a valid object
ORA-36313: (PHYS03) The VALUE option of PHYSICAL cannot be applied to a
variable.
Cause: the VALUE argument to PHYSICAL was supplied for a variable.
Action: remove VALUE or specify a relation or dimension.
ORA-36314: (PHYS01) workspace object must be a dimension, relation or variable.
Cause: The user specified an invalid OLAP object while attempting to use the
PHYSICAL command
Action: Specify a valid object
ORA-36315: (PHYS04) You must specify the VALUE option for scalar relation
workspace object.
Cause: The VALUE argument to PHYSICAL was omitted for a scalar relation
Action: specify VALUE or choose a dimensioned relation
ORA-36316: (PHYS02) Relation workspace object must be a single-dimensional
relation that relates one INTEGER dimension to another.
Cause: The user specified an invalid relation while attempting to use the
PHYSICAL command
Action: Specify a valid relation
ORA-36340: (SNSYN130) The format of the PARTITIONCHECK function is:
PARTITIONCHECK(aggmap, partition_template)
ORA-33000 to ORA-37999 20-41
Cause: Bad syntax
Action: Correct syntax
ORA-36342: (SNSYN200) The format of the CLEAR command is: CLEAR [ ALL |
STATUS ] [ AGGREGATES | CHANGES | PRECOMPUTES |
NONPRECOMPUTES | CACHE ] FROM var1 [var2, var3...] [USING aggmap]
Cause: The syntax for the CLEAR command was invalid.
Action: Modify your syntax using the correct format.
ORA-36376: (XSAGZERO) AGGREGATE attempted to divide by zero. Set
DIVIDEBYZERO to YES if you want NA to be returned as the result of a
division by zero.
Cause: A calculation in the current AGGREGATE command attempted to divide
by zero as a result of an AVERAGE, WAVERAGE, HAVERAGE or HWAVERAGE
operation.
Action: Either fix the data, or set DIVIDEBYZERO to YES to return NA instead of
signaling an error.
ORA-36378: (XSAGTHRWEIGHT) While running AGGREGATE with multiple
threads, the weight variable workspace object specified by your ARGS variable
workspace object must exist in the same analytic workspace as your AGGMAP
workspace object.
Cause: While running AGGREGATE in threaded mode, you attempted to specify
a WEIGHT variable in another analytic workspace.
Action: Use a weight variable from the same analytic workspace as the aggmap
and rollup variable.
ORA-36380: (AGGRECURSE) AGGREGATE was called recursively, which is not
allowed.
Cause: A model, NATRIGGER, or other object called the AGGREGATE function
or command while another AGGREGATE function or command was already in
progress.
Action: Modify your objects so that they do not need to have two AGGREGATE
commands or functions executing at once.
ORA-36389: (XSAGPARTDEP01) Can not aggregate from PARTITION number into
PARTITION number due to increasing sparsity along DIMENSION %J.
Cause: The user is attempting to use partitions as a means of sparsity control,
however they have set up their partitions in a manner that simply makes no sense.
It is a simple fact that during aggregation data becomes more dense, not less
dense, and yet their partitions indicate the opposite.
Action: Modify the partition template add the specified dimension into the source
composite, or removing it from the target composite.
ORA-36391: (XSMXCLEA01) When CLEAR is used with the STATUS keyword or
an AGGMAP, workspace object must be dimensioned identically to workspace
object.
Cause: The user specified objects whose dimensionality didn't match
Action: Break up the CLEAR command into multiple commands where the
dimensionality of the objects matches
ORA-36392: (XSMXCLEA02) When using CLEAR with the PRECOMPUTES or
NONPRECOMPUTES options, you must specify an AGGMAP.
20-42 Oracle Database Error Messages
Cause: The user didn't specify an AGGMAP with the CLEAR command.
Action: specify an aggmap by adding a USING phrase to the CLEAR command,
or attach a '$AGGMAP' property to the variable.
ORA-36393: (XSMXCLEA03) When using the AGGREGATES, CHANGES or
CACHE options, you must specify the ALL keyword.
Cause: The user didn't use the ALL keyword when using CHANGES or CACHE.
Action: Specify the ALL keyword.
ORA-36394: (XSMXCLEA04) When using CLEAR on the AGGMAP workspace
object, CACHE is the only valid directive.
Cause: The user attempted to CLEAR an AGGMAP using a directive other than
CACHE.
Action: Amend the CLEAR line to only use the CACHE keyword with
AGGMAPs.
ORA-36395: (XSMXCLEA05) To CLEAR ALL AGGREGATES from workspace
object, you must specify an AGGMAP.
Cause: The CLEAR command could not determine how the variable was
aggregated because the variable is not dimensioned by a compressed composite.
Action: Specify an aggmap by adding a USING phrase to the CLEAR command,
or attach a '$AGGMAP' property to the variable.
ORA-36397: (XSSPROPNA) The value of property string cannot be NA.
Cause: The user tried to set a system-reserved property on an OLAP object to NA
Action: Set the property to a non-NA value
ORA-36398: (XSSPROP01) Property name 'number' is invalid because only
system-reserved property names can begin with '$'.
Cause: The user attempted to add a property which starts with $ but is not a
reserved property name
Action: Remove the $ from the property name
ORA-36399: (XSSPROPDTYPE) The data type of property string must be string.
Cause: The user tried to set a system-reserved property on an OLAP object to a
value with an illegal datatype
Action: Set the property with the proper datatype
ORA-36400: (XSSPROP02) workspace object is not a valid variable name.
Cause: Not a valid variable name
Action: Change to a valid variable name
ORA-36401: (XSSPROPOTYPE) Property string may only be applied to objects of
type string.
Cause: The user applied a reserved property name to an incorrect object type
Action: Apply the property to the correct object
ORA-36402: (XSSPROP03) The property '$string' requires a leading "$" because it is
a system-reserved property name.
Cause: The user tried to specify a property name which is reserved, but did not
use a leading $
Action: Either add a leading $ or choose another property name
ORA-33000 to ORA-37999 20-43
ORA-36403: (XSBADSPROP) number is an illegal value for system-reserved
property string on workspace object.
Cause: The user tried to specify an illegal value for a special property
Action: Specify a legal value.
ORA-36404: (XSSPROP04) Property string cannot be applied to an undimensioned
(scalar) TEMPORARY variable.
Cause: The user applied a reserved property name to an incorrect object type
Action: Apply the property to the correct object
ORA-36405: (XSSPROP05) Property ignored for object workspace object:
Cause: A property was ignored during import.
Action: Refer to the message that follows this one and correct the error it
describes.
ORA-36406: (VCACHE00) 'number' is an invalid value for the VARCACHE option.
The only permissible values are 'SESSION', 'VARIABLE', and 'NONE'.
Cause: The user tried to assign an invalid value to the VARCACHE option
Action: Assign one of the valid values
ORA-36410: (VCACHE03) 'number' is an invalid value for the $VARCACHE
property. The only permissible values are 'DEFAULT', 'SESSION', 'VARIABLE',
and 'NONE'.
Cause: The user tried to assign an invalid value to the $VARCACHE property on
a variable
Action: Assign one of the valid values
ORA-36608: (XSAGHOVERFLOW) The depth of the hierarchies encountered while
processing a composite dimension in AGGREGATE caused a counter overflow.
Cause: The depth of the hierarchies that are part of a composite exceeded 4 billion
levels during the merge.
Action: Reduce the number of levels in the hierarchies, reduce the number of
dimensions in the composite, or do not aggregate over all dimensions at once.
ORA-36610: (XSLMS00) Unable to locate a message file for OLAP message: value
Cause: An internal OLAP DML program in the EXPRESS Analytic Workspace
failed to retrieve a user message.
Action: Contact support.
ORA-36612: (XSLMS01) invalid OLAP message number: value
Cause: An internal OLAP DML program in the EXPRESS Analytic Workspace
attempted to retrieve a non-existent message.
Action: Contact support.
ORA-36616: (XSAGMODHIER01) There is a cycle formed by MODEL workspace
object and other embedded or containing models with the same dimension,
workspace object.
Cause: Inclusion of a dynamic model formed a cycle in the named dimension.
Action: Edit the models involving this dimension to remove the cycle.
ORA-36617: (XSAGMODHIER02) There is a self-cycle equation in MODEL
workspace object.
20-44 Oracle Database Error Messages
Cause: The model for relation modification included a self-cycle equation.
Action: Remove the self-cycle equation from the model.
ORA-36618: (XSAGMODDIM00) workspace object is not a valid dynamic model for
AGGMAP.
Cause: The model failed one of the following tests: 1) only one dimension (aside
from LAG/LEAD dimensions); 2) assignment to dimension values only; 3) a single
simple solution block; 4) no time-series functions with variable step values.
Action: Edit the model so that it conforms to the above requirements.
ORA-36620: (XSAGMODDIM01) MODEL workspace object cannot find the
matching embedded model.
Cause: AGGMAP ADD model could not find the matching embedded model.
Action: Add the matching embedded model to the AGGMAP.
ORA-36621: (XSAGMODDIM02) You cannot AGGREGATE the individual
partition using static model workspace object because a partition dimension or
its deriver workspace object appears in the equation of the step or simultaneous
block.
Cause: An attempt was made to AGGREGATE the individual partition using the
static model with the partition dimension in the equation of the step or
simultaneous block.
Action: AGGREGATE the variable instead of the individual partition.
ORA-36622: (XSAGMODLIST00) workspace object cannot be added to the
AGGMAP workspace object because it is not a valid MODEL.
Cause: An object specified in AGGMAP ADD was not a model.
Action: Specify the name of a model.
ORA-36626: (XSAGMODLIST02) MODEL workspace object was skipped because
there is already a MODEL by that name attached to AGGMAP workspace object.
Cause: An attempt was made to add the same model to the AGGMAP twice.
Action: None required.
ORA-36628: (XSAGMODLIST03) MODEL workspace object could not be added to
AGGMAP workspace object.
Cause: The dimension of the model did not match a hierarchy of the aggmap.
Action: Add a RELATION statement to the AGGMAP for that dimension.
ORA-36630: (XSDUNION00) An empty base dimension list was specified in the
concat dimension definition.
Cause: An empty concat dimension list was specified.
Action: Specify a valid list of dimensions when defining a concat dimension.
ORA-36632: (XSDUNION01) The concat dimension workspace object is not
currently defined as UNIQUE.
Cause: Attempt was made to CHGDFN a concat, which is already non-unique, to
NOT UNIQUE.
Action: Since the concat is already non-unique, this command is unnecessary.
ORA-36634: (XSDUNION02) INTEGER dimension workspace object cannot be
used as a concat dimension base.
ORA-33000 to ORA-37999 20-45
Cause: The user cannot specify INTEGER base dimensions when defining a
concat dimension.
Action: Change the datatype of the INTEGER base dimension, or omit it from the
concat.
ORA-36635: (XSDUNION03) The base dimension workspace object has an invalid
datatype for use in a UNIQUE concat definition.
Cause: Base dimensions of a unique concat must have TEXT or ID datatypes.
Action: Specify a valid list of dimensions when defining a unique concat
dimension.
ORA-36636: (XSDUNION04) The unique concat dimension workspace object
cannot be changed to NOT UNIQUE, because it is a base of at least one other
unique concat dimension.
Cause: A non-unique concat dimension cannot be used as a base of a dependent
unique concat.
Action: CHGDFN any dependent unique concat dimensions to NOT UNIQUE
and retry.
ORA-36637: (XSDUNION05) The concat dimension cannot be defined as UNIQUE
because it has a non-unique concat base dimension workspace object.
Cause: A non-unique concat dimension cannot be used as a base of a dependent
unique concat.
Action: CHGDFN any non-unique concat base dimensions to UNIQUE and retry.
ORA-36638: (XSDUNION17) Concat dimension workspace object cannot be
changed to UNIQUE because it has a non-unique concat base dimension
workspace object.
Cause: A non-unique concat dimension cannot be used as a base of a dependent
unique concat.
Action: CHGDFN any non-unique concat base dimensions to UNIQUE and retry.
ORA-36639: (XSDUNION18) UNIQUE cannot be applied to this concat dimension
because leaves workspace object and workspace object share the value number.
Cause: Unique concat base dimensions cannot contain duplicate values.
Action: Use MAINTAIN RENAME to change one of the duplicate values and
retry.
ORA-36640: (XSDUNION19) Concat dimension workspace object cannot be
changed to UNIQUE because base dimension workspace object does not have a
TEXT or ID datatype.
Cause: Base dimensions of a unique concat must have TEXT or ID datatypes.
Action: None
ORA-36641: (XSDUNION20) The concat dimension must be defined as UNIQUE
because base dimension workspace object contains custom member values.
Cause: The UNIQUE keyword was not specified in the concat dimension
definition, and is required if any of its base dimensions contain custom member
values.
Action: Define the concat as UNIQUE, or remove all base custom member values.
ORA-36642: (XSDUNION06) Concat dimension list contains duplicate leaf
dimension workspace object.
20-46 Oracle Database Error Messages
Cause: Duplicate concat leaf dimension was found.
Action: Remove duplicate concat base dimensions and retry.
ORA-36643: (XSDUNION21) Concat dimension workspace object cannot be
changed to NOT UNIQUE because it contains custom member values.
Cause: Only UNIQUE concat dimensions can have custom member values or
base dimensions which contain custom member values.
Action: Remove all custom member values from the concat and all of its bases,
and retry.
ORA-36644: (XSDUNION07) Concat dimension workspace object contains a
previously detected leaf dimension.
Cause: Concat dimension contains a previously detected leaf dimension.
Action: None
ORA-36646: (XSDUNION08) Only concat dimensions can be redefined as
UNIQUE. workspace object is not a concat dimension.
Cause: UNIQUE keyword was used with an invalid object.
Action: Retry without the UNIQUE keyword.
ORA-36648: (XSDUNION09) Concat dimension workspace object is already defined
as UNIQUE.
Cause: Attempt to change a concat dimension to UNIQUE, but it is already
UNIQUE.
Action: None
ORA-36650: (XSDUNION10) Concat dimension workspace object cannot be
changed to UNIQUE. Leaves workspace object and workspace object share the
value number.
Cause: Unique concat base dimensions cannot contain duplicate values.
Action: Use MAINTAIN RENAME to change one of the duplicate values and
retry.
ORA-36652: (XSDUNION11) workspace object is not a string type dimension.
Cause: The CHGDFN BASE ADD command is only valid for concat dimensions.
Action: None
ORA-36664: (XSDPART02) You must specify a partitioning method and one or more
partition dimensions when defining a PARTITION TEMPLATE.
Cause: User tried to define a PARTITION TEMPLATE without a PARTITION BY
clause.
Action: Add a PARTITION BY clause.
ORA-36665: (XSDPART03) workspace object is not in the dimension list of the
PARTITION TEMPLATE.
Cause: While defining a partition template, user attempted to specify a partition
dimension that is not a dimension of the partition template itself.
Action: Choose a partition dimension from among the dimensions of the partition
template.
ORA-36666: (XSDPART04) workspace object is not a concat dimension.
ORA-33000 to ORA-37999 20-47
Cause: User tried to define a partition template with PARTITION BY CONCAT(...
dim ...) where dim is not a concat dimension.
Action: Only concat dimensions can serve as partition dimensions with CONCAT
partitioning. Choose a different partition dimension.
ORA-36667: (XSDPART05) string is not a legal CONCAT partition.
Cause: User attempted to use RANGE or LIST syntax in defining a CONCAT
partition template.
Action: Use CONCAT partition syntax.
ORA-36668: (XSDPART06) string is not a legal RANGE partition.
Cause: User attempted to use CONCAT or LIST syntax in defining a RANGE
partition template.
Action: Use RANGE partition syntax.
ORA-36669: (XSDPART07) string is not a legal LIST partition.
Cause: User attempted to use RANGE or CONCAT syntax in defining a LIST
partition template.
Action: Use LIST partition syntax.
ORA-36670: (XSDPART08) workspace object is an INTEGER or NTEXT dimension,
or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT
dimensions cannot be used as partition dimensions.
Cause: User attempted to define a partition template partitioned by an INTEGER
or NTEXT dimension or a concat containing an NTEXT leaf.
Action: Either pick a different partition dimension, or redefine the dimension to
use a different datatype.
ORA-36671: (XSDPART09) Leaves of workspace object have different datatypes. A
partition dimension cannot have more than one datatype when RANGE
partitioning is used.
Cause: User attempted to define a range partition template with a concat partition
dimension, and the concat had two leaf dimensions with different datatypes.
Action: Pick a different partition dimension.
ORA-36672: (XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only
have a single partition dimension.
Cause: User attempted to define a RANGE or LIST partition template with more
than one partition dimension.
Action: Remove all but one of the dimensions from the PARTITION BY
RANGE(...) or PARTITION BY LIST(...) clause of the partition template definition.
ORA-36673: (XSDPART11) Use simple leaf values to identify concat dimension
values in a VALUES LESS THAN clause, rather than the <LEAF: VALUE>
format.
Cause: When defining a RANGE partition template with a concat dimension for
the partition dimension, the user attempted to define a range using the <LEAF:
VALUE> format of a concat dimension value.
Action: Use just the leaf value. Instead of "VALUES LESS THAN <leaf: value>",
just say, "VALUES LESS THAN value".
ORA-36674: (XSDPART12) Invalid dimension value starting at string.
20-48 Oracle Database Error Messages
Cause: When defining a RANGE or LIST partition template, the user specified an
invalid value in a VALUES LESS THAN or VALUES clause. An "invalid value" can
be one of two things: a value whose datatype does not match the partition
dimension's datatype, or a non-constant value.
Action: Modify the offending VALUES LESS THAN or VALUES phrase.
ORA-36676: (XSDPART14) Missing dimension list for string.
Cause: User attempted to define a CONCAT partition template, and didn't supply
a list of dimensions for one of the partition definitions.
Action: Give a dimension list for each partition.
ORA-36677: (XSDPART15) Duplicate value in value lists of number and number
Cause: In a LIST PARTITION TEMPLATE definition, a value appeared in more
than one value list, or more than once within a single value list.
Action: List each value only once.
ORA-36678: (XSDPART16) workspace object is missing from one or more partition
dimension lists.
Cause: In the definition of a partition template, one of the partitions had a
dimension list that did not contain all the dimensions of the partition template.
Action: Add the offending dimension to the partition's dimension list, or delete it
from the partition template's dimension list. If using CONCAT partitioning and
the missing dimension is a partition dimension, add to the partition dimension list
any leaf of the partition dimension or any concat of leaves of the partition
dimension.
ORA-36679: (XSDPART17) workspace object contains a leaf (workspace object) that
is not part of the partition dimension workspace object.
Cause: In the definition of a CONCAT partition template, one of the partitions
was dimensioned by a dimension that is "concat-related" to a partition dimension,
meaning it shares some leaves with the partition dimension, but it contained some
leaves that are not in the partition dimension.
Action: Either modify the dimensionality of the partition template to include a
concat dimension that contains all the desired leaves, or pick a different dimension
for the partition.
ORA-36680: (XSDPART18) workspace object is not a dimension of the PARTITION
TEMPLATE.
Cause: In the definition of a partition template, one of the partitions was
dimensioned by a dimension that was not given in the dimension list of the
partition template.
Action: Remove the offending dimension from the partition's dimension list, or
add it to the partition template's dimension list.
ORA-36681: (XSDPART19) Partitions string and string are out of order.
Cause: In the definition of a range partition template, a partition with a lower
range boundary was listed after a partition with a higher range boundary.
Action: Alter the order of the partition definition list.
ORA-36682: (XSDPART20) Partition name string appears twice.
Cause: User gave a list of AW partitions in which some partition name appeared
twice.
Action: Remove all but the first instance of the partition name from the list.
ORA-33000 to ORA-37999 20-49
ORA-36683: (XSDPART21) Partition string dimensioned by more than one
composite.
Cause: It is illegal to define a partition template in which one of the partitions is
dimensioned by more than one composite.
Action: Make sure that the partition template being defined has at most one
composite per partition.
ORA-36684: (XSDPART22) You cannot rename values of DIMENSION workspace
object because it is the partition dimension of RANGE PARTITION TEMPLATE
workspace object
Cause: User attempted to rename a value of a dimension that serves as the
partition dimension of some RANGE or LIST partition template.
Action: It is not possible to rename values in such a dimension without deleting
all RANGE and LIST partition templates that are partitioned by it.
ORA-36685: (XSDPART23) Only CONCAT partition templates can be
subpartitioned.
Cause: User attempted to define a RANGE or LIST partition template with one or
more partitions dimensioned by another partition template.
Action: Use only regular dimensions and composites to dimension each partition
of the RANGE or LIST template.
ORA-36686: (XSDPART24) Value number is not in partition number.
Cause: User attempted to reorganize a list partition template by removing a value
from some partition's list, but the value was not in the list.
Action: Ensure that the given values match the given partition.
ORA-36687: (XSDPART25) You cannot use compressed composite workspace object
to dimension multiple partitions of the partition template, because its
dimension list includes the PARTITION BY dimension workspace object.
Cause: The specified PARTITION BY dimension also occurred in the dimension
list of a compressed composite used to dimension multiple partitions.
Action: Ensure that no PARTITION BY dimension occurs among the bases of the
compressed composite used to dimension multiple partitions.
ORA-36688: (NTEXTCNV00) Error during conversion from TEXT to NTEXT.
Cause: An unknown character set conversion error occurred when converting a
TEXT value to an NTEXT value.
Action: Unknown.
ORA-36691: (NTEXTCNV02) Invalid escape sequence in argument to UNISTR
function: string.
Cause: The user called the UNISTR function on a string that had an invalid escape
sequence. The only valid escape sequences in UNISTR are 1.) an escape-escape
sequence, and 2.) an escape, followed by exactly four hexadecimal digits.
Action: Make sure that all escape sequences in UNISTR arguments are exactly
four hexadecimal digits. To represent codepoints whose value is less than 0x1000,
use preceding zeros. WRONG: 0x10; RIGHT: 0x0010.
ORA-36692: (XSRELGID24) A level relation must be specified for the GROUPSET
and ROLLUP options of GROUPINGID.
Cause: level relation was not specified.
20-50 Oracle Database Error Messages
Action: Specify a level relation.
ORA-36693: (XSRELGID25) INHIERARCHY cannot be specified with the
GROUPSET and ROLLUP options of GROUPINGID.
Cause: INHIERARCHY option was specified.
Action: Remove INHIERARCHY option.
ORA-36694: (XSRELTBL01) The value cannot be added to dimension workspace
object.
Cause: Unknown.
Action: Check the context and permission for dimension maintenance.
ORA-36695: (XSRELGID26) The length of GID dimension status is number. The
length of LEVEL dimension status is number.
Cause: GID dimension status did not match LEVEL dimension status.
Action: Change either GID dimension status or LEVEL dimension status.
ORA-36696: (XSRELTBL02) QDR dimension workspace object should not be the
related dimension of the relation.
Cause: An ineligible dimension was specified in the Qualified Data Reference
Action: Do not attempt to qualify this dimension.
ORA-36698: (XSRELTBL03) QDR dimension workspace object should be in the
dimension list that dimensions the relation.
Cause: The named dimension was not in the relation's dimension list.
Action: Select only dimensions that are in the relation's dimension list.
ORA-36700: (XSRELTBL04) Dimension workspace object cannot be qualified more
than once.
Cause: The same dimension was specified more than once in the QDR.
Action: Specify each QDR dimension only once.
ORA-36702: (XSRELTBL05) The format of the HIERHEIGHT function is:
HIERHEIGHT(relation [,] level) level >= 1.
Cause: The HIERHEIGHT function was specified incorrectly.
Action: Make sure the format is correct.
ORA-36704: (XSRELTBL06) workspace object should be dimensioned by workspace
object.
Cause: The level relation is not dimensioned by the source relation dimension.
Action: Make sure the level relation has the correct definition.
ORA-36706: (XSRELTBL07) workspace object should be dimensioned by workspace
object and one level dimension.
Cause: The destination relation has the wrong definition.
Action: Make sure the destination relation has the correct dimensions.
ORA-36708: (XSMXALLOC00) Variable workspace object must be dimensioned to
be used by the ALLOCATE command.
Cause: The user supplied an undimensioned (scalar) variable to the ALLOCATE
command.
Action: Use a dimensioned variable.
ORA-33000 to ORA-37999 20-51
ORA-36710: (XSMXALLOC01) TARGETLOG variable workspace object must be
dimensioned identically to TARGET variable workspace object.
Cause: The user attempted to execute ALLOCATE with mismatched TARGET
and TARGETLOG variables
Action: Use TARGET and TARGETLOG variables with matching dimensionality.
ORA-36712: (XSMXALLOC02) Relation workspace object must be a
one-dimensional self-relation to be used as a SOURCE or BASIS with
ALLOCATE.
Cause: The user specified an invalid source or basis relation on the ALLOCATE
command line.
Action: Modify the relation to be a one-dimensional self-relation.
ORA-36714: (XSMXALLOC03) TARGETLOG variable workspace object must have
the same data type as TARGET variable workspace object.
Cause: The user specified a TARGETLOG variable that had a different data type
from the TARGET variable.
Action: Use TARGETLOG and TARGET variables with an identical data type.
ORA-36718: (XSALLOC00) You do not have the necessary permissions to use
AGGMAP workspace object.
Cause: The user did not have sufficient permissions to run the ALLOCATE
command
Action: Change to a user ID with the appropriate permissions, or use objects that
you have permission to use.
ORA-36720: (XSALLOC01) To be used with ALLOCATE, your AGGMAP workspace
object must be defined with the ALLOCMAP command.
Cause: The user used the AGGMAP command to define the AGGMAP, so either
the AGGMAP can only be used with the AGGREGATE command, or the
AGGMAP has no contents attached to it.
Action: Use the ALLOCMAP command to define the AGGMAP.
ORA-36722: (XSALLOC02) In AGGMAP workspace object, you specified an NA or
ZERO sourceval but supplied formula workspace object as your source for
ALLOCATE.
Cause: The user requested that source values be modified during the allocation,
but that is not possible when using a formula source.
Action: Either use a VARIABLE source or remove the SOURCEVAL specification
for your ALLOCMAP.
ORA-36726: (XSALERR00) The character 'character' is not a valid format specifier
for the ALLOCATE error log.
Cause: The user specified an invalid formatter in the ALLOCERRLOGHEADER
or ALLOCERRLOGFORMAT options.
Action: Correct the option to have a valid format.
ORA-36728: (XSALERR01) While performing the ALLOCATE command with
AGGMAP workspace object, the error logging limit of number was exceeded.
Cause: The user specified an ERRORLOG MAX value in the ALLOCMAP, but
more errors were encountered while performing the allocation.
20-52 Oracle Database Error Messages
Action: Either set ERRORLOG NOSTOP, reduce the allocation errors, or increase
the ERRORLOG MAX setting
ORA-36735: A value exceeded the MAX specification
Cause: .
Action: None
ORA-36740: A CHILDLOCK was detected in your valueset
Cause: .
Action: None
ORA-36761: (XSLANGDM01) Analytic workspace string already contains a
dimension (%J) with the string property.
Cause: An attempt was made to apply this property to more than one dimension
in the AW.
Action: Remove the property from the named dimension and try the command
again.
ORA-36762: (XSLANGDM02) You cannot modify the string property of %J because
analytic workspace string is attached in MULTI mode.
Cause: An attempt was made to add or delete a $DEFAULT_LANGUAGE
property in an AW attached in multiwriter mode.
Action: Attach the AW in a different mode.
ORA-36763: (XSAGGCNTMOVE01) Aggregation variable workspace object cannot
have itself as an AGGCOUNT.
Cause: An attempt was made to turn a variable into its own AGGCOUNT.
Action: Select a different AGGCOUNT variable.
ORA-36764: (XSAGGCNTMOVE02) AGGCOUNT variable workspace object must
be of type INTEGER, not string.
Cause: An attempt was made to create a non-INTEGER AGGCOUNT.
Action: Select an INTEGER AGGCOUNT variable.
ORA-36765: (XSAGGCNTMOVE03) A string aggregation variable cannot have a
string AGGCOUNT.
Cause: The specified AGGCOUNT variable did not have the same permanence as
the aggregation variable.
Action: Select an AGGCOUNT variable with the same TEMPORARY or
PERMANENT attribute as the aggregation variable.
ORA-36766: (XSAGGCNTMOVE04) workspace object cannot be used as an
AGGCOUNT because it has an AGGCOUNT.
Cause: The specified AGGCOUNT variable had its own AGGCOUNT
Action: Select a different variable, or remove the AGGCOUNT using CHGDFN.
ORA-36767: (XSAGGCNTMOVE05) workspace object cannot be used as an
AGGCOUNT while there are permissions applied to it.
Cause: The specified AGGCOUNT variable had its own permissions distinct from
those on the aggregation variable.
Action: Select a different AGGCOUNT variable, or remove the permissions. In
some cases this may require an UPDATE before the command can succeed.
ORA-33000 to ORA-37999 20-53
ORA-36768: (XSAGGCNTMOVE06) An aggregation variable and its AGGCOUNT
must have the same base dimensions.
Cause: An AGGCOUNT variable was specified with different base dimensions
than the aggregation variable.
Action: Select an AGGCOUNT variable with exactly the same base dimensions as
the aggregation variable.
ORA-36778: (XSPGTRLOW) The amount of available temporary storage is still low.
Free some temporary storage immediately. You can do so, for example, by
UPDATING or DETACHING an analytic workspace.
Cause: Ran out of temporary tablespace storage.
Action: Increase the amount of temporary tablespace storage.
ORA-36779: Invalid parameter value.
Cause: The specified value for OLAP_PAGE_POOL_SIZE initialization parameter
was out of range. OLAP_PAGE_POOL_SIZE must be between 2097152 and
2147483647. Addditionally, you cannot use a fixed-size OLAP page pool with
multiple tablespace block sizes. OLAP_PAGE_POOL_SIZE remains unmodified.
Action: None
ORA-36800: (XSTBLFUNC00) The OLAP_TABLE function can only have a single
LOOP statement within the LIMITMAP
Cause: The OLAP table function given used more than one LOOP statement.
Action: It is currently impossible to specify more than one LOOP composite,
either remove one of the statements (and loop densely over relevant dimensions),
or create a new composite that encompasses both loops and have a single loop
statement refer to that.
ORA-36802: (XSTBLFUNC01) The OLAP_TABLE function must contain a
DATAMAP that executes a FETCH command or a LIMITMAP.
Cause: There is no limitmap on the table function and either the datamap does
not contain a fetch, or it errored before the fetch was called.
Action: Check the datamap for errors, make sure that it executes a fetch
statement, if it is not intended to execute the fetch then make sure that the table
function has a valid limitmap.
ORA-36804: (XSTBLFUNC02) The OLAP_TABLE function encountered an error
while parsing the LIMITMAP.
Cause: Invalid LIMITMAP syntax, or the name resolution failure of an
ANALYTIC WORSKPACE OBJECT.
Action: Check the syntax of the limit map, check that the OLAP_TABLE function
refers to a valid analytic workspace, check that all analytic workspace objects
within the limitmap actually exist within the analytic workspace
ORA-36806: (XSTBLFUNC03) The OLAP_TABLE function refers to an invalid ADT
attribute: string.
Cause: The limitmap refers to a matching of ADT attribute to AW object, but the
ADT attribute is not an element of the specified ADT table. Most commonly this is
a typo.
Action: Add the attribute to the ADT, correct the LIMITMAP, or remove the
reference from the LIMITMAP.
20-54 Oracle Database Error Messages
ORA-36808: (XSTBLFUNC04) The OLAP_TABLE function LEVELREL clause
cannot declare number ADT fields from number AW fields.
Cause: The limitmap has a levelrel clause which has a different number of values
in the list to the right of the FROM than it has to the left.
Action: Change the limitmap so that there is a 1:1 mapping of adt and aw
elements.
ORA-36810: (XSTBLFUNC05) Analytic workspace object number does not exist.
Cause: The limitmap refers to a non-existent aw object.
Action: Change the limitmap or define the object
ORA-36812: (XSTBLFUNC06) Invalid Syntax at '?'.
Cause: The limitmap has a question mark character outside the context of a string.
Action: Fix the limitmap
ORA-36814: (XSTBLFUNC07) The datatype of the column used in the ROW2CELL
clause of a LIMITMAP must be RAW(16).
Cause: Datatype of column used in ROW2CELL clause of a LIMITMAP is not
RAW(16).
Action: Change datatype to RAW(16).
ORA-36815: (XSTBLFUNC08) The OLAP_TABLE has attempted to use an AW
single row function with the aw_attach parameter set to DURATION QUERY.
Cause: The OLAP_TABLE aw_attach parameter was set to DURATION QUERY.
Action: Change the OLAP_TABLE aw_attach parameter to DURATION SESSION.
ORA-36816: (XSTBLFUNC09) The workspace object dimension is of datatype string
which does not support custom member upserts.
Cause: Custom members were attempted to be added via an upsert to a
dimension that does not support them
Action: Disable the AW Hash optimization for this query
ORA-36817: (XSTBLFUNC10) The LIMITMAP LOOP clause specifies an invalid
type of object. workspace object must be a DIMENSION or COMPOSITE.
Cause: An invalid type of object was specified in the LOOP clause.
Action: Correct the LOOP clause.
ORA-36818: (XSTBLFUNC11) A LIMITMAP DIMENSION clause specifies an
invalid type of object. workspace object must be a DIMENSION.
Cause: An invalid type of object was specified in the DIMENSION clause.
Action: Correct the DIMENSION clause.
ORA-36819: (XSTBLFUNC12) workspace object cannot be used in a LIMITMAP
string clause.
Cause: An invalid type of object was specified in a LIMITMAP clause.
Action: Correct the LIMITMAP clause.
ORA-36820: (XSLMINFO00) The LIMITMAPINFO function encountered an error
while parsing the LIMITMAP.
Cause: Invalid LIMITMAP syntax.
Action: Correct the syntax of the limit map.
ORA-33000 to ORA-37999 20-55
ORA-36821: (XSJPUSH00) An error occurred while attempting to push a join of 2
AW tables.
Cause: Unknown.
Action: Re-execute the query with parameter _optimizer_aw_join_push_enabled
= FALSE.
ORA-36825: (XSTBLFUNC13) An error occurred expanding the cube_name
argument in the OLAP table function
Cause: Incorrect metadata or invalid cube name
Action: Correct the metadata.
ORA-36826: (XSTBLFUNC14) OLAP C Looper is disabled by event 37395
Cause: init.ora event 37395 includes level 8 which disables the OLAP C looper
Action: Remove event level 8 and use explicit FETCH function for OLAP_TABLE
ORA-36830: (XSLMGEN00) Object string.string does not exist
Cause: The object does not exist
Action: Check view token for errors
ORA-36831: (XSLMGEN01) View token cannot be NA
Cause: A NA was passed as the view token
Action: Pass in a valid view token
ORA-36832: (XSLMGEN02) View token cannot be greater than 4000 bytes
Cause: A view token was greater than 4000 bytes
Action: Pass in a view token less than 4000 bytes
ORA-36833: (XSLMGEN03) View token cannot be blank
Cause: A blank was passed as the view token
Action: Pass in a valid view token
ORA-36834: (XSLMGEN04) Column tag is greater than 30 bytes
Cause: A value greater than 30 bytes was passed as the column tag
Action: Pass in a column tag of 30 bytes or less
ORA-36835: (XSLMGEN05) Dimension string.string hierarchy string level string is
missing a COLUMNNAME property value
Cause: The COLUMNNAME property has no value
Action: Add a value to COLUMNNAME property
ORA-36836: (XSLMGEN06) The dimensionality of object string.string is different
than the view token
Cause: The dimensionality of the cube does not match the view token
Action: Check view token for unrelated hierarchies clauses
ORA-36837: (XSLMGEN07) Object owner string is different than string
Cause: The object owners are different
Action: Make the object owners match
ORA-36838: (XSLMGEN08) Dimension string.string attribute string is missing a
COLUMNNAME property value
20-56 Oracle Database Error Messages
Cause: The COLUMNNAME property has no value
Action: Add a value to COLUMNNAME property
ORA-36839: (XSLMGEN09) Cube string.string measure string is missing a
COLUMNNAME property value
Cause: The COLUMNNAME property has no value
Action: Add a value to COLUMNNAME property
ORA-36840: (XSLMGEN10) Cube string.string has no measures
Cause: The cube has no measures
Action: Add a measure to the cube
ORA-36841: (XSLMGEN11) Dimension string.string was not found
Cause: The view token referenced a dimension that does not exist
Action: Pass in a dimension that does exist
ORA-36842: (XSLMGEN12) Hierarchy string.string.string was not found
Cause: The view token referenced a hierarchy that does not exist
Action: Pass in a hierarchy that does exist
ORA-36843: (XSLMGEN13) Dimension string.string hierarchy string is missing a
PHYSICALNAME property value
Cause: The property PHYSICALNAME has no value
Action: Populate the property PHYSICALNAME with a value
ORA-36844: (XSLMGEN14) Dimension string.string is missing a string property
value
Cause: The dimension is missing a required property
Action: Check dimension property values
ORA-36845: (XSLMGEN15) Owner is greater than 30 bytes
Cause: The owner passed is greater than 30 bytes
Action: Pass in an owner that is 30 bytes or less
ORA-36846: (XSLMGEN16) AW name is greater than 30 bytes
Cause: The AW name passed is greater than 30 bytes
Action: Pass in an AW name that is 30 bytes or less
ORA-36847: (XSLMGEN17) AW name is blank
Cause: The AW name passed is blank
Action: Pass in an AW name that has a value
ORA-36848: (XSLMGEN18) Object name string is different than string
Cause: The object names are different
Action: Make the object names match
ORA-36849: (XSLMGEN19) AW owner does not match View token owner
Cause: The AW owner does not match the View token owner
Action: Match AW ower to View token object owner
ORA-36850: (XSLMGEN20) View token string is not correct
ORA-33000 to ORA-37999 20-57
Cause: The view token is not correct
Action: Check view token syntax for errors
ORA-36861: (XSTFRC01) SQL Cache ID parameter is invalid or missing.
Cause: SQL Cache ID parameter is required to identify SQL cache to query
Action: Supply a valid SQL Cache ID. Normally, users should not call OLAP
Random Access Cursor table function themselves and therefore should not
encounter this error.
ORA-36862: (XSTFRC02) Column number for this SQL Cache must be between 1
and number. Specified column number number is invalid.
Cause: Column Map references a column number that is greater than the
maximum column number in SQL Cache
Action: Reference a correct column number. Normally, users should not call
OLAP Random Access Cursor table function themselves and therefore should not
encounter this error.
ORA-36871: (XSFTDSC01) Object string cannot be used to define a column in a
LIMITMAP.
Cause: The object cannot define a column in LIMITMAP most likely because it is
of a wrong type such as, for example, a Worksheet.
Action: Remove the reference from the LIMITMAP.
ORA-36872: (XSTFDSC02) Column type specifier cannot be used when the table
function data type is specified.
Cause: Column type can only be used with implicitly-specified table functions
Action: Remove column type from reference from the LIMITMAP or remove the
explicit table function data type specification.
ORA-36873: (XSTFDSC03) Column type must be specified explicitly.
Cause: Missing column type specification.
Action: Please, make sure to specify a column type in COLUMN MAP. Normally,
users should not call OLAP Random Access Cursor table function themselves and
therefore should not encounter this error.
ORA-36874: (XSTFDSC04) Expression string cannot be used to define a column in a
LIMITMAP.
Cause: The expression cannot define a column in LIMITMAP most likely because
it is of a wrong type such as, for example, a Worksheet.
Action: Remove the reference from the LIMITMAP.
ORA-36875: (XSTFDSC05) LIMITMAP is missing or is not a string literal.
Cause: Table functions that have an automatic ADT require LIMITMAP to be a
string literal.
Action: Either specify ADT for the table function or specify LIMITMAP as a string
literal.
ORA-36876: (XSTFDSC06) The column datatype string is not supported in OLAP
table functions.
Cause: The object type layer does not support column datatype.
Action: Use a supported column datatype.
20-58 Oracle Database Error Messages
ORA-36881: (XSSRF00) The OLAP DML ROW2CELL function can only be used in a
LIMITMAP.
Cause: Using the ROW2CELL function outside of the LIMITMAP.
Action: Remove use of the ROW2CELL function.
ORA-36882: (XSSRF01) The second parameter of an AW single row function cannot
be NULL.
Cause: The second parameter of the AW single row function was NULL
Action: Pass a valid OLAP DML expression as the second parameter of the AW
single row function
ORA-36883: (XSSRF02) The first parameter of an AW single row function cannot be
NULL.
Cause: The first parameter of the AW single row function was NULL
Action: Make sure the column specified in the LIMITMAP ROW2CELL clause is
the first parameter of the AW single row function.
ORA-36884: (XSSRF03) The value of the first parameter of the AW single row
function is incorrect.
Cause: The column specified in the LIMITMAP ROW2CELL clause was not the
first parameter of the AW single row function.
Action: Make sure the column specified in the LIMITMAP ROW2CELL clause is
the first parameter of the AW single row function.
ORA-36885: (XSSRF04) Error rewriting OLAP DML expression. Column name too
big
Cause: The column name specified in the OLAP DML expression was larger than
30 bytes.
Action: Make sure the column name specified in the OLAP DML expression is
less than or equal to 30 bytes.
ORA-36886: (XSSRF05) Error rewritting OLAP DML expression. Rewritten
expression is greater than number bytes
Cause: The rewritten OLAP DML expression was larger than the output buffer.
Action: Create a smaller OLAP DML expression.
ORA-36887: (XSSRF06) Error rewriting OLAP DML expression. Column name
string is not a valid ADT column.
Cause: The column name passes does not exist.
Action: Only reference columns that exist.
ORA-36902: (XSAGDNGL43) In AGGMAP workspace object, the MODEL
workspace object is not a model over a base dimension of the AGGMAP.
Cause: Model may include equations others than dimension values, or blocks
other than simple blocks.
Action: Make sure model only includes the simple blocks with dimension values.
ORA-36904: (XSAGDNGL44) In AGGMAP workspace object, RELATION
workspace object occurs after a dynamic model. The dynamic model must be the
last calculation within the AGGMAP.
Cause: Before the current relation, dynamic model exists.
Action: Make sure the dynamic model is the last statement.
ORA-33000 to ORA-37999 20-59
ORA-36910: (XSAGDNGL47) In AGGMAP workspace object, DYNAMIC MODEL
workspace object can only edit the top level of its matching relation hierarchy.
Cause: The model attempted to edit a child node in the relation hierarchy.
Action: Remove this attempt from the model definition.
ORA-36912: (XSAGDNGL48) In AGGMAP workspace object, MODEL workspace
object cannot be simultaneous.
Cause: The aggmap contained a simultaneous model.
Action: Change the model definition so that it is no longer simultaneous.
ORA-36913: (XSAGDNGL49) In AGGMAP workspace object, LOAD_STATUS
object workspace object must be an undimensioned VALUESET over the
relation dimension.
Cause: The object refered to by the LOAD_STATUS clause of the aggmap wasn't
an undimensioned valueset over the related dimension
Action: Change the aggmap definition so that it doesn't refer to an invalid object
ORA-36914: (XSAGDNGL50) In AGGMAP workspace object, LOAD_STATUS
valueset workspace object contains both a child and its ancestor.
Cause: The LOAD_STATUS valueset is not allowed to contain both a dimension
value and an ancestor of that value.
Action: Perform a limit remove ancestors on the valueset and confirm that the
result matches the intended load.
ORA-36920: (XSVPMVTOPART01) workspace object cannot become anonymous
because it has properties.
Cause: The OLAP DML command would result in a named object becoming an
anonymous object, but the object had one or more properties associated with it.
Action: Remove the properties using the PROPERTY command. In some cases an
UPDATE may be required before the command can proceed.
ORA-36921: (XSVPMVTOPART02) workspace object and workspace object are not
in the same analytic workspace.
Cause: The OLAP DML command requires certain objects to be in the same
analytic workspace, and the command string specified objects from two different
analytic workspaces.
Action: If more than one analytic workspace is attached to the session, make sure
that the object names given in the command are unique across all attached analytic
workspaces. Use qualified object names (QON's) if necessary.
ORA-36922: (XSVPMVTOPART03) workspace object is the target of an external
partition of a partitioned variable.
Cause: An attempt was made to perform some prohibited operation on a variable
which is itself a partition of some other variable.
Action: If desired, use the CHGDFN command to DROP the partition from the
partitioned variable, and then run the command again.
ORA-36923: (XSVPMVTOPART04) workspace object is not a LIST or RANGE
PARTITION TEMPLATE.
Cause: The user ran a command that only operates on a LIST or RANGE partition
template (or a variable dimensioned by a LIST or RANGE partition template) on
some other kind of analytic workspace object.
20-60 Oracle Database Error Messages
Action: Rerun the command on a LIST or RANGE partition template or a variable
dimensioned by a LIST or RANGE partition template.
ORA-36924: (XSVPMVTOPART05) workspace object is not in a COMPOSITE.
Cause: The OLAP DML command expected that the variable would be
dimensioned by a composite containing the specified dimension, the specified
dimension within a composite.
Action: Rerun the command on some variable is dimensioned by a composite
containing the specified dimension.
ORA-36930: Cannot start a recursive call to Oracle OLAP because a ROLLBACK
past an UPDATE to an attached analytic workspace has been performed.
Cause: ROLLBACK past the UPDATE of one of the attached Analytic Workspaces
was called. A recursive Oracle OLAP call cannot be made until the control returns
to the initial OLAP call and the affected Analytic Workspaces detached.
Action: Change the called SQL procedure to avoid the ROLLBACK
ORA-36950: (XSFCAST22) The list of string values cannot have more than number
members. You supplied number.
Cause: There are more than the maximum number of OFFSET or PERIODICITY
values.
Action: Remove some of the values.
ORA-36951: (XSFCAST28) The ALLOCLAST parameter cannot be set to YES unless
PERIODICITY specifies more than one cycle.
Cause: ALLOCLAST was set to YES when PERIODICITY specified a single value
rather than a list of nested cycles.
Action: Set ALLOCLAST to FALSE (the default), or specify more than one value
for PERIODICITY (in the form of a parenthesized list).
ORA-36952: (XSFCAST23) You cannot specify a cycle number when querying the
string forecasting option.
Cause: A cycle number was specified in a call to FCQUERY to retrieve forecast
data not related to a cycle.
Action: Remove the cycle specification from the call to FCQUERY.
ORA-36954: (XSFCAST24) The cycle number must be between 1 and number. You
specified number.
Cause: A cycle number less than 1 or greater than the maximum value was
specified in a call to FCQUERY.
Action: Specify a number in the indicated range.
ORA-36956: (XSFCAST25) There are only number PERIODICITY values. You
cannot specify more OFFSET values.
Cause: More OFFSET values were specified than PERIODICITY values.
Action: Supply only as many OFFSETs as there are PERIODICITY values.
ORA-36958: (XSFCAST26) The OFFSET value for cycle number cannot be greater
than the cycle's PERIODICITY, which is number. You specified number.
Cause: The OFFSET for a cycle exceeded the PERIODICITY for that cycle.
Action: Supply an OFFSET less than or equal to the PERODICITY for the
corresponding cycle.
ORA-33000 to ORA-37999 20-61
ORA-36960: (XSFCAST27) The value of the string expression must be an odd
number. You specified number.
Cause: An even number was given for an option that requires an odd number.
Action: Supply an odd number or let the option default.
ORA-36961: Oracle OLAP is not available.
Cause: The user attempted to utilize functionality found only in Oracle OLAP, but
OLAP has not been enabled in the executable.
Action: Install the Oracle OLAP option
ORA-36962: (XSRELTBL08) string is not a valid workspace object.
Cause: The specified value does not exist in the dimension.
Action: Specify an existing value of the dimension.
ORA-36963: (XSRELTBL16) INHIERARCHY object workspace object should be a
valid valueset or boolean variable.
Cause: Invalid valueset or variable was specified.
Action: Specify a valid valueset or variable.
ORA-36964: (XSRELTBL09) workspace object is not a valid level relation.
Cause: The specified level relation was not consistent with the parentage
hierarchy.
Action: Fix one or both of the relations involved so that all parents are at a higher
level than their children.
ORA-36965: (XSRELTBL17) Invalid LEVELORDER valueset workspace object.
Cause: Invalid LEVELORDER valueset was specified.
Action: Specify a valid valueset.
ORA-36966: (XSRELTBL10) workspace object must be a dimension.
Cause: The qualified object must be a dimensions.
Action: Remove the named object from the QDR.
ORA-36967: (XSRELTBL18) Invalid INHIERARCHY valueset workspace object.
Cause: Invalid valueset was specified.
Action: Specify a valid valueset.
ORA-36968: (XSRELTBL11) Invalid relation workspace object.
Cause: Non-object or an object other than a RELATION was specified as source or
destination.
Action: Specify RELATION objects.
ORA-36969: (XSRELTBL19) Merged family relation cannot take INHIERARCHY
option.
Cause: INHIERARCHY option was specified.
Action: Remove INHIERARCHY option.
ORA-36970: (XSRELTBL12) workspace object must be a self-relation.
Cause: The specified source relation was not a self-relation.
Action: Specify a self-relation as the source.
20-62 Oracle Database Error Messages
ORA-36971: (XSRELTBL19) Merged family relation cannot take LEVELORDER
option.
Cause: LEVELORDER option was specified.
Action: Remove LEVELORDER option.
ORA-36972: (XSRELTBL13) Relation workspace object must be dimensioned by
workspace object.
Cause: Destination relation is not dimensioned by source relation dimension.
Action: Give a correct destination relation.
ORA-36974: (XSRELTBL14) workspace object is not a BOOLEAN variable
dimensioned by all the dimensions of the hierarchy.
Cause: The named variable had either the wrong data type or the wrong
dimensions.
Action: Specify a BOOLEAN variable dimensioned by all the dimensions of the
hierarchy.
ORA-36975: (XSRELTBL15) You must specify a USING clause naming a relation
with same level dimension as LEVELORDER valueset workspace object.
Cause: USING was omitted from the HIERHEIGHT command, or specified a
relation containing values of a different dimension than the LEVELORDER
valueset.
Action: Provide a USING clause naming a relation containing values from the
correct level dimension. --------------------------------------------------------------
ORA-36976: (XSRELGID00) Invlid GROUPINGID destination relation or variable
workspace object.
Cause: Non-Object or invalid relation or invlid variable.
Action: Specify the valid relation or variable.
ORA-36977: (XSRELGID17) The GROUPINGID command does not support
hierarchies with more than 126 levels.
Cause: The user specified a hierarchy with more than 126 levels.
Action: Decrease the number of levels in the hierarchy.
ORA-36978: (XSRELGID01) workspace object must be a self-relation.
Cause: Source relation is not a self-relation.
Action: Specify a self-relation as the source relation.
ORA-36979: (XSRELGID18) Property number can only be set by the GROUPINGID
command.
Cause: You tried to set the $GID_DEPTH property.
Action: Stop to set the $GID_DEPTH property.
ORA-36980: (XSRELGID02) Variable workspace object must have a numeric data
type.
Cause: The destination variable does not have a numeric data type.
Action: Make sure the variable is numeric.
ORA-36981: (XSRELGID19) The format of the GROUPINGID function is:
GROUPINGID(gidrel1 [gidrel2]...)
Cause: Bad syntax
ORA-33000 to ORA-37999 20-63
Action: Correct syntax
ORA-36982: (XSRELGID03) The destination variable/relation workspace object
must be dimensioned by all dimensions of the source relation workspace object
that have more than one value in status.
Cause: Destination variable/relation does not have enough dimensionality to
hold the result from the multi-dimensional source relation.
Action: Either limit the status of hierarchy dimensions or redefine the destination
variable/relation with the extended dimensionality
ORA-36983: (XSRELGID20) The groupingid relation workspace object repeats.
Cause: The groupingid relation repeated.
Action: Remove the duplicated groupingid relation.
ORA-36985: (XSRELGID21) The source relation can be omitted only when using
both surrogate GID and level order valueset.
Cause: Source relation was not specified.
Action: Specify the source relation or both surrogate gid and level order valueset.
ORA-36986: (XSRELGID05) Relation workspace object must be dimensioned by
workspace object.
Cause: The destination relation is not dimensioned by the dimension of the source
relation.
Action: Redefine the destination relation or choose another relation with the
correct dimensionality.
ORA-36988: (XSRELGID06) The related dimension of relation workspace object
must be of type NUMBER.
Cause: The related dimension of the destination relation has the wrong data type.
Action: Redefine the destination relation or choose another relation whose related
dimension is of type NUMBER.
ORA-36989: (XSRELGID23) GROUPSET and ROLLUP options in GROUPINGID
require the destination relation.
Cause: Either variable or surrrogate dimension was specified as destination.
Action: Specify the destination relation.
ORA-36990: (XSRELGID07) The level relation workspace object should be
dimensioned by a level dimension.
Cause: The level relation is not dimensioned by a level dimension.
Action: Redefine the level relation or choose another relation with the correct
dimensionality.
ORA-36991: (XSRELGID08) The level relation and level order valueset provide
inconsistent level mappings.
Cause: There is a conflict between the hierarchy/level relation and the level order
valueset.
Action: Choose objects that do not conflict.
ORA-36992: (XSRELGID09) A level relation is needed to produce a surrogate
dimension gid.
Cause: A level relation was not specified.
20-64 Oracle Database Error Messages
Action: Specify a level relation.
ORA-36993: (XSRELGID10) OBJECT workspace object must be a VARIABLE,
RELATION, or a numeric SURROGATE DIMENSION based on the level
dimension workspace object.
Cause: not a surrogate dimension, or the surrogate dimension is not based on the
level dimension.
Action: modify/change the surrogate dimension.
ORA-36994: (XSRELGID11) The SURROGATE DIMENSION workspace object
must be numeric.
Cause: The surrogate dimension is not numeric
Action: Change the surrogate dimension as numeric
ORA-36995: (XSRELGID12) There are duplicate values in the surrogate dimension
gid. Use the levelorder option to resolve the ambiguity.
Cause: more than 1 hierarchies in the current computing scope.
Action: use inhierarchy to limit
ORA-36996: (XSRELGID13) Valueset workspace object should be defined over
dimension workspace object.
Cause: Valueset doesn't match the dimension
Action: Change the valueset's dimension
ORA-36997: (XSRELGID14) For variable or relation grouping ids, a level relation is
needed when a level order valueset is specified.
Cause: no level relation exists with level order valueset.
Action: provide the level relation.
ORA-36998: (XSRELGID15) LEVEL ORDER VALUESET workspace object and
LEVEL RELATION workspace object have the different level dimensions.
Cause: either level order valueset or level relation has wrong level dimension.
Action: choose the correct level dimension
ORA-36999: (XSRELGID16) OBJECT workspace object is not a surrogate
dimension, a source relation must be specified when creating any non-surrogate
grouping id.
Cause: use variable/relation gid without providing the source relation
Action: use the surrogate or provide the source relation
ORA-37000: (NOTALIAS00) workspace object is not an ALIAS DIMENSION of
workspace object.
Cause: The user specified an object which is not alias dimension of the first
dimension
Action: Specify an alias dimension of the first dimension
ORA-37001: You have one or more attached but unupdated analytic workspaces.
Cause: The user has attempted to shut down OLAP, but they have active analytic
workspaces whose changes have not been saved.
Action: Either issue the update command to update the AWs, or pass TRUE as the
force parameter to dbms_aw.shutdown()
ORA-33000 to ORA-37999 20-65
ORA-37002: Oracle OLAP failed to initialize. Please contact Oracle OLAP technical
support.
Cause: A severe error occurred while initializing OLAP.
Action: Contact support (and possibly OLAP development) for help in debugging
the issue.
ORA-37003: (AWLISTALL01) number readers
Cause: used in AW(LISTALL) output formatting when %d is 0
Action: None
ORA-37004: (AWLISTALL02) number reader
Cause: used in AW(LISTALL) output formatting when %d is 1
Action: None
ORA-37005: (AWLISTALL03) number readers
Cause: used in AW(LISTALL) output formatting when %d is > 1
Action: None
ORA-37006: (AWLISTALL04) number writers
Cause: used in AW(LISTALL) output formatting when %d is 0
Action: None
ORA-37007: (AWLISTALL05) number writer
Cause: used in AW(LISTALL) output formatting when %d is 1
Action: None
ORA-37008: (AWLISTALL06) number writers
Cause: used in AW(LISTALL) output formatting when %d is > 1
Action: None
ORA-37010: (XSACQUIRE_DIFFAW) When using the CONSISTENT WITH clause,
all objects must come from the same analytic workspace.
Cause: The ACQUIRE command cannot keep objects from several workspaces
consistent with each other
Action: Omit the CONSISTENT WITH clause or make sure all objects being
acquired belong to the same analytic workspace.
ORA-37011: (XSACQUIRE_LOCKED) Object workspace object is locked by another
user.
Cause: Could not acquire (or acquire consistent) the object, since it is locked by
another user
Action: Try to acquire this object later
ORA-37012: (XSACQUIRE_TIMEOUT) Object workspace object is locked by
another user and the WAIT timed out.
Cause: Could not acquire (or acquire consistent) the object for a while, since it is
locked by another user
Action: Try to acquire this object later
ORA-37013: (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace
object, since doing so would cause a deadlock.
Cause: Waiting to acquire the object would cause a deadlock
20-66 Oracle Database Error Messages
Action: Release some other object that another user is waiting for and try to
acquire this object again.
ORA-37014: (XSACQUIRE_ACQUIRED) Object workspace object is already
acquired.
Cause: The object is already acquired
Action: Do not try to acquire this object again
ORA-37015: (XSACQUIRE_YNRESYNC) Object workspace object is ambiguously
listed to be acquired both with and without RESYNC.
Cause: The object is listed in with resync list and no resync list. Such usage is
ambiguous as to the user's intent on preserving or not preserving private changes.
Action: Do not list the object both with and without RESYNC
ORA-37016: (XSACQUIRE01) You must specify objects to acquire for the ACQUIRE
command.
Cause: A list of objects to acquire with or without resync is missing
Action: Specify the list of objects to acquire
ORA-37018: (XSACQUIRE03) Multiwriter operations are not supported for object
workspace object.
Cause: Multiwriter presently does not work for this object type
Action: Attach the AW in RW or EXCLUSIVE modes to modify this object.
ORA-37020: (XSMULTI01) Analytic workspace string is not in MULTI mode.
Cause: The workspace for an object is not in multiwriter mode. Hence, no
multiwriter operations are allowed on the objects in the workspace
Action: Attach the workspace in the multiwriter mode or do not use multiwriter
commands with it.
ORA-37021: (XSMULTI02) Object workspace object is not acquired.
Cause: The object must be acquired for this multiwriter operation
Action: Do not use this multiwriter operation on an object that is not acquired
ORA-37023: (XSMLTUPD01) Object workspace object cannot be updated without
dimension workspace object.
Cause: One cannot update an object if it is dimensioned by a maintained
dimension without updating that dimension or if the object is a relation and the
dimension is its target.
Action: Include the maintained dimension in the update list
ORA-37026: (XSMLTRESYNC01) Object workspace object cannot be resynced
without dimension workspace object.
Cause: One cannot resync an object if it is dimensioned by a maintained
dimension without updating that dimension or if the object is a relation and the
dimension is its target.
Action: Include the maintained dimension in the update list
ORA-37027: (XSMLTRESYNC02) Object workspace object cannot be resynced
without modified object workspace object because they share a modified
composite dimension.
Cause: When one resyncs an object that is dimensioned by a composite
dimension, the composite dimension is resynced automatically, dropping all new
ORA-33000 to ORA-37999 20-67
tuples. This cannot be done, however, if the automatic resync of the composite
dimension might cause data in an object that shares the composite dimension to
become NA.
Action: Resync both objects together. Alternatively, you can try to acquire the
other object (that will ensure that the composite dimension is locked in the latest
generation and will not be resynced when resyncing the first object), resync the
first object, and release the other object.
ORA-37028: (XSMLTRESYNC03) Object workspace object cannot be resynced
without modified object workspace object because they share a modified
dimension map.
Cause: When one resyncs an object that is dimensioned by a dimension map, the
dimension map is resynced automatically, dropping all changes. This cannot be
done, however, if the automatic resync of the dimension map might cause data in
an object that shares the dimension map to become NA.
Action: Resync both objects together. Alternatively, you can try to acquire the
other object (that will ensure that the dimensions map is locked in the latest
generation and will not be resynced when resyncing the first object), resync the
first object, and release the other object.
ORA-37030: (XSMLTMAINT01) You cannot maintain workspace object because it is
not ACQUIRED.
Cause: One cannot maintain a dimension in a multiwriter AW if it is not acquired.
Action: Acquire the dimension first.
ORA-37031: (XSMLTMAINT02) You cannot DELETE values of dimension
workspace object in MULTI mode.
Cause: DELETE is allowed in multiwriter mode only for SESSION dimension
members
Action: Attach the AW in a R/W mode and perform the DELETE operation
ORA-37032: (XSMLTMAINT03) You cannot MAINTAIN partition template
workspace object in MULTI mode.
Cause: User attempted to add or remove values from a LIST partition template's
lists while the AW containing the partition template was attached in multiwriter
mode.
Action: Do the maintenance in read only or read-write mode.
ORA-37035: (XSMLTDCL01) You can only DEFINE SESSION objects in analytic
workspace string because it is attached in MULTI mode.
Cause: Persistent object definition in multiwriter mode is not allowed.
Action: Do all persistent object definitions in read-write mode.
ORA-37036: (XSMLTDCL02) You cannot DELETE objects in analytic workspace
string because it is attached in MULTI mode.
Cause: One cannot delete objects in an analytic workspace attached in MULTI
mode.
Action: Do all object in read-only or read-write mode.
ORA-37037: (XSMLTDCL03) You cannot RENAME objects in analytic workspace
string because it is attached in MULTI mode.
Cause: One cannot rename objects in an analytic workspace attached in MULTI
mode.
20-68 Oracle Database Error Messages
Action: Do all persistent object maintenance in read-write mode.
ORA-37038: (XSMLTDCL04) You cannot change definitions of objects in analytic
workspace string because it is attached in MULTI mode.
Cause: One cannot used CHGDFN command on objects in an analytic workspace
attached in MULTI mode.
Action: Do all persistent object maintenance in read-write mode.
ORA-37039: (XSMLTDCL05) You cannot maintain triggers in analytic workspace
string because it is attached in MULTI mode.
Cause: One cannot use TRIGGER command on objects in an analytic workspace
attached in MULTI mode.
Action: Do all persistent object maintenance in read-write mode.
ORA-37040: (XSACQUIRE_DEP_LOCKED) Composite, concat, dimension map, or
internal partition workspace object is locked by another user.
Cause: Some object required locking a composite, concat, dimension map, or
internal partition, which is locked by another user
Action: Try to acquire this object later
ORA-37041: (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or
internal partition workspace object is locked by another user and the WAIT
timed out.
Cause: Some object required locking a composite, concat, dimension map, or
internal partition, which could not be locked for a while, since it is locked by
another user
Action: Try to acquire this object later
ORA-37042: (XSACQUIRE_DEP_DEADLOCK) Cannot wait to acquire composite,
concat, dimension map, or internal partition workspace object, since doing so
would cause a deadlock.
Cause: Some object required locking a composite, concat, dimension map, or
internal partition, which would cause a deadlock
Action: Release some other object that another user is waiting for and try to
acquire this object again.
ORA-37043: (XSACQUIRE_DEP_OLDGEN) Composite, concat, dimension map, or
internal partition workspace object cannot be locked, since another user has
committed a new one already.
Cause: Some object required locking a composite, concat, dimension map, or
internal partition in the present generation, which is not possible, since a newer
generation already exists.
Action: Try to acquire the main object with resync
ORA-37044: (XSACQUIRE_OLDGEN) Cannot acquire object workspace object
without resync.
Cause: Could not acquire the object without resync because another user has
committed a newer version of it already.
Action: Try to acquire this object with resync parameter
ORA-37050: (XSMLTDCL06) You cannot use the RELATION command with
workspace object because analytic workspace string is attached in MULTI mode.
ORA-33000 to ORA-37999 20-69
Cause: One cannot use the RELATION command on objects in an analytic
workspace attached in MULTI mode.
Action: Change the default relation when the analytic workspace is attached in
RW or Exclusive mode.
ORA-37060: (XSMCSESS08) number is not a valid custom member in dimension
workspace object.
Cause: No custom member or invalid custom member
Action: Create the custom member or use the correct custom member
ORA-37069: You may not execute a parallel OLAP operation against the EXPRESS
AW.
Cause: A parallel OLAP command attempted to execute against EXPRESS.
Action: Contact Oracle support. Users should not see this message.
ORA-37070: You may not execute OLAP DML programs in a parallel query session.
Cause: The user attempted to execute a DML program inside of a parallel query
session, perhaps in parallel aggregate
Action: Adjust the job so that a program does no need to be executed, or disable
parallelism
ORA-37071: You may not execute a parallel OLAP operation against updated but
uncommitted AW string.
Cause: The user attempted to use a parallel feature against an AW which they
updated but which has not been committed
Action: Commit the current changes
ORA-37072: (XSMCSESS00) Object workspace object has the wrong type.
Cause: The object is not of the object type specified in the APPLY clause
Action: Specify the correct object type
ORA-37073: (XSMCSESS01) Applied relation workspace object must be
dimensioned by dimension workspace object.
Cause: Applied relation has the different dimension from the dimension currently
being maintained
Action: Maintain relation dimension
ORA-37074: (XSMCSESS02) Variable workspace object has no default aggmap.
Cause: The applied variable has no default aggmap
Action: Use variable with the default aggmap or aggmap directly
ORA-37075: (XSMCSESS03) You cannot rename a session-only dimension value.
Cause: The user tried to apply MAINTAIN RENAME to a SESSION value.
Action: Delete the old value and add a new one with the desired name.
ORA-37076: (XSMCSESS04) workspace object is not the type of dimension that can
have session-only values. Valid types are TEXT, NTEXT, ID, NUMBER, and
CONCAT with the UNIQUE attribute.
Cause: The user tried to add a SESSION value to a dimension type that does not
support SESSION values.
Action: Use a dimension of one of the listed types.
20-70 Oracle Database Error Messages
ORA-37077: (XSMCSESS05) Object workspace object is specified more than once.
Cause: The same object name was given more than once in the apply clause or in
the step dimension list.
Action: Remove the repetitions.
ORA-37078: (XSMCSESS06) The dimension being maintained (workspace object)
cannot also be used as a step dimension.
Cause: The dimension being maintained was named as a step dimension.
Action: Remove this dimension from the list of step dimensions.
ORA-37079: (XSMCSESS07) Aggmap workspace object cannot be used for
AGGREGATE.
Cause: The current aggmap may be for ALLOCATE
Action: Choose the correct aggmap for AGGREGATE only.
ORA-37080: Advice requested for hierarchy with too many levels
Cause: A request was made for advice on a hierarchy with more levels than are
supported.
Action: Only request advice for hierarchies with less than 32 levels.
ORA-37082: Invalid percent
Cause: A request was made for advice with an illegal percent value.
Action: Request between 0 and 100 percent precomputation.
ORA-37083: Invalid object string
Cause: A request was made for advice with an illegal object name.
Action: Request using valid object names.
ORA-37084: Output valueset string must match string's dimensionality
Cause: A request was made for advice for a relation with different dimensionality
from the output valueset.
Action: Request using objects that have the same dimensionality.
ORA-37086: string is not a valueset
Cause: An operation was attempted that supports only valuesets as precompute
expressions in an aggmap, yet a different kind of precompute expression was
used.
Action: Replace this limit expression with an equivalent valueset and retry the
operation. General precompute expressions are deprecated.
ORA-37093: (XSOBJORG_BAD_CUBE) invalid property "string" specified for cube
"string.string"
Cause: Either the specified cube did not have an AW organization, or the
specified property did not apply to cubes.
Action: Specify a property that applies to cubes and a cube with an AW
organization.
ORA-37094: (XSOBJORG_BAD_DIM) invalid property "string" specified for
dimension "string.string"
Cause: Either the specified dimension did not have an AW organization, or the
specified property did not apply to dimensions.
ORA-33000 to ORA-37999 20-71
Action: Specify a property that applies to dimensions and a dimension with an
AW organization.
ORA-37095: (XSOBJORG_BAD_MEAS) invalid property "string" specified for
measure "string.string.string"
Cause: Either the specified measure did not have an AW organization, or the
specified property did not apply to measures.
Action: Specify a property that applies to measures and a measure with an AW
organization.
ORA-37096: (XSOBJORG_BAD_ATTR) invalid property "string" specified for base
attribute "string.string.string"
Cause: Either the specified base attribute did not have an AW organization, or the
specified property did not apply to base attribute.
Action: Specify a property that applies to base attributes and a base attribute with
an AW organization.
ORA-37097: (XSOBJORG_BAD_DIM_LEVEL) invalid property "string" specified
for dimension level "string.string.string"
Cause: Either the specified dimension level did not have an AW organization, or
the specified property did not apply to dimension levels.
Action: Specify a property that applies to dimension levels and a dimension level
with an AW organization.
ORA-37098: (XSOBJORG_BAD_MODEL) invalid property "string" specified for
dimension calculation model "string.string.string"
Cause: Either the specified dimension calculation model did not have an AW
organization, or the specified property di not apply to dimension calculation
models.
Action: Specify a property that applies to dimension calculation models and a
dimension calculation model with an AW organization.
ORA-37099: (XSOBJORG_BAD_DIMALITY) invalid property "string" specified for
dimensionality "string.string.string"
Cause: Either the specified dimensionality did not have an AW organization, or
the specified property did not apply to dimensionalities.
Action: Specify a property that applies to dimensionalities and a dimensionality
with an AW organization.
ORA-37100: (XSUNCOMMITTED) You have one or more updated but
uncommitted analytic workspaces.
Cause: The user has attempted to shut down OLAP, but they have active analytic
workspaces whose changes have not been saved.
Action: Issue the commit command. ---- 37101 - 37110 are reserved for partitioned
variables ----
ORA-37101: (XSVPART01) Partitioning information can only be given for variables
dimensioned by a PARTITION TEMPLATE.
Cause: User attempted to define or reference an AW object with the "all internal"
phrase or internal / external partition list, but the object was not a variable, was
not dimensioned by a partition template, or was an already existing target of an
external partition.
20-72 Oracle Database Error Messages
Action: Eliminate phrases specific to partitioned variables from the definition
string, or dimension the variable by a partition template.
ORA-37102: (XSVPART02) Invalid partition name string.
Cause: The user gave an invalid partition name. When defining a partitioned
variable, this message indicates that the partition name does not exist in the
partition template. In any other context, it indicates that the partitioned variable or
partition template does not have a partition with the given name.
Action: Supply a valid partition name.
ORA-37103: (XSVPART03) The dimensionality or datatype of workspace object
does not match the dimensionality or datatype of the partition.
Cause: User attempted to define a partitioned variable with an external partition,
but the target of the external partition had incorrect dimensionality or datatype.
Action: Pick a different target variable. The target variable must be dimensioned
by exactly the same dimensions, composites, and partition templates, in the same
order, as are specified in the partition template, and must have the exact same
datatype (including width, precision, and scale) as the partitioned variable itself.
ORA-37104: (XSVPART04) A partitioned variable must be dimensioned by a single
partition template only.
Cause: User attempted to define a partitioned variable with more than one
partition templates, or a partition template and one or more other dimensions, in
the dimension list.
Action: Use only a partition template in the dimension list of the variable. All
dimensions of the variable must be included in the definition of the partition
template.
ORA-37105: (XSVPART05) Only variables dimensioned by a CONCAT
PARTITION TEMPLATE can have string partitions.
Cause: User attempted to create an external partition on a partitioned variable,
but the variable was dimensioned by a RANGE or LIST partition template.
Action: Declare the partition INTERNAL instead of EXTERNAL, or use a
CONCAT partition template in place of the RANGE or LIST partition template.
ORA-37106: (XSVPART06) Invalid partition name number.
Cause: The user gave an invalid partition name.
Action: Supply a valid partition name.
ORA-37107: (XSVPART07) Attempt to write to non-existent partition of workspace
object.
Cause: Some action attempted to write data to a partitioned variable, but the
variable didn't have a partition for that data. This can result from a partition
template that does not assign all possible dimension values to some subcube, or
from a partitioned variable that does not have a partition for one of the partitions
defined by the partition template.
Action: Make sure that the cell being written is assigned to some partition by the
partition template, and that the variable has an actual partition associated with the
partition of the template. Use the CHGDFN template DEFINE... command to
define new partitions within the template, and the CHGDFN variable ADD...
command to add new partitions to the variable. Alternatively, the
PARTWRITEERR can be set to false, in which case data being written to a
non-existent partition will be silently discarded.
ORA-33000 to ORA-37999 20-73
ORA-37108: (XSVPART08) workspace object has an AGGCOUNT, but workspace
object does not.
Cause: An attempt was made to add a partition to a partitioned variable. Either
the partition was defined WITH AGGCOUNT and the partitioned variable was
not, or the partitioned variable was defined WITH AGGCOUNT and the partition
was not.
Action: Use CHGDFN ADD AGGCOUNT or CHGDFN DROP AGGCOUNT to
either add or remove an AGGCOUNT from either the partition or the partitioned
variable.
ORA-37109: (XSVPART09) Partition workspace object and its parent variable
workspace object cannot both be specified.
Cause: Partition and its parent partition were operated upon together.
Action: Remove the partition from the object list.
ORA-37111: Unable to load the OLAP API sharable library: (string)
Cause: This happens if: (1) the OLAP API sharable library is missing. (2) a
sharable library upon which the OLAP API sharable library depends is missing.
(3) the OLAP API sharable library is the wrong version.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Customer Support.
ORA-37113: OLAP API initialization error: (string)
Cause: OLAP API initialization failed.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Customer Support.
ORA-37114: OLAP API bootstrap error: (string)
Cause: OLAP API bootstrapping failed.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Customer Support.
ORA-37115: New OLAP API history is not allowed
Cause: If there are active OLAP API sessions, it is not allowed to start a new
OLAP API history by setting _olapi_history_retention parameter to true.
Action: Wait until all active OLAP API sessions terminate before resetting _olapi_
history_retention parameter to true.
ORA-37116: OLAP API table function error: (string)
Cause: OLAP API table function failed.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Customer Support.
ORA-37117: olapi history retention has been disabled
Cause: Under certain circumstances, for example, when the database is read only,
olapi history retention is not possible because it requires updating persistent tables
from time to time. If olapi history retention has been disabled, setting _olapi_
history_retention parameter to true has no effect.
20-74 Oracle Database Error Messages
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Customer Support.
ORA-37118: The OLAP API library was not preloaded.
Cause: In shared-server mode, the OLAP API library should be loaded during
process initialization to ensure that the C++ virtual table addresses are identical in
all shared-server processes. The OLAP API session was executing in a process in
which the library had not been loaded.
Action: Set option _XSOLAPI_LOAD_AT_PROCESS_START to SHARED_
SERVER or ALWAYS, restart the instance, and try again.
ORA-37119: Incompatible OLAP API library load address
Cause: The OLAP API session was executing in a process in which the OLAP API
sharable library was loaded which was at a different address than the process in
which the OLAP API session originated.
Action: Set option _XSOLAPI_LOAD_AT_PROCESS_START to ALWAYS, restart
the instance, and try again.
ORA-37120: expression string is null
Cause: expression parser received a null string for syntax analysis.
Action: Prepare a non-null and well-formed MDX query string and try again.
ORA-37121: AW Spreadsheet invalidated
Cause: While this cursor was open, a command was issued that changed the
underlying data to become inconsistent.
Action: Perform the query again, avoid performing dimension maintenance and
cache clears during spreadsheet processing.
ORA-37122: AW Session cache disabled
Cause: A SQL Spreadsheet was attempted while the AW Session cache was
disabled.
Action: Enable the session cache and perform the query again.
ORA-37123: (XSCCOMP17) Can not AGGREGATE workspace object(partition
number) because it depends on unaggregated compressed partition number.
Cause: attempted to use a feature not supported by CC's in the current AW
format
Action: Remove the unsupported feature from the aggmap, or upgrade the AW
ORA-37124: (XSCCOMP16) COMPRESSED COMPOSITES with string are not
supported in analytic workspace string because it has not been upgraded to
version string.
Cause: attempted to use a feature not supported by CC's in the current AW
format
Action: Remove the unsupported feature from the aggmap, or upgrade the AW
ORA-37126: (XSCCOMP01) The COMPRESSED COMPOSITE workspace object
can only be used as a base of a single variable.
Cause: The user attempted to DEFINE a variable dimensioned by a
COMPRESSED COMPOSITE, but that COMPRESSED COMPOSITE is already
being used by another VARIABLE.
ORA-33000 to ORA-37999 20-75
Action: Create a second COMPRESSED COMPOSITE for the second VARIABLE
or add a measure dimension to the first variable.
ORA-37127: (XSCCOMP02) The COMPRESSED COMPOSITE workspace object
must be last in the dimension list.
Cause: The user attempted to DEFINE a variable dimensioned by a
COMPRESSED COMPOSITE, but gave a slower varying dimension in the
dimension list.
Action: Put the COMPRESSED COMPOSITE last in the dimension list when
defining the VARIABLE.
ORA-37128: (XSCCOMP20) The partition template workspace object has already
used the COMPRESSED COMPOSITE workspace object.
Cause: The COMPRESSED COMPOSITE specified for either a variable or
partition template is already in use in another partition template.
Action: Define a different COMPRESSED COMPOSITE.
ORA-37129: (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE
workspace object using AGGMAP workspace object. All static MODEL
statements must precede all RELATION statements over the bases of the
COMPRESSED COMPOSITE.
Cause: The AGGMAP was defined with a MODEL statement after a RELATION
statement over a base of the COMPRESSED COMPOSITE.
Action: Change the AGGMAP so that the MODEL statements appear before the
RELATION statements.
ORA-37130: (XSCCOMP05) Cannot aggregate over COMPRESSED COMPOSITE
workspace object using AGGMAP workspace object because you must specify
AGGINDEX OFF when there is a PRECOMPUTE clause on a RELATION over
base workspace object.
Cause: A PRECOMPUTE clause was specified in the AGGMAP for a RELATION
over a base of a COMPRESSED COMPOSITE, but AGGINDEX was ON
Action: Remove the PRECOMPUTE clause from the AGGMAP, or add
AGGINDEX OFF
ORA-37131: (XSCCOMP06) Cannot aggregate over COMPRESSED COMPOSITE
workspace object using AGGMAP workspace object because the OPERATOR
string is not supported for bases of a COMPRESSED COMPOSITE.
Cause: The user specified an aggregation OPERATOR that is not supported by
COMPRESSED COMPOSITES.
Action: Use a MODEL for the calculation, or use an uncompressed COMPOSITE.
ORA-37132: (XSCCOMP07) Incremental aggregation over the dense DIMENSION
workspace object is not supported when aggregating a VARIABLE dimensioned
by a COMPRESSED COMPOSITE.
Cause: The status of the specified dimension did not include all detail cells.
Action: Add all detail cells to the status of the dimension and reissue the
AGGREGATE command.
ORA-37133: (XSCCOMP08) You cannot write into an aggregated VARIABLE
dimensioned by a COMPRESSED COMPOSITE. Use the CLEAR
AGGREGATES command to reenable write access.
20-76 Oracle Database Error Messages
Cause: The user attempted to store a value into to a variable dimensioned by a
compressed composite, and the variable had previously been precomputed using
the AGGREGATE command. Once the AGGREGATE command is run on a
variable dimensioned by a compressed composite, it becomes read-only until the
computed values are removed with the CLEAR command.
Action: Run the CLEAR AGGREGATES command to remove the computed
values from the variable and then rerun the failed operation. Note that CLEAR
AGGREGATES will remove all the data computed during the last AGGREGATE
command on this variable.
ORA-37134: (XSCCOMP09) You cannot add new values to workspace object because
it includes positions for precomputed aggregate values.
Cause: The user attempted to create a new position in a compressed composite,
either directly (using MAINTAIN MERGE or MAINTAIN ADD) or by storing a
value into the variable dimensioned by the compressed composite. This is not
allowed when the variable has been precomputed using the AGGREGATE
command. Once the AGGREGATE command is run on a variable dimensioned by
a compressed composite, the compressed composite becomes read-only until the
computed values are removed with the CLEAR command.
Action: Run the CLEAR AGGREGATES command to remove the computed
values from the variable and then rerun the failed operation. Note that CLEAR
AGGREGATES will remove all the data computed during the last AGGREGATE
command on this variable.
ORA-37135: (XSCCOMP19) The COMPRESSED COMPOSITE workspace object in
the current defined partition template should be unique or global.
Cause: The COMPRESSED COMPOSITE was neither unique nor global. Unique
means each subpartition should have different COMPRESSED COMPOSITEs;
Global means all subpartitions should use the same COMPRESSED COMPOSITE
if they use any COMPRESSED COMPOSITE.
Action: Redefine the partition template.
ORA-37136: (XSCCOMP11) Cannot ROLLUP dimension workspace object which is
a base of COMPRESSED COMPOSITE workspace object, use AGGREGATE
instead.
Cause: The user ran ROLLUP on a variable dimensioned by a COMPRESSED
COMPOSITE.
Action: Instead of using ROLLUP, generate an aggmap and use AGGREGATE
ORA-37137: (XSCCOMP12) You cannot CHGDFN workspace object because it is a
COMPRESSED COMPOSITE.
Cause: The user tried to CHGDFN a compressed composite
Action: If the change is desired then delete the old composite and create a new
one.
ORA-37138: (XSCCOMP13) You cannot delete values from workspace object
because it is an aggregated COMPRESSED COMPOSITE.
Cause: The user tried to MAINTAIN DELETE from an aggregated COMPRESSED
COMPOSITE.
Action: In order to perform this sort of maintenance the composite must first be
cleared. This can be done by running the CLEAR AGGREGATES command on the
variable dimensioning the composite. Note that this will remove all data
computed during the last AGGREGATE command.
ORA-33000 to ORA-37999 20-77
ORA-37139: (XSCCOMP14) Cannot AGGREGATE workspace object using
AGGMAP workspace object because you can not AGGREGATE a variable
dimensioned by a COMPRESSED COMPOSITE using an AGGMAP with a
PROTECT clause.
Cause: The user tried to AGGREGATE a variable dimensioned by a
COMPRESSED COMPOSITE with an AGGMAP that included a PROTECT clause.
Action: Modify the aggmap or create a new aggmap that does not include a
PROTECT clause and reaggregate.
ORA-37140: (XSCCOMP15) Cannot AGGREGATE partitioned variable workspace
object using AGGMAP workspace object because you cannot use the base of a
COMPRESSED COMPOSITE as a partition dimension.
Cause: The user tried to run aggregate on a partitioned variable with a partition
dimension that is a base of a COMPRESSED COMPOSITE.
Action: Repartition the data, drop the partition dimension from the aggmap, or
don't use COMPRESSED COMPOSITES.
ORA-37141: (XSSQLMDQ01) Invalid host variable syntax for MDQUERY
procedure.
Cause: The schema and analytic workspace name for the MDQUERY cursor
declaration were incorrectly specified.
Action: Specify the schema and awname as a host variable name preceded by a
colon, or as a text literal string of the form 'SCHEMA.AWNAME' or '*.*' (quotes
optional).
ORA-37142: (XSSQLMDQ02) Invalid host variable data type for MDQUERY
procedure: string expected.
Cause: The user specified a host variable that was not of the correct type.
Action: Choose a different host variable.
ORA-37143: (XSSQLMDQ03) string is not a valid analytic workspace name.
Cause: The user specified an analytic workspace name not qualified by a schema
name, or one or both components of the name exceed the maximum length
Action: Specify a schema-qualified analytic workspace name with components no
longer than 30 characters long.
ORA-37144: (MDQUERY01) string is not a valid metadata object type for
MDQUERY.
Cause: The user specified an unrecognized first argument to MDQUERY
Action: Specify a recognized object type (CUBE or DIMENSION)
ORA-37145: (XSTTS_PLAT) Cannot transport analytic workspace across platforms.
Cause: The user attempted to transport a tablespace containing an analytic
workspace from one platform to another.
Action: Use export/import to move an analytic workspace across platforms.
ORA-37146: (XSCCOMP18) The variable workspace object is already dimensioned
by the COMPRESSED COMPOSITE workspace object.
Cause: An attempt was made to define the partition template dimensioned by the
COMPRESSED COMPOSITE which had dimensioned the variable.
Action: Define the second COMPRESSED COMPOSITE.
20-78 Oracle Database Error Messages
ORA-37147: (XSCCOMP21) The variable workspace object must be in the current
operation group of the COMPRESSED COMPOSITE workspace object.
Cause: The variable dimensioned by the COMPRESSED COMPOSITE was not in
the object list of the current operation group. For AGGREGATE, all variables
dimensioned by the same COMPRESSED COMPOSITE also must use the same
aggmap
Action: Add the variable into the object list of the current operation group.
ORA-37148: (XSCCOMP22) workspace object is an aggregated COMPRESSED
COMPOSITE.
Cause: Defined the variable or partition template with the aggregated
COMPRESSED COMPOSITE.
Action: Clear the COMPRESSED COMPOSITE or use a new COMPRESSED
COMPOSITE
ORA-37149: (XSCCOMP23) Individual partitions of the variable dimensiond by
workspace object cannot be aggregated separately.
Cause: An attempt was made to aggregate partitions of a variable dimensioned
by a global COMPRESSED COMPOSITE partition template.
Action: Aggregate the partitioned variable dimensioned by the global
COMPRESSED COMPOSITE.
ORA-37150: line string, column string, string
Cause: expression syntax error was found in expression query string.
Action: Check the error message details and make the corrections.
ORA-37151: expression parser initialization error
Cause: expression parser initialization failed
Action: Please report this to Oracle Support Services.
ORA-37152: MDX query error: (string)
Cause: An exception occurred while MDX query was processed.
Action: Check the error message details and try again.
ORA-37153: unknown exception caught: (case string)
Cause: An unknown exception was caught while MDX query was processed.
Action: Please report it to Oracle Support Services.
ORA-37154: OLAP API initialization error: (case string)
Cause: OLAP API initialization failed.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Support Services.
ORA-37155: OLAP API bootstrap error: (case string)
Cause: OLAP API bootstraping failed.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Support Services.
ORA-37156: (string)
Cause: unknown
ORA-33000 to ORA-37999 20-79
Action: Check the error message details.
ORA-37157: expression syntax error was found in expression string but error text
was missing
Cause: This happened because the message file was missing.
Action: Make sure that the message file xsous.msb is located in $ORACLE_
HOME/olap/mesg and rerun your expression query.
ORA-37158: Bad clob or varray IN-args: (case string)
Cause: When in clob or varray mode, the PL/SQL mappings of OLAP API's IDL
interface methods were executed blindly with null clob/varray or non-null
clob/varray containing garbages.
Action: Do not blindly execute them as doing so does not make sense unless you
understand how OLAP API works internally.
ORA-37159: C++ virtual table addresses become invalid due to session migration in
shared server mode.
Cause: Exec-shield is the primary reason that caused this error in shared server
mode. When exec-shield is turned on, there is no way to ensure that the C++
virtual table addresses are identical in all shared-server processes.
Action: Set option _XSOLAPI_FIX_VPTRS to TRUE, restart the instance, and try
again.
ORA-37160: OLAP object does not exist
Cause: The specified OLAP object did not exist.
Action: Use an existing OLAP object instead.
ORA-37161: invalid privilege specified for OLAP object
Cause: An attempt was made to grant or revoke an invalid privilege on an OLAP
object.
Action: Specify a valid privilege.
ORA-37162: OLAP error
Cause: An exception was raised by OLAP code.
Action: Check error messages and correct any reported problems.
ORA-37163: cannot delete or truncate AW with dependent CUBES or CUBE
DIMENSIONS
Cause: User attempted to delete or truncate an AW which currently has a CUBE
or CUBE DIMENSION defined over it
Action: Drop the corresponding CUBE or CUBE DIMENSION before deleting the
AW
ORA-37164: The current SQL statement does not support this OLAP object
Cause: The OLAP object is not supported in the current SQL statement.
Action: Use a valid SQL command on the OLAP object.
ORA-37165: cannot use EIF IMPORT into a non-empty Analytic Workspace
(string.string)
Cause: An attempt was made to use EIF IMPORT to populate a non-empty
Analytic Workspace.
20-80 Oracle Database Error Messages
Action: Ensure that the target Analytic Workspace is empty before populating it
with EIF IMPORT.
ORA-37166: (XSOQ_BAD_OBJ) OLAP object "string.string" does not exist
Cause: The specified OLAP object did not exist.
Action: Use an existing OLAP object instead.
ORA-37167: (XSOQ_BAD_SUBOBJ) OLAP object "string.string.string" does not
exist
Cause: The specified OLAP object did not exist.
Action: Use an existing OLAP object instead.
ORA-37168: (XSOBJORG_UNSUPP_OBJ) unsupported OLAP object "string.string"
for OBJORG function
Cause: The specified OLAP object was of a type that is not supported by the
OBJORG function.
Action: Specify an OLAP object of a type that the OBJORG function supports.
ORA-37169: (XSOBJORG_UNSUPP_SUBOBJ) unsupported OLAP object
"string.string.string" for OBJORG function
Cause: The specified OLAP object was of a type that is not supported by the
OBJORG function.
Action: Specify an OLAP object of a type that the OBJORG function supports.
ORA-37170: (XSOBJORG_NA) The top-level object name argument to the OBJORG
function cannot be NA.
Cause: You passed NA as the second argument to the OBJORG function.
Action: Pass the name of the top-level object instead.
ORA-37171: dimension sources not specified
Cause: The user passed an empty or null collection to DBMS_AW.ADVISE_
SPARSITY
Action: Specify a valid set of dimension sources
ORA-37172: illegal dimension type
Cause: The user specified an invalid member of the DIMTYPE field in the
dimension sources argument
Action: Specify one of the valid enumerated values in DBMS_AW
ORA-37173: null dimension source data
Cause: The user specified NULL for one of the members of the dimension sources
argument
Action: Specify a value
ORA-37174: source SQL must be a SELECT statement
Cause: The user specified an INSERT, UPDATE, DELETE or other type of SQL
statement
Action: Specify a SQL SELECT statement instead
ORA-37175: column string is not a column of source data
Cause: A dimension column was specified which did not exist in the input data
Action: Specify one of the columns of the input data
ORA-33000 to ORA-37999 20-81
ORA-37176: argument string is not valid for the sparsity advisor
Cause: An invalid argument was passed to the advisor
Action: Specify a TABLE, VIEW or SELECT statement instead
ORA-37177: column string does not have any leaf values
Cause: The specified dimension column or fact table did not contain any leaf
values
Action: Populate the source data
ORA-37178: column string has no values
Cause: The specified dimension column did not contain any values
Action: Populate the source data
ORA-37179: expected at least one column for dimension string, got string
Cause: Not enough columns were specified for the dimension
Action: Specify more source columns, or change the dimension to another type
ORA-37180: expected exactly one column for dimension string, got string
Cause: Expected a single source column for the dimension. Either none or more
than one was specified.
Action: Specify exactly one column, or change the dimension to another type
ORA-37181: expected exactly string columns for dimension string, got string
Cause: Expected a certain number of source columns for the dimension. Either
none or the wrong number of columns was specified.
Action: Specify the right number of columns, or change the dimension to another
type
ORA-37182: you may only specify one dimension to partition
Cause: The user passed a DIMENSION_SOURCE_T to ADVISE_SPARSITY which
specified partitioning on more than one dimension
Action: Remove all but one of the partitioning requests
ORA-37183: illegal value string for PARTBY
Cause: The user passed a value other than PARTBY_DEFAULT, PARTBY_NONE
or PARTBY_FORCE to DBMS_AW.ADVISE_SPARSITY *Acton: Supply a legal
value instead
Action: None
ORA-37184: illegal value string for ADVMODE
Cause: The user passed a value other than ADVICE_DEFAULT, ADVICE_FAST or
ADVICE_FULL to DBMS_AW.ADVISE_SPARSITY *Acton: Supply a legal value
instead
Action: None
ORA-37185: length of string (string) exceeds maximum (string)
Cause: The user passed an excessively long value
Action: Specify a legal value
ORA-37186: null child value for parent (string) found in parent-child hierarchy
Cause: While reading values for a parent-child hierarchy, a NULL child value was
found for a non-NULL parent
20-82 Oracle Database Error Messages
Action: Correct the source table or SQL to return value parent and child pairs.
ORA-37187: null parent and child pair found in parent-child hierarchy
Cause: While reading values for a parent-child hierarchy, a row was retrieved
which had both null child and parent values.
Action: Correct the source table or SQL to return value parent and child pairs.
ORA-37188: unexpected null result while querying string
Cause: While querying the input fact table, the sparsity advisor unexpectedly got
no results, possibly due to changes being made during operation.
Action: Retry the operation ensuring that the data is not changed while the
sparsity advisor is running / Errors from 37200 - 37399 are reserved for events
ORA-37400: analytic workspace does not exist
Cause: The user attempted to create an OLAP MV or Table on an AW that does
not exist.
Action: Specify a valid AW in the ORGANIZATION CUBE clause
ORA-37401: you may not perform this operation on a system analytic workspace
Cause: The user attempted to create a CUBE MV or Table on a system-created
AW.
Action: Specify a valid AW in the ORGANIZATION CUBE clause
ORA-37402: analytic workspace object does not exist
Cause: The user attempted to create a CUBE MV or Table mapping to an object
that does not exist in the AW.
Action: Specify a valid AW object name in the ORGANIZATION CUBE clause.
ORA-37403: invalid analytic workspace object type
Cause: The user attempted to create a CUBE MV or Table mapping to an object
that is not the correct type.
Action: Specify a valid AW object name in the ORGANIZATION CUBE clause.
ORA-37404: Create table as select disallowed for CUBE ORGANIZED tables
Cause: User attempted to create a CUBE ORGANIZED table by doing a create
table as select.
Action: Do a create table followed by an insert as select
ORA-37405: unknown ORGANIZATION CUBE keyword
Cause: An unknown keyword was encountered while parsing the
ORGANIZATION CUBE clause
Action: Correct the ORGANIZATION CUBE syntax
ORA-37406: invalid option for a CUBE ORGANIZED table
Cause: An attempt to specify one or more options for a CUBE ORGANIZED table
such as: [NO]CACHE, NO LOGGING, CLUSTER, (NO)COMPRESS
Action: Remove the illegal option(s)
ORA-37407: invalid column type for a CUBE ORGANIZED table
Cause: A illegal column type is specified in a CUBE ORGANIZED table.
Action: Do not use column types such as LONG, LOB
ORA-33000 to ORA-37999 20-83
ORA-37408: Truncate table disallowed for CUBE ORGANIZED tables
Cause: User attempted to perform a TRUNCATE operation on a CUBE
ORGANIZED table
Action: Remove data with DELETE or drop the table and recreate it
ORA-37409: cannot delete or truncate AW used by CUBE ORGANIZED table
Cause: User attempted to delete or truncate an AW which currently has a CUBE
ORGANIZED table or MV defined over it
Action: Drop the corresponding table or MV before deleting the AW
ORA-37410: cannot delete or modify AW object referenced by CUBE ORGANIZED
table
Cause: User attempted to delete, chgdfn, or otherwise modify an object referenced
by a CUBE ORGANIZED table or MV
Action: Drop the corresponding table or MV before manipulating the object
ORA-37411: invalid object type
Cause: User referenced an invalid object type
Action: Use an appropriate object
ORA-37412: column not mapped by ORGANIZATION CUBE clause
Cause: Not all columns in the table or MV definition were mapped in the
ORGANIZATION CUBE clause
Action: Make sure that all columns are mapped
ORA-37413: column referenced multiple times in ORGANIZATION CUBE clause
Cause: The same column name was referenced multiple times inside of the
ORGANIZATION CUBE clause
Action: Supply unique mappings for each column
ORA-37414: dimension without mapping or hierarchy in ORGANIZATION CUBE
clause
Cause: A dimension was listed in the ORGANIZATION CUBE clause but no
mapping information was supplied
Action: Provide either a column mapping or hierarchy for the dimension
ORA-37415: AW schema must match TABLE or MATERIALIZED VIEW schema
Cause: An ORGANIZATION CUBE table or MV on top of an existing AW must
be created in the same schema as the AW
Action: Create the new object in the same schema as the AW
ORA-37416: multiple GROUPING IDs found for ORGANIZATION CUBE
Cause: Multiple GROUPING IDs for the ORGANIZATION CUBE TABLE or
MATERIALIZED VIEW
Action: Remove the duplicates
ORA-37417: variable does not have an AGGCOUNT
Cause: A COUNT clause was specified in the ORGANIZATION CUBE
description for a variable that does not have an AGGCOUNT
Action: chgdfn the variable to include an AGGCOUNT
ORA-37418: detail query cannot be derived
20-84 Oracle Database Error Messages
Cause: If an ORANIZATION CUBE MV is to automatically derive its loading
clause, then its definition query cannot contain set operators (eg UNION ALL), a
HAVING clause, START WITH or a SQL MODEL clause. The definition query
contains these or other unsupported syntax.
Action: Use an explicit ORGANIZATION CUBE clause, or simplify the defining
query.
ORA-37419: ORGANIZATION CUBE clause not allowed in explain mview
Cause: User tries to explain mview on a CREATE MATERIALIZED VIEW
statement that contains a ORGANIZATION CUBE clause.
Action: Remove the ORGANIZATION CUBE clause from the CREATE
MATERIALIZED MATERIALIZED VIEW statement.
ORA-37420: unsupported feature with CUBE ORGANIZED materialized view
Cause: User attempts operations such as creating a mv log on an CUBE
ORGANIZED MATERIALIZED VIEW.
Action: Do not do that.
ORA-37421: specified pseudocolumn is not supported by CUBE ORGANIZED
tables
Cause: An unsupported pseudocolumn was referenced with a CUBE
ORGANIZED table.
Action: Remove the unsupported pseudocolumn.
ORA-37422: illegal attempt to write to a calculated column
Cause: An attempt was made to write to a calculated column which could not be
written to.
Action: List only the non-calculated columns in your DML command.
ORA-37423: operation not supported on CUBE ORGANIZED tables
Cause: The attempted operation was not supported with CUBE ORGANIZED
tables.
Action: Do not attempt this operation on CUBE ORGANIZED tables.
ORA-37424: alter materialized view (MV) on a primary cube organized MV failed
to find secondary cube MV table
Cause: The operation failed due to the missing secondary cube materialized view
(MV) table in alter MV.
Action: Recreate the primary CUBE MV and make sure the secondary cube MV
table is correctly created.
ORA-37521: (HASHSCAN00) Dimension string contains duplicate values. Please
contact Oracle OLAP Technical Support.
Cause: The named dimension contains duplicate values.
Action: Contact Technical Support for instructions.
ORA-37522: (HASHSCAN01) You must specify the name of an existing TEXT or
NTEXT dimension.
Cause: the _HASHSCAN program was invoked with an invalid argument
Action: Provide a text expression yielding the name of an existing TEXT
dimension
ORA-33000 to ORA-37999 20-85
ORA-37527: (XSCHGDFN01) SESSION values of dimension string are being
automatically deleted.
Cause: When using CHGDFN to rebuild the hash index of a TEXT or NTEXT
dimension, SESSION values were encountered.
Action: Recreate the SESSION values after the CHGDFN command completes.
Information about the deleted values has been written to the trace file.
ORA-37528: (XSOBJORG_BAD_HIER) invalid property "string" specified for
hierarchy "string.string.string"
Cause: Either the specified hierarchy did not have an AW organization, or the
specified property did not apply to hierarchies.
Action: Specify a property that applies to hierarchy and a dimension with an AW
organization.
ORA-37530: (XSCCLOAD01) When aggregating between compressed partitions the
base dimensions of workspace object did not match the base dimensions of
workspace object.
Cause: When aggregating a partitioned variable the dimensionality of any
compressed partitions should be identical.
Action: Delete the upper partition and redefine it with a composite that matches
the lower partition. If it is dependent on multiple partitions with varying sparsity
you must first unify the the sparsity of the source partitions.
ORA-37531: (XSCCLOAD02) When aggregating between compressed partitions the
source partitions were aggregated with a different AGGMAP, or the
RELATIONS have changed since the source partitions were aggregated.
Cause: When aggregation crosses partition boundaries within a compressed
variable the individual partitions must all be aggregated using a similar aggmap
over the same unaltered relations.
Action: Modify the aggmap for the upper partition to more exactly match the
aggmap of the source partitions, or if the aggmap is already similar, re-aggregate
the source partitions to pick up any changes to the relations.
ORA-37541: Hierarchy element DIMENSION_MEMBER can aggregate into
element MEMBER_ANCESTOR through multiple paths.
Cause: When a low level hierarchy element can reach an aggregate element by
more than one path through the hierarchy, it is said to have multiple paths. The
danger is that the value of the low level hierarchy element will have its value
counted multiple times (once per path) in the total of the aggregate element.
Action: Eliminate multiple paths from the hierarchy.
ORA-37542: DIMENSION_MEMBER makes hierarchy HIERARCHY1 unbalanced.
Cause: A hierarchy is balanced if: 1) All members of a level are at the same depth
from the root of the hierarchy and 2) All the members in different levels are at
different depths from the root of the hierarchy.
Action: Fix the hierarchy so that it is balanced. This is often done by looking for
nulls in the middle levels of a hierarchy.
ORA-37543: Hierarchy member DIMENSION_MEMBER is inconsistent across
HIERARCHY1 and HIERARCHY2.
Cause: Two hierarchies are inconsistent when members that appear in both
hierarchies have different ultimate leaves.
20-86 Oracle Database Error Messages
Action: This problem is usually resolved by defining a new dimension member
for the secondary hierarchy, or fixing the hierarchy table so that the definitions of
the member match across hierarchies.
ORA-37544: Dimension members DIMENSION_MEMBER and MEMBER_
ANCESTOR make this dimension star inconsistent.
Cause: A dimension is "star consistent" when it can be represented in a star
schema table. This requires that a hierarchy level map to a single underlying
column. If a level is shared across one or more hierarchies, it must have the same
set of members in each hierarchy (to share a column).
Action: Create a different level for the secondary hierarchy. This provides a
separate level column for each hierarchy.
ORA-37545: DIMENSION_MEMBER is part of a hierarchy loop.
Cause: A hierarchy has loops when the ancestor of a dimension member uses that
member as its parent. Note that some loops are created across hierarchies. For
example, in hierarchy 1, dimension member A is the parent of B, B is the parent of
C and in hierarchy 2, C is that parent of A forms a hierarchy loop.
Action: Change the hierarchies so that the loop is eliminated or move the problem
hierarchy to a different dimension.
ORA-37546: (XSHIERSP00) Levelorder valueset is empty.
Cause: An empty levelorder valueset was specified for the HIERSHAPE function.
Action: specify a non-empty levelorder valueset.
ORA-37547: (XSHIERSP01) DIMENSION_MEMBER has no level associated with
it.
Cause: DIMENSION_MEMBER did not have an associated level. Level based
hierarchies must have a level for every dimension member.
Action: Add level assignments for all dimension members in the hierarchy.
ORA-37548: (XSHIERSP02) DIMENSION_MEMBER is not specified as a member
of HIERARCHY1.
Cause: When a dimension member is part of a hierarchy, it appears in the INHIER
valueset associated with the hierarchy. This dimension member is missing from
this value set and thus should not be part of this hierarchy.
Action: Alter the hierarchy's membership to include the specified dimension
member.
ORA-37549: (XSHIERSP03) The level of DIMENSION_MEMBER is not lower than
the level of MEMBER_ANCESTOR.
Cause: A dimension member has a parent that is lower or on the same level as
this member according to the levelorder valueset.
Action: Fix the child and/or parent levels so that every dimension member has a
parent whose level is higher than the level of this member.
ORA-37550: (XSHIERSP04) The level of MEMBER_ANCESTOR is not one level
above DIMENSION_MEMBER.
Cause: A dimension member has a parent that is not one level above the level of
this member according to the levelorder valueset.
Action: Fix the child and/or parent levels so that every dimension member has a
parent whose level is one level above the level of this member according to the
levelorder.
ORA-33000 to ORA-37999 20-87
ORA-37551: (XSHIERSP05) Leaf value DIMENSION_MEMBER is not on the same
level as the rest of leaf dimension values.
Cause: The detail or leaf values of this hierarchy must all have the same level.
This member is on a different level than most of the leaf values.
Action: Fix DIMENSION_MEMBER's level so that all leaves are on the same level.
ORA-37552: (XSHIERSP06) DIMENSION_MEMBER is associated with a level not
found in the levelorder valueset.
Cause: DIMENSION_MEMBER must have an associated level that is found in the
levelorder valueset so that we can figure out DIMENSION_MEMBER's level
depth.
Action: Fix DIMENSION_MEMBER's associated level.
ORA-37553: A cycle between number and number has been detected in relation
workspace object over workspace object.
Cause: A relation was used that had loops in it.
Action: Correct the relation so that it does not contain loops.
ORA-37554: A cycle between number and number has been detected in relation
workspace object.
Cause: A relation was used that had loops in it.
Action: Correct the relation so that it does not contain loops.
ORA-37560: lob locator invalid for specified log target
Cause: A lob locator was passed as a target to DBMS_CUBE_LOG.ENABLE, but
the log_target was not DBMS_CUBE_LOG.TARGET_LOB
Action: Specify LOG_TARGET_LOB as the log_target, or specify a valid location
instead
ORA-37561: unknown logging type
Cause: An invalid log_type was specified
Action: Specify a valid logging type from the DBMS_CUBE_LOG package
ORA-37562: unknown logging target
Cause: An invalid log_target was specified
Action: Specify a valid logging target from the DBMS_CUBE_LOG package
ORA-37563: invalid log verbosity
Cause: An invalid log_verbosity was specified
Action: Specify a valid logging verbosity from the DBMS_CUBE_LOG package
ORA-37564: unknown log table version
Cause: Could not determine the version of the specified logging table
Action: Specify a valid target table, or use DBMS_CUBE_LOG.TABLE_CREATE to
create one
ORA-37565: invalid parameter for specified log type
Cause: The log_type specified does not support the specified parameter, for
instance, DBMS_CUBE_LOG.MAX_ERRORS is not valid for
Action: Specify a valid log_type / log_param combination
ORA-37566: invalid log location
20-88 Oracle Database Error Messages
Cause: The specified log location is in an invalid format. For file targets it must be
of the form 'directory_alias/filename'
Action: Specify a valid log location
ORA-37567: log location not specified
Cause: The log location was not specified for a log target which requires one
Action: Specify a valid log location
ORA-37568: invalid log parameter
Cause: An invalid log_param was passed to dbms_cube_log.set_parameter or
get_parameter
Action: Specify a valid parameter
ORA-37569: invalid log parameter value
Cause: An invalid value was passed to dbms_cube_log.set_parameter
Action: Specify a valid value
ORA-37570: invalid log specification
Cause: An invalid logging specification was supplied to DBMS_CUBE_LOG.SET_
LOG_SPEC
Action: Correct the syntax being supplied
ORA-37571: invalid SQL ID
Cause: Either the SQL ID supplied was invalid or no associated logging
information was captured.
Action: Specify a valid SQL ID.
ORA-37572: invalid ID
Cause: An invalid ID was supplied for the given SQL ID.
Action: Specify a valid ID for that SQL ID.
ORA-37573: no limits logged
Cause: There were no corresponding OLAP filters to the supplied information.
Action: Specify predicates on the original query or specify a new SQL ID or ID.
ORA-37574: error logging to table "string.string"
Cause: An error occurerd attempting to write log records to the named table.
Action: Make sure the user has permissions to write to the table.
ORA-37575: Invalid cube operations log component, "string".
Cause: Invalid cube operations log component value.
Action: Provide a valid cube operations log component or accept the default
value by leaving the parameter unspecified.
ORA-37576: Invalid cube operations log handle id.
Cause: An invalid cube operations log handle id was specified. No oplog handle
found for oplogHandleId parameter.
Action: Provide a valid cube operations log handle id for oplogHandleId. Use
DBMS_CUBE_LOG.START_OPLOG to get a valid handle id.
ORA-37577: Invalid cube operations log message name.
Cause: Cube operations log message name value is NULL.
ORA-33000 to ORA-37999 20-89
Action: Provide a valid non-null cube operations log message name.
ORA-37578: Invalid cube operations log operation value.
Cause: Cube operation log operations value is NULL.
Action: Provide a valid non-null cube operations log operation value.
ORA-37580: The EXPRESS AW does not exist.
Cause: The EXPRESS AW does not exist.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Support Services.
ORA-37581: The EXPRESS AW has not been properly installed.
Cause: The EXPRESS AW has not been properly installed.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Support Services.
ORA-37582: The EXPRESS AW version string is different than the Oracle version
string.
Cause: The EXPRESS AW version does not match the current Oracle version.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Support Services.
ORA-37600: (XSPGERRPERMDETACH) Ran out of tablespace storage while
updating analytic workspace string
Cause: Ran out of lob segment space.
Action: Increase tablespace storage. AW may need to be detached.
ORA-37601: (XSPGERRTEMP) Ran out of temporary storage while writing to
analytic workspace with ID=number. Free some temporary storage immediately.
You can do so, for example, by DETACHING an analytic workspace.
Cause: Ran out of temporary tablespace storage.
Action: Increase the amount of temporary tablespace storage.
ORA-37602: (XSPGERRTEMPUSER) Ran out of temporary storage while writing to
analytic workspace string. Free some temporary storage immediately. You can do
so, for example, by DETACHING an analytic workspace.
Cause: Ran out of temporary tablespace storage.
Action: Increase the amount of temporary tablespace storage.
ORA-37603: (XSPGERRTEMPSYSTEM) Ran out of temporary storage while writing
to a system temporary analytic workspace. Free some temporary storage
immediately. You can do so, for example, by DETACHING an analytic
workspace.
Cause: Ran out of temporary tablespace storage.
Action: Increase the amount of temporary tablespace storage.
ORA-37604: (XSPGERRPQUPD) Parallel updating analytic workspace string failed
Cause: Unexpected error occurred to parallel update servers.
20-90 Oracle Database Error Messages
Action: Check the error underneath and act accordingly. AW may need to be
detached.
ORA-37605: error during OLAP AW UPDATE
Cause: An error occurred during the UPDATE process
Action: Refer to the next error in the error stack
ORA-37999: Serious OLAP error: string. Please contact Oracle Technical Support.
Cause: Something unexpected occurred in the OLAP system
Action: Contact Oracle technical support
ORA-38029 to ORA-39965 1 2
ORA-38029: object statistics are locked
Cause: An attept was made to modify optimizer statistics of the object.
Action: Unlock statistics with the DBMS_STATS.UNLOCK_TABLE_STATS
procedure on base table(s). Retry the operation if it is okay to update statistics.
ORA-38101: Invalid column in the INSERT VALUES Clause: string
Cause: INSERT VALUES clause refers to the destination table columns
Action: None
ORA-38102: Invalid column in the INSERT WHERE Clause: string
Cause: INSERT WHERE clause refers to the destination table columns
Action: None
ORA-38103: Invalid column in the UPDATE SET Clause: string
Cause: UPDATE SET clause refers to the source table columns in the LHS
Action: None
ORA-38104: Columns referenced in the ON Clause cannot be updated: string
Cause: LHS of UPDATE SET contains the columns referenced in the ON Clause
Action: None
ORA-38105: Delete not yet supported when Update row-migration is possible
Cause: When Update Row-Migration is possible, Delete in MERGE is not yet
supported
Action: None
ORA-38106: MERGE not supported on join view or view with INSTEAD OF
trigger.
Cause: The MERGE operation contained a join view or view with INSTEAD of
trigger which is not supported.
Action: When using MERGE to modify a view, you must only specify a single
table in the view, and the view cannot have an INSTEAD OF trigger.
ORA-38131: specified SQL handle string does not exist
Cause: The specified SQL handle did not exist in the repository.
Action: Specify correct SQL handle.
ORA-38132: specified SQL ID string does not exist
Cause: The SQL statement for SQL ID did not exist in the cursor cache.
21-2 Oracle Database Error Messages
Action: Specify correct SQL ID.
ORA-38133: invalid parameter name string specified
Cause: An invalid parameter name was specified.
Action: Verify the name of the parameter.
ORA-38134: invalid parameter value string specified
Cause: An invalid parameter value was specified.
Action: Verify the parameter value.
ORA-38135: invalid fixed status value specified
Cause: Specified fixed status value was neither YES or NO.
Action: Specify either 'YES' or 'NO'.
ORA-38136: invalid attribute name string specified
Cause: An invalid attribute name was specified.
Action: Verify the name of the attribute.
ORA-38137: invalid attribute value string specified
Cause: An invalid attribute value was specified.
Action: Verify the attribute value.
ORA-38138: plan name is missing or NULL
Cause: A valid plan name was not specified.
Action: Specify a valid plan name.
ORA-38139: concurrent DDL Error in load plans operation
Cause: A concurrent DDL operation was performed during a load plans
operation.
Action: Try operation again.
ORA-38140: no SQL plan baselines were found
Cause: No SQL plan baselines were found during pack or unpack operation.
Action: Specify correct selection criterion.
ORA-38141: SQL plan baseline string does not exist
Cause: A SQL plan baseline name was specified that did not exist.
Action: Verify the name of the SQL plan baseline.
ORA-38142: SQL plan baseline named string already exists
Cause: A SQL plan baseline already exists with the name specified.
Action: Specify a different name or drop the existing SQL plan baseline.
ORA-38143: invalid enabled status value specified
Cause: Specified enabled status value was neither YES or NO.
Action: Specify either 'YES' or 'NO'.
ORA-38144: specified plan name string does not exist
Cause: The specified plan name did not exist in the repository.
Action: Specify correct plan name.
ORA-38029 to ORA-39965 21-3
ORA-38145: neither SQL handle nor plan name specified
Cause: The SQL handle or plan name was not specified. The SQL handle or plan
name is required.
Action: Specify either SQL handle or plan name or both.
ORA-38146: invalid verify value specified
Cause: Specified verify value was neither YES or NO.
Action: Specify either 'YES' or 'NO'.
ORA-38147: invalid commit value specified
Cause: Specified commit value was neither YES or NO.
Action: Specify either 'YES' or 'NO'.
ORA-38148: invalid time limit specified
Cause: Specified time limit value was not a positive integer.
Action: Specify a positive integer value.
ORA-38149: There is no recommended action for object string in task string.
Cause: The advisor did not generate a recommended action for the given object
and task.
Action: Choose a different object and retry the operation.
ORA-38171: Insufficient privileges for SQL management object operation
Cause: A DDL operation was attempted on a SQL management object by a
session without the proper privileges.
Action: Grant the appropriate privilege.
ORA-38172: No SQL management object satisfies specified filters
Cause: An attempt was made to perform an operation by specifying filters that
did not target any SQL management objects.
Action: Try different filters.
ORA-38173: Invalid value string specified for SQL management object attribute
string
Cause: An invalid attribute value was specified.
Action: Specify a valid attribute value.
ORA-38301: can not perform DDL/DML over objects in Recycle Bin
Cause: Tried to perform DDL or DML operation on Recycle Bin object.
Action: DDL or DML operations are not permitted on Recycle Bin objects.
ORA-38302: invalid PURGE option
Cause: Invalid purge option specified.
Action: Specify a valid purge option.
ORA-38303: invalid option for PURGE TABLESPACE
Cause: Either a token other than USER was found following the tablespace name
or some text was found following USER <user name>.
Action: Place nothing or only USER <user name> after the tablespace name
ORA-38304: missing or invalid user name
21-4 Oracle Database Error Messages
Cause: A valid user name was expected.
Action: Specify a valid user name.
ORA-38305: object not in RECYCLE BIN
Cause: Trying to Flashback Drop an object which is not in RecycleBin.
Action: Only the objects in RecycleBin can be Flashback Dropped.
ORA-38306: this object is not recoverable standalone
Cause: Trying to flashback drop an object other than of type TABLE.
Action: Only tables are recoverable.
ORA-38307: object not in RECYCLE BIN
Cause: Trying to Purge the object which is not in RecycleBin.
Action: Only the objects in RecycleBin can be PURGEDED.
ORA-38308: invalid FLASHBACK DROP option
Cause: Invalid Flashback Drop option specified.
Action: Specify a valid Flashback Drop option.
ORA-38309: object not purgable
Cause: An attempt was made to purge an object that is either not purgable or else
dependent upon some other object.
Action: Cannot purge this object.
ORA-38310: cannot purge tablespace for other users
Cause: An attempt was made to purge the tablespace for a different user by a user
who does not have system DBA priviledges.
Action: Cannot purge the tablespace for some other user.
ORA-38311: cannot purge objects owned by other users
Cause: An attempt was made to purge an object which is owned by some other
user.
Action: Cannot purge this object.
ORA-38312: original name is used by an existing object
Cause: An attempt was made to recover an object preserving the original name,
but that name is taken up by some other object.
Action: use the RENAME clause to recover the object with a different name.
ORA-38320: policy does not exist
Cause: An attempt was made to delete a nonexistent policy.
Action: Correct the policy name.
ORA-38321: duplicate policy name specified
Cause: A policy name was specified that already existed under this schema.
Action: Correct the policy name.
ORA-38322: scope of policy not specified
Cause: An attempt was made to add a policy without the scope.
Action: Specify a scope when creating a policy.
ORA-38029 to ORA-39965 21-5
ORA-38323: policy conflicts with policy string
Cause: An attempt was made to create a policy with the same action type and
based on the same statistic as another policy on the object.
Action: Use a different action and/or statistic for the new policy, or delete the old
policy.
ORA-38324: policy conflicts with policy string
Cause: An attempt was made to create a policy with the same action, scope and
compression level as another policy on the object.
Action: Use a different action, scope and/or level for the new policy, or delete the
old policy.
ORA-38325: policy conflicts with policy string
Cause: An attempt was made to create a compression policy that conflicts with
another policy on the object.
Action: Change the policy so that policies with a higher compression level take
effect after policies with a lower compression level, or delete the old policy.
ORA-38326: schema level policies are not supported
Cause: Attempt was made to create a schema level policy.
Action: Do not create a schema level policy.
ORA-38327: invalid argument value
Cause: The specified API argument values were of the wrong value range.
Action: Supply valid values for the API.
ORA-38328: inconsistent internal state
Cause: An inconsistency was detected in ILM related data in the dictionary.
Action: Contact Oracle Support Services.
ORA-38329: internal ILM error
Cause: An internal error occurred during execution of ILM related activity.
Further information can be found in the alert log.
Action: Fix the problem and retry the operation.
ORA-38330: insufficient privilege for ILM operation
Cause: Sufficient privileges were not granted for the ILM operation.
Action: Retry operation with sufficient privileges granted. Consult
documentation for privileges required to perform the ILM operation.
ORA-38331: row-level write activity tracking not enabled on the table
Cause: An attempt was made to create a modification time-based policy when
row-level write tracking was not enabled on the object.
Action: Ensure that row-level write tracking is enabled on the table.
ORA-38332: valid time periods were not present on the table
Cause: An attempt was made to create a valid time-based policy when valid time
periods were not present on the table.
Action: Add valid time periods to the table.
ORA-38333: row-level access activity tracking not enabled on the table
21-6 Oracle Database Error Messages
Cause: An attempt was made to create an access time-based policy when
row-level access tracking was not enabled on the object.
Action: Ensure that row-level access tracking is enabled on the table.
ORA-38334: segment-level access activity tracking not enabled on the table
Cause: An attempt was made to create an access time-based policy when
segment-level access tracking was not enabled on the object.
Action: Ensure that segment-level access tracking is enabled on the table.
ORA-38335: sysdba privilege is required
Cause: SYSDBA privilege is required for applying ILM policies on a tablespace.
Action: Grant user SYSDBA role before applying tablespace level ILM policies.
ORA-38336: invalid policy
Cause: A row level policy was used with a compression level other than OLTP.
Action: Use the OLTP compression level with row level compression policies.
ORA-38337: invalid policy
Cause: A custom policy is only allowed at the segment level.
Action: Change the scope of the policy to be of type segment.
ORA-38338: incorrect ILM policy scope
Cause: An attempt was made to create an Information Lifecycle Management
(ILM) policy with incompatible scope.
Action: Ensure that the scope of the ILM policy is compatible.
ORA-38339: invalid action specified
Cause: An invalid action was specified in the policy definition.
Action: Specify a valid action in the policy definition.
ORA-38340: invalid policy
Cause: An attempt was made to create a custom policy at the tablespace level.
Action: Specify the policy directly on the desired objects.
ORA-38341: policy conflicts with policy string
Cause: An attempt was made to create more than one storage tiering policy
directly on an object.
Action: Delete the conflicting policy before creating a new policy.
ORA-38342: heat map not enabled
Cause: An attempt was made to create an Information Lifcecycle Management
(ILM) policy when heat map was not enabled.
Action: Enable heat map before creating a new ILM policy.
ORA-38343: ADO online mode not supported with supplemental logging enabled
Cause: An attempt was made to perform an automatic data optimization (ADO)
operation with supplemental logging enabled.
Action: Disable supplemental logging or switch to ADO offline mode and retry.
ORA-38393: ILM internal out-of-space error
Cause: Information Lifecycle Management (ILM) internal operation encountered
out-of-space error.
ORA-38029 to ORA-39965 21-7
Action: None
ORA-38394: test event for table ILM operations
Cause: Internal testing event for table Information Lifecycle Management (ILM)
operations.
Action: None
ORA-38395: debug event for table ILM operations
Cause: There was an internal debugging event for table Information Lifecycle
Management (ILM) operations.
Action: None
ORA-38396: table is already enabled for the ILM feature
Cause: The table was already enabled for the specified Information Lifecycle
Management (ILM) feature.
Action: No action required.
ORA-38397: table is not enabled for the ILM feature
Cause: An attempt was made to perform an Information Lifecycle Management
(ILM) operation on a table on which the specified ILM feature is not enabled.
Action: No action required.
ORA-38398: DDL not allowed on the system ILM column
Cause: An attempt was made to drop, rename, or modify a system Information
Lifecycle Management (ILM) column.
Action: No action required.
ORA-38399: cannot update the system ILM column
Cause: An attempt was made to update a system Information Lifecycle
Management (ILM) column.
Action: No action required.
ORA-38400: cannot combine ILM operation with other operations
Cause: An attempt was made to combine Information Lifecycle Management
(ILM) operation with other ALTER TABLE operations.
Action: Ensure that ILM is the sole operation specified in ALTER TABLE.
ORA-38401: synonym string not allowed
Cause: An attempt was made to use a synonym for a data type of an attribute or a
table alias.
Action: Use the object name instead of the synonym.
ORA-38402: invalid name: empty string or spaces in the name
Cause: There were spaces in the name.
Action: Remove spaces in the name or use quotes around the name.
ORA-38403: attribute set name may not be longer than 22 characters
Cause: The attribute set name was longer than 22 characters.
Action: Choose a name that has 22 or fewer characters.
ORA-38404: schema extension not allowed for the attribute set name
21-8 Oracle Database Error Messages
Cause: There was a schema extension for the attribute set name. Attribute sets are
always created in the current schema and thus schema extended names are not
allowed.
Action: Create the attribute set from the appropriate schema.
ORA-38405: quotes not allowed in the attribute set name
Cause: The attribute set name contained quotes.
Action: Remove quotes in the attribute set name.
ORA-38406: attribute set string already exists
Cause: An attribute set with a matching name already exists in the current
schema.
Action: Drop the existing attribute set or choose a different name.
ORA-38407: The ADT associated with the attribute set already exists.
Cause: The Abstract type (ADT) with the same name as the attribute set already
exists in the current schema.
Action: Create the attribute set for the existing ADT or drop the ADT.
ORA-38408: The ADT "string" does not exist in the current schema.
Cause: An attempt was made to create the attribute set from a nonexistent ADT.
Action: Make sure that the ADT with the same name as the attribute set exists in
the current schema.
ORA-38409: invalid name or option for the attribute set: string
Cause: An invalid name or option was used for the attribute set.
Action: Set serveroutput ON and repeat the operation for additional information.
ORA-38410: schema extension not allowed for the table name
Cause: An attempt was made to use a schema extended name for the table storing
expressions.
Action: The table storing expressions and the corresponding attribute set should
be created in the same schema.
ORA-38411: invalid datatype for the column storing expressions
Cause: An attempt was made to create an expression column from a column of
invalid datatype.
Action: Create a VARCHAR2 or CHAR column to store expressions in a table.
ORA-38412: Expression set column string does not exist.
Cause: The column storing expressions does not exist.
Action: Pass a valid name for the column storing expressions.
ORA-38413: elementary attribute name may not be longer than 32 characters
Cause: An attempt was made to create an elementary attribute with a name
longer than 32 characters.
Action: Use a shorter name for the elementary attribute.
ORA-38414: invalid datatype for the attribute string
Cause: The datatype specified for the attribute was invalid.
Action: If the datatype is an ADT, make sure that the ADT exists and the current
user has execute permissions to it.
ORA-38029 to ORA-39965 21-9
ORA-38415: invalid name or datatype for the attribute: string
Cause: An invalid name or datatype was used for the attribute.
Action: Set serveroutput ON and repeat the operation for additional information.
ORA-38416: A stored attribute may not be longer then 300 characters.
Cause: An attempt was made to create a stored or indexed attribute longer than
300 characters.
Action: A predicate with such attribute may not be indexed. It will be evaluated
as sparse predicate.
ORA-38417: attribute set string does not exist
Cause: An attempt was made to use an attribute set that does not exist.
Action: Create the attribute set or choose an existing attribute set.
ORA-38418: ADT associated with the attribute set string does not exist
Cause: The ADT with the same name as the attribute set was not found in the
current schema.
Action: Drop the attribute set and recreate it.
ORA-38419: invalid identifier in attribute : string
Cause: An identifier used in the stored/indexed attribute sub-expression was not
defined or was invalid.
Action: Create all the required elementary attributes and user-defined functions
and try again.
ORA-38420: invalid stored attribute sub-expression: string
Cause: The sub-expression used for the stored expression was invalid.
Action: Set serveroutput ON and repeat the operation for additional information.
ORA-38421: attribute string already exists
Cause: An attribute with a matching name (or form) already exists in the attribute
set.
Action: Drop the existing attribute or choose a different name for the new
attribute.
ORA-38422: invalid datatype for the attribute: string
Cause: An attempt was made to create an attribute with invalid datatype.
Action: If the data type of the attribute is an ADT, make sure that the type exists.
ORA-38423: Attribute set created from an ADT may not be extended.
Cause: An attempt was made to add an elementary attribute to an attribute set
created from an ADT.
Action: Create a new attribute set and add all the required elementary attributes
one at a time.
ORA-38424: no attribute set currently assigned to the expression set
Cause: An attempt was made to un-assign an attribute set from an expression set
when there is no attribute set assigned to it.
Action: No action is required.
ORA-38425: attribute set used for an index object may not be unassigned
21-10 Oracle Database Error Messages
Cause: An attempt was made to un-assign an attribute set from an expression set
when there is an Expression Filter index defined on the column.
Action: Drop the index before un-assigning the attribute set.
ORA-38426: attribute set assigned to an expression set may not be dropped
Cause: An attempt was made to drop an attribute set when it is still associated
with an expression set.
Action: Un-assign the attribute set from the expression set before dropping it.
ORA-38427: attribute string does not exist
Cause: An attempt was made to use an attribute set that does not exist.
Action: Create the attribute set.
ORA-38428: too many attributes selected for indexing
Cause: An attempt was made to create an expression filter index with more than
490 indexed attributes.
Action: Remove some of the indexed attributes. Make sure that the default
indexed attributes associated with the attribute set combined with the indexed
attributes specified in the Create Index Parameters clause are less than or equal to
490.
ORA-38429: invalid datatype for a stored attribute: string
Cause: The (resulting) datatype for the attribute was not appropriate for storing.
Action: Choose a stored attribute that has a resulting datatype of NUMBER,
VARCHAR2, CHAR or DATE.
ORA-38430: Operation "string" not supported in the current release.
Cause: An attempt was made to perform an unsupported operation.
Action: Do not use the operation.
ORA-38431: could not evaluate subexpression "string" for rowid "string"
Cause: Either the expression was not a valid SQL-WHERE clause format or it had
references to nonexistent schema objects.
Action: Correct the expression.
ORA-38432: EVALUATE operator only allowed on an expression column
Cause: An attempt was made to use the EVALUATE operator on a column not
configured as a column storing expressions.
Action: Assign an attribute set to the column.
ORA-38433: index "string" could not be maintained due to "string"
Cause: The error was caused by the recursive operation.
Action: Fix the error and retry.
ORA-38434: could not evaluate expression "string"
Cause: Either the expression was not in a valid SQL-WHERE clause format or it
had references to nonexistent schema objects or there is a missing attribute value.
Action: Set serveroutput ON for more details.
ORA-38435: missing elementary attribute value or invalid name-value pairs
Cause: The second argument to the EVALUATE operator had either a missing
attribute or an invalid value for an attribute.
ORA-38029 to ORA-39965 21-11
Action: Try again after fixing the error.
ORA-38436: attribute set used for an Expression set may not be modified.
Cause: An attempt was made to add an elementary attribute to an attribute set
assigned to an expression set.
Action: Un-assign the attribute set and try again.
ORA-38437: The ADT "string" may not contain any user methods.
Cause: An attempt was made to create an attribute set from an ADT that has one
or more user methods.
Action: Drop the ADT and recreate it with no user methods.
ORA-38438: getVarchar not possible due to "string" datatype in the attribute set
Cause: An attempt was made to use the getVarchar API when the attribute set has
one or more non-scalar types.
Action: Use AnyData conversion to encode the data item.
ORA-38439: invalid operation "string"
Cause: An attempt was made to use an invalid operation.
Action: Use one of the following operations : ADD, DROP
ORA-38440: attribute set string does not exist
Cause: An attempt was made to copy an attribute set that is not accessible from
the current schema.
Action: Grant execute permissions on the corresponding ADT to the current user
and try again.
ORA-38441: System could not derive the list of STORED and INDEXED attributes.
Cause: The attribute set was created without default index parameters.
Action: Specify the default index parameters for the attribute set or include a
valid PARAMETERS clause for the CREATE INDEX command.
ORA-38442: The ADT "string" is not in a valid state.
Cause: An attempt was made to use an ADT that is not in a valid state.
Action: Check the INCOMPLETE field in the user_types catalog view to make
sure that the ADT is in a valid state. Drop the invalid ADT and recreate the
corresponding attribute set.
ORA-38443: An attribute set should be assigned to the expression set for statistics
collection.
Cause: An attempt was made to collect statistics for an expression set with no
attribute set assigned to it.
Action: Assign an attribute set to the expression set before collecting the statistics.
ORA-38444: statistics do not exist for the expression set
Cause: An attempt was made to clear the statistics that do not exist.
Action: No action was required.
ORA-38445: TOP clause not allowed with no statistics
Cause: An attempt was made to use the TOP parameters clause with no statistics
available for the expression set.
Action: Collect statistics for the expression set and try again.
21-12 Oracle Database Error Messages
ORA-38446: Error with embedded ADT "string" in the attribute set.
Cause: The embedded ADT has errors.
Action: Set serveroutput ON for additional information.
ORA-38447: Type required for the embedded ADT attribute "string" is missing
Cause: Object type required for the embedded ADT was missing.
Action: Set serveroutput ON for additional information.
ORA-38448: Indexing predicates with "string" operator is not supported.
Cause: An unsupported operator was used in the exf$indexoper array.
Action: Choose the operators from this list : =, <, >, <=, >=, !=, is null, is not null,
nvl, and between.
ORA-38449: table "string" does not exist or is not accessible
Cause: An attempt was made to create a table alias for a table that does not exist
or is not accessible.
Action: Grant select privileges on the table to the current user.
ORA-38450: error computing a stored attribute for the expression set.
Cause: Either values for one of the attributes was incorrect or a stored attribute
was invalid due to broken dependencies.
Action: Correct the input.
ORA-38451: index is in an inconsistent state
Cause: One or more secondary objects used to maintain the index did not exist
Action: Drop the index and recreate it.
ORA-38452: Expression Filter index name may not be longer than 25 characters
Cause: An attempt was made to use a name longer than 25 characters for the
Expression Filter index.
Action: Choose a name that has 25 or fewer characters
ORA-38453: ExpFilter index should be created in the same schema as the base table.
Cause: An attempt was made to create the Expression Filter index in a schema
other than that of the base table.
Action: Create the index in the same schema as the base table.
ORA-38454: attribute set not defined for the column being indexed
Cause: An attempt was made to create an Expression Filter index on a column
with no attribute set association.
Action: Assign an attribute set to the expression set column begin indexed.
ORA-38455: Expression Filter index should be created by the owner.
Cause: An attempt was made to create the Expression Filter index by a user who
is not the owner of the index.
Action: Create the index using owner's privileges.
ORA-38456: The attribute set "string" is in an inconsistent state.
Cause: The attribute set was in an inconsistent state due to broken dependencies.
Action: Set serveroutput ON for more details. The attribute set may not be reused
after this error.
ORA-38029 to ORA-39965 21-13
ORA-38457: The attribute "string" is not a valid XMLType attribute.
Cause: An attempt was made to use a non-XMLType attribute to configure XPath
filtering.
Action: Use an attribute of sys.XMLType datatype to configure XPath filtering.
ORA-38458: invalid operation "string" for XPATH_FILTER_PARAMETERS
Cause: An attempt was made to use an invalid operation.
Action: Use one of the following operations : ADD, DROP.
ORA-38459: XML Tag "string" not found for the XMLType attribute "string"
Cause: An Attempt was made to use a non-existent XML Tag.
Action: Correct the name of the XML Tag or the XMLType attribute.
ORA-38460: filtering based on datatype "string" not supported for XML Tags
Cause: An attempt was made to configure XPath filtering with an XML Tag of
unsupported datatype.
Action: Leave the XML Tag out of filter parameters. It will be processed as sparse
predicate
ORA-38461: XML Tag "string" already exists for the XMLType attribute "string"
Cause: An attempt was made to create a duplicate XML Tag.
Action: Choose a different XML Tag.
ORA-38462: invalid attribute list
Cause: The input was missing an attribute list or had null values for the attribute
names.
Action: Correct the input.
ORA-38463: invalid XML Tag list
Cause: The input was missing a tag list or had null values for the tag names.
Action: Correct the input.
ORA-38464: expression set is not empty.
Cause: An attempt was made to assign an attribute set to a non-empty expression
set.
Action: Use FORCE = 'TRUE' to validate all the existing expressions.
ORA-38465: failed to create the privilege checking trigger due to: string
Cause: Creation of the trigger failed due to the error listed in the message.
Action: Set serveroutput ON for more information.
ORA-38466: user does not have privileges to CREATE/MODIFY expressions
Cause: An attempt was made to INSERT or UPDATE a column storing expression
without appropriate permissions.
Action: Appropriate privileges on the expression set should be granted by the
owner of the expression set.
ORA-38467: user cannot GRANT/REVOKE privileges to/from himself
Cause: An attempt was made to GRANT or REVOKE privileges to or from the
current user.
21-14 Oracle Database Error Messages
Action: The the to_user or from_user field should be different from the user
performing the operation.
ORA-38468: column "string" is not identified as a column storing expressions.
Cause: An attempt was made to grant permission on a nonexistent expression set.
Action: Make sure that the table and the column exist and an attribute set is
associated with the column.
ORA-38469: invalid privilege for an expression set: string
Cause: An attempt was made to use an invalid privilege.
Action: See documentation for a valid privilege.
ORA-38470: cannot revoke a privilege that was not granted.
Cause: An attempt was made to revoke a privilege that had not been granted.
Action: Check catalog views to see if the user has the privilege.
ORA-38471: ROWIDs for table aliases cannot be null
Cause: An attempt was made to pass a null value for the table alias attribute in
the data item, which is not permitted.
Action: Pass a valid rowid value for the table alias.
ORA-38472: VARCHAR representation of the data item is too long.
Cause: The VARCHAR representation of data item was too long.
Action: Use the EVALUATE operator with AnyData argument instead.
ORA-38473: cannot drop a type used for Expression Filter attribute set
Cause: An attempt was made to drop an ADT that was used to maintain an
attribute set for the Expression Filter.
Action: Query USER_EXPFIL_ATTRIBUTE_SETS view to see the dependency.
ORA-38474: attribute set may not have attributes of TABLE COLLECTION type.
Cause: An attempt was made to create an attribute with a TABLE COLLECTION
type.
Action: Use VARRAYs instead of table collection, if possible.
ORA-38475: The attribute set and the associated ADT are out of sync.
Cause: The ADT was directly modified by CREATE or ALTER operations.
Action: Drop the attribute set and recreate it from scratch.
ORA-38476: abstract type used for an Attribute set may not be modified.
Cause: An attempt was made to alter a type (ADT) that is used to maintain an
attribute set of an Expression set.
Action: Do not modify the ADT directly. Use DBMS_EXPFIL APIs instead.
ORA-38477: attribute set cannot be derived from an evolved type or a subtype.
Cause: An attempt was made to create an attribute set from an evolved ADT or a
subtype.
Action: The ADT used for the attribute set cannot be an evolved type or a
subtype.
ORA-38478: creation of system trigger EXPFIL_DROPOBJ_MAINT failed
ORA-38029 to ORA-39965 21-15
Cause: The creation of the system trigger EXPFIL_DROPOBJ_MAINT failed due
to missing Expression Filter dictionary tables.
Action: Try a clean installation again. If this error is ignored, the Expression Filter
dictionary could have some stale entries.
ORA-38479: creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed
Cause: The creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed
due to missing Expression Filter dictionary tables.
Action: Try a clean installation again. If this error is ignored, the user will be able
to evolve ADTs associated with the attribute set, thus causing spurious errors.
ORA-38480: creation of system trigger EXPFIL_ALTEREXPTAB_MAINT failed.
Cause: The creation of system trigger EXPFIL_ALTEREXPTAB_MAINT failed due
to errors in SYS.EXF$DBMS_EXPFIL_SYSPACK package.
Action: Try a clean installation again. If this error is ignored, a RENAME of the
expression table may cause the EVALUATE queries to fail.
ORA-38481: ADT "string" is used for a dependent object.
Cause: An attempt was made to create an attribute set from an ADT which is used
by one or more dependent objects.
Action: Use a new ADT instead.
ORA-38482: no elementary attributes defined in the attribute set
Cause: An attempt was made to use an empty attribute set.
Action: Create one or more elementary attributes for the attribute set.
ORA-38483: invalid FUNCTION/PACKAGE/TYPE name: "string"
Cause: An attempt was made to use an invalid name format.
Action: The function/package/type name should be specified in the following
format [owner.]object_name
ORA-38484: FUNCTION/PACKAGE/TYPE string does not exist
Cause: Attempt was made to use a object that does not exist.
Action: Query ALL_OBJECT view to ensure that the object exists.
ORA-38485: invalid object type for the user-defined function
Cause: An attempt was made to use an invalid object as a function.
Action: Valid object types are FUNCTION / PACKAGE / TYPE
ORA-38486: FUNCTION/PACKAGE/TYPE already exists for the attribute set
Cause: An attempt was made to add a duplicate function to the list.
Action: Use a different object name.
ORA-38487: FUNCTION/PACKAGE/TYPE "string" not allowed in the expression
Cause: An attempt was made to use an un-approved function in the expression.
Action: Add the function to the corresponding attribute set
ORA-38488: attribute set already assigned to the column storing expressions
Cause: An attempt was made to reassign an attribute set to an expression column.
Action: Query USER_EXPFIL_EXPRESSION_SETS view to find the attribute set
assigned the expression set
21-16 Oracle Database Error Messages
ORA-38489: predicate table creation failed due to: ORAstring
Cause: Predicate table creation failed due to the reported error.
Action: Set serveroutput ON for additional information
ORA-38490: invalid name: quotes do not match
Cause: The quotes in the name did not match.
Action: Correct the name to match the quotes.
ORA-38491: could not evaluate subexpression for rowid "string"
Cause: Either the expression was not in a valid SQL-WHERE clause format or it
had references to nonexistent schema objects.
Action: Correct the expression.
ORA-38492: invalid ALTER INDEX parameters clause "string"
Cause: An invalid parameters clause was specified with the ALTER INDEX
command.
Action: See documentation for a valid list of parameters.
ORA-38493: feature not enabled : Expression Filter index
Cause: An attempt was made to create an Expression Filter index in Standard
Edition.
Action: Do not attempt to use this feature.
ORA-38494: column in the table alias and an attribute have matching names
Cause: One of the attributes in the set has the same name as the name of one of
the columns in the table configured for table alias.
Action: If possible, use a different name for the attribute.
ORA-38495: data type for the stored attribute string is inconsistent.
Cause: The actual data type for the stored attribute configured for the Expression
Filter index object did not match the data type recorded in the Expression Filter
dictionary.
Action: Delete the attribute from the default index attributes and recreate it.
ORA-38496: Expression Filter index is not in a valid state
Cause: An attempt was made to REBUILD an Expression Filter index that was not
valid.
Action: Use DEFAULT keyword in the parameters clause to rebuild the index
from defaults or drop and recreate the index.
ORA-38497: Expression Filter index does not exist
Cause: Index with a matching name does not exist or the index was not created
using ExpFilter indextype.
Action: Identify the correct index using the Expression Filter catalog views
ORA-38498: invalid stored attribute for the index object : string
Cause: The expression filter index object has a stored or indexed attribute that had
broken dependencies.
Action: Make sure that all the identifiers used in the attribute are valid.
ORA-38499: expression set already configured for stored/indexed attributes
ORA-38029 to ORA-39965 21-17
Cause: The expression set already had a list of stored and indexed attributes.
Additional attributes cannot be specified in the CREATE INDEX parameters
clause.
Action: Remove TOP, STOREATTRS and INDEXATTRS clauses from the
parameters clause or clear the expression set statistics using DBMS_
EXPFIL.INDEX_PARAMETERS API.
ORA-38500: string
Cause: There was a generic error
Action: See documentation for further information.
ORA-38501: sub-query not allowed in the expression
Cause: An attempt was made to use a sub-query in the expression.
Action: Do not use sub-queries in the expressions.
ORA-38502: invalid XML tag: string
Cause: An attempt was made to use an invalid XML tag for the index.
Action: Correct the XML tag and retry.
ORA-38503: index already defined using the parameters
Cause: An attempt was made to modify the index parameters after the index
creation.
Action: Drop the index and retry.
ORA-38504: this operator not allowed with the configured attribute set
Cause: An attempt was made to use the operator binding with an attribute set
containing more than one (table alias) attribute. This is not permitted.
Action: Use a different operator binding.
ORA-38505: invalid default value for the attribute
Cause: An attempt was made to use an invalid default value or a default that is
larger than 100 characters.
Action: Specify a correct default value.
ORA-38506: invalid attribute type for text predicates
Cause: An attempt was made to use an invalid type for an attribute configured for
text predicates.
Action: Use either a VARCHAR or a CLOB attribute instead.
ORA-38507: attributes of string data type should be indexed
Cause: An attempt was made to configure an attribute of spatial or text data type
as stored predicate group.
Action: Configure them as indexed predicate groups instead.
ORA-38601: FI Not enough memory for frequent itemset counting: string
Cause: The memory size did not satisfy the minimum memory requirement.
Action: In workarea_size_policy='manual' mode, set _fic_area_size to a
reasonably larger value. Or, In workarea_size_policy='auto' mode, this error
should never happen.
ORA-38602: FI invalid input cursor
21-18 Oracle Database Error Messages
Cause: The input cursor did not return exactly two columns for transactional
input format or the input cursor didn't have consistent data types for horizontal
input format
Action: For transactional input format, specify that the input cursor returns
exactly two columns: one for transaction-id, one for item-id. For horizontal input
format, make sure the input cursor's columns have the same data types.
ORA-38603: FI including & excluding cursor can only return one column
Cause: The including & excluding cursor did not return exactly one column.
Action: Specify that the cursor return only one column: item-id.
ORA-38604: FI including & excluding cursor item-id type must match input cursor
item-id type
Cause: The including & excluding cursor item-id type did not match input cursor
item-id type
Action: Specify that the item-id type of the cursors match each other.
ORA-38605: FI not enough memory(stringK) for candidate generation(stringK)
Cause: There was insufficient available memory for candidate generation.
Action: In workarea_size_policy='manual' mode, set _fic_area_size to a
reasonably larger value. Or, in workarea_size_policy='auto' mode, set pga_
aggregate_target to a reasonably larger value.
ORA-38606: FI support threshold not between [0, 1]
Cause: The user inputed a support threshold not in the range of [0, 1].
Action: The user should adjust the input value in the range of [0, 1].
ORA-38607: FI minimum and maximum itemset length not between [1, string]
Cause: The inputed minimum or maximum itemset length exceed the internal
maximum itemset length or less than 1.
Action: The user should adjust the input value not larger than the internal
maximum itemset length and not less than 1.
ORA-38608: FI itemset minimum-length(string) should not be greater than
maximum length(string)
Cause: The user inputed minimum length is more than maximum length.
Action: The user should adjust the input values to make the minimum length less
than or equal to the maximum length.
ORA-38609: FI Not enough memory for tree counting, requires at least stringKB
Cause: The memory size did not satisfy the minimum memory requirement for
tree counting.
Action: In workarea_size_policy='manual' mode, set _fic_area_size to a
reasonably larger value. Or, In workarea_size_policy='auto' mode, this error
should never happen.
ORA-38610: FI "string" name prefix is reserved for frequent itemset counting
Cause: An error occurred because DBMS_FREQUENT_ITEMSET and prefix
ORA_FI are reserved for the DBMS_FREQUENT_ITEMSET package's internal use.
Action: Do not re-define functions with names starting with DBMS_FREQUENT_
ITEMSET package or ORA_FI.
ORA-38029 to ORA-39965 21-19
ORA-38611: FI input cursor's item type is not supported
Cause: The input cursor's item type is not number or character type
Action: Redefine the input cursor so that item type is number or character type.
ORA-38612: FI item length cannot exceed half of one database block.
Cause: The item's length was more than half of one database block.
Action: Redefine the data type of the item column so that its maximum length is
less than half of one database block.
ORA-38613: FI Cursor is returning less than 2 columns.
Cause: Cursor parameter is returning less than 2 columns.
Action: Modify the Cursor argument to return 2 columns.
ORA-38620: DT expressions in input cursor do not have an alias name
Cause: Expressions in input cursor do not have an alias name.
Action: Add an alias name for the expression.
ORA-38621: Decision Tree maximum depth setting not between [2, 20]
Cause: The user specified a max tree depth not in the range of [2, 20].
Action: The user should adjust the input value to be in the range of [2, 20].
ORA-38622: Decision Tree not enough memory, requires at least stringKB
Cause: The memory size did not satisfy the minimum memory requirement for
decision tree building.
Action: In workarea_size_policy='manual' mode, set _dtree_area_size to a
reasonably larger value. Or, In workarea_size_policy='auto' mode, please raise
pga_aggregate_target to a reasonably larger value.
ORA-38700: Limit of string flashback database logs has been exceeded.
Cause: The maximum number of flashback database log files was exceeded.
Action: DB_FLASHBACK_RETENTION_TARGET may be set to high. Modify it
to a smaller value.
ORA-38701: Flashback database log string seq string thread string: "string"
Cause: This message reports the filename for details of another message.
Action: Other messages will accompany this message. See the associated
messages for the appropriate action to take.
ORA-38702: Cannot update flashback database log file header.
Cause: Could not write to the flashback database log file.
Action: Restore access to the file.
ORA-38703: Type string in header is not a flashback database log file.
Cause: A corrupt flashback database log file header was read.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38704: Checksum error in flashback database log file header.
Cause: The flashback database log file header contained a checksum that does not
match the value calculated from the file header as read from disk. This means the
file header was corrupt.
21-20 Oracle Database Error Messages
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38705: Expected block size string does not match string in log header.
Cause: When the flashback log file header was read, the block size in the control
file did not match the block size contained in the header.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38706: Cannot turn on FLASHBACK DATABASE logging.
Cause: An ALTER DATABASE FLASHBACK ON command failed. Other
messages in the alert log describe the problem.
Action: Fix the problem and retry.
ORA-38707: Media recovery is not enabled.
Cause: An ALTER DATABASE FLASHBACK ON command failed because media
recovery was not enabled.
Action: Turn on media recovery with an ALTER DATABASE ARCHIVELOG
command and then retry the command.
ORA-38708: not enough space for first flashback database log file
Cause: An ALTER DATABASE FLASHBACK ON command failed because there
was not enough space in the Recovery Area for the first flashback database log file.
Action: Make more space in the Recovery Area. For example, this can be done by
increasing the value of DB_RECOVERY_FILE_DEST_SIZE.
ORA-38709: Recovery Area is not enabled.
Cause: An ALTER DATABASE FLASHBACK ON command failed because the
Recovery Area was not enabled.
Action: Set DB_RECOVERY_FILE_DEST to a location and retry.
ORA-38710: Flashback log version string is incompatible with ORACLE version
string.
Cause: The flashback database log file was rejected because it appeared to be
written by an incompatible version of Oracle.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38711: Corrupt flashback log block header: block string
Cause: A corrupt Flashback Database log file block header was read. More
information was dumped to the trace file.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38712: Corrupt flashback log record header: block string, offset string.
Cause: A corrupt flashback database log record header was read. Either the record
type or length were incorrect. More information was dumped to the trace file.
ORA-38029 to ORA-39965 21-21
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38713: Flashback Database logging is already turned on.
Cause: An ALTER DATABASE FLASHBACK ON command had no effect because
flashback database logging was already on.
Action: No action required.
ORA-38714: Instance recovery required.
Cause: An ALTER DATABASE FLASHBACK ON command failed because the
database either crashed or was shutdown with the ABORT option.
Action: Open the database and then enter the SHUTDOWN command with the
NORMAL or IMMEDIATE option.
ORA-38715: Invalid log number specified in the DUMP FLASHBACK command.
Cause: An invalid log number was used when dumping a flashback database log
file.
Action: Specify a valid flashback database log number.
ORA-38716: Must supply an integer for the TYPE option.
Cause: An invalid value was specified for TYPE in the DUMP FLASHBACK
command.
Action: Specify an integer value.
ORA-38717: Invalid DUMP FLASHBACK option.
Cause: An invalid option was specified in the DUMP FLASHBACK command.
Currently the only options allowed are: DBA, TYPE, and LOGICAL.
Action: Retry the command with the correct options.
ORA-38718: Invalid thread number specified in the DUMP FLASHBACK
command.
Cause: An invalid thread number was used in dumping the flashback database
log files for a thread.
Action: Specify a valid thread number.
ORA-38719: Invalid DUMP FLASHBACK object.
Cause: An invalid object was specified in a DUMP FLASHBACK command.
Currently the only objects allowed are: LOGFILE or THREAD.
Action: Retry the command with the correct options.
ORA-38720: Missing log file name or number.
Cause: A log file name or number was missing in a DUMP FLASHBACK
LOGFILE command.
Action: Supply a valid log file name or number.
ORA-38721: Invalid file number.
Cause: An invalid file number was specified in the DBA clause of a DUMP
FLASHBACK command.
Action: Supply a valid file number.
ORA-38722: ON or OFF expected.
21-22 Oracle Database Error Messages
Cause: The ALTER DATABASE FLASHBACK command was specified without
the ON or OFF keyword.
Action: Retry the command with the ON or OFF keyword.
ORA-38723: Invalid SCN expression.
Cause: The SCN keyword was specified in a FLASHBACK DATABASE command
but the SCN expression was invalid.
Action: Retry the command using a valid SCN number.
ORA-38724: Invalid option to the FLASHBACK DATABASE command.
Cause: An invalid option was specified to the FLASHBACK DATABASE
command. Valid options are: SCN or TIMESTAMP.
Action: Correct the syntax and retry the command.
ORA-38725: specified name "string" does not match actual "string"
Cause: The database name specified in a FLASHBACK DATABASE command did
not match the name of the currently mounted database.
Action: Correct the database name spelling or DISMOUNT the mounted database
and mount the correct database.
ORA-38726: Flashback database logging is not on.
Cause: A FLASHBACK DATABASE command was tried but flashback database
logging has not been enabled.
Action: Flashback database logging must be enabled via the ALTER DATABASE
FLASHBACK ON command before a FLASHBACK DATABASE command can be
tried. If the database must be taken back in time then a restore and incomplete
recovery must be performed.
ORA-38727: FLASHBACK DATABASE requires a current control file.
Cause: The control file being used is a backup control file.
Action: FLASHBACK DATABASE cannot be used with a backup control file. If
the database must be taken back in time then a restore and an incomplete recovery
must be performed.
ORA-38728: Cannot FLASHBACK DATABASE to the future.
Cause: An SCN or time stamp provided in a FLASHBACK DATABASE command
was in the future.
Action: Supply a proper SCN or time stamp and retry the command.
ORA-38729: Not enough flashback database log data to do FLASHBACK.
Cause: There was not enough flashback database log data to do the FLASHBACK
DATABASE.
Action: If the database must be taken back in time then a restore and incomplete
recovery must be performed.
ORA-38730: Invalid SCN/TIMESTAMP expression.
Cause: The expression supplied in a FLASHBACK DATABASE command was
invalid.
Action: Retry the command using a valid number or time stamp expression.
ORA-38731: Expected version string does not match string in log header.
Cause: The version of the flashback database log file header was corrupt.
ORA-38029 to ORA-39965 21-23
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38732: Expected file size string does not match string.
Cause: The file size indicated in the control file did not match the file size
contained in the flashback log file header. The flashback database log file was
corrupt.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38733: Physical size string less than needed string.
Cause: A flashback database log file shrank in size. This was likely to have been
caused by operator or operating system error.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38734: Flashback log is inconsistent; belongs to another database.
Cause: The database ID in the flashback database log file did not match the
database ID in the control file.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38735: Wrong log number string in flashback log file header.
Cause: The log file number in the flashback database log file did not match the
control file.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38736: Wrong thread number string in flashback log file header.
Cause: The thread number in the flashback database log file did not match the
control file.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38737: Expected sequence number string doesn't match string
Cause: The flashback database log is corrupted or is an old version.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38738: Flashback log file is not current copy.
Cause: A check of flashback database log file header at database open found that
the flashback database log appeared to be an incorrectly restored backup.
Flashback database log files cannot be backed up and restored.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
21-24 Oracle Database Error Messages
ORA-38739: Flashback log file is more recent than control file.
Cause: The control file change sequence number in the flashback database log file
was greater than the number in the control file. This implies that the wrong control
file was being used. Note that repeatedly causing this error can make it stop
happening without correcting the real problem. Every attempt to open the
database will advance the control file change sequence number until it is great
enough.
Action: FLASHBACK DATABASE can only be used with the current control file.
If it is not available, then a restore and an incomplete recovery must be performed
instead.
ORA-38740: Usable blocks value string is not valid.
Cause: A flashback database log file header contained a usable blocks value
greater than the file size. The flashback database log file file is corrupt.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38741: Formatted blocks value string is not valid.
Cause: The formatted blocks value in the flashback database log file was greater
than the file size. The flashback database log file was corrupt.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38742: Flashback log file has incorrect log reset status.
Cause: The flashback database log file header had log reset data that was different
than the control file. The log was probably an incorrectly restored backup.
Flashback database logs cannot be backed up.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38743: Time/SCN is in the future of the database.
Cause: The Time/SCN provided in a FLASHBACK DATABASE command was in
the future of the database.
Action: Retry the command with a correct Time/SCN or RECOVER the database.
ORA-38744: file string is not the same file seen at start of flashback
Cause: A different copy of the file was accessed the last time FLASHBACK
DATABASE looked at the file header. A backup of the file was restored or the
meaning of the file name changed during FLASHBACK DATABASE.
Action: Ensure the correct file is available, then retry FLASHBACK DATABASE.
ORA-38746: error occurred while restoring data block (file# string, block# string)
Cause: An error occurred during a FLASHBACK DATABASE command. See
other errors on error stack.
Action: Investigate why the error occurred. It may be that the flashback database
log data is corrupt. If so, a restore and an incomplete recovery must be performed
instead.
ORA-38747: corrupt before image (file# string, block# string)
ORA-38029 to ORA-39965 21-25
Cause: A corrupt data block before image was encountered during a
FLASHBACK DATABASE command.
Action: The flashback log data is probably corrupt. If so, a restore and an
incomplete recovery must be performed instead.
ORA-38748: cannot flashback data file string - file is in use or recovery
Cause: An attempt to do FLASHBACK DATABASE found that the file was not
available for recovery. Either it was online and the database was open in some
instance, or another process was currently doing media recovery or flashback on
the file.
Action: Do not do FLASHBACK DATABASE.
ORA-38749: A media recovery has been started.
Cause: An attempt was made to start a FLASHBACK DATABASE in the same
session as a media recovery.
Action: Complete or cancel the first media recovery session.
ORA-38750: FLASHBACK DATABASE may not be performed using a dispatcher.
Cause: An attempt was made to use a dispatcher process for FLASHBACK
DATABASE. Memory requirements disallow this recovery method.
Action: Connect to the instance via a dedicated server process to perform
FLASHBACK DATABASE.
ORA-38751: Flashback database log: "string"
Cause: This message reports the filename for details of another message.
Action: Other messages will accompany this message. See the associated
messages for the appropriate action to take.
ORA-38752: file string does not exist
Cause: During an RMAN FLASHBACK DATABASE conversation, a file was
listed which was not part of the database. The RMAN conversation was aborted.
Action: Retry the conversation with the appropriate file numbers.
ORA-38753: Cannot flashback data file string; no flashback log data.
Cause: An attempt to perform a FLASHBACK DATABASE failed because the file
does not have enough flashback log data to cover the time to flash back. Either the
file did not have flashback generation enabled for it, or had flashback generation
turned off for it some time during the time span of the flashback.
Action: The file cannot be flashed back. The file must be taken offline or the
tablespace dropped before continuing with the FLASHBACK DATABASE
command.
ORA-38754: FLASHBACK DATABASE not started; required redo log is not
available
Cause: A FLASHBACK DATABASE command did not start. A redo log needed
for the recovery part of FLASHBACK DATABASE could not be found or accessed.
Action: See trace files for details of the problem.
ORA-38755: Flashback is already turned on for this tablespace.
Cause: An attempt was made to turn on flashback database logging for a
tablespace that already has flashback turned on.
Action: No action required.
21-26 Oracle Database Error Messages
ORA-38756: Flashback is already turned off for this tablespace.
Cause: An attempt was made to turn off flashback database logging for a
tablespace that already has flashback off.
Action: No action required.
ORA-38757: Database must be mounted and not open to FLASHBACK.
Cause: An attempt to Flashback a database was made when the database was not
mounted or was already open.
Action: Mount the database and retry the FLASHBACK command.
ORA-38758: cannot flashback data file string; restored since last recovery
Cause: An attempt to do FLASHBACK DATABASE found that the file was
restored since the last standby recovery. The file cannot be flashed back.
Action: The file must be taken offline before continuing with the FLASHBACK
DATABASE command.
ORA-38759: Database must be mounted by only one instance and not open.
Cause: An attempt to turn on or off Flashback Database logging was made when
the database was open or mounted by more than one instance.
Action: Mount the database in only one instance and retry the command.
ORA-38760: This database instance failed to turn on flashback database
Cause: Database flashback is on but this instance failed to start generating
flashback data. Look in alert log for more specific errors.
Action: Correct the error or turn off database flashback.
ORA-38761: redo log sequence string in thread string, incarnation string could not
be accessed
Cause: A redo log needed for the recovery portion of FLASHBACK could not be
read or opened. The FLASHBACK operation failed.
Action: Restore the log and retry the FLASHBACK command.
ORA-38762: redo logs needed for SCN string to SCN string
Cause: The FLASHBACK DATABASE operation failed. The recovery portion of
FLASHBACK DATABASE needed redo from the first SCN to the second, but one
or more of the redo logs in the range could not be read or opened.
Action: Check the FLASHBACK DATABASE command trace file for a description
of the inaccessible redo logs, restore access to them, and retry the FLASHBACK
DATABASE command.
ORA-38763: flashback not started; enabled threads have changed
Cause: A FLASHBACK DATABASE command did not start. The set of enabled
threads changed during the time to flash back.
Action: The flashback cannot be performed. Perform a restore and an incomplete
recovery instead.
ORA-38764: flashback not started; datafile string enabled threads are different
Cause: A FLASHBACK DATABASE command did not start. The datafile was
restored from a backup taken when the enabled threads were different than at the
time of the flashback.
Action: The flashback cannot be performed. Perform a restore and an incomplete
recovery instead.
ORA-38029 to ORA-39965 21-27
ORA-38765: Flashed back database cannot be opened read-only.
Cause: A complete recovery was performed after a database flashback but the
database was not opened for read-write access, or a FLASHBACK DATABASE
command failed.
Action: If a complete recovery was performed after a database flashback, open the
database for read-write access. If a FLASHBACK DATABASE command failed, fix
what caused the command to fail and retry the command, or recover and open the
database for read-write access.
ORA-38766: cannot flashback data file string; file resized smaller
Cause: An attempt to do FLASHBACK DATABASE found that the file was
shrunk during the time to flash back.
Action: The file cannot be flashed back. The file must be taken offline or the
tablespace dropped before continuing with the FLASHBACK DATABASE
command.
ORA-38767: flashback retention target parameter mismatch
Cause: The value of parameters DB_FLASHBACK_RETENTION_TARGET must
be same in all instances. All databases must have same flashback retention target
parameters.
Action: Check DB_FLASHBACK_RETENTION_TARGET values in all instances.
ORA-38768: resizing datafile string failed
Cause: An operating system error occurred when Flashback Database tried to
shrink (resize) a datafile. Flashback shrinks a file in order to undo the effects of a
file expand, for example, an autoextension of the file.
Action: Recover the database to return it to its previous state, or fix the cause of
the operating system error and retry the Flashback. If that is not possible, then the
file can be taken offline and the Flashback command retried. The file will have to
be restored from a backup and rolled forward.
ORA-38769: FLASHBACK DATABASE failed after modifying data.
Cause: A FLASHBACK DATABASE command failed after modifying the the
database. Look in the alert log for more information about the failure.
Action: Recover the database to return it to its previous state, or fix the cause of
the error and retry the Flashback.
ORA-38770: FLASHBACK DATABASE failed during recovery.
Cause: A FLASHBACK DATABASE command successfully restored the database
but failed during the recovery step. Look in the alert log for more information
about the failure.
Action: Fix the error and then recover the database to the same SCN or timestamp
used in the FLASHBACK DATABASE command.
ORA-38771: unnamed datafile(s) added to control file by flashback recovery
Cause: The recovery step of FLASHBACK DATABASE encountered the creation
of a datafile that could not be added to the control file. An entry has been added to
the control file for the new datafile, but with the file name UNNAMEDnnnn,
where nnnn is the file number. Related error messages provide the file names that
were originally used to create the files.
Action: Rename the file in the control file, or use the ALTER ALTER DATABASE
CREATE DATAFILE command to create a file suitable for recovery. If the file is not
going to be recovered, then take it offline with the FOR DROP option. The
21-28 Oracle Database Error Messages
recovery step of Flashback can be resumed by entering a RECOVERY command
with the same SCN or timestamp as used in the FLASHBACK DATABASE
command. For example, RECOVER AUTOMTAIC DATABASE UNTIL CHANGE
<flashback-scn>.
ORA-38772: cannot add datafile 'string' - file could not be created
Cause: The recovery step of FLASHBACK DATABASE encountered the creation
of a datafile and could not recreate the file. The error from the creation attempt is
displayed in another message. The control file file entry for the file is
'UNNAMEDnnnnn'.
Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the
file.
ORA-38773: cannot add data file 'string' - file already part of database
Cause: The recovery step of FLASHBACK database encountered the creation of a
datafile and could not create the file because the file name is already in use in the
database. The control file file entry for the file is 'UNNAMEDnnnnn'.
Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the
file with a different name.
ORA-38774: cannot disable media recovery - flashback database is enabled
Cause: An attempt was made to disable media recovery while flashback database
was enabled.
Action: Use the ALTER DATABASE FLASHBACK OFF statement to disable
flashback database, then disable media recovery.
ORA-38775: cannot disable recovery area - flashback database is enabled
Cause: An attempt was made to set DB_RECOVERY_FILE_DEST to null while
flashback database was enabled. Flashback database requires DB_RECOVERY_
FILE_DEST to be set.
Action: Use the ALTER DATABASE FLASHBACK OFF statement to disable
flashback database, then disable the recovery area.
ORA-38776: cannot begin flashback generation - recovery area is disabled
Cause: During a database mount, the RVWR process discovered that the recovery
area was disabled. DB_RECOVERY_FILE_DEST must have been set null or
removed from the INIT.ORA file while the database was unmounted.
Action: Flashback database requires the recovery area to be enabled. Either enable
the recovery area by setting the DB_RECOVERY_FILE_DEST and DB_
RECOVERY_FILE_DEST_SIZE initialization parameters, or turn off flashback
database with the ALTER DATABASE FLASHBACK OFF command.
ORA-38777: database must not be started in any other instance
Cause: A command was attempted that required the database to be mounted in
this instance and not started in any other instance. ALTER DATABASE OPEN
RESETLOGS requires that the database be started in only one instance if flashback
database logging is enabled.
Action: Ensure that the no other instances are started. Then retry the command.
ORA-38778: Restore point 'string' already exists.
Cause: The restore point name of the CREATE RESTORE POINT command
already exists. A restore point name must be unique.
ORA-38029 to ORA-39965 21-29
Action: Either use a different name or delete the existing restore point with the
same name.
ORA-38779: cannot create restore point - too many restore points.
Cause: The maximum number of restore points already have been created.
Action: Delete some existing restore point and retry the operation.
ORA-38780: Restore point 'string' does not exist.
Cause: The restore point name of the DROP RESTORE POINT command does not
exist.
Action: No action required.
ORA-38781: cannot disable media recovery - have guaranteed restore points
Cause: An attempt was made to disable media recovery while there is at least one
guaranteed restore point.
Action: Drop all guaranteed restore points and then disable media recovery.
ORA-38782: cannot flashback database to non-guaranteed restore point 'string'
Cause: An attempt was made to flashback database to a non-guaranteed restore
point while flashback database is off. You can only flashback a database to
guaranteed restore point when flashback database is not on.
Action: Consider picking a guaranteed restore point to flashback the database to,
if there is one.
ORA-38783: Instance recovery required.
Cause: An attempt was made to create a restore point when the database is in
mount mode but it was not shutdown cleanly before it was mounted. In order to
create a restore point when the database is mounted, the database must be
shutdown cleanly before it is mounted.
Action: Consider one of the following:
1. Create the restore point after opening the database.
2. Open the database, shut it down cleanly, mount the database, and retry creating
the restore point.
ORA-38784: Cannot create restore point 'string'.
Cause: An attempt to create a restore point failed. See other errors on the error
stack and in the alert log for the specific reason.
Action: Fix the problem and retry.
ORA-38785: Media recovery must be enabled for guaranteed restore point.
Cause: Media recovery is not enabled. Media recovery must be enabled in order
to create a guaranteed restore point.
Action: Turn on media recovery with an ALTER DATABASE ARCHIVELOG
statement and then retry the command.
ORA-38786: Recovery area is not enabled.
Cause: An attempt was made to perform a command that requires Flash recovery
area to be enabled.
Action: Set DB_RECOVERY_FILE_DEST to an appropriate location and retry.
ORA-38787: Creating the first guaranteed restore point requires mount mode when
flashback database is off.
21-30 Oracle Database Error Messages
Cause: While flashback database is not on, an attempt was made to create the first
guaranteed restore point while the database is open.
Action: Mount the database and retry.
ORA-38788: More standby database recovery is needed
Cause: An attempt was made to create a restore point or a guaranteed while a
physical standby database is not cleanly checkpointed.
Action: Perform more standby database recovery via managed standby database
recovery. Cancel managed recovery and retry the command.
ORA-38789: File name is too long.
Cause: The file name provided in the command was longer than the maximum
allowed.
Action: Use a shorter file name.
ORA-38790: BEFORE must be specified with RESETLOGS
Cause: The FLASHBACK DATABASE command included the RESETLOGS
parameter but not the BEFORE parameter.
Action: Retry the command with TO BEFORE RESETLOGS.
ORA-38791: flashback did not start because file string was not in a valid
incarnation
Cause: Flashback could not be started because a file was checkpointed or fuzzy at
a point where the file can neither be restored nor recovered to our restore target. In
order for a file to be brought to the restore target, the file has to be in one of the
incarnations along the ancestral path from the current incarnation to the restore
incarnation.
Action: Manually restore or recover the file to a point where it is in one of the
incarnations along the ancestral path from the current incarnation to the restore
incarnation.
ORA-38792: encountered unknown flashback record from release string
Cause: A Flashback Database logfile contains a record written by a future Oracle
release and is unknown by this release.
Action: The given release of Oracle must be installed in order to use these
flashback database log files.
ORA-38793: cannot FLASHBACK the database or pluggable database to a future
SCN or time
Cause: The Flashback Pluggable Database target SCN or timestamp is greater
than the current database or pluggable database SCN/timestamp and the database
or pluggable database incarnation is not the last opened incarnation.
Action: If the target SCN or timestamp is in the current incarnation or a child
incarnation whose branch point is after the current database or pluggable database
SCN then RECOVER DATABASE or RECOVER PLUGGABLE DATABASE to the
target SCN or time. If the target SCN or timestamp is in a child incarnation whose
branch point is prior to the current database or pluggable database SCN then
FLASHBACK DATABASE to before the branch point. Next, use RMAN to reset the
database or pluggable database to the child incarnation. Finally, RECOVER
DATABASE OR PLUGGABLE DATABASE to the target SCN time.
ORA-38794: Flashback target time not in current incarnation
ORA-38029 to ORA-39965 21-31
Cause: The Flashback Database target timestamp is not in the database's current
incarnation or any of its ancestors.
Action: Use a different target timestamp or use RMAN to reset the database to the
appropriate incarnation.
ORA-38795: WARNING: FLASHBACK DATABASE succeeded but OPEN
RESETLOGS would fail
Cause: FLASHBACK DATABASE succeeded. However, if ALTER DATABASE
OPEN RESETLOGS command was attempted now, it would fail with the specified
error.
Action: Fix the error before trying ALTER DATABASE OPEN RESETLOGS.
ORA-38796: Not enough flashback database log data to undo FLASHBACK.
Cause: There was not enough flashback log data to undo the flashback so a
flashback was not started.
Action: It is still possible to get to the restore target by doing a flashback until the
resetlogs branch point of the restore target is reached. This can be done by
executing multiple "flashback to before resetlogs" commands, or by doing a
flashback to the exact time or SCN of the desired resetlogs branch point. Note that
this flashback cannot be undone should an error occur. The only option is to
complete the flashback.
ORA-38797: Full database recovery required after a database has been flashed back
Cause: An attempt was made to recover some datafiles or tablespaces of a
database after the database had been flashed back. In order to recover control file
and all datafiles correctly, full database recovery is required after a database has
been flashed back.
Action: Recover the whole database instead.
ORA-38798: Cannot perform partial database recovery
Cause: See other other messages on error stack for the cause.
Action: See other other messages on error stack for the action.
ORA-38799: Cannot drop guaranteed restore point internally created for snapshot
standby
Cause: An attempt is made to drop the guaranteed restore point Oracle created
internally for a snapshot standby.
Action: Use the "alter database convert to physical standby" command to convert
the snapshot standby to a normal physical standby. This will automatically
flashback the database and drop this guaranteed restore point.
ORA-38800: Cannot start Redo Apply on the open physical standby database
Cause: An attempt was made to start Redo Apply on an open physical standby
database instance.
Action: Make sure the primary database is at compatibility 11.0.0 or higher. The
redo logs to be recovered on an open physical standby database must be generated
at compatibility 11.0.0 or higher. If you have any redo below 11.0.0 to be applied
on the standby, you must apply them on a mounted standby before restarting
recovery on an open standby when the log format advances to 11.0.0 or higher. If
this is a RAC standby database, make sure the ACTIVE_INSTANCE_COUNT
parameter is not set.
ORA-38801: improper value for ORA_EDITION
21-32 Oracle Database Error Messages
Cause: An improper value was used for ORA_EDITION when trying to specify
an edition to use at login time. The value is not understandable as an identifier, or
is too long.
Action: Correct the value for ORA_EDITION and try again.
ORA-38802: edition does not exist
Cause: This error occurred because a reference was made to an edition that does
not exist or that the current user does not have privileges on.
Action: Check the edition name and verify that the current user has appropriate
privileges on the edition.
ORA-38803: edition is unusable
Cause: This error occurred because a reference was made to an unusable edition.
Action: Use another edition.
ORA-38804: not a legal edition name
Cause: This error occurred because an attempt was made to create an edition
called ORA$BASE, DATABASE_DEFAULT, or USER_DEFAULT. These are not
legal edition names. Or a value provided as an edition name is not understandable
as an identifier, or is too long.
Action: Choose a different name for the edition.
ORA-38805: edition is in use
Cause: An attempt was made to ALTER or DROP an edition that was being used
in another session or was the database default edition.
Action: Retry when the edition is not in use and is not the database default
edition.
ORA-38806: edition is being altered or dropped
Cause: An attempt was made to use an edition that was in the process of being
altered or dropped.
Action: Use a different edition.
ORA-38807: Implementation restriction: an edition can have only one child
Cause: This error occurred because an attempt was made to create more than one
child edition for a parent edition.
Action: Create the edition as a child of the leaf edition.
ORA-38808: edition has a usable parent and a usable child
Cause: An attempt was made to make an edition with a usable parent and a
usable child edition unusable.
Action: An edition with a usable parent and a usable child edition cannot be
made unusable. Retry after either parent or child has been made unusable.
ORA-38809: edition must be unusable
Cause: This error occurred because an attempt was made to drop a usable edition.
Action: Retry after the altering the edition to be unusable.
ORA-38810: Implementation restriction: cannot drop edition that has a parent and a
child
Cause: This error occurred because an attempt was made to drop an edition that
has a parent and a child edition.
ORA-38029 to ORA-39965 21-33
Action: Retry after dropping the parent or child edition.
ORA-38811: need CASCADE option to drop edition that has actual objects
Cause: This error occurred because an attempt was made to drop an edition that
has actual objects.
Action: Specify CASCADE option in drop command.
ORA-38812: maximum number of editions reached
Cause: The number of editions has reached the limit.
Action: Drop some editions before creating new ones.
ORA-38813: editions not supported for schema string
Cause: The Oracle-supplied schema did not support editions.
Action: Do not attempt to enable editions for the specified Oracle-supplied
schema.
ORA-38814: ALTER SESSION SET EDITION must be first statement of transaction
Cause: An attempt was made to execute an edition switch within an open
transaction.
Action: Commit or rollback the transaction and reexecute the statement, or use
DBMS_SESSION.SET_EDITION_DEFERRED if its deferred effect is appropriate.
ORA-38815: ALTER SESSION SET EDITION must be a top-level SQL statement
Cause: An edition switch failed because it was executed from a PL/SQL block or
using recursive SQL.
Action: Execute the statement from a top-level OCI call, or use dbms_session.set_
edition if its deferred effect is appropriate.
ORA-38816: edition has a child that inherits objects from the edition
Cause: This error occurred because an attempt was made to drop an edition that a
child that inherits objects from the edition.
Action: Retry after the child edition has no inherited objects.
ORA-38817: Insufficient privileges
Cause: You did not have sufficient privileges to execute the subprogram package
DBMS_EDITIONS_UTIL.
Action: Obtain the necessary privileges. Please see the package specification for
details.
ORA-38818: illegal reference to editioned object string.string
Cause: An attempt was made to violate the rule "A noneditioned object may not
depend on an editioned object."
Action: Either make this object editioned; or do not make the illegal reference.
ORA-38819: user string owns one or more objects whose type is editionable and
that have noneditioned dependent objects
Cause: An attempt was made to violate the rule "A noneditioned object may not
depend on an editioned object."
Action: Either make sure that those objects owned by this user whose type is
editionable have no noneditioned dependent objects; or use the FORCE option.
ORA-38820: user has evolved object type
21-34 Oracle Database Error Messages
Cause: User could not be edition enabled if it has evolved object type.
Action: Reset the evolved object type first.
ORA-38821: unsupported DBMS_SQL Edition operation
Cause: Could not bind or define ADT, VARRAY, nested table or REF data type
when the specified Edition is different from the current edition.
Action: Use the current Edition.
ORA-38822: referential integrity constraints not allowed on editioned views
Cause: An attempt was made to create a referential integrity constraint to or from
an editioned view or enable editions for a user that has views with referential
integrity constraints.
Action: Do not attempt to create editioned views with referential integrity
constraints.
ORA-38823: Crossedition triggers are not allowed to exist when dropping the root
edition
Cause: An attempt was made to drop the root edition when enabled crossedition
trigger exists.
Action: Drop or disable all the crossedition triggers before dropping the root
edition.
ORA-38824: A CREATE OR REPLACE command may not change the
EDITIONABLE property of an existing object.
Cause: An attempt was made to replace an existing object with a different value
for the EDITIONABLE property.
Action: Switch the EDITIONABLE property in the REPLACE statement, or alter
the existing object to have an EDITIONABLE property matching the
EDITIONABLE property in the REPLACE statement.
ORA-38825: The EDITIONABLE property of an editioned object cannot be altered.
Cause: An attempt was made to alter the EDITIONABLE property of an object
whose type has been enabled for editioning in the owner's schema.
Action: Drop the object and re-create it with the desired EDITIONABLE state.
ORA-38826: The EDITIONABLE property of a TYPE or PACKAGE specification
and its body must match.
Cause: An attempt was made to create a TYPE or PACKAGE specification or body
whose EDITIONABLE property did not match its counterpart.
Action: Switch the EDITIONABLE property in the CREATE statement, or alter the
existing object to have an EDITIONABLE property matching the EDITIONABLE
property in the CREATE statement.
ORA-38850: an enabled thread missing from control file
Cause: A CREATE CONTROLFILE statement was given that did not list all the
enabled threads for the database.
Action: Reissue the CREATE CONTROLFILE statement, including all enabled
threads.
ORA-38851: cannot mark the current instance (redo thread) as disabled
Cause: The standby switchover or failover operation failed because it needs to
mark the current instance (redo thread) as disabled.
ORA-38029 to ORA-39965 21-35
Action: Shut down this instance and start up using a different instance name or
redo thread number and retry.
ORA-38852: cannot mark the current instance (redo thread) as disabled
Cause: The open resetlogs or standby activation operation failed because it must
use a different instance (redo thread) than the current instance (redo thread) to
open the database.
Action: Shut down this instance and start up using a different instance name or
redo thread number and retry.
ORA-38853: cannot mark instance string (redo thread string) as disabled
Cause: The standby switchover or failover operation failed because it needs to
mark an instance (redo thread) as disabled. That instance was up, which
prevented it from being disabled.
Action: Shut down the specified instance and retry this command.
ORA-38854: cannot mark instance string (redo thread string) as disabled
Cause: The open resetlogs or standby activation operation failed because it needs
to mark an instance (redo thread) as disabled. That instance was up, which
prevented it from being disabled.
Action: Shut down the specified instance and retry this command.
ORA-38855: cannot mark instance string (redo thread string) as enabled
Cause: The standby switchover or failover operation failed because it needs to
mark an instance (redo thread) as enabled. However, it had less than 2 online redo
logs, which prevented it from being enabled.
Action: Add more logfiles to the specified instance and retry the command.
ORA-38856: cannot mark instance string (redo thread string) as enabled
Cause: The open resetlogs or standby activation operation failed because it needs
to mark an instance (redo thread) as enabled. However, it had less than 2 online
redo logs, which prevented it from being enabled.
Action: Add more logfiles to the specified instance and retry the command.
ORA-38857: cannot mark redo thread string as enabled
Cause: The standby switchover or failover operation failed because it needs to
mark a redo thread as enabled. However, the control file was recreated with a
MAXINSTANCES value smaller than the thread number of the redo thread.
Action: Recreate the control file with a larger MAXINSTANCES value.
ORA-38858: cannot mark redo thread string as enabled
Cause: The open resetlogs or standby activation operation failed because it needs
to mark a redo thread as enabled. However, the control file was recreated with a
MAXINSTANCES value smaller than the thread number of the redo thread.
Action: Recreate the control file with a larger MAXINSTANCES value.
ORA-38859: instance string (thread string) is not ready to be disabled
Cause: The command attempted to switch the instance (thread) into a new log
before disabling it. The switch attempt failed because all eligible online logs were
either being cleared or not completely archived yet.
Action: Wait a few minutes and retry.
21-36 Oracle Database Error Messages
ORA-38860: cannot FLASHBACK DATABASE during instantiation of a logical
standby
Cause: The command was not permitted because the controlfile indicates the
database was in the process of becoming a logical standby database but the
controlfile conversion had not completed.
Action: If in the process of creating a logical standby database, perform the
remaining instantiation procedures to completion. If this flashback operation
followed a Data Guard failure, permit the errant Data Guard operation to
successfully complete. Once the instantiation is complete, reissue the flashback
operation.
ORA-38861: flashback recovery stopped before reaching recovery target
Cause: Flashback recovery on the standby ended early because the user
attempted to flashback to an SCN or time for which there were no redo logs. Most
likely, the user is trying to flashback to a future time in the database that the
database has never recovered through. Check the alert log to find out which SCN
the database recovered to.
Action: Flashback to an older SCN or acquire the necessary redo logs.
ORA-38862: Flashback database logs are in use.
Cause: The command could not be performed because the flashback database logs
were locked by another operation, such as FLASHBACK DATABASE or a query of
V$FLASHBACK_DATABASE_LOG.
Action: Wait for the other operation to complete.
ORA-38863: datafile string has been restored from an optimized RMAN backup.
Cause: Flashback Database could not flash back the file because it was restored
from an RMAN optimized backup with deallocated objects. Flashback cannot
revert the file to a time before the last deallocation in the datafile backup.
Action: Restore the file from a backup prior to the Flashback target SCN or time
and then retry the command.
ORA-38864: cannot create a guaranteed restore point with user specified SCN or
time.
Cause: An SCN or timestamp was specified when creating a guaranteed restore
point. This is not supported. You can only create a guaranteed restore point as of
the current time.
Action: Avoid this combination of options for creating a restore point.
ORA-38865: cannot create restore point for a future SCN or time.
Cause: An attempt was made to create a restore point with an SCN or timestamp
that is in the future.
Action: Revise the SCN or timestamp specified so that it is an SCN or timestamp
in the past.
ORA-38866: cannot create restore point for an SCN or time before current database
incarnation.
Cause: An attempt was made to create a restore point with an SCN or timestamp
that is before the beginning of the current database incarnation.
Action: Revise the SCN or timestamp specified so that it is within current
database incarnation.
ORA-38029 to ORA-39965 21-37
ORA-38867: database not open: cannot create restore point with the specified
timestamp
Cause: An attempt was made to create a restore point with the specified
timestamp while the database was not open. The database must be open in order
to map the timestamp to an SCN.
Action: Open the database first or pick another way to create the restore point.
ORA-38868: warning: the control file may have incorrect data file structure
Cause: This control file was created or converted based on a control file from a
time different from the time of the database.
Action: Open database and all pluggable databases read-only to synchronize the
control file with the database dictionary. You can also force recovery to proceed by
invoking recovery again.
ORA-38869: datafile string has been restored from an RMAN backup with undo
block compression.
Cause: Flashback Database could not flash back the database because a file was
restored from an RMAN backup with undo block compression, and the Flashback
target was to a time when the missing undo may be needed to open the database.
Action: Restore an earlier backup of the file and retry the command or Flashback
to a later time.
ORA-38870: cannot backup a control file that may have incorrect data file structure.
Cause: This control file was created or converted based on a control file from a
time different from the time of the database.
Action: Open database read-only to synchronize the control file with the database
dictionary to fix the control file.
ORA-38871: cannot enable flashback before open resetlogs after incomplete
recovery.
Cause: To enable flashback on a primary database, the database must be clean
without requiring open resetlogs.
Action: Open resetlogs first and then enable flashback database.
ORA-38872: Cannot perform backup control file recovery if Flashback Database is
enabled.
Cause: RECOVER DATABASE with the BACKUP CONTROLFILE option, or a
database recovery that required the control file be made a backup failed because
Flashback Database was enabled or there was a guaranteed restore point.
Action: Disable Flashback Database or remove the guaranteed restore point and
retry the command.
ORA-38873: missing incarnation information
Cause: Flashback Database failed because incarnation information was not found
in the control file. The Flashback target incarnation was not in the control file or
had a missing parent incarnation.
Action: Register logs from the missing incarnations and retry the command.
ORA-38874: cannot flashback data file string - missing incarnation information
Cause: Flashback Database failed because incarnation information for the start of
the offline range for a file was not found in the control file. Flashback could not
update the file's header with the missing incarnation's resetlogs information.
21-38 Oracle Database Error Messages
Action: Check the trace log for the offline range of the data file. If redo logs from
the missing incarnation can be found, register the logs in the control file and retry
the command.
ORA-38875: FLASHBACK DATABASE not started; in test mode
Cause: The FLASHBACK DATABASE command was not performed because it
was started in test mode.
Action: No action required.
ORA-38876: redo logs not required
Cause: The FLASHBACK DATABASE command was performed in test mode and
determined that no redo logs were required to perform the tested FLASHBACK
DATABASE command.
Action: No action required.
ORA-38877: required redo logs are available
Cause: The FLASHBACK DATABASE command was performed in test mode and
determined that no redo logs required to perform the tested FLASHBACK
DATABASE command were missing.
Action: No action required.
ORA-38878: required redo log is not available
Cause: A redo log needed for the recovery part of FLASHBACK DATABASE
could not be found or accessed.
Action: See trace files for details of the problem.
ORA-38879: Cannot flashback data file string; may not be able to undo all changes.
Cause: A data file was plugged in when there was a guaranteed restore point, but
Flashback Database was not enabled. It is possible that some changes to the data
file, after it was converted, were not logged to the Flashback Database logs.
Action: If the FLASHBACK DATABASE command was meant to rewind the
database to a time before the file was plugged in, take the data file offline and retry
the command. If the FLASHBACK DATABASE command was meant to rewind
the database to a time after the file was plugged in, restore the original version of
the plugged in file and retry the command.
ORA-38880: Cannot advance compatibility from string to string due to guaranteed
restore points
Cause: Flashback database cannot undo the advance of database compatibility.
Therefore, one cannot advance the compatibility of the database while there are
guaranteed restore points in the database.
Action: Drop all guaranteed restore points first and retry, or delay the advance of
database compatibility to a later time.
ORA-38881: Cannot drop tablespace string on primary database due to guaranteed
restore points.
Cause: An attempt was made to drop a tablespace on a primary database while
there are guaranteed restore points. You cannot do this because Flashback
database cannot undo dropping of a tablespace.
Action: Drop all guaranteed restore points first and retry, or delay dropping the
tablespace until all guaranteed restore points are removed.
ORA-38029 to ORA-39965 21-39
ORA-38882: Cannot drop tablespace string on standby database due to guaranteed
restore points.
Cause: An attempt was made to drop a tablespace on a standby database while
there are guaranteed restore points. You cannot do this because Flashback
database cannot undo dropping of a tablespace.
Action: Drop all guaranteed restore points and rerun recovery on standby
database.
ORA-38883: Cannot shrink data file string on primary database due to guaranteed
restore points.
Cause: An attempt was made to shrink a data file on a primary database while
there are guaranteed restore points. You cannot do this because Flashback
database cannot undo the shrinking of a data file.
Action: Drop all guaranteed restore points first and retry, or delay the data file
resize until all guaranteed restore points are removed.
ORA-38884: Cannot shrink data file string on standby database due to guaranteed
restore points.
Cause: An attempt was made to shrink a data file on a standby database while
there are guaranteed restore points. You cannot do this because Flashback
database cannot undo the shrinking of a data file.
Action: Drop all guaranteed restore points and rerun recovery on standby
database.
ORA-38885: WARNING: Flashback database has been disabled while fast-start
failover is enabled.
Cause: Flashback database was disabled while fast-start failover was enabled.
Action: Enable flashback database if fast-start failover is enabled.
ORA-38886: WARNING: Flashback database was disabled due to error when
writing flashback database logs.
Cause: Recovery writer (RVWR) encountered an error when writing flashback
database logs.
Action: See the error stack in the alert log.
ORA-38887: WARNING: Recovery writer (RVWR) hang due to error when writing
flashback database logs.
Cause: An error occurred while writing to the flashback database logs.
Action: Shutdown the instance or turn off flashback database.
ORA-38888: invalid redo thread number
Cause: The provided thread number was invalid.
Action: Specify a valid redo thread number.
ORA-38900: missing mandatory column "string" of error log table "string"
Cause: Mandatory column of error logging table is not present
Action: Add the named column to the error logging table. Consult ORACLE
documentation for the correct data type.
ORA-38901: column "string" of table "string" must be one of the first "string"
columns
21-40 Oracle Database Error Messages
Cause: Mandatory information column of error logging table is present, but must
be at the beginning of the row.
Action: Create the error logging table correctly. Consult ORACLE documentation
for the correct format of an error logging table.
ORA-38902: errors in array DML exceed string
Cause: The operation failed because the array DML had more errors than can be
stored internally for BATCH ERRORs.
Action: Do not use BATCH ERROR mode when array DML has more error rows
than the number specified in the error.
ORA-38903: DML error logging is not supported for abstract column "string"
Cause: A DML Error Logging operation was attempted on a table which has an
ADT, REF, VARRAY, or nested table column type, and the error logging table
referred to the specified column.
Action: Either do not use DML Error Logging on such a table or remove the
offending column from the error logging table. The scalar columns can be logged,
but not abstract column types.
ORA-38904: DML error logging is not supported for LOB column "string"
Cause: A DML Error Logging operation was attempted on a table which has a
CLOB, NCLOB, or BLOB column type, and the error logging table referred to the
specified column.
Action: Either do not use DML Error Logging on such table or remove the
offending column from the error logging table. The scalar columns can be logged,
but not LOB column types.
ORA-38905: DML error logging is not supported for LONG column "string"
Cause: A DML Error Logging operation was attempted on a table which has a
LONG, or LONG RAW column type, and the error logging table referred to the
specified column.
Action: Either do not use DML Error Logging on such a table or remove the
offending column from the error logging table. The scalar columns can be logged,
but not long column types.
ORA-38906: insert into DML Error Logging table "string" failed
Cause: An error occurred when attempting to log a DML Error on behalf of the
DML Error logging clause. This may be intended if a trigger is defined on the error
table (which in turn errors out in certain cases).
Action: Determine root cause of error (in error stack).
ORA-38907: DML error logging is not supported for FILE column "string"
Cause: A DML Error Logging operation was attempted on a table which has a
BFILE column and the Error Logging table referred to the specified column.
Action: Either don't use DML Error Logging on such table or remove the
offending column from the error logging table. The scalar columns can be logged,
but not BFILE column types.
ORA-38908: internal error occurred during DML Error Logging
Cause: An unexpected error occurred while executing recursive SQL to insert a
row into the DML Error Logging table.
Action: Report this error to Oracle Support.
ORA-38029 to ORA-39965 21-41
ORA-38909: DML Error logging is not supported with BATCH ERROR mode
Cause: A DML Error Logging operation was attempted on a table which has
BATCH ERROR mode also specified.
Action: Refrain from using both DML Error Logging and BATCH ERROR mode
on the same table.
ORA-38910: BATCH ERROR mode is not supported for this operation
Cause: BATCH ERROR mode specified for this operation.
Action: Refrain from using BATCH ERROR mode with this operation.
ORA-38911: unique constraint (string.string) violated
Cause: An INSERT statement with a CHANGE_DUPKEY_ERROR_INDEX hint
tried to insert a duplicate key into a table.
Action: Either remove the unique restriction or do not insert the key.
ORA-38912: An index must be specified in the index hint
Cause: Index specification was missing in an IGNORE_ROW_ON_DUPKEY_
INDEX or CHANGE_DUPKEY_ERROR_INDEX hint.
Action: In the hint, specify a unique index that exists on the table.
ORA-38913: Index specified in the index hint is invalid
Cause: The index specified in an IGNORE_ROW_ON_DUPKEY_INDEX or
CHANGE_DUPKEY_ERROR_INDEX hint could not be found.
Action: Specify a unique index that exists on the table. The index cannot be a
non-unique index or a bitmap index.
ORA-38914: Either mutate the error or ignore row on unique violation
Cause: IGNORE_ROW_ON_DUPKEY_INDEX and CHANGE_DUPKEY_
ERROR_INDEX were both specified in the same statement.
Action: You cannot specify both hints in the same statement. Remove one of these
two hints, or both, from the statement.
ORA-38915: Multiple indexes in change or ignore duplicate key hint
Cause: Multiple indexes were specified in an IGNORE_ROW_ON_DUPKEY_
INDEX or CHANGE_DUPKEY_ERROR_INDEX hint.
Action: Only one index must be specified in the hint.
ORA-38916: CHANGE_DUPKEY_ERROR_INDEX hint disallowed for this
operation
Cause: CHANGE_DUPKEY_ERROR_INDEX hint was specified for the operation.
Action: You cannot specify this hint for this operation. Remove the hint from the
statement.
ORA-38917: IGNORE_ROW_ON_DUPKEY_INDEX hint disallowed for this
operation
Cause: IGNORE_ROW_ON_DUPKEY_INDEX hint was specified for the
operation.
Action: You cannot specify this hint for this operation. Remove the hint from the
statement.
ORA-38918: RETRY_ON_ROW_CHANGE hint disallowed for this operation
Cause: RETRY_ON_ROW_CHANGE hint was specified for the operation.
21-42 Oracle Database Error Messages
Action: You cannot specify this hint for this operation. Remove the hint from the
statement.
ORA-38919: remote table not supported for DML error logging
Cause: A remote table was specified in the DML error logging clause.
Action: You cannot specify a remote table to which errors will be logged. Specify a
local table only.
ORA-38950: Source platform string not cross platform compliant
Cause: Cross platform transport was not allowed for this platform.
Action: For a list of supported platforms, query fixed view
SYS.V$TRANSPORTABLE_PLATFORM.
ORA-38951: Target platform string not cross platform compliant
Cause: Cross platform transport was not allowed for this platform.
Action: None
ORA-38952: Source database not 10.0.0.0 compatible
Cause: Cross platform transport is not supported unless database compatibility is
advanced to 10.0.0.0 or higher
Action: Use the compatible parameter to advance source database compatibility
and redo the transport
ORA-38954: Cross platform transport is not supported between source platform
identifier string and target platform identifier string
Cause: The platform identifier in the transported file indicated that the datafile
format was different than the target database datafile format.
Action: For a list of supported platforms, query fixed view
SYS.V$TRANSPORTABLE_PLATFORM. If both platforms are present, Contact
Oracle support
ORA-38955: Source platform string not cross platform compliant
Cause: The platform identifier in the transported file indicated that this platform
is not supported for a cross platform transport.
Action: For a list of supported platforms, query fixed view
SYS.V$TRANSPORTABLE_PLATFORM.
ORA-38956: Target platform string not cross platform compliant
Cause: Cross platform transport was not allowed for this platform.
Action: For a list of supported platforms, query fixed view
SYS.V$TRANSPORTABLE_PLATFORM.
ORA-38958: Source platform string is in different byte order than target platform
string
Cause: Probably a conversion was not done before the import phase of the
transport.
Action: Use RMAN CONVERT functionality to convert endian ordering.
ORA-38959: Failed to update block 0 to new version 10 format
Cause: An attempt was made to update block 0 to version 10 format.
Action: check additional error messages and contact Oracle Support Services.
ORA-38029 to ORA-39965 21-43
ORA-38960: File string from platform string is not compatible with current platform
string
Cause: The file was directly copied to this platform from a platform with a
different endian ordering.
Action: Use RMAN CONVERT functionality to convert endian ordering.
ORA-38961: data file: string
Cause: Reporting file name for details of another error.
Action: See associated error message.
ORA-39000: bad dump file specification
Cause: The user specified a dump file that could not be used in the current job.
Subsequent error messages describe the inadequacies of the dump file.
Action: Specify a dump file that is usable for the job.
ORA-39001: invalid argument value
Cause: The user specified API parameters were of the wrong type or value range.
Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further
describe the error.
Action: Correct the bad argument and retry the API.
ORA-39002: invalid operation
Cause: The current API cannot be executed because of inconsistencies between
the API and the current definition of the job. Subsequent messages supplied by
DBMS_DATAPUMP.GET_STATUS will further describe the error.
Action: Modify the API call to be consistent with the current job or redefine the
job in a manner that will support the specified API.
ORA-39003: unable to get count of total workers alive
Cause: Attempt to get count of total worker processes alive failed.
Action: Check the additional error messages to see what caused the failure.
Correct the error, if possible, and try the operation again. If this error occurs from a
Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs
again, contact Oracle Customer Support and report the error.
ORA-39004: invalid state
Cause: The state of the job precludes the execution of the API.
Action: Rerun the job to specify the API when the job is an appropriate state.
ORA-39005: inconsistent arguments
Cause: The current API cannot be executed because of inconsistencies between
arguments of the API call. Subsequent messages supplied by DBMS_
DATAPUMP.GET_STATUS will further describe the error.
Action: Modify the API call to be consistent with itself.
ORA-39006: internal error
Cause: An unexpected error occurred while processing a Data Pump job.
Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further
describe the error.
Action: Contact Oracle Customer Support.
ORA-39012: Client detached before the job started.
21-44 Oracle Database Error Messages
Cause: The client detached or ended their session before the Data Pump job was
started.
Action: Create new job and remain attached to the job until it is started.
ORA-39013: Remapping the SYSTEM schema is not supported.
Cause: A remap_schema transform with the SYSTEM schema was specified.
Action: Retry the import command without remapping the SYSTEM schema.
ORA-39014: One or more workers have prematurely exited.
Cause: One or more of the worker processes exited before the job was completed.
With no workers, the master process will terminate the job.
Action: Rerun the job. If problem persists, contact Oracle Customer Support.
ORA-39015: job is not running
Cause: An API was executed that required the job to be running, but the job was
not active.
Action: Retry the API. If problem persists, contact Oracle Customer Support.
ORA-39016: Operation not supported when job is in string state.
Cause: The state of the job precludes the execution of the API.
Action: Rerun the job to specify the API when the job is an appropriate state.
ORA-39017: Worker request not supported when job is in string state.
Cause: The state of the job precludes the execution of a worker request. This is an
internal error.
Action: Contact Oracle Customer Support.
ORA-39018: master process received invalid message number string
Cause: Internal Error
Action: Contact Oracle Customer Support.
ORA-39019: invalid operation type string
Cause: User specified an invalid operation name on an DBMS_
DATAPUMP.OPEN API or an invalid operation name was specified in the master
table for a restart API.
Action: Correct the operation name and recreate the job.
ORA-39020: invalid mode type string
Cause: User specified an invalid mode on an DBMS_DATAPUMP.OPEN API or
an invalid mode was specified in the master table for a restart API.
Action: Correct the mode and recreate the job.
ORA-39021: Database compatibility version string is not supported.
Cause: User selected COMPATIBLE as the version on an DBMS_
DATAPUMP.OPEN API, but the current database compatibility version is not
supported by the Data Pump API. Database versions before 9.2 are not supported
by the Data Pump.
Action: Specify a supported version and recreate the job.
ORA-39022: Database version string is not supported.
ORA-38029 to ORA-39965 21-45
Cause: User selected LATEST as the version on an DBMS_DATAPUMP.OPEN
API, but the current database version is not supported by the Data Pump API.
Database versions before 9.2 are not supported by the Data Pump.
Action: Specify a supported version and recreate the job.
ORA-39023: Version string is not supported.
Cause: User specified an explicit version on an DBMS_DATAPUMP.OPEN API,
but the current database version is not supported by the Data Pump API. Database
versions before 9.2 are not supported by the Data Pump.
Action: Specify a supported version and recreate the job.
ORA-39024: wrong schema specified for job
Cause: Internal error caused by the master process finding inconsistencies
between the schemas specified for the job.
Action: Contact Oracle Customer Support.
ORA-39025: jobs of type string are not restartable
Cause: Attempt to restart a job which was not restartable.
Action: Recreate the job via the open API.
ORA-39026: master table is inconsistent on validation string
Cause: Job cannot be restarted because it failed a validation check. Validation
checks are of the form -xx.y where -xx is the value of the PROCESS_ORDER
column in the master table where the error was detected and y is the actual
validity check for the row.
Action: Recreate the job. If master table has not been modified, but problem
persists, contact Oracle Customer Support.
ORA-39027: wrong version of master table
Cause: Job cannot be restarted because the version of the database upon which
the job started is different than the current version of the database and the format
of the master table has changed between the versions.
Action: Recreate the job.
ORA-39028: cannot restart job from string state
Cause: The job was not in a suitable state for restart. Jobs must begin executing
before they can be restarted.
Action: Recreate the job.
ORA-39029: worker string with process name "string" prematurely terminated
Cause: The specified worker process terminated unexpectedly. Subsequent
messages describe the reason for the termination.
Action: In many cases, the Data Pump will attempt to automatically restart the
worker. If problem persists, contact Oracle Customer Support.
ORA-39030: invalid file type string
Cause: An invalid filetype was specified for an DBMS_DATAPUMP.ADD_FILE
API call.
Action: Correct the filetype parameter and reissue the API request.
ORA-39031: invalid filter name string
21-46 Oracle Database Error Messages
Cause: An invalid filter name was specified on a DBMS_DATAPUMP.DATA_
FILTER API call.
Action: Correct the filter name parameter and reissue the API request.
ORA-39032: Parameter string is not supported in string jobs.
Cause: The specified parameter was not supported for the specified class of jobs.
Action: Re-create the job with the appropriate mode or operation type.
ORA-39033: Data cannot be filtered under the direct path access method.
Cause: The user specified that the data access method for the job was direct which
precludes the use of certain data filters.
Action: Use the SUBQUERY or the SAMPLE data filter with the automatic data
access method.
ORA-39034: Table string does not exist.
Cause: The user referenced a table in an API that did not exist.
Action: Correct table name and retry API.
ORA-39035: Data filter string has already been specified.
Cause: The user has already specified a data filter that matches on the filter name,
schema name, and table.
Action: Specify a different data filter.
ORA-39036: invalid metadata filter name string
Cause: An invalid metadata filter name was specified on a DBMS_
DATAPUMP.METADATA_FILTER API call.
Action: Correct the metadata filter name parameter and reissue the API request.
ORA-39037: Object type path not supported for string metadata filter.
Cause: An object type path was specified for the filter, but the filter does not
support the object type path parameter.
Action: Remove the object type path parameter.
ORA-39038: Object path "string" is not supported for string jobs.
Cause: The specified object type path is invalid for the job mode.
Action: Correct the object type path.
ORA-39039: Schema expression "string" contains no valid schemas.
Cause: The specified SCHEMA_EXPR filter resulted in no schemas being selected.
Action: Correct the the SCHEMA_EXPR filter specification.
ORA-39040: Schema expression "string" must identify exactly one schema.
Cause: For TABLE mode jobs, the SCHEMA_EXPR filter must identify exactly one
schema.
Action: Correct the the SCHEMA_EXPR filter specification.
ORA-39041: Filter "string" either identifies all object types or no object types.
Cause: A Metadata filter specifying path names either returned all objects or no
objects in the job.
Action: Correct the the metadata filter specification.
ORA-39042: invalid transform name string
ORA-38029 to ORA-39965 21-47
Cause: An invalid transform name was specified on a DBMS_
DATAPUMP.METADATA_TRANSFORM API call.
Action: Correct the transform name parameter and reissue the API request.
ORA-39043: Object type string is not supported for string.
Cause: The specified object type is invalid for the specified transform or remap.
Action: Correct the object type.
ORA-39044: Metadata transform string has already been specified.
Cause: The user has already specified the metadata transform for the same class
of object types.
Action: Specify a different object_type for the transform.
ORA-39045: invalid metadata remap name string
Cause: An invalid metadata remap name was specified on a DBMS_
DATAPUMP.METADATA_REMAP API call.
Action: Correct the metadata remap name parameter and reissue the API request.
ORA-39046: Metadata remap string has already been specified.
Cause: The user has already specified a metadata remap that matches on the
remap name and original value.
Action: Specify a different original value.
ORA-39047: Jobs of type string cannot use multiple execution streams.
Cause: The user specified a value of parallelism that is precluded by the operation
type or mode of the job.
Action: Specify only a parallelism of 1 for this type of job.
ORA-39048: Unable to start all workers; only string worker(s) available.
Cause: The full degree of parallelism could not be honored due process limits,
resource limits, or other internal errors.
Action: Increase process/resource limits for the job.
ORA-39049: invalid parameter name string
Cause: An invalid parameter name was specified on a DBMS_DATAPUMP.SET_
PARAMETER API call.
Action: Correct the parameter name and reissue the API request.
ORA-39050: parameter string is incompatible with parameter string
Cause: Two parameters were set that were incompatible with each other. Only the
first parameter setting will be used.
Action: Decide which parameter is to be used and stick to it.
ORA-39051: parameter string specified multiple times
Cause: The user has already specified a parameter that matches on the name and
the specific parameter doesn't support duplicate definitions.
Action: Specify non-repeatable parameters only once.
ORA-39052: cannot specify SKIP_CURRENT on initial start of a job.
Cause: The user has already specified SKIP_CURRENT for a job that has never
executed.
Action: Only specify SKIP_CURRENT when restarting a job.
21-48 Oracle Database Error Messages
ORA-39053: parameter or attribute string must be defined for a string job
Cause: The job being defined cannot be started because it is missing the specified
definition.
Action: Specify the omitted parameter or attribute before starting the job.
ORA-39054: missing or invalid definition of the SQL output file.
Cause: The job being defined cannot be started because it is missing the file to
receive the SQL output of the job or the definition is unusable.
Action: Specify a valid directory name and file name for the SQL file.
ORA-39055: The string feature is not supported in version string.
Cause: The user attempted to use a feature that was not enabled in the database
version specified for the current job. Typically, this error occurs if the compatibility
level of the database is below the current version of the database or if the user
explicitly specifies a version for a Data Pump job.
Action: Specify the current database version as a version parameter for the the
job.
ORA-39056: invalid log file specification.
Cause: The log file for the job was incorrectly specified.
Action: Specify a valid directory name and file name for the log file.
ORA-39057: invalid worker request string for string jobs.
Cause: The worker process sent a message that wasn't supported for the current
job.
Action: Internal error -- contact Oracle Customer Support and report the error.
ORA-39058: current object skipped: string of type string
Cause: The user specified SKIP_CURRENT when restarting a job. This message is
a confirmation that the object will not be imported.
Action: User must manually define the object in the target database.
ORA-39059: dump file set is incomplete
Cause: An IMPORT or SQL_FILE operation was being performed but not all of
the files from the EXPORT dump file set were included.
Action: Check the export log file and make sure all of the files that were exported
are included in the current job.
ORA-39060: table(s) dropped because of conflict with master table
Cause: A table specified by a job was not included because its definition would
collide with the master table definition for the current job.
Action: After the job completes. Import the conflicting tables using a unique job
name to avoid conflicts with normal user tables.
ORA-39061: import mode string conflicts with export mode string
Cause: The mode used for import cannot be used with a dump file set of specified
mode. Transportable jobs are not compatible with other modes.
Action: Perform the import using a mode compatible with the export.
ORA-39062: error creating master process string
Cause: An attempt to create the listed master process failed.
ORA-38029 to ORA-39965 21-49
Action: Refer to any following error messages for possible actions. Check the trace
log for the failed process to see if there is any information about the failure.
Correct the error, if possible, and try the operation again. If the error occurs again,
contact Oracle Customer Support and report the error.
ORA-39064: unable to write to the log file
Cause: Errors were detecting while writing to the log file. Subsequent messages
will detail the problems.
Action: Fix the problems outlined in the secondary messages.
ORA-39065: unexpected master process exception in string
Cause: An unhandled exception was detected internally within the master control
process for the Data Pump job. This is an internal error. messages will detail the
problems.
Action: If problem persists, contact Oracle Customer Support.
ORA-39067: Unable to close the log file.
Cause: Errors were detecting while closing the log file. Subsequent messages will
detail the problems.
Action: Fix the problems outlined in the secondary messages.
ORA-39068: invalid master table data in row with PROCESS_ORDER=string
Cause: A corruption was detected in the master table in the specified row(s).
Either the row wasn't found, it was missing columns or had illegal values in its
columns.
Action: Rerun the job with an uncorrupted master table.
ORA-39070: Unable to open the log file.
Cause: Errors were detecting while opening the log file. Subsequent messages will
detail the problems.
Action: Fix the problems outlined in the secondary messages.
ORA-39071: Value for string is badly formed.
Cause: The value of the user specified filter did not contain a legitimate SQL
clause. Subsequent messages will detail the problems.
Action: Fix the problems outlined in the secondary messages.
ORA-39076: cannot delete job string for user string
Cause: Unable to delete a job. Refer to the any following or prior error messages
for clarification.
Action: Eliminate the problems indicated.
ORA-39077: unable to subscribe agent string to queue "string"
Cause: The Data Pump's communication layer was unable to attach one of its
processes to the control or status queue. Subsequent messages will detail the
problem.
Action: Fix the problem if possible, or contact Oracle Customer Support.
ORA-39078: unable to dequeue message for agent string from queue "string"
Cause: The Data Pump's communication layer was unable to retrieve a message
from the control or status queue. Subsequent messages will detail the problem.
Action: Fix the problem if possible, or contact Oracle Customer Support.
21-50 Oracle Database Error Messages
ORA-39079: unable to enqueue message string
Cause: The Data Pump's communication layer was unable to send the specified
message on the control or status queue. Subsequent messages will detail the
problem.
Action: Fix the problem if possible, or contact Oracle Customer Support.
ORA-39080: failed to create queues "string" and "string" for Data Pump job
Cause: The Data Pump's communication layer was unable to create the status and
control queues required for interprocess communication. Subsequent messages
will detail the problem.
Action: Fix the problem if possible, or contact Oracle Support.
ORA-39081: failed to unsubscribe agent string from queue "string"
Cause: The Data Pump's communication layer was unable to unsubscribe a
process from the control or status queue. Subsequent messages will detail the
problem.
Action: Fix the problem if possible, or contact Oracle Customer Support.
ORA-39082: Object type string created with compilation warnings
Cause: The object in the SQL statement following this error was created with
compilation errors. If this error occurred for a view, it is possible that the base table
of the view was missing.
Action: This is a warning. The object may have to be recompiled before being
used.
ORA-39083: Object type string failed to create with error: string Failing sql is: string
Cause: Examine original error code to determine actual cause
Action: Original error code will contain more information
ORA-39084: cannot detach job string for user string
Cause: Unable to detach a job from the session. Refer to any following error
messages for clarification.
Action: Eliminate the problems indicated.
ORA-39085: cannot update job string for user string
Cause: Unable to update the fixed table information for a job. Refer to any
following or prior error messages for clarification.
Action: Eliminate the problems indicated.
ORA-39086: cannot retrieve job information
Cause: Unable to retrieve fixed table information for a job. Refer to the secondary
error messages that follow this one for clarification.
Action: Eliminate the problems indicated by the secondary errors.
ORA-39087: directory name string is invalid
Cause: A corresponding directory object does not exist.
Action: Correct the directory object parameter, or create a corresponding directory
object with the CREATE DIRECTORY command.
ORA-39088: file name cannot contain a path specification
Cause: The name of a dump file, log file, or sql file contains a path specification.
ORA-38029 to ORA-39965 21-51
Action: Use the name of a directory object to indicate where the file should be
stored.
ORA-39090: Cannot add devices to file oriented job.
Cause: Attempt to add a device to a job that already contains more than one disk
file.
Action: Only specify one file for jobs that contain sequential devices.
ORA-39091: unable to determine logical standby and streams status
Cause: An error occurred when determining if the Data Pump job needed to
support logical standby or streams.
Action: The subsequent message describes the error that was detected. Correct the
specified problem and restart the job.
ORA-39092: unable to set SCN metadata for object "string.string" of type string
Cause: An error occurred when applying a SCN to the specified object to support
logical standby or streams.
Action: The subsequent message describes the error that was detected. Correct the
specified problem and restart the job.
ORA-39093: FLASHBACK automatically enabled to preserve database integrity.
Cause: A Data Pump job was required to enable flashback support to specific
SCNs in order to preserve the consistency of a logical standby or streams
instantiation.
Action: None
ORA-39094: Parallel execution not supported in this database edition.
Cause: Parallel execution of Data Pump jobs is not supported for this database
edition.
Action: Specify a parallelism of 1 for jobs not running on Enterprise Edition
databases.
ORA-39095: Dump file space has been exhausted: Unable to allocate string bytes
Cause: The Export job ran out of dump file space before the job was completed.
Action: Reattach to the job and add additional dump files to the job restarting the
job.
ORA-39096: invalid input value string for parameter string
Cause: A NULL or invalid value was supplied for the parameter.
Action: Correct the input value and try the call again.
ORA-39097: Data Pump job encountered unexpected error string
Cause: An unexpected, potentially non-fatal error occurred while processing a
Data Pump job.
Action: Contact Oracle Customer Support.
ORA-39098: Worker process received data objects while loading metadata. Invalid
process order range is string..string
Cause: This is an internal error. Messages will detail the problem.
Action: If problem persists, contact Oracle Customer Support.
ORA-39099: cannot create index for "string" on master table string
21-52 Oracle Database Error Messages
Cause: One or more indexes couldn't be created on the master table. subsequent
error messages describe the failure.
Action: Correct the condition that is preventing the indexes from being created.
ORA-39102: Timeout before master process string finished initialization. Master
error:
Cause: The master process whose name is listed started up but did not finish its
initialization within the allowed time limit.
Action: Refer to any following error messages for possible actions. Also, check the
trace log for the failed process, if one was created, to see if there is any additional
information about the failure. Correct the error, if possible, and try the operation
again. If the error occurs again, contact Oracle Customer Support and report the
error.
ORA-39103: Timeout before worker process string finished initialization. Worker
error:
Cause: The worker process whose name is listed started up but did not finish its
initialization within the allowed time limit.
Action: Refer to any following error messages for possible actions. Also, check the
trace log for the failed process, if one was created, to see if there is any additional
information about the failure. Correct the error, if possible, and try the operation
again. If the error occurs again, contact Oracle Customer Support and report the
error.
ORA-39104: cannot call this function from a SQL parallel query slave process
Cause: Called a Data Pump process model function from a process which is a SQL
parallel query slave process
Action: A SQL parallel query slave process cannot create a Data Pump master
process. This is not supported. If this error occurs from a Data Pump client (for
example, expdp or impdp), contact Oracle Customer Support and report the error.
ORA-39105: Master process string failed during startup. Master error:
Cause: The master process whose name is listed failed during startup.
Action: Refer to any following error messages for possible actions. Also, check the
trace log for the failed process, if one was created, to see if there is any additional
information about the failure. Correct the error, if possible, and try the operation
again. If the error occurs again, contact Oracle Customer Support and report the
error.
ORA-39106: Worker process string failed during startup. Worker error:
Cause: The worker process whose name is listed failed during startup.
Action: Refer to any following error messages for possible actions. Also, check the
trace log for the failed process, if one was created, to see if there is any additional
information about the failure. Correct the error, if possible, and try the operation
again. If the error occurs again, contact Oracle Customer Support and report the
error.
ORA-39107: Master process string violated startup protocol. Master error:
Cause: The master process whose name is listed started up but then exited before
notifying the creating process that it was finished with initialization.
Action: Refer to any following error messages for possible actions. Also, check the
trace log for the failed process, if one was created, to see if there is any additional
information about the failure. Correct the error, if possible, and try the operation
ORA-38029 to ORA-39965 21-53
again. If the error occurs again, contact Oracle Customer Support and report the
error.
ORA-39108: Worker process string violated startup protocol. Worker error:
Cause: The worker process whose name is listed started up but then exited before
notifying the creating process that it was finished with initialization.
Action: Refer to any following error messages for possible actions. Also, check the
trace log for the failed process, if one was created, to see if there is any additional
information about the failure. Correct the error, if possible, and try the operation
again. If the error occurs again, contact Oracle Customer Support and report the
error.
ORA-39109: Unprivileged users may not operate upon other users' schemas
Cause: An unprivileged user attempted to reference another user's schema during
a Data Pump operation. Because of this, no schemas were were selected for the job.
Action: Retry the operation under a username owning the schema.
ORA-39110: error deleting worker processes
Cause: An attempt to delete the worker processes failed.
Action: Refer to any following error messages for possible actions. Correct the
error, if possible, and try the operation again. If the error occurs again, contact
Oracle Customer Support and report the error.
ORA-39111: Dependent object type string skipped, base object type string already
exists
Cause: During a Data Pump import job, a dependent object is being skipped
because its base object already existed.
Action: If the object from the dump file is wanted, drop the base and dependent
objects and try to import again using desired filters.
ORA-39112: Dependent object type string skipped, base object type string creation
failed
Cause: During a Data Pump import job, a dependent object is being skipped
because its base object creation failed.
Action: If the object from the dump file is wanted, drop the base and dependent
objects and try to import again using desired filters
ORA-39113: Unable to determine database version
Cause: The Data Pump was unable to determine the compatibility level and
version of the current database using SYS.DBMS_UTILITY.DB_VERSION.
Action: Make sure access to the DBMS_UTILITY package is granted to you. If this
is a network job, be sure that access to the DBMS_UTILITY package is granted to
you on the remote instance.
ORA-39114: Dump files are not supported for network jobs.
Cause: An attempt was made to add a dumpfile to an Import job that is using a
network link to the source database.
Action: Do not specify a dumpfile for jobs that do not require dumpfiles.
ORA-39115: string is not supported over a network link
Cause: An attempt was made to use an option that is not supported over network
links such as the PARTITION_LIST filter.
21-54 Oracle Database Error Messages
Action: Do not attempt to use Data Pump features on network jobs if they are not
compatible with jobs over the network.
ORA-39116: invalid trigger operation on mutating table string.string
Cause: A Data Pump load operation failed because a trigger attempted to fire on
the table while it was mutating.
Action: Disable trigger(s) on the specified table. Also see ORA-004091.
ORA-39117: Type needed to create table is not included in this operation. Failing
sql is: string
Cause: A create table was attempted and a dependent type does not exist in the
dumpfile or on the target database. Either the export or the import Data Pump job
was a table mode job and types are not included in table mode jobs.
Action: Determine which type(s) are missing and create them on the target system
and run the Data Pump import job again.
ORA-39119: worker process interrupt for delete worker processes call by master
process
Cause: The master process that created this worker process called delete worker
processes to abort the current operation.
Action: No action is necessary. This is an informational error message.
ORA-39120: Table string can't be truncated, data will be skipped. Failing error is:
string
Cause: Table data was about to be loaded into a table that already existed and the
table_exists_action parameter is truncate, but the table could not be truncated.
Action: Determine actual cause by looking at base error.
ORA-39121: Table string can't be replaced, data will be skipped. Failing error is:
string
Cause: Table data was about to be loaded into a table that already existed and the
table_exists_action parameter is replace, but the table could not be dropped.
Action: Determine actual cause by looking at base error.
ORA-39122: Unprivileged users may not perform string remappings.
Cause: A user attempted to remap objects during an import but lacked the
IMPORT_FULL_DATABASE privilege.
Action: Retry the job from a schema that owns the IMPORT_FULL_DATABASE
privilege.
ORA-39123: Data Pump transportable tablespace job aborted string
Cause: A DBMS_PLUGTS procedure failed and the Data Pump operation could
not continue so it was aborted. The DBMS_PLUGTS failure listed describes the
original error.
Action: Look at the DBMS_PLUGTS error to determine actual cause.
ORA-39124: dump file name "string" contains an invalid substitution variable
Cause: The substitution variable '%' must be followed by '%','u', or 'U'.
Action: Correct the substitution variable in the dump file name and re-enter the
command.
ORA-39125: Worker unexpected fatal error in string while calling string [string]
ORA-38029 to ORA-39965 21-55
Cause: An unhandled exception was detected internally within the worker
process for the Data Pump job while calling the specified external routine. This is
an internal error. Additional information may be supplied.
Action: If problem persists, contact Oracle Customer Support.
ORA-39126: Worker unexpected fatal error in string [string] string
Cause: An unhandled exception was detected internally within the worker
process for the Data Pump job. This is an internal error. Additional information
may be supplied.
Action: If problem persists, contact Oracle Customer Support.
ORA-39127: unexpected error from call to string string
Cause: The exception was raised by the function invocation, a procedural action
extension of export.
Action: Record the accompanying messages and report this as a Data Pump
internal error to customer support.
ORA-39128: unexpected DbmsJava error number from statement string
Cause: The error was returned from a call to a DbmsJava procedure.
Action: Record the accompanying messages and report this as a Data Pump
internal error to customer support.
ORA-39129: Object type string not imported. Name conflicts with the master table
Cause: The table being imported from the remote instance has the same name as
the master table running this Data Pump job.
Action: Rerun the Data Pump job with a nonconflicting name.
ORA-39130: Object type string not imported. Base object name conflicts with the
master table
Cause: The object being imported from the remote instance is dependent on an
object that has the same name as the master table running this Data Pump job.
Action: Rerun the Data Pump job with a nonconflicting name.
ORA-39132: object type "string"."string" already exists with different hashcode
Cause: An object type could not be created because there was already a type with
the same name but a different hashcode on the target system. Tables in the
transportable tablespace set that use this object type cannot be read.
Action: Drop the object type from the target system and retry the operation.
ORA-39133: object type "string"."string" already exists with different typeid
Cause: An object type in a transportable tablespace set already exists on the target
system, but with a different typeid. The typeid could not be changed because the
type is used by an existing table. Tables in the transportable tablespace set that use
this object type cannot be read.
Action: Drop the object type from the target system and retry the operation.
ORA-39134: Cannot include "string" tablespace as a Transportable Tablespace
Cause: The user attempt to specify the SYSAUX or SYSTEM tablespace as a
member of the transportable tablespace list in the current job. These tablespaces
may not be transported between databases.
Action: Specify different tablespaces to be transported.
21-56 Oracle Database Error Messages
ORA-39135: File "string" is already a member of this dump set
Cause: An attempt was made to add a new file to an export job but a file with the
same name already exists in the dump set for the job.
Action: Reenter the new file information using a different file name.
ORA-39136: cannot specify an SCN on a transportable job
Cause: A target SCN was specified for a table in a transportable job by the streams
or logical standy components which was not the defaulted SCN for the table.
Action: This is an internal error. Please report it to Oracle support.
ORA-39137: cannot specify a TABLE_EXISTS_ACTION of string for a job with no
metadata
Cause: A job was defined with the TABLE_EXISTS_ACTION parameter set to
REPLACE or SKIP, but without metadata. Without metadata, data could not be
loaded for the requested table actions.
Action: Change the setting of the TABLE_EXISTS_ACTION parameter to
APPEND or TRUNCATE or supply Metadata with the data.
ORA-39138: Insufficient privileges to load data not in your schema
Cause: An unprivileged user attempted to load data into a different schema.
Action: Use a privileged account if you must load data not in your schema
ORA-39139: Data Pump does not support XMLType objects in version string. string
will be skipped.
Cause: Object had an XMLType column using either an object relational or binary
storage format, which is unsupported by Data Pump in the target version.
Action: Use the original export and import utilities to move this object.
ORA-39140: dump file "string" belongs to job string
Cause: When a dump file set consists of multiple files, all files in the set must be
specified for an import operation, and all files must have been produced by the
same export job. One of the files provided does not belong to the original dump
file set. For instance, it was created by a different export job than the other files.
Action: Remove the dump file indicated in the message and retry the import
operation providing only the complete set of dump files created by a specific
export job.
ORA-39141: dump file "string" is a duplicate of dump file "string"
Cause: When a dump file set consists of multiple files, all files in the set must be
specified for an import operation. One of the files provided to import was found to
be a duplicate of another dump file in the set. This can occur if the files in the
dump set were copied or renamed using operating system utilities and the same
dump file was inadvertently copied more than once with different destination
names.
Action: Remove the dump file indicated in the message and retry the import
operation providing only the complete set of dump files created by a specific
export job.
ORA-39142: incompatible version number string in dump file "string"
Cause: A dump file was specified for an import operation whose version number
is incompatible with the dump file version of the Data Pump product currently
running on the system. Usually this message indicates that the dump file was
produced by a newer version of the Data Pump export utility.
ORA-38029 to ORA-39965 21-57
Action: Import this dump file using the Data Pump import utility with the same
version as the export which created the file.
ORA-39143: dump file "string" may be an original export dump file
Cause: A dump file was specified for an import operation which appears to have
been created using the original export utility. These dump files cannot be
processed by the Data Pump import utility.
Action: Try using the original import utility to process this dump file.
ORA-39144: file name parameter must be specified and non-null
Cause: No file name was provided in an DBMS_DATAPUMP.ADD_FILE API call.
Action: Correct the file name parameter and reissue the API request.
ORA-39145: directory object parameter must be specified and non-null
Cause: No directory object was provided in either an DBMS_DATAPUMP.ADD_
FILE API call or to the directory parameter used by the Data Pump command line
clients.
Action: Correct the directory object parameter and retry the operation.
ORA-39146: schema "string" does not exist
Cause: The specified schema was referenced as the source of a REMAP_SCHEMA
parameter, but did not exist in the dump file (for file-based import) or in the
source database (for network import).
Action: Specify the correct name of the schema to be remapped.
ORA-39147: cannot migrate Data Pump queue table ownership to this instance
Cause: There are active Data Pump jobs running on another instance in a RAC.
All concurrent, active Data Pump jobs must be run on the same instance.
Action: Start this job on the same instance where other active Data Pump jobs are
running, or wait until they finish.
ORA-39148: unable to import data into pre-existing queue table string. Table_
exists_action of string being ignored for this table
Cause: A Data Pump import detected that a queue table that was to be imported
already exists. Importing data into pre-existing queue tables is not supported.
Action: If the data from the dump file is desired, then drop the queue table and
perform the import again, or use the import parameter table_exists_
action=replace.
ORA-39149: cannot link privileged user to non-privileged user
Cause: A Data Pump job initiated be a user with EXPORT_FULL_
DATABASE/IMPORT_FULL_DATABASE roles specified a network link that did
not correspond to a user with equivalent roles on the remote database.
Action: Specify a network link that maps users to identically privileged users in
the remote database.
ORA-39150: bad flashback time
Cause: A flashback time was specified for the Data Pump job which either could
not be parsed or else could not be translated into a system change number (SCN).
This typically occurs when specifying a time far in the past.
Action: Specify an explicit SCN for the desired flashback rather than a time.
ORA-39154: Objects from foreign schemas have been removed from import
21-58 Oracle Database Error Messages
Cause: An non-privileged user attempted to import objects into a schema other
than their own.
Action: Either perform the import from a privileged schema or else remap all
schemas that were exported into the username running the import.
ORA-39155: error expanding dump file name "string"
Cause: Export was unable to expand the directory object and dump file name into
a full file name. Subsequent messages will detail the problems.
Action: Fix the problems outlined in the secondary messages.
ORA-39156: error parsing dump file name "string"
Cause: Export was unable to parse the dump file name. Subsequent messages will
detail the problems.
Action: Fix the problems outlined in the secondary messages.
ORA-39157: error appending extension to file "string"
Cause: Export or Import was unable to append the default extension to create the
file name. The given file name could be too long or contain illegal characters.
Subsequent messages will detail the problems.
Action: Fix the problems outlined in the secondary messages.
ORA-39159: cannot call this function from a non-Data Pump process
Cause: Called a Data Pump process model function from a process which is not a
Data Pump process.
Action: Refer to any other error messages for additional information. If this error
occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If
the error occurs again, contact Oracle Customer Support and report the error.
ORA-39160: error on whats my name call
Cause: Attempt to get the Data Pump process name failed.
Action: Refer to any following error messages for additional information. If this
error occurs from a Data Pump client (e.g. expdp or impdp), try the operation
again. If the error occurs again, contact Oracle Customer Support and report the
error.
ORA-39161: Full database jobs require privileges
Cause: Either an attempt to perform a full database export without the EXP_
FULL_DATABASE role or an attempt to perform a full database import over a
network link without the IMP_FULL_DATABASE role.
Action: Retry the operation in a schema that has the required roles.
ORA-39162: Transportable tablespace job require privileges
Cause: User attempted to perform a transportable tablespace job without being
having the proper EXP_FULL_DATABASE or IMP_FULL_DATABASE role.
Action: Retry the operation in a schema that has the required roles.
ORA-39163: A sample size of string is invalid.
Cause: An attempt was made to do data sampling on a table with a value outside
of the range of 0 - 100.
Action: Retry the filtering using a sampling number greater than 0 and less than
100.
ORA-38029 to ORA-39965 21-59
ORA-39164: Partition string was not found.
Cause: If exporting or importing over the network, the user specified a partition
name that was not found in the source database. For importing from files, the user
specified a partition name not found in the dump file set.
Action: Retry the operation using the correct partition name.
ORA-39165: Schema string was not found.
Cause: If exporting or importing over the network, either the user specified a
schema name that was not found in the source database or else the user lacked the
proper EXP_FULL_DATABASE or IMP_FULL_DATABASE role that would allow
them to access another schema. For importing from files, the user specified a
schema name not found in the dump file set.
Action: Retry the operation using the correct schema name.
ORA-39166: Object string was not found or could not be exported or imported.
Cause: If exporting to files or importing over the network, one of the following
occurred:
- The object specified did not exist in the source database.
- The user lacked the proper EXP_FULL_DATABASE or IMP_FULL_DATABASE
role that would allow access to the object.
- The VIEWS_AS_TABLES object contained a type that is not supported with the
VIEWS_AS_TABLES parameter. If importing from files, the user specified an
object name that was not found in the dump file set.
Action: Retry the operation using the correct object name, correct set of privileges,
or a view that has only supported types.
ORA-39168: Object path string was not found.
Cause: If exporting or importing over the network, the user specified an object
type path name that was not found in the source database. For importing from
files, the user specified an object type path name not found in the dump file set.
Action: Retry the operation using the correct object type path name.
ORA-39169: Local version of string cannot work with remote version of string.
Cause: A Data Pump job specified a network link, but the version on the remote
database cannot interoperate with the version on the local database.
Action: Do not specify network links between instance running different versions
of the database.
ORA-39170: Schema expression string does not correspond to any schemas.
Cause: A schema expression or schema list was supplied for a Data Pump job that
did not identify any schemas in the source database.
Action: Correct the schema specifications and retry the job.
ORA-39171: Job is experiencing a resumable wait. string
Cause: The Data Pump job is stalled with one or more of its sessions having a
resumable wait. Resumable waits are typically caused by a non-expandable
tablespace running out of space. The follow-on message describes the nature of the
wait.
Action: Correct the condition causing the wait. This will typically involve adding
datafiles to the tablespace that is full.
21-60 Oracle Database Error Messages
ORA-39172: Cannot remap transportable tablespace names with compatibility of
string.
Cause: The user attempted to remap a tablespace name in a transportable
tablespace job when the compatibility level was set below 10.1.
Action: Reset the compatibility level of the database to a more recent version.
ORA-39173: Encrypted data has been stored unencrypted in dump file set.
Cause: No encryption password was specified for an export job that involved
data that was encrypted in the database.
Action: No specific user action is required. This is only a warning that secure data
may be readable from within the dump file set.
ORA-39174: Encryption password must be supplied.
Cause: No encryption password was supplied to import a dump file set that was
created using an encryption password.
Action: Specify the encryption password for the dump file set.
ORA-39175: Encryption password is not needed.
Cause: An encryption password was supplied to import a dump file set that was
not created using an encryption password.
Action: No user action is required. This is merely a warning message.
ORA-39176: Encryption password is incorrect.
Cause: The wrong encryption password was supplied to import a dump file set.
Action: Resubmit the job using the correct encryption password for the dump file
set.
ORA-39177: invalid compression value string
Cause: An invalid value was specified for compression.
Action: Correct the value and recreate the job.
ORA-39178: cannot perform estimate on metadata only jobs
Cause: An estimate was requested for a job by specifying the ESTIMATE or
ESTIMATE_ONLY parameter. However, the job was also defined to have no data.
These specifications conflict with each other.
Action: Remove one of the conflicting specifications for the job.
ORA-39179: unable to load table "string"."string" because of OID transform
Cause: The OID transform for the job was set to false and the identified table
contained either VARRAYs with non-final types or unscoped REF columns. Both
of these column types have embedded OIDs so they cannot be imported correctly
when OIDs are not preserved.
Action: You must manually move the data with the specified tables when OIDs
are not preserved.
ORA-39180: unable to encrypt ENCRYPTION_PASSWORD
Cause: The specified encryption password was unable to be encrypted for
placement within the master table or decrypted when it was to be restored from
the master table. Subsequent messages will describe the actual error that caused
the encryption to fail.
Action: Fix the problems referenced by the subsequent messages. The most
common reason for the encryption to fail is the lack of a security wallet.
ORA-38029 to ORA-39965 21-61
ORA-39181: Only partial table data may be exported due to fine grain access control
on string
Cause: An unprivileged user has tried to export a table that has fine grain access
control. The table owner is subjected to access control and may not be able to
export all rows in the table. Only the rows that can be seen by that user will be
exported. In order to preserve integrity of the table, the user importing the table
should have enough privilege to recreate the table with the security policies at
import time.
Action: It is strongly recommended that the database administrator handle
exporting of this table.
ORA-39182: internal error string occurred during compression phase string
Cause: An unexpected error occurred while compressing data buffers.
Action: Contact Oracle Customer Support.
ORA-39183: internal error string ocurred during decompression phase string
Cause: An unexpected error occurred while decompressing data buffers.
Action: Contact Oracle Customer Support.
ORA-39184: Transportable Data Pump jobs cannot exclude PLUGTS objects
Cause: A Transportable Data Pump job requires all PLUGTS% objects, but the
user-supplied exclude filters were excluding these objects.
Action: Reenter command without excluding PLUGTS% objects.
ORA-39185: The transportable tablespace failure list is
Cause: Some of the tablespaces specified for this job could not be exported.
Action: See specific errors for each tablespace, correct the problem, and try again.
ORA-39186: No tablespaces in the specified list exist.
Cause: The tablespaces specified on the EXPORT command did not exist.
Action: Check the list of tablespaces and reenter command with correct set of
tablespaces.
ORA-39187: The transportable set is not self-contained, violation list is
Cause: The tablespaces specified for this job did not satisfy the closure checking.
The list of violations specified each closure violation.
Action: See specific errors for violation and correct the problem or change the
tablespaces on the command line and try again.
ORA-39188: unable to encrypt dump file set
Cause: Data Pump could not create an encrypted dump file set. This message will
be accompanied by other messages that give more details about why the
encrypted dump file set could not be created. The most common reason for this
message is that you are trying to create a dump file set that can be transparently
decrypted, and the database external security device is not open.
Action: If the external security device is not open, then open it. If the external
security device is not configured, then the only type of encrypted dump file set
that you can create is a password-based dump file set.
ORA-39189: unable to decrypt dump file set
21-62 Oracle Database Error Messages
Cause: The dump file set could not be decrypted. The reason could be either that
an invalid password was entered, or that, when using transparent decryption, the
database external security device was not open.
Action: If password-based import was enabled for this dump file set, then supply
the correct password. If transparent import was enabled for this dump file set,
then ensure that the database external security device is open.
ORA-39190: internal error occurred during encryption phase string
Cause: An unexpected error occurred while encrypting data buffers.
Action: See the secondary error for more information and contact Oracle
Customer Support.
ORA-39191: internal error ocurred during decryption phase string
Cause: An unexpected error occurred while decrypting data buffers.
Action: See the secondary error for more information and contact Oracle
Customer Support.
ORA-39192: table mode jobs with transportable=always and partition filters only
allow objects from one table
Cause: Multiple tables are not supported when specifying partitions while using
transportable table mode.
Action: Retry the job specifying only one table.
ORA-39193: Table mode jobs do not allow the schema to be wild carded.
Cause: The table filter included a schema expression with the % wild card.
Action: Retry the job specifying actual schemas.
ORA-39194: Table mode jobs require the tables to be comma separated.
Cause: The string describing tables in a table mode job was not comma separated.
Action: Retry the job specifying the tables separated by commas.
ORA-39195: At least one schema in the TABLE_FILTER does not exist.
Cause: The TABLE_FITER specified contains a schema that does not exist.
Action: Retry the job specifying only schemas that exist.
ORA-39200: Link name "string" is invalid.
Cause: The name of the network link supplied for a Data Pump job was not
usable. Secondary messages identify the problem.
Action: Rerun the job using a valid network link.
ORA-39201: Dump files are not supported for estimate only jobs.
Cause: An attempt was made to add a dumpfile to an Export job that only
requested file estimates.
Action: Do not specify a dumpfile for jobs that do not require dumpfiles.
ORA-39202: Data cannot be filtered or selected in string jobs.
Cause: A data filter was supplied for the specified type of job, but is not
supported in the specified job type. From the command line, data filters can be
specified by the CONTENT, TABLES (partition specifications), SAMPLE and
QUERY parameters.
Action: Do not restrict data handling on jobs that cannot support data filtering.
ORA-38029 to ORA-39965 21-63
ORA-39203: Partition selection is not supported over a network link.
Cause: Specific partitions were selected for a job operating over a network link.
Action: Remove the partition specifications and rerun the job.
ORA-39204: No subsetting of tablespaces is allowed for transportable import.
Cause: A tablespace filter was applied to a transportable import job that was not
performed over a network link. In this case, the tablespace may not be changed
from its specification at export time.
Action: Rerun the job without specifying a tablespace filter.
ORA-39205: Transforms are not supported in transportable jobs.
Cause: A metadata transformation such as STORAGE or SEGMENT_
ATTRIBUTES has been specified for a transportable Data Pump job.
Action: Rerun the job without specifying a transform.
ORA-39206: A parallel degree of string is invalid.
Cause: A bad numeric was supplied for specifying the parallelism to be used
within a Data Pump job. The degree of parallelism must be an integer great than 0.
Action: The the degree specifying and retry the parallelism setting.
ORA-39207: Value string is invalid for parameter string.
Cause: A parameter for a Data Pump job was set with a NULL or invalid value.
Action: Refer to the documentation to identify the legal values for each parameter.
Retry the operation with a valid value.
ORA-39208: Parameter string is invalid for string jobs.
Cause: The a parameter has been specified that is not supported for the specified
type of Data Pump.
Action: Remove the parameter specification and retry the operation.
ORA-39209: Parameter string requires privileges.
Cause: Use of the specified privileges requires the user to have the IMP_FULL_
DATABASE role for import jobs or the EXP_FULL_DATABASE role for export
jobs.
Action: Remove the parameter specification and retry the operation.
ORA-39210: A PCTSPACE adjustment of string is invalid.
Cause: User specified a storage space transformation that was out of range.
Values for PCTSPACE must be greater than zero.
Action: Retry the operation with a valid PCTSPACE value.
ORA-39211: unable to retrieve dumpfile information as specified
Cause: User specified an invalid or inaccessible file with the specified filename
and directory object.
Action: Retry the operation with a valid directory object and filename.
ORA-39212: installation error: XSL stylesheets not loaded correctly
Cause: The XSL stylesheets used by the Data Pump Metadata API were not
loaded correctly into the Oracle dictionary table "sys.metastylesheet." Either the
stylesheets were not loaded at all, or they were not converted to the database
character set.
21-64 Oracle Database Error Messages
Action: Connect AS SYSDBA and execute dbms_metadata_util.load_stylesheets
to reload the stylesheets.
ORA-39213: Metadata processing is not available
Cause: The Data Pump could not use the Metadata API. Typically, this is caused
by the XSL stylesheets not being set up properly.
Action: Connect AS SYSDBA and execute dbms_metadata_util.load_stylesheets
to reload the stylesheets.
ORA-39214: Data Pump does not support external tables with encrypted columns.
string will not be exported
Cause: The object is an external table with encrypted columns and this is
unsupported with Data Pump.
Action: External table must be manually recreated on the target system.
ORA-39216: object type "string"."string" hashcode mismatch
Cause: An object type in a transportable tablespace set could not be used because
there was a type with the same name but a different hashcode (and type
definition) on the target system. Tables in the transportable tablespace set that use
this object type cannot be created.
Action: Drop the object type and dependent objects from the target system if
possible and retry the operation.
ORA-39217: object type "string"."string" typeid mismatch
Cause: An object type in a transportable tablespace set already exists on the target
system, but with a different typeid. The typeid could not be changed because the
type or a dependent type is used by an existing table. Tables in the transportable
tablespace set that use this object be created.
Action: Drop the object type and dependent objects from the target system if
possible and retry the operation.
ORA-39218: type check on object type "string"."string" failed
Cause: The type check on a type failed. Therefore, the table create for the table
which uses the type also fails.
Action: Refer to any following error messages for additional information. Correct
the error, if possible, and try the action again.
ORA-39219: directory object name is too long
Cause: The directory object name provided to the Data Pump Job was invalid
because its length was greater than 30 characters.
Action: Retry the operation with a valid directory object name.
ORA-39220: file name is too long
Cause: The file name provided to the Data Pump Job was invalid because its
length was greater than 4000 characters.
Action: Retry the operation with a valid file name.
ORA-39221: Specifying data filters is invalid when dumpfiles do not contain table
data.
Cause: A data filter was supplied for an import job, but the dumpfile does not
contain any table data. The export command created a dumpfile with metadata
only. No table data was included. From the command line, data filters can be
specified by the CONTENT, SAMPLE and QUERY parameters.
ORA-38029 to ORA-39965 21-65
Action: Do not restrict data handling on jobs that cannot support data filtering.
ORA-39222: Unable to create global temporary master table string
Cause: Data Pump tried to create a global temporary master table but could not.
The errors that follow describe why the table could not be created.
Action: Examine and fix the problems described in the additional errors.
ORA-39223: Internal Data Pump error. Master table information for version string
not found.
Cause: An unexpected error occurred while processing the job. The data in an
internal table could not be found.
Action: Contact Oracle Support Services.
ORA-39224: string row(s) were rejected with the following error: string
Cause: These rows were not loaded due to constraint or index violations.
Action: Retry the operation when row data is fixed.
ORA-39228: Unable to construct a unique departitioned object name for string
string.string:string when defaulted.
Cause: All (sub)partitions in the job were to be created as individual objects and
the renaming was defaulted. The job will attempt to create unique object names,
but the name creation algorithm was unable to find a unique object name for the
specified (sub)partition.
Action: Specify a rename_table transform to use or delete some of the existing
objects causing the name conflicts.
ORA-39230: Service name string is not available
Cause: The specified resource service name for the Data Pump job was not
available.
Action: Pick a service name that the user is authorized to use.
ORA-39231: invalid data remap name: string
Cause: The specified type of data remapping was not supported.
Action: Only COLUMN_FUNCTION data remaps are supported. Retry the
operation using a supported data remap name.
ORA-39232: invalid remap function: string
Cause: The specified package function for performing data remapping was not
found.
Action: Either create the specified package function or else grant the user access
to the function.
ORA-39233: invalid remap column name: string
Cause: The column name specified for the data remapping does not exist in the
specified table.
Action: Specify a scalar column name within the table to be remapped.
ORA-39234: Data cannot be remapped under the direct path access method.
Cause: Data remapping was requested on a job that requires the direct path access
method. Data remapping can only be performed using the external table access
method.
Action: Retry the job without specifying any access method.
21-66 Oracle Database Error Messages
ORA-39235: data remap string has already been specified
Cause: A data remap has already been specified for the indicated column. Only
one data remap may be defined for a column.
Action: Remove one of the data remap specifications for the job.
ORA-39237: Failed to load XML document string. Compare process aborted.
Cause: An error occurred while performing XML difference parse.
Action: Resubmit XML compare request with valid document.
ORA-39238: XML node attribute differences are not supported.
Cause: MDAPI XML difference parsing did not support node attributes.
Action: Resubmit XML compare request with valid document.
ORA-39239: No differences found.
Cause: XML documents compared were identical.
Action: No action required.
ORA-39240: Error while processing difference document.
Cause: Error occurred in the MDAPI difference writer.
Action: Refer to any following error messages for additional information. Correct
the error, if possible, and try the action again.
ORA-39242: Unable to export/import string due to table attributes.
Cause: See the Data Pump documentation for an explanation of what table
attributes prevent an export or import from succeeding.
Action: Resolve conflicting table attributes.
ORA-39243: Import job requires 'TRANSPORT_DATAFILES' parameter.
Cause: The export job used 'TRANSPORTABLE=ALWAYS' and the import job
requires TRANSPORT_DATAFILES to be specified.
Action: Specify the transport datafiles associated with this job.
ORA-39245: import job requires export dump file "string"
Cause: A Data Pump IMPORT or SQL_FILE operation was being performed but
not all of the files from the Data Pump export dump file set were included.
Action: Check the export log file and make sure all of the files that were exported
are included in the current job. The import log file also lists the export names of
the missing files.
ORA-39246: cannot locate master table within provided dump files
Cause: A Data Pump IMPORT or SQL_FILE operation was being performed but
not all of the files from the Data Pump export dump file set were included. In
particular, the dump file containing the export job's master table was not provided.
Action: Check the export log file and make sure all of the files that were exported
are included in the current job.
ORA-39251: Importing a SecureFile LOB with metadata into a scalar, column string,
is not allowed.
Cause: An import of a SecureFile LOB with metadata into a scalar column was
attempted.
Action: Change the scalar column to a SecureFile LOB.
ORA-38029 to ORA-39965 21-67
ORA-39252: Importing a SecureFile LOB with metadata or archived SecureFile LOB
into a BasicFile LOB is not allowed
Cause: An attempt was made to import a SecureFile LOB that contained metadata
or was archived at the time of export into a BasicFile LOB.
Action: Perform the import into a different table, perform DBMS_
LOB.ARCHIVE_GET on any archived SecureFile LOBs, and then use INSERT AS
SELECT to migrate the SecureFile LOB data to the BasicFile LOB.
ORA-39253: Specified tables do not exist.
Cause: The tables specified for this export job did not exist.
Action: Check the specified table list and make sure the tables listed exist.
ORA-39254: direct path load not possible into preexisting table with column that
has a default value and is not being loaded; table string, column string
Cause: The direct path access method could not be used to load into a pre-existing
table that has a column with a default value and that column is not being loaded
into.
Action: Remove the ACCESS_METHOD parameter from the import command
line.
ORA-39255: Failed to fetch PLUGTS_BLKs.
Cause: The Data Pump expected a PLUGTS_BLK object to be exported but none
were.
Action: Contact Oracle Support Services.
ORA-39256: Transportable tablespace Data Pump jobs from read-only databases not
supported.
Cause: The remote database was read-only and Data Pump export jobs using
transportable tablespace over a network link require the remote database to be
read/write.
Action: Use Data Pump without transportable tablespace or make the remote
database read/write.
ORA-39258: Cannot rename cluster.
Cause: DBMS_METADATA_DIFF was comparing two clusters with different
names. There is no SQL ALTER statement to rename a cluster.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39259: Cannot add column to cluster.
Cause: DBMS_METADATA_DIFF was comparing two clusters with different
column lists. There is no SQL ALTER statement to add a column to a cluster.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39260: Cannot delete column from cluster.
Cause: DBMS_METADATA_DIFF was comparing two clusters with different
column lists. There is no SQL ALTER statement to delete a column from a cluster.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39261: Cannot modify column in cluster.
Cause: DBMS_METADATA_DIFF was comparing two clusters with different
column lists. There is no SQL ALTER statement to modify a column in a cluster.
Action: The difference cannot be eliminated with an SQL ALTER statement.
21-68 Oracle Database Error Messages
ORA-39262: Cannot alter size for hash cluster.
Cause: DBMS_METADATA_DIFF was comparing two hash clusters with different
sizes. There is no SQL ALTER statement to modify the size of a hash cluster.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39263: Cannot alter PARALLEL INSTANCES.
Cause: DBMS_METADATA_DIFF was comparing two objects, both with
PARALLEL but with different INSTANCES values. There is no SQL ALTER
statement to modify PARALLEL INSTANCES.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39264: Cannot alter type of table: string
Cause: DBMS_METADATA_DIFF was comparing tables of different types:
relational table, object table or XMLType table. There is no SQL ALTER statement
to change a table's type.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39265: Cannot alter object_type of object table: string
Cause: DBMS_METADATA_DIFF was comparing object tables based on different
object types. There is no SQL ALTER statement to change an object table's object
type.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39266: Cannot alter unpartitioned table to partitioned.
Cause: DBMS_METADATA_DIFF was comparing two tables, one unpartitioned,
the other partitioned. There is no SQL ALTER statement to partition an
unpartitioned table.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39267: Cannot remove default from table column.
Cause: DBMS_METADATA_DIFF was comparing two table columns, one with a
default value, one without. There is no SQL ALTER syntax to remove a column
default.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39268: Cannot alter a real column to make it virtual or vice versa.
Cause: DBMS_METADATA_DIFF was comparing two table columns, one virtual,
one real. There is no SQL ALTER statement to make a virtual column real or vice
versa.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39269: Cannot alter a column of type LONG to anything other than LOB.
Cause: DBMS_METADATA_DIFF was comparing two table columns, the first of
type LONG, the second of a data type other than LOB. There is no SQL ALTER
statement to modify a long data type to anything other than a CLOB or NCLOB.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39270: Cannot alter a LOB column to another data type.
Cause: DBMS_METADATA_DIFF was comparing two table columns, the first of
type CLOB, NCLOB or BLOB, the second of some other data type. There is no SQL
ALTER statement to change the data type of a LOB column.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-38029 to ORA-39965 21-69
ORA-39271: Cannot alter substitutability of column: string
Cause: DBMS_METADATA_DIFF was comparing two table columns. This error
may occur because the first column is substitutable and the second column is not,
or because the first column is OF TYPE and the second column is substitutable.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39272: Cannot alter organization of nested table column: string
Cause: DBMS_METADATA_DIFF was comparing two nested table columns. One
was a heap table, the other an index-organized table. There is no SQL ALTER
statement to change the organization of a nested table.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39273: Cannot alter storage type of XMLType column: string
Cause: DBMS_METADATA_DIFF was comparing two XMLType columns with
different storage types (CLOB, BINARY, OBJECT RELATIONAL). There is no SQL
ALTER statement to change the storage type of an XMLType column.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39274: Cannot alter physical organization of table.
Cause: DBMS_METADATA_DIFF was comparing two tables with different
physical organizations (heap, index organized, external, or cluster). There is no
SQL ALTER statement to change the physical organization of a table.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39275: Cannot alter INITIAL storage option.
Cause: DBMS_METADATA_DIFF was comparing two tables with different
FREELIST GROUPS storage options. There is no SQL ALTER statement to change
a table's INITIAL storage option.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39276: Cannot alter MINEXTENTS storage option.
Cause: DBMS_METADATA_DIFF was comparing two tables with different
MINEXTENTS storage options. There is no SQL ALTER statement to change a
table's MINEXTENTS storage option.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39277: Cannot alter FREELIST GROUPS storage option.
Cause: DBMS_METADATA_DIFF was comparing two tables with different
FREELIST GROUPS storage options. There is no SQL ALTER statement to change
a table's FREELIST GROUPS storage option.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39278: Cannot alter table with segments to segment creation deferred.
Cause: DBMS_METADATA_DIFF was comparing two tables, the first with
allocated segments, the second with deferred segments. There is no SQL ALTER
statement to change a table which already has segments to segment creation
deferred.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39279: Cannot alter tablespace of overflow segment.
21-70 Oracle Database Error Messages
Cause: DBMS_METADATA_DIFF was comparing two index organized tables
whose overflow segments have different tablespaces. There is no SQL ALTER
statement to change an overflow segment's tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39280: Cannot drop overflow segment.
Cause: DBMS_METADATA_DIFF was comparing two index organized tables, the
first with an overflow segment, the second without. There is no SQL ALTER
statement to drop an overflow segment.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39281: Cannot alter COMPRESS in index-organized materialized view.
Cause: DBMS_METADATA_DIFF was comparing two index organized
materialized views with different key compression values. There is no SQL ALTER
statement to modify the key compression of an index organized materialized view.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39282: Cannot alter default tablespace of partitions in partitioned table.
Cause: DBMS_METADATA_DIFF was comparing two partitioned tables with
different default tablespaces. There is no SQL ALTER statement to change the
default tablespace of a partitioned table.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39283: Cannot drop, split or merge hash partition: string
Cause: DBMS_METADATA_DIFF was comparing two tables or indexes
partitioned or subpartitioned by hash, and a (sub)partition in the first object was
not present in the second object. Partition maintenance operations such as drop,
split or merge can only be performed on list or range (sub)partitioned objects.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39284: Cannot alter the list values of a list subpartition: string
Cause: DBMS_METADATA_DIFF was comparing two tables subpartitioned by
list, one of which has a subpartition with the same name but a different values list
as a subpartition in the other. There is no SQL ALTER statement to change the list
values of a list subpartition.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39285: Cannot alter index key compression.
Cause: DBMS_METADATA_DIFF was comparing two indexes with different
values of key compression. There is no SQL ALTER statement to change index key
compression.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39286: Cannot convert between types of index.
Cause: DBMS_METADATA_DIFF was comparing two indexes of different types,
for example, a table index, a domain index, a cluster index, a bitmap index or a
bitmap join index There is no SQL ALTER statement to change the type of an
index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39287: Cannot alter index column list.
Cause: DBMS_METADATA_DIFF was comparing two indexes with different
column lists. There is no SQL ALTER statement to change the columns of an index.
ORA-38029 to ORA-39965 21-71
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39288: Cannot alter index base table.
Cause: DBMS_METADATA_DIFF was comparing two table indexes defined on
different tables. There is no SQL ALTER statement to change the base table of an
index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39289: Cannot add or drop local index partition or subpartition: string
Cause: DBMS_METADATA_DIFF was comparing two locally partitioned indexes
with different partitions or subpartitions. There is no SQL ALTER statement to add
or drop a partition or subpartition of a locally partitioned index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39290: Cannot drop a partition of a globally partitioned index.
Cause: DBMS_METADATA_DIFF was comparing two globally partitioned
indexes and a partition in the first index does not exist in the second index. There
is no SQL ALTER statement to drop a partition of a globally partitioned index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39291: Cannot alter index storage option: string
Cause: DBMS_METADATA_DIFF was comparing two indexes with different
values for the specified storage option. There is no SQL ALTER statement to
change this storage option.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39292: Cannot alter join table of bitmap join index.
Cause: DBMS_METADATA_DIFF was comparing two bitmap join indexes with
different join tables. There is no SQL ALTER statement to alter the join tables of a
bitmap join index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39293: Cannot alter join condition of bitmap join index.
Cause: DBMS_METADATA_DIFF was comparing two bitmap join indexes with
different join conditions. There is no SQL ALTER statement to alter the join
condition of a bitmap join index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39294: Cannot alter indextype of domain index.
Cause: DBMS_METADATA_DIFF was comparing two bitmap domain indexes
with different indextypes. There is no SQL ALTER statement to alter the indextype
of a domain index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39295: Cannot alter index base cluster.
Cause: DBMS_METADATA_DIFF was comparing two cluster indexes defined on
different clusters. There is no SQL ALTER statement to change the base cluster of a
cluster index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39296: Cannot alter index partitioning type or partitioning columns.
Cause: DBMS_METADATA_DIFF was comparing two indexes with incompatible
partitioning: (1) one is partitioned and one is not (2) both are partitioned but in
21-72 Oracle Database Error Messages
different ways (locally vs. globally, hash vs. range) (3) both are partitioned but on
different columns. There is no SQL ALTER statement to change the way an index
is partitioned.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39297: Cannot alter materialized view attribute: string
Cause: DBMS_METADATA_DIFF was comparing two materialized views with
incompatible attributes. There is no SQL ALTER statement to change this attribute
of a materialized view.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39298: Cannot alter materialized view partitioning type or partitioning
columns.
Cause: DBMS_METADATA_DIFF was comparing two materialized views with
incompatible partitioning: (1) one is partitioned and one is not (2) both are
partitioned but in different ways (locally vs. globally, hash vs. range) (3) both are
partitioned but on different columns. There is no SQL ALTER statement to change
the way a materialized view is partitioned.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39299: Cannot alter materialized view physical organization.
Cause: DBMS_METADATA_DIFF was comparing two materialized views with
different physical organizations: heap, index organized, etc. There is no SQL
ALTER statement to change the index organization of a materialized view.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39300: Cannot alter materialized view log partitioning type or partitioning
columns.
Cause: DBMS_METADATA_DIFF was comparing two materialized view logs
with incompatible partitioning: (1) one is partitioned and one is not (2) both are
partitioned but in different ways (locally vs. globally, hash vs. range) (3) both are
partitioned but on different columns. There is no SQL ALTER statement to change
the way a materialized view log is partitioned.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39301: Cannot alter values recorded in materialized view log: string
Cause: DBMS_METADATA_DIFF was comparing two materialized view logs that
are recording different values, and the set of values in the first materialized view
log cannot be changed to that in the second materialized view log. The error
message identifies the specific problem.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39302: Cannot alter tablespace of materialized view log.
Cause: DBMS_METADATA_DIFF was comparing two materialized view logs
which have different tablespaces. There is no SQL ALTER statement to change the
tablespace of a materialized view log.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39303: Cannot alter attribute of queue: string
Cause: DBMS_METADATA_DIFF was comparing two advanced queues with
attribute differences that cannot be reconciled. The error message identifies the
specific problem.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-38029 to ORA-39965 21-73
ORA-39304: Cannot alter attribute of queue table: string
Cause: DBMS_METADATA_DIFF was comparing two AQ queue tabless with
attribute differences that cannot be reconciled. The error message identifies the
specific problem.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39305: Cannot alter attribute of sequence: string
Cause: DBMS_METADATA_DIFF was comparing two sequences with attribute
differences that cannot be reconciled. The error message identifies the specific
problem.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39306: Cannot alter attribute of trigger: string
Cause: DBMS_METADATA_DIFF was comparing two triggers with differences
that cannot be reconciled. The error message identifies the specific problem.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39307: Cannot alter attribute of type: string
Cause: DBMS_METADATA_DIFF was comparing two types with differences that
cannot be reconciled. The error message identifies the specific problem.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39308: Cannot alter attribute of view: string
Cause: DBMS_METADATA_DIFF was comparing two views with differences that
cannot be reconciled. The error message identifies the specific problem.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39309: Cannot alter tablespace between bigfile and smallfile.
Cause: DBMS_METADATA_DIFF was comparing two tablespaces, one bigfile,
one smallfile. There is no SQL ALTER statement to change a tablespace from
smallfile to bigfile or vice versa.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39310: Cannot alter tablespace type.
Cause: DBMS_METADATA_DIFF was comparing two tablespaces of different
types: permanent, temporary or undo. There is no SQL ALTER statement to
change the type of a tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39311: Cannot alter tablespace blocksize.
Cause: DBMS_METADATA_DIFF was comparing two tablespaces with different
blocksizes. There is no SQL ALTER statement to change the blocksize of a
tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39312: Cannot alter tablespace encryption.
Cause: DBMS_METADATA_DIFF was comparing two tablespaces, one
encrypted, one not. There is no SQL ALTER statement to change the encryption
property of a tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39313: Cannot alter tablespace flashback mode.
21-74 Oracle Database Error Messages
Cause: DBMS_METADATA_DIFF was comparing two tablespaces, one in
flashback mode, one not. There is no SQL ALTER statement to alter the flashback
mode of a tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39314: Cannot alter tablespace extent_management.
Cause: DBMS_METADATA_DIFF was comparing two tablespaces with different
extent management properties. There is no SQL ALTER statement to alter the
extent management properties of a tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39315: Cannot drop the first data file from a permanent or undo tablespace.
Cause: DBMS_METADATA_DIFF was comparing two permanent or undo
tablespaces. The first data file in the first tablespace is missing from the second
tablespace. There is no SQL ALTER statement to drop the first data file from a
permanent or undo tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39316: Cannot resize a data file in a smallfile tablespace.
Cause: DBMS_METADATA_DIFF was comparing two smallfile tablespaces. A
data file in the first tablespace is of a different size from the corresponding data file
in the second tablespace. There is no SQL ALTER statement to resize a data file in
a smallfile tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39317: Cannot change the segment space management of a tablespace.
Cause: DBMS_METADATA_DIFF was comparing two tablespaces with different
segment space management. There is no SQL ALTER statement to change the
segment space management of a tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39318: Cannot alter user name.
Cause: DBMS_METADATA_DIFF was comparing two users with different names.
There is no SQL ALTER statement to change the name of a user.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39319: Cannot undo password expiration.
Cause: DBMS_METADATA_DIFF was comparing two users and the first user had
an expired password. There is no SQL ALTER statement to undo the expiration of
a user password.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39320: Column names do not match between export and import databases.
Cause: The column names of the table being imported did not match the column
names of the preexisting table.
Action: Ensure the column names match between export and import database.
ORA-39321: Cannot alter functional index or virtual expression column: string
Cause: Altered column was referenced in a virtual column or functional index
expression. There is no SQL ALTER statement to change a column which is
referenced in one of these types of expressions.
Action: The difference cannot be eliminated with a SQL ALTER statement.
ORA-38029 to ORA-39965 21-75
ORA-39322: Cannot use transportable tablespace with TIMESTAMP WITH TIME
ZONE columns and different time zone version.
Cause: The source database was at a different time zone version than the target
database and there were tables in the dumpfile with TIMESTAMP WITH TIME
ZONE columns.
Action: Convert the target database to the same timezone version as the source
database or use Data Pump without transportable tablespace.
ORA-39323: cannot load data from external table dump file "string"
Cause: A dump file was specified for an import operation that had been created
with external tables using the ORACLE_DATAPUMP access driver. This type of
dump file cannot be processed using the Data Pump import utility.
Action: Access the data in this dump file with external tables using the ORACLE_
DATAPUMP access driver.
ORA-39324: cannot load data from Data Pump dump file "string"
Cause: A dump file was specified for a load operation that had been created using
the Data Pump. This type of dump file cannot be processed by external tables
using the ORACLE_DATAPUMP access driver.
Action: Access the data in this dump file using the Data Pump.
ORA-39325: TABLE_EXISTS_ACTION cannot be applied to string.
Cause: An object was already in existence that uses a name in common with this
table. The name collision could be the table name, a constraint, a LOB storage
table, or something else in the table definition.
Action: Drop the existing object before running Data Pump.
ORA-39326: cannot load data into table, string, due to an unusable index
Cause: An unusable index existed on the table. This index prevented data from
being loaded into the table associated with this index.
Action: Either drop the unusable index or make it valid before attempting the
import operation.
ORA-39327: Oracle Database Vault data is being stored unencrypted in dump file
set.
Cause: No encryption was specified for an export job that involved data from an
Oracle Database Vault realm.
Action: No specific user action is required. This is only a warning that secure data
may be readable from within the dump file set.
ORA-39328: encryption password is too long
Cause: The encryption password provided to the Data Pump job was invalid
because its length was greater than the maximum allowed. When using the
password to encrypt the dump file set, the maximum length is 1000 bytes. When
using the password to re-encrypt encrypted columns only, the maximum length is
30 bytes.
Action: Retry the operation with a valid encryption password.
ORA-39329: Tablespace string needs to be locally managed.
Cause: An attempt was made to run an Oracle Data Pump job with the
TRANSPORTABLE=ALWAYS parameter. Tablespaces that contain data for
EARLY_OPTIONS in an Oracle Data Pump job run with FULL=Y and
TRANSPORTABLE=ALWAYS parameter need to be locally managed.
21-76 Oracle Database Error Messages
Action: Run the Oracle Data Pump job without the TRANSPORTABLE parameter
set to ALWAYS.
ORA-39331: Wallet is not open on remote node.
Cause: The security module wallet was not open on the remote node.
Action: Open the wallet on the remote node.
ORA-39339: Table string was skipped due to transportable import and TSTZ issues
resulting from time zone version mismatch.
Cause: The source database is at a different time zone version than the target
database and this table contains TIMESTAMP WITH TIME ZONE data.
Action: Convert the target database to the same time zone version as the source
database or use Oracle Data Pump with conventional data movement to export
then import this table.
ORA-39340: unsupported object, string will be skipped.
Cause: Oracle Data Pump encountered an object type that it currently does not
support.
Action: Manually move the object to the target database.
ORA-39341: Cannot convert an existing column into an identity column.
Cause: An attempt was made to convert an existing column into an identity
column. There is no SQL ALTER statement that will convert an existing column
into an identity column.
Action: The difference cannot be eliminated with a SQL ALTER statement.
ORA-39342: Internal error - failed to import internal objects tagged with string due
to string.
Cause: Oracle Data Pump encountered an internal tagged object that failed to
import properly. All other objects with the same tag will be skipped.
Action: Contact Oracle Support Services.
ORA-39343: Object type string failed to create returning error: string
Cause: The object type could not be created. Examine the original error code to
determine the actual cause.
Action: The original error code will contain more information.
ORA-39345: WARNING: possible data loss in character set conversions
Cause: Oracle Data Pump displayed this message at the start of the import
operation because it determined that the character set or the NCHAR character set
used by the export database was different from that of the target database and also
that the target database character set was not a superset of the export database
character set.
Action: No specific user action is required.
ORA-39346: data loss in character set conversion for object string
Cause: Oracle Data Pump import converted a metadata object from the export
database character set into the target database character set prior to processing the
object. Some characters could not be converted to the target database character set
and so the default replacement character was used.
Action: No specific user action is required. This type of data loss can occur if the
target database character set is not a superset of the export databases character set.
ORA-38029 to ORA-39965 21-77
ORA-39347: Character data loss was detected during conversion, the row was
rejected.
Cause: The row contained characters that did not exist in the destination character
set.
Action: No specific user action is required. The destination character set must be a
superset of the source character set to avoid data loss.
ORA-39352: Wrong number of TRANSPORT_DATAFILES specified: expected
string, received string
Cause: The number of TRANSPORT_DATAFILES specified on the impdp
command was not correct.
Action: Specify the correct TRANSPORT_DATAFILES for this transportable job.
ORA-39353: Data was not imported for string. Cannot locate the time zone version
string file.
Cause: This table contains TIMESTAMP WITH TIME ZONE data and Oracle Data
Pump needed to load the source version of the time zone file. This version cannot
be located.
Action: Install the latest time zone version files.
ORA-39357: WARNING: Oracle Data Pump operations are not typically needed
when connected to the root or seed of a container database.
Cause: The Oracle Data Pump client was attached to the root or seed container
database.
Action: Continue if this is the desired connection string or attach to a pluggable
database within the container database.
ORA-39358: Export dump file version string not compatible with target version
string
Cause: The Oracle Data Pump export job version was newer than the target
compatibility version.
Action: Upgrade the target database to a compatibility level of at least the export
job version, or rerun the export job with a job version that is lower than or equal to
the compatibility version of the target database.
ORA-39359: Source time zone version is string and target time zone version is
string.
Cause: The time zone version of the source database is not the same as the time
zone version of the target database.
Action: Tables containing TIMESTAMP WITH TIME ZONE data cannot be
imported with transportable tablespace technology when time zone versions are
different between the export and target databases. All affected tables will be
reported during the import job and will not be created. If any are reported, convert
the target database to the same time zone version as the source or use Oracle Data
Pump with conventional data movement to export then import the affected tables.
ORA-39360: Table string was skipped due to transportable import and TSLTZ
issues resulting from time zone mismatch.
Cause: The time zone of the source database is different than the time zone of the
target database and this table contains TIMESTAMP WITH LOCAL TIME ZONE
data.
21-78 Oracle Database Error Messages
Action: Convert the target database to the same time zone as the source database
or use Oracle Data Pump with conventional data movement to export then import
this table.
ORA-39361: Source time zone is string and target time zone is string.
Cause: The time zone of the source database is different than the time zone of the
target database.
Action: Tables containing TIMESTAMP WITH LOCAL TIME ZONE data cannot
be imported with transportable tablespace technology when time zones are
different between the export and target databases. All affected tables will be
reported during the import job and will not be created. If any are reported, convert
the target database to the same time zone as the source or use Oracle Data Pump
with conventional data movement to export then import the affected tables.
ORA-39363: Type evolution could not be preserved for string
Cause: Trying to apply each version of the type during import resulted in
compilation warnings. The type was successfully recreated to the latest version
only.
Action: Export dump files as well as transportable tablespaces that contain earlier
versions of this type cannot be imported on top of this type definition.
ORA-39364: encryption password is too long
Cause: The encryption password provided to the Oracle Data Pump job was
invalid because its length was greater than the maximum allowed. When using the
password to encrypt the dump file set, the maximum length is 128 bytes. When
using the password to re-encrypt encrypted columns only, the maximum length is
30 bytes.
Action: Retry the operation with a valid encryption password.
ORA-39365: supplemental log data could not be generated for string
Cause: The instance was unable to generate supplemental log data when Data
Pump was importing the table. Supplemental logging is not supported for Data
Pump import of tables containing columns of user-defined types.
Action: No action is required for replication using Oracle GoldenGate. For logical
standby users, perform a separate import of this table into the standby database.
ORA-39366: disable table lock on string.string failed with: string
Cause: Examine the original error code to determine the actual cause.
Action: The original error code contains more information.
ORA-39367: Statistcis are being skipped. Cannot locate the time zone version string
file.
Cause: Importing statistics requires that the Oracle Data Pump load the source
version of the time zone file. This version cannot be located.
Action: Install the latest time zone version files.
ORA-39368: cannot alter partition varray column properties
Cause: DBMS_METADATA_DIFF was comparing two partitioned tables. There is
no SQL ALTER statement to change varray column properties.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39369: some rows may not be exported for string due to block corruption
ORA-38029 to ORA-39965 21-79
Cause: The corrupted data blocks were ignored when Oracle Data Pump was
exporting the table.
Action: No action is required.
ORA-39370: remap value string is too long
Cause: The remap value provided to the Oracle Data Pump job was invalid
because its length was greater than the maximum allowed.
Action: Retry the operation with a valid remap value.
ORA-39371: cannot specify partition in remap_table without departitioning
Cause: The 'remap_table' value specified a partition but the tables were not being
departitioned.
Action: Either remove the partition name in the 'remap_table' parameter or add
the 'partition_options=departition' parameter.
ORA-39500: failed to notify CRS of a Startup/Shutdown event for database "string",
instance "string" (ignored)
Cause: The instance was unable to obtain the context or information required to
notify the CRS framework.
Action: None Required. The error is ignored.
ORA-39501: failed to notify CRS of a Startup/Shutdown event [string] (ignored)
Cause: The instance was unable to communicate with the CRS framework.
Action: None Required. The error is ignored.
ORA-39502: failed to notify CRS of a Startup/Shutdown event [string] (ignored)
Cause: The instance was unable to create an environment context.
Action: None Required. The error is ignored.
ORA-39503: failed to notify CRS of a Startup/Shutdown event [string] (ignored)
Cause: The instance was unable to populate the environment context.
Action: None Required. The error is ignored.
ORA-39504: failed to notify CRS of a Startup/Shutdown event [string] (ignored)
Cause: The instance was unable to find the location of the alert file.
Action: None Required. The error is ignored.
ORA-39510: CRS error performing string on string 'string' on 'string' string
Cause: Unable to perform action on associated CRS resource.
Action: See following error messages for additional information. Fix error and
retry.
ORA-39600: Queue keys needs to be a suffix of cluster key.
Cause: Attempt to specify queue key columns that don't form a suffix of the
cluster key.
Action: Only specify queue key columns as a suffix of cluster key.
ORA-39601: Hash key is required.
Cause: Missing hash key in the cluster key specification.
Action: Specify one or more hash key columns.
ORA-39700: database must be opened with UPGRADE option
21-80 Oracle Database Error Messages
Cause: A normal database open was attempted, but the database has not been
upgraded to the current server version.
Action: Use the UPGRADE option when opening the database to run
catupgrd.sql (for database upgrade), or to run catalog.sql and catproc.sql (after
initial database creation).
ORA-39701: database must be mounted EXCLUSIVE for UPGRADE or
DOWNGRADE
Cause: The database was mounted for SHARED cluster access.
Action: Set the CLUSTER_DATABASE initialization parameter to FALSE and
restart the server with the UPGRADE or DOWNGRADE option.
ORA-39702: database not open for UPGRADE or DOWNGRADE
Cause: An upgrade, downgrade, reload, or patch script was invoked when the
database was not open for UPGRADE or DOWNGRADE.
Action: Use STARTUP UPGRADE to open the database for upgrade or to apply a
patch set. Use STARTUP DOWNGRADE for running a downgrade script or the
reload script.
ORA-39703: server version and script version do not match
Cause: An upgrade, downgrade, reload, or patch script was invoked, but the
database instance version was not the version for which the script was intended.
Action: Check that the correct ORACLE_HOME and ORACLE_SID environment
variables are set. Also check that the SQL script is being invoked from the correct
ORACLE_HOME.
ORA-39704: permission to modify component registry entry denied
Cause: An attempt was made to modify an entry in the component registry, but
the session user was not authorized; only the CONTROL or SCHEMA user for the
component are authorized to modify the component registry entry.
Action: Connect as either the CONTROL or SCHEMA user for the component.
ORA-39705: component 'string' not found in registry
Cause: No entry in the component registry was found for the specfied
component.
Action: Check the spelling of the component ID and use the DBA_REGISTRY
view to list the existing components.
ORA-39706: schema 'string' not found
Cause: The schema name specified was not found in the database.
Action: Create the schema before loading the component.
ORA-39707: compatibile parameter string too high for downgrade to string
Cause: A downgrade was attempted, but the compatible initialization parameter
value was greater than the downgrade release version.
Action: Once the compatible value has been raised, downgrade to earlier releases
is not supported.
ORA-39708: component 'string' not a string component
Cause: The component was not a component for the specified namespace.
Action: Either enter a valid component identifier for the namespace or set the
session namespace to the correct component namespace.
ORA-38029 to ORA-39965 21-81
ORA-39709: incomplete component downgrade; string downgrade aborted
Cause: One or more components did not have a status of DOWNGRADED.
Action: Correct the component problem and re-run the downgrade script.
ORA-39710: only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
Cause: An attempt was made to connect to a database when the database was
OPEN for UPGRADE or DOWNGRADE.
Action: Try to connect again after the database upgrade or downgrade is
complete.
ORA-39711: critical patch number less than last installed CPU number
Cause: A Critical Patch Update (CPU) script was invoked that had a number that
was less than the last CPU installed in the database.
Action: Check the DBA_REGISTRY_HISTORY view to identify the last CPU for
the database, and install the most recent CPU.
ORA-39712: XE edition server cannot open database
Cause: An attempt was made to open a Standard Edition or Enterprise Edition
database with the Express Edition of the server.
Action: Use the Express Edition server only with Express Edition databases.
ORA-39714: upgrade script utlmmig.sql failed
Cause: A normal database open was attempted, but the upgrade script
utlmmig.sql failed to complete.
Action: Use the UPGRADE option when opening the database and then run
utlmmig.sql.
ORA-39715: Downgrade script UTLMMIGDOWN.SQL failed.
Cause: A normal database open was attempted, but the downgrade script
UTLMMIGDOWN.SQL failed to complete.
Action: Use the DOWNGRADE option when opening the database and then run
UTLMMIGDOWN.SQL.
ORA-39726: unsupported add/drop column operation on compressed tables
Cause: An unsupported add/drop column operation for compressed table was
attemped.
Action: When adding a column, do not specify a default value. DROP column is
only supported in the form of SET UNUSED column (meta-data drop column).
ORA-39727: COMPATIBLE must be set to 10.0.0.0.0 or higher
Cause: An add/drop column operation for compressed table has been performed
on the database. This requires COMPATIBLE to be set to 10.0.0.0.0 or higher
during upgrade from 9.2 to a 10i or higher release.
Action: Set COMPATIBLE to 10.0.0.0.0 and retry the upgrade.
ORA-39751: partitioned table on both sides of PARTITIONED OUTER JOIN is not
supported
Cause: An attempt was made to partition both sides of PARTITIONED OUTER
JOIN.
Action: Specify partitioned table on one side of PARTITIONED OUTER JOIN
only.
21-82 Oracle Database Error Messages
ORA-39752: redundant column in partitioning and join columns is not allowed
Cause: An attempt was made to specify redundant columns in partitioning and
join columns for NATURAL or named column PARTITIONED OUTER JOIN.
Action: Do not specify redundant column in partitioning and join columns.
ORA-39753: unsupported use of subquery in PARTITIONED OUTER JOIN
condition
Cause: An attempt was made to use subquery in PARTITIONED OUTER JOIN
condition.
Action: Remove subquery from the join condition.
ORA-39754: FULL PARTITIONED OUTER JOIN is not supported
Cause: An attempt was made to use FULL PARTITIONED OUTER JOIN.
Action: Specify FULL PARTITIONED OUTER JOIN through UNION of LEFT and
RIGHT PARITTION OUTER JOIN.
ORA-39755: cannot use PARTITIONED OUTER JOIN with a left correlation
Cause: An attempt was made to use a PARTITIONED OUTER JOIN where the
right side is a lateral view with a left correlation to the left side and is partitioned.
Action: Rewrite the query without the left correlation.
ORA-39761: stream reset required before loading this stream again
Cause: An attempt was made to load a stream that was previously loaded but has
not been reset yet.
Action: Reset the specified stream and convert column array data to it before
attempting to load it again.
ORA-39762: streams must be loaded in conversion order
Cause: An attempt was made to load a stream out of conversion order.
Action: Load streams in the same order they were converted.
ORA-39763: stream must be completely loaded before it is reset
Cause: An attempt was made to reset a stream that contains converted column
array data and hasn't been completely loaded yet.
Action: Before resetting a stream, load it until a status of OCI_SUCCESS, OCI_
NO_DATA, or OCI_NEED_DATA is returned.
ORA-39764: specified stream is not in the specified direct path context
Cause: A direct path operation was attempted using a stream that was not created
in the specfied direct path context.
Action: Only use streams created in the specified direct path context.
ORA-39765: stream must be reset before used in a column array conversion
Cause: The stream was completely loaded, but has not been reset yet.
Action: Reset loaded streams after load returns OCI_SUCCESS, OCI_NO_DATA,
or OCI_NEED_DATA. The stream can then be used in a column array to stream
conversion.
ORA-39766: invaid stream specified for column array conversion
Cause: A stream must be loaded and reset before used again in a
column-array-to-stream conversion. This error is issued if another stream has
ORA-38029 to ORA-39965 21-83
subsequently been converted before the specified stream has been loaded, or if the
latest load of this stream returned OCI_ERROR.
Action: Don't convert into a previous stream before it is loaded. Also, when load
stream returns OCI_ERROR, the stream must be loaded again to insure any
remaining information in the stream is loaded. The stream must be loaded even if
the last or only row was in error. There may be error information in the stream that
needs to be sent to the server.
ORA-39767: finish is not allowed when unloaded stream data exists
Cause: A direct path finish was attempted when at least one stream buffer has not
been completely loaded.
Action: All streams must be loaded after a column array to stream conversion
until load stream returns a status of OCI_SUCCESS or OCI_NO_DATA. The load
can then be finished.
ORA-39768: only one direct path context top level column array is allowed
Cause: Attempt to create multiple top level column arrays in a direct path context,
when only one is allowed.
Action: Create another direct path context if additional top level column arrays
are required.
ORA-39769: finish is not allowed with an incompletely loaded last row
Cause: Part of a row has been loaded, but it is not complete.
Action: Finish loading the current row when load stream returns OCI_ERROR or
OCI_NEED_DATA.
ORA-39771: stream must be loaded before its handle is freed
Cause: An attempt was made to free a stream handle after conversion but before
the stream was loaded.
Action: Load the stream until OCI_SUCCESS, OCI_NEED_DATA or OCI_NO_
DATA is returned before attempting to free the stream handle. If OCI_NEED_
DATA is returned, another stream must be loaded to complete last row.
ORA-39772: column array reset disallowed after OCI_CONTINUE or OCI_NEED_
DATA
Cause: An attempt was made to reset a column array when a row conversion is
still in progress.
Action: Complete the current row before reseting the column array. To ignore the
current row when conversion returned OCI_NEED_DATA, set the current column
flag to OCI_DIRPATH_COL_ERROR. This should be followed by a conversion,
which will undo and ignore the row. The column array(s) can then be reset.
ORA-39773: parse of metadata stream failed
Cause: An unexpected error occured while attempting to parse the metadata //
stream for a table being loaded.
Action: Call Oracle support.
ORA-39774: parse of metadata stream failed with the following error: string
Cause: An unexpected error occured while parsing the metadata stream.
Action: See the secondary error for more information.
ORA-39775: direct path API commit not allowed due to previous fatal error
Cause: An attempt was made to commit a Direct Path context after a fatal error.
21-84 Oracle Database Error Messages
Action: Correct the error and retry.
ORA-39776: fatal Direct Path API error loading table string
Cause: A fatal error was detected loading the specified or previous table.
Action: Correct the error and retry.
ORA-39777: data saves are not allowed when loading lob columns
Cause: An attempt was made to save data when loading lob columns or columns
stored as lobs (such as varrays and xml types).
Action: Do not attempt to do a data save or partial save when loading lob
columns. A finish save is allowed.
ORA-39778: the parallel load option is not allowed when loading lob columns
Cause: An attempt was made to load lob columns using the attribute OCI_ATTR_
DIRPATH_PARALLEL. This error will also be issued when loading any columns
that are stored as lobs (such as varrays and xml types).
Action: Do not use the parallel attribute when loading lob columns.
ORA-39779: type "string"."string" not found or conversion to latest version is not
possible
Cause: Unable to import table data using the specified type. The type was
nonexistent in the database or the input type could not be converted to the existing
type. The reasons why a conversion was not possible are:
1. The version of the type in the database was greater than the version of the type
at export time because 1 or more attributes have been added or dropped from the
type.
2. If the type existed in the database prior to the import operation, then its internal
identifier may not match the internal identifier of the type from the export
database. The identifiers must match for an import to succeed.
Action: Ensure the types in the database match those at export time.
ORA-39780: Direct path context operations are not allowed after the context is
aborted or finished
Cause: The specified direct path context was aborted or finished.
Action: Do not pass a direct path context that has ended to any direct path
functions.
ORA-39781: Direct path stream loads are not allowed after another context loading
the same table has ended
Cause: Attempt to load a stream in one context after another loading the same
table has ended.
Action: Close all contexts before trying to create another that loads the same table
as a previous context in the same session.
ORA-39782: Direct path prepare is not allowed after another context loading the
same table has ended
Cause: Direct path prepare called after a context loading the same table has
ended.
Action: Close all contexts before trying to create another that loads the same table
as a previous context in the same session.
ORA-39783: Invalid direct path transaction active
ORA-38029 to ORA-39965 21-85
Cause: Direct path operations were not performed in the transaction started by
the first OCIDirPathPrepare call.
Action: Ensure the correct transaction is active prior to calling Direct Path API
operations.
ORA-39784: This direct path operation is not allowed while another is in progress
Cause: Another direct path operation was active.
Action: Complete any direct path operations in progress before attempting this
operation.
ORA-39785: SQL expressions returning ADT objects are not allowed in direct path
Cause: The passed SQL expression returned a user-defined ADT which was not
supported.
Action: Remove the SQL expression.
ORA-39786: Number of columns does not match between export and import
databases
Cause: External tables could not import into a table with mismatched columns.
Action: Ensure the number of columns matches between export and import
database.
ORA-39787: Column string subtype "string"."string" is not instantiable.
Cause: Subtype specified was not instantiable.
Action: Ensure all subtypes specified are instantiable.
ORA-39788: Subtype "string"."string" is specified multiple times for column string.
Cause: Subtype specified was not unique.
Action: Ensure all subtypes specified are unique.
ORA-39789: "string"."string" is not a valid type for column string.
Cause: Subtype specified was not a valid type for the column being loaded.
Action: Ensure all subtypes specified are valid types for the column being loaded.
ORA-39790: Attribute "string" specified multiple times for column string.
Cause: Attribute specified multiple times.
Action: Ensure all attributes specified are unique.
ORA-39791: Attribute "string" for column string is not in subtype "string"."string".
Cause: Attribute was not included in the subtype indicated.
Action: Ensure the attribute is included in the subtype indicated by the specified
subtype index.
ORA-39792: Attribute "string" is not valid for subtypes(s) loaded into column
string.
Cause: Attribute specified was not included in any subtypes specified for the
column or the declared subtype of the column.
Action: Ensure the attribute is included in at least one of the subtypes loaded into
the column.
ORA-39793: Attribute "string" is not unique within the hierarchy being loaded.
Cause: The attribute was defined in multiple lines of descent in the hierarchy
being loaded.
21-86 Oracle Database Error Messages
Action: When describing the attribute, a subtype index must be specified to
uniquely identify the attibute being loaded.
ORA-39794: No attributes loaded for subtype "string"."string".
Cause: None of the attributes loaded were included in the type shown.
Action: At least one attribute must be loaded for each subtype specified.
ORA-39795: Subtype index is not first attribute for object table or column, string.
Cause: The subtype index was not the first attribute when describing the atributes
of an object column or object table with multiple subtypes.
Action: Describe the subtype index as the first attribute for this object column or
object table.
ORA-39796: column array entry for string is not valid for the current subtype
Cause: This column was not part of the current subtype being loaded for this
object column or table. Therefore, its entry must be null in the column array.
Action: Set the column array entry to null.
ORA-39797: The subtype index value is not valid.
Cause: The subtype index value in the column array was not valid for the object
column or object table.
Action: Set a valid subtype index value in the column array for this table or
column.
ORA-39798: The column array row offset number is out of range (max: number).
Cause: The specified row offset was too large for the column array.
Action: Ensure the row offset is in range.
ORA-39799: The column index number is out of range (max: number).
Cause: The specified column index was too large for the column array.
Action: Ensure the column index is in range.
ORA-39800: Database version number does not support the load of multiple
subtypes.
Cause: Direct Path API support for loading multiple subtypes of an object table or
column was only present in the Oracle 11 release and higher.
Action: Upgrade database to Oracle 11 or higher.
ORA-39801: Subtype "string"."string" is not a valid subtype for column string.
Cause: Subtype specified was not the declared type nor was it derived from the
declared type.
Action: Ensure all subtypes specified are either the declared type or derived from
the declared type.
ORA-39802: ADT object column string specified a SQL expression which is not
allowed in direct path mode.
Cause: The ADT column reported in the error specified a SQL expression which
returned the ADT. This is not supported.
Action: Remove the SQL expression.
ORA-39803: Data saves are not allowed on tables with partitioning referential
constraints.
ORA-38029 to ORA-39965 21-87
Cause: Data saves (and the sqlldr ROWS parameter) are not allowed when
loading both the parent and child tables of a partitioning referential constraint.
Action: Do not attempt data saves when loading both the parent and child tables
of a partitioning referential constraint.
ORA-39804: The load was aborted due to an error loading parent string while also
loading child string.
Cause: An error occurred while loading the child and parent table of a
partitioning referential constraint. The load was aborted to ensure the partitioning
referential constraint was not violated.
Action: Fix the error that caused the load to abort and retry.
ORA-39805: Parallel loads are not allowed when loading child and parent.
Cause: A parallel load was requested when loading the child and parent of a
partitioning referential constraint. This is not allowed.
Action: Remove the parallel option.
ORA-39806: The attempt to lock string parent table string string string failed.
Cause: While loading the child table of a partitioning referential constraint, the
parent table must be locked in SHARE mode.
Action: Determine why the parent table could not be locked and retry.
ORA-39807: Partial data save on child string was ignored.
Cause: An attempt was made to partially save data when loading both the child
and parent of a partitioning referential constraint or when loading a table with a
domain index.
Action: Fix the error that caused the partial load and retry.
ORA-39808: The SINGLEROW option must be specified for parent table string.
Cause: The SINGLEROW option was not specified when loading both the parent
and child table of a partitioning referential constraint.
Action: Ensure the SINGLEROW option is specified for the parent when loading
the parent and child of a partitioning referential constraint.
ORA-39809: Data saves are not allowed on tables with domain indexes.
Cause: Data saves (and the sqlldr ROWS parameter) could not be allowed when
loading a table with domain indexes.
Action: Do not attempt data saves when loading a table with domain indexes.
ORA-39810: Data saves are not allowed when NO_INDEX_ERRORS is specified.
Cause: Data saves (and the sqlldr ROWS parameter) could not be allowed when
loading with the NO_INDEX_ERRORS option.
Action: Do not attempt data saves when loading a table with the NO_INDEX_
ERRORS option.
ORA-39811: index string.string had the following error:
Cause: An error occurred on the index; error follows.
Action: Fix the error and retry.
ORA-39812: index string.string partition string had the following error:
Cause: An error occurred on the index; error follows.
Action: Fix the error and retry.
21-88 Oracle Database Error Messages
ORA-39813: index string.string had string partition errors:
Cause: A logical index error occurred on a partitioned index which affected one or
more index partitions, which are listed below this message.
Action: Fix the error(s) and retry.
ORA-39814: The SKIP_INDEX_MAINTENANCE option is not allowed with NO_
INDEX_ERRORS.
Cause: The SKIP_INDEX_MAINTENANCE option was used with the NO_
INDEX_ERRORS option.
Action: Do not use SKIP_INDEX_MAINTENANCE with NO_INDEX_ERRORS.
ORA-39815: Direct Path Unload of an external table is not allowed.
Cause: An attempt was made to use Direct Path API Unload to unload an external
table.
Action: Do not use Direct Path Unload to unload an external table.
ORA-39816: Direct Path Unload of tables with encrypted column(string.string) is
not allowed.
Cause: An attempt was made to use Direct Path API Unload to unload a table
with encrypted columns.
Action: Do not use Direct Path Unload to unload a table with encrypted columns.
ORA-39817: index string.string was ignored due to:
Cause: Index was unusable at the start of the load and it was requested that
unusable indexes be skipped.
Action: No action required.
ORA-39818: index string.string partition string was ignored due to:
Cause: Index was unusable at the start of the load and it was requested that
unusable indexes be skipped.
Action: No action required.
ORA-39819: The OCI_ATTR_DIRPATH_NO_INDEX_ERRORS attribute cannot be
set to TRUE in direct path parallel loads.
Cause: An attempt was made to set the OCI_ATTR_DIRPATH_NO_INDEX_
ERRORS attribute to TRUE in a direct path parallel load.
Action: Do not set the OCI_ATTR_DIRPATH_NO_INDEX_ERRORS to TRUE for
direct path parallel loads.
ORA-39820: Zero length LONG piece detected for column string row string.
Cause: A zero length piece was detected for a LONG column.
Action: Do not use a length of zero when loading LONG columns.
ORA-39821: domain index on columnar data made unusable
Cause: An attempt was made to load a columnar table with a domain index using
SQL*Loader direct part load
Action: None
ORA-39822: A new direct path operation is not allowed in the current transaction.
Cause: All previous direct path contexts ended and the current transaction was
ready for a commit or abort of those changes.
ORA-38029 to ORA-39965 21-89
Action: Commit or abort the current transaction, and start a new transaction for
the next direct path context.
ORA-39823: The attribute OCI_ATTR_DIRPATH_USE_ACTIVE_TRANS is only
allowed for load operations.
Cause: The attribute OCI_ATTR_DIRPATH_USE_ACTIVE_TRANS was set for a
nonload operation.
Action: Use OCI_ATTR_DIRPATH_USE_ACTIVE_TRANS for load operations
only.
ORA-39824: The OCI_ATTR_DIRPATH_USE_ACTIVE_TRANS attribute was set
when no transaction was active.
Cause: There was no active transaction to use.
Action: Start a transaction or do not set the attribute OCI_ATTR_DIRPATH_USE_
ACTIVE_TRANS to TRUE.
ORA-39825: Direct path load of view or synonym (string.string) with multiple
dependencies not permitted.
Cause: An attempt was made to load a view or synonym which has more than a
single dependency.
Action: A view or synonym being loaded by the direct path API must resolve to a
single object.
ORA-39826: Direct path load of view or synonym (string.string) could not be
resolved.
Cause: A synonym or view could not be translated.
Action: Verify that the view or synonym is valid.
ORA-39827: Direct path load of PL/SQL function not permitted.
Cause: An attempt was made to load a PL/SQL function with the direct path API.
Action: Remove PL/SQL function the direct path load.
ORA-39828: Constraint string was disabled because of index string.string error.
Cause: The index used for the constraint was set as unusable.
Action: Fix the error that caused the index to be set unusable.
ORA-39829: function-based index on columnar data made unusable
Cause: An attempt was made to load a columnar table with a function-based
index using SQL*Loader direct path load.
Action: Rebuild the function-based index after the load completes.
ORA-39830: XML parsing failed string
Cause: XML parser returned an error while trying to parse the document.
Action: Fix the error that caused the document to be invalid.
ORA-39831: Direct path load failed, (string.string) is not a table.
Cause: Object being loaded did not resolve to a table.
Action: Verify that the view or table name is correct.
ORA-39832: Direct path unload was not allowed due to columns with default
values.
21-90 Oracle Database Error Messages
Cause: Direct path unload was attempted on a table with columns that have
default values.
Action: Do not attempt a direct path unload of a table with columns that have
default values.
ORA-39833: Direct path parallel load was not allowed on a temporary table.
Cause: A direct path parallel load was attempted on a temporary table.
Action: Do not attempt a direct path parallel load on a temporary table.
ORA-39834: Direct path load or unload was not allowed on a remote table.
Cause: An attempt was made to specify a remote table in a direct path API load or
unload.
Action: Do not specify a remote table in a direct path API load or unload.
ORA-39835: Direct path load partition memory exceeded. PGA use is stringkb, PGA
limit is: stringkb
Cause: A direct path load ran out of process memory when loading multiple
partitions.
Action: Use the PARTITION_MEMORY parameter to limit memory used when
loading many partitions. Once this limit is reached, loading of some partition rows
will be delayed until memory use falls below the limit. Use a value (kb) lower than
the current program global area (PGA) limit included in this message and try the
load again.
ORA-39861: auxiliary data file copy file for Pluggable Database string: "string"
Cause: This message reports the filename for details of another message.
Action: Other messages will accompany this message. See the associated
messages for the appropriate action to take.
ORA-39862: RESETLOGS option only valid after a Pluggable Database incomplete
recovery
Cause: The ALTER PLUGGABLE DATABASE OPEN RESETLOGS command was
issued, but the Pluggable Database was not flashed back or point-in-time
recovered.
Action: Retry the ALTER PLUGGABLE DATABASE OPEN command without
specifying RESETLOGS.
ORA-39863: An earlier Pluggable Database incomplete recovery failed.
Cause: An earlier Pluggable Database flashback or point-in-time recovery failed.
Action: Retry the Pluggable Database flashback or incomplete recovery.
ORA-39865: cannot FLASHBACK beyond Pluggable Database resetlogs operation
Cause: An attempt was made to perform a FLASHBACK DATABASE beyond a
Pluggable Database resetlogs system change number (SCN).
Action: Choose a FLASHBACK SCN that is more recent than the Pluggable
Database resetlogs SCN.
ORA-39866: Data files for Pluggable Database string must be offline to flashback
across PDB point-in-time recovery.
Cause: An attempt was made to perform a FLASHBACK DATABASE beyond a
Pluggable Database (PDB) resetlogs system change number (SCN) while data files
for the Pluggable Database are still online.
ORA-38029 to ORA-39965 21-91
Action: Take the data files for the Pluggable Database (PDB) offline before
performing the FLASHBACK DATABASE command. To bring the PDB to the
same past point in time as the container database (CDB), those data files can be
restored from backups and recovered to that same past point in time. This can be
done in one of two ways:
* Flashback the CDB and open the CDB with resetlogs. Restore the PDB later, and
perform a complete PDB recovery.
* Flashback the CDB first. Restore and recover the PDB to the same system change
number (SCN). Open CDB with resetlogs.
ORA-39870: container database is not open in read/write mode
Cause: A command was attempted that requires the container database (CDB) to
be open in read/write mode.
Action: Open the container database in read/write mode and try the command
again.
ORA-39871: An earlier Pluggable Database resetlogs operation failed after making
changes.
Cause: An earlier ALTER PLUGGABLE DATABASE OPEN RESETLOGS
command failed after it made some changes.
Action: Perform another Pluggable Database point-in-time recovery before
attempting to open the Pluggable Database with RESETLOGS.
ORA-39872: Data file number is in the middle of Pluggable Database resetlogs
operation.
Cause: The data file was in the middle of a Pluggable Database resetlogs
operation.
Action: Find the right file version or perform more media recovery. For additional
information, see other errors.
ORA-39873: Restore all data files to a checkpoint SCN lower than string.
Cause: This error provides additional information for error 39874.
Action: Restore the data files as suggested and restart the recovery process.
ORA-39874: Pluggable Database string recovery halted
Cause: The Pluggable Database was recovered into an orphan branch.
Action: Restore all data files to a checkpoint system change number (SCN) lower
than the branch point and restart the recovery process. Check the alert log for
additional information.
ORA-39875: Data file string is in the middle of Pluggable Database resetlogs
operation.
Cause: The data file is in the middle of a Pluggable Database (PDB) resetlogs
operation.
Action: If possible, recover the data file further so that it is not in the middle of a
PDB resetlogs operation. Another alternative is to perform PDB point-in-time
recovery.
ORA-39876: cannot perform CDB OPEN RESETLOGS because data file string is in
the middle of a PDB resetlogs operation
Cause: The data file mentioned was in the middle of a Pluggable Database (PDB)
resetlogs operation.
21-92 Oracle Database Error Messages
Action: Recover the container database (CDB) to a different system change
number (SCN) at which the data files are not in the middle of a PDB resetlogs
operation. Alternatively, you can offline the problematic data file and let CDB
OPEN RESETLOGS succeed. You may need to perform PDB point-in-time
recovery later in order to open the PDB of the offlined data file.
ORA-39877: keyword ONLINE or OFFLINE expected
Cause: The ONLINE or OFFLINE keyword was not specified after the ALL
keyword.
Action: Use the correct syntax.
ORA-39878: Only one Pluggable Database name can be specified.
Cause: Multiple Pluggable Database names were specified for the ALTER
PLUGGABLE DATABASE OPEN RESETLOGS command.
Action: Specify only one Pluggable Database name.
ORA-39879: Pluggable Database string is in the middle of a Pluggable Database
RESETLOGS operation
Cause: There was already an on-going Pluggable Database OPEN RESETLOGS
operation for this Pluggable Database.
Action: If needed, retry after the Pluggable Database OPEN RESETLOGS
operation completes.
ORA-39880: One or more pluggable databases were in the middle of a point-in-time
recovery at this incomplete database recovery SCN.
Cause: In the past, one or more pluggable databases had an active pluggable
database RESETLOGS operation as of this incomplete recovery SCN.
Action: Additional messages are logged in the alert log indicating all of the
pluggable databases affected by this container database OPEN RESETLOGS
operation. Recover the container database to a different system change number
(SCN) at which none of the pluggable databases had an active RESETLOGS
operation. To continue the container database OPEN RESETLOGS operation at the
same SCN, offline all of the data files of the affected pluggable databases first and
reissue the command. However, a new point-in-time recovery of the affected
pluggable databases would be required before these databases can be opened
again.
ORA-39881: Pluggable database string must be closed while recovering the physical
standby across PDB RESETLOGS
Cause: The pluggable database (PDB) is open while the physical standby is
recovering across a PDB RESETLOGS operation for the PDB.
Action: Close the PDB and restart physical standby recovery.
ORA-39901: Partitioned table string.string is partially contained in the
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Check table partitions by querying SYS.DBA_TAB_PARTITIONS.
ORA-39902: Subpartitioned table string.string is partially contained in the
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
ORA-38029 to ORA-39965 21-93
Action: Check table subpartitions by querying SYS.DBA_TAB_SUBPARTITIONS.
ORA-39903: IOT Partition string.string is partially contained in the transportable
set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Check table partitions by querying SYS.DBA_IND_PARTITIONS.
ORA-39904: Partitioned object string.string is partially contained in the
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Check partitions and overflow segments by querying SYS.DBA_IND_
PARTITIONS and SYS.DBA_TAB_PARTITIONS.
ORA-39905: Table string.string in tablespace string points to LOB segment
string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39906: Constraint string between table string.string in tablespace string and
table string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39907: Index string.string in tablespace string points to table string.string in
tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39908: Index string.string in tablespace string enforces primary constraints
string of table string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39909: Index string.string in tablespace string points to table/cluster
string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39910: Partitioned Global index string.string in tablespace string points to
partition string of table string.string in tablespace string outside of transportable
set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
21-94 Oracle Database Error Messages
ORA-39911: Index string.string in tablespace string points to partition string of table
string.string in tablespace string outside of transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39912: Partitioned index string.string in tablespace string points to table
string.string in tablespace string outside of transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39913: string string.string in tablespace string not allowed in transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39914: Index string.string in tablespace string points to subpartition string of
table string.string in tablespace string outside of transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39915: Partition string of table string.string in tablespace string points to LOB
segment string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39916: Subpartition string of table string.string in tablespace string points to
LOB segment string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39917: SYS owned object string in tablespace string not allowed in pluggable
set
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39918: PLSQL Functional Index string.string in tablespace string not allowed
in transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39919: Object string.string in tablespace string not contained within
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Check SYS.DBA_OBJECTS.
ORA-38029 to ORA-39965 21-95
ORA-39920: Rollback segment string in tablespace string not allowed in
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39921: Default Partition (Table) Tablespace string for string not contained in
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39922: Default Partition (Index) Tablespace string for string not contained in
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39923: Default Composite Partition (Table) Tablespace string for string not
contained in transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39924: Default Composite Partition (Index) Tablespace string for string not
contained in transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39925: LOB segment string.string in tablespace string points to table
string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39926: Join index between table string.string in tablespace string and table
string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39927: Scoped REF constraint between table string.string in tablespace string
and table string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39928: string string.string in tablespace string contains evolved type data that
have not been upgraded.
Cause: Transportable tablespace operation could not be performed because some
tables depending on evolved types were not upgraded.
21-96 Oracle Database Error Messages
Action: Transportable tablespace operation can only be performed when all tables
depending on evolved types have been upgraded. Perform ALTER TABLE <tab_
name> UPGRADE for the table name listed in the message above
ORA-39929: Table string.string in tablespace string has encrypted columns which
are not supported.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39930: Violation string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Contact Oracle Support Services.
ORA-39931: XML Schema string Owner: string not fully contained in the
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Identify the associated elements and resolve self containment.
ORA-39932: Extensible Index string.string not fully contained in the transportable
set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Identify the associated table and list of secondary objects and resolve self
containment.
ORA-39933: Parent table string.string and its nested table columns are not fully
contained in the transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Identify the nested tables using view DBA_NESTED_TABLES and resolve
self containment.
ORA-39934: Materialized view log string.string in tablespace string and master
table string.string in tablespace string are not fully contained in the
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39935: Updatable materialized view log string.string in tablespace string and
materialized view string.string in tablespace string are not fully contained in the
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39936: Token manager for the CSX tablespace string not fully contained in the
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
ORA-38029 to ORA-39965 21-97
Action: Include the specified tablespace into the transportable set.
ORA-39937: Unsupported operation, default token tables used for binary XML
data.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Copy default token tables into a new token table set using DBMS_CSX_
ADMIN package.
ORA-39938: Operation not supported, tablespace string contains binary XML data.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39939: More than one set of token tables are used in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Remap tables in the specified tablespace to use same token tables.
ORA-39940: Child reference partitioned table string.string in tablespace string or
parent table string.string in tablespace string is included but not both.
Cause: Informational message to describe a failure during transportable
containment checking. Both parent and child reference partition tables must be
included.
Action: Check reference partitioned tables.
ORA-39941: Partitioned table string.string in tablespace string has a partition that
has an incomplete online move.
Cause: This is an informational message to describe a failure during transportable
containment checking. Online moves need to be complete before transporting a
tablespace.
Action: Use the DBMS_PART.CLEANUP_ONLINE_OP procedure to force the
online move to complete.
ORA-39942: Subpartitioned table string.string in tablespace string has a
subpartition that has an incomplete online move.
Cause: This is an informational message to describe a failure during transportable
containment checking. Online moves need to be complete before transporting a
tablespace.
Action: Use the DBMS_PART.CLEANUP_ONLINE_OP procedure to force the
online move to complete.
ORA-39943: Global index string.string in tablespace string has orphaned entries.
Cause: This is an informational message to describe a failure during transportable
containment checking. Orphaned entries need to be cleaned up before
transporting a tablespace.
Action: Use DBMS_PART.CLEANUP_GIDX() to cleanup orphaned index entries.
ORA-39944: Global partitioned index string.string in tablespace string has
orphaned entries.
Cause: This is an informational message to describe a failure during transportable
containment checking. Orphaned entries need to be cleaned up before
transporting a tablespace.
21-98 Oracle Database Error Messages
Action: Use DBMS_PART.CLEANUP_GIDX() to cleanup orphaned index entries.
ORA-39945: Token conflicting with existing tokens.
Cause: The binary XML tokens contained in the imported tablespace conflicted
with the existing tokens.
Action: Use the dump file export or import instead of transportable tablespace.
ORA-39946: Nondefault token table encountered.
Cause: During transportable tablespace import, a nondefault token table was
encountered.
Action: Use the dump file export or import instead of transportable tablespace.
ORA-39950: invalid parameter for PLSQL warnings flag
Cause: The user either entered invalid value for the PLSQL_WARNINGS flag or
the value of the flag conflicts with other values.
Action: Enter correct values for the switch.
ORA-39951: incomplete values specified for PL/SQL warning settings
Cause: The user either did not enter the value for the settings or entered
incomplete values.
Action: Enter correct syntax for the switch.
ORA-39952: only numbers can be specified as range values
Cause: The range values did not have numerical values only.
Action: Enter only numerical values.
ORA-39953: the range value specified is beyond allowed range
Cause: The range values were either too low or too high.
Action: Specify only the allowed range values.
ORA-39954: DEFERRED is required for this system parameter
Cause: The ALTER SYSTEM command for PLSQL_WARNINGS did not include
the keyword, DEFERRED.
Action: Change the command to use the keyword, DEFERRED.
ORA-39955: invalid PL/SQL warning message number
Cause: The PL/SQL message number specified was not in a valid range.
Action: Specify PL/SQL warning message numbers within the valid range.
ORA-39956: duplicate setting for PL/SQL compiler parameter string
Cause: A PL/SQL compiler parameter was set more than once.
Action: Remove the duplicate PL/SQL compiler setting.
ORA-39957: invalid warning category
Cause: The category of the message was incorrect.
Action: Specify a vaild category
ORA-39958: invalid warning category qualifier
Cause: The category qualifier was incorrect.
Action: Specify a vaild category qualifier.
ORA-39959: invalid warning number (string)
ORA-38029 to ORA-39965 21-99
Cause: The warning number was incorrect.
Action: Specify a vaild warning number.
ORA-39960: scope can only be SYSTEM or SESSION
Cause: The scope specified was not set.
Action: Specify a vaild scope, either SESSION or SYSTEM.
ORA-39961: message specified was not found
Cause: The message number specified was not set.
Action: specify the message number whise settings have been set in the given
scope.
ORA-39962: invalid parameter for PLSQL_CCFLAGS
Cause: The value for the PLSQL_CCFLAGS parameter was not valid.
Action: Specify a vaild value for the PLSQL_CCFLAGS parameter.
ORA-39964: Specified value for _PLSQL_MAX_STACK_SIZE (string) is larger than
available memory (string)
Cause: The value specified for the _PLSQL_MAX_STACK_SIZE parameter was
larger than the amount of stack size available to the process.
Action: Specify a smaller value for the _PLSQL_MAX_STACK_SIZE parameter.
ORA-39965: Collection of records with PL/SQL type attributes are not allowed in
this context.
Cause: The collection of records with attributes of PL/SQL types were not
allowed as an argument to the TABLE operator.
Action: Use the collection of records whose attributes are of the types that SQL
can understand.
Cause: An unexpected error occurred.
Action: Contact Oracle Support Services.
ORA-32801: invalid value string for string
Cause: An invalid value was specified for a parameter.
Action: Specify a valid value for the parameter.
ORA-32802: value for string must be string
Cause: An invalid value was specified for a parameter.
Action: Specify the value as indicated by the message.
ORA-32803: value for string cannot be altered
Cause: An attempt was made to alter a value that cannot be altered.
Action: Retry the operation without altering the indicated value.
ORA-32804: invalid value string, string should have form string
Cause: A value specified for a parameter has the incorrect form.
Action: Specify a string of the correct form.
ORA-32805: identifier for string too long, maximum length is string characters
Cause: An identifier string exceeded the maximum allowed length.
Action: Specify a string whose length is less than the maximum allowed length.
ORA-32806: value for string is too long, maximum length is string
Cause: A value exceeded it's maximum allowed length.
Action: Specify a value whose length is less than the maximum allowed length.
ORA-32807: message system link string already exists
Cause: A message system link of the specified name already exists.
Action: Specify a different name.
ORA-32808: message system link string does not exist
Cause: A message system link of the specified name does not exist.
Action: Specify a message system link name that already exists.
ORA-32809: foreign queue string is already registered
19-2 Oracle Database Error Messages
Cause: The foreign queue has already been registered for this message system link
(NAME@MSGLINK).
Action: Specify a different name that is not being used for this message system
link.
ORA-32810: foreign queue string is not registered
Cause: The foreign queue (NAME@MSGLINK) has not been registered for this
message system link.
Action: Specify the name of a registered foreign queue.
ORA-32811: subscriber string already exists
Cause: The specified subscriber identifier already exists.
Action: Specify a different identifier.
ORA-32812: subscriber string does not exist
Cause: The specified subscriber identifier does not exist.
Action: Specify an existing subscriber identifier.
ORA-32813: propagation schedule string already exists
Cause: The specified propagation schedule identifer already exists.
Action: Specify a different identifier.
ORA-32814: propagation schedule string does not exist
Cause: The specified propagation schedule identifier does not exist.
Action: Specify a schedule identifier that already exists.
ORA-32815: message system link string is referenced by a foreign queue
Cause: An attempt was made to remove a message system link currently
referenced by one or more registered foreign queues.
Action: Unregister all foreign queues using this message system link and retry the
operation.
ORA-32816: foreign queue string is referenced by a subscriber or schedule
Cause: An attempt was made to unregister a foreign queue currently referenced
by one or more subscribers or propagation schedules.
Action: Remove all subscribers and propagation schedules using this foreign
queue and retry the operation.
ORA-32817: message system link string is not configured with a log queue for
string
Cause: An attempt was made to add a propagation subscriber but the message
system link was not configured with a log queue for the indicated propagation
type.
Action: Alter the message system link to configure the link with a log queue for
this propagation type.
ORA-32818: AQ queue string does not exist
Cause: An operation was attempted where the specified AQ queue does not exist.
Action: Specify the name of an existing AQ queue.
ORA-32819: AQ queue string must be a normal queue
ORA-32800 to ORA-32857 19-3
Cause: An operation was attempted where the specified AQ queue exists but is
not a normal queue.
Action: Specify the name of an AQ queue which was created as a normal queue
(NORMAL_QUEUE).
ORA-32820: subscriber queue and exception queue must use same message system
link
Cause: An operation was attempted for INBOUND propagation where the
specified subscriber queue and exception queue reference different message
system links.
Action: Specify an exception queue that is a registered foreign queue of the same
message system link as the subscriber queue.
ORA-32821: subscriber queue and exception queue must have same payload type
Cause: An operation was attempted for OUTBOUND propagation where the AQ
queues used for the subscriber queue and exception queue have different payload
types.
Action: Specify an exception queue that has the same payload type as the
subscriber queue.
ORA-32822: subscriber string is marked for removal
Cause: An administration operation was attempted for a subscriber which is
marked for removal. If attempting to remove a subscriber, the Messaging Gateway
agent is not running or is running but unable to remove the subscriber at this time.
Action: Do not issue propagation administration commands for a subscriber for
which removal is pending. Wait for the subscriber to be removed by the agent or
issue REMOVE_SUBSCRIBER with the FORCE option to force the subscriber to be
removed.
ORA-32823: subscriber exists for queue string and destination string
Cause: An attempt was made to create a propagation subscriber when one
already exists for the specified queue and destination pair.
Action: Specify a different queue and destination pair, or remove the subscriber
using that pair and retry the operation.
ORA-32824: schedule exists for source string and destination string
Cause: An attempt was made to create a propagation schedule when one already
exists for the specified source and destination pair.
Action: Specify a different source and destination pair, or remove the schedule
using that pair and retry the operation.
ORA-32825: Messaging Gateway agent has not been started
Cause: An attempt was made to shut down the Messaging Gateway agent when it
is not started.
Action: No action required.
ORA-32826: Messaging Gateway agent has already been started
Cause: An attempt was made to start the Messaging Gateway agent when it is
already started.
Action: No action required.
ORA-32827: Messaging Gateway agent must be shut down
19-4 Oracle Database Error Messages
Cause: An operation was attempted that requires the Messaging Gateway agent
to be shut down.
Action: Issue SHUTDOWN, wait for MGW_GATEWAY view to show a NOT_
STARTED status, and retry the operation. CLEANUP_GATEWAY may need to be
issued to reset the gateway state if the agent fails to shut down after a reasonable
time period.
ORA-32828: Messaging Gateway agent must be running
Cause: An operation was attempted that requires the Messaging Gateway agent
to be started and responsive.
Action: Issue STARTUP, wait for MGW_GATEWAY view to show a RUNNING
status, and retry the operation.
ORA-32829: Messaging Gateway agent cannot be shut down while it is starting
Cause: An attempt was made to shut down the Messaging Gateway agent when it
is in the process of starting and initializing.
Action: Wait for MGW_GATEWAY view to show a RUNNING status and retry
the operation. CLEANUP_GATEWAY may need to be issued to reset the gateway
state if the agent fails to start after a reasonable time period.
ORA-32830: result code string returned by Messaging Gateway agent
Cause: The Messaging Gateway agent terminated abnormally due to an
unexpected error.
Action: Review the Messaging Gateway log file for further information regarding
the problem. Resolve the problem and start the Messaging Gateway agent. Contact
Oracle Support Services if the problem cannot be resolved.
ORA-32831: timed out trying to acquire administration lock
Cause: A timeout occurred when attempting an administration operation. Either
an administration operation was attempted while the Messaging Gateway agent
was starting and initializing, or two administration operations were attempted at
the same time.
Action: Retry the operation. If the Messaging Gateway agent is starting, wait for
MGW_GATEWAY view to show a RUNNING status and retry the operation.
ORA-32832: failure string trying to acquire administration lock
Cause: An unexpected error occurred trying to acquire administration lock.
Action: Retry the operation. Contact Oracle Support Services if the error persists.
ORA-32833: failure string trying to release administration lock
Cause: An unexpected error occurred trying to release administration lock.
Action: Contact Oracle Support Services if the error persists.
ORA-32834: Messaging Gateway agent user has not been set
Cause: A Messaging Gateway agent user has not been configured.
Action: Create a database user having role MGW_AGENT_ROLE and issue DB_
CONNECT_INFO to configure an agent user.
ORA-32835: database user string does not exist
Cause: The specified database user does not currently exist.
Action: Create the user and grant all necessary privileges and roles.
ORA-32800 to ORA-32857 19-5
ORA-32836: database user string must be granted role string
Cause: The specified database user does not have a required role.
Action: Grant the user the indicated role.
ORA-32837: invalid configuration state string
Cause: The specified configuration state is invalid.
Action: Remove and re-create the configured entities. Contact Oracle Support
Services if the problem cannot be identified or resolved.
ORA-32838: exceeded maximum number of properties
Cause: An attempt was made to alter a property list where the number of
properties in the resulting list exceeds the maximum allowed.
Action: Order the elements of the alter list differently so the number of elements
in the resulting list is less than the maximum.
ORA-32839: property string is reserved, names with MGWPROP$_ prefix are not
valid
Cause: An attempt was made to specify a reserved name for a property name.
Action: Use a non-reserved name.
ORA-32840: property name cannot be NULL
Cause: An attempt was made to use NULL for a property name.
Action: Specify a non-NULL name.
ORA-32841: invalid value for property string
Cause: An attempt was made to specify an invalid value for a property.
Action: Specify a valid property value.
ORA-32842: value for property string cannot be altered
Cause: An attempt was made to alter a property that cannot be altered.
Action: Retry the operation without altering the indicated property.
ORA-32843: value for string is outside the valid range of string to string
Cause: A value was specified that is not in the valid range.
Action: Specify a value within the indicated range.
ORA-32844: exceeded maximum number of string values
Cause: An attempt was made to add a value of the specified type but the
maximum number of such values has been reached.
Action: No action required.
ORA-32845: Messaging Gateway agent is already running
Cause: An attempt was made to start the Messaging Gateway agent when an
agent instance is already running.
Action: Shut down the Messaging Gateway agent currently running, verify the
agent process has been terminated, and start the Messaging Gateway agent.
ORA-32846: Messaging Gateway agent cannot be started; status is string
Cause: An attempt to start the Messaging Gateway agent failed due to the
indicated agent status. A BROKEN status indicates a problem that requires user
intervention before the agent can be started.
19-6 Oracle Database Error Messages
Action: Review the MGW_GATEWAY view and the Messaging Gateway log file
for further information. Resolve the problem and start the Messaging Gateway
agent. Contact Oracle Support Services if the problem cannot be resolved.
ORA-32847: operation is not supported on this platform
Cause: An attempt was made to perform an operation that is not supported on
this platform.
Action: Switch to a platform on which the operation is supported.
ORA-32848: foreign queue DOMAIN required for JMS unified connections
Cause: A DOMAIN was not specified when registering a foreign queue for a
messaging system link that is configured to use the JMS unified messaging model.
Action: Specify a non-NULL value for the DOMAIN parameter.
ORA-32849: string cannot be set unless string is set
Cause: An attempt was made to specify a value for a parameter that cannot be set
unless an associated parameter is also set.
Action: Specify a valid value for both parameters, or, do not specify a value for
either parameter.
ORA-32850: agent string does not exist
Cause: The specified Messaging Gateway agent name did not exist.
Action: Specify an existing agent name.
ORA-32851: agent string already exists
Cause: The specified Messaging Gateway agent name already existed.
Action: Specify a different agent name.
ORA-32852: agent string is referenced by a message system link
Cause: An attempt was made to remove a Messaging Gateway agent currently
referenced by one or more message system links.
Action: Remove all message system links associated with this agent and retry the
operation.
ORA-32853: propagation job string does not exist
Cause: The specified propagation job identifier did not exist.
Action: Specify an existing identifier.
ORA-32854: propagation job string already exists
Cause: The specified propagation job identifier already existed.
Action: Specify a different identifier.
ORA-32855: propagation job string is marked for removal
Cause: An administration operation was attempted for a propagation job which is
marked for removal. If attempting to remove a job, the Messaging Gateway agent
is not running or is running but unable to remove the job at this time.
Action: Do not issue propagation administration commands for a job for which
removal is pending. Wait for the job to be removed by the agent, or, issue
REMOVE_JOB with the FORCE option to force the job to be removed.
ORA-32856: operation not supported for propagation job
ORA-32800 to ORA-32857 19-7
Cause: An attempt was made to perform an operation that was not supported for
a propagation job.
Action: Perform the operation using a propagation job procedure.
ORA-32857: propagation job exists for source string and destination string
Cause: An attempt was made to create a propagation job, subscriber, or schedule
when a propagation job already existed for the specified source and destination
pair.
Action: Specify a different source and destination pair, or remove the propagation
job using that pair and retry the operation.
19-8 Oracle Database Error Messages
20
ORA-33000 to ORA-37999 0 2
ORA-33000: (AGOPEN00) AGGMAP workspace object cannot be accessed because
it was compiled by a more recent version of string.
Cause: The AGGMAP was already compiled by a more recent version of the
product than was being used to execute this command.
Action: Recompile the AGGMAP in the current version.
ORA-33002: (XSAGDNGL00) In AGGMAP workspace object, the FLOOR argument
of number must be less than the CEILING argument of number.
Cause: The user specified a floor argument greater than the ceiling argument.
Action: Adjust the floor and ceiling arguments so that the floor is less than the
ceiling. OBSOLETE, please remove this
ORA-33003: (XSAGDIMDROP) workspace object, to be transformed during data
load, must be a base dimension and not otherwise referenced in the AGGMAP.
Cause: The user tried to specify a dimension in a dataflow-related clause in an
aggmap which is already in another RELATION statement, DIMENSION
statement, or possibly dimensioning the AGGMAP, or they specified a composite
or conjoint dimension, or an object which is not a dimension
Action: Remove the conflicting reference or specify a valid object
ORA-33004: (XSAGDNGL01) workspace object is not a relationship array.
Cause: A RELATION clause in the AGGMAP named a workspace object that is
not a relation.
Action: Name a valid self-relation in the RELATION statement.
ORA-33005: (XSAGDIMBREAK) Invalid breakout for dimension workspace object.
Cause: The user specified something that was not a valid dimension or relation on
a BREAKOUTDIM line in an aggmap. This might be because the object was not a
valid relation, was not over the specified dimension or was multidimensional
Action: Use a valid relation instead
ORA-33006: (XSAGDNGL02) The relation workspace object is not related to itself.
Cause: A relation was named in a RELATION clause of the AGGMAP that is not a
self-relation.
Action: Name a valid self-relation in the RELATION statement.
ORA-33008: (XSAGDNGL03) The relation workspace object is not a relation over a
base dimension of AGGMAP workspace object.
20-2 Oracle Database Error Messages
Cause: A relation was named in a RELATION clause of the AGGMAP that is not a
relation for a base dimension of the AGGMAP.
Action: Name a valid self-relation in the RELATION statement, that is, one that
has a dimension that dimensions the AGGMAP.
ORA-33009: (XSAGDNGLPREC) In AGGMAP workspace object, PRECOMPUTE
may only be specified either for the entire AGGMAP or for individual
RELATION statements.
Cause: PRECOMPUTE was specified both as a line in the AGGMAP and on at
least one of the RELATION lines, or it was specified more than once as a line of the
AGGMAP.
Action: Remove either the PRECOMPUTE line, or the PRECOMPUTE
specification for all of the RELATION lines.
ORA-33010: (XSAGDNGL04) Relation workspace object is duplicated in the
AGGMAP workspace object.
Cause: Two RELATION statements in the AGGMAP reference the same relation
object.
Action: Remove the duplicate RELATION statement.
ORA-33012: (XSAGDNGL05) AGGMAP workspace object contains invalid syntax.
Cause: A line in the AGGMAP contains invalid syntax.
Action: Change the line to have valid syntax.
ORA-33014: (XSAGDNGL06) In AGGMAP workspace object, variable operator
workspace object cannot be dimensioned by rollup dimension workspace object.
Cause: Operator variables cannot have the rollup dimension as one of their base
dimensions.
Action: Modify the definition of the operator variable so that the current rollup
dimension is not one of its bases.
ORA-33016: (XSAGDNGL07) In AGGMAP workspace object, workspace object is
not a valid operator or variable name.
Cause: An invalid argument was supplied to the OPERATOR clause in the
relation statement.
Action: Fix the OPERATOR clause so that it specifies either a valid variable name
or a valid operator.
ORA-33018: (XSAGDNGL08) In AGGMAP workspace object, the data type of
workspace object must be TEXT, not string.
Cause: An operator variable was supplied whose data type is not TEXT.
Action: Change the operator clause to reference a TEXT variable.
ORA-33022: (XSAGDNGL10) The measure dimension workspace object must be a
TEXT or ID base dimension that does not dimension AGGMAP workspace
object, but is in the same analytic workspace.
Cause: A MEASUREDIM was supplied in the AGGMAP that was not acceptable.
Action: Modify the MEASUREDIM clause to specify a valid dimension.
ORA-33024: (XSAGDNGL11) AGGMAP workspace object contains duplicate
information.
Cause: The aggmap contains multiple instances of a clause that can only be
specified once.
ORA-33000 to ORA-37999 20-3
Action: Remove the extra clause.
ORA-33026: (XSAGDNGL12) In AGGMAP workspace object, workspace object is
not a valid valueset.
Cause: A line in the AGGMAP contains an invalid element where a valid valueset
is required.
Action: Change the line to have a valid valueset.
ORA-33028: (XSAGDNGL13) In AGGMAP workspace object, workspace object
should be scalar, not a dimensioned valueset.
Cause: A line in the AGGMAP contains a dimensioned valueset where a scalared
valueset is required.
Action: Change the line to have a scalar valueset.
ORA-33030: (XSAGDNGL14) In AGGMAP workspace object, you can have either a
single independent PROTECT statement or PROTECT statements in your
RELATION statements.
Cause: The AGGMAP either specified multiple PROTECT statements not on a
RELATION line, or specified PROTECT statements both independently and on
RELATION lines.
Action: Correct the AGGMAP to have valid syntax.
ORA-33032: (XSAGDNGL15) In AGGMAP workspace object, VALUESET
workspace object must be in extra dimensions of the relation.
Cause: The RELATION phrase contains a VALUESET which is not over the extra
dimension of the RELATION.
Action: Correct the RELATION phrase to contain a valueset over the extra
dimension or not to contain any valueset.
ORA-33034: (XSAGDNGL16) In AGGMAP workspace object, VALUESET
workspace object in PRECOMPUTE phrase must be in the self dimension of the
relation.
Cause: The precompute phrase contains a valueset which is not over the self
dimension of the relation.
Action: Correct the relation phrase to contain a valueset over the self dimension
or not to contain any valueset.
ORA-33036: (XSAGDNGL17) ARGS option workspace object must be a TEXT
variable.
Cause: An ARGS value had a non-text data type.
Action: Use a text variable for ARGS.
ORA-33038: (XSAGDNGL18) In AGGMAP workspace object, RELATION
workspace object contains hierarchy dimensions that are also dimensions of the
AGGMAP.
Cause: Hierarchy dimensions(extra dimensions) of a RELATION in the AGGMAP
are base dimensions of the AGGMAP.
Action: Correct the RELATION not to have hierarchy dimensions(extra
dimensions) which are also base dimensions of the AGGMAP.
ORA-33040: (XSAGDNGL19) In AGGMAP workspace object, VALUESETS
workspace object and workspace object are both over the same hierarchy
dimension.
20-4 Oracle Database Error Messages
Cause: Two or more different VALUESETs over the same hierarchy dimension are
used in the AGGMAP.
Action: Use the same VALUESET for two RELATION phrases or use two different
VALUESETs over two different hierachy dimensions.
ORA-33042: (XSAGDNGL20) In AGGMAP workspace object, VALUESET
workspace object must qualify all relations dimensioned by workspace object.
Cause: A VALUESET over a hierarchy dimension qualifies some RELATIONs but
not all RELATIONs dimensioned by the same hierarchy dimension.
Action: Use the same VALUESET to qualify all the RELATIONs dimensioned by
the same hierarchy dimension.
ORA-33044: (XSAGDNGL21) AGGREGATE operator string requires a WEIGHTBY
clause, but the ARGS clause in AGGMAP workspace object did not specify one.
Cause: The user used an operator which needs weight values but not provided
the weight values.
Action: Provide weight values using a WEIGHTBY cluase.
ORA-33045: (XSAGDNGL51) The AGGREGATE operator string does not require a
weight, but ARGS clause in AGGMAP workspace object specified workspace
object as a weight.
Cause: The ARGS variable specified a weight even though one is not needed.
Action: Modify the ARGS variable so that it does not specify a weight for that
operation.
ORA-33046: (XSAGDNGL22) In AGGMAP workspace object, you can specify only
one SCREENBY clause.
Cause: The AGGMAP contained multiple SCREENBY clauses.
Action: Remove one of the SCREENBY clauses from the AGGMAP.
ORA-33048: (XSAGDNGL23) In AGGMAP workspace object, the relation
workspace object and the relation workspace object are both over the same base
dimension.
Cause: The AGGMAP contains incompatible RELATION statements.
Action: Remove one of the RELATION statements from the AGGMAP.
ORA-33050: (XSAGDNGL24) AGGMAP workspace object cannot be used to
aggregate workspace object, because it is defined in a different analytic
workspace.
Cause: The user attempted to aggregate a variable in another analytic workspace.
Action: Create an AGGMAP in the other analytic workspace to aggregate that
variable.
ORA-33052: (XSAGDNGL25) AGGMAP workspace object is a dimensioned
AGGMAP; it can only be used to aggregate like-dimensioned variables.
Cause: The user attempted to aggregate a variable with different dimensions than
the AGGMAP. This is only possible with undimensioned AGGMAPs.
Action: Create a new undimensioned AGGMAP.
ORA-33058: (XSAGDNGL28) In AGGMAP workspace object, error code string is
greater than the maximum error code of number.
Cause: The user specified an invalid ERRORMASK value.
ORA-33000 to ORA-37999 20-5
Action: Remove the invalid value from the ERRORMASK list.
ORA-33060: (XSAGDNGL29) In AGGMAP workspace object, the value for the
ERRORLOG MAX option must be greater than 0.
Cause: The user specified an ERRORLOG MAX of 0 or a negative number.
Action: Adjust the AGGMAP so that it uses a positive number.
ORA-33062: (XSAGDNGL30) In ALLOCMAP workspace object, WEIGHTBY
option workspace object must be a numerical VARIABLE or FORMULA.
Cause: The WEIGHTBY clause requires numerical VARIABLE or FORMULA but
the user used invalid objects.
Action: Correct the WEIGHTBY cluase to use a valid numerical VARIABLE or
FORMULA.
ORA-33064: (XSAGDNGL31) In AGGMAP workspace object, the hierarchy
dimension QDR workspace object cannot refer to the related dimension of the
relation.
Cause: The user specified an invalid hierarchy dimension qualified data reference.
Action: Adjust the AGGMAP so that it uses a valid dimension value qualified
data reference.
ORA-33066: (XSAGDNGL32) In AGGMAP workspace object, the hierarchy
dimension QDR workspace object must be a hierarchy dimension of the
relation.
Cause: The user specified an invalid qualified data reference for the hierarchy
dimension.
Action: Adjust the AGGMAP so that it uses a valid dimension value qualified
data reference.
ORA-33068: (XSAGDNGL33) In AGGMAP workspace object, the hierarchy
dimension QDR over dimension workspace object must specify a positive
dimension offset.
Cause: The user specified an invalid qualified data reference for the hierarchy
dimension.
Action: Adjust the AGGMAP so that it uses a valid dimension value qualified
data reference.
ORA-33070: (XSAGDNGL34) In AGGMAP workspace object, all QDRs of
dimension workspace object must map to the same dimension position.
Cause: The user specified two conflicting hierarchy dimension qualified data
references.
Action: Adjust the AGGMAP so that it uses a consistent qualified data reference.
ORA-33072: (XSAGDNGL35) In AGGMAP workspace object, the hierarchy
dimension QDR over dimension workspace object must be specified for every
relation dimensioned by that hierarchy dimension.
Cause: Multiple dimensions share the same hierarchy dimension, but it is only
qualified within a subset of the AGGMAP relations.
Action: Adjust the AGGMAP so that it uses consistent qualified data references.
ORA-33074: (XSAGDNGL36) In AGGMAP workspace object, the offset number is
not a valid offset into dimension workspace object.
Cause: The hierarchy dimension offset is an invalid dimension position.
20-6 Oracle Database Error Messages
Action: Adjust the AGGMAP so that it uses valid qualified data references.
ORA-33076: (XSAGDNGL37) In AGGMAP workspace object, the value 'number' is
not a valid value of dimension workspace object.
Cause: The hierarchy dimension offset is an invalid dimension position.
Action: Adjust the AGGMAP so that it uses valid qualified data references.
ORA-33078: (XSAGDNGL39) In AGGMAP workspace object, the hierarchy
dimension QDR workspace object must refer to a dimension.
Cause: The user specified an invalid qualified data reference for the hierarchy
dimension.
Action: Adjust the AGGMAP so that it uses a valid dimension value qualified
data reference.
ORA-33080: (XSAGDNGL40) In AGGMAP workspace object, you cannot reference
dimension workspace object with both a RELATION statement and a
DIMENSION statement.
Cause: The user included both RELATION and DIMENSION statements in the
AGGMAP referring to the same AGGMAP.
Action: Remove one of the conflicting clauses.
ORA-33082: (XSAGDNGL41) In AGGMAP workspace object, the non-dimensioned
valueset workspace object must have a parent QDR in its VALUESET statement
over the VALUESET's base dimension.
Cause: The VALUESET statement specified a scalar valueset but did not include a
qualified data reference to specify the parent.
Action: Add a qualified data reference specifying the parent to the VALUESET
statement.
ORA-33084: (XSAGDNGL42) In AGGMAP workspace object, you cannot qualify
the dimensioned valueset workspace object.
Cause: The VALUESET line referred to a dimensioned valueset.
Action: Use a non-dimensioned valueset to limit the status of the dimensioned
one.
ORA-33086: (XSAGINIT01) AGGMAP workspace object cannot be dimensioned by
a conjoint dimension.
Cause: The specified AGGMAP was dimensioned by a conjoint dimension.
Action: Use the CHGDFN command to change the conjoint to a composite
dimension.
ORA-33092: (XSAGCOMP04) number is not the name of a MODEL in any attached
analytic workspace.
Cause: An invalid model name was attached to an AGGMAP.
Action: Remove the model from the AGGMAP or create a model with that name.
ORA-33094: (XSAGGMAPLIST01) Your expression uses too much execution space.
Eliminate recursion or reduce the levels of nesting.
Cause: formulas likely refer to each other recursively or with a great deal of
depth.
Action: eliminate recursion and flatten formula trees.
ORA-33000 to ORA-37999 20-7
ORA-33098: (APABBR01) A value of '%V' is not valid for the workspace object
option.
Cause: An inappropriate value was specified for the named option.
Action: Set a legal value for the option.
ORA-33100: (APABBR02) Value 'number' is not valid for the workspace object
option.
Cause: An inappropriate value was specified for the named option.
Action: Set a legal value for the option.
ORA-33141: (XSAWFREEZE1) The analytic workspace string is already frozen.
Cause: Attempting to freeze an AW when it is already frozen
Action: Thaw the AW before freezing it again.
ORA-33143: (XSAWFREEZE2) The analytic workspace string must be attached RW
or RX.
Cause: The AW must be updatable to change the freeze state
Action: Reattach AW before freezing or thawing it again.
ORA-33145: (XSAWFREEZE3) Cannot rollback analytic workspace string;
generations are in use.
Cause: One or more generations due to be destroyed as part of a rollback to freeze
command are currently in use.
Action: Get sessions using those generations to detach the AW.
ORA-33147: (XSAWFREEZE4) The analytic workspace string is not frozen.
Cause: You are attempting to "rollback to freeze" an AW that is not frozen.
Action: Only execute this command on a frozen AW.
ORA-33213: (CINSERT06) The target position for MAINTAIN ADD or MAINTAIN
MOVE cannot fall in the range of session-only values.
Cause: The user specified a BEFORE or AFTER clause specifying a position in the
range of SESSION dimension values.
Action: Do not use a position clause, or specify a position before the first
SESSION value.
ORA-33214: (CINSERT02) The workspace object dimension is too large.
Cause: The dimension has too many values.
Action: Deleted values can still take up space in the dimension and cause this
error. Try removing the deleted values by exporting the dimension to EIF and
reimporting it with the REPLACE DELETE option.
ORA-33215: (CINSERT07) You cannot add session-only values to the workspace
object dimension.
Cause: The user tried to add a SESSION dimension value while a spreadsheet
spreadsheet cursor was open.
Action: Try adding the SESSION value while the cursor is not active.
ORA-33217: (CINSERT20) Custom member values cannot be added to concat
dimension workspace object, or to any of its bases, because it is not defined as
UNIQUE.
Cause: Only UNIQUE concat dimensions can have custom member values.
20-8 Oracle Database Error Messages
Action: Use the CHGDFN command to change the concat dimension to UNIQUE
and retry.
ORA-33218: (CINSERT04) %K is not a valid value for the workspace object
dimension. Values for this dimension can have at most number significant digits
after rounding to number decimal places.
Cause: The user attempted to insert a value that had too many digits into a
NUMBER dimension. For instance, the user might have tried to insert the value
99999 (5 digits) into a dimension with data type NUMBER(4).
Action: Use a smaller number for the dimension value, or define a new dimension
with a larger precision and replace the old dimension with the new one.
ORA-33219: (CINSERT05) %K cannot be added to workspace object because it is
already a value of the dependent UNIQUE concat dimension workspace object,
from leaf dimension workspace object.
Cause: A value cannot be added to a dimension if it conflicts with an existing
value in a unique concat dimension containing this dimension.
Action: The concat(s) causing the conflict could be CHGDFNed to NOT UNIQUE,
or either of the duplicate values could be renamed to make them UNIQUE.
ORA-33223: (CMOVE03) You cannot move a session-only dimension value.
Cause: The user named a SESSION dimension value in the MAINTAIN MOVE
command.
Action: Do not try to MAINTAIN MOVE session-only dimension values.
ORA-33247: (CRENAME03) %K is already a value of the dependent UNIQUE
concat dimension workspace object, from leaf dimension workspace object.
Cause: A value cannot be renamed in a dimension if the new value conflicts with
an existing value in a unique concat dimension containing this dimension.
Action: The concat(s) causing the conflict could be CHGDFNed to NOT UNIQUE,
or either of the duplicate values could be changed to make them UNIQUE.
ORA-33260: (DIMSHOW01) Partition number does not exist.
Cause: The DIMSHOW command specified a nonexistent partition.
Action: Specify the name of an existing partition, or remove the PARTITION
qualification from the DIMSHOW command.
ORA-33261: (DIMSHOW02) A partition name may be specified only for a
partitioned variable.
Cause: A PARTITION qualification was provided for an object other than a
partitioned variable.
Action: Remove the PARTITION qualification.
ORA-33262: (DBERR01) Analytic workspace string does not exist.
Cause: The analytic workspace requested does not seem to be in the current
database
Action: Check that you are in the correct schema and have access to the requested
AW.
ORA-33263: Could not create analytic workspace string
Cause: A serious error was encountered while trying to set up the tables for the
named analytic workspace. Possibilities include a tablespace that can't be written
ORA-33000 to ORA-37999 20-9
to, corrupted metadata about which AWs exist, bogus tables with names the code
expects to be able to use, or the remains of a partially removed AW.
Action: There should be another error on the error stack. Consult it to determine
what is causing the problem and remove that table.
ORA-33265: (DBERRBSZ) Analytic workspace string cannot be opened. Tablespace
blocksize number does not match database cache size number.
Cause: The blocksize of the containing tablespace didn't match database cache
size.
Action: Change either size to make them consistent, or set olap_page_pool_size to
0 to allow automatic OLAP pool management when compatibility is greater than
10.2.
ORA-33267: (DBERRRLS) Analytic workspace string cannot be accessed because it
has fine-grained access control applied to it
Cause: An attempt was made to access the specified analytic workspace's LOB
table. The OLAP option detected the table had fine-grained security applied to it.
The OLAP option requires full access to this table to operate correctly.
Action: Remove the fine-grained access control.
ORA-33268: (DBERRTHW) Analytic workspace string cannot be attached with the
THAW option because it was frozen with the NOTHAW option
Cause: An attempt to attach the AW using the thaw option was made; the AW
was frozen using the NOTHAW option.
Action: Either attempt the command again without the THAW option.
ORA-33269: while operating on 'string'
Cause: Error is raised to inform user what object was being worked on when an
error occurred during the creation of an AW. It should always be signaled with
33263
Action: See error#33263
ORA-33270: (DBERR05) Analytic workspace string already exists.
Cause: The AW CREATE command was passed the name of an analytic
workspace that already exists
Action: Specify a different name.
ORA-33271: simulated paging error
Cause: This is an internal error that should never be seen
Action: Contact Oracle technical support
ORA-33273: (XSCHKRLS01) Analytic workspace string has open cursors and cannot
be detached.
Cause: A session attempted to detach an analytic workspace while there are
cursors open against it.
Action: Close the open cursor before attempting to close the analytic workspace.
ORA-33274: (DBERR07) Timed out while trying to lock analytic workspace string
for string.
Cause: A lock operation that was supposed to happen very quickly was taking
too long. It can be due to another session being stopped while holding that lock,
another session crashing while holding that lock, or an internal error.
20-10 Oracle Database Error Messages
Action: If another session is stopped, resume that session to let it release the lock.
If another session has crashed, wait for a few minutes while PMON or SMON
process is recovering that lock. Contact Oracle OLAP Support if none of the
situations above apply.
ORA-33275: Autonomous transaction query of an UPDATEd analytic workspace is
not supported
Cause: The user made attempt to reference an anayltic workspace that has
uncommited updates within an autonomous query.
Action: Either COMMIT or ROLLBACK your uncommited changes, or don't use
an autonomous transaction.
ORA-33278: (DBERR09) Analytic workspace string cannot be attached in RW or
EXCLUSIVE mode until the changes made and updated in MULTI mode are
committed or rolled back.
Cause: There are still changes to this analytic workspace that were updated and
not committed when the workspace was attached in MULTI mode.
Action: Either try attaching the workspace is RO or MULTI mode or commit or
roll back the transaction before trying to attach the workspace in RW or
EXCLUSIVE mode.
ORA-33280: (DBERR10) Analytic workspace string cannot be attached in MULTI
mode until the changes made and updated in RW or EXCLUSIVE mode are
committed or rolled back.
Cause: There are still changes to this analytic workspace that were updated and
not committed when the workspace was attached in RW or EXCLUSIVE mode.
Action: Either try attaching the workspace is RO, RW, or EXCLUSIVE mode or
commit or roll back the transaction before trying to attach the workspace in
MULTI mode.
ORA-33282: (DBERR11) Cannot wait for analytic workspace string to become
available since doing so would cause a deadlock.
Cause: Trying to wait for the workspace to become available caused a deadlock.
Action: Release an analytic workspace that some other user might be waiting for
before proceeding to attach this analytic workspace in this mode.
ORA-33284: (DBERR12) Analytic workspace string cannot be opened in MULTI
mode before converting it by the latest version of string.
Cause: The AW is stored in 9i format.
Action: Convert the AW to a later format
ORA-33288: (DBERR15) Another user has incompatible access to analytic
workspace string, and the wait timeout has expired.
Cause: An attempt to access an analytic workspace conflicted with another user's
access, and the timeout specified has elapsed.
Action: Wait until the conflicting user is done.
ORA-33290: (DBERR17) Analytic workspace string cannot be attached in the mode
you requested because another user has it attached in an incompatible mode.
Cause: An attempt to access an analytic workspace conflicted with another user's
access, and no timeout was specified
Action: Wait until the conflicting user is done.
ORA-33000 to ORA-37999 20-11
ORA-33291: (DBERRSYNC) Analytic workspace string cannto be attached RW until
a RESYNC command has brought it up to the current generation.
Cause: Another session has updated the analytic workspace since it was attached
in the current session.
Action: Execute a RESYNC AW command to bring the analytic workspace up to
the most recent version.
ORA-33292: (DBERR18) Insufficient permissions to access analytic workspace
string using the specified access mode.
Cause: You do not have sufficient permissions to access this analytic workspace in
the desired mode.
Action: Ask the owner of the schema or OLAP DBA to grant you sufficient
permissions to access the {SCHEMA}.AW${AWNAME} table (for example,
SCOTT.AW$FOO table).
ORA-33293: Please use the OLAP command AW TRUNCATE to truncate this table.
Cause: This table is part of an analytic workspace, and the OLAP option needs to
control the truncation of the table.
Action: use the OLAP option to truncate the table.
ORA-33295: (DBERR20) An attached analytic workspace is blocking this command.
Cause: A table cannot be dropped because an analytic workspace based on this
table is being attached.
Action: Look up the session in question in GV$AW_OLAP and kill it.
ORA-33296: (DBERR21) Analytic workspace string can only be attached RO while
tablespace string is READONLY.
Cause: The underlying tablespace of the analytic workspace is in READONLY
status.
Action: Attach the analytic workspace in RO mode or alter the tablespace.
ORA-33297: (DBERR22) Analytic workspace string cannot be opened because it was
last modified by an incompatible version of string.
Cause: The user attempted to attach an old OLAP Services analytic workspace
that cannot be converted by this version of OLAP Services.
Action: Either create a new analytic workspace or try using a version of OLAP
Services compatible with the one that created this analytic workspace.
ORA-33298: (AWUPG01) Analytic workspace string is already in the newest format
allowed by the current compatibility setting
Cause: User ran the DBMS_AW.CONVERT procedure on an analytic workspace
that was created in or previously upgraded to the current compatibility mode.
Action: If upgrading the analytic workspace is necessary, upgrade the database
instance and then re-run DBMS_AW.CONVERT. If the new features offered by
upgrading the analytic workspace are not required, then no action is needed.
ORA-33299: Please use DBMS_AW.AW_RENAME to rename this table.
Cause: This table is part of an analytic workspace, and the OLAP option needs to
control the rename of the table.
Action: use the OLAP option to rename the table.
ORA-33302: (DBVALID01) SEVERE ERROR: Record number multiply used.
20-12 Oracle Database Error Messages
Cause: The AW VALIDATE command has detected an error in the structure of the
analytic workspace. This error will result in the corruption of one or more objects
Action: Export what you can of the analytic workspace.
ORA-33304: (DBVALID02) Note: Record number was allocated but not used. This
can result in wasted space.
Cause: This is a benign message. The AW VALIDATE command found an analytic
workspace has some inaccessible space.
Action: Either nothing, or export and recreate the analytic workspace
ORA-33305: (DBVALID06) Note: Record number was allocated but not used. This
can result in wasted space. (PS number)
Cause: This is a benign message. The AW VALIDATE command found an analytic
workspace has some inaccessible space.
Action: Either nothing, or export and recreate the analytic workspace
ORA-33306: (DBVALID03) The AW VALIDATE command cannot be used with
read-only analytic workspace string.
Cause: The AW VALIDATE command does not support read-only access.
Action: Attach the analytic workspace read/write and try again.
ORA-33308: (DBVALID04) SEVERE ERROR: Record number used but not allocated
Cause: The AW VALIDATE command has detected a problem that will result in
corruption of the analytic workspace. There is no corruption yet.
Action: Export and recreate the analytic workspace.
ORA-33309: (DBVALID05) SEVERE ERROR: Record number used but not allocated
(PS number)
Cause: The AW VALIDATE command has detected a problem that will result in
corruption of the analytic workspace. There is no corruption yet.
Action: Export and recreate the analytic workspace.
ORA-33313: (DELDENT05) workspace object cannot be deleted because it is the
target of an external partition of a partitioned variable.
Cause: User attempted to delete a variable, but some partitioned variable was
defined to use that variable as the target of one of its external partitions.
Action: DELETE the partitioned variable or CHGDFN DROP PARTITION the the
external partition from the partitioned variable, then delete the target variable.
ORA-33315: (XSDELDENTANON) You cannot delete workspace object while
looping over unnamed composite workspace object.
Cause: While looping over the named anonymous composite, an attempt was
made to delete an object which is dimensioned by it.
Action: Delete the object outside of a loop over the dimension.
ORA-33332: (DSSEXIST01) Use the AW command to establish a current analytic
workspace. Then start your current activity again.
Cause: There is no currently active analytic workspace. The command that
generated the error requires an active analytic workspace to operate on.
Action: Execute an AW ATTACH or AW CREATE command to establish an active
workspace.
ORA-33000 to ORA-37999 20-13
ORA-33334: (DSSEXIST04) Analytic workspace string is not attached.
Cause: The specified analytic workspace is currently not attached to the session,
or the name is misspelled.
Action: Attach the analytic workspace with the AW ATTACH command, or
correct the spelling of the name .
ORA-33336: (DSSEXIST04A) Analytic workspace string is not attached.
Cause: The specified analytic workspace is currently not attached to the session,
or the name is misspelled.
Action: Attach the analytic workspace with the AW ATTACH command, or
correct the spelling of the name .
ORA-33338: (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.
Cause: The command requires a non-temporary analytic workspace to operate on.
Action: Specify an analytic workspace other than EXPTEMP.
ORA-33339: You cannot detach analytic workspace string. It is in use by an API
branch.
Cause: The OLAP API is in a branch, and you are not allowed to detach the AW
while the branch is active.
Action: End the branch before detaching the AW.
ORA-33393: (EIFIMPRT01) Object string exists in both the EIF file and the current
analytic workspace.
Cause: An object with the given name was found in both the EIF file and the
current analytic workspace.
Action: Rename the object in the analytic workspace that is causing the name
conflict. If the object named in the error message belongs to a cube or a cube
dimension, rename that cube or cube dimension.
ORA-33409: (EIFEXPRT16) Cannot use the FULLMAPID or RELATIVEMAPID
syntax because NOAPI has been specified.
Cause: An attempt was made to specify FULLMAPID or RELATIVEMAPID
syntax with the NOAPI option.
Action: Either specify the API option instead of NOAPI, or remove the
FULLMAPID or RELATIVEMAPID option.
ORA-33413: (EIFMAKEF01) You cannot export compressed composite workspace
object because one of its bases has limited status or a PERMIT READ
restriction.
Cause: Export of a compressed composite to an EIF file or lob failed because one
or more of the bases had some values that were not in the current status. This can
be caused either by a LIMIT command or a PERMIT READ restriction on the
dimension.
Action: Either set the base dimensions' statuses to ALL and remove their PERMIT
READ programs, or export using the NOAGGR keyword.
ORA-33425: (EIFMAKEF15) CAUTION: Exporting NTEXT objects using string for
the EIF file character set can cause loss of data. To preserve all NTEXT data,
export using the UTF8 character set for the EIF file.
Cause: The user exported an object with data type NTEXT, but the EIF file that
will result from the EXPORT command is not written in Unicode. Because no
non-Unicode file can represent all possible Unicode data, it is possible that some
20-14 Oracle Database Error Messages
data will be lost when converting from the Unicode NTEXT object to the EIF file.
The EIF file will be written in the character set indicated by the "nls_charset"
argument of the EXPORT command, or, if no such argument is present, in the
database character set.
Action: If the user is certain that the contents of the NTEXT object can be
represented in the specified character set, then no action is necessary. Otherwise,
the user can add "nls_charset 'UTF8'" to the EXPORT command string. This will
result in the EIF file being written in UTF8 Unicode, which can represent all the
data contained in NTEXT objects.
ORA-33427: (EIFMAKEF16) CAUTION: NTEXT object workspace object will be
exported with type TEXT.
Cause: User attempted to export an object whose data type is NTEXT, but but the
EIFVERSION option indicates a version of Express / Oracle OLAP that does not
support the NTEXT data type. The object will be exported as a TEXT object
instead.
Action: No action needed.
ORA-33429: (EIFMAKEF17) CAUTION: NTEXT expression will be exported with
type TEXT.
Cause: User attempted to export an expression whose data type is NTEXT, but
but the EIFVERSION option indicates a version of Express / Oracle OLAP that
does not support the NTEXT data type. The expression will be exported as a TEXT
object instead.
Action: No action needed.
ORA-33443: (ESDREAD14) Discarding compiled code for workspace object because
analytic workspace string is not attached.
Cause: A program used an analytic workspace name in a qualified object name.
The named analytic workspace is not attached at program run time.
Action: No action necessary. The program will be automatically recompiled. It is
likely that the recompile will fail with an appropriate exception code, in which
case the signaled condition should be corrected and the program re-run.
ORA-33445: (ESDREAD15) Discarding compiled code for workspace object because
workspace object and workspace object, which were not partition-dependent
when the code was compiled, are now partition-dependent.
Cause: Two variables are "partition-dependent" if they share any external
partition target variables, or if one is the target of an external partition of the other.
If object names referred to non-partition-dependent variables at compile time but
refer to partition-dependent variables in the run-time context, the OLAP DML
program, formula, or model will be automatically recompiled.
Action: None needed.
ORA-33447: (ESDREAD16) Discarding compiled code for workspace object because
workspace object and workspace object, which were partition-dependent when
the code was compiled, are now not partition-dependent.
Cause: Two variables are "partition-dependent" if they share any external
partition target variables, or if one is the target of an external partition of the other.
If object names referred to partition-dependent variables at compile time but refer
to non-partition-dependent variables in the run-time context, the OLAP DML
program, formula, or model will be automatically recompiled.
Action: None needed.
ORA-33000 to ORA-37999 20-15
ORA-33448: (ESDREAD04) Discarding compiled code for workspace object because
number now has string data, whereas it had string data when the code was
compiled.
Cause: The datatype of the specified variable has changed.
Action: None needed.
ORA-33449: (ESDREAD17) Discarding compiled code for workspace object because
the partition method or partition dimension of number has changed since it was
compiled.
Cause: The partitioning method (LIST, RANGE, or CONCAT) or the partition
dimension of the partition template is sufficiently different from what it was when
the code was compiled that the code must be recompiled.
Action: None needed.
ORA-33450: (ESDREAD05) Discarding compiled code for workspace object because
number now has more or fewer dimensions than it had when the code was
compiled.
Cause: The dimensionality of the specified object has changed.
Action: None needed.
ORA-33452: (ESDREAD06) Discarding compiled code for workspace object because
number is now dimensioned by workspace object. It was dimensioned by
workspace object when the code was compiled.
Cause: The dimensionality of the specified object has changed.
Action: None needed.
ORA-33454: (ESDREAD07) Discarding compiled code for workspace object because
number is now string workspace object, whereas it was string workspace object
when the code was compiled.
Cause: The specified object has changed.
Action: None needed.
ORA-33456: (ESDREAD08) Discarding compiled code for workspace object because
number is a(n) string, which string did not expect to find in a compiled program.
Cause: The type of the specified object has changed.
Action: None needed.
ORA-33458: (ESDREAD09) Discarding compiled code for workspace object because
number is now type string, whereas it was type string when the code was
compiled.
Cause: The type of the specified object has changed.
Action: None needed.
ORA-33460: (ESDREAD10) Discarding compiled code for workspace object because
object workspace object is not in analytic workspace string.
Cause: The specified object is not in the same analytic workspace it was in when
the compiled object was compiled.
Action: None needed.
ORA-33462: (ESDREAD10A) Discarding compiled code for workspace object
because object number is not in analytic workspace string.
20-16 Oracle Database Error Messages
Cause: The specified object was not in the same analytic workspace it was when
the compiled object was compiled
Action: None needed.
ORA-33468: (ESDREAD13) Discarding compiled code for workspace object because
number is no longer a surrogate of dimension workspace object.
Cause: When the compiled code was saved, the specified object was a surrogate
of a certain dimension. Now the specified object is a surrogate of a different
dimension.
Action: No action needed; program automatically recompiles.
ORA-33557: (MAINTCHK01) You cannot string values of dimension workspace
object during a loop over it.
Cause: User tried to insert or delete a value of the specified dimension while some
loop over that dimension was active. The loop could be an explicit FOR or
ACROSS loop, or a natural expression evaluation or OLAP_TABLE loop. Also, it
could be a loop over the dimension itself or over a derived dimension (like a
composite or partition template) or dimension alias that includes it. The insert or
delete could be explicitly caused by the MAINTAIN command. It is also possible
that the user attempted to assign a value to a variable or partition dimensioned by
a composite during a loop over that composite using a qualified data reference
(QDR), and that the exception was generated by the engine's attempt to insert a
new position in the composite to hold the new value.
Action: Move the dimension maintenance or QDR-based variable assignment
outside the dimension loop.
ORA-33558: (LOCKCHECK01) The status or contents of the workspace object
dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is
set to value.
Cause: A LIMIT or MAINTAIN was attempted on the named language dimension
while the boolean option LOCK_LANGUAGE_DIMS was set to YES.
Action: SET LOCK_LANGUAGE_DIMS to NO and retry the MAINTAIN or
LIMIT.
ORA-33625: (FRASSIGN02) You cannot use the APPEND keyword with concat
dimension workspace object.
Cause: User used the APPEND keyword on a CONCAT target in a FILEREAD,
SQL FETCH or SQL SELECT command.
Action: APPENDing a value to one of the CONCATs leaves automatically
appends to the CONCAT.
ORA-33733: (xsILPMLTPreOp01) The analytic workspace string cannot be
REVERTed or RESYNCed while the string program is active.
Cause: The AW REVERT and AW RESYNC commands cannot be used on an
analytic workspace that contains a running program.
Action: Execute the command without running the specified program.
ORA-33883: (MAKEDCL36) You cannot use the string attribute when you define an
EXTERNAL partition with an existing target.
Cause: User gave the TEMPORARY keyword in the definition of an external
partition whose target variable was previously defined.
ORA-33000 to ORA-37999 20-17
Action: Any storage characteristics of the external partition are determined by the
target variable. These attributes should be set when the target is defined, not when
the external partition is defined.
ORA-33911: (MAKEDCL29) You cannot define a string in analytic workspace string
because it has not been upgraded to version string.
Cause: User attempted to define an object that requires a certain compatibility
setting in an AW that has not been upgraded to that compatibility level.
Action: Make sure that the database is running in the appropriate compatibility
mode, and upgrade the AW.
ORA-33918: (MAKEDCL33) You cannot define a surrogate of dimension workspace
object because it is a string.
Cause: Not all kinds of dimensions can have surrogates. The user attempted to
define a surrogate of a prohibited kind of dimension.
Action: Do not attempt to define a surrogate on this dimension.
ORA-33920: (MAKEDCL34) The string SURROGATE must have one of the
following data types: ID, NTEXT, TEXT, NUMBER, DATETIME, TIMESTAMP,
or INTEGER.
Cause: The user attempted to define a surrogate without specifying a valid data
type.
Action: Specify the data type (ID, NTEXT, TEXT, NUMBER, or INTEGER) in the
definition of the surrogate.
ORA-33922: (MAKEDCL35) You cannot define a surrogate of dimension workspace
object because it is a time dimension.
Cause: The user attempted to define a surrogate on a dimension that has type
DAY, WEEK, MONTH, or YEAR.
Action: Do not attempt to define a surrogate on this dimension.
ORA-33998: (MODCOMP12) You cannot use both workspace object and workspace
object as model dimensions, because workspace object is a surrogate of
workspace object.
Cause: The user attempted to include both a dimension and its surrogate in the
DIMENSION statement of a model.
Action: Use either the dimension or the surrogate in the DIMENSION statement
of the model, but not both.
ORA-34000: (MODCOMP13) You cannot use both workspace object and workspace
object as model dimensions, because they are both surrogates of dimension
workspace object.
Cause: The user attempted to include two dimension surrogates of the same
dimension in the DIMENSION statement of a model.
Action: Use either of the two surrogates in the DIMENSION statement of the
model, but not both.
ORA-34001: (MODCOMP14) Concat leaf dimension workspace object already is
used in a DIMENSION statement, either explicitly or as a leaf of another concat
dimension.
Cause: Either two concat dimensions which share a common leaf dimension, or a
concat and one of its leaves where both specified in the DIMENSION statement(s).
20-18 Oracle Database Error Messages
Action: Do not specify overlapping concat dimensions, or any leaves of specified
concat dimensions.
ORA-34019: (MSCGADD03) workspace object is not a LIST PARTITION
TEMPLATE.
Cause: User attempted to MAINTAINT ADD or DELETE a list value from a
RANGE or CONCAT partition template.
Action: Partitioning in a RANGE or CONCAT partition template cannot be
changed using the MAINTAIN command.
ORA-34021: (MSCGADD04) You must specify a partition when maintaining
PARTITION TEMPLATE workspace object.
Cause: User attempted to MAINTAINT ADD or DELETE a list value from a LIST
partition template, but didn't specify which partition to add to or delete from.
Action: Specify the partition: maintain (template) add to partition (partitionname)
(values) or maintain (template) delete from partition (partitionname) (values)
ORA-34059: (MSEXECUT12) You cannot delete non session-only dimension values
from unique concat dimension workspace object.
Cause: The user tried to apply MAINTAIN DELETE to a non-SESSION value.
Action: Only use MAINTAIN DELETE to remove SESSION values from a concat
dimension.
ORA-34061: (MSEXECUT11) Session-only values cannot be added to non-unique
concat dimension workspace object, or any of its base dimensions.
Cause: Only UNIQUE concat dimensions can have custom member values.
Action: Use the CHGDFN command to change the concat dimension to UNIQUE
and retry.
ORA-34141: (MXCGPUT00) You cannot use the ASSIGN keyword with
DIMENSION workspace object.
Cause: User used the ASSIGN keyword on a DIMENSION target in a FILEREAD,
SQL FETCH or SQL SELECT command.
Action: To create a new dimension value in a FILEREAD, SQL FETCH or SQL
SELECT command, use the APPEND keyword.
ORA-34143: (MXCGPUT02) You cannot assign values to SURROGATE workspace
object because it is type INTEGER.
Cause: The user attempted to assign a value to a dimension surrogate whose data
type is INTEGER. INTEGER surrogates, like INTEGER dimensions, cannot have
values assigned to them. They can only be referenced by position.
Action: Do not attempt to assign values to an INTEGER surrogate. Values will
automatically appear and disappear from the INTEGER surrogate as positions are
added to or removed from the underlying dimension.
ORA-34145: (MXCGPUT03) You cannot use the APPEND keyword with
SURROGATE workspace object.
Cause: User used the APPEND keyword on a SURROGATE target in a
FILEREAD, SQL FETCH or SQL SELECT command.
Action: To assign a value to a SURROGATE in a FILEREAD, SQL FETCH or SQL
SELECT command, use the ASSIGN keyword.
ORA-33000 to ORA-37999 20-19
ORA-34164: (MXCGVAR01) A dimension used to define a local string variable
cannot be located. Execution cannot continue.
Cause: A local relation or valueset has become invalid, most probably because an
object used by the currently executing program has been deleted.
Action: This is an internal error that should be referred to Oracle technical
support.
ORA-34177: (MXCHGDCL19) number cannot be deleted because one or more
partitioned variables instantiate it.
Cause: User attempted to CHGDFN DELETE a partition template, but some
partitioned variable had data in the partition specified for deletion.
Action: Drop the partitions that are causing the problem, then retry.
ORA-34179: (MXCHGDCL20) workspace object is not a PARTITION TEMPLATE.
Cause: User specified an object that is not a partition template where a partition
template is required.
Action: Supply the name of a partition template.
ORA-34181: (MXCHGDCL21) workspace object is not a partitioned VARIABLE.
Cause: User specified an object that is not a partitioned variable in a place where a
partitioned variable is required.
Action: Supply the name of a partitioned variable.
ORA-34183: (MXCHGDCL22) Partition number already exists.
Cause: User attempted to ADD a partition that already existed to a partitioned
variable.
Action: None required - the partition already exists.
ORA-34210: (MXCHGDCL18) You cannot change workspace object to a dimension
composite because one or more surrogates has been defined for it.
Cause: The user attempted to redefine a conjoint dimension as a composite, but
the conjoint has one or more surrogates defined. A dimension that has surrogates
cannot be redefined as a composite.
Action: Either delete all surrogates for the dimension, or do not attempt to
redefine the dimension as a composite.
ORA-34243: (MXDCL11) You can only use the string keyword when defining a
COMPOSITE.
Cause: User supplied the COMPRESSED keyword when defining an object that
was not a COMPOSITE.
Action: If the intent is to create a compressed composite, make sure that the object
type is COMPOSITE. Otherwise, remove the COMPRESSED keyword from the
command string and rerun.
ORA-34260: (MXDCL25) You cannot use number to dimension a string because it is,
or involves, a dimension composite. Use the composite's bases instead.
Cause: The user attempted to use a COMPOSITE in the dimension list of an object
that does not allow for such dimensions.
Action: Use the base dimensions of the COMPOSITE in the dimension list.
ORA-34276: (MXDCL33) (Precision, Scale) arguments can only be used with a
NUMBER variable or dimension.
20-20 Oracle Database Error Messages
Cause: The user attempted to use NUMBER(Precision) or NUMBER(Precision,
Scale) as the datatype in a definition for some object other than a DIMENSION or
VARIABLE, such as a FORMULA or PROGRAM. This error can also be produced
in cases where a NUMBER data type is not allowed at all.
Action: Use the NUMBER type without specifying a precision or scale. If a
NUMBER data type is not allowed at all, this fix will only change the exception
message to something more specific.
ORA-34279: (MXDCL37) CONCAT can only be used when defining a
DIMENSION.
Cause: The CONCAT keyword was used incorrectly.
Action: Retry the command without the CONCAT keyword.
ORA-34286: (MXDCL53) workspace object cannot be used in this context because it
is a string.
Cause: User specified a dimension composite, conjoint, or partition template in a
place where that kind of dimension is not allowed. For instance, a relation cannot
be dimensioned by a composite, and only a variable can dimensioned by a
partition template.
Action: Usually, the offending dimension can be replaced with its bases. For
instance, a relation cannot be dimensioned by a a composite of PRODUCT and
GEOG, but it can be dimensioned by both PRODUCT and GEOG instead.
ORA-34342: (MXDSS01) IMPORTANT: Analytic workspace string is read-only.
Therefore, you will not be able to use the UPDATE command to save changes to
it.
Cause: This is an informational message that reminds you that you may not save
changes to the specified analytic workspace.
Action: None, unless it was desired to save changes to the analytic workspace. In
that case, detach and reattach the analytic workspace read-write.
ORA-34344: (MXDSS03) Analytic workspace string is not attached.
Cause: The command attempted to operate on an analytic workspace that is not
currently attached, or the name of the analytic workspace is misspelled.
Action: Attach the analytic workspace or correct the spelling.
ORA-34346: (MXDSS04) The string analytic workspace cannot be detached.
Cause: The specified analytic workspace is an internal workspace and may not be
detached by the user.
Action: Specify a different analytic workspace to detach.
ORA-34348: (MXDSS05) string is used only for internal purposes and cannot be
accessed as an analytic workspace.
Cause: The command attempted to operate on an internal analytic workspace
used by the system.
Action: Specify a different analytic workspace.
ORA-34350: (MXDSS06) string is an open analytic workspace.
Cause: The specified analytic workspace is currently in use.
Action: The desired action requires an analytic workspace that is not currently in
use.
ORA-34357: (MXDSS10) string is not an alias of analytic workspace string.
ORA-33000 to ORA-37999 20-21
Cause: User attempted to use AW UNALIAS on a non-existent alias.
Action: Make sure that the command specified the correct analytic workspace and
alias. The alias must have been assigned (using AW ALIAS) during the current
session and must not have been removed by a previous AW UNALIAS or AW
DETACH command.
ORA-34358: (MXDSS14) number other users reading
Cause: Used for AW LIST output formatting when %d > 1
Action: None
ORA-34359: (MXDSS11) string appears twice in the alias list.
Cause: User included the same name twice in the alias list of an AW ALIAS or
AW UNALIAS command.
Action: Remove the duplicate name and try again.
ORA-34360: (MXDSS15) number other users writing
Cause: Used for AW LIST output formatting when %d > 1
Action: None
ORA-34361: (MXDSS12) number other user reading
Cause: Used for AW LIST output formatting when %d == 1
Action: None
ORA-34363: (MXDSS13) number other user writing
Cause: Used for AW LIST output formatting when %d == 1
Action: None
ORA-34374: (MXDSS27) string is not a valid analytic workspace name. Analytic
workspace names must be 26 characters or less, can contain only letters, digits,
and underscores, and cannot begin with a digit.
Cause: a specified AW or ALIAS name was too long or contained invalid
characters.
Action: verify that AW name meets the specified criteria.
ORA-34376: (MXDSS28) string is not a valid analytic workspace name. Analytic
workspace names must be 26 characters or less, can contain only letters, digits,
underscores, and dollar signs, and cannot begin with a digit or dollar sign.
Cause: a specified AW or ALIAS name was too long or contained invalid
characters.
Action: verify that AW name meets the specified criteria.
ORA-34481: (MXMAINT07) You cannot string values of PARTITION TEMPLATE
workspace object.
Cause: User attempted to use the MAINTAIN command with some keyword
other than ADD or DELETE on a partition template.
Action: It is not possible to MAINTAIN a partition template, except to add or
delete values of a partition list.
ORA-34487: (MXMAINT08) You cannot string values of non-unique concat
dimension workspace object.
Cause: The specified MAINTAIN operation can only be applied to UNQUE
concats.
20-22 Oracle Database Error Messages
Action: Use the CHGDFN command to change the concat dimension to UNIQUE
and retry.
ORA-34489: (MXMAINT06) You cannot maintain workspace object because it is a
SURROGATE.
Cause: The user attempted to use the MAINTAIN command on a dimension
surrogate. The MAINTAIN command can only be used with real dimensions, not
surrogates.
Action: Use the MAINTAIN command to modify the underlying dimension of the
surrogate instead.
ORA-34514: (MXOPERR) You cannot string string data in the expression that begins
with 'string'.
Cause: The user attempted an invalid operation.
Action: None
ORA-34647: (MXSQL18) The text expression in a CURSOR FOR TEXT declaration
cannot be NA.
Cause: The text for the SELECT expression in a CURSOR FOR TEXT declaration
was evaluated at compile time as NA.
Action: Specify a text expression that is not NA at the time the program
containing the SQL DECLARE is compiled.
ORA-34656: (MXSQL24) Additional WHERE clause conditions with CURRENT OF
<cursor name> syntax
Cause: A SQL UPDATE or DELETE statement tried to use the CURRENT of
<cursor name> syntax with a WHERE clause containing multiple conditions.
Action: When using the CURRENT OF <cursor name> syntax make sure it is the
only condition in the WHERE clause.
ORA-34658: (MXSQL25) The words CURSOR FOR TEXT must be followed by a
compile-time text expression specifying a SELECT command.
Cause: A SQL DECLARE <csr> CURSOR FOR TEXT command lacked a text
expression, or the expression was otherwise invalid.
Action: Specify a single text expression that can be evaluated at compile time to
yield a SELECT statement
ORA-34719: (NLSCHARSET03) Character data loss in NTEXT/TEXT conversion
Cause: When character set conversion happens between TEXT and NTEXT either
implicitly or explicitly, some characters are lost due to no mapping characters in
the destination character set.
Action: Make sure all the characters can be mapped to destination character set or
set NLS_NCHAR_CONV_EXCP to be FALSE. Note: This message is the OLAP
equivalent of ORA-12713.
ORA-34722: (NLSCHARSET05) CAUTION: Character data loss in character set
conversion from string to string
Cause: Some operation required a string to be converted into a different character
set, but the string contained characters that didn't exist in the new character set.
Action: Choose different character sets.
ORA-34726: (NLSCHARSET06) CAUTION: String truncated during character set
conversion from string to string
ORA-33000 to ORA-37999 20-23
Cause: Some operation required a string to be converted into a different character
set. The string required more bytes in the new encoding, and exceeded some byte
limit on its allowable length, causing some characters to be removed from the end
of the string.
Action: If the byte limit is due to using the ID datatype, consider using the CHAR
datatype instead. If the byte limit is due to the limit of 4000 bytes per line of CHAR
data, break the long line up into multiple lines.
ORA-34731: (NLSSORT01) 'number' is not a valid NLS_SORT specification.
Cause: An unrecognized NLS_SORT value was specified in the SORT command
or the SORT, SORTLINES or UNIQUELINES function.
Action: Specify a supported NLS_SORT value.
ORA-34738: (NOUPDATE) A severe problem has been detected. Analytic
workspace operations have been disabled.
Cause: A previous fatal error has marked the session so that it cannot perform
any UPDATEs
Action: Start a new session
ORA-34761: (NXHANDLEALLO) A decimal overflow occurred during an
ALLOCATE operation. The results are not reliable.
Cause: While performing an ALLOCATE, a decimal overflow occurred
Action: Correct the data or use a higher precision datatype
ORA-34796: (OCI08) SQL host variable number cannot be bound.
Cause: The data type of the host variable is not supported.
Action: Specify only variables of supported types as host variable names.
ORA-34802: (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of
an attached analytic workspace. Current operation canceled.
Cause: ROLLBACK past the UPDATE of one of the attached Analytic Workspaces
was called. The current operation is aborted, and the Analytic Workspace
detached.
Action: Change the called SQL procedure to avoid the ROLLBACK
ORA-34804: (OCI12) The value of SQL host variable number is too long. Use the
WIDE keyword for columns that may exceed number bytes.
Cause: The host variable had a text value longer than the maximum SQL
VARCHAR length
Action: Use the WIDE keyword in the host variable specification, e.g. :WIDE
OLAP_object_name
ORA-34805: (OCI13) Statement number must have at least one host variable.
Cause: Statements prepared with DIRECT=YES must have at least one host
variable.
Action: Add a host variable to the prepared statements declaration.
ORA-34806: (OCI14) Statement number can only be executed within an ACROSS
command.
Cause: Statements prepared with DIRECT=YES must be executed in an ACROSS
command.
Action: Execute the statement within an ACROSS command.
20-24 Oracle Database Error Messages
ORA-34840: (OPCREATE01) The string option must be declared with datatype
string.
Cause: An attempt was made to declare the option with the wrong datatype.
Action: Declare the option with the correct datatype.
ORA-34841: (OPCREATE02) The string option must be declared with the
READONLY attribute.
Cause: An attempt was made to declare the option without the READONLY
attribute.
Action: Declare the option READONLY.
ORA-34859: (PMTUPDAT07) Permission condition for workspace object contains
an expression longer than number bytes and cannot be stored.
Cause: One of the components of the PERMIT condition was too long.
Action: Rewrite the condition to shorten it.
ORA-34871: (PERMIT06) Session-only value 'value' of workspace object has been
deleted because a PERMIT change has revealed a duplicate value.
Cause: Execution of a PERMIT command revealed a permanent dimension or
surrogate value having the same name as the SESSION value.
Action: If the SESSION value is still needed, add it with a different name.
ORA-34896: (PPMONTHS00) At least 12 month names must be given. Only number
were provided.
Cause: There must be at least one name for each month. Not enough names were
provided.
Action: Provide at least 12 names.
ORA-34897: (PPMONTHS01) Blank lines are not allowed in the MONTHNAMES
option.
Cause: There is at least one blank line in the string populating the
MONTHNAMES option. We do not allow blank month names.
Action: Remove the blank line(s) from the string.
ORA-34900: (PPWKDAYS00) At least 7 day names must be given. Only number
were provided.
Cause: There must be at least one name for each day. Not enough names were
provided.
Action: Make sure there are at least 7 names in the string.
ORA-34901: (PPWKDAYS01) Blank lines are not allowed in the DAYNAMES
option.
Cause: There is at least one blank line in the string populating the DAYNAMES
option. We do not allow blank day names.
Action: Remove the blank line(s) from the string.
ORA-35016: (QFCHECK00) The analytic workspace and EIF file definitions of
workspace object have a mismatched type.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
ORA-33000 to ORA-37999 20-25
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35017: (QFCHECK06) The Analytic Workspace and EIF file definitions of
workspace object have different partitioning methods.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35018: (QFCHECK01) The analytic workspace and EIF file definitions of
workspace object have a mismatched data type.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35019: (QFCHECK07) The Analytic Workspace and EIF file definitions of
workspace object have different partition dimensions.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35020: (QFCHECK02) The analytic workspace and EIF file definitions of
workspace object have mismatched dimensioning.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35021: (QFCHECK08) The EIF file definition of workspace object has some
partitions that are not present in the existing Analytic Workspace object.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35022: (QFCHECK03) The analytic workspace and EIF file definitions of
workspace object have a mismatched relation.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35023: (QFCHECK09) The analytic workspace and EIF file definitions of
workspace object have incompatible partition definitions.
20-26 Oracle Database Error Messages
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35024: (QFCHECK04) The analytic workspace and EIF file definitions of
workspace object have mismatched time dimension attributes.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35026: (QFCHECK05) The analytic workspace and EIF file definitions of
workspace object have a mismatched ALIASOF dimension.
Cause: Importing from an EIF file or LOB into an existing Analytic Workspace
object failed because the definition of the existing object was too different from the
definition of the object in the EIF file or LOB.
Action: Import the object into an Analytic Workspace that does not already
contain an object with the same name.
ORA-35031: (QFSVNS00) The IMPORT command has terminated because of a
defect in the EIF file.
Cause: The EIF file contains a compressed composite with defective aggregation
data.
Action: Recreate the EIF file using the NOAGGR keyword.
ORA-35062: (QFGET01) Duplicate files found for extension number number of EIF
file string.
Cause: IMPORT searched the directories specified in EIFEXTENSIONPATH and
found two EIF extension files with the same name (differing at most by the case
used in the final name component.
Action: Delete, rename or move any files that are not to be read by IMPORT.
ORA-35066: (QFGET03) Extension number number is missing for EIF file string.
Cause: IMPORT searched the directories specified in EIFEXTENSIONPATH and
could not find the appropriately numbered extension file.
Action: Move the missing file into one of the searched directories.
ORA-35071: (QFHEAD06) EIF file string cannot be imported because analytic
workspace string has not been upgraded to version string.
Cause: User attempted to import from an EIF file that was created by a newer
version of the product into an AW that was created by a older version of the
product.
Action: Make sure that the compatibility mode parameter in the init.ora of the
importing instance specifies a version that is at least as high as the parameter was
in the exporting instance. Then, convert the AW to the latest storage format and
reexecute the import command. Alternatively, change the EIFVERSION option of
the exporting instance to a lower number, recreate the EIF file, and import the new
file.
ORA-35074: (QFHEAD02) EIF file string cannot be read by this version of string.
ORA-33000 to ORA-37999 20-27
Cause: The EIF file was created with an internal version number indicating it may
contain objects that are not compatible with the current Oracle OLAP version, or
the EIF file is in an obsolete format.
Action: If possible, set EIFVERSION in the exporting instance to a lower number,
recreate the EIF file, and import the new file.
ORA-35076: (QFHEAD04) CAUTION: The textual data in EIF file string is encoded
in a character set that is not recognized by this version of string.
Cause: IMPORT could not recognize the character set specification in the EIF file.
Action: Check the imported text data. If it was not imported correctly, recreate the
EIF file with a character set supported by the current Oracle version.
ORA-35078: (QFHEAD05) An EIF extension file header for string is not in the
correct format.
Cause: An EIF extension file in multi-file IMPORT did not contain correct header
information.
Action: Check to be sure that EIFEXTENSIONPATH is set correctly and that all
the extension files for the current IMPORT were created by the same EXPORT
command as the main EIF file.
ORA-35095: (QFSVNS01) One or more imported values of fixed-width dimension
workspace object have been truncated.
Cause: The data in the EIF file was exported from a dimension with wider values
than the target dimension will accommodate.
Action: Change the definition of the target dimension, or check to be sure that
multiple values from the target dimension have not become identical during the
import process. This could cause data loss as data from later dimension values
overstores data imported earlier.
ORA-35106: (REGRESS00) The regression was not calculated because of a linear
relationship between your independent variables.
Cause: The values of the specified independent variables are not independent. For
example, one may be a multiple of the other.
Action: Chose independent variables whose values are truly independent of one
another.
ORA-35171: you may not signal error number string with the SIGNAL command
Cause: The user attempted to explicitly signal an invalid error number with the
OLAP DML SIGNAL command
Action: Signal another error number
ORA-35180: (SNSYN103) The format of the OUTFILE command is: OUTFILE
[APPEND] {EOF | TRACEFILE | filename [NOCACHE] [NLS_CHARSET
name]}
Cause: The user specified incorrect syntax for the OUTFILE command.
Action: None
ORA-35276: (SNSYN163) The format of the ALLOCATE command is: ALLOCATE
varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]]
[TARGET tvarname [TARGETLOG logvarname]] [USING aggmap]
Cause: The user used incorrect syntax for the ALLOCATE command.
Action: Correct the calling syntax.
20-28 Oracle Database Error Messages
ORA-35280: (SNSYN165) The format of the AGGREGATE command is:
AGGREGATE varname1 [varname2 varname3 ...] [USING aggmap-name]
[COUNTVAR intvar-name1 [intvar-name2 intvar-name3 ...]] [FUNCDATA]
[FORCEORDER] [PARALLEL #] [{FROM|FROMVAR} fromname [, fromname2
...]]
Cause: The user used incorrect syntax for the AGGREGATE command.
Action: Correct the calling syntax.
ORA-35282: (SNSYN166) The format of the AGGREGATE function is:
AGGREGATE(varname [USING aggmap-name] [COUNTVAR intvar-name]
[FORCECALC] [FORCEORDER] [{FROM|FROMVAR} fromname [, fromname2
...]])
Cause: The user used incorrect syntax for the AGGREGATE function.
Action: Correct the calling syntax.
ORA-35561: (XSRWLD01) Object workspace object is not a valid target.
Cause: An invalid object was specified as a target.
Action: Choose a valid object as a target.
ORA-35562: (SQLIMP01) The SQL IMPORT command will produce number
columns of output, but you have provided number host variables in your INTO
clause.
Cause: The expression is the source query do not match the targets in the INTO
clause.
Action: Make sure the the expressions in the source query match the targets in the
INTO clause.
ORA-35563: (XSRWLD17) Multiple values exist for an attribute of this dimension
member.
Cause: Multiple source table rows containing different values for a dimension
attribute were found. Only the first of the multiple rows has been loaded.
Action: Fix the mapping or remove the rows with conflicting attribute values.
ORA-35564: (XSRWLD02) Cannot convert from the string type to the string type.
Cause: Conversion from source to target is not allowed
Action: Choose a different target datatype
ORA-35565: (XSRWLD03) For object workspace object only APPEND, MATCH or
ASSIGN may be used.
Cause: An incorrect setting was applied to the target
Action: For DIMENSIONs use APPEND or MATCH, for SURROGATEs use
ASSIGN.
ORA-35566: (XSRWLD04) Object workspace object cannot be used with QDRs
Cause: A QDR was placed on a target dimension
Action: Remove the QDR on the target dimension
ORA-35568: (SQLIMP03) The datatype of variable number should be INTEGER,
LONGINTEGER or SHORTINTEGER.
Cause: The target variable was not INTEGER, LONGINTEGER or
SHORTINTEGER.
ORA-33000 to ORA-37999 20-29
Action: The target variable must be INTEGER, LONGINTEGER or
SHORTINTEGER.
ORA-35569: (XSRWLD05) An error was encountered in converting data string to
string in column number.
Cause: The data could not be converted to the target datatype.
Action: Ensure the source data is valid for the target datatype.
ORA-35570: (XSRWLD06) A column value is not a valid member of its target
dimension.
Cause: The source value for a dimension is not an existing member of the
dimension.
Action: Ensure the column value is an existing member of its target dimension.
ORA-35571: (XSRWLD07) The maximum number of load errors has occurred. No
changes from this step were committed to the database.
Cause: The number of load errors exceeded the specified maximum.
Action: Fix the load errors, or increase the maximum number allowed and rerun
the load.
ORA-35572: (XSRWLD08) A column value is not a valid member of its related
dimension.
Cause: The source data for a relation is not a member of the related dimension.
Action: Ensure the source data is a valid member of the related dimension.
ORA-35573: (XSRWLD09) An incoming dimension value is null.
Cause: A source value for a dimension is null.
Action: Ensure the source data for the dimension is not null.
ORA-35578: (SQLOUT11) SQL cursor 'number' cannot be used with CURRENT OF
<cursor name> syntax
Cause: The CURRENT OF <cursor> syntax in the WHERE clause tried to use a
cursor that was not declared with the FOR UPDATE [ of <column name> ] SQL
syntax.
Action: Add the FOR UPDATE [ OF <column name> ] SQL syntax to the cursor
specified.
ORA-35580: (XSRWLD10) An incoming column contains a data type mismatch.
Cause: The data could not be converted to the target datatype.
Action: Ensure the source data is valid for the target datatype.
ORA-35581: (XSRWLD11) You do not have permission to write this value of the
target.
Cause: You do not have sufficient permissions to write to the specified target.
Action: Ask the owner of the schema or OLAP DBA to grant you sufficient
permissions.
ORA-35582: (XSRWLD12) Cannot change the level of dimension member "number"
from "number" to "number" within a single load.
Cause: A dimension member is mapped to more than one level.
Action: Change the mapping so that each dimension member is mapped to only
one level.
20-30 Oracle Database Error Messages
ORA-35583: (XSRWLD13) Cannot change the level of a dimension member within a
single load.
Cause: A dimension member is mapped to more than one level.
Action: Change the mapping so that each dimension member is mapped to only
one level.
ORA-35585: (XSRWLD14) This SQL query generated rejected records.
Cause: Rejected records were generated by this query.
Action: Locate the records that were rejected and resolve the rejection (for
example, data, mapping, and so on).
ORA-35587: (SQLOUT20) The nesting of table functions and SQL commands has
exceeded the maximum of number levels.
Cause: The nesting of table functions with the PREDMLCMD token populated
with an OLAP DML expression that use the embedded SQL support to access
another table function which contains a table functions with the PREDMLCMD
token filled in with an OLAP DML expression that uses the embedded SQL
support.
Action: Reduce the level of nesting between table functions and OLAP DML
embedded SQL support.
ORA-35588: (XSRWLD15) Cannot change the parent of existing dimension member
"number" from "number" to "number" in LOAD RETAIN mode.
Cause: An attempt was made to change the parent of an existing dimension
member in LOAD RETAIN mode.
Action: Fix the mapping or use LOAD [NO] SYNCH mode.
ORA-35589: (XSRWLD16) Cannot change the parent of an existing dimension
member in LOAD RETAIN mode.
Cause: An attempt was made to change the parent of an existing dimension
member in LOAD RETAIN mode.
Action: Fix the mapping or use LOAD [NO] SYNCH mode.
ORA-35749: (VCHEX01) 'character' is not a valid hexadecimal digit.
Cause: The text being converted contains an invalid hexadecimal digit.
Action: Replace the character with a digit in the range 0-9 or A-F.
ORA-35756: (VCTODT02) 'number' is not a valid date because number is out of
range for a year.
Cause: n'%1p'
Action: None
ORA-35810: (XSINPUTERR) The command has requested more input than was
supplied in the command string.
Cause: The command required input that was not supplied in the string.
Action: Reexecute the command with the required input.
ORA-35917: (XSHIDE05) You cannot HIDE model workspace object because the
analytic workspace in which it is defined has not been upgraded to version
string.
Cause: User attempted to apply the HIDE command to a model in an AW that has
not been upgraded to the necessary compatibility level.
ORA-33000 to ORA-37999 20-31
Action: Make sure that the database is running in the appropriate compatibility
mode, and upgrade the AW.
ORA-35952: (XSSPFC01) The string dimension workspace object and the string
dimension workspace object must have the same number of values in status for
SPFCEXEC method number.
Cause: This method requires the named dimensions to have the same number of
values in status, but the user provided statuses of different lengths.
Action: Relimit the dimensions so that their status lengths are the same.
ORA-36017: (XSHIERCK10) The definition of hierarchy workspace object over
number in level number is not star consistent. The collision parents include
number.
Cause: The definition of the hierarchy was not star consistent.
Action: Change the definition of the hierarchy.
ORA-36018: (XSHIERCK02) The format of the HIERCHECK command is:
HIERCHECK relation [STATUS|NOSTATUS|valueset] [MULTIPATH]
[CONSISTENT] [{BALANCED|STAR_CONSISTENT} levelrelation] Or
HIERCHECK aggmap [MULTIPATH] [CONSISTENT]
Cause: The wrong object type was specified.
Action: Change the object to a RELATION or AGGMAP.
ORA-36019: (XSHIERCK11) The format of the HIERSHAPE function is:
HIERSHAPE(relation[(qdr)] {level|ragged|skiplevel|regular} USING levelrel
[INHIERARCHY inhvs] LEVELORDER levelvs)
Cause: The wrong object type or the wrong object definition was specified.
Action: Change the object type or use the correct object definition.
ORA-36020: (XSHIERCK03) The definition of hierarchy workspace object over
number is inconsistent.
Cause: The definition of the hierarchy was inconsistent.
Action: Change the definition of the hierarchy.
ORA-36021: (XSHIERCK12) The format of the HIERCHECK function is:
HIERCHECK(relation [STATUS|NOSTATUS|valueset] [MULTIPATH]
[CONSISTENT] [{BALANCED|STAR_CONSISTENT} levelrelation]) Or
HIERCHECK(aggmap [MULTIPATH] [CONSISTENT])
Cause: The wrong object type was specified.
Action: Change the object to a RELATION or AGGMAP.
ORA-36022: (XSHIERCK04) Valuesets specified in the HIERCHECK command
must be scalar. workspace object is dimensioned.
Cause: The HIERCHECK command specified a dimensioned valueset.
Action: Specify a scalar valueset in its place.
ORA-36024: (XSHIERCK05) Valueset workspace object must contain values of one
of the extra dimensions of relation workspace object.
Cause: The HIERCHECK command specified a valueset over an invalid
dimension.
Action: Specify a valueset containing values of one of the self-relation's extra
dimensions (the dimensions in the relation's dimension list, minus the self-related
dimension itself).
20-32 Oracle Database Error Messages
ORA-36025: (XSHIERCK06) The level dimension of the level relation workspace
object is the same as the relation dimension workspace object.
Cause: The level dimension was the same as the relation dimension.
Action: Change the definition of the level relation.
ORA-36026: (XSHIERCK07) Level relation workspace object is not dimensioned by
relation dimension workspace object.
Cause: The level relation was not dimensioned by the relation dimension.
Action: Change the definition of the level relation.
ORA-36027: (XSHIERCK08) Hierarchy workspace object is not balanced.
Cause: The current hierarchy was not balanced.
Action: Change the hierarchy to balanced.
ORA-36028: (XSHIERCK09) Hierarchy workspace object has multiple paths from
number to number.
Cause: The current hierarchy had multiple paths.
Action: Remove multiple paths from the hierarchy.
ORA-36034: (XSMHIERCK00) One or more loops have been detected in
relationship workspace object over workspace object. The last number of the
items are number.
Cause: A relation was used that had loops in it. There were more items involved
than could be reported.
Action: Correct the relation so that it does not contain loops.
ORA-36035: (XSMHIERCKREL) One or more loops have been detected in
workspace object. number items involved are number.
Cause: A relation was used that had loops in it.
Action: Correct the relation so that it does not contain loops.
ORA-36036: (XSMHIERCK01) One or more loops have been detected in
relationship workspace object over workspace object. The number items
involved are number.
Cause: A relation was used that had loops in it.
Action: Correct the relation so that it does not contain loops.
ORA-36145: (SETPROP01) The property "%1" cannot be set for measure "%2".
Cause: A property name was given that is not one of the allowed properties to be
set.
Action: Specify one of the legal property names.
ORA-36154: (XSMXAGGR01) workspace object is not a data variable.
Cause: An object was specified on the Aggregate command line that was not a
variable
Action: Specify a variable instead
ORA-36155: (XSMXAGGRFROM) workspace object must be a variable or formula
of a similar data type to workspace object to be used with FROM, or a TEXT
variable or formula to be used with FROMVAR.
Cause: The user specified an illegal variable for use with FROM or FROMVAR on
the AGGREGATE command line
ORA-33000 to ORA-37999 20-33
Action: Specify a legal variable instead
ORA-36157: (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you
must also specify the AUTOUPDATE keyword.
Cause: The user specified AUTOCOMMIT but not AUTOUPDATE on the
AGGREGATE command line, which is illegal
Action: Either also specify AUTOUPDATE or don't specify AUTOCOMMIT
ORA-36160: (XSMXAGGR04) You cannot use string on scalar VARIABLE
workspace object.
Cause: The user tried to run the AGGREGATE or AGGCOUNT command or
function on a scalar variable.
Action: Specify a dimensioned variable instead
ORA-36161: (XSAGGRRUVCV) Aggregation variable workspace object cannot have
itself as a COUNTVAR.
Cause: The user specified the same variable as both an aggregation variable and a
COUNTVAR
Action: Specify a different COUNTVAR
ORA-36162: (XSMXAGGR05) COUNTVAR variable workspace object must be of
type INTEGER, not string.
Cause: The user specified a non-INTEGER variable as a COUNTVAR for
aggregation
Action: Redefine the COUNTVAR to be an INTEGER
ORA-36164: (XSMXAGGR07) When using the COUNTVAR clause, the number of
variables to be aggregated (number) must match the number of COUNTVAR
variables (number).
Cause: The user specified a COUNTVAR clause to the AGGREGATE command,
but the number of COUNTVAR variables specified did not match the number of
variables to be aggregated
Action: Specify a separate COUNTVAR for each variable
ORA-36165: (XSAGGCNTPROP) Variable workspace object cannot have both an
AGGCOUNT and the $COUNTVAR property.
Cause: An attempt was made to add the $COUNTVAR property to a variable
which already had an AGGCOUNT, or vice versa.
Action: Delete the already existing $COUNTVAR property or AGGCOUNT first.
ORA-36166: (XSMXAGGR08) workspace object is not a VARIABLE.
Cause: An attempt was made to perform an AGGREGATE or other action on an
object which is not a variable.
Action: Specify a variable instead.
ORA-36167: (XSAGGRFORM) workspace object is an illegal AGGMAP for
aggregating a FORMULA.
Cause: The user attempted to aggregate a FORMULA using an AGGMAP that is
not valid for aggregating FORMULAs. The AGGMAP must specify
PRECOMPUTE(NA) for all relation lines and must not specify any caching.
Action: Correct the AGGMAP so it is legal for aggregating a FORMULA.
20-34 Oracle Database Error Messages
ORA-36168: (XSMXAGGR10) COUNTVAR variable workspace object must have
the same dimensionality as workspace object
Cause: The user specified a COUNTVAR variable which is missing at least one
dimension of the aggregation variable
Action: Specify a COUNTVAR variable which has at least as many base
dimensions as the aggregation variable
ORA-36170: (XSMXAGGR12) The data type of the WEIGHT workspace object must
be numeric or BOOLEAN, not string.
Cause: The user specified a WEIGHT variable or formula which wasn't numeric
or boolean
Action: Specify a numerical or boolean weight instead
ORA-36174: (XSMXAGGR23) workspace object must be either a VARIABLE, a
RELATION or a FORMULA.
Cause: The user specified something that was not a variable, a relation or a
formula as a weight for AGGREGATE
Action: Specify a valid variable, relation or formula instead
ORA-36176: (XSMXAGGR25) Relation workspace object must be a one-dimensional
self-relation to be used as a weight for AGGREGATE.
Cause: The user specified an illegal relation as a weight. The relation might have
been multidimensional, not a self-relation, or not a relation over one of the bases of
the aggregation variable.
Action: Specify a valid self relation over one of the bases of the aggregation
variable.
ORA-36178: (XSAGGR01) To be used with AGGREGATE, AGGMAP workspace
object must be declared with the AGGMAP command.
Cause: The user used the ALLOCMAP command to define the AGGMAP, so the
AGGMAP can only be used with the ALLOCATE command, or the AGGMAP has
no contents attached to it.
Action: Use the AGGMAP command to define the AGGMAP.
ORA-36179: (XSNOAGM) No AGGMAP was specified for VARIABLE workspace
object.
Cause: The user used the AGGREGATE command without specifying an
AGGMAP on the command line, with a variable which had no $AGGMAP
property.
Action: Specify an AGGMAP on the AGGREGATE command line, or add the
$AGGMAP property to the variable in question.
ORA-36180: (XSAGGR08) AGGREGATE cannot function because there is a
permission clause associated with variable workspace object.
Cause: When using AGGREGATE, only simple permissions and permissions on
base dimensions are valid.
Action: Remove the permissions clause from the variable causing problems.
ORA-36181: A VARIABLE cannot have both the $AGGREGATE_FROM and
$AGGREGATE_FROMVAR properties applied to it.
Cause: The user attempted to add both the $AGGREGATE_FROM and
$AGGREGATE_FROMVAR properties to a single variable.
ORA-33000 to ORA-37999 20-35
Action: Remove the existing property before applying the new one.
ORA-36182: (XSAGGR09) Could not locate a value for variable number in measure
dimension workspace object.
Cause: A measure dimension was supplied in the AGGMAP, but a position for
the variable was not found in it.
Action: Add a position for the variable in the measure dimension.
ORA-36184: (XSAGGR10) You do not have sufficient permissions for the variable
workspace object.
Cause: The user lacked the permissions necessary for the aggregation variable.
Action: Remove the restricting permissions from the variable or base dimension.
ORA-36185: (XSAGGR11) workspace object does not have any AGGCOUNT
information.
Cause: User attempted an operation (such as the AVERAGE aggregation operator
or the AGGCOUNT function) that requires a variable to have AGGCOUNT
information on a variable that does not.
Action: Define the variable using the WITH AGGCOUNT clause, or use the
CHGDFN ADD AGGCOUNT command to enable AGGCOUNT for the variable.
ORA-36188: (XSAGGR16) AGGREGATE read a value less than 1 out of
COUNTVAR variable workspace object. Either the values of the COUNTVAR
variable are stored improperly, or there is problem in AGGREGATE. If no one
has modified the values in this COUNTVAR, contact Oracle customer support.
Cause: Either someone improperly changed the COUNTVAR variable, or
AGGREGATE has an error.
Action: Set the COUNTVAR variable to NA before starting AGGREGATE. If you
previously set the COUNTVAR variable to NA, then contact Oracle OLAP
technical support.
ORA-36198: (XSAGGR33) Cannot aggregate over COMPRESSED COMPOSITE
workspace object using AGGMAP workspace object because the operator
variable with more than 1 line dimensions is not supported for bases of a
COMPRESSED COMPOSITE.
Cause: The user specified an aggregation the operator variable with more than 1
line dimensions that is not supported by COMPRESSED COMPOSITES.
Action: Use a MODEL for the calculation, or use an uncompressed COMPOSITE.
ORA-36200: (XSAGGR34) AGGREGATE operator string requires a WEIGHTBY
clause, but ARGS variable workspace object did not specify one.
Cause: The given operator requires a WEIGHT specification, but the ARGS
variable did not supply one.
Action: Modify the ARGS variable to specify a weight for the operation.
ORA-36201: (XSAGGR35) Cannot aggregate workspace object(partition workspace
object) because the subpartition is itself partitioned.
Cause: Attempted to aggregate an intermediate partition of a variable with nested
partitioning.
Action: rerun the aggregate command seperately for each ultimate partition or
just for the variable as a whole
ORA-36202: (XSAGOP01) 'number' is not a valid aggregation operator.
20-36 Oracle Database Error Messages
Cause: An invalid string was provided for an aggregation operator.
Action: Check the spelling of the operator to make sure you are specifying a valid
one.
ORA-36204: (XSAGOP04N) In AGGMAP workspace object, the NAOPERATOR
string must be HFIRST, HLAST or HEVEN.
Cause: An invalid NAOPERATOR was specified.
Action: Specify HFIRST, HLAST or HEVEN.
ORA-36206: (XSAGOP04R) In AGGMAP workspace object, REMOPERATOR string
must be MIN, MAX, FIRST, LAST, HFIRST or HLAST.
Cause: An invalid REMOPERATOR was specified.
Action: Specify one of the legal operators.
ORA-36208: (XSAGOP05N) In AGGMAP workspace object, you can only specify
NAOPERATOR string with the PROPORTIONAL or EVEN operators, not
string.
Cause: The user specified an NAOPERATOR when you were not using
PROPORTIONAL or EVEN.
Action: Remove the NAOPERATOR clause from the RELATION line.
ORA-36210: (XSAGOP05R) In AGGMAP workspace object, you can only specify
the REMOPERATOR string with the PROPORTIONAL, EVEN, or HEVEN
operators, not string.
Cause: The user specified a REMOPERATOR without using PROPORTIONAL,
EVEN, or HEVEN.
Action: Remove the REMOPERATOR clause from the RELATION line.
ORA-36212: (XSAGOP06) In AGGMAP workspace object, you can only specify the
MIN, MAX, FLOOR, and CEILING arguments while using the
PROPORTIONAL operator, not string.
Cause: The user specified MIN, MAX, FLOOR, or CEILING when using an
operator other than PROPORTIONAL.
Action: Remove the incorrect argument from the RELATION line.
ORA-36220: (XSLPDSC01) All dimensions in LIST number are also in the IGNORE
clause.
Cause: One of the dimension lists in the dimension loop descriptor had no base
dimensions except those in the IGNORE list. This leaves no dimensions for
looping over.
Action: Fix the dimension loop descriptor.
ORA-36221: (XSLPDSC02) LIST number and LIST number have different base
dimensions.
Cause: The base dimensions of the dimension lists given in the loop descriptor do
not match.
Action: Ensure that each dimension list has the same set of looping base
dimensions. If necessary, use IGNORE within a lists to discard base dimensions
that should not be looped.
ORA-36222: (XSLPDSC03) duplicate IGNORE or DENSE information for
dimension workspace object
ORA-33000 to ORA-37999 20-37
Cause: An IGNORE or DENSE list in a dimension loop descriptor included the
dimension twice, included two different valuesets of the dimension, or includes
the dimension and a valueset of the dimension.
Action: Only use the dimension or a valueset of the dimension once in an
IGNORE or DENSE list.
ORA-36223: (XSLPDSC04) object workspace object in IGNORE or DENSE list has
illegal type
Cause: An IGNORE or DENSE list in a dimension loop descriptor included and
object that was not a dimension or a valueset, was a conjoint dimension, or was a
dimensioned valueset.
Action: Only use simple dimensions and undimensioned valuesets in the
IGNORE or DENSE list.
ORA-36224: (XSLPDSC05) workspace object is not a loop dimension
Cause: An IGNORE or DENSE list in a dimension loop descriptor referenced a
dimension (or a valueset of a dimension) that was not a base dimension of the
loop dimension list.
Action: Remove the dimension or valueset from the IGNORE or DENSE list.
ORA-36225: (XSLPDSC06) A LOOP AGGMAP list must contain an aggmap object,
followed by one or more variables and/or dimensions.
Cause: An invalid AGGMAP list was specified. Either to few objects were
specified, or an incorrect type of object was used.
Action: Specify a valid AGGMAP list consisting of an aggmap object, followed by
one or more variables and/or dimensions.
ORA-36226: (XSLPDSC07) The syntax of the $LOOP property on formula
workspace object is incorrect.
Cause: Unrecognized contents in the $LOOP property of a formula in the table
function measure list.
Action: Restrict the contents of the $LOOP property to valid elements (other than
OPTIMIZED and MEASURES) of the table function LOOP directive.
ORA-36230: (XSANALYZ00) object workspace object cannot be used in the
ANALYZE command
Cause: An object that cannot be analyzed was used in the ANALYZE command.
Action: Analyze VARIABLES, RELATIONS, DIMENSIONS, or SURROGATES.
ORA-36231: (XSANALYZ01) object workspace object cannot be used in the
INHIERARCHY clause
Cause: An invalid INHIERARCHY object was referenced.
Action: Use either a VALUESET or boolean VARIABLE.
ORA-36232: (XSANALYZ02) a level list was specified when a language dimension
was present
Cause: A level list dimension was specified when a language dimension was
present.
Action: Remove the USING clause.
ORA-36233: (XSANALYZ03) the dimensionality of object workspace object does not
match the ANALYZE command
20-38 Oracle Database Error Messages
Cause: The dimensionality of the object did not match the ANALYZE command
syntax used.
Action: Match the ANALYZE syntax to the dimensionality of the specified object.
ORA-36234: (XSANALYZ04) all objects in the current status of the NAME
dimension must have the same dimensionality when used with the ANALYZE
command
Cause: The dimensionality of at least one of the objects listed in the NAME
dimension does not match the rest of the objects.
Action: Make sure all objects listed in the NAME dimension have the same
dimensionality.
ORA-36236: (XSANALYZ06) the AW format must be 11.0.0.0 or higher to use the
ANALYZE command
Cause: The AW version is less than 11.0.0.0
Action: Make sure the compatible mode is 11.0.0.0 or higher and upgrade the AW
ORA-36237: (XSANALYZ07) analytic workspace string.string must be attached RW
or EXCLUSIVE mode
Cause: The analytic workspace was already attached RO or MULTI mode.
Action: Detach the analytic workspace.
ORA-36238: (XSANALYZ08) object string.string does not exist
Cause: The object name does not exist
Action: Check the spelling and case of the object name
ORA-36258: (XSAGINFO00) When the AGGMAPINFO function is called,
workspace object must be an AGGMAP.
Cause: The AGGMAPINFO function was called with an object that is not an
AGGMAP.
Action: Modify the call to AGGMAPINFO to specify an AGGMAP object.
ORA-36260: (XSAGHIERPART00) Aggregating from partition %J to partition %J
over hierarchy workspace object creates an increase in sparsity.
Cause: In the partition creation / aggmap creation a situation developed such that
when aggregating over a particular dimension of the aggmap a partition boundary
was crossed such that the sparsity of the target partition included dimensions that
were not in the sparsity of the source partition. Since the process of aggregation
always densifies rather than sparsifying this is an extremely suboptimal design
and it is not supported by the aggregate system.
Action: Set up your partitioning such that for any partition boundary the source
and target partitions of the aggregation will always move towards denser
partitions. For any child (c) and any parent (p) where (c) and (p) are in different
partitions it must be the case that the parent partition contains no dimension in the
composite that the child partition does not contain in its composite.
ORA-36261: (XSAGPARTDEP00) Can not Aggregate PARTITION TEMPLATE %J
because the path of aggregation would recursively enter partition %J.
Cause: The partitioning scheme was such that while aggregating there exists a cell
(m) such that both one of its descendants and one of its ancestors are both in the
referenced partition, while (m) is in a different partition.
Action: Change the partitioning scheme.
ORA-33000 to ORA-37999 20-39
ORA-36266: (XSCGMDLAGG00) Invalid context for the AGGREGATION function
Cause: The AGGREGATION function was used outside of the MODEL context.
Action: Use AGGREGATION only in a model.
ORA-36267: (XSCGMDLAGG09) workspace object has no dimensions, so it cannot
have a qualified data reference.
Cause: A dimension qualification was specified for a valueset with no
dimensions.
Action: Remove the qualification.
ORA-36268: (XSCGMDLAGG01) 'string' is not a valid dimension value.
Cause: The AGGREGATION parameter list included a value that does not exist in
the MODEL dimension that contains the target of the AGGREGATION
Action: Specify only values from the appropriate MODEL dimension
ORA-36269: (XSCGMDLAGG10) 'workspace object' does not exist or is not a
dimension.
Cause: A nonexistent or invalid object was specified as a QDR dimension.
Action: Specify existing dimensions only.
ORA-36270: (XSCGMDLAGG03) The parameter list for the AGGREGATION
function includes duplicate values.
Cause: One or more duplicate values appeared in the AGGREGATION parameter
list.
Action: Remove the duplication.
ORA-36271: (XSCGMDLAGG11) workspace object is not in the dimension list of
valueset workspace object.
Cause: A QDR dimension was specified that does not appear in the valueset's
dimension list.
Action: Specify only dimensions in the valueset's dimension list.
ORA-36272: (XSCGMDLAGG04) 'workspace object' is not a valid operator for the
AGGREGATION function.
Cause: An invalid AGGREGATION operator was specified.
Action: Correct the invalid operator.
ORA-36273: (XSCGMDLAGG12) Dimension workspace object appears more than
once in the QDR.
Cause: A dimension was specified more than once in the QDR.
Action: Remove the duplication.
ORA-36274: (XSCGMDLAGG05) The operator used in this equation needs a weight
variable.
Cause: An invalid weight variable was specified.
Action: Correct the invalid weight variable.
ORA-36275: (XSCGMDLAGG13) string is not a valid workspace object.
Cause: A value was specified that does not exist in the QDR dimension.
Action: Specify an existing value.
20-40 Oracle Database Error Messages
ORA-36276: (XSCGMDLAGG06) The current operator does not need a weight
variable.
Cause: A weight variable was specified in a context that does not support it.
Action: Remove the weight variable.
ORA-36278: (XSCGMDLAGG07) workspace object does not exist or is not valueset.
Cause: A nonexistent or invalid object was specified where a valueset is required.
Action: Specify an existing valueset only.
ORA-36280: (XSCGMDLAGG08) Valueset workspace object does not contain values
of any dimension of the current model.
Cause: AGGREGATION specified a valueset of a dimension not listed in a
DIMENSION statement for the current model.
Action: Add the valueset's dimension to the model's DIMENSION list, or choose
a different valueset.
ORA-36290: (EIFMAKEF14) You cannot export object workspace object, because
EIFVERSION is set to number. That version does not support string strings.
Cause: The user tried to export a NUMBER dimension to an EIF file with the
EIFVERSION option set to a number less than 80000. Versions previous to that
eversion do not support NUMBER dimensions.
Action: A NUMBER dimension cannot be used in a version of older than 9.2.0. If
ORA-36312: (PHYS00) workspace object must be a dimension, dimensioned
variable or relation.
Cause: The user specified an invalid OLAP object while attempting to use the
PHYSICAL function
Action: Specify a valid object
ORA-36313: (PHYS03) The VALUE option of PHYSICAL cannot be applied to a
variable.
Cause: the VALUE argument to PHYSICAL was supplied for a variable.
Action: remove VALUE or specify a relation or dimension.
ORA-36314: (PHYS01) workspace object must be a dimension, relation or variable.
Cause: The user specified an invalid OLAP object while attempting to use the
PHYSICAL command
Action: Specify a valid object
ORA-36315: (PHYS04) You must specify the VALUE option for scalar relation
workspace object.
Cause: The VALUE argument to PHYSICAL was omitted for a scalar relation
Action: specify VALUE or choose a dimensioned relation
ORA-36316: (PHYS02) Relation workspace object must be a single-dimensional
relation that relates one INTEGER dimension to another.
Cause: The user specified an invalid relation while attempting to use the
PHYSICAL command
Action: Specify a valid relation
ORA-36340: (SNSYN130) The format of the PARTITIONCHECK function is:
PARTITIONCHECK(aggmap, partition_template)
ORA-33000 to ORA-37999 20-41
Cause: Bad syntax
Action: Correct syntax
ORA-36342: (SNSYN200) The format of the CLEAR command is: CLEAR [ ALL |
STATUS ] [ AGGREGATES | CHANGES | PRECOMPUTES |
NONPRECOMPUTES | CACHE ] FROM var1 [var2, var3...] [USING aggmap]
Cause: The syntax for the CLEAR command was invalid.
Action: Modify your syntax using the correct format.
ORA-36376: (XSAGZERO) AGGREGATE attempted to divide by zero. Set
DIVIDEBYZERO to YES if you want NA to be returned as the result of a
division by zero.
Cause: A calculation in the current AGGREGATE command attempted to divide
by zero as a result of an AVERAGE, WAVERAGE, HAVERAGE or HWAVERAGE
operation.
Action: Either fix the data, or set DIVIDEBYZERO to YES to return NA instead of
signaling an error.
ORA-36378: (XSAGTHRWEIGHT) While running AGGREGATE with multiple
threads, the weight variable workspace object specified by your ARGS variable
workspace object must exist in the same analytic workspace as your AGGMAP
workspace object.
Cause: While running AGGREGATE in threaded mode, you attempted to specify
a WEIGHT variable in another analytic workspace.
Action: Use a weight variable from the same analytic workspace as the aggmap
and rollup variable.
ORA-36380: (AGGRECURSE) AGGREGATE was called recursively, which is not
allowed.
Cause: A model, NATRIGGER, or other object called the AGGREGATE function
or command while another AGGREGATE function or command was already in
progress.
Action: Modify your objects so that they do not need to have two AGGREGATE
commands or functions executing at once.
ORA-36389: (XSAGPARTDEP01) Can not aggregate from PARTITION number into
PARTITION number due to increasing sparsity along DIMENSION %J.
Cause: The user is attempting to use partitions as a means of sparsity control,
however they have set up their partitions in a manner that simply makes no sense.
It is a simple fact that during aggregation data becomes more dense, not less
dense, and yet their partitions indicate the opposite.
Action: Modify the partition template add the specified dimension into the source
composite, or removing it from the target composite.
ORA-36391: (XSMXCLEA01) When CLEAR is used with the STATUS keyword or
an AGGMAP, workspace object must be dimensioned identically to workspace
object.
Cause: The user specified objects whose dimensionality didn't match
Action: Break up the CLEAR command into multiple commands where the
dimensionality of the objects matches
ORA-36392: (XSMXCLEA02) When using CLEAR with the PRECOMPUTES or
NONPRECOMPUTES options, you must specify an AGGMAP.
20-42 Oracle Database Error Messages
Cause: The user didn't specify an AGGMAP with the CLEAR command.
Action: specify an aggmap by adding a USING phrase to the CLEAR command,
or attach a '$AGGMAP' property to the variable.
ORA-36393: (XSMXCLEA03) When using the AGGREGATES, CHANGES or
CACHE options, you must specify the ALL keyword.
Cause: The user didn't use the ALL keyword when using CHANGES or CACHE.
Action: Specify the ALL keyword.
ORA-36394: (XSMXCLEA04) When using CLEAR on the AGGMAP workspace
object, CACHE is the only valid directive.
Cause: The user attempted to CLEAR an AGGMAP using a directive other than
CACHE.
Action: Amend the CLEAR line to only use the CACHE keyword with
AGGMAPs.
ORA-36395: (XSMXCLEA05) To CLEAR ALL AGGREGATES from workspace
object, you must specify an AGGMAP.
Cause: The CLEAR command could not determine how the variable was
aggregated because the variable is not dimensioned by a compressed composite.
Action: Specify an aggmap by adding a USING phrase to the CLEAR command,
or attach a '$AGGMAP' property to the variable.
ORA-36397: (XSSPROPNA) The value of property string cannot be NA.
Cause: The user tried to set a system-reserved property on an OLAP object to NA
Action: Set the property to a non-NA value
ORA-36398: (XSSPROP01) Property name 'number' is invalid because only
system-reserved property names can begin with '$'.
Cause: The user attempted to add a property which starts with $ but is not a
reserved property name
Action: Remove the $ from the property name
ORA-36399: (XSSPROPDTYPE) The data type of property string must be string.
Cause: The user tried to set a system-reserved property on an OLAP object to a
value with an illegal datatype
Action: Set the property with the proper datatype
ORA-36400: (XSSPROP02) workspace object is not a valid variable name.
Cause: Not a valid variable name
Action: Change to a valid variable name
ORA-36401: (XSSPROPOTYPE) Property string may only be applied to objects of
type string.
Cause: The user applied a reserved property name to an incorrect object type
Action: Apply the property to the correct object
ORA-36402: (XSSPROP03) The property '$string' requires a leading "$" because it is
a system-reserved property name.
Cause: The user tried to specify a property name which is reserved, but did not
use a leading $
Action: Either add a leading $ or choose another property name
ORA-33000 to ORA-37999 20-43
ORA-36403: (XSBADSPROP) number is an illegal value for system-reserved
property string on workspace object.
Cause: The user tried to specify an illegal value for a special property
Action: Specify a legal value.
ORA-36404: (XSSPROP04) Property string cannot be applied to an undimensioned
(scalar) TEMPORARY variable.
Cause: The user applied a reserved property name to an incorrect object type
Action: Apply the property to the correct object
ORA-36405: (XSSPROP05) Property ignored for object workspace object:
Cause: A property was ignored during import.
Action: Refer to the message that follows this one and correct the error it
describes.
ORA-36406: (VCACHE00) 'number' is an invalid value for the VARCACHE option.
The only permissible values are 'SESSION', 'VARIABLE', and 'NONE'.
Cause: The user tried to assign an invalid value to the VARCACHE option
Action: Assign one of the valid values
ORA-36410: (VCACHE03) 'number' is an invalid value for the $VARCACHE
property. The only permissible values are 'DEFAULT', 'SESSION', 'VARIABLE',
and 'NONE'.
Cause: The user tried to assign an invalid value to the $VARCACHE property on
a variable
Action: Assign one of the valid values
ORA-36608: (XSAGHOVERFLOW) The depth of the hierarchies encountered while
processing a composite dimension in AGGREGATE caused a counter overflow.
Cause: The depth of the hierarchies that are part of a composite exceeded 4 billion
levels during the merge.
Action: Reduce the number of levels in the hierarchies, reduce the number of
dimensions in the composite, or do not aggregate over all dimensions at once.
ORA-36610: (XSLMS00) Unable to locate a message file for OLAP message: value
Cause: An internal OLAP DML program in the EXPRESS Analytic Workspace
failed to retrieve a user message.
Action: Contact support.
ORA-36612: (XSLMS01) invalid OLAP message number: value
Cause: An internal OLAP DML program in the EXPRESS Analytic Workspace
attempted to retrieve a non-existent message.
Action: Contact support.
ORA-36616: (XSAGMODHIER01) There is a cycle formed by MODEL workspace
object and other embedded or containing models with the same dimension,
workspace object.
Cause: Inclusion of a dynamic model formed a cycle in the named dimension.
Action: Edit the models involving this dimension to remove the cycle.
ORA-36617: (XSAGMODHIER02) There is a self-cycle equation in MODEL
workspace object.
20-44 Oracle Database Error Messages
Cause: The model for relation modification included a self-cycle equation.
Action: Remove the self-cycle equation from the model.
ORA-36618: (XSAGMODDIM00) workspace object is not a valid dynamic model for
AGGMAP.
Cause: The model failed one of the following tests: 1) only one dimension (aside
from LAG/LEAD dimensions); 2) assignment to dimension values only; 3) a single
simple solution block; 4) no time-series functions with variable step values.
Action: Edit the model so that it conforms to the above requirements.
ORA-36620: (XSAGMODDIM01) MODEL workspace object cannot find the
matching embedded model.
Cause: AGGMAP ADD model could not find the matching embedded model.
Action: Add the matching embedded model to the AGGMAP.
ORA-36621: (XSAGMODDIM02) You cannot AGGREGATE the individual
partition using static model workspace object because a partition dimension or
its deriver workspace object appears in the equation of the step or simultaneous
block.
Cause: An attempt was made to AGGREGATE the individual partition using the
static model with the partition dimension in the equation of the step or
simultaneous block.
Action: AGGREGATE the variable instead of the individual partition.
ORA-36622: (XSAGMODLIST00) workspace object cannot be added to the
AGGMAP workspace object because it is not a valid MODEL.
Cause: An object specified in AGGMAP ADD was not a model.
Action: Specify the name of a model.
ORA-36626: (XSAGMODLIST02) MODEL workspace object was skipped because
there is already a MODEL by that name attached to AGGMAP workspace object.
Cause: An attempt was made to add the same model to the AGGMAP twice.
Action: None required.
ORA-36628: (XSAGMODLIST03) MODEL workspace object could not be added to
AGGMAP workspace object.
Cause: The dimension of the model did not match a hierarchy of the aggmap.
Action: Add a RELATION statement to the AGGMAP for that dimension.
ORA-36630: (XSDUNION00) An empty base dimension list was specified in the
concat dimension definition.
Cause: An empty concat dimension list was specified.
Action: Specify a valid list of dimensions when defining a concat dimension.
ORA-36632: (XSDUNION01) The concat dimension workspace object is not
currently defined as UNIQUE.
Cause: Attempt was made to CHGDFN a concat, which is already non-unique, to
NOT UNIQUE.
Action: Since the concat is already non-unique, this command is unnecessary.
ORA-36634: (XSDUNION02) INTEGER dimension workspace object cannot be
used as a concat dimension base.
ORA-33000 to ORA-37999 20-45
Cause: The user cannot specify INTEGER base dimensions when defining a
concat dimension.
Action: Change the datatype of the INTEGER base dimension, or omit it from the
concat.
ORA-36635: (XSDUNION03) The base dimension workspace object has an invalid
datatype for use in a UNIQUE concat definition.
Cause: Base dimensions of a unique concat must have TEXT or ID datatypes.
Action: Specify a valid list of dimensions when defining a unique concat
dimension.
ORA-36636: (XSDUNION04) The unique concat dimension workspace object
cannot be changed to NOT UNIQUE, because it is a base of at least one other
unique concat dimension.
Cause: A non-unique concat dimension cannot be used as a base of a dependent
unique concat.
Action: CHGDFN any dependent unique concat dimensions to NOT UNIQUE
and retry.
ORA-36637: (XSDUNION05) The concat dimension cannot be defined as UNIQUE
because it has a non-unique concat base dimension workspace object.
Cause: A non-unique concat dimension cannot be used as a base of a dependent
unique concat.
Action: CHGDFN any non-unique concat base dimensions to UNIQUE and retry.
ORA-36638: (XSDUNION17) Concat dimension workspace object cannot be
changed to UNIQUE because it has a non-unique concat base dimension
workspace object.
Cause: A non-unique concat dimension cannot be used as a base of a dependent
unique concat.
Action: CHGDFN any non-unique concat base dimensions to UNIQUE and retry.
ORA-36639: (XSDUNION18) UNIQUE cannot be applied to this concat dimension
because leaves workspace object and workspace object share the value number.
Cause: Unique concat base dimensions cannot contain duplicate values.
Action: Use MAINTAIN RENAME to change one of the duplicate values and
retry.
ORA-36640: (XSDUNION19) Concat dimension workspace object cannot be
changed to UNIQUE because base dimension workspace object does not have a
TEXT or ID datatype.
Cause: Base dimensions of a unique concat must have TEXT or ID datatypes.
Action: None
ORA-36641: (XSDUNION20) The concat dimension must be defined as UNIQUE
because base dimension workspace object contains custom member values.
Cause: The UNIQUE keyword was not specified in the concat dimension
definition, and is required if any of its base dimensions contain custom member
values.
Action: Define the concat as UNIQUE, or remove all base custom member values.
ORA-36642: (XSDUNION06) Concat dimension list contains duplicate leaf
dimension workspace object.
20-46 Oracle Database Error Messages
Cause: Duplicate concat leaf dimension was found.
Action: Remove duplicate concat base dimensions and retry.
ORA-36643: (XSDUNION21) Concat dimension workspace object cannot be
changed to NOT UNIQUE because it contains custom member values.
Cause: Only UNIQUE concat dimensions can have custom member values or
base dimensions which contain custom member values.
Action: Remove all custom member values from the concat and all of its bases,
and retry.
ORA-36644: (XSDUNION07) Concat dimension workspace object contains a
previously detected leaf dimension.
Cause: Concat dimension contains a previously detected leaf dimension.
Action: None
ORA-36646: (XSDUNION08) Only concat dimensions can be redefined as
UNIQUE. workspace object is not a concat dimension.
Cause: UNIQUE keyword was used with an invalid object.
Action: Retry without the UNIQUE keyword.
ORA-36648: (XSDUNION09) Concat dimension workspace object is already defined
as UNIQUE.
Cause: Attempt to change a concat dimension to UNIQUE, but it is already
UNIQUE.
Action: None
ORA-36650: (XSDUNION10) Concat dimension workspace object cannot be
changed to UNIQUE. Leaves workspace object and workspace object share the
value number.
Cause: Unique concat base dimensions cannot contain duplicate values.
Action: Use MAINTAIN RENAME to change one of the duplicate values and
retry.
ORA-36652: (XSDUNION11) workspace object is not a string type dimension.
Cause: The CHGDFN BASE ADD command is only valid for concat dimensions.
Action: None
ORA-36664: (XSDPART02) You must specify a partitioning method and one or more
partition dimensions when defining a PARTITION TEMPLATE.
Cause: User tried to define a PARTITION TEMPLATE without a PARTITION BY
clause.
Action: Add a PARTITION BY clause.
ORA-36665: (XSDPART03) workspace object is not in the dimension list of the
PARTITION TEMPLATE.
Cause: While defining a partition template, user attempted to specify a partition
dimension that is not a dimension of the partition template itself.
Action: Choose a partition dimension from among the dimensions of the partition
template.
ORA-36666: (XSDPART04) workspace object is not a concat dimension.
ORA-33000 to ORA-37999 20-47
Cause: User tried to define a partition template with PARTITION BY CONCAT(...
dim ...) where dim is not a concat dimension.
Action: Only concat dimensions can serve as partition dimensions with CONCAT
partitioning. Choose a different partition dimension.
ORA-36667: (XSDPART05) string is not a legal CONCAT partition.
Cause: User attempted to use RANGE or LIST syntax in defining a CONCAT
partition template.
Action: Use CONCAT partition syntax.
ORA-36668: (XSDPART06) string is not a legal RANGE partition.
Cause: User attempted to use CONCAT or LIST syntax in defining a RANGE
partition template.
Action: Use RANGE partition syntax.
ORA-36669: (XSDPART07) string is not a legal LIST partition.
Cause: User attempted to use RANGE or CONCAT syntax in defining a LIST
partition template.
Action: Use LIST partition syntax.
ORA-36670: (XSDPART08) workspace object is an INTEGER or NTEXT dimension,
or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT
dimensions cannot be used as partition dimensions.
Cause: User attempted to define a partition template partitioned by an INTEGER
or NTEXT dimension or a concat containing an NTEXT leaf.
Action: Either pick a different partition dimension, or redefine the dimension to
use a different datatype.
ORA-36671: (XSDPART09) Leaves of workspace object have different datatypes. A
partition dimension cannot have more than one datatype when RANGE
partitioning is used.
Cause: User attempted to define a range partition template with a concat partition
dimension, and the concat had two leaf dimensions with different datatypes.
Action: Pick a different partition dimension.
ORA-36672: (XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only
have a single partition dimension.
Cause: User attempted to define a RANGE or LIST partition template with more
than one partition dimension.
Action: Remove all but one of the dimensions from the PARTITION BY
RANGE(...) or PARTITION BY LIST(...) clause of the partition template definition.
ORA-36673: (XSDPART11) Use simple leaf values to identify concat dimension
values in a VALUES LESS THAN clause, rather than the <LEAF: VALUE>
format.
Cause: When defining a RANGE partition template with a concat dimension for
the partition dimension, the user attempted to define a range using the <LEAF:
VALUE> format of a concat dimension value.
Action: Use just the leaf value. Instead of "VALUES LESS THAN <leaf: value>",
just say, "VALUES LESS THAN value".
ORA-36674: (XSDPART12) Invalid dimension value starting at string.
20-48 Oracle Database Error Messages
Cause: When defining a RANGE or LIST partition template, the user specified an
invalid value in a VALUES LESS THAN or VALUES clause. An "invalid value" can
be one of two things: a value whose datatype does not match the partition
dimension's datatype, or a non-constant value.
Action: Modify the offending VALUES LESS THAN or VALUES phrase.
ORA-36676: (XSDPART14) Missing dimension list for string.
Cause: User attempted to define a CONCAT partition template, and didn't supply
a list of dimensions for one of the partition definitions.
Action: Give a dimension list for each partition.
ORA-36677: (XSDPART15) Duplicate value in value lists of number and number
Cause: In a LIST PARTITION TEMPLATE definition, a value appeared in more
than one value list, or more than once within a single value list.
Action: List each value only once.
ORA-36678: (XSDPART16) workspace object is missing from one or more partition
dimension lists.
Cause: In the definition of a partition template, one of the partitions had a
dimension list that did not contain all the dimensions of the partition template.
Action: Add the offending dimension to the partition's dimension list, or delete it
from the partition template's dimension list. If using CONCAT partitioning and
the missing dimension is a partition dimension, add to the partition dimension list
any leaf of the partition dimension or any concat of leaves of the partition
dimension.
ORA-36679: (XSDPART17) workspace object contains a leaf (workspace object) that
is not part of the partition dimension workspace object.
Cause: In the definition of a CONCAT partition template, one of the partitions
was dimensioned by a dimension that is "concat-related" to a partition dimension,
meaning it shares some leaves with the partition dimension, but it contained some
leaves that are not in the partition dimension.
Action: Either modify the dimensionality of the partition template to include a
concat dimension that contains all the desired leaves, or pick a different dimension
for the partition.
ORA-36680: (XSDPART18) workspace object is not a dimension of the PARTITION
TEMPLATE.
Cause: In the definition of a partition template, one of the partitions was
dimensioned by a dimension that was not given in the dimension list of the
partition template.
Action: Remove the offending dimension from the partition's dimension list, or
add it to the partition template's dimension list.
ORA-36681: (XSDPART19) Partitions string and string are out of order.
Cause: In the definition of a range partition template, a partition with a lower
range boundary was listed after a partition with a higher range boundary.
Action: Alter the order of the partition definition list.
ORA-36682: (XSDPART20) Partition name string appears twice.
Cause: User gave a list of AW partitions in which some partition name appeared
twice.
Action: Remove all but the first instance of the partition name from the list.
ORA-33000 to ORA-37999 20-49
ORA-36683: (XSDPART21) Partition string dimensioned by more than one
composite.
Cause: It is illegal to define a partition template in which one of the partitions is
dimensioned by more than one composite.
Action: Make sure that the partition template being defined has at most one
composite per partition.
ORA-36684: (XSDPART22) You cannot rename values of DIMENSION workspace
object because it is the partition dimension of RANGE PARTITION TEMPLATE
workspace object
Cause: User attempted to rename a value of a dimension that serves as the
partition dimension of some RANGE or LIST partition template.
Action: It is not possible to rename values in such a dimension without deleting
all RANGE and LIST partition templates that are partitioned by it.
ORA-36685: (XSDPART23) Only CONCAT partition templates can be
subpartitioned.
Cause: User attempted to define a RANGE or LIST partition template with one or
more partitions dimensioned by another partition template.
Action: Use only regular dimensions and composites to dimension each partition
of the RANGE or LIST template.
ORA-36686: (XSDPART24) Value number is not in partition number.
Cause: User attempted to reorganize a list partition template by removing a value
from some partition's list, but the value was not in the list.
Action: Ensure that the given values match the given partition.
ORA-36687: (XSDPART25) You cannot use compressed composite workspace object
to dimension multiple partitions of the partition template, because its
dimension list includes the PARTITION BY dimension workspace object.
Cause: The specified PARTITION BY dimension also occurred in the dimension
list of a compressed composite used to dimension multiple partitions.
Action: Ensure that no PARTITION BY dimension occurs among the bases of the
compressed composite used to dimension multiple partitions.
ORA-36688: (NTEXTCNV00) Error during conversion from TEXT to NTEXT.
Cause: An unknown character set conversion error occurred when converting a
TEXT value to an NTEXT value.
Action: Unknown.
ORA-36691: (NTEXTCNV02) Invalid escape sequence in argument to UNISTR
function: string.
Cause: The user called the UNISTR function on a string that had an invalid escape
sequence. The only valid escape sequences in UNISTR are 1.) an escape-escape
sequence, and 2.) an escape, followed by exactly four hexadecimal digits.
Action: Make sure that all escape sequences in UNISTR arguments are exactly
four hexadecimal digits. To represent codepoints whose value is less than 0x1000,
use preceding zeros. WRONG: 0x10; RIGHT: 0x0010.
ORA-36692: (XSRELGID24) A level relation must be specified for the GROUPSET
and ROLLUP options of GROUPINGID.
Cause: level relation was not specified.
20-50 Oracle Database Error Messages
Action: Specify a level relation.
ORA-36693: (XSRELGID25) INHIERARCHY cannot be specified with the
GROUPSET and ROLLUP options of GROUPINGID.
Cause: INHIERARCHY option was specified.
Action: Remove INHIERARCHY option.
ORA-36694: (XSRELTBL01) The value cannot be added to dimension workspace
object.
Cause: Unknown.
Action: Check the context and permission for dimension maintenance.
ORA-36695: (XSRELGID26) The length of GID dimension status is number. The
length of LEVEL dimension status is number.
Cause: GID dimension status did not match LEVEL dimension status.
Action: Change either GID dimension status or LEVEL dimension status.
ORA-36696: (XSRELTBL02) QDR dimension workspace object should not be the
related dimension of the relation.
Cause: An ineligible dimension was specified in the Qualified Data Reference
Action: Do not attempt to qualify this dimension.
ORA-36698: (XSRELTBL03) QDR dimension workspace object should be in the
dimension list that dimensions the relation.
Cause: The named dimension was not in the relation's dimension list.
Action: Select only dimensions that are in the relation's dimension list.
ORA-36700: (XSRELTBL04) Dimension workspace object cannot be qualified more
than once.
Cause: The same dimension was specified more than once in the QDR.
Action: Specify each QDR dimension only once.
ORA-36702: (XSRELTBL05) The format of the HIERHEIGHT function is:
HIERHEIGHT(relation [,] level) level >= 1.
Cause: The HIERHEIGHT function was specified incorrectly.
Action: Make sure the format is correct.
ORA-36704: (XSRELTBL06) workspace object should be dimensioned by workspace
object.
Cause: The level relation is not dimensioned by the source relation dimension.
Action: Make sure the level relation has the correct definition.
ORA-36706: (XSRELTBL07) workspace object should be dimensioned by workspace
object and one level dimension.
Cause: The destination relation has the wrong definition.
Action: Make sure the destination relation has the correct dimensions.
ORA-36708: (XSMXALLOC00) Variable workspace object must be dimensioned to
be used by the ALLOCATE command.
Cause: The user supplied an undimensioned (scalar) variable to the ALLOCATE
command.
Action: Use a dimensioned variable.
ORA-33000 to ORA-37999 20-51
ORA-36710: (XSMXALLOC01) TARGETLOG variable workspace object must be
dimensioned identically to TARGET variable workspace object.
Cause: The user attempted to execute ALLOCATE with mismatched TARGET
and TARGETLOG variables
Action: Use TARGET and TARGETLOG variables with matching dimensionality.
ORA-36712: (XSMXALLOC02) Relation workspace object must be a
one-dimensional self-relation to be used as a SOURCE or BASIS with
ALLOCATE.
Cause: The user specified an invalid source or basis relation on the ALLOCATE
command line.
Action: Modify the relation to be a one-dimensional self-relation.
ORA-36714: (XSMXALLOC03) TARGETLOG variable workspace object must have
the same data type as TARGET variable workspace object.
Cause: The user specified a TARGETLOG variable that had a different data type
from the TARGET variable.
Action: Use TARGETLOG and TARGET variables with an identical data type.
ORA-36718: (XSALLOC00) You do not have the necessary permissions to use
AGGMAP workspace object.
Cause: The user did not have sufficient permissions to run the ALLOCATE
command
Action: Change to a user ID with the appropriate permissions, or use objects that
you have permission to use.
ORA-36720: (XSALLOC01) To be used with ALLOCATE, your AGGMAP workspace
object must be defined with the ALLOCMAP command.
Cause: The user used the AGGMAP command to define the AGGMAP, so either
the AGGMAP can only be used with the AGGREGATE command, or the
AGGMAP has no contents attached to it.
Action: Use the ALLOCMAP command to define the AGGMAP.
ORA-36722: (XSALLOC02) In AGGMAP workspace object, you specified an NA or
ZERO sourceval but supplied formula workspace object as your source for
ALLOCATE.
Cause: The user requested that source values be modified during the allocation,
but that is not possible when using a formula source.
Action: Either use a VARIABLE source or remove the SOURCEVAL specification
for your ALLOCMAP.
ORA-36726: (XSALERR00) The character 'character' is not a valid format specifier
for the ALLOCATE error log.
Cause: The user specified an invalid formatter in the ALLOCERRLOGHEADER
or ALLOCERRLOGFORMAT options.
Action: Correct the option to have a valid format.
ORA-36728: (XSALERR01) While performing the ALLOCATE command with
AGGMAP workspace object, the error logging limit of number was exceeded.
Cause: The user specified an ERRORLOG MAX value in the ALLOCMAP, but
more errors were encountered while performing the allocation.
20-52 Oracle Database Error Messages
Action: Either set ERRORLOG NOSTOP, reduce the allocation errors, or increase
the ERRORLOG MAX setting
ORA-36735: A value exceeded the MAX specification
Cause: .
Action: None
ORA-36740: A CHILDLOCK was detected in your valueset
Cause: .
Action: None
ORA-36761: (XSLANGDM01) Analytic workspace string already contains a
dimension (%J) with the string property.
Cause: An attempt was made to apply this property to more than one dimension
in the AW.
Action: Remove the property from the named dimension and try the command
again.
ORA-36762: (XSLANGDM02) You cannot modify the string property of %J because
analytic workspace string is attached in MULTI mode.
Cause: An attempt was made to add or delete a $DEFAULT_LANGUAGE
property in an AW attached in multiwriter mode.
Action: Attach the AW in a different mode.
ORA-36763: (XSAGGCNTMOVE01) Aggregation variable workspace object cannot
have itself as an AGGCOUNT.
Cause: An attempt was made to turn a variable into its own AGGCOUNT.
Action: Select a different AGGCOUNT variable.
ORA-36764: (XSAGGCNTMOVE02) AGGCOUNT variable workspace object must
be of type INTEGER, not string.
Cause: An attempt was made to create a non-INTEGER AGGCOUNT.
Action: Select an INTEGER AGGCOUNT variable.
ORA-36765: (XSAGGCNTMOVE03) A string aggregation variable cannot have a
string AGGCOUNT.
Cause: The specified AGGCOUNT variable did not have the same permanence as
the aggregation variable.
Action: Select an AGGCOUNT variable with the same TEMPORARY or
PERMANENT attribute as the aggregation variable.
ORA-36766: (XSAGGCNTMOVE04) workspace object cannot be used as an
AGGCOUNT because it has an AGGCOUNT.
Cause: The specified AGGCOUNT variable had its own AGGCOUNT
Action: Select a different variable, or remove the AGGCOUNT using CHGDFN.
ORA-36767: (XSAGGCNTMOVE05) workspace object cannot be used as an
AGGCOUNT while there are permissions applied to it.
Cause: The specified AGGCOUNT variable had its own permissions distinct from
those on the aggregation variable.
Action: Select a different AGGCOUNT variable, or remove the permissions. In
some cases this may require an UPDATE before the command can succeed.
ORA-33000 to ORA-37999 20-53
ORA-36768: (XSAGGCNTMOVE06) An aggregation variable and its AGGCOUNT
must have the same base dimensions.
Cause: An AGGCOUNT variable was specified with different base dimensions
than the aggregation variable.
Action: Select an AGGCOUNT variable with exactly the same base dimensions as
the aggregation variable.
ORA-36778: (XSPGTRLOW) The amount of available temporary storage is still low.
Free some temporary storage immediately. You can do so, for example, by
UPDATING or DETACHING an analytic workspace.
Cause: Ran out of temporary tablespace storage.
Action: Increase the amount of temporary tablespace storage.
ORA-36779: Invalid parameter value.
Cause: The specified value for OLAP_PAGE_POOL_SIZE initialization parameter
was out of range. OLAP_PAGE_POOL_SIZE must be between 2097152 and
2147483647. Addditionally, you cannot use a fixed-size OLAP page pool with
multiple tablespace block sizes. OLAP_PAGE_POOL_SIZE remains unmodified.
Action: None
ORA-36800: (XSTBLFUNC00) The OLAP_TABLE function can only have a single
LOOP statement within the LIMITMAP
Cause: The OLAP table function given used more than one LOOP statement.
Action: It is currently impossible to specify more than one LOOP composite,
either remove one of the statements (and loop densely over relevant dimensions),
or create a new composite that encompasses both loops and have a single loop
statement refer to that.
ORA-36802: (XSTBLFUNC01) The OLAP_TABLE function must contain a
DATAMAP that executes a FETCH command or a LIMITMAP.
Cause: There is no limitmap on the table function and either the datamap does
not contain a fetch, or it errored before the fetch was called.
Action: Check the datamap for errors, make sure that it executes a fetch
statement, if it is not intended to execute the fetch then make sure that the table
function has a valid limitmap.
ORA-36804: (XSTBLFUNC02) The OLAP_TABLE function encountered an error
while parsing the LIMITMAP.
Cause: Invalid LIMITMAP syntax, or the name resolution failure of an
ANALYTIC WORSKPACE OBJECT.
Action: Check the syntax of the limit map, check that the OLAP_TABLE function
refers to a valid analytic workspace, check that all analytic workspace objects
within the limitmap actually exist within the analytic workspace
ORA-36806: (XSTBLFUNC03) The OLAP_TABLE function refers to an invalid ADT
attribute: string.
Cause: The limitmap refers to a matching of ADT attribute to AW object, but the
ADT attribute is not an element of the specified ADT table. Most commonly this is
a typo.
Action: Add the attribute to the ADT, correct the LIMITMAP, or remove the
reference from the LIMITMAP.
20-54 Oracle Database Error Messages
ORA-36808: (XSTBLFUNC04) The OLAP_TABLE function LEVELREL clause
cannot declare number ADT fields from number AW fields.
Cause: The limitmap has a levelrel clause which has a different number of values
in the list to the right of the FROM than it has to the left.
Action: Change the limitmap so that there is a 1:1 mapping of adt and aw
elements.
ORA-36810: (XSTBLFUNC05) Analytic workspace object number does not exist.
Cause: The limitmap refers to a non-existent aw object.
Action: Change the limitmap or define the object
ORA-36812: (XSTBLFUNC06) Invalid Syntax at '?'.
Cause: The limitmap has a question mark character outside the context of a string.
Action: Fix the limitmap
ORA-36814: (XSTBLFUNC07) The datatype of the column used in the ROW2CELL
clause of a LIMITMAP must be RAW(16).
Cause: Datatype of column used in ROW2CELL clause of a LIMITMAP is not
RAW(16).
Action: Change datatype to RAW(16).
ORA-36815: (XSTBLFUNC08) The OLAP_TABLE has attempted to use an AW
single row function with the aw_attach parameter set to DURATION QUERY.
Cause: The OLAP_TABLE aw_attach parameter was set to DURATION QUERY.
Action: Change the OLAP_TABLE aw_attach parameter to DURATION SESSION.
ORA-36816: (XSTBLFUNC09) The workspace object dimension is of datatype string
which does not support custom member upserts.
Cause: Custom members were attempted to be added via an upsert to a
dimension that does not support them
Action: Disable the AW Hash optimization for this query
ORA-36817: (XSTBLFUNC10) The LIMITMAP LOOP clause specifies an invalid
type of object. workspace object must be a DIMENSION or COMPOSITE.
Cause: An invalid type of object was specified in the LOOP clause.
Action: Correct the LOOP clause.
ORA-36818: (XSTBLFUNC11) A LIMITMAP DIMENSION clause specifies an
invalid type of object. workspace object must be a DIMENSION.
Cause: An invalid type of object was specified in the DIMENSION clause.
Action: Correct the DIMENSION clause.
ORA-36819: (XSTBLFUNC12) workspace object cannot be used in a LIMITMAP
string clause.
Cause: An invalid type of object was specified in a LIMITMAP clause.
Action: Correct the LIMITMAP clause.
ORA-36820: (XSLMINFO00) The LIMITMAPINFO function encountered an error
while parsing the LIMITMAP.
Cause: Invalid LIMITMAP syntax.
Action: Correct the syntax of the limit map.
ORA-33000 to ORA-37999 20-55
ORA-36821: (XSJPUSH00) An error occurred while attempting to push a join of 2
AW tables.
Cause: Unknown.
Action: Re-execute the query with parameter _optimizer_aw_join_push_enabled
= FALSE.
ORA-36825: (XSTBLFUNC13) An error occurred expanding the cube_name
argument in the OLAP table function
Cause: Incorrect metadata or invalid cube name
Action: Correct the metadata.
ORA-36826: (XSTBLFUNC14) OLAP C Looper is disabled by event 37395
Cause: init.ora event 37395 includes level 8 which disables the OLAP C looper
Action: Remove event level 8 and use explicit FETCH function for OLAP_TABLE
ORA-36830: (XSLMGEN00) Object string.string does not exist
Cause: The object does not exist
Action: Check view token for errors
ORA-36831: (XSLMGEN01) View token cannot be NA
Cause: A NA was passed as the view token
Action: Pass in a valid view token
ORA-36832: (XSLMGEN02) View token cannot be greater than 4000 bytes
Cause: A view token was greater than 4000 bytes
Action: Pass in a view token less than 4000 bytes
ORA-36833: (XSLMGEN03) View token cannot be blank
Cause: A blank was passed as the view token
Action: Pass in a valid view token
ORA-36834: (XSLMGEN04) Column tag is greater than 30 bytes
Cause: A value greater than 30 bytes was passed as the column tag
Action: Pass in a column tag of 30 bytes or less
ORA-36835: (XSLMGEN05) Dimension string.string hierarchy string level string is
missing a COLUMNNAME property value
Cause: The COLUMNNAME property has no value
Action: Add a value to COLUMNNAME property
ORA-36836: (XSLMGEN06) The dimensionality of object string.string is different
than the view token
Cause: The dimensionality of the cube does not match the view token
Action: Check view token for unrelated hierarchies clauses
ORA-36837: (XSLMGEN07) Object owner string is different than string
Cause: The object owners are different
Action: Make the object owners match
ORA-36838: (XSLMGEN08) Dimension string.string attribute string is missing a
COLUMNNAME property value
20-56 Oracle Database Error Messages
Cause: The COLUMNNAME property has no value
Action: Add a value to COLUMNNAME property
ORA-36839: (XSLMGEN09) Cube string.string measure string is missing a
COLUMNNAME property value
Cause: The COLUMNNAME property has no value
Action: Add a value to COLUMNNAME property
ORA-36840: (XSLMGEN10) Cube string.string has no measures
Cause: The cube has no measures
Action: Add a measure to the cube
ORA-36841: (XSLMGEN11) Dimension string.string was not found
Cause: The view token referenced a dimension that does not exist
Action: Pass in a dimension that does exist
ORA-36842: (XSLMGEN12) Hierarchy string.string.string was not found
Cause: The view token referenced a hierarchy that does not exist
Action: Pass in a hierarchy that does exist
ORA-36843: (XSLMGEN13) Dimension string.string hierarchy string is missing a
PHYSICALNAME property value
Cause: The property PHYSICALNAME has no value
Action: Populate the property PHYSICALNAME with a value
ORA-36844: (XSLMGEN14) Dimension string.string is missing a string property
value
Cause: The dimension is missing a required property
Action: Check dimension property values
ORA-36845: (XSLMGEN15) Owner is greater than 30 bytes
Cause: The owner passed is greater than 30 bytes
Action: Pass in an owner that is 30 bytes or less
ORA-36846: (XSLMGEN16) AW name is greater than 30 bytes
Cause: The AW name passed is greater than 30 bytes
Action: Pass in an AW name that is 30 bytes or less
ORA-36847: (XSLMGEN17) AW name is blank
Cause: The AW name passed is blank
Action: Pass in an AW name that has a value
ORA-36848: (XSLMGEN18) Object name string is different than string
Cause: The object names are different
Action: Make the object names match
ORA-36849: (XSLMGEN19) AW owner does not match View token owner
Cause: The AW owner does not match the View token owner
Action: Match AW ower to View token object owner
ORA-36850: (XSLMGEN20) View token string is not correct
ORA-33000 to ORA-37999 20-57
Cause: The view token is not correct
Action: Check view token syntax for errors
ORA-36861: (XSTFRC01) SQL Cache ID parameter is invalid or missing.
Cause: SQL Cache ID parameter is required to identify SQL cache to query
Action: Supply a valid SQL Cache ID. Normally, users should not call OLAP
Random Access Cursor table function themselves and therefore should not
encounter this error.
ORA-36862: (XSTFRC02) Column number for this SQL Cache must be between 1
and number. Specified column number number is invalid.
Cause: Column Map references a column number that is greater than the
maximum column number in SQL Cache
Action: Reference a correct column number. Normally, users should not call
OLAP Random Access Cursor table function themselves and therefore should not
encounter this error.
ORA-36871: (XSFTDSC01) Object string cannot be used to define a column in a
LIMITMAP.
Cause: The object cannot define a column in LIMITMAP most likely because it is
of a wrong type such as, for example, a Worksheet.
Action: Remove the reference from the LIMITMAP.
ORA-36872: (XSTFDSC02) Column type specifier cannot be used when the table
function data type is specified.
Cause: Column type can only be used with implicitly-specified table functions
Action: Remove column type from reference from the LIMITMAP or remove the
explicit table function data type specification.
ORA-36873: (XSTFDSC03) Column type must be specified explicitly.
Cause: Missing column type specification.
Action: Please, make sure to specify a column type in COLUMN MAP. Normally,
users should not call OLAP Random Access Cursor table function themselves and
therefore should not encounter this error.
ORA-36874: (XSTFDSC04) Expression string cannot be used to define a column in a
LIMITMAP.
Cause: The expression cannot define a column in LIMITMAP most likely because
it is of a wrong type such as, for example, a Worksheet.
Action: Remove the reference from the LIMITMAP.
ORA-36875: (XSTFDSC05) LIMITMAP is missing or is not a string literal.
Cause: Table functions that have an automatic ADT require LIMITMAP to be a
string literal.
Action: Either specify ADT for the table function or specify LIMITMAP as a string
literal.
ORA-36876: (XSTFDSC06) The column datatype string is not supported in OLAP
table functions.
Cause: The object type layer does not support column datatype.
Action: Use a supported column datatype.
20-58 Oracle Database Error Messages
ORA-36881: (XSSRF00) The OLAP DML ROW2CELL function can only be used in a
LIMITMAP.
Cause: Using the ROW2CELL function outside of the LIMITMAP.
Action: Remove use of the ROW2CELL function.
ORA-36882: (XSSRF01) The second parameter of an AW single row function cannot
be NULL.
Cause: The second parameter of the AW single row function was NULL
Action: Pass a valid OLAP DML expression as the second parameter of the AW
single row function
ORA-36883: (XSSRF02) The first parameter of an AW single row function cannot be
NULL.
Cause: The first parameter of the AW single row function was NULL
Action: Make sure the column specified in the LIMITMAP ROW2CELL clause is
the first parameter of the AW single row function.
ORA-36884: (XSSRF03) The value of the first parameter of the AW single row
function is incorrect.
Cause: The column specified in the LIMITMAP ROW2CELL clause was not the
first parameter of the AW single row function.
Action: Make sure the column specified in the LIMITMAP ROW2CELL clause is
the first parameter of the AW single row function.
ORA-36885: (XSSRF04) Error rewriting OLAP DML expression. Column name too
big
Cause: The column name specified in the OLAP DML expression was larger than
30 bytes.
Action: Make sure the column name specified in the OLAP DML expression is
less than or equal to 30 bytes.
ORA-36886: (XSSRF05) Error rewritting OLAP DML expression. Rewritten
expression is greater than number bytes
Cause: The rewritten OLAP DML expression was larger than the output buffer.
Action: Create a smaller OLAP DML expression.
ORA-36887: (XSSRF06) Error rewriting OLAP DML expression. Column name
string is not a valid ADT column.
Cause: The column name passes does not exist.
Action: Only reference columns that exist.
ORA-36902: (XSAGDNGL43) In AGGMAP workspace object, the MODEL
workspace object is not a model over a base dimension of the AGGMAP.
Cause: Model may include equations others than dimension values, or blocks
other than simple blocks.
Action: Make sure model only includes the simple blocks with dimension values.
ORA-36904: (XSAGDNGL44) In AGGMAP workspace object, RELATION
workspace object occurs after a dynamic model. The dynamic model must be the
last calculation within the AGGMAP.
Cause: Before the current relation, dynamic model exists.
Action: Make sure the dynamic model is the last statement.
ORA-33000 to ORA-37999 20-59
ORA-36910: (XSAGDNGL47) In AGGMAP workspace object, DYNAMIC MODEL
workspace object can only edit the top level of its matching relation hierarchy.
Cause: The model attempted to edit a child node in the relation hierarchy.
Action: Remove this attempt from the model definition.
ORA-36912: (XSAGDNGL48) In AGGMAP workspace object, MODEL workspace
object cannot be simultaneous.
Cause: The aggmap contained a simultaneous model.
Action: Change the model definition so that it is no longer simultaneous.
ORA-36913: (XSAGDNGL49) In AGGMAP workspace object, LOAD_STATUS
object workspace object must be an undimensioned VALUESET over the
relation dimension.
Cause: The object refered to by the LOAD_STATUS clause of the aggmap wasn't
an undimensioned valueset over the related dimension
Action: Change the aggmap definition so that it doesn't refer to an invalid object
ORA-36914: (XSAGDNGL50) In AGGMAP workspace object, LOAD_STATUS
valueset workspace object contains both a child and its ancestor.
Cause: The LOAD_STATUS valueset is not allowed to contain both a dimension
value and an ancestor of that value.
Action: Perform a limit remove ancestors on the valueset and confirm that the
result matches the intended load.
ORA-36920: (XSVPMVTOPART01) workspace object cannot become anonymous
because it has properties.
Cause: The OLAP DML command would result in a named object becoming an
anonymous object, but the object had one or more properties associated with it.
Action: Remove the properties using the PROPERTY command. In some cases an
UPDATE may be required before the command can proceed.
ORA-36921: (XSVPMVTOPART02) workspace object and workspace object are not
in the same analytic workspace.
Cause: The OLAP DML command requires certain objects to be in the same
analytic workspace, and the command string specified objects from two different
analytic workspaces.
Action: If more than one analytic workspace is attached to the session, make sure
that the object names given in the command are unique across all attached analytic
workspaces. Use qualified object names (QON's) if necessary.
ORA-36922: (XSVPMVTOPART03) workspace object is the target of an external
partition of a partitioned variable.
Cause: An attempt was made to perform some prohibited operation on a variable
which is itself a partition of some other variable.
Action: If desired, use the CHGDFN command to DROP the partition from the
partitioned variable, and then run the command again.
ORA-36923: (XSVPMVTOPART04) workspace object is not a LIST or RANGE
PARTITION TEMPLATE.
Cause: The user ran a command that only operates on a LIST or RANGE partition
template (or a variable dimensioned by a LIST or RANGE partition template) on
some other kind of analytic workspace object.
20-60 Oracle Database Error Messages
Action: Rerun the command on a LIST or RANGE partition template or a variable
dimensioned by a LIST or RANGE partition template.
ORA-36924: (XSVPMVTOPART05) workspace object is not in a COMPOSITE.
Cause: The OLAP DML command expected that the variable would be
dimensioned by a composite containing the specified dimension, the specified
dimension within a composite.
Action: Rerun the command on some variable is dimensioned by a composite
containing the specified dimension.
ORA-36930: Cannot start a recursive call to Oracle OLAP because a ROLLBACK
past an UPDATE to an attached analytic workspace has been performed.
Cause: ROLLBACK past the UPDATE of one of the attached Analytic Workspaces
was called. A recursive Oracle OLAP call cannot be made until the control returns
to the initial OLAP call and the affected Analytic Workspaces detached.
Action: Change the called SQL procedure to avoid the ROLLBACK
ORA-36950: (XSFCAST22) The list of string values cannot have more than number
members. You supplied number.
Cause: There are more than the maximum number of OFFSET or PERIODICITY
values.
Action: Remove some of the values.
ORA-36951: (XSFCAST28) The ALLOCLAST parameter cannot be set to YES unless
PERIODICITY specifies more than one cycle.
Cause: ALLOCLAST was set to YES when PERIODICITY specified a single value
rather than a list of nested cycles.
Action: Set ALLOCLAST to FALSE (the default), or specify more than one value
for PERIODICITY (in the form of a parenthesized list).
ORA-36952: (XSFCAST23) You cannot specify a cycle number when querying the
string forecasting option.
Cause: A cycle number was specified in a call to FCQUERY to retrieve forecast
data not related to a cycle.
Action: Remove the cycle specification from the call to FCQUERY.
ORA-36954: (XSFCAST24) The cycle number must be between 1 and number. You
specified number.
Cause: A cycle number less than 1 or greater than the maximum value was
specified in a call to FCQUERY.
Action: Specify a number in the indicated range.
ORA-36956: (XSFCAST25) There are only number PERIODICITY values. You
cannot specify more OFFSET values.
Cause: More OFFSET values were specified than PERIODICITY values.
Action: Supply only as many OFFSETs as there are PERIODICITY values.
ORA-36958: (XSFCAST26) The OFFSET value for cycle number cannot be greater
than the cycle's PERIODICITY, which is number. You specified number.
Cause: The OFFSET for a cycle exceeded the PERIODICITY for that cycle.
Action: Supply an OFFSET less than or equal to the PERODICITY for the
corresponding cycle.
ORA-33000 to ORA-37999 20-61
ORA-36960: (XSFCAST27) The value of the string expression must be an odd
number. You specified number.
Cause: An even number was given for an option that requires an odd number.
Action: Supply an odd number or let the option default.
ORA-36961: Oracle OLAP is not available.
Cause: The user attempted to utilize functionality found only in Oracle OLAP, but
OLAP has not been enabled in the executable.
Action: Install the Oracle OLAP option
ORA-36962: (XSRELTBL08) string is not a valid workspace object.
Cause: The specified value does not exist in the dimension.
Action: Specify an existing value of the dimension.
ORA-36963: (XSRELTBL16) INHIERARCHY object workspace object should be a
valid valueset or boolean variable.
Cause: Invalid valueset or variable was specified.
Action: Specify a valid valueset or variable.
ORA-36964: (XSRELTBL09) workspace object is not a valid level relation.
Cause: The specified level relation was not consistent with the parentage
hierarchy.
Action: Fix one or both of the relations involved so that all parents are at a higher
level than their children.
ORA-36965: (XSRELTBL17) Invalid LEVELORDER valueset workspace object.
Cause: Invalid LEVELORDER valueset was specified.
Action: Specify a valid valueset.
ORA-36966: (XSRELTBL10) workspace object must be a dimension.
Cause: The qualified object must be a dimensions.
Action: Remove the named object from the QDR.
ORA-36967: (XSRELTBL18) Invalid INHIERARCHY valueset workspace object.
Cause: Invalid valueset was specified.
Action: Specify a valid valueset.
ORA-36968: (XSRELTBL11) Invalid relation workspace object.
Cause: Non-object or an object other than a RELATION was specified as source or
destination.
Action: Specify RELATION objects.
ORA-36969: (XSRELTBL19) Merged family relation cannot take INHIERARCHY
option.
Cause: INHIERARCHY option was specified.
Action: Remove INHIERARCHY option.
ORA-36970: (XSRELTBL12) workspace object must be a self-relation.
Cause: The specified source relation was not a self-relation.
Action: Specify a self-relation as the source.
20-62 Oracle Database Error Messages
ORA-36971: (XSRELTBL19) Merged family relation cannot take LEVELORDER
option.
Cause: LEVELORDER option was specified.
Action: Remove LEVELORDER option.
ORA-36972: (XSRELTBL13) Relation workspace object must be dimensioned by
workspace object.
Cause: Destination relation is not dimensioned by source relation dimension.
Action: Give a correct destination relation.
ORA-36974: (XSRELTBL14) workspace object is not a BOOLEAN variable
dimensioned by all the dimensions of the hierarchy.
Cause: The named variable had either the wrong data type or the wrong
dimensions.
Action: Specify a BOOLEAN variable dimensioned by all the dimensions of the
hierarchy.
ORA-36975: (XSRELTBL15) You must specify a USING clause naming a relation
with same level dimension as LEVELORDER valueset workspace object.
Cause: USING was omitted from the HIERHEIGHT command, or specified a
relation containing values of a different dimension than the LEVELORDER
valueset.
Action: Provide a USING clause naming a relation containing values from the
correct level dimension. --------------------------------------------------------------
ORA-36976: (XSRELGID00) Invlid GROUPINGID destination relation or variable
workspace object.
Cause: Non-Object or invalid relation or invlid variable.
Action: Specify the valid relation or variable.
ORA-36977: (XSRELGID17) The GROUPINGID command does not support
hierarchies with more than 126 levels.
Cause: The user specified a hierarchy with more than 126 levels.
Action: Decrease the number of levels in the hierarchy.
ORA-36978: (XSRELGID01) workspace object must be a self-relation.
Cause: Source relation is not a self-relation.
Action: Specify a self-relation as the source relation.
ORA-36979: (XSRELGID18) Property number can only be set by the GROUPINGID
command.
Cause: You tried to set the $GID_DEPTH property.
Action: Stop to set the $GID_DEPTH property.
ORA-36980: (XSRELGID02) Variable workspace object must have a numeric data
type.
Cause: The destination variable does not have a numeric data type.
Action: Make sure the variable is numeric.
ORA-36981: (XSRELGID19) The format of the GROUPINGID function is:
GROUPINGID(gidrel1 [gidrel2]...)
Cause: Bad syntax
ORA-33000 to ORA-37999 20-63
Action: Correct syntax
ORA-36982: (XSRELGID03) The destination variable/relation workspace object
must be dimensioned by all dimensions of the source relation workspace object
that have more than one value in status.
Cause: Destination variable/relation does not have enough dimensionality to
hold the result from the multi-dimensional source relation.
Action: Either limit the status of hierarchy dimensions or redefine the destination
variable/relation with the extended dimensionality
ORA-36983: (XSRELGID20) The groupingid relation workspace object repeats.
Cause: The groupingid relation repeated.
Action: Remove the duplicated groupingid relation.
ORA-36985: (XSRELGID21) The source relation can be omitted only when using
both surrogate GID and level order valueset.
Cause: Source relation was not specified.
Action: Specify the source relation or both surrogate gid and level order valueset.
ORA-36986: (XSRELGID05) Relation workspace object must be dimensioned by
workspace object.
Cause: The destination relation is not dimensioned by the dimension of the source
relation.
Action: Redefine the destination relation or choose another relation with the
correct dimensionality.
ORA-36988: (XSRELGID06) The related dimension of relation workspace object
must be of type NUMBER.
Cause: The related dimension of the destination relation has the wrong data type.
Action: Redefine the destination relation or choose another relation whose related
dimension is of type NUMBER.
ORA-36989: (XSRELGID23) GROUPSET and ROLLUP options in GROUPINGID
require the destination relation.
Cause: Either variable or surrrogate dimension was specified as destination.
Action: Specify the destination relation.
ORA-36990: (XSRELGID07) The level relation workspace object should be
dimensioned by a level dimension.
Cause: The level relation is not dimensioned by a level dimension.
Action: Redefine the level relation or choose another relation with the correct
dimensionality.
ORA-36991: (XSRELGID08) The level relation and level order valueset provide
inconsistent level mappings.
Cause: There is a conflict between the hierarchy/level relation and the level order
valueset.
Action: Choose objects that do not conflict.
ORA-36992: (XSRELGID09) A level relation is needed to produce a surrogate
dimension gid.
Cause: A level relation was not specified.
20-64 Oracle Database Error Messages
Action: Specify a level relation.
ORA-36993: (XSRELGID10) OBJECT workspace object must be a VARIABLE,
RELATION, or a numeric SURROGATE DIMENSION based on the level
dimension workspace object.
Cause: not a surrogate dimension, or the surrogate dimension is not based on the
level dimension.
Action: modify/change the surrogate dimension.
ORA-36994: (XSRELGID11) The SURROGATE DIMENSION workspace object
must be numeric.
Cause: The surrogate dimension is not numeric
Action: Change the surrogate dimension as numeric
ORA-36995: (XSRELGID12) There are duplicate values in the surrogate dimension
gid. Use the levelorder option to resolve the ambiguity.
Cause: more than 1 hierarchies in the current computing scope.
Action: use inhierarchy to limit
ORA-36996: (XSRELGID13) Valueset workspace object should be defined over
dimension workspace object.
Cause: Valueset doesn't match the dimension
Action: Change the valueset's dimension
ORA-36997: (XSRELGID14) For variable or relation grouping ids, a level relation is
needed when a level order valueset is specified.
Cause: no level relation exists with level order valueset.
Action: provide the level relation.
ORA-36998: (XSRELGID15) LEVEL ORDER VALUESET workspace object and
LEVEL RELATION workspace object have the different level dimensions.
Cause: either level order valueset or level relation has wrong level dimension.
Action: choose the correct level dimension
ORA-36999: (XSRELGID16) OBJECT workspace object is not a surrogate
dimension, a source relation must be specified when creating any non-surrogate
grouping id.
Cause: use variable/relation gid without providing the source relation
Action: use the surrogate or provide the source relation
ORA-37000: (NOTALIAS00) workspace object is not an ALIAS DIMENSION of
workspace object.
Cause: The user specified an object which is not alias dimension of the first
dimension
Action: Specify an alias dimension of the first dimension
ORA-37001: You have one or more attached but unupdated analytic workspaces.
Cause: The user has attempted to shut down OLAP, but they have active analytic
workspaces whose changes have not been saved.
Action: Either issue the update command to update the AWs, or pass TRUE as the
force parameter to dbms_aw.shutdown()
ORA-33000 to ORA-37999 20-65
ORA-37002: Oracle OLAP failed to initialize. Please contact Oracle OLAP technical
support.
Cause: A severe error occurred while initializing OLAP.
Action: Contact support (and possibly OLAP development) for help in debugging
the issue.
ORA-37003: (AWLISTALL01) number readers
Cause: used in AW(LISTALL) output formatting when %d is 0
Action: None
ORA-37004: (AWLISTALL02) number reader
Cause: used in AW(LISTALL) output formatting when %d is 1
Action: None
ORA-37005: (AWLISTALL03) number readers
Cause: used in AW(LISTALL) output formatting when %d is > 1
Action: None
ORA-37006: (AWLISTALL04) number writers
Cause: used in AW(LISTALL) output formatting when %d is 0
Action: None
ORA-37007: (AWLISTALL05) number writer
Cause: used in AW(LISTALL) output formatting when %d is 1
Action: None
ORA-37008: (AWLISTALL06) number writers
Cause: used in AW(LISTALL) output formatting when %d is > 1
Action: None
ORA-37010: (XSACQUIRE_DIFFAW) When using the CONSISTENT WITH clause,
all objects must come from the same analytic workspace.
Cause: The ACQUIRE command cannot keep objects from several workspaces
consistent with each other
Action: Omit the CONSISTENT WITH clause or make sure all objects being
acquired belong to the same analytic workspace.
ORA-37011: (XSACQUIRE_LOCKED) Object workspace object is locked by another
user.
Cause: Could not acquire (or acquire consistent) the object, since it is locked by
another user
Action: Try to acquire this object later
ORA-37012: (XSACQUIRE_TIMEOUT) Object workspace object is locked by
another user and the WAIT timed out.
Cause: Could not acquire (or acquire consistent) the object for a while, since it is
locked by another user
Action: Try to acquire this object later
ORA-37013: (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace
object, since doing so would cause a deadlock.
Cause: Waiting to acquire the object would cause a deadlock
20-66 Oracle Database Error Messages
Action: Release some other object that another user is waiting for and try to
acquire this object again.
ORA-37014: (XSACQUIRE_ACQUIRED) Object workspace object is already
acquired.
Cause: The object is already acquired
Action: Do not try to acquire this object again
ORA-37015: (XSACQUIRE_YNRESYNC) Object workspace object is ambiguously
listed to be acquired both with and without RESYNC.
Cause: The object is listed in with resync list and no resync list. Such usage is
ambiguous as to the user's intent on preserving or not preserving private changes.
Action: Do not list the object both with and without RESYNC
ORA-37016: (XSACQUIRE01) You must specify objects to acquire for the ACQUIRE
command.
Cause: A list of objects to acquire with or without resync is missing
Action: Specify the list of objects to acquire
ORA-37018: (XSACQUIRE03) Multiwriter operations are not supported for object
workspace object.
Cause: Multiwriter presently does not work for this object type
Action: Attach the AW in RW or EXCLUSIVE modes to modify this object.
ORA-37020: (XSMULTI01) Analytic workspace string is not in MULTI mode.
Cause: The workspace for an object is not in multiwriter mode. Hence, no
multiwriter operations are allowed on the objects in the workspace
Action: Attach the workspace in the multiwriter mode or do not use multiwriter
commands with it.
ORA-37021: (XSMULTI02) Object workspace object is not acquired.
Cause: The object must be acquired for this multiwriter operation
Action: Do not use this multiwriter operation on an object that is not acquired
ORA-37023: (XSMLTUPD01) Object workspace object cannot be updated without
dimension workspace object.
Cause: One cannot update an object if it is dimensioned by a maintained
dimension without updating that dimension or if the object is a relation and the
dimension is its target.
Action: Include the maintained dimension in the update list
ORA-37026: (XSMLTRESYNC01) Object workspace object cannot be resynced
without dimension workspace object.
Cause: One cannot resync an object if it is dimensioned by a maintained
dimension without updating that dimension or if the object is a relation and the
dimension is its target.
Action: Include the maintained dimension in the update list
ORA-37027: (XSMLTRESYNC02) Object workspace object cannot be resynced
without modified object workspace object because they share a modified
composite dimension.
Cause: When one resyncs an object that is dimensioned by a composite
dimension, the composite dimension is resynced automatically, dropping all new
ORA-33000 to ORA-37999 20-67
tuples. This cannot be done, however, if the automatic resync of the composite
dimension might cause data in an object that shares the composite dimension to
become NA.
Action: Resync both objects together. Alternatively, you can try to acquire the
other object (that will ensure that the composite dimension is locked in the latest
generation and will not be resynced when resyncing the first object), resync the
first object, and release the other object.
ORA-37028: (XSMLTRESYNC03) Object workspace object cannot be resynced
without modified object workspace object because they share a modified
dimension map.
Cause: When one resyncs an object that is dimensioned by a dimension map, the
dimension map is resynced automatically, dropping all changes. This cannot be
done, however, if the automatic resync of the dimension map might cause data in
an object that shares the dimension map to become NA.
Action: Resync both objects together. Alternatively, you can try to acquire the
other object (that will ensure that the dimensions map is locked in the latest
generation and will not be resynced when resyncing the first object), resync the
first object, and release the other object.
ORA-37030: (XSMLTMAINT01) You cannot maintain workspace object because it is
not ACQUIRED.
Cause: One cannot maintain a dimension in a multiwriter AW if it is not acquired.
Action: Acquire the dimension first.
ORA-37031: (XSMLTMAINT02) You cannot DELETE values of dimension
workspace object in MULTI mode.
Cause: DELETE is allowed in multiwriter mode only for SESSION dimension
members
Action: Attach the AW in a R/W mode and perform the DELETE operation
ORA-37032: (XSMLTMAINT03) You cannot MAINTAIN partition template
workspace object in MULTI mode.
Cause: User attempted to add or remove values from a LIST partition template's
lists while the AW containing the partition template was attached in multiwriter
mode.
Action: Do the maintenance in read only or read-write mode.
ORA-37035: (XSMLTDCL01) You can only DEFINE SESSION objects in analytic
workspace string because it is attached in MULTI mode.
Cause: Persistent object definition in multiwriter mode is not allowed.
Action: Do all persistent object definitions in read-write mode.
ORA-37036: (XSMLTDCL02) You cannot DELETE objects in analytic workspace
string because it is attached in MULTI mode.
Cause: One cannot delete objects in an analytic workspace attached in MULTI
mode.
Action: Do all object in read-only or read-write mode.
ORA-37037: (XSMLTDCL03) You cannot RENAME objects in analytic workspace
string because it is attached in MULTI mode.
Cause: One cannot rename objects in an analytic workspace attached in MULTI
mode.
20-68 Oracle Database Error Messages
Action: Do all persistent object maintenance in read-write mode.
ORA-37038: (XSMLTDCL04) You cannot change definitions of objects in analytic
workspace string because it is attached in MULTI mode.
Cause: One cannot used CHGDFN command on objects in an analytic workspace
attached in MULTI mode.
Action: Do all persistent object maintenance in read-write mode.
ORA-37039: (XSMLTDCL05) You cannot maintain triggers in analytic workspace
string because it is attached in MULTI mode.
Cause: One cannot use TRIGGER command on objects in an analytic workspace
attached in MULTI mode.
Action: Do all persistent object maintenance in read-write mode.
ORA-37040: (XSACQUIRE_DEP_LOCKED) Composite, concat, dimension map, or
internal partition workspace object is locked by another user.
Cause: Some object required locking a composite, concat, dimension map, or
internal partition, which is locked by another user
Action: Try to acquire this object later
ORA-37041: (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or
internal partition workspace object is locked by another user and the WAIT
timed out.
Cause: Some object required locking a composite, concat, dimension map, or
internal partition, which could not be locked for a while, since it is locked by
another user
Action: Try to acquire this object later
ORA-37042: (XSACQUIRE_DEP_DEADLOCK) Cannot wait to acquire composite,
concat, dimension map, or internal partition workspace object, since doing so
would cause a deadlock.
Cause: Some object required locking a composite, concat, dimension map, or
internal partition, which would cause a deadlock
Action: Release some other object that another user is waiting for and try to
acquire this object again.
ORA-37043: (XSACQUIRE_DEP_OLDGEN) Composite, concat, dimension map, or
internal partition workspace object cannot be locked, since another user has
committed a new one already.
Cause: Some object required locking a composite, concat, dimension map, or
internal partition in the present generation, which is not possible, since a newer
generation already exists.
Action: Try to acquire the main object with resync
ORA-37044: (XSACQUIRE_OLDGEN) Cannot acquire object workspace object
without resync.
Cause: Could not acquire the object without resync because another user has
committed a newer version of it already.
Action: Try to acquire this object with resync parameter
ORA-37050: (XSMLTDCL06) You cannot use the RELATION command with
workspace object because analytic workspace string is attached in MULTI mode.
ORA-33000 to ORA-37999 20-69
Cause: One cannot use the RELATION command on objects in an analytic
workspace attached in MULTI mode.
Action: Change the default relation when the analytic workspace is attached in
RW or Exclusive mode.
ORA-37060: (XSMCSESS08) number is not a valid custom member in dimension
workspace object.
Cause: No custom member or invalid custom member
Action: Create the custom member or use the correct custom member
ORA-37069: You may not execute a parallel OLAP operation against the EXPRESS
AW.
Cause: A parallel OLAP command attempted to execute against EXPRESS.
Action: Contact Oracle support. Users should not see this message.
ORA-37070: You may not execute OLAP DML programs in a parallel query session.
Cause: The user attempted to execute a DML program inside of a parallel query
session, perhaps in parallel aggregate
Action: Adjust the job so that a program does no need to be executed, or disable
parallelism
ORA-37071: You may not execute a parallel OLAP operation against updated but
uncommitted AW string.
Cause: The user attempted to use a parallel feature against an AW which they
updated but which has not been committed
Action: Commit the current changes
ORA-37072: (XSMCSESS00) Object workspace object has the wrong type.
Cause: The object is not of the object type specified in the APPLY clause
Action: Specify the correct object type
ORA-37073: (XSMCSESS01) Applied relation workspace object must be
dimensioned by dimension workspace object.
Cause: Applied relation has the different dimension from the dimension currently
being maintained
Action: Maintain relation dimension
ORA-37074: (XSMCSESS02) Variable workspace object has no default aggmap.
Cause: The applied variable has no default aggmap
Action: Use variable with the default aggmap or aggmap directly
ORA-37075: (XSMCSESS03) You cannot rename a session-only dimension value.
Cause: The user tried to apply MAINTAIN RENAME to a SESSION value.
Action: Delete the old value and add a new one with the desired name.
ORA-37076: (XSMCSESS04) workspace object is not the type of dimension that can
have session-only values. Valid types are TEXT, NTEXT, ID, NUMBER, and
CONCAT with the UNIQUE attribute.
Cause: The user tried to add a SESSION value to a dimension type that does not
support SESSION values.
Action: Use a dimension of one of the listed types.
20-70 Oracle Database Error Messages
ORA-37077: (XSMCSESS05) Object workspace object is specified more than once.
Cause: The same object name was given more than once in the apply clause or in
the step dimension list.
Action: Remove the repetitions.
ORA-37078: (XSMCSESS06) The dimension being maintained (workspace object)
cannot also be used as a step dimension.
Cause: The dimension being maintained was named as a step dimension.
Action: Remove this dimension from the list of step dimensions.
ORA-37079: (XSMCSESS07) Aggmap workspace object cannot be used for
AGGREGATE.
Cause: The current aggmap may be for ALLOCATE
Action: Choose the correct aggmap for AGGREGATE only.
ORA-37080: Advice requested for hierarchy with too many levels
Cause: A request was made for advice on a hierarchy with more levels than are
supported.
Action: Only request advice for hierarchies with less than 32 levels.
ORA-37082: Invalid percent
Cause: A request was made for advice with an illegal percent value.
Action: Request between 0 and 100 percent precomputation.
ORA-37083: Invalid object string
Cause: A request was made for advice with an illegal object name.
Action: Request using valid object names.
ORA-37084: Output valueset string must match string's dimensionality
Cause: A request was made for advice for a relation with different dimensionality
from the output valueset.
Action: Request using objects that have the same dimensionality.
ORA-37086: string is not a valueset
Cause: An operation was attempted that supports only valuesets as precompute
expressions in an aggmap, yet a different kind of precompute expression was
used.
Action: Replace this limit expression with an equivalent valueset and retry the
operation. General precompute expressions are deprecated.
ORA-37093: (XSOBJORG_BAD_CUBE) invalid property "string" specified for cube
"string.string"
Cause: Either the specified cube did not have an AW organization, or the
specified property did not apply to cubes.
Action: Specify a property that applies to cubes and a cube with an AW
organization.
ORA-37094: (XSOBJORG_BAD_DIM) invalid property "string" specified for
dimension "string.string"
Cause: Either the specified dimension did not have an AW organization, or the
specified property did not apply to dimensions.
ORA-33000 to ORA-37999 20-71
Action: Specify a property that applies to dimensions and a dimension with an
AW organization.
ORA-37095: (XSOBJORG_BAD_MEAS) invalid property "string" specified for
measure "string.string.string"
Cause: Either the specified measure did not have an AW organization, or the
specified property did not apply to measures.
Action: Specify a property that applies to measures and a measure with an AW
organization.
ORA-37096: (XSOBJORG_BAD_ATTR) invalid property "string" specified for base
attribute "string.string.string"
Cause: Either the specified base attribute did not have an AW organization, or the
specified property did not apply to base attribute.
Action: Specify a property that applies to base attributes and a base attribute with
an AW organization.
ORA-37097: (XSOBJORG_BAD_DIM_LEVEL) invalid property "string" specified
for dimension level "string.string.string"
Cause: Either the specified dimension level did not have an AW organization, or
the specified property did not apply to dimension levels.
Action: Specify a property that applies to dimension levels and a dimension level
with an AW organization.
ORA-37098: (XSOBJORG_BAD_MODEL) invalid property "string" specified for
dimension calculation model "string.string.string"
Cause: Either the specified dimension calculation model did not have an AW
organization, or the specified property di not apply to dimension calculation
models.
Action: Specify a property that applies to dimension calculation models and a
dimension calculation model with an AW organization.
ORA-37099: (XSOBJORG_BAD_DIMALITY) invalid property "string" specified for
dimensionality "string.string.string"
Cause: Either the specified dimensionality did not have an AW organization, or
the specified property did not apply to dimensionalities.
Action: Specify a property that applies to dimensionalities and a dimensionality
with an AW organization.
ORA-37100: (XSUNCOMMITTED) You have one or more updated but
uncommitted analytic workspaces.
Cause: The user has attempted to shut down OLAP, but they have active analytic
workspaces whose changes have not been saved.
Action: Issue the commit command. ---- 37101 - 37110 are reserved for partitioned
variables ----
ORA-37101: (XSVPART01) Partitioning information can only be given for variables
dimensioned by a PARTITION TEMPLATE.
Cause: User attempted to define or reference an AW object with the "all internal"
phrase or internal / external partition list, but the object was not a variable, was
not dimensioned by a partition template, or was an already existing target of an
external partition.
20-72 Oracle Database Error Messages
Action: Eliminate phrases specific to partitioned variables from the definition
string, or dimension the variable by a partition template.
ORA-37102: (XSVPART02) Invalid partition name string.
Cause: The user gave an invalid partition name. When defining a partitioned
variable, this message indicates that the partition name does not exist in the
partition template. In any other context, it indicates that the partitioned variable or
partition template does not have a partition with the given name.
Action: Supply a valid partition name.
ORA-37103: (XSVPART03) The dimensionality or datatype of workspace object
does not match the dimensionality or datatype of the partition.
Cause: User attempted to define a partitioned variable with an external partition,
but the target of the external partition had incorrect dimensionality or datatype.
Action: Pick a different target variable. The target variable must be dimensioned
by exactly the same dimensions, composites, and partition templates, in the same
order, as are specified in the partition template, and must have the exact same
datatype (including width, precision, and scale) as the partitioned variable itself.
ORA-37104: (XSVPART04) A partitioned variable must be dimensioned by a single
partition template only.
Cause: User attempted to define a partitioned variable with more than one
partition templates, or a partition template and one or more other dimensions, in
the dimension list.
Action: Use only a partition template in the dimension list of the variable. All
dimensions of the variable must be included in the definition of the partition
template.
ORA-37105: (XSVPART05) Only variables dimensioned by a CONCAT
PARTITION TEMPLATE can have string partitions.
Cause: User attempted to create an external partition on a partitioned variable,
but the variable was dimensioned by a RANGE or LIST partition template.
Action: Declare the partition INTERNAL instead of EXTERNAL, or use a
CONCAT partition template in place of the RANGE or LIST partition template.
ORA-37106: (XSVPART06) Invalid partition name number.
Cause: The user gave an invalid partition name.
Action: Supply a valid partition name.
ORA-37107: (XSVPART07) Attempt to write to non-existent partition of workspace
object.
Cause: Some action attempted to write data to a partitioned variable, but the
variable didn't have a partition for that data. This can result from a partition
template that does not assign all possible dimension values to some subcube, or
from a partitioned variable that does not have a partition for one of the partitions
defined by the partition template.
Action: Make sure that the cell being written is assigned to some partition by the
partition template, and that the variable has an actual partition associated with the
partition of the template. Use the CHGDFN template DEFINE... command to
define new partitions within the template, and the CHGDFN variable ADD...
command to add new partitions to the variable. Alternatively, the
PARTWRITEERR can be set to false, in which case data being written to a
non-existent partition will be silently discarded.
ORA-33000 to ORA-37999 20-73
ORA-37108: (XSVPART08) workspace object has an AGGCOUNT, but workspace
object does not.
Cause: An attempt was made to add a partition to a partitioned variable. Either
the partition was defined WITH AGGCOUNT and the partitioned variable was
not, or the partitioned variable was defined WITH AGGCOUNT and the partition
was not.
Action: Use CHGDFN ADD AGGCOUNT or CHGDFN DROP AGGCOUNT to
either add or remove an AGGCOUNT from either the partition or the partitioned
variable.
ORA-37109: (XSVPART09) Partition workspace object and its parent variable
workspace object cannot both be specified.
Cause: Partition and its parent partition were operated upon together.
Action: Remove the partition from the object list.
ORA-37111: Unable to load the OLAP API sharable library: (string)
Cause: This happens if: (1) the OLAP API sharable library is missing. (2) a
sharable library upon which the OLAP API sharable library depends is missing.
(3) the OLAP API sharable library is the wrong version.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Customer Support.
ORA-37113: OLAP API initialization error: (string)
Cause: OLAP API initialization failed.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Customer Support.
ORA-37114: OLAP API bootstrap error: (string)
Cause: OLAP API bootstrapping failed.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Customer Support.
ORA-37115: New OLAP API history is not allowed
Cause: If there are active OLAP API sessions, it is not allowed to start a new
OLAP API history by setting _olapi_history_retention parameter to true.
Action: Wait until all active OLAP API sessions terminate before resetting _olapi_
history_retention parameter to true.
ORA-37116: OLAP API table function error: (string)
Cause: OLAP API table function failed.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Customer Support.
ORA-37117: olapi history retention has been disabled
Cause: Under certain circumstances, for example, when the database is read only,
olapi history retention is not possible because it requires updating persistent tables
from time to time. If olapi history retention has been disabled, setting _olapi_
history_retention parameter to true has no effect.
20-74 Oracle Database Error Messages
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Customer Support.
ORA-37118: The OLAP API library was not preloaded.
Cause: In shared-server mode, the OLAP API library should be loaded during
process initialization to ensure that the C++ virtual table addresses are identical in
all shared-server processes. The OLAP API session was executing in a process in
which the library had not been loaded.
Action: Set option _XSOLAPI_LOAD_AT_PROCESS_START to SHARED_
SERVER or ALWAYS, restart the instance, and try again.
ORA-37119: Incompatible OLAP API library load address
Cause: The OLAP API session was executing in a process in which the OLAP API
sharable library was loaded which was at a different address than the process in
which the OLAP API session originated.
Action: Set option _XSOLAPI_LOAD_AT_PROCESS_START to ALWAYS, restart
the instance, and try again.
ORA-37120: expression string is null
Cause: expression parser received a null string for syntax analysis.
Action: Prepare a non-null and well-formed MDX query string and try again.
ORA-37121: AW Spreadsheet invalidated
Cause: While this cursor was open, a command was issued that changed the
underlying data to become inconsistent.
Action: Perform the query again, avoid performing dimension maintenance and
cache clears during spreadsheet processing.
ORA-37122: AW Session cache disabled
Cause: A SQL Spreadsheet was attempted while the AW Session cache was
disabled.
Action: Enable the session cache and perform the query again.
ORA-37123: (XSCCOMP17) Can not AGGREGATE workspace object(partition
number) because it depends on unaggregated compressed partition number.
Cause: attempted to use a feature not supported by CC's in the current AW
format
Action: Remove the unsupported feature from the aggmap, or upgrade the AW
ORA-37124: (XSCCOMP16) COMPRESSED COMPOSITES with string are not
supported in analytic workspace string because it has not been upgraded to
version string.
Cause: attempted to use a feature not supported by CC's in the current AW
format
Action: Remove the unsupported feature from the aggmap, or upgrade the AW
ORA-37126: (XSCCOMP01) The COMPRESSED COMPOSITE workspace object
can only be used as a base of a single variable.
Cause: The user attempted to DEFINE a variable dimensioned by a
COMPRESSED COMPOSITE, but that COMPRESSED COMPOSITE is already
being used by another VARIABLE.
ORA-33000 to ORA-37999 20-75
Action: Create a second COMPRESSED COMPOSITE for the second VARIABLE
or add a measure dimension to the first variable.
ORA-37127: (XSCCOMP02) The COMPRESSED COMPOSITE workspace object
must be last in the dimension list.
Cause: The user attempted to DEFINE a variable dimensioned by a
COMPRESSED COMPOSITE, but gave a slower varying dimension in the
dimension list.
Action: Put the COMPRESSED COMPOSITE last in the dimension list when
defining the VARIABLE.
ORA-37128: (XSCCOMP20) The partition template workspace object has already
used the COMPRESSED COMPOSITE workspace object.
Cause: The COMPRESSED COMPOSITE specified for either a variable or
partition template is already in use in another partition template.
Action: Define a different COMPRESSED COMPOSITE.
ORA-37129: (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE
workspace object using AGGMAP workspace object. All static MODEL
statements must precede all RELATION statements over the bases of the
COMPRESSED COMPOSITE.
Cause: The AGGMAP was defined with a MODEL statement after a RELATION
statement over a base of the COMPRESSED COMPOSITE.
Action: Change the AGGMAP so that the MODEL statements appear before the
RELATION statements.
ORA-37130: (XSCCOMP05) Cannot aggregate over COMPRESSED COMPOSITE
workspace object using AGGMAP workspace object because you must specify
AGGINDEX OFF when there is a PRECOMPUTE clause on a RELATION over
base workspace object.
Cause: A PRECOMPUTE clause was specified in the AGGMAP for a RELATION
over a base of a COMPRESSED COMPOSITE, but AGGINDEX was ON
Action: Remove the PRECOMPUTE clause from the AGGMAP, or add
AGGINDEX OFF
ORA-37131: (XSCCOMP06) Cannot aggregate over COMPRESSED COMPOSITE
workspace object using AGGMAP workspace object because the OPERATOR
string is not supported for bases of a COMPRESSED COMPOSITE.
Cause: The user specified an aggregation OPERATOR that is not supported by
COMPRESSED COMPOSITES.
Action: Use a MODEL for the calculation, or use an uncompressed COMPOSITE.
ORA-37132: (XSCCOMP07) Incremental aggregation over the dense DIMENSION
workspace object is not supported when aggregating a VARIABLE dimensioned
by a COMPRESSED COMPOSITE.
Cause: The status of the specified dimension did not include all detail cells.
Action: Add all detail cells to the status of the dimension and reissue the
AGGREGATE command.
ORA-37133: (XSCCOMP08) You cannot write into an aggregated VARIABLE
dimensioned by a COMPRESSED COMPOSITE. Use the CLEAR
AGGREGATES command to reenable write access.
20-76 Oracle Database Error Messages
Cause: The user attempted to store a value into to a variable dimensioned by a
compressed composite, and the variable had previously been precomputed using
the AGGREGATE command. Once the AGGREGATE command is run on a
variable dimensioned by a compressed composite, it becomes read-only until the
computed values are removed with the CLEAR command.
Action: Run the CLEAR AGGREGATES command to remove the computed
values from the variable and then rerun the failed operation. Note that CLEAR
AGGREGATES will remove all the data computed during the last AGGREGATE
command on this variable.
ORA-37134: (XSCCOMP09) You cannot add new values to workspace object because
it includes positions for precomputed aggregate values.
Cause: The user attempted to create a new position in a compressed composite,
either directly (using MAINTAIN MERGE or MAINTAIN ADD) or by storing a
value into the variable dimensioned by the compressed composite. This is not
allowed when the variable has been precomputed using the AGGREGATE
command. Once the AGGREGATE command is run on a variable dimensioned by
a compressed composite, the compressed composite becomes read-only until the
computed values are removed with the CLEAR command.
Action: Run the CLEAR AGGREGATES command to remove the computed
values from the variable and then rerun the failed operation. Note that CLEAR
AGGREGATES will remove all the data computed during the last AGGREGATE
command on this variable.
ORA-37135: (XSCCOMP19) The COMPRESSED COMPOSITE workspace object in
the current defined partition template should be unique or global.
Cause: The COMPRESSED COMPOSITE was neither unique nor global. Unique
means each subpartition should have different COMPRESSED COMPOSITEs;
Global means all subpartitions should use the same COMPRESSED COMPOSITE
if they use any COMPRESSED COMPOSITE.
Action: Redefine the partition template.
ORA-37136: (XSCCOMP11) Cannot ROLLUP dimension workspace object which is
a base of COMPRESSED COMPOSITE workspace object, use AGGREGATE
instead.
Cause: The user ran ROLLUP on a variable dimensioned by a COMPRESSED
COMPOSITE.
Action: Instead of using ROLLUP, generate an aggmap and use AGGREGATE
ORA-37137: (XSCCOMP12) You cannot CHGDFN workspace object because it is a
COMPRESSED COMPOSITE.
Cause: The user tried to CHGDFN a compressed composite
Action: If the change is desired then delete the old composite and create a new
one.
ORA-37138: (XSCCOMP13) You cannot delete values from workspace object
because it is an aggregated COMPRESSED COMPOSITE.
Cause: The user tried to MAINTAIN DELETE from an aggregated COMPRESSED
COMPOSITE.
Action: In order to perform this sort of maintenance the composite must first be
cleared. This can be done by running the CLEAR AGGREGATES command on the
variable dimensioning the composite. Note that this will remove all data
computed during the last AGGREGATE command.
ORA-33000 to ORA-37999 20-77
ORA-37139: (XSCCOMP14) Cannot AGGREGATE workspace object using
AGGMAP workspace object because you can not AGGREGATE a variable
dimensioned by a COMPRESSED COMPOSITE using an AGGMAP with a
PROTECT clause.
Cause: The user tried to AGGREGATE a variable dimensioned by a
COMPRESSED COMPOSITE with an AGGMAP that included a PROTECT clause.
Action: Modify the aggmap or create a new aggmap that does not include a
PROTECT clause and reaggregate.
ORA-37140: (XSCCOMP15) Cannot AGGREGATE partitioned variable workspace
object using AGGMAP workspace object because you cannot use the base of a
COMPRESSED COMPOSITE as a partition dimension.
Cause: The user tried to run aggregate on a partitioned variable with a partition
dimension that is a base of a COMPRESSED COMPOSITE.
Action: Repartition the data, drop the partition dimension from the aggmap, or
don't use COMPRESSED COMPOSITES.
ORA-37141: (XSSQLMDQ01) Invalid host variable syntax for MDQUERY
procedure.
Cause: The schema and analytic workspace name for the MDQUERY cursor
declaration were incorrectly specified.
Action: Specify the schema and awname as a host variable name preceded by a
colon, or as a text literal string of the form 'SCHEMA.AWNAME' or '*.*' (quotes
optional).
ORA-37142: (XSSQLMDQ02) Invalid host variable data type for MDQUERY
procedure: string expected.
Cause: The user specified a host variable that was not of the correct type.
Action: Choose a different host variable.
ORA-37143: (XSSQLMDQ03) string is not a valid analytic workspace name.
Cause: The user specified an analytic workspace name not qualified by a schema
name, or one or both components of the name exceed the maximum length
Action: Specify a schema-qualified analytic workspace name with components no
longer than 30 characters long.
ORA-37144: (MDQUERY01) string is not a valid metadata object type for
MDQUERY.
Cause: The user specified an unrecognized first argument to MDQUERY
Action: Specify a recognized object type (CUBE or DIMENSION)
ORA-37145: (XSTTS_PLAT) Cannot transport analytic workspace across platforms.
Cause: The user attempted to transport a tablespace containing an analytic
workspace from one platform to another.
Action: Use export/import to move an analytic workspace across platforms.
ORA-37146: (XSCCOMP18) The variable workspace object is already dimensioned
by the COMPRESSED COMPOSITE workspace object.
Cause: An attempt was made to define the partition template dimensioned by the
COMPRESSED COMPOSITE which had dimensioned the variable.
Action: Define the second COMPRESSED COMPOSITE.
20-78 Oracle Database Error Messages
ORA-37147: (XSCCOMP21) The variable workspace object must be in the current
operation group of the COMPRESSED COMPOSITE workspace object.
Cause: The variable dimensioned by the COMPRESSED COMPOSITE was not in
the object list of the current operation group. For AGGREGATE, all variables
dimensioned by the same COMPRESSED COMPOSITE also must use the same
aggmap
Action: Add the variable into the object list of the current operation group.
ORA-37148: (XSCCOMP22) workspace object is an aggregated COMPRESSED
COMPOSITE.
Cause: Defined the variable or partition template with the aggregated
COMPRESSED COMPOSITE.
Action: Clear the COMPRESSED COMPOSITE or use a new COMPRESSED
COMPOSITE
ORA-37149: (XSCCOMP23) Individual partitions of the variable dimensiond by
workspace object cannot be aggregated separately.
Cause: An attempt was made to aggregate partitions of a variable dimensioned
by a global COMPRESSED COMPOSITE partition template.
Action: Aggregate the partitioned variable dimensioned by the global
COMPRESSED COMPOSITE.
ORA-37150: line string, column string, string
Cause: expression syntax error was found in expression query string.
Action: Check the error message details and make the corrections.
ORA-37151: expression parser initialization error
Cause: expression parser initialization failed
Action: Please report this to Oracle Support Services.
ORA-37152: MDX query error: (string)
Cause: An exception occurred while MDX query was processed.
Action: Check the error message details and try again.
ORA-37153: unknown exception caught: (case string)
Cause: An unknown exception was caught while MDX query was processed.
Action: Please report it to Oracle Support Services.
ORA-37154: OLAP API initialization error: (case string)
Cause: OLAP API initialization failed.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Support Services.
ORA-37155: OLAP API bootstrap error: (case string)
Cause: OLAP API bootstraping failed.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Support Services.
ORA-37156: (string)
Cause: unknown
ORA-33000 to ORA-37999 20-79
Action: Check the error message details.
ORA-37157: expression syntax error was found in expression string but error text
was missing
Cause: This happened because the message file was missing.
Action: Make sure that the message file xsous.msb is located in $ORACLE_
HOME/olap/mesg and rerun your expression query.
ORA-37158: Bad clob or varray IN-args: (case string)
Cause: When in clob or varray mode, the PL/SQL mappings of OLAP API's IDL
interface methods were executed blindly with null clob/varray or non-null
clob/varray containing garbages.
Action: Do not blindly execute them as doing so does not make sense unless you
understand how OLAP API works internally.
ORA-37159: C++ virtual table addresses become invalid due to session migration in
shared server mode.
Cause: Exec-shield is the primary reason that caused this error in shared server
mode. When exec-shield is turned on, there is no way to ensure that the C++
virtual table addresses are identical in all shared-server processes.
Action: Set option _XSOLAPI_FIX_VPTRS to TRUE, restart the instance, and try
again.
ORA-37160: OLAP object does not exist
Cause: The specified OLAP object did not exist.
Action: Use an existing OLAP object instead.
ORA-37161: invalid privilege specified for OLAP object
Cause: An attempt was made to grant or revoke an invalid privilege on an OLAP
object.
Action: Specify a valid privilege.
ORA-37162: OLAP error
Cause: An exception was raised by OLAP code.
Action: Check error messages and correct any reported problems.
ORA-37163: cannot delete or truncate AW with dependent CUBES or CUBE
DIMENSIONS
Cause: User attempted to delete or truncate an AW which currently has a CUBE
or CUBE DIMENSION defined over it
Action: Drop the corresponding CUBE or CUBE DIMENSION before deleting the
AW
ORA-37164: The current SQL statement does not support this OLAP object
Cause: The OLAP object is not supported in the current SQL statement.
Action: Use a valid SQL command on the OLAP object.
ORA-37165: cannot use EIF IMPORT into a non-empty Analytic Workspace
(string.string)
Cause: An attempt was made to use EIF IMPORT to populate a non-empty
Analytic Workspace.
20-80 Oracle Database Error Messages
Action: Ensure that the target Analytic Workspace is empty before populating it
with EIF IMPORT.
ORA-37166: (XSOQ_BAD_OBJ) OLAP object "string.string" does not exist
Cause: The specified OLAP object did not exist.
Action: Use an existing OLAP object instead.
ORA-37167: (XSOQ_BAD_SUBOBJ) OLAP object "string.string.string" does not
exist
Cause: The specified OLAP object did not exist.
Action: Use an existing OLAP object instead.
ORA-37168: (XSOBJORG_UNSUPP_OBJ) unsupported OLAP object "string.string"
for OBJORG function
Cause: The specified OLAP object was of a type that is not supported by the
OBJORG function.
Action: Specify an OLAP object of a type that the OBJORG function supports.
ORA-37169: (XSOBJORG_UNSUPP_SUBOBJ) unsupported OLAP object
"string.string.string" for OBJORG function
Cause: The specified OLAP object was of a type that is not supported by the
OBJORG function.
Action: Specify an OLAP object of a type that the OBJORG function supports.
ORA-37170: (XSOBJORG_NA) The top-level object name argument to the OBJORG
function cannot be NA.
Cause: You passed NA as the second argument to the OBJORG function.
Action: Pass the name of the top-level object instead.
ORA-37171: dimension sources not specified
Cause: The user passed an empty or null collection to DBMS_AW.ADVISE_
SPARSITY
Action: Specify a valid set of dimension sources
ORA-37172: illegal dimension type
Cause: The user specified an invalid member of the DIMTYPE field in the
dimension sources argument
Action: Specify one of the valid enumerated values in DBMS_AW
ORA-37173: null dimension source data
Cause: The user specified NULL for one of the members of the dimension sources
argument
Action: Specify a value
ORA-37174: source SQL must be a SELECT statement
Cause: The user specified an INSERT, UPDATE, DELETE or other type of SQL
statement
Action: Specify a SQL SELECT statement instead
ORA-37175: column string is not a column of source data
Cause: A dimension column was specified which did not exist in the input data
Action: Specify one of the columns of the input data
ORA-33000 to ORA-37999 20-81
ORA-37176: argument string is not valid for the sparsity advisor
Cause: An invalid argument was passed to the advisor
Action: Specify a TABLE, VIEW or SELECT statement instead
ORA-37177: column string does not have any leaf values
Cause: The specified dimension column or fact table did not contain any leaf
values
Action: Populate the source data
ORA-37178: column string has no values
Cause: The specified dimension column did not contain any values
Action: Populate the source data
ORA-37179: expected at least one column for dimension string, got string
Cause: Not enough columns were specified for the dimension
Action: Specify more source columns, or change the dimension to another type
ORA-37180: expected exactly one column for dimension string, got string
Cause: Expected a single source column for the dimension. Either none or more
than one was specified.
Action: Specify exactly one column, or change the dimension to another type
ORA-37181: expected exactly string columns for dimension string, got string
Cause: Expected a certain number of source columns for the dimension. Either
none or the wrong number of columns was specified.
Action: Specify the right number of columns, or change the dimension to another
type
ORA-37182: you may only specify one dimension to partition
Cause: The user passed a DIMENSION_SOURCE_T to ADVISE_SPARSITY which
specified partitioning on more than one dimension
Action: Remove all but one of the partitioning requests
ORA-37183: illegal value string for PARTBY
Cause: The user passed a value other than PARTBY_DEFAULT, PARTBY_NONE
or PARTBY_FORCE to DBMS_AW.ADVISE_SPARSITY *Acton: Supply a legal
value instead
Action: None
ORA-37184: illegal value string for ADVMODE
Cause: The user passed a value other than ADVICE_DEFAULT, ADVICE_FAST or
ADVICE_FULL to DBMS_AW.ADVISE_SPARSITY *Acton: Supply a legal value
instead
Action: None
ORA-37185: length of string (string) exceeds maximum (string)
Cause: The user passed an excessively long value
Action: Specify a legal value
ORA-37186: null child value for parent (string) found in parent-child hierarchy
Cause: While reading values for a parent-child hierarchy, a NULL child value was
found for a non-NULL parent
20-82 Oracle Database Error Messages
Action: Correct the source table or SQL to return value parent and child pairs.
ORA-37187: null parent and child pair found in parent-child hierarchy
Cause: While reading values for a parent-child hierarchy, a row was retrieved
which had both null child and parent values.
Action: Correct the source table or SQL to return value parent and child pairs.
ORA-37188: unexpected null result while querying string
Cause: While querying the input fact table, the sparsity advisor unexpectedly got
no results, possibly due to changes being made during operation.
Action: Retry the operation ensuring that the data is not changed while the
sparsity advisor is running / Errors from 37200 - 37399 are reserved for events
ORA-37400: analytic workspace does not exist
Cause: The user attempted to create an OLAP MV or Table on an AW that does
not exist.
Action: Specify a valid AW in the ORGANIZATION CUBE clause
ORA-37401: you may not perform this operation on a system analytic workspace
Cause: The user attempted to create a CUBE MV or Table on a system-created
AW.
Action: Specify a valid AW in the ORGANIZATION CUBE clause
ORA-37402: analytic workspace object does not exist
Cause: The user attempted to create a CUBE MV or Table mapping to an object
that does not exist in the AW.
Action: Specify a valid AW object name in the ORGANIZATION CUBE clause.
ORA-37403: invalid analytic workspace object type
Cause: The user attempted to create a CUBE MV or Table mapping to an object
that is not the correct type.
Action: Specify a valid AW object name in the ORGANIZATION CUBE clause.
ORA-37404: Create table as select disallowed for CUBE ORGANIZED tables
Cause: User attempted to create a CUBE ORGANIZED table by doing a create
table as select.
Action: Do a create table followed by an insert as select
ORA-37405: unknown ORGANIZATION CUBE keyword
Cause: An unknown keyword was encountered while parsing the
ORGANIZATION CUBE clause
Action: Correct the ORGANIZATION CUBE syntax
ORA-37406: invalid option for a CUBE ORGANIZED table
Cause: An attempt to specify one or more options for a CUBE ORGANIZED table
such as: [NO]CACHE, NO LOGGING, CLUSTER, (NO)COMPRESS
Action: Remove the illegal option(s)
ORA-37407: invalid column type for a CUBE ORGANIZED table
Cause: A illegal column type is specified in a CUBE ORGANIZED table.
Action: Do not use column types such as LONG, LOB
ORA-33000 to ORA-37999 20-83
ORA-37408: Truncate table disallowed for CUBE ORGANIZED tables
Cause: User attempted to perform a TRUNCATE operation on a CUBE
ORGANIZED table
Action: Remove data with DELETE or drop the table and recreate it
ORA-37409: cannot delete or truncate AW used by CUBE ORGANIZED table
Cause: User attempted to delete or truncate an AW which currently has a CUBE
ORGANIZED table or MV defined over it
Action: Drop the corresponding table or MV before deleting the AW
ORA-37410: cannot delete or modify AW object referenced by CUBE ORGANIZED
table
Cause: User attempted to delete, chgdfn, or otherwise modify an object referenced
by a CUBE ORGANIZED table or MV
Action: Drop the corresponding table or MV before manipulating the object
ORA-37411: invalid object type
Cause: User referenced an invalid object type
Action: Use an appropriate object
ORA-37412: column not mapped by ORGANIZATION CUBE clause
Cause: Not all columns in the table or MV definition were mapped in the
ORGANIZATION CUBE clause
Action: Make sure that all columns are mapped
ORA-37413: column referenced multiple times in ORGANIZATION CUBE clause
Cause: The same column name was referenced multiple times inside of the
ORGANIZATION CUBE clause
Action: Supply unique mappings for each column
ORA-37414: dimension without mapping or hierarchy in ORGANIZATION CUBE
clause
Cause: A dimension was listed in the ORGANIZATION CUBE clause but no
mapping information was supplied
Action: Provide either a column mapping or hierarchy for the dimension
ORA-37415: AW schema must match TABLE or MATERIALIZED VIEW schema
Cause: An ORGANIZATION CUBE table or MV on top of an existing AW must
be created in the same schema as the AW
Action: Create the new object in the same schema as the AW
ORA-37416: multiple GROUPING IDs found for ORGANIZATION CUBE
Cause: Multiple GROUPING IDs for the ORGANIZATION CUBE TABLE or
MATERIALIZED VIEW
Action: Remove the duplicates
ORA-37417: variable does not have an AGGCOUNT
Cause: A COUNT clause was specified in the ORGANIZATION CUBE
description for a variable that does not have an AGGCOUNT
Action: chgdfn the variable to include an AGGCOUNT
ORA-37418: detail query cannot be derived
20-84 Oracle Database Error Messages
Cause: If an ORANIZATION CUBE MV is to automatically derive its loading
clause, then its definition query cannot contain set operators (eg UNION ALL), a
HAVING clause, START WITH or a SQL MODEL clause. The definition query
contains these or other unsupported syntax.
Action: Use an explicit ORGANIZATION CUBE clause, or simplify the defining
query.
ORA-37419: ORGANIZATION CUBE clause not allowed in explain mview
Cause: User tries to explain mview on a CREATE MATERIALIZED VIEW
statement that contains a ORGANIZATION CUBE clause.
Action: Remove the ORGANIZATION CUBE clause from the CREATE
MATERIALIZED MATERIALIZED VIEW statement.
ORA-37420: unsupported feature with CUBE ORGANIZED materialized view
Cause: User attempts operations such as creating a mv log on an CUBE
ORGANIZED MATERIALIZED VIEW.
Action: Do not do that.
ORA-37421: specified pseudocolumn is not supported by CUBE ORGANIZED
tables
Cause: An unsupported pseudocolumn was referenced with a CUBE
ORGANIZED table.
Action: Remove the unsupported pseudocolumn.
ORA-37422: illegal attempt to write to a calculated column
Cause: An attempt was made to write to a calculated column which could not be
written to.
Action: List only the non-calculated columns in your DML command.
ORA-37423: operation not supported on CUBE ORGANIZED tables
Cause: The attempted operation was not supported with CUBE ORGANIZED
tables.
Action: Do not attempt this operation on CUBE ORGANIZED tables.
ORA-37424: alter materialized view (MV) on a primary cube organized MV failed
to find secondary cube MV table
Cause: The operation failed due to the missing secondary cube materialized view
(MV) table in alter MV.
Action: Recreate the primary CUBE MV and make sure the secondary cube MV
table is correctly created.
ORA-37521: (HASHSCAN00) Dimension string contains duplicate values. Please
contact Oracle OLAP Technical Support.
Cause: The named dimension contains duplicate values.
Action: Contact Technical Support for instructions.
ORA-37522: (HASHSCAN01) You must specify the name of an existing TEXT or
NTEXT dimension.
Cause: the _HASHSCAN program was invoked with an invalid argument
Action: Provide a text expression yielding the name of an existing TEXT
dimension
ORA-33000 to ORA-37999 20-85
ORA-37527: (XSCHGDFN01) SESSION values of dimension string are being
automatically deleted.
Cause: When using CHGDFN to rebuild the hash index of a TEXT or NTEXT
dimension, SESSION values were encountered.
Action: Recreate the SESSION values after the CHGDFN command completes.
Information about the deleted values has been written to the trace file.
ORA-37528: (XSOBJORG_BAD_HIER) invalid property "string" specified for
hierarchy "string.string.string"
Cause: Either the specified hierarchy did not have an AW organization, or the
specified property did not apply to hierarchies.
Action: Specify a property that applies to hierarchy and a dimension with an AW
organization.
ORA-37530: (XSCCLOAD01) When aggregating between compressed partitions the
base dimensions of workspace object did not match the base dimensions of
workspace object.
Cause: When aggregating a partitioned variable the dimensionality of any
compressed partitions should be identical.
Action: Delete the upper partition and redefine it with a composite that matches
the lower partition. If it is dependent on multiple partitions with varying sparsity
you must first unify the the sparsity of the source partitions.
ORA-37531: (XSCCLOAD02) When aggregating between compressed partitions the
source partitions were aggregated with a different AGGMAP, or the
RELATIONS have changed since the source partitions were aggregated.
Cause: When aggregation crosses partition boundaries within a compressed
variable the individual partitions must all be aggregated using a similar aggmap
over the same unaltered relations.
Action: Modify the aggmap for the upper partition to more exactly match the
aggmap of the source partitions, or if the aggmap is already similar, re-aggregate
the source partitions to pick up any changes to the relations.
ORA-37541: Hierarchy element DIMENSION_MEMBER can aggregate into
element MEMBER_ANCESTOR through multiple paths.
Cause: When a low level hierarchy element can reach an aggregate element by
more than one path through the hierarchy, it is said to have multiple paths. The
danger is that the value of the low level hierarchy element will have its value
counted multiple times (once per path) in the total of the aggregate element.
Action: Eliminate multiple paths from the hierarchy.
ORA-37542: DIMENSION_MEMBER makes hierarchy HIERARCHY1 unbalanced.
Cause: A hierarchy is balanced if: 1) All members of a level are at the same depth
from the root of the hierarchy and 2) All the members in different levels are at
different depths from the root of the hierarchy.
Action: Fix the hierarchy so that it is balanced. This is often done by looking for
nulls in the middle levels of a hierarchy.
ORA-37543: Hierarchy member DIMENSION_MEMBER is inconsistent across
HIERARCHY1 and HIERARCHY2.
Cause: Two hierarchies are inconsistent when members that appear in both
hierarchies have different ultimate leaves.
20-86 Oracle Database Error Messages
Action: This problem is usually resolved by defining a new dimension member
for the secondary hierarchy, or fixing the hierarchy table so that the definitions of
the member match across hierarchies.
ORA-37544: Dimension members DIMENSION_MEMBER and MEMBER_
ANCESTOR make this dimension star inconsistent.
Cause: A dimension is "star consistent" when it can be represented in a star
schema table. This requires that a hierarchy level map to a single underlying
column. If a level is shared across one or more hierarchies, it must have the same
set of members in each hierarchy (to share a column).
Action: Create a different level for the secondary hierarchy. This provides a
separate level column for each hierarchy.
ORA-37545: DIMENSION_MEMBER is part of a hierarchy loop.
Cause: A hierarchy has loops when the ancestor of a dimension member uses that
member as its parent. Note that some loops are created across hierarchies. For
example, in hierarchy 1, dimension member A is the parent of B, B is the parent of
C and in hierarchy 2, C is that parent of A forms a hierarchy loop.
Action: Change the hierarchies so that the loop is eliminated or move the problem
hierarchy to a different dimension.
ORA-37546: (XSHIERSP00) Levelorder valueset is empty.
Cause: An empty levelorder valueset was specified for the HIERSHAPE function.
Action: specify a non-empty levelorder valueset.
ORA-37547: (XSHIERSP01) DIMENSION_MEMBER has no level associated with
it.
Cause: DIMENSION_MEMBER did not have an associated level. Level based
hierarchies must have a level for every dimension member.
Action: Add level assignments for all dimension members in the hierarchy.
ORA-37548: (XSHIERSP02) DIMENSION_MEMBER is not specified as a member
of HIERARCHY1.
Cause: When a dimension member is part of a hierarchy, it appears in the INHIER
valueset associated with the hierarchy. This dimension member is missing from
this value set and thus should not be part of this hierarchy.
Action: Alter the hierarchy's membership to include the specified dimension
member.
ORA-37549: (XSHIERSP03) The level of DIMENSION_MEMBER is not lower than
the level of MEMBER_ANCESTOR.
Cause: A dimension member has a parent that is lower or on the same level as
this member according to the levelorder valueset.
Action: Fix the child and/or parent levels so that every dimension member has a
parent whose level is higher than the level of this member.
ORA-37550: (XSHIERSP04) The level of MEMBER_ANCESTOR is not one level
above DIMENSION_MEMBER.
Cause: A dimension member has a parent that is not one level above the level of
this member according to the levelorder valueset.
Action: Fix the child and/or parent levels so that every dimension member has a
parent whose level is one level above the level of this member according to the
levelorder.
ORA-33000 to ORA-37999 20-87
ORA-37551: (XSHIERSP05) Leaf value DIMENSION_MEMBER is not on the same
level as the rest of leaf dimension values.
Cause: The detail or leaf values of this hierarchy must all have the same level.
This member is on a different level than most of the leaf values.
Action: Fix DIMENSION_MEMBER's level so that all leaves are on the same level.
ORA-37552: (XSHIERSP06) DIMENSION_MEMBER is associated with a level not
found in the levelorder valueset.
Cause: DIMENSION_MEMBER must have an associated level that is found in the
levelorder valueset so that we can figure out DIMENSION_MEMBER's level
depth.
Action: Fix DIMENSION_MEMBER's associated level.
ORA-37553: A cycle between number and number has been detected in relation
workspace object over workspace object.
Cause: A relation was used that had loops in it.
Action: Correct the relation so that it does not contain loops.
ORA-37554: A cycle between number and number has been detected in relation
workspace object.
Cause: A relation was used that had loops in it.
Action: Correct the relation so that it does not contain loops.
ORA-37560: lob locator invalid for specified log target
Cause: A lob locator was passed as a target to DBMS_CUBE_LOG.ENABLE, but
the log_target was not DBMS_CUBE_LOG.TARGET_LOB
Action: Specify LOG_TARGET_LOB as the log_target, or specify a valid location
instead
ORA-37561: unknown logging type
Cause: An invalid log_type was specified
Action: Specify a valid logging type from the DBMS_CUBE_LOG package
ORA-37562: unknown logging target
Cause: An invalid log_target was specified
Action: Specify a valid logging target from the DBMS_CUBE_LOG package
ORA-37563: invalid log verbosity
Cause: An invalid log_verbosity was specified
Action: Specify a valid logging verbosity from the DBMS_CUBE_LOG package
ORA-37564: unknown log table version
Cause: Could not determine the version of the specified logging table
Action: Specify a valid target table, or use DBMS_CUBE_LOG.TABLE_CREATE to
create one
ORA-37565: invalid parameter for specified log type
Cause: The log_type specified does not support the specified parameter, for
instance, DBMS_CUBE_LOG.MAX_ERRORS is not valid for
Action: Specify a valid log_type / log_param combination
ORA-37566: invalid log location
20-88 Oracle Database Error Messages
Cause: The specified log location is in an invalid format. For file targets it must be
of the form 'directory_alias/filename'
Action: Specify a valid log location
ORA-37567: log location not specified
Cause: The log location was not specified for a log target which requires one
Action: Specify a valid log location
ORA-37568: invalid log parameter
Cause: An invalid log_param was passed to dbms_cube_log.set_parameter or
get_parameter
Action: Specify a valid parameter
ORA-37569: invalid log parameter value
Cause: An invalid value was passed to dbms_cube_log.set_parameter
Action: Specify a valid value
ORA-37570: invalid log specification
Cause: An invalid logging specification was supplied to DBMS_CUBE_LOG.SET_
LOG_SPEC
Action: Correct the syntax being supplied
ORA-37571: invalid SQL ID
Cause: Either the SQL ID supplied was invalid or no associated logging
information was captured.
Action: Specify a valid SQL ID.
ORA-37572: invalid ID
Cause: An invalid ID was supplied for the given SQL ID.
Action: Specify a valid ID for that SQL ID.
ORA-37573: no limits logged
Cause: There were no corresponding OLAP filters to the supplied information.
Action: Specify predicates on the original query or specify a new SQL ID or ID.
ORA-37574: error logging to table "string.string"
Cause: An error occurerd attempting to write log records to the named table.
Action: Make sure the user has permissions to write to the table.
ORA-37575: Invalid cube operations log component, "string".
Cause: Invalid cube operations log component value.
Action: Provide a valid cube operations log component or accept the default
value by leaving the parameter unspecified.
ORA-37576: Invalid cube operations log handle id.
Cause: An invalid cube operations log handle id was specified. No oplog handle
found for oplogHandleId parameter.
Action: Provide a valid cube operations log handle id for oplogHandleId. Use
DBMS_CUBE_LOG.START_OPLOG to get a valid handle id.
ORA-37577: Invalid cube operations log message name.
Cause: Cube operations log message name value is NULL.
ORA-33000 to ORA-37999 20-89
Action: Provide a valid non-null cube operations log message name.
ORA-37578: Invalid cube operations log operation value.
Cause: Cube operation log operations value is NULL.
Action: Provide a valid non-null cube operations log operation value.
ORA-37580: The EXPRESS AW does not exist.
Cause: The EXPRESS AW does not exist.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Support Services.
ORA-37581: The EXPRESS AW has not been properly installed.
Cause: The EXPRESS AW has not been properly installed.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Support Services.
ORA-37582: The EXPRESS AW version string is different than the Oracle version
string.
Cause: The EXPRESS AW version does not match the current Oracle version.
Action: Ensure that Oracle is properly installed with the OLAP option. If the
RDBMS has been patched, review the patch log for errors. If the problem persists,
report it to Oracle Support Services.
ORA-37600: (XSPGERRPERMDETACH) Ran out of tablespace storage while
updating analytic workspace string
Cause: Ran out of lob segment space.
Action: Increase tablespace storage. AW may need to be detached.
ORA-37601: (XSPGERRTEMP) Ran out of temporary storage while writing to
analytic workspace with ID=number. Free some temporary storage immediately.
You can do so, for example, by DETACHING an analytic workspace.
Cause: Ran out of temporary tablespace storage.
Action: Increase the amount of temporary tablespace storage.
ORA-37602: (XSPGERRTEMPUSER) Ran out of temporary storage while writing to
analytic workspace string. Free some temporary storage immediately. You can do
so, for example, by DETACHING an analytic workspace.
Cause: Ran out of temporary tablespace storage.
Action: Increase the amount of temporary tablespace storage.
ORA-37603: (XSPGERRTEMPSYSTEM) Ran out of temporary storage while writing
to a system temporary analytic workspace. Free some temporary storage
immediately. You can do so, for example, by DETACHING an analytic
workspace.
Cause: Ran out of temporary tablespace storage.
Action: Increase the amount of temporary tablespace storage.
ORA-37604: (XSPGERRPQUPD) Parallel updating analytic workspace string failed
Cause: Unexpected error occurred to parallel update servers.
20-90 Oracle Database Error Messages
Action: Check the error underneath and act accordingly. AW may need to be
detached.
ORA-37605: error during OLAP AW UPDATE
Cause: An error occurred during the UPDATE process
Action: Refer to the next error in the error stack
ORA-37999: Serious OLAP error: string. Please contact Oracle Technical Support.
Cause: Something unexpected occurred in the OLAP system
Action: Contact Oracle technical support
ORA-38029 to ORA-39965 1 2
ORA-38029: object statistics are locked
Cause: An attept was made to modify optimizer statistics of the object.
Action: Unlock statistics with the DBMS_STATS.UNLOCK_TABLE_STATS
procedure on base table(s). Retry the operation if it is okay to update statistics.
ORA-38101: Invalid column in the INSERT VALUES Clause: string
Cause: INSERT VALUES clause refers to the destination table columns
Action: None
ORA-38102: Invalid column in the INSERT WHERE Clause: string
Cause: INSERT WHERE clause refers to the destination table columns
Action: None
ORA-38103: Invalid column in the UPDATE SET Clause: string
Cause: UPDATE SET clause refers to the source table columns in the LHS
Action: None
ORA-38104: Columns referenced in the ON Clause cannot be updated: string
Cause: LHS of UPDATE SET contains the columns referenced in the ON Clause
Action: None
ORA-38105: Delete not yet supported when Update row-migration is possible
Cause: When Update Row-Migration is possible, Delete in MERGE is not yet
supported
Action: None
ORA-38106: MERGE not supported on join view or view with INSTEAD OF
trigger.
Cause: The MERGE operation contained a join view or view with INSTEAD of
trigger which is not supported.
Action: When using MERGE to modify a view, you must only specify a single
table in the view, and the view cannot have an INSTEAD OF trigger.
ORA-38131: specified SQL handle string does not exist
Cause: The specified SQL handle did not exist in the repository.
Action: Specify correct SQL handle.
ORA-38132: specified SQL ID string does not exist
Cause: The SQL statement for SQL ID did not exist in the cursor cache.
21-2 Oracle Database Error Messages
Action: Specify correct SQL ID.
ORA-38133: invalid parameter name string specified
Cause: An invalid parameter name was specified.
Action: Verify the name of the parameter.
ORA-38134: invalid parameter value string specified
Cause: An invalid parameter value was specified.
Action: Verify the parameter value.
ORA-38135: invalid fixed status value specified
Cause: Specified fixed status value was neither YES or NO.
Action: Specify either 'YES' or 'NO'.
ORA-38136: invalid attribute name string specified
Cause: An invalid attribute name was specified.
Action: Verify the name of the attribute.
ORA-38137: invalid attribute value string specified
Cause: An invalid attribute value was specified.
Action: Verify the attribute value.
ORA-38138: plan name is missing or NULL
Cause: A valid plan name was not specified.
Action: Specify a valid plan name.
ORA-38139: concurrent DDL Error in load plans operation
Cause: A concurrent DDL operation was performed during a load plans
operation.
Action: Try operation again.
ORA-38140: no SQL plan baselines were found
Cause: No SQL plan baselines were found during pack or unpack operation.
Action: Specify correct selection criterion.
ORA-38141: SQL plan baseline string does not exist
Cause: A SQL plan baseline name was specified that did not exist.
Action: Verify the name of the SQL plan baseline.
ORA-38142: SQL plan baseline named string already exists
Cause: A SQL plan baseline already exists with the name specified.
Action: Specify a different name or drop the existing SQL plan baseline.
ORA-38143: invalid enabled status value specified
Cause: Specified enabled status value was neither YES or NO.
Action: Specify either 'YES' or 'NO'.
ORA-38144: specified plan name string does not exist
Cause: The specified plan name did not exist in the repository.
Action: Specify correct plan name.
ORA-38029 to ORA-39965 21-3
ORA-38145: neither SQL handle nor plan name specified
Cause: The SQL handle or plan name was not specified. The SQL handle or plan
name is required.
Action: Specify either SQL handle or plan name or both.
ORA-38146: invalid verify value specified
Cause: Specified verify value was neither YES or NO.
Action: Specify either 'YES' or 'NO'.
ORA-38147: invalid commit value specified
Cause: Specified commit value was neither YES or NO.
Action: Specify either 'YES' or 'NO'.
ORA-38148: invalid time limit specified
Cause: Specified time limit value was not a positive integer.
Action: Specify a positive integer value.
ORA-38149: There is no recommended action for object string in task string.
Cause: The advisor did not generate a recommended action for the given object
and task.
Action: Choose a different object and retry the operation.
ORA-38171: Insufficient privileges for SQL management object operation
Cause: A DDL operation was attempted on a SQL management object by a
session without the proper privileges.
Action: Grant the appropriate privilege.
ORA-38172: No SQL management object satisfies specified filters
Cause: An attempt was made to perform an operation by specifying filters that
did not target any SQL management objects.
Action: Try different filters.
ORA-38173: Invalid value string specified for SQL management object attribute
string
Cause: An invalid attribute value was specified.
Action: Specify a valid attribute value.
ORA-38301: can not perform DDL/DML over objects in Recycle Bin
Cause: Tried to perform DDL or DML operation on Recycle Bin object.
Action: DDL or DML operations are not permitted on Recycle Bin objects.
ORA-38302: invalid PURGE option
Cause: Invalid purge option specified.
Action: Specify a valid purge option.
ORA-38303: invalid option for PURGE TABLESPACE
Cause: Either a token other than USER was found following the tablespace name
or some text was found following USER <user name>.
Action: Place nothing or only USER <user name> after the tablespace name
ORA-38304: missing or invalid user name
21-4 Oracle Database Error Messages
Cause: A valid user name was expected.
Action: Specify a valid user name.
ORA-38305: object not in RECYCLE BIN
Cause: Trying to Flashback Drop an object which is not in RecycleBin.
Action: Only the objects in RecycleBin can be Flashback Dropped.
ORA-38306: this object is not recoverable standalone
Cause: Trying to flashback drop an object other than of type TABLE.
Action: Only tables are recoverable.
ORA-38307: object not in RECYCLE BIN
Cause: Trying to Purge the object which is not in RecycleBin.
Action: Only the objects in RecycleBin can be PURGEDED.
ORA-38308: invalid FLASHBACK DROP option
Cause: Invalid Flashback Drop option specified.
Action: Specify a valid Flashback Drop option.
ORA-38309: object not purgable
Cause: An attempt was made to purge an object that is either not purgable or else
dependent upon some other object.
Action: Cannot purge this object.
ORA-38310: cannot purge tablespace for other users
Cause: An attempt was made to purge the tablespace for a different user by a user
who does not have system DBA priviledges.
Action: Cannot purge the tablespace for some other user.
ORA-38311: cannot purge objects owned by other users
Cause: An attempt was made to purge an object which is owned by some other
user.
Action: Cannot purge this object.
ORA-38312: original name is used by an existing object
Cause: An attempt was made to recover an object preserving the original name,
but that name is taken up by some other object.
Action: use the RENAME clause to recover the object with a different name.
ORA-38320: policy does not exist
Cause: An attempt was made to delete a nonexistent policy.
Action: Correct the policy name.
ORA-38321: duplicate policy name specified
Cause: A policy name was specified that already existed under this schema.
Action: Correct the policy name.
ORA-38322: scope of policy not specified
Cause: An attempt was made to add a policy without the scope.
Action: Specify a scope when creating a policy.
ORA-38029 to ORA-39965 21-5
ORA-38323: policy conflicts with policy string
Cause: An attempt was made to create a policy with the same action type and
based on the same statistic as another policy on the object.
Action: Use a different action and/or statistic for the new policy, or delete the old
policy.
ORA-38324: policy conflicts with policy string
Cause: An attempt was made to create a policy with the same action, scope and
compression level as another policy on the object.
Action: Use a different action, scope and/or level for the new policy, or delete the
old policy.
ORA-38325: policy conflicts with policy string
Cause: An attempt was made to create a compression policy that conflicts with
another policy on the object.
Action: Change the policy so that policies with a higher compression level take
effect after policies with a lower compression level, or delete the old policy.
ORA-38326: schema level policies are not supported
Cause: Attempt was made to create a schema level policy.
Action: Do not create a schema level policy.
ORA-38327: invalid argument value
Cause: The specified API argument values were of the wrong value range.
Action: Supply valid values for the API.
ORA-38328: inconsistent internal state
Cause: An inconsistency was detected in ILM related data in the dictionary.
Action: Contact Oracle Support Services.
ORA-38329: internal ILM error
Cause: An internal error occurred during execution of ILM related activity.
Further information can be found in the alert log.
Action: Fix the problem and retry the operation.
ORA-38330: insufficient privilege for ILM operation
Cause: Sufficient privileges were not granted for the ILM operation.
Action: Retry operation with sufficient privileges granted. Consult
documentation for privileges required to perform the ILM operation.
ORA-38331: row-level write activity tracking not enabled on the table
Cause: An attempt was made to create a modification time-based policy when
row-level write tracking was not enabled on the object.
Action: Ensure that row-level write tracking is enabled on the table.
ORA-38332: valid time periods were not present on the table
Cause: An attempt was made to create a valid time-based policy when valid time
periods were not present on the table.
Action: Add valid time periods to the table.
ORA-38333: row-level access activity tracking not enabled on the table
21-6 Oracle Database Error Messages
Cause: An attempt was made to create an access time-based policy when
row-level access tracking was not enabled on the object.
Action: Ensure that row-level access tracking is enabled on the table.
ORA-38334: segment-level access activity tracking not enabled on the table
Cause: An attempt was made to create an access time-based policy when
segment-level access tracking was not enabled on the object.
Action: Ensure that segment-level access tracking is enabled on the table.
ORA-38335: sysdba privilege is required
Cause: SYSDBA privilege is required for applying ILM policies on a tablespace.
Action: Grant user SYSDBA role before applying tablespace level ILM policies.
ORA-38336: invalid policy
Cause: A row level policy was used with a compression level other than OLTP.
Action: Use the OLTP compression level with row level compression policies.
ORA-38337: invalid policy
Cause: A custom policy is only allowed at the segment level.
Action: Change the scope of the policy to be of type segment.
ORA-38338: incorrect ILM policy scope
Cause: An attempt was made to create an Information Lifecycle Management
(ILM) policy with incompatible scope.
Action: Ensure that the scope of the ILM policy is compatible.
ORA-38339: invalid action specified
Cause: An invalid action was specified in the policy definition.
Action: Specify a valid action in the policy definition.
ORA-38340: invalid policy
Cause: An attempt was made to create a custom policy at the tablespace level.
Action: Specify the policy directly on the desired objects.
ORA-38341: policy conflicts with policy string
Cause: An attempt was made to create more than one storage tiering policy
directly on an object.
Action: Delete the conflicting policy before creating a new policy.
ORA-38342: heat map not enabled
Cause: An attempt was made to create an Information Lifcecycle Management
(ILM) policy when heat map was not enabled.
Action: Enable heat map before creating a new ILM policy.
ORA-38343: ADO online mode not supported with supplemental logging enabled
Cause: An attempt was made to perform an automatic data optimization (ADO)
operation with supplemental logging enabled.
Action: Disable supplemental logging or switch to ADO offline mode and retry.
ORA-38393: ILM internal out-of-space error
Cause: Information Lifecycle Management (ILM) internal operation encountered
out-of-space error.
ORA-38029 to ORA-39965 21-7
Action: None
ORA-38394: test event for table ILM operations
Cause: Internal testing event for table Information Lifecycle Management (ILM)
operations.
Action: None
ORA-38395: debug event for table ILM operations
Cause: There was an internal debugging event for table Information Lifecycle
Management (ILM) operations.
Action: None
ORA-38396: table is already enabled for the ILM feature
Cause: The table was already enabled for the specified Information Lifecycle
Management (ILM) feature.
Action: No action required.
ORA-38397: table is not enabled for the ILM feature
Cause: An attempt was made to perform an Information Lifecycle Management
(ILM) operation on a table on which the specified ILM feature is not enabled.
Action: No action required.
ORA-38398: DDL not allowed on the system ILM column
Cause: An attempt was made to drop, rename, or modify a system Information
Lifecycle Management (ILM) column.
Action: No action required.
ORA-38399: cannot update the system ILM column
Cause: An attempt was made to update a system Information Lifecycle
Management (ILM) column.
Action: No action required.
ORA-38400: cannot combine ILM operation with other operations
Cause: An attempt was made to combine Information Lifecycle Management
(ILM) operation with other ALTER TABLE operations.
Action: Ensure that ILM is the sole operation specified in ALTER TABLE.
ORA-38401: synonym string not allowed
Cause: An attempt was made to use a synonym for a data type of an attribute or a
table alias.
Action: Use the object name instead of the synonym.
ORA-38402: invalid name: empty string or spaces in the name
Cause: There were spaces in the name.
Action: Remove spaces in the name or use quotes around the name.
ORA-38403: attribute set name may not be longer than 22 characters
Cause: The attribute set name was longer than 22 characters.
Action: Choose a name that has 22 or fewer characters.
ORA-38404: schema extension not allowed for the attribute set name
21-8 Oracle Database Error Messages
Cause: There was a schema extension for the attribute set name. Attribute sets are
always created in the current schema and thus schema extended names are not
allowed.
Action: Create the attribute set from the appropriate schema.
ORA-38405: quotes not allowed in the attribute set name
Cause: The attribute set name contained quotes.
Action: Remove quotes in the attribute set name.
ORA-38406: attribute set string already exists
Cause: An attribute set with a matching name already exists in the current
schema.
Action: Drop the existing attribute set or choose a different name.
ORA-38407: The ADT associated with the attribute set already exists.
Cause: The Abstract type (ADT) with the same name as the attribute set already
exists in the current schema.
Action: Create the attribute set for the existing ADT or drop the ADT.
ORA-38408: The ADT "string" does not exist in the current schema.
Cause: An attempt was made to create the attribute set from a nonexistent ADT.
Action: Make sure that the ADT with the same name as the attribute set exists in
the current schema.
ORA-38409: invalid name or option for the attribute set: string
Cause: An invalid name or option was used for the attribute set.
Action: Set serveroutput ON and repeat the operation for additional information.
ORA-38410: schema extension not allowed for the table name
Cause: An attempt was made to use a schema extended name for the table storing
expressions.
Action: The table storing expressions and the corresponding attribute set should
be created in the same schema.
ORA-38411: invalid datatype for the column storing expressions
Cause: An attempt was made to create an expression column from a column of
invalid datatype.
Action: Create a VARCHAR2 or CHAR column to store expressions in a table.
ORA-38412: Expression set column string does not exist.
Cause: The column storing expressions does not exist.
Action: Pass a valid name for the column storing expressions.
ORA-38413: elementary attribute name may not be longer than 32 characters
Cause: An attempt was made to create an elementary attribute with a name
longer than 32 characters.
Action: Use a shorter name for the elementary attribute.
ORA-38414: invalid datatype for the attribute string
Cause: The datatype specified for the attribute was invalid.
Action: If the datatype is an ADT, make sure that the ADT exists and the current
user has execute permissions to it.
ORA-38029 to ORA-39965 21-9
ORA-38415: invalid name or datatype for the attribute: string
Cause: An invalid name or datatype was used for the attribute.
Action: Set serveroutput ON and repeat the operation for additional information.
ORA-38416: A stored attribute may not be longer then 300 characters.
Cause: An attempt was made to create a stored or indexed attribute longer than
300 characters.
Action: A predicate with such attribute may not be indexed. It will be evaluated
as sparse predicate.
ORA-38417: attribute set string does not exist
Cause: An attempt was made to use an attribute set that does not exist.
Action: Create the attribute set or choose an existing attribute set.
ORA-38418: ADT associated with the attribute set string does not exist
Cause: The ADT with the same name as the attribute set was not found in the
current schema.
Action: Drop the attribute set and recreate it.
ORA-38419: invalid identifier in attribute : string
Cause: An identifier used in the stored/indexed attribute sub-expression was not
defined or was invalid.
Action: Create all the required elementary attributes and user-defined functions
and try again.
ORA-38420: invalid stored attribute sub-expression: string
Cause: The sub-expression used for the stored expression was invalid.
Action: Set serveroutput ON and repeat the operation for additional information.
ORA-38421: attribute string already exists
Cause: An attribute with a matching name (or form) already exists in the attribute
set.
Action: Drop the existing attribute or choose a different name for the new
attribute.
ORA-38422: invalid datatype for the attribute: string
Cause: An attempt was made to create an attribute with invalid datatype.
Action: If the data type of the attribute is an ADT, make sure that the type exists.
ORA-38423: Attribute set created from an ADT may not be extended.
Cause: An attempt was made to add an elementary attribute to an attribute set
created from an ADT.
Action: Create a new attribute set and add all the required elementary attributes
one at a time.
ORA-38424: no attribute set currently assigned to the expression set
Cause: An attempt was made to un-assign an attribute set from an expression set
when there is no attribute set assigned to it.
Action: No action is required.
ORA-38425: attribute set used for an index object may not be unassigned
21-10 Oracle Database Error Messages
Cause: An attempt was made to un-assign an attribute set from an expression set
when there is an Expression Filter index defined on the column.
Action: Drop the index before un-assigning the attribute set.
ORA-38426: attribute set assigned to an expression set may not be dropped
Cause: An attempt was made to drop an attribute set when it is still associated
with an expression set.
Action: Un-assign the attribute set from the expression set before dropping it.
ORA-38427: attribute string does not exist
Cause: An attempt was made to use an attribute set that does not exist.
Action: Create the attribute set.
ORA-38428: too many attributes selected for indexing
Cause: An attempt was made to create an expression filter index with more than
490 indexed attributes.
Action: Remove some of the indexed attributes. Make sure that the default
indexed attributes associated with the attribute set combined with the indexed
attributes specified in the Create Index Parameters clause are less than or equal to
490.
ORA-38429: invalid datatype for a stored attribute: string
Cause: The (resulting) datatype for the attribute was not appropriate for storing.
Action: Choose a stored attribute that has a resulting datatype of NUMBER,
VARCHAR2, CHAR or DATE.
ORA-38430: Operation "string" not supported in the current release.
Cause: An attempt was made to perform an unsupported operation.
Action: Do not use the operation.
ORA-38431: could not evaluate subexpression "string" for rowid "string"
Cause: Either the expression was not a valid SQL-WHERE clause format or it had
references to nonexistent schema objects.
Action: Correct the expression.
ORA-38432: EVALUATE operator only allowed on an expression column
Cause: An attempt was made to use the EVALUATE operator on a column not
configured as a column storing expressions.
Action: Assign an attribute set to the column.
ORA-38433: index "string" could not be maintained due to "string"
Cause: The error was caused by the recursive operation.
Action: Fix the error and retry.
ORA-38434: could not evaluate expression "string"
Cause: Either the expression was not in a valid SQL-WHERE clause format or it
had references to nonexistent schema objects or there is a missing attribute value.
Action: Set serveroutput ON for more details.
ORA-38435: missing elementary attribute value or invalid name-value pairs
Cause: The second argument to the EVALUATE operator had either a missing
attribute or an invalid value for an attribute.
ORA-38029 to ORA-39965 21-11
Action: Try again after fixing the error.
ORA-38436: attribute set used for an Expression set may not be modified.
Cause: An attempt was made to add an elementary attribute to an attribute set
assigned to an expression set.
Action: Un-assign the attribute set and try again.
ORA-38437: The ADT "string" may not contain any user methods.
Cause: An attempt was made to create an attribute set from an ADT that has one
or more user methods.
Action: Drop the ADT and recreate it with no user methods.
ORA-38438: getVarchar not possible due to "string" datatype in the attribute set
Cause: An attempt was made to use the getVarchar API when the attribute set has
one or more non-scalar types.
Action: Use AnyData conversion to encode the data item.
ORA-38439: invalid operation "string"
Cause: An attempt was made to use an invalid operation.
Action: Use one of the following operations : ADD, DROP
ORA-38440: attribute set string does not exist
Cause: An attempt was made to copy an attribute set that is not accessible from
the current schema.
Action: Grant execute permissions on the corresponding ADT to the current user
and try again.
ORA-38441: System could not derive the list of STORED and INDEXED attributes.
Cause: The attribute set was created without default index parameters.
Action: Specify the default index parameters for the attribute set or include a
valid PARAMETERS clause for the CREATE INDEX command.
ORA-38442: The ADT "string" is not in a valid state.
Cause: An attempt was made to use an ADT that is not in a valid state.
Action: Check the INCOMPLETE field in the user_types catalog view to make
sure that the ADT is in a valid state. Drop the invalid ADT and recreate the
corresponding attribute set.
ORA-38443: An attribute set should be assigned to the expression set for statistics
collection.
Cause: An attempt was made to collect statistics for an expression set with no
attribute set assigned to it.
Action: Assign an attribute set to the expression set before collecting the statistics.
ORA-38444: statistics do not exist for the expression set
Cause: An attempt was made to clear the statistics that do not exist.
Action: No action was required.
ORA-38445: TOP clause not allowed with no statistics
Cause: An attempt was made to use the TOP parameters clause with no statistics
available for the expression set.
Action: Collect statistics for the expression set and try again.
21-12 Oracle Database Error Messages
ORA-38446: Error with embedded ADT "string" in the attribute set.
Cause: The embedded ADT has errors.
Action: Set serveroutput ON for additional information.
ORA-38447: Type required for the embedded ADT attribute "string" is missing
Cause: Object type required for the embedded ADT was missing.
Action: Set serveroutput ON for additional information.
ORA-38448: Indexing predicates with "string" operator is not supported.
Cause: An unsupported operator was used in the exf$indexoper array.
Action: Choose the operators from this list : =, <, >, <=, >=, !=, is null, is not null,
nvl, and between.
ORA-38449: table "string" does not exist or is not accessible
Cause: An attempt was made to create a table alias for a table that does not exist
or is not accessible.
Action: Grant select privileges on the table to the current user.
ORA-38450: error computing a stored attribute for the expression set.
Cause: Either values for one of the attributes was incorrect or a stored attribute
was invalid due to broken dependencies.
Action: Correct the input.
ORA-38451: index is in an inconsistent state
Cause: One or more secondary objects used to maintain the index did not exist
Action: Drop the index and recreate it.
ORA-38452: Expression Filter index name may not be longer than 25 characters
Cause: An attempt was made to use a name longer than 25 characters for the
Expression Filter index.
Action: Choose a name that has 25 or fewer characters
ORA-38453: ExpFilter index should be created in the same schema as the base table.
Cause: An attempt was made to create the Expression Filter index in a schema
other than that of the base table.
Action: Create the index in the same schema as the base table.
ORA-38454: attribute set not defined for the column being indexed
Cause: An attempt was made to create an Expression Filter index on a column
with no attribute set association.
Action: Assign an attribute set to the expression set column begin indexed.
ORA-38455: Expression Filter index should be created by the owner.
Cause: An attempt was made to create the Expression Filter index by a user who
is not the owner of the index.
Action: Create the index using owner's privileges.
ORA-38456: The attribute set "string" is in an inconsistent state.
Cause: The attribute set was in an inconsistent state due to broken dependencies.
Action: Set serveroutput ON for more details. The attribute set may not be reused
after this error.
ORA-38029 to ORA-39965 21-13
ORA-38457: The attribute "string" is not a valid XMLType attribute.
Cause: An attempt was made to use a non-XMLType attribute to configure XPath
filtering.
Action: Use an attribute of sys.XMLType datatype to configure XPath filtering.
ORA-38458: invalid operation "string" for XPATH_FILTER_PARAMETERS
Cause: An attempt was made to use an invalid operation.
Action: Use one of the following operations : ADD, DROP.
ORA-38459: XML Tag "string" not found for the XMLType attribute "string"
Cause: An Attempt was made to use a non-existent XML Tag.
Action: Correct the name of the XML Tag or the XMLType attribute.
ORA-38460: filtering based on datatype "string" not supported for XML Tags
Cause: An attempt was made to configure XPath filtering with an XML Tag of
unsupported datatype.
Action: Leave the XML Tag out of filter parameters. It will be processed as sparse
predicate
ORA-38461: XML Tag "string" already exists for the XMLType attribute "string"
Cause: An attempt was made to create a duplicate XML Tag.
Action: Choose a different XML Tag.
ORA-38462: invalid attribute list
Cause: The input was missing an attribute list or had null values for the attribute
names.
Action: Correct the input.
ORA-38463: invalid XML Tag list
Cause: The input was missing a tag list or had null values for the tag names.
Action: Correct the input.
ORA-38464: expression set is not empty.
Cause: An attempt was made to assign an attribute set to a non-empty expression
set.
Action: Use FORCE = 'TRUE' to validate all the existing expressions.
ORA-38465: failed to create the privilege checking trigger due to: string
Cause: Creation of the trigger failed due to the error listed in the message.
Action: Set serveroutput ON for more information.
ORA-38466: user does not have privileges to CREATE/MODIFY expressions
Cause: An attempt was made to INSERT or UPDATE a column storing expression
without appropriate permissions.
Action: Appropriate privileges on the expression set should be granted by the
owner of the expression set.
ORA-38467: user cannot GRANT/REVOKE privileges to/from himself
Cause: An attempt was made to GRANT or REVOKE privileges to or from the
current user.
21-14 Oracle Database Error Messages
Action: The the to_user or from_user field should be different from the user
performing the operation.
ORA-38468: column "string" is not identified as a column storing expressions.
Cause: An attempt was made to grant permission on a nonexistent expression set.
Action: Make sure that the table and the column exist and an attribute set is
associated with the column.
ORA-38469: invalid privilege for an expression set: string
Cause: An attempt was made to use an invalid privilege.
Action: See documentation for a valid privilege.
ORA-38470: cannot revoke a privilege that was not granted.
Cause: An attempt was made to revoke a privilege that had not been granted.
Action: Check catalog views to see if the user has the privilege.
ORA-38471: ROWIDs for table aliases cannot be null
Cause: An attempt was made to pass a null value for the table alias attribute in
the data item, which is not permitted.
Action: Pass a valid rowid value for the table alias.
ORA-38472: VARCHAR representation of the data item is too long.
Cause: The VARCHAR representation of data item was too long.
Action: Use the EVALUATE operator with AnyData argument instead.
ORA-38473: cannot drop a type used for Expression Filter attribute set
Cause: An attempt was made to drop an ADT that was used to maintain an
attribute set for the Expression Filter.
Action: Query USER_EXPFIL_ATTRIBUTE_SETS view to see the dependency.
ORA-38474: attribute set may not have attributes of TABLE COLLECTION type.
Cause: An attempt was made to create an attribute with a TABLE COLLECTION
type.
Action: Use VARRAYs instead of table collection, if possible.
ORA-38475: The attribute set and the associated ADT are out of sync.
Cause: The ADT was directly modified by CREATE or ALTER operations.
Action: Drop the attribute set and recreate it from scratch.
ORA-38476: abstract type used for an Attribute set may not be modified.
Cause: An attempt was made to alter a type (ADT) that is used to maintain an
attribute set of an Expression set.
Action: Do not modify the ADT directly. Use DBMS_EXPFIL APIs instead.
ORA-38477: attribute set cannot be derived from an evolved type or a subtype.
Cause: An attempt was made to create an attribute set from an evolved ADT or a
subtype.
Action: The ADT used for the attribute set cannot be an evolved type or a
subtype.
ORA-38478: creation of system trigger EXPFIL_DROPOBJ_MAINT failed
ORA-38029 to ORA-39965 21-15
Cause: The creation of the system trigger EXPFIL_DROPOBJ_MAINT failed due
to missing Expression Filter dictionary tables.
Action: Try a clean installation again. If this error is ignored, the Expression Filter
dictionary could have some stale entries.
ORA-38479: creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed
Cause: The creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed
due to missing Expression Filter dictionary tables.
Action: Try a clean installation again. If this error is ignored, the user will be able
to evolve ADTs associated with the attribute set, thus causing spurious errors.
ORA-38480: creation of system trigger EXPFIL_ALTEREXPTAB_MAINT failed.
Cause: The creation of system trigger EXPFIL_ALTEREXPTAB_MAINT failed due
to errors in SYS.EXF$DBMS_EXPFIL_SYSPACK package.
Action: Try a clean installation again. If this error is ignored, a RENAME of the
expression table may cause the EVALUATE queries to fail.
ORA-38481: ADT "string" is used for a dependent object.
Cause: An attempt was made to create an attribute set from an ADT which is used
by one or more dependent objects.
Action: Use a new ADT instead.
ORA-38482: no elementary attributes defined in the attribute set
Cause: An attempt was made to use an empty attribute set.
Action: Create one or more elementary attributes for the attribute set.
ORA-38483: invalid FUNCTION/PACKAGE/TYPE name: "string"
Cause: An attempt was made to use an invalid name format.
Action: The function/package/type name should be specified in the following
format [owner.]object_name
ORA-38484: FUNCTION/PACKAGE/TYPE string does not exist
Cause: Attempt was made to use a object that does not exist.
Action: Query ALL_OBJECT view to ensure that the object exists.
ORA-38485: invalid object type for the user-defined function
Cause: An attempt was made to use an invalid object as a function.
Action: Valid object types are FUNCTION / PACKAGE / TYPE
ORA-38486: FUNCTION/PACKAGE/TYPE already exists for the attribute set
Cause: An attempt was made to add a duplicate function to the list.
Action: Use a different object name.
ORA-38487: FUNCTION/PACKAGE/TYPE "string" not allowed in the expression
Cause: An attempt was made to use an un-approved function in the expression.
Action: Add the function to the corresponding attribute set
ORA-38488: attribute set already assigned to the column storing expressions
Cause: An attempt was made to reassign an attribute set to an expression column.
Action: Query USER_EXPFIL_EXPRESSION_SETS view to find the attribute set
assigned the expression set
21-16 Oracle Database Error Messages
ORA-38489: predicate table creation failed due to: ORAstring
Cause: Predicate table creation failed due to the reported error.
Action: Set serveroutput ON for additional information
ORA-38490: invalid name: quotes do not match
Cause: The quotes in the name did not match.
Action: Correct the name to match the quotes.
ORA-38491: could not evaluate subexpression for rowid "string"
Cause: Either the expression was not in a valid SQL-WHERE clause format or it
had references to nonexistent schema objects.
Action: Correct the expression.
ORA-38492: invalid ALTER INDEX parameters clause "string"
Cause: An invalid parameters clause was specified with the ALTER INDEX
command.
Action: See documentation for a valid list of parameters.
ORA-38493: feature not enabled : Expression Filter index
Cause: An attempt was made to create an Expression Filter index in Standard
Edition.
Action: Do not attempt to use this feature.
ORA-38494: column in the table alias and an attribute have matching names
Cause: One of the attributes in the set has the same name as the name of one of
the columns in the table configured for table alias.
Action: If possible, use a different name for the attribute.
ORA-38495: data type for the stored attribute string is inconsistent.
Cause: The actual data type for the stored attribute configured for the Expression
Filter index object did not match the data type recorded in the Expression Filter
dictionary.
Action: Delete the attribute from the default index attributes and recreate it.
ORA-38496: Expression Filter index is not in a valid state
Cause: An attempt was made to REBUILD an Expression Filter index that was not
valid.
Action: Use DEFAULT keyword in the parameters clause to rebuild the index
from defaults or drop and recreate the index.
ORA-38497: Expression Filter index does not exist
Cause: Index with a matching name does not exist or the index was not created
using ExpFilter indextype.
Action: Identify the correct index using the Expression Filter catalog views
ORA-38498: invalid stored attribute for the index object : string
Cause: The expression filter index object has a stored or indexed attribute that had
broken dependencies.
Action: Make sure that all the identifiers used in the attribute are valid.
ORA-38499: expression set already configured for stored/indexed attributes
ORA-38029 to ORA-39965 21-17
Cause: The expression set already had a list of stored and indexed attributes.
Additional attributes cannot be specified in the CREATE INDEX parameters
clause.
Action: Remove TOP, STOREATTRS and INDEXATTRS clauses from the
parameters clause or clear the expression set statistics using DBMS_
EXPFIL.INDEX_PARAMETERS API.
ORA-38500: string
Cause: There was a generic error
Action: See documentation for further information.
ORA-38501: sub-query not allowed in the expression
Cause: An attempt was made to use a sub-query in the expression.
Action: Do not use sub-queries in the expressions.
ORA-38502: invalid XML tag: string
Cause: An attempt was made to use an invalid XML tag for the index.
Action: Correct the XML tag and retry.
ORA-38503: index already defined using the parameters
Cause: An attempt was made to modify the index parameters after the index
creation.
Action: Drop the index and retry.
ORA-38504: this operator not allowed with the configured attribute set
Cause: An attempt was made to use the operator binding with an attribute set
containing more than one (table alias) attribute. This is not permitted.
Action: Use a different operator binding.
ORA-38505: invalid default value for the attribute
Cause: An attempt was made to use an invalid default value or a default that is
larger than 100 characters.
Action: Specify a correct default value.
ORA-38506: invalid attribute type for text predicates
Cause: An attempt was made to use an invalid type for an attribute configured for
text predicates.
Action: Use either a VARCHAR or a CLOB attribute instead.
ORA-38507: attributes of string data type should be indexed
Cause: An attempt was made to configure an attribute of spatial or text data type
as stored predicate group.
Action: Configure them as indexed predicate groups instead.
ORA-38601: FI Not enough memory for frequent itemset counting: string
Cause: The memory size did not satisfy the minimum memory requirement.
Action: In workarea_size_policy='manual' mode, set _fic_area_size to a
reasonably larger value. Or, In workarea_size_policy='auto' mode, this error
should never happen.
ORA-38602: FI invalid input cursor
21-18 Oracle Database Error Messages
Cause: The input cursor did not return exactly two columns for transactional
input format or the input cursor didn't have consistent data types for horizontal
input format
Action: For transactional input format, specify that the input cursor returns
exactly two columns: one for transaction-id, one for item-id. For horizontal input
format, make sure the input cursor's columns have the same data types.
ORA-38603: FI including & excluding cursor can only return one column
Cause: The including & excluding cursor did not return exactly one column.
Action: Specify that the cursor return only one column: item-id.
ORA-38604: FI including & excluding cursor item-id type must match input cursor
item-id type
Cause: The including & excluding cursor item-id type did not match input cursor
item-id type
Action: Specify that the item-id type of the cursors match each other.
ORA-38605: FI not enough memory(stringK) for candidate generation(stringK)
Cause: There was insufficient available memory for candidate generation.
Action: In workarea_size_policy='manual' mode, set _fic_area_size to a
reasonably larger value. Or, in workarea_size_policy='auto' mode, set pga_
aggregate_target to a reasonably larger value.
ORA-38606: FI support threshold not between [0, 1]
Cause: The user inputed a support threshold not in the range of [0, 1].
Action: The user should adjust the input value in the range of [0, 1].
ORA-38607: FI minimum and maximum itemset length not between [1, string]
Cause: The inputed minimum or maximum itemset length exceed the internal
maximum itemset length or less than 1.
Action: The user should adjust the input value not larger than the internal
maximum itemset length and not less than 1.
ORA-38608: FI itemset minimum-length(string) should not be greater than
maximum length(string)
Cause: The user inputed minimum length is more than maximum length.
Action: The user should adjust the input values to make the minimum length less
than or equal to the maximum length.
ORA-38609: FI Not enough memory for tree counting, requires at least stringKB
Cause: The memory size did not satisfy the minimum memory requirement for
tree counting.
Action: In workarea_size_policy='manual' mode, set _fic_area_size to a
reasonably larger value. Or, In workarea_size_policy='auto' mode, this error
should never happen.
ORA-38610: FI "string" name prefix is reserved for frequent itemset counting
Cause: An error occurred because DBMS_FREQUENT_ITEMSET and prefix
ORA_FI are reserved for the DBMS_FREQUENT_ITEMSET package's internal use.
Action: Do not re-define functions with names starting with DBMS_FREQUENT_
ITEMSET package or ORA_FI.
ORA-38029 to ORA-39965 21-19
ORA-38611: FI input cursor's item type is not supported
Cause: The input cursor's item type is not number or character type
Action: Redefine the input cursor so that item type is number or character type.
ORA-38612: FI item length cannot exceed half of one database block.
Cause: The item's length was more than half of one database block.
Action: Redefine the data type of the item column so that its maximum length is
less than half of one database block.
ORA-38613: FI Cursor is returning less than 2 columns.
Cause: Cursor parameter is returning less than 2 columns.
Action: Modify the Cursor argument to return 2 columns.
ORA-38620: DT expressions in input cursor do not have an alias name
Cause: Expressions in input cursor do not have an alias name.
Action: Add an alias name for the expression.
ORA-38621: Decision Tree maximum depth setting not between [2, 20]
Cause: The user specified a max tree depth not in the range of [2, 20].
Action: The user should adjust the input value to be in the range of [2, 20].
ORA-38622: Decision Tree not enough memory, requires at least stringKB
Cause: The memory size did not satisfy the minimum memory requirement for
decision tree building.
Action: In workarea_size_policy='manual' mode, set _dtree_area_size to a
reasonably larger value. Or, In workarea_size_policy='auto' mode, please raise
pga_aggregate_target to a reasonably larger value.
ORA-38700: Limit of string flashback database logs has been exceeded.
Cause: The maximum number of flashback database log files was exceeded.
Action: DB_FLASHBACK_RETENTION_TARGET may be set to high. Modify it
to a smaller value.
ORA-38701: Flashback database log string seq string thread string: "string"
Cause: This message reports the filename for details of another message.
Action: Other messages will accompany this message. See the associated
messages for the appropriate action to take.
ORA-38702: Cannot update flashback database log file header.
Cause: Could not write to the flashback database log file.
Action: Restore access to the file.
ORA-38703: Type string in header is not a flashback database log file.
Cause: A corrupt flashback database log file header was read.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38704: Checksum error in flashback database log file header.
Cause: The flashback database log file header contained a checksum that does not
match the value calculated from the file header as read from disk. This means the
file header was corrupt.
21-20 Oracle Database Error Messages
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38705: Expected block size string does not match string in log header.
Cause: When the flashback log file header was read, the block size in the control
file did not match the block size contained in the header.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38706: Cannot turn on FLASHBACK DATABASE logging.
Cause: An ALTER DATABASE FLASHBACK ON command failed. Other
messages in the alert log describe the problem.
Action: Fix the problem and retry.
ORA-38707: Media recovery is not enabled.
Cause: An ALTER DATABASE FLASHBACK ON command failed because media
recovery was not enabled.
Action: Turn on media recovery with an ALTER DATABASE ARCHIVELOG
command and then retry the command.
ORA-38708: not enough space for first flashback database log file
Cause: An ALTER DATABASE FLASHBACK ON command failed because there
was not enough space in the Recovery Area for the first flashback database log file.
Action: Make more space in the Recovery Area. For example, this can be done by
increasing the value of DB_RECOVERY_FILE_DEST_SIZE.
ORA-38709: Recovery Area is not enabled.
Cause: An ALTER DATABASE FLASHBACK ON command failed because the
Recovery Area was not enabled.
Action: Set DB_RECOVERY_FILE_DEST to a location and retry.
ORA-38710: Flashback log version string is incompatible with ORACLE version
string.
Cause: The flashback database log file was rejected because it appeared to be
written by an incompatible version of Oracle.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38711: Corrupt flashback log block header: block string
Cause: A corrupt Flashback Database log file block header was read. More
information was dumped to the trace file.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38712: Corrupt flashback log record header: block string, offset string.
Cause: A corrupt flashback database log record header was read. Either the record
type or length were incorrect. More information was dumped to the trace file.
ORA-38029 to ORA-39965 21-21
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38713: Flashback Database logging is already turned on.
Cause: An ALTER DATABASE FLASHBACK ON command had no effect because
flashback database logging was already on.
Action: No action required.
ORA-38714: Instance recovery required.
Cause: An ALTER DATABASE FLASHBACK ON command failed because the
database either crashed or was shutdown with the ABORT option.
Action: Open the database and then enter the SHUTDOWN command with the
NORMAL or IMMEDIATE option.
ORA-38715: Invalid log number specified in the DUMP FLASHBACK command.
Cause: An invalid log number was used when dumping a flashback database log
file.
Action: Specify a valid flashback database log number.
ORA-38716: Must supply an integer for the TYPE option.
Cause: An invalid value was specified for TYPE in the DUMP FLASHBACK
command.
Action: Specify an integer value.
ORA-38717: Invalid DUMP FLASHBACK option.
Cause: An invalid option was specified in the DUMP FLASHBACK command.
Currently the only options allowed are: DBA, TYPE, and LOGICAL.
Action: Retry the command with the correct options.
ORA-38718: Invalid thread number specified in the DUMP FLASHBACK
command.
Cause: An invalid thread number was used in dumping the flashback database
log files for a thread.
Action: Specify a valid thread number.
ORA-38719: Invalid DUMP FLASHBACK object.
Cause: An invalid object was specified in a DUMP FLASHBACK command.
Currently the only objects allowed are: LOGFILE or THREAD.
Action: Retry the command with the correct options.
ORA-38720: Missing log file name or number.
Cause: A log file name or number was missing in a DUMP FLASHBACK
LOGFILE command.
Action: Supply a valid log file name or number.
ORA-38721: Invalid file number.
Cause: An invalid file number was specified in the DBA clause of a DUMP
FLASHBACK command.
Action: Supply a valid file number.
ORA-38722: ON or OFF expected.
21-22 Oracle Database Error Messages
Cause: The ALTER DATABASE FLASHBACK command was specified without
the ON or OFF keyword.
Action: Retry the command with the ON or OFF keyword.
ORA-38723: Invalid SCN expression.
Cause: The SCN keyword was specified in a FLASHBACK DATABASE command
but the SCN expression was invalid.
Action: Retry the command using a valid SCN number.
ORA-38724: Invalid option to the FLASHBACK DATABASE command.
Cause: An invalid option was specified to the FLASHBACK DATABASE
command. Valid options are: SCN or TIMESTAMP.
Action: Correct the syntax and retry the command.
ORA-38725: specified name "string" does not match actual "string"
Cause: The database name specified in a FLASHBACK DATABASE command did
not match the name of the currently mounted database.
Action: Correct the database name spelling or DISMOUNT the mounted database
and mount the correct database.
ORA-38726: Flashback database logging is not on.
Cause: A FLASHBACK DATABASE command was tried but flashback database
logging has not been enabled.
Action: Flashback database logging must be enabled via the ALTER DATABASE
FLASHBACK ON command before a FLASHBACK DATABASE command can be
tried. If the database must be taken back in time then a restore and incomplete
recovery must be performed.
ORA-38727: FLASHBACK DATABASE requires a current control file.
Cause: The control file being used is a backup control file.
Action: FLASHBACK DATABASE cannot be used with a backup control file. If
the database must be taken back in time then a restore and an incomplete recovery
must be performed.
ORA-38728: Cannot FLASHBACK DATABASE to the future.
Cause: An SCN or time stamp provided in a FLASHBACK DATABASE command
was in the future.
Action: Supply a proper SCN or time stamp and retry the command.
ORA-38729: Not enough flashback database log data to do FLASHBACK.
Cause: There was not enough flashback database log data to do the FLASHBACK
DATABASE.
Action: If the database must be taken back in time then a restore and incomplete
recovery must be performed.
ORA-38730: Invalid SCN/TIMESTAMP expression.
Cause: The expression supplied in a FLASHBACK DATABASE command was
invalid.
Action: Retry the command using a valid number or time stamp expression.
ORA-38731: Expected version string does not match string in log header.
Cause: The version of the flashback database log file header was corrupt.
ORA-38029 to ORA-39965 21-23
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38732: Expected file size string does not match string.
Cause: The file size indicated in the control file did not match the file size
contained in the flashback log file header. The flashback database log file was
corrupt.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38733: Physical size string less than needed string.
Cause: A flashback database log file shrank in size. This was likely to have been
caused by operator or operating system error.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38734: Flashback log is inconsistent; belongs to another database.
Cause: The database ID in the flashback database log file did not match the
database ID in the control file.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38735: Wrong log number string in flashback log file header.
Cause: The log file number in the flashback database log file did not match the
control file.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38736: Wrong thread number string in flashback log file header.
Cause: The thread number in the flashback database log file did not match the
control file.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38737: Expected sequence number string doesn't match string
Cause: The flashback database log is corrupted or is an old version.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38738: Flashback log file is not current copy.
Cause: A check of flashback database log file header at database open found that
the flashback database log appeared to be an incorrectly restored backup.
Flashback database log files cannot be backed up and restored.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
21-24 Oracle Database Error Messages
ORA-38739: Flashback log file is more recent than control file.
Cause: The control file change sequence number in the flashback database log file
was greater than the number in the control file. This implies that the wrong control
file was being used. Note that repeatedly causing this error can make it stop
happening without correcting the real problem. Every attempt to open the
database will advance the control file change sequence number until it is great
enough.
Action: FLASHBACK DATABASE can only be used with the current control file.
If it is not available, then a restore and an incomplete recovery must be performed
instead.
ORA-38740: Usable blocks value string is not valid.
Cause: A flashback database log file header contained a usable blocks value
greater than the file size. The flashback database log file file is corrupt.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38741: Formatted blocks value string is not valid.
Cause: The formatted blocks value in the flashback database log file was greater
than the file size. The flashback database log file was corrupt.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38742: Flashback log file has incorrect log reset status.
Cause: The flashback database log file header had log reset data that was different
than the control file. The log was probably an incorrectly restored backup.
Flashback database logs cannot be backed up.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be
performed because of the corrupted log. A restore and an incomplete recovery
must be performed instead.
ORA-38743: Time/SCN is in the future of the database.
Cause: The Time/SCN provided in a FLASHBACK DATABASE command was in
the future of the database.
Action: Retry the command with a correct Time/SCN or RECOVER the database.
ORA-38744: file string is not the same file seen at start of flashback
Cause: A different copy of the file was accessed the last time FLASHBACK
DATABASE looked at the file header. A backup of the file was restored or the
meaning of the file name changed during FLASHBACK DATABASE.
Action: Ensure the correct file is available, then retry FLASHBACK DATABASE.
ORA-38746: error occurred while restoring data block (file# string, block# string)
Cause: An error occurred during a FLASHBACK DATABASE command. See
other errors on error stack.
Action: Investigate why the error occurred. It may be that the flashback database
log data is corrupt. If so, a restore and an incomplete recovery must be performed
instead.
ORA-38747: corrupt before image (file# string, block# string)
ORA-38029 to ORA-39965 21-25
Cause: A corrupt data block before image was encountered during a
FLASHBACK DATABASE command.
Action: The flashback log data is probably corrupt. If so, a restore and an
incomplete recovery must be performed instead.
ORA-38748: cannot flashback data file string - file is in use or recovery
Cause: An attempt to do FLASHBACK DATABASE found that the file was not
available for recovery. Either it was online and the database was open in some
instance, or another process was currently doing media recovery or flashback on
the file.
Action: Do not do FLASHBACK DATABASE.
ORA-38749: A media recovery has been started.
Cause: An attempt was made to start a FLASHBACK DATABASE in the same
session as a media recovery.
Action: Complete or cancel the first media recovery session.
ORA-38750: FLASHBACK DATABASE may not be performed using a dispatcher.
Cause: An attempt was made to use a dispatcher process for FLASHBACK
DATABASE. Memory requirements disallow this recovery method.
Action: Connect to the instance via a dedicated server process to perform
FLASHBACK DATABASE.
ORA-38751: Flashback database log: "string"
Cause: This message reports the filename for details of another message.
Action: Other messages will accompany this message. See the associated
messages for the appropriate action to take.
ORA-38752: file string does not exist
Cause: During an RMAN FLASHBACK DATABASE conversation, a file was
listed which was not part of the database. The RMAN conversation was aborted.
Action: Retry the conversation with the appropriate file numbers.
ORA-38753: Cannot flashback data file string; no flashback log data.
Cause: An attempt to perform a FLASHBACK DATABASE failed because the file
does not have enough flashback log data to cover the time to flash back. Either the
file did not have flashback generation enabled for it, or had flashback generation
turned off for it some time during the time span of the flashback.
Action: The file cannot be flashed back. The file must be taken offline or the
tablespace dropped before continuing with the FLASHBACK DATABASE
command.
ORA-38754: FLASHBACK DATABASE not started; required redo log is not
available
Cause: A FLASHBACK DATABASE command did not start. A redo log needed
for the recovery part of FLASHBACK DATABASE could not be found or accessed.
Action: See trace files for details of the problem.
ORA-38755: Flashback is already turned on for this tablespace.
Cause: An attempt was made to turn on flashback database logging for a
tablespace that already has flashback turned on.
Action: No action required.
21-26 Oracle Database Error Messages
ORA-38756: Flashback is already turned off for this tablespace.
Cause: An attempt was made to turn off flashback database logging for a
tablespace that already has flashback off.
Action: No action required.
ORA-38757: Database must be mounted and not open to FLASHBACK.
Cause: An attempt to Flashback a database was made when the database was not
mounted or was already open.
Action: Mount the database and retry the FLASHBACK command.
ORA-38758: cannot flashback data file string; restored since last recovery
Cause: An attempt to do FLASHBACK DATABASE found that the file was
restored since the last standby recovery. The file cannot be flashed back.
Action: The file must be taken offline before continuing with the FLASHBACK
DATABASE command.
ORA-38759: Database must be mounted by only one instance and not open.
Cause: An attempt to turn on or off Flashback Database logging was made when
the database was open or mounted by more than one instance.
Action: Mount the database in only one instance and retry the command.
ORA-38760: This database instance failed to turn on flashback database
Cause: Database flashback is on but this instance failed to start generating
flashback data. Look in alert log for more specific errors.
Action: Correct the error or turn off database flashback.
ORA-38761: redo log sequence string in thread string, incarnation string could not
be accessed
Cause: A redo log needed for the recovery portion of FLASHBACK could not be
read or opened. The FLASHBACK operation failed.
Action: Restore the log and retry the FLASHBACK command.
ORA-38762: redo logs needed for SCN string to SCN string
Cause: The FLASHBACK DATABASE operation failed. The recovery portion of
FLASHBACK DATABASE needed redo from the first SCN to the second, but one
or more of the redo logs in the range could not be read or opened.
Action: Check the FLASHBACK DATABASE command trace file for a description
of the inaccessible redo logs, restore access to them, and retry the FLASHBACK
DATABASE command.
ORA-38763: flashback not started; enabled threads have changed
Cause: A FLASHBACK DATABASE command did not start. The set of enabled
threads changed during the time to flash back.
Action: The flashback cannot be performed. Perform a restore and an incomplete
recovery instead.
ORA-38764: flashback not started; datafile string enabled threads are different
Cause: A FLASHBACK DATABASE command did not start. The datafile was
restored from a backup taken when the enabled threads were different than at the
time of the flashback.
Action: The flashback cannot be performed. Perform a restore and an incomplete
recovery instead.
ORA-38029 to ORA-39965 21-27
ORA-38765: Flashed back database cannot be opened read-only.
Cause: A complete recovery was performed after a database flashback but the
database was not opened for read-write access, or a FLASHBACK DATABASE
command failed.
Action: If a complete recovery was performed after a database flashback, open the
database for read-write access. If a FLASHBACK DATABASE command failed, fix
what caused the command to fail and retry the command, or recover and open the
database for read-write access.
ORA-38766: cannot flashback data file string; file resized smaller
Cause: An attempt to do FLASHBACK DATABASE found that the file was
shrunk during the time to flash back.
Action: The file cannot be flashed back. The file must be taken offline or the
tablespace dropped before continuing with the FLASHBACK DATABASE
command.
ORA-38767: flashback retention target parameter mismatch
Cause: The value of parameters DB_FLASHBACK_RETENTION_TARGET must
be same in all instances. All databases must have same flashback retention target
parameters.
Action: Check DB_FLASHBACK_RETENTION_TARGET values in all instances.
ORA-38768: resizing datafile string failed
Cause: An operating system error occurred when Flashback Database tried to
shrink (resize) a datafile. Flashback shrinks a file in order to undo the effects of a
file expand, for example, an autoextension of the file.
Action: Recover the database to return it to its previous state, or fix the cause of
the operating system error and retry the Flashback. If that is not possible, then the
file can be taken offline and the Flashback command retried. The file will have to
be restored from a backup and rolled forward.
ORA-38769: FLASHBACK DATABASE failed after modifying data.
Cause: A FLASHBACK DATABASE command failed after modifying the the
database. Look in the alert log for more information about the failure.
Action: Recover the database to return it to its previous state, or fix the cause of
the error and retry the Flashback.
ORA-38770: FLASHBACK DATABASE failed during recovery.
Cause: A FLASHBACK DATABASE command successfully restored the database
but failed during the recovery step. Look in the alert log for more information
about the failure.
Action: Fix the error and then recover the database to the same SCN or timestamp
used in the FLASHBACK DATABASE command.
ORA-38771: unnamed datafile(s) added to control file by flashback recovery
Cause: The recovery step of FLASHBACK DATABASE encountered the creation
of a datafile that could not be added to the control file. An entry has been added to
the control file for the new datafile, but with the file name UNNAMEDnnnn,
where nnnn is the file number. Related error messages provide the file names that
were originally used to create the files.
Action: Rename the file in the control file, or use the ALTER ALTER DATABASE
CREATE DATAFILE command to create a file suitable for recovery. If the file is not
going to be recovered, then take it offline with the FOR DROP option. The
21-28 Oracle Database Error Messages
recovery step of Flashback can be resumed by entering a RECOVERY command
with the same SCN or timestamp as used in the FLASHBACK DATABASE
command. For example, RECOVER AUTOMTAIC DATABASE UNTIL CHANGE
<flashback-scn>.
ORA-38772: cannot add datafile 'string' - file could not be created
Cause: The recovery step of FLASHBACK DATABASE encountered the creation
of a datafile and could not recreate the file. The error from the creation attempt is
displayed in another message. The control file file entry for the file is
'UNNAMEDnnnnn'.
Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the
file.
ORA-38773: cannot add data file 'string' - file already part of database
Cause: The recovery step of FLASHBACK database encountered the creation of a
datafile and could not create the file because the file name is already in use in the
database. The control file file entry for the file is 'UNNAMEDnnnnn'.
Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the
file with a different name.
ORA-38774: cannot disable media recovery - flashback database is enabled
Cause: An attempt was made to disable media recovery while flashback database
was enabled.
Action: Use the ALTER DATABASE FLASHBACK OFF statement to disable
flashback database, then disable media recovery.
ORA-38775: cannot disable recovery area - flashback database is enabled
Cause: An attempt was made to set DB_RECOVERY_FILE_DEST to null while
flashback database was enabled. Flashback database requires DB_RECOVERY_
FILE_DEST to be set.
Action: Use the ALTER DATABASE FLASHBACK OFF statement to disable
flashback database, then disable the recovery area.
ORA-38776: cannot begin flashback generation - recovery area is disabled
Cause: During a database mount, the RVWR process discovered that the recovery
area was disabled. DB_RECOVERY_FILE_DEST must have been set null or
removed from the INIT.ORA file while the database was unmounted.
Action: Flashback database requires the recovery area to be enabled. Either enable
the recovery area by setting the DB_RECOVERY_FILE_DEST and DB_
RECOVERY_FILE_DEST_SIZE initialization parameters, or turn off flashback
database with the ALTER DATABASE FLASHBACK OFF command.
ORA-38777: database must not be started in any other instance
Cause: A command was attempted that required the database to be mounted in
this instance and not started in any other instance. ALTER DATABASE OPEN
RESETLOGS requires that the database be started in only one instance if flashback
database logging is enabled.
Action: Ensure that the no other instances are started. Then retry the command.
ORA-38778: Restore point 'string' already exists.
Cause: The restore point name of the CREATE RESTORE POINT command
already exists. A restore point name must be unique.
ORA-38029 to ORA-39965 21-29
Action: Either use a different name or delete the existing restore point with the
same name.
ORA-38779: cannot create restore point - too many restore points.
Cause: The maximum number of restore points already have been created.
Action: Delete some existing restore point and retry the operation.
ORA-38780: Restore point 'string' does not exist.
Cause: The restore point name of the DROP RESTORE POINT command does not
exist.
Action: No action required.
ORA-38781: cannot disable media recovery - have guaranteed restore points
Cause: An attempt was made to disable media recovery while there is at least one
guaranteed restore point.
Action: Drop all guaranteed restore points and then disable media recovery.
ORA-38782: cannot flashback database to non-guaranteed restore point 'string'
Cause: An attempt was made to flashback database to a non-guaranteed restore
point while flashback database is off. You can only flashback a database to
guaranteed restore point when flashback database is not on.
Action: Consider picking a guaranteed restore point to flashback the database to,
if there is one.
ORA-38783: Instance recovery required.
Cause: An attempt was made to create a restore point when the database is in
mount mode but it was not shutdown cleanly before it was mounted. In order to
create a restore point when the database is mounted, the database must be
shutdown cleanly before it is mounted.
Action: Consider one of the following:
1. Create the restore point after opening the database.
2. Open the database, shut it down cleanly, mount the database, and retry creating
the restore point.
ORA-38784: Cannot create restore point 'string'.
Cause: An attempt to create a restore point failed. See other errors on the error
stack and in the alert log for the specific reason.
Action: Fix the problem and retry.
ORA-38785: Media recovery must be enabled for guaranteed restore point.
Cause: Media recovery is not enabled. Media recovery must be enabled in order
to create a guaranteed restore point.
Action: Turn on media recovery with an ALTER DATABASE ARCHIVELOG
statement and then retry the command.
ORA-38786: Recovery area is not enabled.
Cause: An attempt was made to perform a command that requires Flash recovery
area to be enabled.
Action: Set DB_RECOVERY_FILE_DEST to an appropriate location and retry.
ORA-38787: Creating the first guaranteed restore point requires mount mode when
flashback database is off.
21-30 Oracle Database Error Messages
Cause: While flashback database is not on, an attempt was made to create the first
guaranteed restore point while the database is open.
Action: Mount the database and retry.
ORA-38788: More standby database recovery is needed
Cause: An attempt was made to create a restore point or a guaranteed while a
physical standby database is not cleanly checkpointed.
Action: Perform more standby database recovery via managed standby database
recovery. Cancel managed recovery and retry the command.
ORA-38789: File name is too long.
Cause: The file name provided in the command was longer than the maximum
allowed.
Action: Use a shorter file name.
ORA-38790: BEFORE must be specified with RESETLOGS
Cause: The FLASHBACK DATABASE command included the RESETLOGS
parameter but not the BEFORE parameter.
Action: Retry the command with TO BEFORE RESETLOGS.
ORA-38791: flashback did not start because file string was not in a valid
incarnation
Cause: Flashback could not be started because a file was checkpointed or fuzzy at
a point where the file can neither be restored nor recovered to our restore target. In
order for a file to be brought to the restore target, the file has to be in one of the
incarnations along the ancestral path from the current incarnation to the restore
incarnation.
Action: Manually restore or recover the file to a point where it is in one of the
incarnations along the ancestral path from the current incarnation to the restore
incarnation.
ORA-38792: encountered unknown flashback record from release string
Cause: A Flashback Database logfile contains a record written by a future Oracle
release and is unknown by this release.
Action: The given release of Oracle must be installed in order to use these
flashback database log files.
ORA-38793: cannot FLASHBACK the database or pluggable database to a future
SCN or time
Cause: The Flashback Pluggable Database target SCN or timestamp is greater
than the current database or pluggable database SCN/timestamp and the database
or pluggable database incarnation is not the last opened incarnation.
Action: If the target SCN or timestamp is in the current incarnation or a child
incarnation whose branch point is after the current database or pluggable database
SCN then RECOVER DATABASE or RECOVER PLUGGABLE DATABASE to the
target SCN or time. If the target SCN or timestamp is in a child incarnation whose
branch point is prior to the current database or pluggable database SCN then
FLASHBACK DATABASE to before the branch point. Next, use RMAN to reset the
database or pluggable database to the child incarnation. Finally, RECOVER
DATABASE OR PLUGGABLE DATABASE to the target SCN time.
ORA-38794: Flashback target time not in current incarnation
ORA-38029 to ORA-39965 21-31
Cause: The Flashback Database target timestamp is not in the database's current
incarnation or any of its ancestors.
Action: Use a different target timestamp or use RMAN to reset the database to the
appropriate incarnation.
ORA-38795: WARNING: FLASHBACK DATABASE succeeded but OPEN
RESETLOGS would fail
Cause: FLASHBACK DATABASE succeeded. However, if ALTER DATABASE
OPEN RESETLOGS command was attempted now, it would fail with the specified
error.
Action: Fix the error before trying ALTER DATABASE OPEN RESETLOGS.
ORA-38796: Not enough flashback database log data to undo FLASHBACK.
Cause: There was not enough flashback log data to undo the flashback so a
flashback was not started.
Action: It is still possible to get to the restore target by doing a flashback until the
resetlogs branch point of the restore target is reached. This can be done by
executing multiple "flashback to before resetlogs" commands, or by doing a
flashback to the exact time or SCN of the desired resetlogs branch point. Note that
this flashback cannot be undone should an error occur. The only option is to
complete the flashback.
ORA-38797: Full database recovery required after a database has been flashed back
Cause: An attempt was made to recover some datafiles or tablespaces of a
database after the database had been flashed back. In order to recover control file
and all datafiles correctly, full database recovery is required after a database has
been flashed back.
Action: Recover the whole database instead.
ORA-38798: Cannot perform partial database recovery
Cause: See other other messages on error stack for the cause.
Action: See other other messages on error stack for the action.
ORA-38799: Cannot drop guaranteed restore point internally created for snapshot
standby
Cause: An attempt is made to drop the guaranteed restore point Oracle created
internally for a snapshot standby.
Action: Use the "alter database convert to physical standby" command to convert
the snapshot standby to a normal physical standby. This will automatically
flashback the database and drop this guaranteed restore point.
ORA-38800: Cannot start Redo Apply on the open physical standby database
Cause: An attempt was made to start Redo Apply on an open physical standby
database instance.
Action: Make sure the primary database is at compatibility 11.0.0 or higher. The
redo logs to be recovered on an open physical standby database must be generated
at compatibility 11.0.0 or higher. If you have any redo below 11.0.0 to be applied
on the standby, you must apply them on a mounted standby before restarting
recovery on an open standby when the log format advances to 11.0.0 or higher. If
this is a RAC standby database, make sure the ACTIVE_INSTANCE_COUNT
parameter is not set.
ORA-38801: improper value for ORA_EDITION
21-32 Oracle Database Error Messages
Cause: An improper value was used for ORA_EDITION when trying to specify
an edition to use at login time. The value is not understandable as an identifier, or
is too long.
Action: Correct the value for ORA_EDITION and try again.
ORA-38802: edition does not exist
Cause: This error occurred because a reference was made to an edition that does
not exist or that the current user does not have privileges on.
Action: Check the edition name and verify that the current user has appropriate
privileges on the edition.
ORA-38803: edition is unusable
Cause: This error occurred because a reference was made to an unusable edition.
Action: Use another edition.
ORA-38804: not a legal edition name
Cause: This error occurred because an attempt was made to create an edition
called ORA$BASE, DATABASE_DEFAULT, or USER_DEFAULT. These are not
legal edition names. Or a value provided as an edition name is not understandable
as an identifier, or is too long.
Action: Choose a different name for the edition.
ORA-38805: edition is in use
Cause: An attempt was made to ALTER or DROP an edition that was being used
in another session or was the database default edition.
Action: Retry when the edition is not in use and is not the database default
edition.
ORA-38806: edition is being altered or dropped
Cause: An attempt was made to use an edition that was in the process of being
altered or dropped.
Action: Use a different edition.
ORA-38807: Implementation restriction: an edition can have only one child
Cause: This error occurred because an attempt was made to create more than one
child edition for a parent edition.
Action: Create the edition as a child of the leaf edition.
ORA-38808: edition has a usable parent and a usable child
Cause: An attempt was made to make an edition with a usable parent and a
usable child edition unusable.
Action: An edition with a usable parent and a usable child edition cannot be
made unusable. Retry after either parent or child has been made unusable.
ORA-38809: edition must be unusable
Cause: This error occurred because an attempt was made to drop a usable edition.
Action: Retry after the altering the edition to be unusable.
ORA-38810: Implementation restriction: cannot drop edition that has a parent and a
child
Cause: This error occurred because an attempt was made to drop an edition that
has a parent and a child edition.
ORA-38029 to ORA-39965 21-33
Action: Retry after dropping the parent or child edition.
ORA-38811: need CASCADE option to drop edition that has actual objects
Cause: This error occurred because an attempt was made to drop an edition that
has actual objects.
Action: Specify CASCADE option in drop command.
ORA-38812: maximum number of editions reached
Cause: The number of editions has reached the limit.
Action: Drop some editions before creating new ones.
ORA-38813: editions not supported for schema string
Cause: The Oracle-supplied schema did not support editions.
Action: Do not attempt to enable editions for the specified Oracle-supplied
schema.
ORA-38814: ALTER SESSION SET EDITION must be first statement of transaction
Cause: An attempt was made to execute an edition switch within an open
transaction.
Action: Commit or rollback the transaction and reexecute the statement, or use
DBMS_SESSION.SET_EDITION_DEFERRED if its deferred effect is appropriate.
ORA-38815: ALTER SESSION SET EDITION must be a top-level SQL statement
Cause: An edition switch failed because it was executed from a PL/SQL block or
using recursive SQL.
Action: Execute the statement from a top-level OCI call, or use dbms_session.set_
edition if its deferred effect is appropriate.
ORA-38816: edition has a child that inherits objects from the edition
Cause: This error occurred because an attempt was made to drop an edition that a
child that inherits objects from the edition.
Action: Retry after the child edition has no inherited objects.
ORA-38817: Insufficient privileges
Cause: You did not have sufficient privileges to execute the subprogram package
DBMS_EDITIONS_UTIL.
Action: Obtain the necessary privileges. Please see the package specification for
details.
ORA-38818: illegal reference to editioned object string.string
Cause: An attempt was made to violate the rule "A noneditioned object may not
depend on an editioned object."
Action: Either make this object editioned; or do not make the illegal reference.
ORA-38819: user string owns one or more objects whose type is editionable and
that have noneditioned dependent objects
Cause: An attempt was made to violate the rule "A noneditioned object may not
depend on an editioned object."
Action: Either make sure that those objects owned by this user whose type is
editionable have no noneditioned dependent objects; or use the FORCE option.
ORA-38820: user has evolved object type
21-34 Oracle Database Error Messages
Cause: User could not be edition enabled if it has evolved object type.
Action: Reset the evolved object type first.
ORA-38821: unsupported DBMS_SQL Edition operation
Cause: Could not bind or define ADT, VARRAY, nested table or REF data type
when the specified Edition is different from the current edition.
Action: Use the current Edition.
ORA-38822: referential integrity constraints not allowed on editioned views
Cause: An attempt was made to create a referential integrity constraint to or from
an editioned view or enable editions for a user that has views with referential
integrity constraints.
Action: Do not attempt to create editioned views with referential integrity
constraints.
ORA-38823: Crossedition triggers are not allowed to exist when dropping the root
edition
Cause: An attempt was made to drop the root edition when enabled crossedition
trigger exists.
Action: Drop or disable all the crossedition triggers before dropping the root
edition.
ORA-38824: A CREATE OR REPLACE command may not change the
EDITIONABLE property of an existing object.
Cause: An attempt was made to replace an existing object with a different value
for the EDITIONABLE property.
Action: Switch the EDITIONABLE property in the REPLACE statement, or alter
the existing object to have an EDITIONABLE property matching the
EDITIONABLE property in the REPLACE statement.
ORA-38825: The EDITIONABLE property of an editioned object cannot be altered.
Cause: An attempt was made to alter the EDITIONABLE property of an object
whose type has been enabled for editioning in the owner's schema.
Action: Drop the object and re-create it with the desired EDITIONABLE state.
ORA-38826: The EDITIONABLE property of a TYPE or PACKAGE specification
and its body must match.
Cause: An attempt was made to create a TYPE or PACKAGE specification or body
whose EDITIONABLE property did not match its counterpart.
Action: Switch the EDITIONABLE property in the CREATE statement, or alter the
existing object to have an EDITIONABLE property matching the EDITIONABLE
property in the CREATE statement.
ORA-38850: an enabled thread missing from control file
Cause: A CREATE CONTROLFILE statement was given that did not list all the
enabled threads for the database.
Action: Reissue the CREATE CONTROLFILE statement, including all enabled
threads.
ORA-38851: cannot mark the current instance (redo thread) as disabled
Cause: The standby switchover or failover operation failed because it needs to
mark the current instance (redo thread) as disabled.
ORA-38029 to ORA-39965 21-35
Action: Shut down this instance and start up using a different instance name or
redo thread number and retry.
ORA-38852: cannot mark the current instance (redo thread) as disabled
Cause: The open resetlogs or standby activation operation failed because it must
use a different instance (redo thread) than the current instance (redo thread) to
open the database.
Action: Shut down this instance and start up using a different instance name or
redo thread number and retry.
ORA-38853: cannot mark instance string (redo thread string) as disabled
Cause: The standby switchover or failover operation failed because it needs to
mark an instance (redo thread) as disabled. That instance was up, which
prevented it from being disabled.
Action: Shut down the specified instance and retry this command.
ORA-38854: cannot mark instance string (redo thread string) as disabled
Cause: The open resetlogs or standby activation operation failed because it needs
to mark an instance (redo thread) as disabled. That instance was up, which
prevented it from being disabled.
Action: Shut down the specified instance and retry this command.
ORA-38855: cannot mark instance string (redo thread string) as enabled
Cause: The standby switchover or failover operation failed because it needs to
mark an instance (redo thread) as enabled. However, it had less than 2 online redo
logs, which prevented it from being enabled.
Action: Add more logfiles to the specified instance and retry the command.
ORA-38856: cannot mark instance string (redo thread string) as enabled
Cause: The open resetlogs or standby activation operation failed because it needs
to mark an instance (redo thread) as enabled. However, it had less than 2 online
redo logs, which prevented it from being enabled.
Action: Add more logfiles to the specified instance and retry the command.
ORA-38857: cannot mark redo thread string as enabled
Cause: The standby switchover or failover operation failed because it needs to
mark a redo thread as enabled. However, the control file was recreated with a
MAXINSTANCES value smaller than the thread number of the redo thread.
Action: Recreate the control file with a larger MAXINSTANCES value.
ORA-38858: cannot mark redo thread string as enabled
Cause: The open resetlogs or standby activation operation failed because it needs
to mark a redo thread as enabled. However, the control file was recreated with a
MAXINSTANCES value smaller than the thread number of the redo thread.
Action: Recreate the control file with a larger MAXINSTANCES value.
ORA-38859: instance string (thread string) is not ready to be disabled
Cause: The command attempted to switch the instance (thread) into a new log
before disabling it. The switch attempt failed because all eligible online logs were
either being cleared or not completely archived yet.
Action: Wait a few minutes and retry.
21-36 Oracle Database Error Messages
ORA-38860: cannot FLASHBACK DATABASE during instantiation of a logical
standby
Cause: The command was not permitted because the controlfile indicates the
database was in the process of becoming a logical standby database but the
controlfile conversion had not completed.
Action: If in the process of creating a logical standby database, perform the
remaining instantiation procedures to completion. If this flashback operation
followed a Data Guard failure, permit the errant Data Guard operation to
successfully complete. Once the instantiation is complete, reissue the flashback
operation.
ORA-38861: flashback recovery stopped before reaching recovery target
Cause: Flashback recovery on the standby ended early because the user
attempted to flashback to an SCN or time for which there were no redo logs. Most
likely, the user is trying to flashback to a future time in the database that the
database has never recovered through. Check the alert log to find out which SCN
the database recovered to.
Action: Flashback to an older SCN or acquire the necessary redo logs.
ORA-38862: Flashback database logs are in use.
Cause: The command could not be performed because the flashback database logs
were locked by another operation, such as FLASHBACK DATABASE or a query of
V$FLASHBACK_DATABASE_LOG.
Action: Wait for the other operation to complete.
ORA-38863: datafile string has been restored from an optimized RMAN backup.
Cause: Flashback Database could not flash back the file because it was restored
from an RMAN optimized backup with deallocated objects. Flashback cannot
revert the file to a time before the last deallocation in the datafile backup.
Action: Restore the file from a backup prior to the Flashback target SCN or time
and then retry the command.
ORA-38864: cannot create a guaranteed restore point with user specified SCN or
time.
Cause: An SCN or timestamp was specified when creating a guaranteed restore
point. This is not supported. You can only create a guaranteed restore point as of
the current time.
Action: Avoid this combination of options for creating a restore point.
ORA-38865: cannot create restore point for a future SCN or time.
Cause: An attempt was made to create a restore point with an SCN or timestamp
that is in the future.
Action: Revise the SCN or timestamp specified so that it is an SCN or timestamp
in the past.
ORA-38866: cannot create restore point for an SCN or time before current database
incarnation.
Cause: An attempt was made to create a restore point with an SCN or timestamp
that is before the beginning of the current database incarnation.
Action: Revise the SCN or timestamp specified so that it is within current
database incarnation.
ORA-38029 to ORA-39965 21-37
ORA-38867: database not open: cannot create restore point with the specified
timestamp
Cause: An attempt was made to create a restore point with the specified
timestamp while the database was not open. The database must be open in order
to map the timestamp to an SCN.
Action: Open the database first or pick another way to create the restore point.
ORA-38868: warning: the control file may have incorrect data file structure
Cause: This control file was created or converted based on a control file from a
time different from the time of the database.
Action: Open database and all pluggable databases read-only to synchronize the
control file with the database dictionary. You can also force recovery to proceed by
invoking recovery again.
ORA-38869: datafile string has been restored from an RMAN backup with undo
block compression.
Cause: Flashback Database could not flash back the database because a file was
restored from an RMAN backup with undo block compression, and the Flashback
target was to a time when the missing undo may be needed to open the database.
Action: Restore an earlier backup of the file and retry the command or Flashback
to a later time.
ORA-38870: cannot backup a control file that may have incorrect data file structure.
Cause: This control file was created or converted based on a control file from a
time different from the time of the database.
Action: Open database read-only to synchronize the control file with the database
dictionary to fix the control file.
ORA-38871: cannot enable flashback before open resetlogs after incomplete
recovery.
Cause: To enable flashback on a primary database, the database must be clean
without requiring open resetlogs.
Action: Open resetlogs first and then enable flashback database.
ORA-38872: Cannot perform backup control file recovery if Flashback Database is
enabled.
Cause: RECOVER DATABASE with the BACKUP CONTROLFILE option, or a
database recovery that required the control file be made a backup failed because
Flashback Database was enabled or there was a guaranteed restore point.
Action: Disable Flashback Database or remove the guaranteed restore point and
retry the command.
ORA-38873: missing incarnation information
Cause: Flashback Database failed because incarnation information was not found
in the control file. The Flashback target incarnation was not in the control file or
had a missing parent incarnation.
Action: Register logs from the missing incarnations and retry the command.
ORA-38874: cannot flashback data file string - missing incarnation information
Cause: Flashback Database failed because incarnation information for the start of
the offline range for a file was not found in the control file. Flashback could not
update the file's header with the missing incarnation's resetlogs information.
21-38 Oracle Database Error Messages
Action: Check the trace log for the offline range of the data file. If redo logs from
the missing incarnation can be found, register the logs in the control file and retry
the command.
ORA-38875: FLASHBACK DATABASE not started; in test mode
Cause: The FLASHBACK DATABASE command was not performed because it
was started in test mode.
Action: No action required.
ORA-38876: redo logs not required
Cause: The FLASHBACK DATABASE command was performed in test mode and
determined that no redo logs were required to perform the tested FLASHBACK
DATABASE command.
Action: No action required.
ORA-38877: required redo logs are available
Cause: The FLASHBACK DATABASE command was performed in test mode and
determined that no redo logs required to perform the tested FLASHBACK
DATABASE command were missing.
Action: No action required.
ORA-38878: required redo log is not available
Cause: A redo log needed for the recovery part of FLASHBACK DATABASE
could not be found or accessed.
Action: See trace files for details of the problem.
ORA-38879: Cannot flashback data file string; may not be able to undo all changes.
Cause: A data file was plugged in when there was a guaranteed restore point, but
Flashback Database was not enabled. It is possible that some changes to the data
file, after it was converted, were not logged to the Flashback Database logs.
Action: If the FLASHBACK DATABASE command was meant to rewind the
database to a time before the file was plugged in, take the data file offline and retry
the command. If the FLASHBACK DATABASE command was meant to rewind
the database to a time after the file was plugged in, restore the original version of
the plugged in file and retry the command.
ORA-38880: Cannot advance compatibility from string to string due to guaranteed
restore points
Cause: Flashback database cannot undo the advance of database compatibility.
Therefore, one cannot advance the compatibility of the database while there are
guaranteed restore points in the database.
Action: Drop all guaranteed restore points first and retry, or delay the advance of
database compatibility to a later time.
ORA-38881: Cannot drop tablespace string on primary database due to guaranteed
restore points.
Cause: An attempt was made to drop a tablespace on a primary database while
there are guaranteed restore points. You cannot do this because Flashback
database cannot undo dropping of a tablespace.
Action: Drop all guaranteed restore points first and retry, or delay dropping the
tablespace until all guaranteed restore points are removed.
ORA-38029 to ORA-39965 21-39
ORA-38882: Cannot drop tablespace string on standby database due to guaranteed
restore points.
Cause: An attempt was made to drop a tablespace on a standby database while
there are guaranteed restore points. You cannot do this because Flashback
database cannot undo dropping of a tablespace.
Action: Drop all guaranteed restore points and rerun recovery on standby
database.
ORA-38883: Cannot shrink data file string on primary database due to guaranteed
restore points.
Cause: An attempt was made to shrink a data file on a primary database while
there are guaranteed restore points. You cannot do this because Flashback
database cannot undo the shrinking of a data file.
Action: Drop all guaranteed restore points first and retry, or delay the data file
resize until all guaranteed restore points are removed.
ORA-38884: Cannot shrink data file string on standby database due to guaranteed
restore points.
Cause: An attempt was made to shrink a data file on a standby database while
there are guaranteed restore points. You cannot do this because Flashback
database cannot undo the shrinking of a data file.
Action: Drop all guaranteed restore points and rerun recovery on standby
database.
ORA-38885: WARNING: Flashback database has been disabled while fast-start
failover is enabled.
Cause: Flashback database was disabled while fast-start failover was enabled.
Action: Enable flashback database if fast-start failover is enabled.
ORA-38886: WARNING: Flashback database was disabled due to error when
writing flashback database logs.
Cause: Recovery writer (RVWR) encountered an error when writing flashback
database logs.
Action: See the error stack in the alert log.
ORA-38887: WARNING: Recovery writer (RVWR) hang due to error when writing
flashback database logs.
Cause: An error occurred while writing to the flashback database logs.
Action: Shutdown the instance or turn off flashback database.
ORA-38888: invalid redo thread number
Cause: The provided thread number was invalid.
Action: Specify a valid redo thread number.
ORA-38900: missing mandatory column "string" of error log table "string"
Cause: Mandatory column of error logging table is not present
Action: Add the named column to the error logging table. Consult ORACLE
documentation for the correct data type.
ORA-38901: column "string" of table "string" must be one of the first "string"
columns
21-40 Oracle Database Error Messages
Cause: Mandatory information column of error logging table is present, but must
be at the beginning of the row.
Action: Create the error logging table correctly. Consult ORACLE documentation
for the correct format of an error logging table.
ORA-38902: errors in array DML exceed string
Cause: The operation failed because the array DML had more errors than can be
stored internally for BATCH ERRORs.
Action: Do not use BATCH ERROR mode when array DML has more error rows
than the number specified in the error.
ORA-38903: DML error logging is not supported for abstract column "string"
Cause: A DML Error Logging operation was attempted on a table which has an
ADT, REF, VARRAY, or nested table column type, and the error logging table
referred to the specified column.
Action: Either do not use DML Error Logging on such a table or remove the
offending column from the error logging table. The scalar columns can be logged,
but not abstract column types.
ORA-38904: DML error logging is not supported for LOB column "string"
Cause: A DML Error Logging operation was attempted on a table which has a
CLOB, NCLOB, or BLOB column type, and the error logging table referred to the
specified column.
Action: Either do not use DML Error Logging on such table or remove the
offending column from the error logging table. The scalar columns can be logged,
but not LOB column types.
ORA-38905: DML error logging is not supported for LONG column "string"
Cause: A DML Error Logging operation was attempted on a table which has a
LONG, or LONG RAW column type, and the error logging table referred to the
specified column.
Action: Either do not use DML Error Logging on such a table or remove the
offending column from the error logging table. The scalar columns can be logged,
but not long column types.
ORA-38906: insert into DML Error Logging table "string" failed
Cause: An error occurred when attempting to log a DML Error on behalf of the
DML Error logging clause. This may be intended if a trigger is defined on the error
table (which in turn errors out in certain cases).
Action: Determine root cause of error (in error stack).
ORA-38907: DML error logging is not supported for FILE column "string"
Cause: A DML Error Logging operation was attempted on a table which has a
BFILE column and the Error Logging table referred to the specified column.
Action: Either don't use DML Error Logging on such table or remove the
offending column from the error logging table. The scalar columns can be logged,
but not BFILE column types.
ORA-38908: internal error occurred during DML Error Logging
Cause: An unexpected error occurred while executing recursive SQL to insert a
row into the DML Error Logging table.
Action: Report this error to Oracle Support.
ORA-38029 to ORA-39965 21-41
ORA-38909: DML Error logging is not supported with BATCH ERROR mode
Cause: A DML Error Logging operation was attempted on a table which has
BATCH ERROR mode also specified.
Action: Refrain from using both DML Error Logging and BATCH ERROR mode
on the same table.
ORA-38910: BATCH ERROR mode is not supported for this operation
Cause: BATCH ERROR mode specified for this operation.
Action: Refrain from using BATCH ERROR mode with this operation.
ORA-38911: unique constraint (string.string) violated
Cause: An INSERT statement with a CHANGE_DUPKEY_ERROR_INDEX hint
tried to insert a duplicate key into a table.
Action: Either remove the unique restriction or do not insert the key.
ORA-38912: An index must be specified in the index hint
Cause: Index specification was missing in an IGNORE_ROW_ON_DUPKEY_
INDEX or CHANGE_DUPKEY_ERROR_INDEX hint.
Action: In the hint, specify a unique index that exists on the table.
ORA-38913: Index specified in the index hint is invalid
Cause: The index specified in an IGNORE_ROW_ON_DUPKEY_INDEX or
CHANGE_DUPKEY_ERROR_INDEX hint could not be found.
Action: Specify a unique index that exists on the table. The index cannot be a
non-unique index or a bitmap index.
ORA-38914: Either mutate the error or ignore row on unique violation
Cause: IGNORE_ROW_ON_DUPKEY_INDEX and CHANGE_DUPKEY_
ERROR_INDEX were both specified in the same statement.
Action: You cannot specify both hints in the same statement. Remove one of these
two hints, or both, from the statement.
ORA-38915: Multiple indexes in change or ignore duplicate key hint
Cause: Multiple indexes were specified in an IGNORE_ROW_ON_DUPKEY_
INDEX or CHANGE_DUPKEY_ERROR_INDEX hint.
Action: Only one index must be specified in the hint.
ORA-38916: CHANGE_DUPKEY_ERROR_INDEX hint disallowed for this
operation
Cause: CHANGE_DUPKEY_ERROR_INDEX hint was specified for the operation.
Action: You cannot specify this hint for this operation. Remove the hint from the
statement.
ORA-38917: IGNORE_ROW_ON_DUPKEY_INDEX hint disallowed for this
operation
Cause: IGNORE_ROW_ON_DUPKEY_INDEX hint was specified for the
operation.
Action: You cannot specify this hint for this operation. Remove the hint from the
statement.
ORA-38918: RETRY_ON_ROW_CHANGE hint disallowed for this operation
Cause: RETRY_ON_ROW_CHANGE hint was specified for the operation.
21-42 Oracle Database Error Messages
Action: You cannot specify this hint for this operation. Remove the hint from the
statement.
ORA-38919: remote table not supported for DML error logging
Cause: A remote table was specified in the DML error logging clause.
Action: You cannot specify a remote table to which errors will be logged. Specify a
local table only.
ORA-38950: Source platform string not cross platform compliant
Cause: Cross platform transport was not allowed for this platform.
Action: For a list of supported platforms, query fixed view
SYS.V$TRANSPORTABLE_PLATFORM.
ORA-38951: Target platform string not cross platform compliant
Cause: Cross platform transport was not allowed for this platform.
Action: None
ORA-38952: Source database not 10.0.0.0 compatible
Cause: Cross platform transport is not supported unless database compatibility is
advanced to 10.0.0.0 or higher
Action: Use the compatible parameter to advance source database compatibility
and redo the transport
ORA-38954: Cross platform transport is not supported between source platform
identifier string and target platform identifier string
Cause: The platform identifier in the transported file indicated that the datafile
format was different than the target database datafile format.
Action: For a list of supported platforms, query fixed view
SYS.V$TRANSPORTABLE_PLATFORM. If both platforms are present, Contact
Oracle support
ORA-38955: Source platform string not cross platform compliant
Cause: The platform identifier in the transported file indicated that this platform
is not supported for a cross platform transport.
Action: For a list of supported platforms, query fixed view
SYS.V$TRANSPORTABLE_PLATFORM.
ORA-38956: Target platform string not cross platform compliant
Cause: Cross platform transport was not allowed for this platform.
Action: For a list of supported platforms, query fixed view
SYS.V$TRANSPORTABLE_PLATFORM.
ORA-38958: Source platform string is in different byte order than target platform
string
Cause: Probably a conversion was not done before the import phase of the
transport.
Action: Use RMAN CONVERT functionality to convert endian ordering.
ORA-38959: Failed to update block 0 to new version 10 format
Cause: An attempt was made to update block 0 to version 10 format.
Action: check additional error messages and contact Oracle Support Services.
ORA-38029 to ORA-39965 21-43
ORA-38960: File string from platform string is not compatible with current platform
string
Cause: The file was directly copied to this platform from a platform with a
different endian ordering.
Action: Use RMAN CONVERT functionality to convert endian ordering.
ORA-38961: data file: string
Cause: Reporting file name for details of another error.
Action: See associated error message.
ORA-39000: bad dump file specification
Cause: The user specified a dump file that could not be used in the current job.
Subsequent error messages describe the inadequacies of the dump file.
Action: Specify a dump file that is usable for the job.
ORA-39001: invalid argument value
Cause: The user specified API parameters were of the wrong type or value range.
Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further
describe the error.
Action: Correct the bad argument and retry the API.
ORA-39002: invalid operation
Cause: The current API cannot be executed because of inconsistencies between
the API and the current definition of the job. Subsequent messages supplied by
DBMS_DATAPUMP.GET_STATUS will further describe the error.
Action: Modify the API call to be consistent with the current job or redefine the
job in a manner that will support the specified API.
ORA-39003: unable to get count of total workers alive
Cause: Attempt to get count of total worker processes alive failed.
Action: Check the additional error messages to see what caused the failure.
Correct the error, if possible, and try the operation again. If this error occurs from a
Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs
again, contact Oracle Customer Support and report the error.
ORA-39004: invalid state
Cause: The state of the job precludes the execution of the API.
Action: Rerun the job to specify the API when the job is an appropriate state.
ORA-39005: inconsistent arguments
Cause: The current API cannot be executed because of inconsistencies between
arguments of the API call. Subsequent messages supplied by DBMS_
DATAPUMP.GET_STATUS will further describe the error.
Action: Modify the API call to be consistent with itself.
ORA-39006: internal error
Cause: An unexpected error occurred while processing a Data Pump job.
Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further
describe the error.
Action: Contact Oracle Customer Support.
ORA-39012: Client detached before the job started.
21-44 Oracle Database Error Messages
Cause: The client detached or ended their session before the Data Pump job was
started.
Action: Create new job and remain attached to the job until it is started.
ORA-39013: Remapping the SYSTEM schema is not supported.
Cause: A remap_schema transform with the SYSTEM schema was specified.
Action: Retry the import command without remapping the SYSTEM schema.
ORA-39014: One or more workers have prematurely exited.
Cause: One or more of the worker processes exited before the job was completed.
With no workers, the master process will terminate the job.
Action: Rerun the job. If problem persists, contact Oracle Customer Support.
ORA-39015: job is not running
Cause: An API was executed that required the job to be running, but the job was
not active.
Action: Retry the API. If problem persists, contact Oracle Customer Support.
ORA-39016: Operation not supported when job is in string state.
Cause: The state of the job precludes the execution of the API.
Action: Rerun the job to specify the API when the job is an appropriate state.
ORA-39017: Worker request not supported when job is in string state.
Cause: The state of the job precludes the execution of a worker request. This is an
internal error.
Action: Contact Oracle Customer Support.
ORA-39018: master process received invalid message number string
Cause: Internal Error
Action: Contact Oracle Customer Support.
ORA-39019: invalid operation type string
Cause: User specified an invalid operation name on an DBMS_
DATAPUMP.OPEN API or an invalid operation name was specified in the master
table for a restart API.
Action: Correct the operation name and recreate the job.
ORA-39020: invalid mode type string
Cause: User specified an invalid mode on an DBMS_DATAPUMP.OPEN API or
an invalid mode was specified in the master table for a restart API.
Action: Correct the mode and recreate the job.
ORA-39021: Database compatibility version string is not supported.
Cause: User selected COMPATIBLE as the version on an DBMS_
DATAPUMP.OPEN API, but the current database compatibility version is not
supported by the Data Pump API. Database versions before 9.2 are not supported
by the Data Pump.
Action: Specify a supported version and recreate the job.
ORA-39022: Database version string is not supported.
ORA-38029 to ORA-39965 21-45
Cause: User selected LATEST as the version on an DBMS_DATAPUMP.OPEN
API, but the current database version is not supported by the Data Pump API.
Database versions before 9.2 are not supported by the Data Pump.
Action: Specify a supported version and recreate the job.
ORA-39023: Version string is not supported.
Cause: User specified an explicit version on an DBMS_DATAPUMP.OPEN API,
but the current database version is not supported by the Data Pump API. Database
versions before 9.2 are not supported by the Data Pump.
Action: Specify a supported version and recreate the job.
ORA-39024: wrong schema specified for job
Cause: Internal error caused by the master process finding inconsistencies
between the schemas specified for the job.
Action: Contact Oracle Customer Support.
ORA-39025: jobs of type string are not restartable
Cause: Attempt to restart a job which was not restartable.
Action: Recreate the job via the open API.
ORA-39026: master table is inconsistent on validation string
Cause: Job cannot be restarted because it failed a validation check. Validation
checks are of the form -xx.y where -xx is the value of the PROCESS_ORDER
column in the master table where the error was detected and y is the actual
validity check for the row.
Action: Recreate the job. If master table has not been modified, but problem
persists, contact Oracle Customer Support.
ORA-39027: wrong version of master table
Cause: Job cannot be restarted because the version of the database upon which
the job started is different than the current version of the database and the format
of the master table has changed between the versions.
Action: Recreate the job.
ORA-39028: cannot restart job from string state
Cause: The job was not in a suitable state for restart. Jobs must begin executing
before they can be restarted.
Action: Recreate the job.
ORA-39029: worker string with process name "string" prematurely terminated
Cause: The specified worker process terminated unexpectedly. Subsequent
messages describe the reason for the termination.
Action: In many cases, the Data Pump will attempt to automatically restart the
worker. If problem persists, contact Oracle Customer Support.
ORA-39030: invalid file type string
Cause: An invalid filetype was specified for an DBMS_DATAPUMP.ADD_FILE
API call.
Action: Correct the filetype parameter and reissue the API request.
ORA-39031: invalid filter name string
21-46 Oracle Database Error Messages
Cause: An invalid filter name was specified on a DBMS_DATAPUMP.DATA_
FILTER API call.
Action: Correct the filter name parameter and reissue the API request.
ORA-39032: Parameter string is not supported in string jobs.
Cause: The specified parameter was not supported for the specified class of jobs.
Action: Re-create the job with the appropriate mode or operation type.
ORA-39033: Data cannot be filtered under the direct path access method.
Cause: The user specified that the data access method for the job was direct which
precludes the use of certain data filters.
Action: Use the SUBQUERY or the SAMPLE data filter with the automatic data
access method.
ORA-39034: Table string does not exist.
Cause: The user referenced a table in an API that did not exist.
Action: Correct table name and retry API.
ORA-39035: Data filter string has already been specified.
Cause: The user has already specified a data filter that matches on the filter name,
schema name, and table.
Action: Specify a different data filter.
ORA-39036: invalid metadata filter name string
Cause: An invalid metadata filter name was specified on a DBMS_
DATAPUMP.METADATA_FILTER API call.
Action: Correct the metadata filter name parameter and reissue the API request.
ORA-39037: Object type path not supported for string metadata filter.
Cause: An object type path was specified for the filter, but the filter does not
support the object type path parameter.
Action: Remove the object type path parameter.
ORA-39038: Object path "string" is not supported for string jobs.
Cause: The specified object type path is invalid for the job mode.
Action: Correct the object type path.
ORA-39039: Schema expression "string" contains no valid schemas.
Cause: The specified SCHEMA_EXPR filter resulted in no schemas being selected.
Action: Correct the the SCHEMA_EXPR filter specification.
ORA-39040: Schema expression "string" must identify exactly one schema.
Cause: For TABLE mode jobs, the SCHEMA_EXPR filter must identify exactly one
schema.
Action: Correct the the SCHEMA_EXPR filter specification.
ORA-39041: Filter "string" either identifies all object types or no object types.
Cause: A Metadata filter specifying path names either returned all objects or no
objects in the job.
Action: Correct the the metadata filter specification.
ORA-39042: invalid transform name string
ORA-38029 to ORA-39965 21-47
Cause: An invalid transform name was specified on a DBMS_
DATAPUMP.METADATA_TRANSFORM API call.
Action: Correct the transform name parameter and reissue the API request.
ORA-39043: Object type string is not supported for string.
Cause: The specified object type is invalid for the specified transform or remap.
Action: Correct the object type.
ORA-39044: Metadata transform string has already been specified.
Cause: The user has already specified the metadata transform for the same class
of object types.
Action: Specify a different object_type for the transform.
ORA-39045: invalid metadata remap name string
Cause: An invalid metadata remap name was specified on a DBMS_
DATAPUMP.METADATA_REMAP API call.
Action: Correct the metadata remap name parameter and reissue the API request.
ORA-39046: Metadata remap string has already been specified.
Cause: The user has already specified a metadata remap that matches on the
remap name and original value.
Action: Specify a different original value.
ORA-39047: Jobs of type string cannot use multiple execution streams.
Cause: The user specified a value of parallelism that is precluded by the operation
type or mode of the job.
Action: Specify only a parallelism of 1 for this type of job.
ORA-39048: Unable to start all workers; only string worker(s) available.
Cause: The full degree of parallelism could not be honored due process limits,
resource limits, or other internal errors.
Action: Increase process/resource limits for the job.
ORA-39049: invalid parameter name string
Cause: An invalid parameter name was specified on a DBMS_DATAPUMP.SET_
PARAMETER API call.
Action: Correct the parameter name and reissue the API request.
ORA-39050: parameter string is incompatible with parameter string
Cause: Two parameters were set that were incompatible with each other. Only the
first parameter setting will be used.
Action: Decide which parameter is to be used and stick to it.
ORA-39051: parameter string specified multiple times
Cause: The user has already specified a parameter that matches on the name and
the specific parameter doesn't support duplicate definitions.
Action: Specify non-repeatable parameters only once.
ORA-39052: cannot specify SKIP_CURRENT on initial start of a job.
Cause: The user has already specified SKIP_CURRENT for a job that has never
executed.
Action: Only specify SKIP_CURRENT when restarting a job.
21-48 Oracle Database Error Messages
ORA-39053: parameter or attribute string must be defined for a string job
Cause: The job being defined cannot be started because it is missing the specified
definition.
Action: Specify the omitted parameter or attribute before starting the job.
ORA-39054: missing or invalid definition of the SQL output file.
Cause: The job being defined cannot be started because it is missing the file to
receive the SQL output of the job or the definition is unusable.
Action: Specify a valid directory name and file name for the SQL file.
ORA-39055: The string feature is not supported in version string.
Cause: The user attempted to use a feature that was not enabled in the database
version specified for the current job. Typically, this error occurs if the compatibility
level of the database is below the current version of the database or if the user
explicitly specifies a version for a Data Pump job.
Action: Specify the current database version as a version parameter for the the
job.
ORA-39056: invalid log file specification.
Cause: The log file for the job was incorrectly specified.
Action: Specify a valid directory name and file name for the log file.
ORA-39057: invalid worker request string for string jobs.
Cause: The worker process sent a message that wasn't supported for the current
job.
Action: Internal error -- contact Oracle Customer Support and report the error.
ORA-39058: current object skipped: string of type string
Cause: The user specified SKIP_CURRENT when restarting a job. This message is
a confirmation that the object will not be imported.
Action: User must manually define the object in the target database.
ORA-39059: dump file set is incomplete
Cause: An IMPORT or SQL_FILE operation was being performed but not all of
the files from the EXPORT dump file set were included.
Action: Check the export log file and make sure all of the files that were exported
are included in the current job.
ORA-39060: table(s) dropped because of conflict with master table
Cause: A table specified by a job was not included because its definition would
collide with the master table definition for the current job.
Action: After the job completes. Import the conflicting tables using a unique job
name to avoid conflicts with normal user tables.
ORA-39061: import mode string conflicts with export mode string
Cause: The mode used for import cannot be used with a dump file set of specified
mode. Transportable jobs are not compatible with other modes.
Action: Perform the import using a mode compatible with the export.
ORA-39062: error creating master process string
Cause: An attempt to create the listed master process failed.
ORA-38029 to ORA-39965 21-49
Action: Refer to any following error messages for possible actions. Check the trace
log for the failed process to see if there is any information about the failure.
Correct the error, if possible, and try the operation again. If the error occurs again,
contact Oracle Customer Support and report the error.
ORA-39064: unable to write to the log file
Cause: Errors were detecting while writing to the log file. Subsequent messages
will detail the problems.
Action: Fix the problems outlined in the secondary messages.
ORA-39065: unexpected master process exception in string
Cause: An unhandled exception was detected internally within the master control
process for the Data Pump job. This is an internal error. messages will detail the
problems.
Action: If problem persists, contact Oracle Customer Support.
ORA-39067: Unable to close the log file.
Cause: Errors were detecting while closing the log file. Subsequent messages will
detail the problems.
Action: Fix the problems outlined in the secondary messages.
ORA-39068: invalid master table data in row with PROCESS_ORDER=string
Cause: A corruption was detected in the master table in the specified row(s).
Either the row wasn't found, it was missing columns or had illegal values in its
columns.
Action: Rerun the job with an uncorrupted master table.
ORA-39070: Unable to open the log file.
Cause: Errors were detecting while opening the log file. Subsequent messages will
detail the problems.
Action: Fix the problems outlined in the secondary messages.
ORA-39071: Value for string is badly formed.
Cause: The value of the user specified filter did not contain a legitimate SQL
clause. Subsequent messages will detail the problems.
Action: Fix the problems outlined in the secondary messages.
ORA-39076: cannot delete job string for user string
Cause: Unable to delete a job. Refer to the any following or prior error messages
for clarification.
Action: Eliminate the problems indicated.
ORA-39077: unable to subscribe agent string to queue "string"
Cause: The Data Pump's communication layer was unable to attach one of its
processes to the control or status queue. Subsequent messages will detail the
problem.
Action: Fix the problem if possible, or contact Oracle Customer Support.
ORA-39078: unable to dequeue message for agent string from queue "string"
Cause: The Data Pump's communication layer was unable to retrieve a message
from the control or status queue. Subsequent messages will detail the problem.
Action: Fix the problem if possible, or contact Oracle Customer Support.
21-50 Oracle Database Error Messages
ORA-39079: unable to enqueue message string
Cause: The Data Pump's communication layer was unable to send the specified
message on the control or status queue. Subsequent messages will detail the
problem.
Action: Fix the problem if possible, or contact Oracle Customer Support.
ORA-39080: failed to create queues "string" and "string" for Data Pump job
Cause: The Data Pump's communication layer was unable to create the status and
control queues required for interprocess communication. Subsequent messages
will detail the problem.
Action: Fix the problem if possible, or contact Oracle Support.
ORA-39081: failed to unsubscribe agent string from queue "string"
Cause: The Data Pump's communication layer was unable to unsubscribe a
process from the control or status queue. Subsequent messages will detail the
problem.
Action: Fix the problem if possible, or contact Oracle Customer Support.
ORA-39082: Object type string created with compilation warnings
Cause: The object in the SQL statement following this error was created with
compilation errors. If this error occurred for a view, it is possible that the base table
of the view was missing.
Action: This is a warning. The object may have to be recompiled before being
used.
ORA-39083: Object type string failed to create with error: string Failing sql is: string
Cause: Examine original error code to determine actual cause
Action: Original error code will contain more information
ORA-39084: cannot detach job string for user string
Cause: Unable to detach a job from the session. Refer to any following error
messages for clarification.
Action: Eliminate the problems indicated.
ORA-39085: cannot update job string for user string
Cause: Unable to update the fixed table information for a job. Refer to any
following or prior error messages for clarification.
Action: Eliminate the problems indicated.
ORA-39086: cannot retrieve job information
Cause: Unable to retrieve fixed table information for a job. Refer to the secondary
error messages that follow this one for clarification.
Action: Eliminate the problems indicated by the secondary errors.
ORA-39087: directory name string is invalid
Cause: A corresponding directory object does not exist.
Action: Correct the directory object parameter, or create a corresponding directory
object with the CREATE DIRECTORY command.
ORA-39088: file name cannot contain a path specification
Cause: The name of a dump file, log file, or sql file contains a path specification.
ORA-38029 to ORA-39965 21-51
Action: Use the name of a directory object to indicate where the file should be
stored.
ORA-39090: Cannot add devices to file oriented job.
Cause: Attempt to add a device to a job that already contains more than one disk
file.
Action: Only specify one file for jobs that contain sequential devices.
ORA-39091: unable to determine logical standby and streams status
Cause: An error occurred when determining if the Data Pump job needed to
support logical standby or streams.
Action: The subsequent message describes the error that was detected. Correct the
specified problem and restart the job.
ORA-39092: unable to set SCN metadata for object "string.string" of type string
Cause: An error occurred when applying a SCN to the specified object to support
logical standby or streams.
Action: The subsequent message describes the error that was detected. Correct the
specified problem and restart the job.
ORA-39093: FLASHBACK automatically enabled to preserve database integrity.
Cause: A Data Pump job was required to enable flashback support to specific
SCNs in order to preserve the consistency of a logical standby or streams
instantiation.
Action: None
ORA-39094: Parallel execution not supported in this database edition.
Cause: Parallel execution of Data Pump jobs is not supported for this database
edition.
Action: Specify a parallelism of 1 for jobs not running on Enterprise Edition
databases.
ORA-39095: Dump file space has been exhausted: Unable to allocate string bytes
Cause: The Export job ran out of dump file space before the job was completed.
Action: Reattach to the job and add additional dump files to the job restarting the
job.
ORA-39096: invalid input value string for parameter string
Cause: A NULL or invalid value was supplied for the parameter.
Action: Correct the input value and try the call again.
ORA-39097: Data Pump job encountered unexpected error string
Cause: An unexpected, potentially non-fatal error occurred while processing a
Data Pump job.
Action: Contact Oracle Customer Support.
ORA-39098: Worker process received data objects while loading metadata. Invalid
process order range is string..string
Cause: This is an internal error. Messages will detail the problem.
Action: If problem persists, contact Oracle Customer Support.
ORA-39099: cannot create index for "string" on master table string
21-52 Oracle Database Error Messages
Cause: One or more indexes couldn't be created on the master table. subsequent
error messages describe the failure.
Action: Correct the condition that is preventing the indexes from being created.
ORA-39102: Timeout before master process string finished initialization. Master
error:
Cause: The master process whose name is listed started up but did not finish its
initialization within the allowed time limit.
Action: Refer to any following error messages for possible actions. Also, check the
trace log for the failed process, if one was created, to see if there is any additional
information about the failure. Correct the error, if possible, and try the operation
again. If the error occurs again, contact Oracle Customer Support and report the
error.
ORA-39103: Timeout before worker process string finished initialization. Worker
error:
Cause: The worker process whose name is listed started up but did not finish its
initialization within the allowed time limit.
Action: Refer to any following error messages for possible actions. Also, check the
trace log for the failed process, if one was created, to see if there is any additional
information about the failure. Correct the error, if possible, and try the operation
again. If the error occurs again, contact Oracle Customer Support and report the
error.
ORA-39104: cannot call this function from a SQL parallel query slave process
Cause: Called a Data Pump process model function from a process which is a SQL
parallel query slave process
Action: A SQL parallel query slave process cannot create a Data Pump master
process. This is not supported. If this error occurs from a Data Pump client (for
example, expdp or impdp), contact Oracle Customer Support and report the error.
ORA-39105: Master process string failed during startup. Master error:
Cause: The master process whose name is listed failed during startup.
Action: Refer to any following error messages for possible actions. Also, check the
trace log for the failed process, if one was created, to see if there is any additional
information about the failure. Correct the error, if possible, and try the operation
again. If the error occurs again, contact Oracle Customer Support and report the
error.
ORA-39106: Worker process string failed during startup. Worker error:
Cause: The worker process whose name is listed failed during startup.
Action: Refer to any following error messages for possible actions. Also, check the
trace log for the failed process, if one was created, to see if there is any additional
information about the failure. Correct the error, if possible, and try the operation
again. If the error occurs again, contact Oracle Customer Support and report the
error.
ORA-39107: Master process string violated startup protocol. Master error:
Cause: The master process whose name is listed started up but then exited before
notifying the creating process that it was finished with initialization.
Action: Refer to any following error messages for possible actions. Also, check the
trace log for the failed process, if one was created, to see if there is any additional
information about the failure. Correct the error, if possible, and try the operation
ORA-38029 to ORA-39965 21-53
again. If the error occurs again, contact Oracle Customer Support and report the
error.
ORA-39108: Worker process string violated startup protocol. Worker error:
Cause: The worker process whose name is listed started up but then exited before
notifying the creating process that it was finished with initialization.
Action: Refer to any following error messages for possible actions. Also, check the
trace log for the failed process, if one was created, to see if there is any additional
information about the failure. Correct the error, if possible, and try the operation
again. If the error occurs again, contact Oracle Customer Support and report the
error.
ORA-39109: Unprivileged users may not operate upon other users' schemas
Cause: An unprivileged user attempted to reference another user's schema during
a Data Pump operation. Because of this, no schemas were were selected for the job.
Action: Retry the operation under a username owning the schema.
ORA-39110: error deleting worker processes
Cause: An attempt to delete the worker processes failed.
Action: Refer to any following error messages for possible actions. Correct the
error, if possible, and try the operation again. If the error occurs again, contact
Oracle Customer Support and report the error.
ORA-39111: Dependent object type string skipped, base object type string already
exists
Cause: During a Data Pump import job, a dependent object is being skipped
because its base object already existed.
Action: If the object from the dump file is wanted, drop the base and dependent
objects and try to import again using desired filters.
ORA-39112: Dependent object type string skipped, base object type string creation
failed
Cause: During a Data Pump import job, a dependent object is being skipped
because its base object creation failed.
Action: If the object from the dump file is wanted, drop the base and dependent
objects and try to import again using desired filters
ORA-39113: Unable to determine database version
Cause: The Data Pump was unable to determine the compatibility level and
version of the current database using SYS.DBMS_UTILITY.DB_VERSION.
Action: Make sure access to the DBMS_UTILITY package is granted to you. If this
is a network job, be sure that access to the DBMS_UTILITY package is granted to
you on the remote instance.
ORA-39114: Dump files are not supported for network jobs.
Cause: An attempt was made to add a dumpfile to an Import job that is using a
network link to the source database.
Action: Do not specify a dumpfile for jobs that do not require dumpfiles.
ORA-39115: string is not supported over a network link
Cause: An attempt was made to use an option that is not supported over network
links such as the PARTITION_LIST filter.
21-54 Oracle Database Error Messages
Action: Do not attempt to use Data Pump features on network jobs if they are not
compatible with jobs over the network.
ORA-39116: invalid trigger operation on mutating table string.string
Cause: A Data Pump load operation failed because a trigger attempted to fire on
the table while it was mutating.
Action: Disable trigger(s) on the specified table. Also see ORA-004091.
ORA-39117: Type needed to create table is not included in this operation. Failing
sql is: string
Cause: A create table was attempted and a dependent type does not exist in the
dumpfile or on the target database. Either the export or the import Data Pump job
was a table mode job and types are not included in table mode jobs.
Action: Determine which type(s) are missing and create them on the target system
and run the Data Pump import job again.
ORA-39119: worker process interrupt for delete worker processes call by master
process
Cause: The master process that created this worker process called delete worker
processes to abort the current operation.
Action: No action is necessary. This is an informational error message.
ORA-39120: Table string can't be truncated, data will be skipped. Failing error is:
string
Cause: Table data was about to be loaded into a table that already existed and the
table_exists_action parameter is truncate, but the table could not be truncated.
Action: Determine actual cause by looking at base error.
ORA-39121: Table string can't be replaced, data will be skipped. Failing error is:
string
Cause: Table data was about to be loaded into a table that already existed and the
table_exists_action parameter is replace, but the table could not be dropped.
Action: Determine actual cause by looking at base error.
ORA-39122: Unprivileged users may not perform string remappings.
Cause: A user attempted to remap objects during an import but lacked the
IMPORT_FULL_DATABASE privilege.
Action: Retry the job from a schema that owns the IMPORT_FULL_DATABASE
privilege.
ORA-39123: Data Pump transportable tablespace job aborted string
Cause: A DBMS_PLUGTS procedure failed and the Data Pump operation could
not continue so it was aborted. The DBMS_PLUGTS failure listed describes the
original error.
Action: Look at the DBMS_PLUGTS error to determine actual cause.
ORA-39124: dump file name "string" contains an invalid substitution variable
Cause: The substitution variable '%' must be followed by '%','u', or 'U'.
Action: Correct the substitution variable in the dump file name and re-enter the
command.
ORA-39125: Worker unexpected fatal error in string while calling string [string]
ORA-38029 to ORA-39965 21-55
Cause: An unhandled exception was detected internally within the worker
process for the Data Pump job while calling the specified external routine. This is
an internal error. Additional information may be supplied.
Action: If problem persists, contact Oracle Customer Support.
ORA-39126: Worker unexpected fatal error in string [string] string
Cause: An unhandled exception was detected internally within the worker
process for the Data Pump job. This is an internal error. Additional information
may be supplied.
Action: If problem persists, contact Oracle Customer Support.
ORA-39127: unexpected error from call to string string
Cause: The exception was raised by the function invocation, a procedural action
extension of export.
Action: Record the accompanying messages and report this as a Data Pump
internal error to customer support.
ORA-39128: unexpected DbmsJava error number from statement string
Cause: The error was returned from a call to a DbmsJava procedure.
Action: Record the accompanying messages and report this as a Data Pump
internal error to customer support.
ORA-39129: Object type string not imported. Name conflicts with the master table
Cause: The table being imported from the remote instance has the same name as
the master table running this Data Pump job.
Action: Rerun the Data Pump job with a nonconflicting name.
ORA-39130: Object type string not imported. Base object name conflicts with the
master table
Cause: The object being imported from the remote instance is dependent on an
object that has the same name as the master table running this Data Pump job.
Action: Rerun the Data Pump job with a nonconflicting name.
ORA-39132: object type "string"."string" already exists with different hashcode
Cause: An object type could not be created because there was already a type with
the same name but a different hashcode on the target system. Tables in the
transportable tablespace set that use this object type cannot be read.
Action: Drop the object type from the target system and retry the operation.
ORA-39133: object type "string"."string" already exists with different typeid
Cause: An object type in a transportable tablespace set already exists on the target
system, but with a different typeid. The typeid could not be changed because the
type is used by an existing table. Tables in the transportable tablespace set that use
this object type cannot be read.
Action: Drop the object type from the target system and retry the operation.
ORA-39134: Cannot include "string" tablespace as a Transportable Tablespace
Cause: The user attempt to specify the SYSAUX or SYSTEM tablespace as a
member of the transportable tablespace list in the current job. These tablespaces
may not be transported between databases.
Action: Specify different tablespaces to be transported.
21-56 Oracle Database Error Messages
ORA-39135: File "string" is already a member of this dump set
Cause: An attempt was made to add a new file to an export job but a file with the
same name already exists in the dump set for the job.
Action: Reenter the new file information using a different file name.
ORA-39136: cannot specify an SCN on a transportable job
Cause: A target SCN was specified for a table in a transportable job by the streams
or logical standy components which was not the defaulted SCN for the table.
Action: This is an internal error. Please report it to Oracle support.
ORA-39137: cannot specify a TABLE_EXISTS_ACTION of string for a job with no
metadata
Cause: A job was defined with the TABLE_EXISTS_ACTION parameter set to
REPLACE or SKIP, but without metadata. Without metadata, data could not be
loaded for the requested table actions.
Action: Change the setting of the TABLE_EXISTS_ACTION parameter to
APPEND or TRUNCATE or supply Metadata with the data.
ORA-39138: Insufficient privileges to load data not in your schema
Cause: An unprivileged user attempted to load data into a different schema.
Action: Use a privileged account if you must load data not in your schema
ORA-39139: Data Pump does not support XMLType objects in version string. string
will be skipped.
Cause: Object had an XMLType column using either an object relational or binary
storage format, which is unsupported by Data Pump in the target version.
Action: Use the original export and import utilities to move this object.
ORA-39140: dump file "string" belongs to job string
Cause: When a dump file set consists of multiple files, all files in the set must be
specified for an import operation, and all files must have been produced by the
same export job. One of the files provided does not belong to the original dump
file set. For instance, it was created by a different export job than the other files.
Action: Remove the dump file indicated in the message and retry the import
operation providing only the complete set of dump files created by a specific
export job.
ORA-39141: dump file "string" is a duplicate of dump file "string"
Cause: When a dump file set consists of multiple files, all files in the set must be
specified for an import operation. One of the files provided to import was found to
be a duplicate of another dump file in the set. This can occur if the files in the
dump set were copied or renamed using operating system utilities and the same
dump file was inadvertently copied more than once with different destination
names.
Action: Remove the dump file indicated in the message and retry the import
operation providing only the complete set of dump files created by a specific
export job.
ORA-39142: incompatible version number string in dump file "string"
Cause: A dump file was specified for an import operation whose version number
is incompatible with the dump file version of the Data Pump product currently
running on the system. Usually this message indicates that the dump file was
produced by a newer version of the Data Pump export utility.
ORA-38029 to ORA-39965 21-57
Action: Import this dump file using the Data Pump import utility with the same
version as the export which created the file.
ORA-39143: dump file "string" may be an original export dump file
Cause: A dump file was specified for an import operation which appears to have
been created using the original export utility. These dump files cannot be
processed by the Data Pump import utility.
Action: Try using the original import utility to process this dump file.
ORA-39144: file name parameter must be specified and non-null
Cause: No file name was provided in an DBMS_DATAPUMP.ADD_FILE API call.
Action: Correct the file name parameter and reissue the API request.
ORA-39145: directory object parameter must be specified and non-null
Cause: No directory object was provided in either an DBMS_DATAPUMP.ADD_
FILE API call or to the directory parameter used by the Data Pump command line
clients.
Action: Correct the directory object parameter and retry the operation.
ORA-39146: schema "string" does not exist
Cause: The specified schema was referenced as the source of a REMAP_SCHEMA
parameter, but did not exist in the dump file (for file-based import) or in the
source database (for network import).
Action: Specify the correct name of the schema to be remapped.
ORA-39147: cannot migrate Data Pump queue table ownership to this instance
Cause: There are active Data Pump jobs running on another instance in a RAC.
All concurrent, active Data Pump jobs must be run on the same instance.
Action: Start this job on the same instance where other active Data Pump jobs are
running, or wait until they finish.
ORA-39148: unable to import data into pre-existing queue table string. Table_
exists_action of string being ignored for this table
Cause: A Data Pump import detected that a queue table that was to be imported
already exists. Importing data into pre-existing queue tables is not supported.
Action: If the data from the dump file is desired, then drop the queue table and
perform the import again, or use the import parameter table_exists_
action=replace.
ORA-39149: cannot link privileged user to non-privileged user
Cause: A Data Pump job initiated be a user with EXPORT_FULL_
DATABASE/IMPORT_FULL_DATABASE roles specified a network link that did
not correspond to a user with equivalent roles on the remote database.
Action: Specify a network link that maps users to identically privileged users in
the remote database.
ORA-39150: bad flashback time
Cause: A flashback time was specified for the Data Pump job which either could
not be parsed or else could not be translated into a system change number (SCN).
This typically occurs when specifying a time far in the past.
Action: Specify an explicit SCN for the desired flashback rather than a time.
ORA-39154: Objects from foreign schemas have been removed from import
21-58 Oracle Database Error Messages
Cause: An non-privileged user attempted to import objects into a schema other
than their own.
Action: Either perform the import from a privileged schema or else remap all
schemas that were exported into the username running the import.
ORA-39155: error expanding dump file name "string"
Cause: Export was unable to expand the directory object and dump file name into
a full file name. Subsequent messages will detail the problems.
Action: Fix the problems outlined in the secondary messages.
ORA-39156: error parsing dump file name "string"
Cause: Export was unable to parse the dump file name. Subsequent messages will
detail the problems.
Action: Fix the problems outlined in the secondary messages.
ORA-39157: error appending extension to file "string"
Cause: Export or Import was unable to append the default extension to create the
file name. The given file name could be too long or contain illegal characters.
Subsequent messages will detail the problems.
Action: Fix the problems outlined in the secondary messages.
ORA-39159: cannot call this function from a non-Data Pump process
Cause: Called a Data Pump process model function from a process which is not a
Data Pump process.
Action: Refer to any other error messages for additional information. If this error
occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If
the error occurs again, contact Oracle Customer Support and report the error.
ORA-39160: error on whats my name call
Cause: Attempt to get the Data Pump process name failed.
Action: Refer to any following error messages for additional information. If this
error occurs from a Data Pump client (e.g. expdp or impdp), try the operation
again. If the error occurs again, contact Oracle Customer Support and report the
error.
ORA-39161: Full database jobs require privileges
Cause: Either an attempt to perform a full database export without the EXP_
FULL_DATABASE role or an attempt to perform a full database import over a
network link without the IMP_FULL_DATABASE role.
Action: Retry the operation in a schema that has the required roles.
ORA-39162: Transportable tablespace job require privileges
Cause: User attempted to perform a transportable tablespace job without being
having the proper EXP_FULL_DATABASE or IMP_FULL_DATABASE role.
Action: Retry the operation in a schema that has the required roles.
ORA-39163: A sample size of string is invalid.
Cause: An attempt was made to do data sampling on a table with a value outside
of the range of 0 - 100.
Action: Retry the filtering using a sampling number greater than 0 and less than
100.
ORA-38029 to ORA-39965 21-59
ORA-39164: Partition string was not found.
Cause: If exporting or importing over the network, the user specified a partition
name that was not found in the source database. For importing from files, the user
specified a partition name not found in the dump file set.
Action: Retry the operation using the correct partition name.
ORA-39165: Schema string was not found.
Cause: If exporting or importing over the network, either the user specified a
schema name that was not found in the source database or else the user lacked the
proper EXP_FULL_DATABASE or IMP_FULL_DATABASE role that would allow
them to access another schema. For importing from files, the user specified a
schema name not found in the dump file set.
Action: Retry the operation using the correct schema name.
ORA-39166: Object string was not found or could not be exported or imported.
Cause: If exporting to files or importing over the network, one of the following
occurred:
- The object specified did not exist in the source database.
- The user lacked the proper EXP_FULL_DATABASE or IMP_FULL_DATABASE
role that would allow access to the object.
- The VIEWS_AS_TABLES object contained a type that is not supported with the
VIEWS_AS_TABLES parameter. If importing from files, the user specified an
object name that was not found in the dump file set.
Action: Retry the operation using the correct object name, correct set of privileges,
or a view that has only supported types.
ORA-39168: Object path string was not found.
Cause: If exporting or importing over the network, the user specified an object
type path name that was not found in the source database. For importing from
files, the user specified an object type path name not found in the dump file set.
Action: Retry the operation using the correct object type path name.
ORA-39169: Local version of string cannot work with remote version of string.
Cause: A Data Pump job specified a network link, but the version on the remote
database cannot interoperate with the version on the local database.
Action: Do not specify network links between instance running different versions
of the database.
ORA-39170: Schema expression string does not correspond to any schemas.
Cause: A schema expression or schema list was supplied for a Data Pump job that
did not identify any schemas in the source database.
Action: Correct the schema specifications and retry the job.
ORA-39171: Job is experiencing a resumable wait. string
Cause: The Data Pump job is stalled with one or more of its sessions having a
resumable wait. Resumable waits are typically caused by a non-expandable
tablespace running out of space. The follow-on message describes the nature of the
wait.
Action: Correct the condition causing the wait. This will typically involve adding
datafiles to the tablespace that is full.
21-60 Oracle Database Error Messages
ORA-39172: Cannot remap transportable tablespace names with compatibility of
string.
Cause: The user attempted to remap a tablespace name in a transportable
tablespace job when the compatibility level was set below 10.1.
Action: Reset the compatibility level of the database to a more recent version.
ORA-39173: Encrypted data has been stored unencrypted in dump file set.
Cause: No encryption password was specified for an export job that involved
data that was encrypted in the database.
Action: No specific user action is required. This is only a warning that secure data
may be readable from within the dump file set.
ORA-39174: Encryption password must be supplied.
Cause: No encryption password was supplied to import a dump file set that was
created using an encryption password.
Action: Specify the encryption password for the dump file set.
ORA-39175: Encryption password is not needed.
Cause: An encryption password was supplied to import a dump file set that was
not created using an encryption password.
Action: No user action is required. This is merely a warning message.
ORA-39176: Encryption password is incorrect.
Cause: The wrong encryption password was supplied to import a dump file set.
Action: Resubmit the job using the correct encryption password for the dump file
set.
ORA-39177: invalid compression value string
Cause: An invalid value was specified for compression.
Action: Correct the value and recreate the job.
ORA-39178: cannot perform estimate on metadata only jobs
Cause: An estimate was requested for a job by specifying the ESTIMATE or
ESTIMATE_ONLY parameter. However, the job was also defined to have no data.
These specifications conflict with each other.
Action: Remove one of the conflicting specifications for the job.
ORA-39179: unable to load table "string"."string" because of OID transform
Cause: The OID transform for the job was set to false and the identified table
contained either VARRAYs with non-final types or unscoped REF columns. Both
of these column types have embedded OIDs so they cannot be imported correctly
when OIDs are not preserved.
Action: You must manually move the data with the specified tables when OIDs
are not preserved.
ORA-39180: unable to encrypt ENCRYPTION_PASSWORD
Cause: The specified encryption password was unable to be encrypted for
placement within the master table or decrypted when it was to be restored from
the master table. Subsequent messages will describe the actual error that caused
the encryption to fail.
Action: Fix the problems referenced by the subsequent messages. The most
common reason for the encryption to fail is the lack of a security wallet.
ORA-38029 to ORA-39965 21-61
ORA-39181: Only partial table data may be exported due to fine grain access control
on string
Cause: An unprivileged user has tried to export a table that has fine grain access
control. The table owner is subjected to access control and may not be able to
export all rows in the table. Only the rows that can be seen by that user will be
exported. In order to preserve integrity of the table, the user importing the table
should have enough privilege to recreate the table with the security policies at
import time.
Action: It is strongly recommended that the database administrator handle
exporting of this table.
ORA-39182: internal error string occurred during compression phase string
Cause: An unexpected error occurred while compressing data buffers.
Action: Contact Oracle Customer Support.
ORA-39183: internal error string ocurred during decompression phase string
Cause: An unexpected error occurred while decompressing data buffers.
Action: Contact Oracle Customer Support.
ORA-39184: Transportable Data Pump jobs cannot exclude PLUGTS objects
Cause: A Transportable Data Pump job requires all PLUGTS% objects, but the
user-supplied exclude filters were excluding these objects.
Action: Reenter command without excluding PLUGTS% objects.
ORA-39185: The transportable tablespace failure list is
Cause: Some of the tablespaces specified for this job could not be exported.
Action: See specific errors for each tablespace, correct the problem, and try again.
ORA-39186: No tablespaces in the specified list exist.
Cause: The tablespaces specified on the EXPORT command did not exist.
Action: Check the list of tablespaces and reenter command with correct set of
tablespaces.
ORA-39187: The transportable set is not self-contained, violation list is
Cause: The tablespaces specified for this job did not satisfy the closure checking.
The list of violations specified each closure violation.
Action: See specific errors for violation and correct the problem or change the
tablespaces on the command line and try again.
ORA-39188: unable to encrypt dump file set
Cause: Data Pump could not create an encrypted dump file set. This message will
be accompanied by other messages that give more details about why the
encrypted dump file set could not be created. The most common reason for this
message is that you are trying to create a dump file set that can be transparently
decrypted, and the database external security device is not open.
Action: If the external security device is not open, then open it. If the external
security device is not configured, then the only type of encrypted dump file set
that you can create is a password-based dump file set.
ORA-39189: unable to decrypt dump file set
21-62 Oracle Database Error Messages
Cause: The dump file set could not be decrypted. The reason could be either that
an invalid password was entered, or that, when using transparent decryption, the
database external security device was not open.
Action: If password-based import was enabled for this dump file set, then supply
the correct password. If transparent import was enabled for this dump file set,
then ensure that the database external security device is open.
ORA-39190: internal error occurred during encryption phase string
Cause: An unexpected error occurred while encrypting data buffers.
Action: See the secondary error for more information and contact Oracle
Customer Support.
ORA-39191: internal error ocurred during decryption phase string
Cause: An unexpected error occurred while decrypting data buffers.
Action: See the secondary error for more information and contact Oracle
Customer Support.
ORA-39192: table mode jobs with transportable=always and partition filters only
allow objects from one table
Cause: Multiple tables are not supported when specifying partitions while using
transportable table mode.
Action: Retry the job specifying only one table.
ORA-39193: Table mode jobs do not allow the schema to be wild carded.
Cause: The table filter included a schema expression with the % wild card.
Action: Retry the job specifying actual schemas.
ORA-39194: Table mode jobs require the tables to be comma separated.
Cause: The string describing tables in a table mode job was not comma separated.
Action: Retry the job specifying the tables separated by commas.
ORA-39195: At least one schema in the TABLE_FILTER does not exist.
Cause: The TABLE_FITER specified contains a schema that does not exist.
Action: Retry the job specifying only schemas that exist.
ORA-39200: Link name "string" is invalid.
Cause: The name of the network link supplied for a Data Pump job was not
usable. Secondary messages identify the problem.
Action: Rerun the job using a valid network link.
ORA-39201: Dump files are not supported for estimate only jobs.
Cause: An attempt was made to add a dumpfile to an Export job that only
requested file estimates.
Action: Do not specify a dumpfile for jobs that do not require dumpfiles.
ORA-39202: Data cannot be filtered or selected in string jobs.
Cause: A data filter was supplied for the specified type of job, but is not
supported in the specified job type. From the command line, data filters can be
specified by the CONTENT, TABLES (partition specifications), SAMPLE and
QUERY parameters.
Action: Do not restrict data handling on jobs that cannot support data filtering.
ORA-38029 to ORA-39965 21-63
ORA-39203: Partition selection is not supported over a network link.
Cause: Specific partitions were selected for a job operating over a network link.
Action: Remove the partition specifications and rerun the job.
ORA-39204: No subsetting of tablespaces is allowed for transportable import.
Cause: A tablespace filter was applied to a transportable import job that was not
performed over a network link. In this case, the tablespace may not be changed
from its specification at export time.
Action: Rerun the job without specifying a tablespace filter.
ORA-39205: Transforms are not supported in transportable jobs.
Cause: A metadata transformation such as STORAGE or SEGMENT_
ATTRIBUTES has been specified for a transportable Data Pump job.
Action: Rerun the job without specifying a transform.
ORA-39206: A parallel degree of string is invalid.
Cause: A bad numeric was supplied for specifying the parallelism to be used
within a Data Pump job. The degree of parallelism must be an integer great than 0.
Action: The the degree specifying and retry the parallelism setting.
ORA-39207: Value string is invalid for parameter string.
Cause: A parameter for a Data Pump job was set with a NULL or invalid value.
Action: Refer to the documentation to identify the legal values for each parameter.
Retry the operation with a valid value.
ORA-39208: Parameter string is invalid for string jobs.
Cause: The a parameter has been specified that is not supported for the specified
type of Data Pump.
Action: Remove the parameter specification and retry the operation.
ORA-39209: Parameter string requires privileges.
Cause: Use of the specified privileges requires the user to have the IMP_FULL_
DATABASE role for import jobs or the EXP_FULL_DATABASE role for export
jobs.
Action: Remove the parameter specification and retry the operation.
ORA-39210: A PCTSPACE adjustment of string is invalid.
Cause: User specified a storage space transformation that was out of range.
Values for PCTSPACE must be greater than zero.
Action: Retry the operation with a valid PCTSPACE value.
ORA-39211: unable to retrieve dumpfile information as specified
Cause: User specified an invalid or inaccessible file with the specified filename
and directory object.
Action: Retry the operation with a valid directory object and filename.
ORA-39212: installation error: XSL stylesheets not loaded correctly
Cause: The XSL stylesheets used by the Data Pump Metadata API were not
loaded correctly into the Oracle dictionary table "sys.metastylesheet." Either the
stylesheets were not loaded at all, or they were not converted to the database
character set.
21-64 Oracle Database Error Messages
Action: Connect AS SYSDBA and execute dbms_metadata_util.load_stylesheets
to reload the stylesheets.
ORA-39213: Metadata processing is not available
Cause: The Data Pump could not use the Metadata API. Typically, this is caused
by the XSL stylesheets not being set up properly.
Action: Connect AS SYSDBA and execute dbms_metadata_util.load_stylesheets
to reload the stylesheets.
ORA-39214: Data Pump does not support external tables with encrypted columns.
string will not be exported
Cause: The object is an external table with encrypted columns and this is
unsupported with Data Pump.
Action: External table must be manually recreated on the target system.
ORA-39216: object type "string"."string" hashcode mismatch
Cause: An object type in a transportable tablespace set could not be used because
there was a type with the same name but a different hashcode (and type
definition) on the target system. Tables in the transportable tablespace set that use
this object type cannot be created.
Action: Drop the object type and dependent objects from the target system if
possible and retry the operation.
ORA-39217: object type "string"."string" typeid mismatch
Cause: An object type in a transportable tablespace set already exists on the target
system, but with a different typeid. The typeid could not be changed because the
type or a dependent type is used by an existing table. Tables in the transportable
tablespace set that use this object be created.
Action: Drop the object type and dependent objects from the target system if
possible and retry the operation.
ORA-39218: type check on object type "string"."string" failed
Cause: The type check on a type failed. Therefore, the table create for the table
which uses the type also fails.
Action: Refer to any following error messages for additional information. Correct
the error, if possible, and try the action again.
ORA-39219: directory object name is too long
Cause: The directory object name provided to the Data Pump Job was invalid
because its length was greater than 30 characters.
Action: Retry the operation with a valid directory object name.
ORA-39220: file name is too long
Cause: The file name provided to the Data Pump Job was invalid because its
length was greater than 4000 characters.
Action: Retry the operation with a valid file name.
ORA-39221: Specifying data filters is invalid when dumpfiles do not contain table
data.
Cause: A data filter was supplied for an import job, but the dumpfile does not
contain any table data. The export command created a dumpfile with metadata
only. No table data was included. From the command line, data filters can be
specified by the CONTENT, SAMPLE and QUERY parameters.
ORA-38029 to ORA-39965 21-65
Action: Do not restrict data handling on jobs that cannot support data filtering.
ORA-39222: Unable to create global temporary master table string
Cause: Data Pump tried to create a global temporary master table but could not.
The errors that follow describe why the table could not be created.
Action: Examine and fix the problems described in the additional errors.
ORA-39223: Internal Data Pump error. Master table information for version string
not found.
Cause: An unexpected error occurred while processing the job. The data in an
internal table could not be found.
Action: Contact Oracle Support Services.
ORA-39224: string row(s) were rejected with the following error: string
Cause: These rows were not loaded due to constraint or index violations.
Action: Retry the operation when row data is fixed.
ORA-39228: Unable to construct a unique departitioned object name for string
string.string:string when defaulted.
Cause: All (sub)partitions in the job were to be created as individual objects and
the renaming was defaulted. The job will attempt to create unique object names,
but the name creation algorithm was unable to find a unique object name for the
specified (sub)partition.
Action: Specify a rename_table transform to use or delete some of the existing
objects causing the name conflicts.
ORA-39230: Service name string is not available
Cause: The specified resource service name for the Data Pump job was not
available.
Action: Pick a service name that the user is authorized to use.
ORA-39231: invalid data remap name: string
Cause: The specified type of data remapping was not supported.
Action: Only COLUMN_FUNCTION data remaps are supported. Retry the
operation using a supported data remap name.
ORA-39232: invalid remap function: string
Cause: The specified package function for performing data remapping was not
found.
Action: Either create the specified package function or else grant the user access
to the function.
ORA-39233: invalid remap column name: string
Cause: The column name specified for the data remapping does not exist in the
specified table.
Action: Specify a scalar column name within the table to be remapped.
ORA-39234: Data cannot be remapped under the direct path access method.
Cause: Data remapping was requested on a job that requires the direct path access
method. Data remapping can only be performed using the external table access
method.
Action: Retry the job without specifying any access method.
21-66 Oracle Database Error Messages
ORA-39235: data remap string has already been specified
Cause: A data remap has already been specified for the indicated column. Only
one data remap may be defined for a column.
Action: Remove one of the data remap specifications for the job.
ORA-39237: Failed to load XML document string. Compare process aborted.
Cause: An error occurred while performing XML difference parse.
Action: Resubmit XML compare request with valid document.
ORA-39238: XML node attribute differences are not supported.
Cause: MDAPI XML difference parsing did not support node attributes.
Action: Resubmit XML compare request with valid document.
ORA-39239: No differences found.
Cause: XML documents compared were identical.
Action: No action required.
ORA-39240: Error while processing difference document.
Cause: Error occurred in the MDAPI difference writer.
Action: Refer to any following error messages for additional information. Correct
the error, if possible, and try the action again.
ORA-39242: Unable to export/import string due to table attributes.
Cause: See the Data Pump documentation for an explanation of what table
attributes prevent an export or import from succeeding.
Action: Resolve conflicting table attributes.
ORA-39243: Import job requires 'TRANSPORT_DATAFILES' parameter.
Cause: The export job used 'TRANSPORTABLE=ALWAYS' and the import job
requires TRANSPORT_DATAFILES to be specified.
Action: Specify the transport datafiles associated with this job.
ORA-39245: import job requires export dump file "string"
Cause: A Data Pump IMPORT or SQL_FILE operation was being performed but
not all of the files from the Data Pump export dump file set were included.
Action: Check the export log file and make sure all of the files that were exported
are included in the current job. The import log file also lists the export names of
the missing files.
ORA-39246: cannot locate master table within provided dump files
Cause: A Data Pump IMPORT or SQL_FILE operation was being performed but
not all of the files from the Data Pump export dump file set were included. In
particular, the dump file containing the export job's master table was not provided.
Action: Check the export log file and make sure all of the files that were exported
are included in the current job.
ORA-39251: Importing a SecureFile LOB with metadata into a scalar, column string,
is not allowed.
Cause: An import of a SecureFile LOB with metadata into a scalar column was
attempted.
Action: Change the scalar column to a SecureFile LOB.
ORA-38029 to ORA-39965 21-67
ORA-39252: Importing a SecureFile LOB with metadata or archived SecureFile LOB
into a BasicFile LOB is not allowed
Cause: An attempt was made to import a SecureFile LOB that contained metadata
or was archived at the time of export into a BasicFile LOB.
Action: Perform the import into a different table, perform DBMS_
LOB.ARCHIVE_GET on any archived SecureFile LOBs, and then use INSERT AS
SELECT to migrate the SecureFile LOB data to the BasicFile LOB.
ORA-39253: Specified tables do not exist.
Cause: The tables specified for this export job did not exist.
Action: Check the specified table list and make sure the tables listed exist.
ORA-39254: direct path load not possible into preexisting table with column that
has a default value and is not being loaded; table string, column string
Cause: The direct path access method could not be used to load into a pre-existing
table that has a column with a default value and that column is not being loaded
into.
Action: Remove the ACCESS_METHOD parameter from the import command
line.
ORA-39255: Failed to fetch PLUGTS_BLKs.
Cause: The Data Pump expected a PLUGTS_BLK object to be exported but none
were.
Action: Contact Oracle Support Services.
ORA-39256: Transportable tablespace Data Pump jobs from read-only databases not
supported.
Cause: The remote database was read-only and Data Pump export jobs using
transportable tablespace over a network link require the remote database to be
read/write.
Action: Use Data Pump without transportable tablespace or make the remote
database read/write.
ORA-39258: Cannot rename cluster.
Cause: DBMS_METADATA_DIFF was comparing two clusters with different
names. There is no SQL ALTER statement to rename a cluster.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39259: Cannot add column to cluster.
Cause: DBMS_METADATA_DIFF was comparing two clusters with different
column lists. There is no SQL ALTER statement to add a column to a cluster.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39260: Cannot delete column from cluster.
Cause: DBMS_METADATA_DIFF was comparing two clusters with different
column lists. There is no SQL ALTER statement to delete a column from a cluster.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39261: Cannot modify column in cluster.
Cause: DBMS_METADATA_DIFF was comparing two clusters with different
column lists. There is no SQL ALTER statement to modify a column in a cluster.
Action: The difference cannot be eliminated with an SQL ALTER statement.
21-68 Oracle Database Error Messages
ORA-39262: Cannot alter size for hash cluster.
Cause: DBMS_METADATA_DIFF was comparing two hash clusters with different
sizes. There is no SQL ALTER statement to modify the size of a hash cluster.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39263: Cannot alter PARALLEL INSTANCES.
Cause: DBMS_METADATA_DIFF was comparing two objects, both with
PARALLEL but with different INSTANCES values. There is no SQL ALTER
statement to modify PARALLEL INSTANCES.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39264: Cannot alter type of table: string
Cause: DBMS_METADATA_DIFF was comparing tables of different types:
relational table, object table or XMLType table. There is no SQL ALTER statement
to change a table's type.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39265: Cannot alter object_type of object table: string
Cause: DBMS_METADATA_DIFF was comparing object tables based on different
object types. There is no SQL ALTER statement to change an object table's object
type.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39266: Cannot alter unpartitioned table to partitioned.
Cause: DBMS_METADATA_DIFF was comparing two tables, one unpartitioned,
the other partitioned. There is no SQL ALTER statement to partition an
unpartitioned table.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39267: Cannot remove default from table column.
Cause: DBMS_METADATA_DIFF was comparing two table columns, one with a
default value, one without. There is no SQL ALTER syntax to remove a column
default.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39268: Cannot alter a real column to make it virtual or vice versa.
Cause: DBMS_METADATA_DIFF was comparing two table columns, one virtual,
one real. There is no SQL ALTER statement to make a virtual column real or vice
versa.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39269: Cannot alter a column of type LONG to anything other than LOB.
Cause: DBMS_METADATA_DIFF was comparing two table columns, the first of
type LONG, the second of a data type other than LOB. There is no SQL ALTER
statement to modify a long data type to anything other than a CLOB or NCLOB.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39270: Cannot alter a LOB column to another data type.
Cause: DBMS_METADATA_DIFF was comparing two table columns, the first of
type CLOB, NCLOB or BLOB, the second of some other data type. There is no SQL
ALTER statement to change the data type of a LOB column.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-38029 to ORA-39965 21-69
ORA-39271: Cannot alter substitutability of column: string
Cause: DBMS_METADATA_DIFF was comparing two table columns. This error
may occur because the first column is substitutable and the second column is not,
or because the first column is OF TYPE and the second column is substitutable.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39272: Cannot alter organization of nested table column: string
Cause: DBMS_METADATA_DIFF was comparing two nested table columns. One
was a heap table, the other an index-organized table. There is no SQL ALTER
statement to change the organization of a nested table.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39273: Cannot alter storage type of XMLType column: string
Cause: DBMS_METADATA_DIFF was comparing two XMLType columns with
different storage types (CLOB, BINARY, OBJECT RELATIONAL). There is no SQL
ALTER statement to change the storage type of an XMLType column.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39274: Cannot alter physical organization of table.
Cause: DBMS_METADATA_DIFF was comparing two tables with different
physical organizations (heap, index organized, external, or cluster). There is no
SQL ALTER statement to change the physical organization of a table.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39275: Cannot alter INITIAL storage option.
Cause: DBMS_METADATA_DIFF was comparing two tables with different
FREELIST GROUPS storage options. There is no SQL ALTER statement to change
a table's INITIAL storage option.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39276: Cannot alter MINEXTENTS storage option.
Cause: DBMS_METADATA_DIFF was comparing two tables with different
MINEXTENTS storage options. There is no SQL ALTER statement to change a
table's MINEXTENTS storage option.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39277: Cannot alter FREELIST GROUPS storage option.
Cause: DBMS_METADATA_DIFF was comparing two tables with different
FREELIST GROUPS storage options. There is no SQL ALTER statement to change
a table's FREELIST GROUPS storage option.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39278: Cannot alter table with segments to segment creation deferred.
Cause: DBMS_METADATA_DIFF was comparing two tables, the first with
allocated segments, the second with deferred segments. There is no SQL ALTER
statement to change a table which already has segments to segment creation
deferred.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39279: Cannot alter tablespace of overflow segment.
21-70 Oracle Database Error Messages
Cause: DBMS_METADATA_DIFF was comparing two index organized tables
whose overflow segments have different tablespaces. There is no SQL ALTER
statement to change an overflow segment's tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39280: Cannot drop overflow segment.
Cause: DBMS_METADATA_DIFF was comparing two index organized tables, the
first with an overflow segment, the second without. There is no SQL ALTER
statement to drop an overflow segment.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39281: Cannot alter COMPRESS in index-organized materialized view.
Cause: DBMS_METADATA_DIFF was comparing two index organized
materialized views with different key compression values. There is no SQL ALTER
statement to modify the key compression of an index organized materialized view.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39282: Cannot alter default tablespace of partitions in partitioned table.
Cause: DBMS_METADATA_DIFF was comparing two partitioned tables with
different default tablespaces. There is no SQL ALTER statement to change the
default tablespace of a partitioned table.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39283: Cannot drop, split or merge hash partition: string
Cause: DBMS_METADATA_DIFF was comparing two tables or indexes
partitioned or subpartitioned by hash, and a (sub)partition in the first object was
not present in the second object. Partition maintenance operations such as drop,
split or merge can only be performed on list or range (sub)partitioned objects.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39284: Cannot alter the list values of a list subpartition: string
Cause: DBMS_METADATA_DIFF was comparing two tables subpartitioned by
list, one of which has a subpartition with the same name but a different values list
as a subpartition in the other. There is no SQL ALTER statement to change the list
values of a list subpartition.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39285: Cannot alter index key compression.
Cause: DBMS_METADATA_DIFF was comparing two indexes with different
values of key compression. There is no SQL ALTER statement to change index key
compression.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39286: Cannot convert between types of index.
Cause: DBMS_METADATA_DIFF was comparing two indexes of different types,
for example, a table index, a domain index, a cluster index, a bitmap index or a
bitmap join index There is no SQL ALTER statement to change the type of an
index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39287: Cannot alter index column list.
Cause: DBMS_METADATA_DIFF was comparing two indexes with different
column lists. There is no SQL ALTER statement to change the columns of an index.
ORA-38029 to ORA-39965 21-71
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39288: Cannot alter index base table.
Cause: DBMS_METADATA_DIFF was comparing two table indexes defined on
different tables. There is no SQL ALTER statement to change the base table of an
index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39289: Cannot add or drop local index partition or subpartition: string
Cause: DBMS_METADATA_DIFF was comparing two locally partitioned indexes
with different partitions or subpartitions. There is no SQL ALTER statement to add
or drop a partition or subpartition of a locally partitioned index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39290: Cannot drop a partition of a globally partitioned index.
Cause: DBMS_METADATA_DIFF was comparing two globally partitioned
indexes and a partition in the first index does not exist in the second index. There
is no SQL ALTER statement to drop a partition of a globally partitioned index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39291: Cannot alter index storage option: string
Cause: DBMS_METADATA_DIFF was comparing two indexes with different
values for the specified storage option. There is no SQL ALTER statement to
change this storage option.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39292: Cannot alter join table of bitmap join index.
Cause: DBMS_METADATA_DIFF was comparing two bitmap join indexes with
different join tables. There is no SQL ALTER statement to alter the join tables of a
bitmap join index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39293: Cannot alter join condition of bitmap join index.
Cause: DBMS_METADATA_DIFF was comparing two bitmap join indexes with
different join conditions. There is no SQL ALTER statement to alter the join
condition of a bitmap join index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39294: Cannot alter indextype of domain index.
Cause: DBMS_METADATA_DIFF was comparing two bitmap domain indexes
with different indextypes. There is no SQL ALTER statement to alter the indextype
of a domain index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39295: Cannot alter index base cluster.
Cause: DBMS_METADATA_DIFF was comparing two cluster indexes defined on
different clusters. There is no SQL ALTER statement to change the base cluster of a
cluster index.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39296: Cannot alter index partitioning type or partitioning columns.
Cause: DBMS_METADATA_DIFF was comparing two indexes with incompatible
partitioning: (1) one is partitioned and one is not (2) both are partitioned but in
21-72 Oracle Database Error Messages
different ways (locally vs. globally, hash vs. range) (3) both are partitioned but on
different columns. There is no SQL ALTER statement to change the way an index
is partitioned.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39297: Cannot alter materialized view attribute: string
Cause: DBMS_METADATA_DIFF was comparing two materialized views with
incompatible attributes. There is no SQL ALTER statement to change this attribute
of a materialized view.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39298: Cannot alter materialized view partitioning type or partitioning
columns.
Cause: DBMS_METADATA_DIFF was comparing two materialized views with
incompatible partitioning: (1) one is partitioned and one is not (2) both are
partitioned but in different ways (locally vs. globally, hash vs. range) (3) both are
partitioned but on different columns. There is no SQL ALTER statement to change
the way a materialized view is partitioned.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39299: Cannot alter materialized view physical organization.
Cause: DBMS_METADATA_DIFF was comparing two materialized views with
different physical organizations: heap, index organized, etc. There is no SQL
ALTER statement to change the index organization of a materialized view.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39300: Cannot alter materialized view log partitioning type or partitioning
columns.
Cause: DBMS_METADATA_DIFF was comparing two materialized view logs
with incompatible partitioning: (1) one is partitioned and one is not (2) both are
partitioned but in different ways (locally vs. globally, hash vs. range) (3) both are
partitioned but on different columns. There is no SQL ALTER statement to change
the way a materialized view log is partitioned.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39301: Cannot alter values recorded in materialized view log: string
Cause: DBMS_METADATA_DIFF was comparing two materialized view logs that
are recording different values, and the set of values in the first materialized view
log cannot be changed to that in the second materialized view log. The error
message identifies the specific problem.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39302: Cannot alter tablespace of materialized view log.
Cause: DBMS_METADATA_DIFF was comparing two materialized view logs
which have different tablespaces. There is no SQL ALTER statement to change the
tablespace of a materialized view log.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39303: Cannot alter attribute of queue: string
Cause: DBMS_METADATA_DIFF was comparing two advanced queues with
attribute differences that cannot be reconciled. The error message identifies the
specific problem.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-38029 to ORA-39965 21-73
ORA-39304: Cannot alter attribute of queue table: string
Cause: DBMS_METADATA_DIFF was comparing two AQ queue tabless with
attribute differences that cannot be reconciled. The error message identifies the
specific problem.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39305: Cannot alter attribute of sequence: string
Cause: DBMS_METADATA_DIFF was comparing two sequences with attribute
differences that cannot be reconciled. The error message identifies the specific
problem.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39306: Cannot alter attribute of trigger: string
Cause: DBMS_METADATA_DIFF was comparing two triggers with differences
that cannot be reconciled. The error message identifies the specific problem.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39307: Cannot alter attribute of type: string
Cause: DBMS_METADATA_DIFF was comparing two types with differences that
cannot be reconciled. The error message identifies the specific problem.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39308: Cannot alter attribute of view: string
Cause: DBMS_METADATA_DIFF was comparing two views with differences that
cannot be reconciled. The error message identifies the specific problem.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39309: Cannot alter tablespace between bigfile and smallfile.
Cause: DBMS_METADATA_DIFF was comparing two tablespaces, one bigfile,
one smallfile. There is no SQL ALTER statement to change a tablespace from
smallfile to bigfile or vice versa.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39310: Cannot alter tablespace type.
Cause: DBMS_METADATA_DIFF was comparing two tablespaces of different
types: permanent, temporary or undo. There is no SQL ALTER statement to
change the type of a tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39311: Cannot alter tablespace blocksize.
Cause: DBMS_METADATA_DIFF was comparing two tablespaces with different
blocksizes. There is no SQL ALTER statement to change the blocksize of a
tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39312: Cannot alter tablespace encryption.
Cause: DBMS_METADATA_DIFF was comparing two tablespaces, one
encrypted, one not. There is no SQL ALTER statement to change the encryption
property of a tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39313: Cannot alter tablespace flashback mode.
21-74 Oracle Database Error Messages
Cause: DBMS_METADATA_DIFF was comparing two tablespaces, one in
flashback mode, one not. There is no SQL ALTER statement to alter the flashback
mode of a tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39314: Cannot alter tablespace extent_management.
Cause: DBMS_METADATA_DIFF was comparing two tablespaces with different
extent management properties. There is no SQL ALTER statement to alter the
extent management properties of a tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39315: Cannot drop the first data file from a permanent or undo tablespace.
Cause: DBMS_METADATA_DIFF was comparing two permanent or undo
tablespaces. The first data file in the first tablespace is missing from the second
tablespace. There is no SQL ALTER statement to drop the first data file from a
permanent or undo tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39316: Cannot resize a data file in a smallfile tablespace.
Cause: DBMS_METADATA_DIFF was comparing two smallfile tablespaces. A
data file in the first tablespace is of a different size from the corresponding data file
in the second tablespace. There is no SQL ALTER statement to resize a data file in
a smallfile tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39317: Cannot change the segment space management of a tablespace.
Cause: DBMS_METADATA_DIFF was comparing two tablespaces with different
segment space management. There is no SQL ALTER statement to change the
segment space management of a tablespace.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39318: Cannot alter user name.
Cause: DBMS_METADATA_DIFF was comparing two users with different names.
There is no SQL ALTER statement to change the name of a user.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39319: Cannot undo password expiration.
Cause: DBMS_METADATA_DIFF was comparing two users and the first user had
an expired password. There is no SQL ALTER statement to undo the expiration of
a user password.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39320: Column names do not match between export and import databases.
Cause: The column names of the table being imported did not match the column
names of the preexisting table.
Action: Ensure the column names match between export and import database.
ORA-39321: Cannot alter functional index or virtual expression column: string
Cause: Altered column was referenced in a virtual column or functional index
expression. There is no SQL ALTER statement to change a column which is
referenced in one of these types of expressions.
Action: The difference cannot be eliminated with a SQL ALTER statement.
ORA-38029 to ORA-39965 21-75
ORA-39322: Cannot use transportable tablespace with TIMESTAMP WITH TIME
ZONE columns and different time zone version.
Cause: The source database was at a different time zone version than the target
database and there were tables in the dumpfile with TIMESTAMP WITH TIME
ZONE columns.
Action: Convert the target database to the same timezone version as the source
database or use Data Pump without transportable tablespace.
ORA-39323: cannot load data from external table dump file "string"
Cause: A dump file was specified for an import operation that had been created
with external tables using the ORACLE_DATAPUMP access driver. This type of
dump file cannot be processed using the Data Pump import utility.
Action: Access the data in this dump file with external tables using the ORACLE_
DATAPUMP access driver.
ORA-39324: cannot load data from Data Pump dump file "string"
Cause: A dump file was specified for a load operation that had been created using
the Data Pump. This type of dump file cannot be processed by external tables
using the ORACLE_DATAPUMP access driver.
Action: Access the data in this dump file using the Data Pump.
ORA-39325: TABLE_EXISTS_ACTION cannot be applied to string.
Cause: An object was already in existence that uses a name in common with this
table. The name collision could be the table name, a constraint, a LOB storage
table, or something else in the table definition.
Action: Drop the existing object before running Data Pump.
ORA-39326: cannot load data into table, string, due to an unusable index
Cause: An unusable index existed on the table. This index prevented data from
being loaded into the table associated with this index.
Action: Either drop the unusable index or make it valid before attempting the
import operation.
ORA-39327: Oracle Database Vault data is being stored unencrypted in dump file
set.
Cause: No encryption was specified for an export job that involved data from an
Oracle Database Vault realm.
Action: No specific user action is required. This is only a warning that secure data
may be readable from within the dump file set.
ORA-39328: encryption password is too long
Cause: The encryption password provided to the Data Pump job was invalid
because its length was greater than the maximum allowed. When using the
password to encrypt the dump file set, the maximum length is 1000 bytes. When
using the password to re-encrypt encrypted columns only, the maximum length is
30 bytes.
Action: Retry the operation with a valid encryption password.
ORA-39329: Tablespace string needs to be locally managed.
Cause: An attempt was made to run an Oracle Data Pump job with the
TRANSPORTABLE=ALWAYS parameter. Tablespaces that contain data for
EARLY_OPTIONS in an Oracle Data Pump job run with FULL=Y and
TRANSPORTABLE=ALWAYS parameter need to be locally managed.
21-76 Oracle Database Error Messages
Action: Run the Oracle Data Pump job without the TRANSPORTABLE parameter
set to ALWAYS.
ORA-39331: Wallet is not open on remote node.
Cause: The security module wallet was not open on the remote node.
Action: Open the wallet on the remote node.
ORA-39339: Table string was skipped due to transportable import and TSTZ issues
resulting from time zone version mismatch.
Cause: The source database is at a different time zone version than the target
database and this table contains TIMESTAMP WITH TIME ZONE data.
Action: Convert the target database to the same time zone version as the source
database or use Oracle Data Pump with conventional data movement to export
then import this table.
ORA-39340: unsupported object, string will be skipped.
Cause: Oracle Data Pump encountered an object type that it currently does not
support.
Action: Manually move the object to the target database.
ORA-39341: Cannot convert an existing column into an identity column.
Cause: An attempt was made to convert an existing column into an identity
column. There is no SQL ALTER statement that will convert an existing column
into an identity column.
Action: The difference cannot be eliminated with a SQL ALTER statement.
ORA-39342: Internal error - failed to import internal objects tagged with string due
to string.
Cause: Oracle Data Pump encountered an internal tagged object that failed to
import properly. All other objects with the same tag will be skipped.
Action: Contact Oracle Support Services.
ORA-39343: Object type string failed to create returning error: string
Cause: The object type could not be created. Examine the original error code to
determine the actual cause.
Action: The original error code will contain more information.
ORA-39345: WARNING: possible data loss in character set conversions
Cause: Oracle Data Pump displayed this message at the start of the import
operation because it determined that the character set or the NCHAR character set
used by the export database was different from that of the target database and also
that the target database character set was not a superset of the export database
character set.
Action: No specific user action is required.
ORA-39346: data loss in character set conversion for object string
Cause: Oracle Data Pump import converted a metadata object from the export
database character set into the target database character set prior to processing the
object. Some characters could not be converted to the target database character set
and so the default replacement character was used.
Action: No specific user action is required. This type of data loss can occur if the
target database character set is not a superset of the export databases character set.
ORA-38029 to ORA-39965 21-77
ORA-39347: Character data loss was detected during conversion, the row was
rejected.
Cause: The row contained characters that did not exist in the destination character
set.
Action: No specific user action is required. The destination character set must be a
superset of the source character set to avoid data loss.
ORA-39352: Wrong number of TRANSPORT_DATAFILES specified: expected
string, received string
Cause: The number of TRANSPORT_DATAFILES specified on the impdp
command was not correct.
Action: Specify the correct TRANSPORT_DATAFILES for this transportable job.
ORA-39353: Data was not imported for string. Cannot locate the time zone version
string file.
Cause: This table contains TIMESTAMP WITH TIME ZONE data and Oracle Data
Pump needed to load the source version of the time zone file. This version cannot
be located.
Action: Install the latest time zone version files.
ORA-39357: WARNING: Oracle Data Pump operations are not typically needed
when connected to the root or seed of a container database.
Cause: The Oracle Data Pump client was attached to the root or seed container
database.
Action: Continue if this is the desired connection string or attach to a pluggable
database within the container database.
ORA-39358: Export dump file version string not compatible with target version
string
Cause: The Oracle Data Pump export job version was newer than the target
compatibility version.
Action: Upgrade the target database to a compatibility level of at least the export
job version, or rerun the export job with a job version that is lower than or equal to
the compatibility version of the target database.
ORA-39359: Source time zone version is string and target time zone version is
string.
Cause: The time zone version of the source database is not the same as the time
zone version of the target database.
Action: Tables containing TIMESTAMP WITH TIME ZONE data cannot be
imported with transportable tablespace technology when time zone versions are
different between the export and target databases. All affected tables will be
reported during the import job and will not be created. If any are reported, convert
the target database to the same time zone version as the source or use Oracle Data
Pump with conventional data movement to export then import the affected tables.
ORA-39360: Table string was skipped due to transportable import and TSLTZ
issues resulting from time zone mismatch.
Cause: The time zone of the source database is different than the time zone of the
target database and this table contains TIMESTAMP WITH LOCAL TIME ZONE
data.
21-78 Oracle Database Error Messages
Action: Convert the target database to the same time zone as the source database
or use Oracle Data Pump with conventional data movement to export then import
this table.
ORA-39361: Source time zone is string and target time zone is string.
Cause: The time zone of the source database is different than the time zone of the
target database.
Action: Tables containing TIMESTAMP WITH LOCAL TIME ZONE data cannot
be imported with transportable tablespace technology when time zones are
different between the export and target databases. All affected tables will be
reported during the import job and will not be created. If any are reported, convert
the target database to the same time zone as the source or use Oracle Data Pump
with conventional data movement to export then import the affected tables.
ORA-39363: Type evolution could not be preserved for string
Cause: Trying to apply each version of the type during import resulted in
compilation warnings. The type was successfully recreated to the latest version
only.
Action: Export dump files as well as transportable tablespaces that contain earlier
versions of this type cannot be imported on top of this type definition.
ORA-39364: encryption password is too long
Cause: The encryption password provided to the Oracle Data Pump job was
invalid because its length was greater than the maximum allowed. When using the
password to encrypt the dump file set, the maximum length is 128 bytes. When
using the password to re-encrypt encrypted columns only, the maximum length is
30 bytes.
Action: Retry the operation with a valid encryption password.
ORA-39365: supplemental log data could not be generated for string
Cause: The instance was unable to generate supplemental log data when Data
Pump was importing the table. Supplemental logging is not supported for Data
Pump import of tables containing columns of user-defined types.
Action: No action is required for replication using Oracle GoldenGate. For logical
standby users, perform a separate import of this table into the standby database.
ORA-39366: disable table lock on string.string failed with: string
Cause: Examine the original error code to determine the actual cause.
Action: The original error code contains more information.
ORA-39367: Statistcis are being skipped. Cannot locate the time zone version string
file.
Cause: Importing statistics requires that the Oracle Data Pump load the source
version of the time zone file. This version cannot be located.
Action: Install the latest time zone version files.
ORA-39368: cannot alter partition varray column properties
Cause: DBMS_METADATA_DIFF was comparing two partitioned tables. There is
no SQL ALTER statement to change varray column properties.
Action: The difference cannot be eliminated with an SQL ALTER statement.
ORA-39369: some rows may not be exported for string due to block corruption
ORA-38029 to ORA-39965 21-79
Cause: The corrupted data blocks were ignored when Oracle Data Pump was
exporting the table.
Action: No action is required.
ORA-39370: remap value string is too long
Cause: The remap value provided to the Oracle Data Pump job was invalid
because its length was greater than the maximum allowed.
Action: Retry the operation with a valid remap value.
ORA-39371: cannot specify partition in remap_table without departitioning
Cause: The 'remap_table' value specified a partition but the tables were not being
departitioned.
Action: Either remove the partition name in the 'remap_table' parameter or add
the 'partition_options=departition' parameter.
ORA-39500: failed to notify CRS of a Startup/Shutdown event for database "string",
instance "string" (ignored)
Cause: The instance was unable to obtain the context or information required to
notify the CRS framework.
Action: None Required. The error is ignored.
ORA-39501: failed to notify CRS of a Startup/Shutdown event [string] (ignored)
Cause: The instance was unable to communicate with the CRS framework.
Action: None Required. The error is ignored.
ORA-39502: failed to notify CRS of a Startup/Shutdown event [string] (ignored)
Cause: The instance was unable to create an environment context.
Action: None Required. The error is ignored.
ORA-39503: failed to notify CRS of a Startup/Shutdown event [string] (ignored)
Cause: The instance was unable to populate the environment context.
Action: None Required. The error is ignored.
ORA-39504: failed to notify CRS of a Startup/Shutdown event [string] (ignored)
Cause: The instance was unable to find the location of the alert file.
Action: None Required. The error is ignored.
ORA-39510: CRS error performing string on string 'string' on 'string' string
Cause: Unable to perform action on associated CRS resource.
Action: See following error messages for additional information. Fix error and
retry.
ORA-39600: Queue keys needs to be a suffix of cluster key.
Cause: Attempt to specify queue key columns that don't form a suffix of the
cluster key.
Action: Only specify queue key columns as a suffix of cluster key.
ORA-39601: Hash key is required.
Cause: Missing hash key in the cluster key specification.
Action: Specify one or more hash key columns.
ORA-39700: database must be opened with UPGRADE option
21-80 Oracle Database Error Messages
Cause: A normal database open was attempted, but the database has not been
upgraded to the current server version.
Action: Use the UPGRADE option when opening the database to run
catupgrd.sql (for database upgrade), or to run catalog.sql and catproc.sql (after
initial database creation).
ORA-39701: database must be mounted EXCLUSIVE for UPGRADE or
DOWNGRADE
Cause: The database was mounted for SHARED cluster access.
Action: Set the CLUSTER_DATABASE initialization parameter to FALSE and
restart the server with the UPGRADE or DOWNGRADE option.
ORA-39702: database not open for UPGRADE or DOWNGRADE
Cause: An upgrade, downgrade, reload, or patch script was invoked when the
database was not open for UPGRADE or DOWNGRADE.
Action: Use STARTUP UPGRADE to open the database for upgrade or to apply a
patch set. Use STARTUP DOWNGRADE for running a downgrade script or the
reload script.
ORA-39703: server version and script version do not match
Cause: An upgrade, downgrade, reload, or patch script was invoked, but the
database instance version was not the version for which the script was intended.
Action: Check that the correct ORACLE_HOME and ORACLE_SID environment
variables are set. Also check that the SQL script is being invoked from the correct
ORACLE_HOME.
ORA-39704: permission to modify component registry entry denied
Cause: An attempt was made to modify an entry in the component registry, but
the session user was not authorized; only the CONTROL or SCHEMA user for the
component are authorized to modify the component registry entry.
Action: Connect as either the CONTROL or SCHEMA user for the component.
ORA-39705: component 'string' not found in registry
Cause: No entry in the component registry was found for the specfied
component.
Action: Check the spelling of the component ID and use the DBA_REGISTRY
view to list the existing components.
ORA-39706: schema 'string' not found
Cause: The schema name specified was not found in the database.
Action: Create the schema before loading the component.
ORA-39707: compatibile parameter string too high for downgrade to string
Cause: A downgrade was attempted, but the compatible initialization parameter
value was greater than the downgrade release version.
Action: Once the compatible value has been raised, downgrade to earlier releases
is not supported.
ORA-39708: component 'string' not a string component
Cause: The component was not a component for the specified namespace.
Action: Either enter a valid component identifier for the namespace or set the
session namespace to the correct component namespace.
ORA-38029 to ORA-39965 21-81
ORA-39709: incomplete component downgrade; string downgrade aborted
Cause: One or more components did not have a status of DOWNGRADED.
Action: Correct the component problem and re-run the downgrade script.
ORA-39710: only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
Cause: An attempt was made to connect to a database when the database was
OPEN for UPGRADE or DOWNGRADE.
Action: Try to connect again after the database upgrade or downgrade is
complete.
ORA-39711: critical patch number less than last installed CPU number
Cause: A Critical Patch Update (CPU) script was invoked that had a number that
was less than the last CPU installed in the database.
Action: Check the DBA_REGISTRY_HISTORY view to identify the last CPU for
the database, and install the most recent CPU.
ORA-39712: XE edition server cannot open database
Cause: An attempt was made to open a Standard Edition or Enterprise Edition
database with the Express Edition of the server.
Action: Use the Express Edition server only with Express Edition databases.
ORA-39714: upgrade script utlmmig.sql failed
Cause: A normal database open was attempted, but the upgrade script
utlmmig.sql failed to complete.
Action: Use the UPGRADE option when opening the database and then run
utlmmig.sql.
ORA-39715: Downgrade script UTLMMIGDOWN.SQL failed.
Cause: A normal database open was attempted, but the downgrade script
UTLMMIGDOWN.SQL failed to complete.
Action: Use the DOWNGRADE option when opening the database and then run
UTLMMIGDOWN.SQL.
ORA-39726: unsupported add/drop column operation on compressed tables
Cause: An unsupported add/drop column operation for compressed table was
attemped.
Action: When adding a column, do not specify a default value. DROP column is
only supported in the form of SET UNUSED column (meta-data drop column).
ORA-39727: COMPATIBLE must be set to 10.0.0.0.0 or higher
Cause: An add/drop column operation for compressed table has been performed
on the database. This requires COMPATIBLE to be set to 10.0.0.0.0 or higher
during upgrade from 9.2 to a 10i or higher release.
Action: Set COMPATIBLE to 10.0.0.0.0 and retry the upgrade.
ORA-39751: partitioned table on both sides of PARTITIONED OUTER JOIN is not
supported
Cause: An attempt was made to partition both sides of PARTITIONED OUTER
JOIN.
Action: Specify partitioned table on one side of PARTITIONED OUTER JOIN
only.
21-82 Oracle Database Error Messages
ORA-39752: redundant column in partitioning and join columns is not allowed
Cause: An attempt was made to specify redundant columns in partitioning and
join columns for NATURAL or named column PARTITIONED OUTER JOIN.
Action: Do not specify redundant column in partitioning and join columns.
ORA-39753: unsupported use of subquery in PARTITIONED OUTER JOIN
condition
Cause: An attempt was made to use subquery in PARTITIONED OUTER JOIN
condition.
Action: Remove subquery from the join condition.
ORA-39754: FULL PARTITIONED OUTER JOIN is not supported
Cause: An attempt was made to use FULL PARTITIONED OUTER JOIN.
Action: Specify FULL PARTITIONED OUTER JOIN through UNION of LEFT and
RIGHT PARITTION OUTER JOIN.
ORA-39755: cannot use PARTITIONED OUTER JOIN with a left correlation
Cause: An attempt was made to use a PARTITIONED OUTER JOIN where the
right side is a lateral view with a left correlation to the left side and is partitioned.
Action: Rewrite the query without the left correlation.
ORA-39761: stream reset required before loading this stream again
Cause: An attempt was made to load a stream that was previously loaded but has
not been reset yet.
Action: Reset the specified stream and convert column array data to it before
attempting to load it again.
ORA-39762: streams must be loaded in conversion order
Cause: An attempt was made to load a stream out of conversion order.
Action: Load streams in the same order they were converted.
ORA-39763: stream must be completely loaded before it is reset
Cause: An attempt was made to reset a stream that contains converted column
array data and hasn't been completely loaded yet.
Action: Before resetting a stream, load it until a status of OCI_SUCCESS, OCI_
NO_DATA, or OCI_NEED_DATA is returned.
ORA-39764: specified stream is not in the specified direct path context
Cause: A direct path operation was attempted using a stream that was not created
in the specfied direct path context.
Action: Only use streams created in the specified direct path context.
ORA-39765: stream must be reset before used in a column array conversion
Cause: The stream was completely loaded, but has not been reset yet.
Action: Reset loaded streams after load returns OCI_SUCCESS, OCI_NO_DATA,
or OCI_NEED_DATA. The stream can then be used in a column array to stream
conversion.
ORA-39766: invaid stream specified for column array conversion
Cause: A stream must be loaded and reset before used again in a
column-array-to-stream conversion. This error is issued if another stream has
ORA-38029 to ORA-39965 21-83
subsequently been converted before the specified stream has been loaded, or if the
latest load of this stream returned OCI_ERROR.
Action: Don't convert into a previous stream before it is loaded. Also, when load
stream returns OCI_ERROR, the stream must be loaded again to insure any
remaining information in the stream is loaded. The stream must be loaded even if
the last or only row was in error. There may be error information in the stream that
needs to be sent to the server.
ORA-39767: finish is not allowed when unloaded stream data exists
Cause: A direct path finish was attempted when at least one stream buffer has not
been completely loaded.
Action: All streams must be loaded after a column array to stream conversion
until load stream returns a status of OCI_SUCCESS or OCI_NO_DATA. The load
can then be finished.
ORA-39768: only one direct path context top level column array is allowed
Cause: Attempt to create multiple top level column arrays in a direct path context,
when only one is allowed.
Action: Create another direct path context if additional top level column arrays
are required.
ORA-39769: finish is not allowed with an incompletely loaded last row
Cause: Part of a row has been loaded, but it is not complete.
Action: Finish loading the current row when load stream returns OCI_ERROR or
OCI_NEED_DATA.
ORA-39771: stream must be loaded before its handle is freed
Cause: An attempt was made to free a stream handle after conversion but before
the stream was loaded.
Action: Load the stream until OCI_SUCCESS, OCI_NEED_DATA or OCI_NO_
DATA is returned before attempting to free the stream handle. If OCI_NEED_
DATA is returned, another stream must be loaded to complete last row.
ORA-39772: column array reset disallowed after OCI_CONTINUE or OCI_NEED_
DATA
Cause: An attempt was made to reset a column array when a row conversion is
still in progress.
Action: Complete the current row before reseting the column array. To ignore the
current row when conversion returned OCI_NEED_DATA, set the current column
flag to OCI_DIRPATH_COL_ERROR. This should be followed by a conversion,
which will undo and ignore the row. The column array(s) can then be reset.
ORA-39773: parse of metadata stream failed
Cause: An unexpected error occured while attempting to parse the metadata //
stream for a table being loaded.
Action: Call Oracle support.
ORA-39774: parse of metadata stream failed with the following error: string
Cause: An unexpected error occured while parsing the metadata stream.
Action: See the secondary error for more information.
ORA-39775: direct path API commit not allowed due to previous fatal error
Cause: An attempt was made to commit a Direct Path context after a fatal error.
21-84 Oracle Database Error Messages
Action: Correct the error and retry.
ORA-39776: fatal Direct Path API error loading table string
Cause: A fatal error was detected loading the specified or previous table.
Action: Correct the error and retry.
ORA-39777: data saves are not allowed when loading lob columns
Cause: An attempt was made to save data when loading lob columns or columns
stored as lobs (such as varrays and xml types).
Action: Do not attempt to do a data save or partial save when loading lob
columns. A finish save is allowed.
ORA-39778: the parallel load option is not allowed when loading lob columns
Cause: An attempt was made to load lob columns using the attribute OCI_ATTR_
DIRPATH_PARALLEL. This error will also be issued when loading any columns
that are stored as lobs (such as varrays and xml types).
Action: Do not use the parallel attribute when loading lob columns.
ORA-39779: type "string"."string" not found or conversion to latest version is not
possible
Cause: Unable to import table data using the specified type. The type was
nonexistent in the database or the input type could not be converted to the existing
type. The reasons why a conversion was not possible are:
1. The version of the type in the database was greater than the version of the type
at export time because 1 or more attributes have been added or dropped from the
type.
2. If the type existed in the database prior to the import operation, then its internal
identifier may not match the internal identifier of the type from the export
database. The identifiers must match for an import to succeed.
Action: Ensure the types in the database match those at export time.
ORA-39780: Direct path context operations are not allowed after the context is
aborted or finished
Cause: The specified direct path context was aborted or finished.
Action: Do not pass a direct path context that has ended to any direct path
functions.
ORA-39781: Direct path stream loads are not allowed after another context loading
the same table has ended
Cause: Attempt to load a stream in one context after another loading the same
table has ended.
Action: Close all contexts before trying to create another that loads the same table
as a previous context in the same session.
ORA-39782: Direct path prepare is not allowed after another context loading the
same table has ended
Cause: Direct path prepare called after a context loading the same table has
ended.
Action: Close all contexts before trying to create another that loads the same table
as a previous context in the same session.
ORA-39783: Invalid direct path transaction active
ORA-38029 to ORA-39965 21-85
Cause: Direct path operations were not performed in the transaction started by
the first OCIDirPathPrepare call.
Action: Ensure the correct transaction is active prior to calling Direct Path API
operations.
ORA-39784: This direct path operation is not allowed while another is in progress
Cause: Another direct path operation was active.
Action: Complete any direct path operations in progress before attempting this
operation.
ORA-39785: SQL expressions returning ADT objects are not allowed in direct path
Cause: The passed SQL expression returned a user-defined ADT which was not
supported.
Action: Remove the SQL expression.
ORA-39786: Number of columns does not match between export and import
databases
Cause: External tables could not import into a table with mismatched columns.
Action: Ensure the number of columns matches between export and import
database.
ORA-39787: Column string subtype "string"."string" is not instantiable.
Cause: Subtype specified was not instantiable.
Action: Ensure all subtypes specified are instantiable.
ORA-39788: Subtype "string"."string" is specified multiple times for column string.
Cause: Subtype specified was not unique.
Action: Ensure all subtypes specified are unique.
ORA-39789: "string"."string" is not a valid type for column string.
Cause: Subtype specified was not a valid type for the column being loaded.
Action: Ensure all subtypes specified are valid types for the column being loaded.
ORA-39790: Attribute "string" specified multiple times for column string.
Cause: Attribute specified multiple times.
Action: Ensure all attributes specified are unique.
ORA-39791: Attribute "string" for column string is not in subtype "string"."string".
Cause: Attribute was not included in the subtype indicated.
Action: Ensure the attribute is included in the subtype indicated by the specified
subtype index.
ORA-39792: Attribute "string" is not valid for subtypes(s) loaded into column
string.
Cause: Attribute specified was not included in any subtypes specified for the
column or the declared subtype of the column.
Action: Ensure the attribute is included in at least one of the subtypes loaded into
the column.
ORA-39793: Attribute "string" is not unique within the hierarchy being loaded.
Cause: The attribute was defined in multiple lines of descent in the hierarchy
being loaded.
21-86 Oracle Database Error Messages
Action: When describing the attribute, a subtype index must be specified to
uniquely identify the attibute being loaded.
ORA-39794: No attributes loaded for subtype "string"."string".
Cause: None of the attributes loaded were included in the type shown.
Action: At least one attribute must be loaded for each subtype specified.
ORA-39795: Subtype index is not first attribute for object table or column, string.
Cause: The subtype index was not the first attribute when describing the atributes
of an object column or object table with multiple subtypes.
Action: Describe the subtype index as the first attribute for this object column or
object table.
ORA-39796: column array entry for string is not valid for the current subtype
Cause: This column was not part of the current subtype being loaded for this
object column or table. Therefore, its entry must be null in the column array.
Action: Set the column array entry to null.
ORA-39797: The subtype index value is not valid.
Cause: The subtype index value in the column array was not valid for the object
column or object table.
Action: Set a valid subtype index value in the column array for this table or
column.
ORA-39798: The column array row offset number is out of range (max: number).
Cause: The specified row offset was too large for the column array.
Action: Ensure the row offset is in range.
ORA-39799: The column index number is out of range (max: number).
Cause: The specified column index was too large for the column array.
Action: Ensure the column index is in range.
ORA-39800: Database version number does not support the load of multiple
subtypes.
Cause: Direct Path API support for loading multiple subtypes of an object table or
column was only present in the Oracle 11 release and higher.
Action: Upgrade database to Oracle 11 or higher.
ORA-39801: Subtype "string"."string" is not a valid subtype for column string.
Cause: Subtype specified was not the declared type nor was it derived from the
declared type.
Action: Ensure all subtypes specified are either the declared type or derived from
the declared type.
ORA-39802: ADT object column string specified a SQL expression which is not
allowed in direct path mode.
Cause: The ADT column reported in the error specified a SQL expression which
returned the ADT. This is not supported.
Action: Remove the SQL expression.
ORA-39803: Data saves are not allowed on tables with partitioning referential
constraints.
ORA-38029 to ORA-39965 21-87
Cause: Data saves (and the sqlldr ROWS parameter) are not allowed when
loading both the parent and child tables of a partitioning referential constraint.
Action: Do not attempt data saves when loading both the parent and child tables
of a partitioning referential constraint.
ORA-39804: The load was aborted due to an error loading parent string while also
loading child string.
Cause: An error occurred while loading the child and parent table of a
partitioning referential constraint. The load was aborted to ensure the partitioning
referential constraint was not violated.
Action: Fix the error that caused the load to abort and retry.
ORA-39805: Parallel loads are not allowed when loading child and parent.
Cause: A parallel load was requested when loading the child and parent of a
partitioning referential constraint. This is not allowed.
Action: Remove the parallel option.
ORA-39806: The attempt to lock string parent table string string string failed.
Cause: While loading the child table of a partitioning referential constraint, the
parent table must be locked in SHARE mode.
Action: Determine why the parent table could not be locked and retry.
ORA-39807: Partial data save on child string was ignored.
Cause: An attempt was made to partially save data when loading both the child
and parent of a partitioning referential constraint or when loading a table with a
domain index.
Action: Fix the error that caused the partial load and retry.
ORA-39808: The SINGLEROW option must be specified for parent table string.
Cause: The SINGLEROW option was not specified when loading both the parent
and child table of a partitioning referential constraint.
Action: Ensure the SINGLEROW option is specified for the parent when loading
the parent and child of a partitioning referential constraint.
ORA-39809: Data saves are not allowed on tables with domain indexes.
Cause: Data saves (and the sqlldr ROWS parameter) could not be allowed when
loading a table with domain indexes.
Action: Do not attempt data saves when loading a table with domain indexes.
ORA-39810: Data saves are not allowed when NO_INDEX_ERRORS is specified.
Cause: Data saves (and the sqlldr ROWS parameter) could not be allowed when
loading with the NO_INDEX_ERRORS option.
Action: Do not attempt data saves when loading a table with the NO_INDEX_
ERRORS option.
ORA-39811: index string.string had the following error:
Cause: An error occurred on the index; error follows.
Action: Fix the error and retry.
ORA-39812: index string.string partition string had the following error:
Cause: An error occurred on the index; error follows.
Action: Fix the error and retry.
21-88 Oracle Database Error Messages
ORA-39813: index string.string had string partition errors:
Cause: A logical index error occurred on a partitioned index which affected one or
more index partitions, which are listed below this message.
Action: Fix the error(s) and retry.
ORA-39814: The SKIP_INDEX_MAINTENANCE option is not allowed with NO_
INDEX_ERRORS.
Cause: The SKIP_INDEX_MAINTENANCE option was used with the NO_
INDEX_ERRORS option.
Action: Do not use SKIP_INDEX_MAINTENANCE with NO_INDEX_ERRORS.
ORA-39815: Direct Path Unload of an external table is not allowed.
Cause: An attempt was made to use Direct Path API Unload to unload an external
table.
Action: Do not use Direct Path Unload to unload an external table.
ORA-39816: Direct Path Unload of tables with encrypted column(string.string) is
not allowed.
Cause: An attempt was made to use Direct Path API Unload to unload a table
with encrypted columns.
Action: Do not use Direct Path Unload to unload a table with encrypted columns.
ORA-39817: index string.string was ignored due to:
Cause: Index was unusable at the start of the load and it was requested that
unusable indexes be skipped.
Action: No action required.
ORA-39818: index string.string partition string was ignored due to:
Cause: Index was unusable at the start of the load and it was requested that
unusable indexes be skipped.
Action: No action required.
ORA-39819: The OCI_ATTR_DIRPATH_NO_INDEX_ERRORS attribute cannot be
set to TRUE in direct path parallel loads.
Cause: An attempt was made to set the OCI_ATTR_DIRPATH_NO_INDEX_
ERRORS attribute to TRUE in a direct path parallel load.
Action: Do not set the OCI_ATTR_DIRPATH_NO_INDEX_ERRORS to TRUE for
direct path parallel loads.
ORA-39820: Zero length LONG piece detected for column string row string.
Cause: A zero length piece was detected for a LONG column.
Action: Do not use a length of zero when loading LONG columns.
ORA-39821: domain index on columnar data made unusable
Cause: An attempt was made to load a columnar table with a domain index using
SQL*Loader direct part load
Action: None
ORA-39822: A new direct path operation is not allowed in the current transaction.
Cause: All previous direct path contexts ended and the current transaction was
ready for a commit or abort of those changes.
ORA-38029 to ORA-39965 21-89
Action: Commit or abort the current transaction, and start a new transaction for
the next direct path context.
ORA-39823: The attribute OCI_ATTR_DIRPATH_USE_ACTIVE_TRANS is only
allowed for load operations.
Cause: The attribute OCI_ATTR_DIRPATH_USE_ACTIVE_TRANS was set for a
nonload operation.
Action: Use OCI_ATTR_DIRPATH_USE_ACTIVE_TRANS for load operations
only.
ORA-39824: The OCI_ATTR_DIRPATH_USE_ACTIVE_TRANS attribute was set
when no transaction was active.
Cause: There was no active transaction to use.
Action: Start a transaction or do not set the attribute OCI_ATTR_DIRPATH_USE_
ACTIVE_TRANS to TRUE.
ORA-39825: Direct path load of view or synonym (string.string) with multiple
dependencies not permitted.
Cause: An attempt was made to load a view or synonym which has more than a
single dependency.
Action: A view or synonym being loaded by the direct path API must resolve to a
single object.
ORA-39826: Direct path load of view or synonym (string.string) could not be
resolved.
Cause: A synonym or view could not be translated.
Action: Verify that the view or synonym is valid.
ORA-39827: Direct path load of PL/SQL function not permitted.
Cause: An attempt was made to load a PL/SQL function with the direct path API.
Action: Remove PL/SQL function the direct path load.
ORA-39828: Constraint string was disabled because of index string.string error.
Cause: The index used for the constraint was set as unusable.
Action: Fix the error that caused the index to be set unusable.
ORA-39829: function-based index on columnar data made unusable
Cause: An attempt was made to load a columnar table with a function-based
index using SQL*Loader direct path load.
Action: Rebuild the function-based index after the load completes.
ORA-39830: XML parsing failed string
Cause: XML parser returned an error while trying to parse the document.
Action: Fix the error that caused the document to be invalid.
ORA-39831: Direct path load failed, (string.string) is not a table.
Cause: Object being loaded did not resolve to a table.
Action: Verify that the view or table name is correct.
ORA-39832: Direct path unload was not allowed due to columns with default
values.
21-90 Oracle Database Error Messages
Cause: Direct path unload was attempted on a table with columns that have
default values.
Action: Do not attempt a direct path unload of a table with columns that have
default values.
ORA-39833: Direct path parallel load was not allowed on a temporary table.
Cause: A direct path parallel load was attempted on a temporary table.
Action: Do not attempt a direct path parallel load on a temporary table.
ORA-39834: Direct path load or unload was not allowed on a remote table.
Cause: An attempt was made to specify a remote table in a direct path API load or
unload.
Action: Do not specify a remote table in a direct path API load or unload.
ORA-39835: Direct path load partition memory exceeded. PGA use is stringkb, PGA
limit is: stringkb
Cause: A direct path load ran out of process memory when loading multiple
partitions.
Action: Use the PARTITION_MEMORY parameter to limit memory used when
loading many partitions. Once this limit is reached, loading of some partition rows
will be delayed until memory use falls below the limit. Use a value (kb) lower than
the current program global area (PGA) limit included in this message and try the
load again.
ORA-39861: auxiliary data file copy file for Pluggable Database string: "string"
Cause: This message reports the filename for details of another message.
Action: Other messages will accompany this message. See the associated
messages for the appropriate action to take.
ORA-39862: RESETLOGS option only valid after a Pluggable Database incomplete
recovery
Cause: The ALTER PLUGGABLE DATABASE OPEN RESETLOGS command was
issued, but the Pluggable Database was not flashed back or point-in-time
recovered.
Action: Retry the ALTER PLUGGABLE DATABASE OPEN command without
specifying RESETLOGS.
ORA-39863: An earlier Pluggable Database incomplete recovery failed.
Cause: An earlier Pluggable Database flashback or point-in-time recovery failed.
Action: Retry the Pluggable Database flashback or incomplete recovery.
ORA-39865: cannot FLASHBACK beyond Pluggable Database resetlogs operation
Cause: An attempt was made to perform a FLASHBACK DATABASE beyond a
Pluggable Database resetlogs system change number (SCN).
Action: Choose a FLASHBACK SCN that is more recent than the Pluggable
Database resetlogs SCN.
ORA-39866: Data files for Pluggable Database string must be offline to flashback
across PDB point-in-time recovery.
Cause: An attempt was made to perform a FLASHBACK DATABASE beyond a
Pluggable Database (PDB) resetlogs system change number (SCN) while data files
for the Pluggable Database are still online.
ORA-38029 to ORA-39965 21-91
Action: Take the data files for the Pluggable Database (PDB) offline before
performing the FLASHBACK DATABASE command. To bring the PDB to the
same past point in time as the container database (CDB), those data files can be
restored from backups and recovered to that same past point in time. This can be
done in one of two ways:
* Flashback the CDB and open the CDB with resetlogs. Restore the PDB later, and
perform a complete PDB recovery.
* Flashback the CDB first. Restore and recover the PDB to the same system change
number (SCN). Open CDB with resetlogs.
ORA-39870: container database is not open in read/write mode
Cause: A command was attempted that requires the container database (CDB) to
be open in read/write mode.
Action: Open the container database in read/write mode and try the command
again.
ORA-39871: An earlier Pluggable Database resetlogs operation failed after making
changes.
Cause: An earlier ALTER PLUGGABLE DATABASE OPEN RESETLOGS
command failed after it made some changes.
Action: Perform another Pluggable Database point-in-time recovery before
attempting to open the Pluggable Database with RESETLOGS.
ORA-39872: Data file number is in the middle of Pluggable Database resetlogs
operation.
Cause: The data file was in the middle of a Pluggable Database resetlogs
operation.
Action: Find the right file version or perform more media recovery. For additional
information, see other errors.
ORA-39873: Restore all data files to a checkpoint SCN lower than string.
Cause: This error provides additional information for error 39874.
Action: Restore the data files as suggested and restart the recovery process.
ORA-39874: Pluggable Database string recovery halted
Cause: The Pluggable Database was recovered into an orphan branch.
Action: Restore all data files to a checkpoint system change number (SCN) lower
than the branch point and restart the recovery process. Check the alert log for
additional information.
ORA-39875: Data file string is in the middle of Pluggable Database resetlogs
operation.
Cause: The data file is in the middle of a Pluggable Database (PDB) resetlogs
operation.
Action: If possible, recover the data file further so that it is not in the middle of a
PDB resetlogs operation. Another alternative is to perform PDB point-in-time
recovery.
ORA-39876: cannot perform CDB OPEN RESETLOGS because data file string is in
the middle of a PDB resetlogs operation
Cause: The data file mentioned was in the middle of a Pluggable Database (PDB)
resetlogs operation.
21-92 Oracle Database Error Messages
Action: Recover the container database (CDB) to a different system change
number (SCN) at which the data files are not in the middle of a PDB resetlogs
operation. Alternatively, you can offline the problematic data file and let CDB
OPEN RESETLOGS succeed. You may need to perform PDB point-in-time
recovery later in order to open the PDB of the offlined data file.
ORA-39877: keyword ONLINE or OFFLINE expected
Cause: The ONLINE or OFFLINE keyword was not specified after the ALL
keyword.
Action: Use the correct syntax.
ORA-39878: Only one Pluggable Database name can be specified.
Cause: Multiple Pluggable Database names were specified for the ALTER
PLUGGABLE DATABASE OPEN RESETLOGS command.
Action: Specify only one Pluggable Database name.
ORA-39879: Pluggable Database string is in the middle of a Pluggable Database
RESETLOGS operation
Cause: There was already an on-going Pluggable Database OPEN RESETLOGS
operation for this Pluggable Database.
Action: If needed, retry after the Pluggable Database OPEN RESETLOGS
operation completes.
ORA-39880: One or more pluggable databases were in the middle of a point-in-time
recovery at this incomplete database recovery SCN.
Cause: In the past, one or more pluggable databases had an active pluggable
database RESETLOGS operation as of this incomplete recovery SCN.
Action: Additional messages are logged in the alert log indicating all of the
pluggable databases affected by this container database OPEN RESETLOGS
operation. Recover the container database to a different system change number
(SCN) at which none of the pluggable databases had an active RESETLOGS
operation. To continue the container database OPEN RESETLOGS operation at the
same SCN, offline all of the data files of the affected pluggable databases first and
reissue the command. However, a new point-in-time recovery of the affected
pluggable databases would be required before these databases can be opened
again.
ORA-39881: Pluggable database string must be closed while recovering the physical
standby across PDB RESETLOGS
Cause: The pluggable database (PDB) is open while the physical standby is
recovering across a PDB RESETLOGS operation for the PDB.
Action: Close the PDB and restart physical standby recovery.
ORA-39901: Partitioned table string.string is partially contained in the
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Check table partitions by querying SYS.DBA_TAB_PARTITIONS.
ORA-39902: Subpartitioned table string.string is partially contained in the
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
ORA-38029 to ORA-39965 21-93
Action: Check table subpartitions by querying SYS.DBA_TAB_SUBPARTITIONS.
ORA-39903: IOT Partition string.string is partially contained in the transportable
set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Check table partitions by querying SYS.DBA_IND_PARTITIONS.
ORA-39904: Partitioned object string.string is partially contained in the
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Check partitions and overflow segments by querying SYS.DBA_IND_
PARTITIONS and SYS.DBA_TAB_PARTITIONS.
ORA-39905: Table string.string in tablespace string points to LOB segment
string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39906: Constraint string between table string.string in tablespace string and
table string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39907: Index string.string in tablespace string points to table string.string in
tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39908: Index string.string in tablespace string enforces primary constraints
string of table string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39909: Index string.string in tablespace string points to table/cluster
string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39910: Partitioned Global index string.string in tablespace string points to
partition string of table string.string in tablespace string outside of transportable
set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
21-94 Oracle Database Error Messages
ORA-39911: Index string.string in tablespace string points to partition string of table
string.string in tablespace string outside of transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39912: Partitioned index string.string in tablespace string points to table
string.string in tablespace string outside of transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39913: string string.string in tablespace string not allowed in transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39914: Index string.string in tablespace string points to subpartition string of
table string.string in tablespace string outside of transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39915: Partition string of table string.string in tablespace string points to LOB
segment string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39916: Subpartition string of table string.string in tablespace string points to
LOB segment string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39917: SYS owned object string in tablespace string not allowed in pluggable
set
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39918: PLSQL Functional Index string.string in tablespace string not allowed
in transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39919: Object string.string in tablespace string not contained within
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Check SYS.DBA_OBJECTS.
ORA-38029 to ORA-39965 21-95
ORA-39920: Rollback segment string in tablespace string not allowed in
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39921: Default Partition (Table) Tablespace string for string not contained in
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39922: Default Partition (Index) Tablespace string for string not contained in
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39923: Default Composite Partition (Table) Tablespace string for string not
contained in transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39924: Default Composite Partition (Index) Tablespace string for string not
contained in transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39925: LOB segment string.string in tablespace string points to table
string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39926: Join index between table string.string in tablespace string and table
string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39927: Scoped REF constraint between table string.string in tablespace string
and table string.string in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39928: string string.string in tablespace string contains evolved type data that
have not been upgraded.
Cause: Transportable tablespace operation could not be performed because some
tables depending on evolved types were not upgraded.
21-96 Oracle Database Error Messages
Action: Transportable tablespace operation can only be performed when all tables
depending on evolved types have been upgraded. Perform ALTER TABLE <tab_
name> UPGRADE for the table name listed in the message above
ORA-39929: Table string.string in tablespace string has encrypted columns which
are not supported.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39930: Violation string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Contact Oracle Support Services.
ORA-39931: XML Schema string Owner: string not fully contained in the
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Identify the associated elements and resolve self containment.
ORA-39932: Extensible Index string.string not fully contained in the transportable
set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Identify the associated table and list of secondary objects and resolve self
containment.
ORA-39933: Parent table string.string and its nested table columns are not fully
contained in the transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Identify the nested tables using view DBA_NESTED_TABLES and resolve
self containment.
ORA-39934: Materialized view log string.string in tablespace string and master
table string.string in tablespace string are not fully contained in the
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39935: Updatable materialized view log string.string in tablespace string and
materialized view string.string in tablespace string are not fully contained in the
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39936: Token manager for the CSX tablespace string not fully contained in the
transportable set.
Cause: Informational message to describe a failure during transportable
containment checking.
ORA-38029 to ORA-39965 21-97
Action: Include the specified tablespace into the transportable set.
ORA-39937: Unsupported operation, default token tables used for binary XML
data.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Copy default token tables into a new token table set using DBMS_CSX_
ADMIN package.
ORA-39938: Operation not supported, tablespace string contains binary XML data.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: None required.
ORA-39939: More than one set of token tables are used in tablespace string.
Cause: Informational message to describe a failure during transportable
containment checking.
Action: Remap tables in the specified tablespace to use same token tables.
ORA-39940: Child reference partitioned table string.string in tablespace string or
parent table string.string in tablespace string is included but not both.
Cause: Informational message to describe a failure during transportable
containment checking. Both parent and child reference partition tables must be
included.
Action: Check reference partitioned tables.
ORA-39941: Partitioned table string.string in tablespace string has a partition that
has an incomplete online move.
Cause: This is an informational message to describe a failure during transportable
containment checking. Online moves need to be complete before transporting a
tablespace.
Action: Use the DBMS_PART.CLEANUP_ONLINE_OP procedure to force the
online move to complete.
ORA-39942: Subpartitioned table string.string in tablespace string has a
subpartition that has an incomplete online move.
Cause: This is an informational message to describe a failure during transportable
containment checking. Online moves need to be complete before transporting a
tablespace.
Action: Use the DBMS_PART.CLEANUP_ONLINE_OP procedure to force the
online move to complete.
ORA-39943: Global index string.string in tablespace string has orphaned entries.
Cause: This is an informational message to describe a failure during transportable
containment checking. Orphaned entries need to be cleaned up before
transporting a tablespace.
Action: Use DBMS_PART.CLEANUP_GIDX() to cleanup orphaned index entries.
ORA-39944: Global partitioned index string.string in tablespace string has
orphaned entries.
Cause: This is an informational message to describe a failure during transportable
containment checking. Orphaned entries need to be cleaned up before
transporting a tablespace.
21-98 Oracle Database Error Messages
Action: Use DBMS_PART.CLEANUP_GIDX() to cleanup orphaned index entries.
ORA-39945: Token conflicting with existing tokens.
Cause: The binary XML tokens contained in the imported tablespace conflicted
with the existing tokens.
Action: Use the dump file export or import instead of transportable tablespace.
ORA-39946: Nondefault token table encountered.
Cause: During transportable tablespace import, a nondefault token table was
encountered.
Action: Use the dump file export or import instead of transportable tablespace.
ORA-39950: invalid parameter for PLSQL warnings flag
Cause: The user either entered invalid value for the PLSQL_WARNINGS flag or
the value of the flag conflicts with other values.
Action: Enter correct values for the switch.
ORA-39951: incomplete values specified for PL/SQL warning settings
Cause: The user either did not enter the value for the settings or entered
incomplete values.
Action: Enter correct syntax for the switch.
ORA-39952: only numbers can be specified as range values
Cause: The range values did not have numerical values only.
Action: Enter only numerical values.
ORA-39953: the range value specified is beyond allowed range
Cause: The range values were either too low or too high.
Action: Specify only the allowed range values.
ORA-39954: DEFERRED is required for this system parameter
Cause: The ALTER SYSTEM command for PLSQL_WARNINGS did not include
the keyword, DEFERRED.
Action: Change the command to use the keyword, DEFERRED.
ORA-39955: invalid PL/SQL warning message number
Cause: The PL/SQL message number specified was not in a valid range.
Action: Specify PL/SQL warning message numbers within the valid range.
ORA-39956: duplicate setting for PL/SQL compiler parameter string
Cause: A PL/SQL compiler parameter was set more than once.
Action: Remove the duplicate PL/SQL compiler setting.
ORA-39957: invalid warning category
Cause: The category of the message was incorrect.
Action: Specify a vaild category
ORA-39958: invalid warning category qualifier
Cause: The category qualifier was incorrect.
Action: Specify a vaild category qualifier.
ORA-39959: invalid warning number (string)
ORA-38029 to ORA-39965 21-99
Cause: The warning number was incorrect.
Action: Specify a vaild warning number.
ORA-39960: scope can only be SYSTEM or SESSION
Cause: The scope specified was not set.
Action: Specify a vaild scope, either SESSION or SYSTEM.
ORA-39961: message specified was not found
Cause: The message number specified was not set.
Action: specify the message number whise settings have been set in the given
scope.
ORA-39962: invalid parameter for PLSQL_CCFLAGS
Cause: The value for the PLSQL_CCFLAGS parameter was not valid.
Action: Specify a vaild value for the PLSQL_CCFLAGS parameter.
ORA-39964: Specified value for _PLSQL_MAX_STACK_SIZE (string) is larger than
available memory (string)
Cause: The value specified for the _PLSQL_MAX_STACK_SIZE parameter was
larger than the amount of stack size available to the process.
Action: Specify a smaller value for the _PLSQL_MAX_STACK_SIZE parameter.
ORA-39965: Collection of records with PL/SQL type attributes are not allowed in
this context.
Cause: The collection of records with attributes of PL/SQL types were not
allowed as an argument to the TABLE operator.
Action: Use the collection of records whose attributes are of the types that SQL
can understand.
扫一扫
2789
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
