ORA-12737: Instant Client Light: unsupported server
character set string
Cause:
The character set specified is not allowed for this operation or is invalid.
Instant Client Light has only minimal character sets.
Action:
Do not use Instant Client Light for this character set
ORA-12738: Express Instant Client: unsupported
client national character set string
Cause:
Only UTF8 and AL16UTF16 are allowed to be used as the national character set.
Instant Client has only minimal character sets.
Action:
Do not use Express Instant Client for this character set
ORA-12739: Express Instant Client: unsupported
client character set string
Cause:
The character set specified is not allowed for this operation or is invalid.
Express Instant Client has only minimal character sets.
Action:
Do not use Express Instant Client for this character set
ORA-12740: Express Instant Client: unsupported
server national character set string
Cause:
Only UTF8 and AL16UTF16 are allowed to be used as the national character set.
Instant Client has only minimal character sets.
Action:
Do not use Express Instant Client for this character set
ORA-12741: Express Instant Client: unsupported
server character set string
Cause:
The character set specified is not allowed for this operation or is invalid.
Express Instant Client has only minimal character sets.
Action:
Do not use Express Instant Light for this character set
ORA-12800: system appears too busy for parallel
query execution
Cause:
load on system is too high to perform parallel queries.
Action:
re-execute serially or wait until system load is reduced.
ORA-12801: error signaled in parallel query server string
Cause:
A parallel query server reached an exception condition.
Action:
Check the following error message for the cause, and consult your error manual
for the appropriate action.
ORA-12802: parallel query server lost contact with
coordinator
Cause:
A parallel query server lost contact with the foreground (coordinator)
process/thread.
Action:
Check your system for anomalies and reissue the statement. If this error persists,
contact Oracle Support Services.
ORA-12803: parallel query server lost contact with
another server
Cause:
A parallel query server lost contact with another server.
Action:
Check your system for anomalies and reissue the statement. If this error persists,
contact Oracle Support Services.
ORA-12804: parallel query server appears to have
died
Cause:
Cannot find process information for a parallel query server thread.
Action:
Check your system for anomalies and reissue the statement. If this error persists,
contact Oracle Support Services.
ORA-12805: parallel query server died unexpectedly
Cause:
A parallel query server died unexpectedly, PMON cleaning up the process.
Action:
Check your system for anomalies and reissue the statement. If this error persists,
contact Oracle Support Services. See trace file for more details.
ORA-12806: could not get background process to hold
enqueue
Cause:
Internal error.
Action:
This error should not normally occur. If it persists, contact Oracle Support
Services.
ORA-12807: process queue could not receive parallel
query message
Cause:
Internal error.
Action:
This error should not normally occur. If it persists, contact Oracle Support
Services.
ORA-12808: cannot set string_INSTANCES
greater than number of instances string
Cause:
An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER
SYSTEM command to a value larger than the number of available instances.
Action:
See the accompanying message for the current allowable maximum value, or set
SCAN_INSTANCES / CACHE_INSTANCES to ALL.
ORA-12809: cannot set string_INSTANCES when
mounted in exclusive mode
Cause:
An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER
SYSTEM command while the database was mounted in exclusive mode.
Action:
SCAN_INSTANCES / CACHE_INSTANCES may not be set unless running Oracle Real
Application Clusters mounted in CLUSTER_DATABASE mode.
ORA-12810: PARALLEL_MAX_SERVERS must be less than
or equal to string
Cause:
An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value higher
than the maximum allowed by the system.
Action:
Set PARALLEL_MAX_SERVERS to a value less than or equal to the maximum specified
in the accompanying message and retry.
ORA-12811: PARALLEL_MIN_SERVERS must be less than
or equal to PARALLEL_MAX_SERVERS, string
Cause:
An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher
than PARALLEL_MAX_SERVERS.
Action:
Set PARALLEL_MIN_SERVERS to a value less than or equal to PARALLEL_MAX_SERVERS
(indicated in the accompanying message) and retry.
ORA-12812: only one PARALLEL or NOPARALLEL clause
may be specified
Cause:
PARALLEL was specified more than once, NOPARALLEL was specified more than once,
or both PARALLEL and NOPARALLEL were specified in a CREATE TABLE, CLUSTER, or
INDEX or in an ALTER TABLE or CLUSTER statement, or in a RECOVER command.
Action:
Remove all but one of the PARALLEL or NOPARALLEL clauses and reissue the
statement.
ORA-12813: value for PARALLEL or DEGREE must be
greater than 0
Cause:
PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER, or INDEX or in
an ALTER TABLE or CLUSTER statement.
Action:
Specify a degree of parallelism greater than 0 or specify default parallelism
using PARALLEL with no degree or using DEGREE DEFAULT within a PARALLEL clause.
ORA-12814: only one CACHE or NOCACHE clause may be
specified
Cause:
CACHE was specified more than once, NOCACHE was specified more than once, or
both CACHE and NOCACHE were specified in a CREATE TABLE or CLUSTER, or in an ALTER
TABLE or CLUSTER statement.
Action:
Remove all but one of the CACHE or NOCACHE clauses and reissue the statement.
ORA-12815: value for INSTANCES must be greater than
0
Cause:
PARALLEL parameter specifying number of instances must be a positive integer or
DEFAULT
Action:
specify a positive integer or DEFAULT for INSTANCES if parallelism across
instances is desired.
ORA-12817: parallel query option must be enabled
Cause:
A parallel query option feature has been invoked but this option has not been
enabled.
Action:
Enable the parallel query option.
ORA-12818: invalid option in PARALLEL clause
Cause:
an unrecognized option was used within a PARALLEL clause.
Action:
specify any combination of DEGREE { <n> | DEFAULT } and INSTANCES {
<n> | DEFAULT } within the PARALLEL clause.
ORA-12819: missing options in PARALLEL clause
Cause:
PARALLEL clause cannot be empty.
Action:
specify any combination of DEGREE { <n> | DEFAULT } and INSTANCES {
<n> | DEFAULT } within the PARALLEL clause.
ORA-12820: invalid value for DEGREE
Cause:
invalid value for DEGREE was specified within a PARALLEL clause.
Action:
specify a positive integer or DEFAULT for the DEGREE option within a PARALLEL
clause.
ORA-12821: invalid value for INSTANCES
Cause:
invalid value for INSTANCES was specified within a PARALLEL clause.
Action:
specify a positive integer or DEFAULT for the INSTANCES option within a
PARALLEL clause.
ORA-12822: duplicate option in PARALLEL clause
Cause:
DEGREE or INSTANCES was specified more than once within a PARALLEL clause.
Action:
specify each desired PARALLEL clause option only once.
ORA-12823: default degree of parallelism may not be
specified here
Cause:
the PARALLEL keyword was used alone or DEGREE DEFAULT was specified in the
PARALLEL clause of an ALTER DATABASE RECOVER command.
Action:
respecify with an explicit degree of parallelism.
ORA-12824: INSTANCES DEFAULT may not be specified
here
Cause:
INSTANCES DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE
RECOVER command
Action:
respecify with an explicit value for INSTANCES or omit the INSTANCES option if
single instance recovery is desired.
ORA-12825: explicit degree of parallelism must be
specified here
Cause:
the DEGREE option was omitted from an ALTER DATABASE RECOVER command.
Action:
respecify with an explicit degree of parallelism.
ORA-12826: hung parallel query server was killed
Cause:
parallel query server was hung and subsequently killed.
Action:
re-execute query and report suspicious events in trace file to Oracle Support
Services if error persists.
ORA-12827: insufficient parallel query slaves
available
Cause:
PARALLEL_MIN_PERCENT parameter was specified and fewer than minimum slaves were
acquired
Action:
either re-execute query with lower PARALLEL_MIN_PERCENT or wait until some
running queries are completed, thus freeing up slaves
ORA-12828: Can't start parallel transaction at a
remote site
Cause:
PDML transaction cannot be started because we are not in the coordinator site
of the distributed transaction.
Action:
Do not use PDML at remote sites.
ORA-12829: Deadlock - itls occupied by siblings at
block string of file string
Cause:
parallel statement failed because all itls in the current block are occupied by
siblings of the same transaction.
Action:
increase MAXTRANS of the block or reduce the degree of parallelism for the
statement. Reexecute the statement. Report suspicious events in trace file to
Oracle Support Services if error persists.
ORA-12830: Must COMMIT or ROLLBACK after executing
parallel INSERT/UPDATE/DELETE
Cause:
After executing a parallel INSERT/UPDATE/DELETE statement, a command other than
COMMIT or ROLLBACK was issued.
Action:
Execute COMMIT or ROLLBACK before issuing another SQL command.
ORA-12831: Must COMMIT or ROLLBACK after executing
INSERT with APPEND hint
Cause:
After executing an INSERT statement with an APPEND hint, a command other than
COMMIT or ROLLBACK was issued.
Action:
Execute COMMIT or ROLLBACK before issuing another SQL command.
ORA-12832: Could not allocate slaves on all
specified instances
Cause:
After executing a query on a global v$ fixed view, one or more instances failed
to allocate a slave to process query
Action:
To allow results to be returned by sucessfully allocated slaves, execute ALTER
SESSION SET ALLOW_PARTIAL_SN_RESULTS=TRUE statement, or check parameters of
instances
ORA-12833: Coordinator's instance not a member of
parallel_instance_group
Cause:
The coordinator's instance must be a member of the parallel_instance_group in
which this operation will be run.
Action:
Either add the coordinator's instance to the current parallel_instance_group or
change parallel_instance_group.
ORA-12834: Instance group name, 'string',
too long, must be less than string characters
Cause:
The instance group name is too long.
Action:
Either shorten the name or get rid of the instance group.
ORA-12835: No instances are active in the
GLOBAL_VIEW_ADMIN_GROUP
Cause:
There must be at least one instance in the GLOBAL_VIEW_ADMIN_GROUP in order to
execute a query on global views
Action:
Change the value of GLOBAL_VIEW_ADMIN_GROUP
ORA-12838: cannot read/modify an object after
modifying it in parallel
Cause:
Within the same transaction, an attempt was made to add read or modification
statements on a table after it had been modified in parallel or with direct
load. This is not permitted.
Action:
Rewrite the transaction, or break it up into two transactions: one containing
the initial modification and the second containing the parallel modification
operation.
ORA-12839: cannot modify an object in parallel
after modifying it
Cause:
Within the same transaction, an attempt was made to perform parallel
modification operations on a table after it had been modified. This is not
permitted.
Action:
Rewrite the transaction or break it up into two transactions: one containing
the parallel modification and the second containing the initial modification
operation.
ORA-12840: cannot access a remote table after
parallel/insert direct load txn
Cause:
Within a transaction, an attempt was made to perform distributed access after a
PDML or insert direct statement had been issued.
Action:
Commit/rollback the PDML transaction first, and then perform the distributed
access, or perform the distributed access before the first PDML statement in
the transaction.
ORA-12841: Cannot alter the session parallel DML
state within a transaction
Cause:
Transaction in progress
Action:
Commit or rollback transaction and then re-execute
ORA-12842: Cursor invalidated during parallel
execution
Cause:
The cursor was invalidated during the parse phase of deferred parallel
processing, e.g. when set operands are parallelized.
Action:
Depends on why the cursor was invalidated. Possible causes include DDL on a
schema object and shared pool being flushed.
ORA-12843: pdml lock not held properly on the table
Cause:
The coodinator crashed or released the lock on the partition which the slave is
trying to aquire currently.
Action:
Check if the coordinator or some of the other slaves died. Also check that the
lock has not been corrupted. Issue the pdml again.
ORA-12844: cluster reconfiguration in progress
Cause:
Internal error
Action:
THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR
DOCUMENTED. IT IS USED ONLY FOR INTERNAL ERROR.
ORA-12845: failed to receive interinstance parallel
execution message
Cause:
OS or interconnect problem receiving interinstance message
Action:
Check OS specific diagnostics
ORA-12850: Could not allocate slaves on all
specified instances: string needed, string allocated
Cause:
When executing a query on a gv$ fixed view, one or more instances failed to
allocate a slave to process query.
Action:
Check trace output for instances on which slaves failed to start. GV$ query can
only proceed if slaves can be allocated on all instances.
ORA-12851: PARALLEL_MAX_SERVERS must be greater
than or equal to PARALLEL_MIN_SERVERS, string
Cause:
An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value less
than PARALLEL_MIN_SERVERS.
Action:
Set PARALLEL_MAX_SERVERS to a value greater than or equal to
PARALLEL_MIN_SERVERS value specified in the accompanying message and retry.
ORA-12852: PARALLEL_MIN_SERVERS must be less than
PROCESSES, string
Cause:
An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher
than PROCESSES.
Action:
Set PARALLEL_MIN_SERVERS to a value less than PROCESSES value specified in the
accompanying message and retry.
ORA-12853: insufficient memory for PX buffers:
current stringK, max needed stringK
Cause:
Insufficient SGA memory for PX buffers
Action:
Reconfigure sga to include at least (max - current) bytes of additional memory
ORA-12854: Parallel query is not supported on
temporary LOBs
Cause:
The parallel query statement produced a temporary LOB.
Action:
Turn off parallelism for the query or underlying table
ORA-12855: cannot run parallel or insert direct
load in a loopback
Cause:
A loopback was created in the transaction before this operation.
Action:
Do not use loopback when using pdml or insert direct load.
ORA-12856: cannot run parallel query on a loopback
connection
Cause:
A table or index in a parallel query is referenced via a loopback connection.
Action:
Do not use loopback connection when running a query in parallel.
ORA-12872: First slave parse gave different plan
Cause:
First hard parse on slave given QC-supplied environment and parameters gave
different plan from QC. Try again with outline.
Action:
No external action. Internally used for outline-based reparse.
ORA-12899: value too large for column string
(actual: string, maximum: string)
Cause:
An attempt was made to insert or update a column with a value which is too wide
for the width of the destination column. The name of the column is given, along
with the actual width of the value, and the maximum allowed width of the column.
Note that widths are reported in characters if character length semantics are
in effect for the column, otherwise widths are reported in bytes.
Action:
Examine the SQL statement for correctness. Check source and destination column
data types. Either make the destination column wider, or use a subset of the
source column (i.e. use substring).
ORA-12900: must specify a default temporary
tablespace for a locally managed database
Cause:
a locally managed database must have a temporary tablespace other than SYSTEM
tablespace
Action:
specify the default temporary tablespace when creating a locally managed
database
ORA-12901: default temporary tablespace must be of
TEMPORARY type
Cause:
in a locally managed database, default temporary tablespace must be TEMPORARY
type
Action:
None
ORA-12902: default temporary tablespace must be
SYSTEM or of TEMPORARY type
Cause:
in a dictionary managed database, default temporary tablespace must be SYSTEM
or TEMPORARY type
Action:
None
ORA-12910: cannot specify temporary tablespace as
default tablespace
Cause:
attempt to assign a temporary tablespace to be a user's default tablespace
Action:
assign a permanent tablespace to be the default tablespace
ORA-12911: permanent tablespace cannot be temporary
tablespace
Cause:
attempt to assign a permanent tablespace to be a user's temporary tablespace
Action:
assign a temporary tablespace to be user's temporary tablespace
ORA-12912: Dictionary managed tablespace specified
as temporary tablespace
Cause:
attempt to assign a dictionary managed tablespace to be a user's temporary
tablespace
Action:
Assign a locally managed temporary tablespace to be user's temporary tablespace
ORA-12913: Cannot create dictionary managed
tablespace
Cause:
Attemp to create dictionary managed tablespace in database which has system
tablespace as locally managed
Action:
Create a locally managed tablespace.
ORA-12914: Cannot migrate tablespace to dictionary
managed type
Cause:
Attemp to migrate locally managed tablespace to dictionary managed type when
the database has locally managed system tablespace.
Action:
Command cannot be issued.
ORA-12915: Cannot alter dictionary managed
tablespace to read write
Cause:
Attemp to alter dictionary managed tablespace to read write in database which
has system tablespace as locally managed. This tablespace can only be dropped.
Action:
Command cannot be issued.
ORA-12916: cannot shrink permanent or dictionary
managed tablespace
Cause:
An attempt was made to shrink a permanent tablespace or a dictionary managed
tablespace.
Action:
Check the tablespace type and issue the statement only on locally managed
temporary tablespaces.
ORA-12918: Invalid tablespace type for default
permanent tablespace
Cause:
The tablespace is either dropped, temporary or undo
Action:
Check the tablespace type and reissue the statement
ORA-12919: Can not drop the default permanent
tablespace
Cause:
An attemp was made to drop the default permanent tablespace
Action:
Make a different tablespace as the default permanent tablespace and reissue the
drop
ORA-12920: database is already in force logging
mode
Cause:
ALTER DATABASE FORCE LOGGING command failed because the database is already in
force logging mode.
Action:
None
ORA-12921: database is not in force logging mode
Cause:
ALTER DATABASE NO FORCE LOGGING command failed because the database is not in
force logging mode.
Action:
None
ORA-12922: concurrent ALTER DATABASE [NO] FORCE
LOGGING command is running
Cause:
There is a concurrent ALTER DATABASE FORCE LOGGING or ALTER DATABASE NO FORCE
LOGGING command running in the system.
Action:
Contact the database administrator who is responsible for the concurrent
command.
ORA-12923: tablespace string is in force
logging mode
Cause:
An attempt to alter the specified tablespace temporary failed because the
tablespace is in force logging mode.
Action:
Put the tablespace out of force logging mode by ALTER TABLESPACE NO FORCE
LOGGING command.
ORA-12924: tablespace string is already in
force logging mode
Cause:
An attempt to alter the specified tablespace into force logging mode failed
because it is already in force logging mode.
Action:
None
ORA-12925: tablespace string is not in force
logging mode
Cause:
An attempt to alter the specified tablespace out of force logging mode failed
because it is not in force logging mode.
Action:
None
ORA-12926: FORCE LOGGING option already specified
Cause:
In CREATE TABLESPACE, the FORCE LOGGING option was specified more than once.
Action:
Remove all but one of the FORCE LOGGING options.
ORA-12927: RETENTION option already specified
Cause:
In CREATE TABLESPACE, the RETENTION option was specified more than once.
Action:
Remove all but one of the RETENTION options.
ORA-12928: ENCRYPTION option already specified
Cause:
In CREATE TABLESPACE, the ENCRYPTION option was specified more than once.
Action:
Remove all but one of the ENCRYPTION options.
ORA-12940: Not enough space in DBVerify text buffer
Cause:
DBVerify ran out of text buffer. The error was trapped internally by the
system. DBVerify would return the result in text buffer and then resume
checking.
Action:
None
ORA-12941: DBVerify exception
Cause:
DBVerify encountered run-time error. The error signal was trapped internally by
the system.
Action:
None
ORA-12950: SYSTEM tablespace specified as default
permanent tablespace
Cause:
SYSTEM tablespace was specified as the default permanent during database
creation.
Action:
If default permanent tablespace is not specified,then SYSTEM will implicitly
become the default permanent tablespace. Specify an alternate tablespace or
omit the default tablespace clause and reissue the CREATE DATABASE statement
ORA-12951: Attempt to change default permanent
tablespace to temporary
Cause:
It is incorrect to alter the default permanent tablespace of a database to temporary
type
Action:
None
ORA-12980: checkpoint option not allowed with SET
UNUSED
Cause:
An attempt was made to specify checkpoint option with SET UNUSED.
Action:
Remove checkpoint option.
ORA-12981: cannot drop column from an object type
table
Cause:
An attempt was made to drop a column from an object type table.
Action:
This action is not allowed.
ORA-12982: cannot drop column from a nested table
Cause:
An attempt was made to drop a column from a nested table.
Action:
This action is not allowed.
ORA-12983: cannot drop all columns in a table
Cause:
An attempt was made to drop all columns in a table.
Action:
Make sure at least one column remains in the table after the drop column
operation.
ORA-12984: cannot drop partitioning column
Cause:
An attempt was made to drop a column used as the partitioning key.
Action:
This action is not allowed.
ORA-12985: tablespace 'string' is read only,
cannot drop column
Cause:
An attempt was made to drop column from a partition/subpartition on a read only
tablespace.
Action:
Set the tablespace to read write and resubmit statement.
ORA-12986: columns in partially dropped state.
Submit ALTER TABLE DROP COLUMNS CONTINUE
Cause:
An attempt was made to access a table with columns in partially dropped state
(i.e., drop column operation was interrupted).
Action:
Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the drop column operation
before accessing the table.
ORA-12987: cannot combine drop column with other
operations
Cause:
An attempt was made to combine drop column with other ALTER TABLE operations.
Action:
Ensure that drop column is the sole operation specified in ALTER TABLE.
ORA-12988: cannot drop column from table owned by
SYS
Cause:
An attempt was made to drop a column from a system table.
Action:
This action is not allowed
ORA-12989: invalid value for checkpoint interval
Cause:
An invalid checkpoint interval specified in statement. Checkpoint interval must
be between 0 and (2^31-1).
Action:
Correct checkpoint interval and resubmit statement
ORA-12990: duplicate option specified
Cause:
Duplicate option specified in statement.
Action:
Remove the duplicate option and resubmit statement.
ORA-12991: column is referenced in a multi-column
constraint
Cause:
An attempt was made to drop a column referenced by some constraints.
Action:
Drop all constraints referencing the dropped column or specify CASCADE
CONSTRAINTS in statement.
ORA-12992: cannot drop parent key column
Cause:
An attempt was made to drop a parent key column.
Action:
Drop all constraints referencing the parent key column, or specify CASCADE
CONSTRAINTS in statement.
ORA-12993: tablespace 'string' is offline,
cannot drop column
Cause:
An attempt was made to drop a column from a partition/subpartition on an
offline tablespace.
Action:
Bring the tablespace online and resubmit statement.
ORA-12994: drop column option only allowed once in
statement
Cause:
An attempt was made to repeat the drop column option in a single statement.
Action:
Separate drop column options into different statements and resubmit statements.
ORA-12995: no columns in partially dropped state
Cause:
An attempt was made to submit DROP COLUMNS CONTINUE statement while there are
no partially dropped columns.
Action:
Cannot submit this statement.
ORA-12996: cannot drop system-generated virtual
column
Cause:
An attempt was made to drop a virtual column generated by the system.
Action:
None
ORA-12997: cannot drop primary key column from an
index-organized table
Cause:
An attempt was made to drop a primary key column from an index- organized
table.
Action:
This action is not allowed.
ORA-13000: dimension number is out of range
Cause:
The specified dimension is either smaller than 1 or greater than the number of
dimensions encoded in the HHCODE.
Action:
Make sure that the dimension number is between 1 and the maximum number of
dimensions encoded in the HHCODE.
ORA-13001: dimensions mismatch error
Cause:
The number of dimensions in two HHCODEs involved in a binary HHCODE operation
do not match.
Action:
Make sure that the number of dimensions in the HHCODEs match.
ORA-13002: specified level is out of range
Cause:
The specified level is either smaller than 1 or greater than the maximum level
encoded in an HHCODE.
Action:
Verify that all levels are between 1 and the maximum number of levels encoded
in the HHCODE.
ORA-13003: the specified range for a dimension is
invalid
Cause:
The specified range for a dimension is invalid.
Action:
Make sure that the lower bound (lb) is less than the upper bound (ub).
ORA-13004: the specified buffer size is invalid
Cause:
The buffer size for a function is not valid.
Action:
This is an internal error. Contact Oracle Support Services.
No hay comentarios:
Publicar un comentario