Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 12800-12849: Parallel Query/Index Creation Messages

This section lists some of the messages generated during a parallel query or parallel index creation.

##### ORA-12800: system appears too busy for parallel query execution

Cause: The load on the system is too high to perform parallel queries.

Action: Re-enter the statements serially or wait until the system load is reduced.

##### ORA-12801: error signaled in parallel query server name

Cause: A parallel query server encountered an exception as described in the accompanying message(s).

Action: Correct the error described in the accompanying message.

##### ORA-12802: parallel query server lost contact with coordinator

Cause: A parallel query server was unable to communicate with the server coordinating the parallel query.

Action: Check for operating system or network errors and retry the statement. If this problem persists, contact customer support.

##### ORA-12803: parallel query server lost contact with another server

Cause: A parallel query server was unable to communicate with another server involved in the parallel query.

Action: Check for operating system or network errors and retry the statement. If this problem persists, contact customer support.

##### ORA-12804: parallel query server appears to have died

Cause: Process information for a parallel query server thread cannot be found.

Action: Check for operating system errors and retry the statement. If this problem persists, contact customer support.

##### ORA-12805: parallel query server died unexpectedly

Cause: The PMON process is cleaning up the process because a parallel query server terminated unexpectedly.

Action: Check for operating system errors and retry the statement. If this problem persists, contact customer support.

##### ORA-12806: could not get background process to hold enqueue

Cause: This is an internal error that is not usually issued.

Action: Contact customer support.

##### ORA-12807: process queue could not receive parallel query message

Cause: This is an internal error that is not usually issued.

Action: Contact customer support.

##### ORA-12808: cannot set [CACHE | SCAN]_INSTANCES greater than number of instances num

Cause: An attempt was made, using the ALTER SYSTEM command, to set CACHE_INSTANCES or SCAN_INSTANCES to a value greater than the number of available instances.

Action: See the accompanying message for the allowable maximum value or set SCAN_INSTANCES or CACHE_INSTANCES to ALL.

##### ORA-12809: cannot set [CACHE | SCAN]_INSTANCES when mounted in exclusive mode

Cause: An attempt was made to set CACHE_INSTANCES or SCAN_INSTANCES using the ALTER SYSTEM command while the database was mounted in exclusive mode.

Action: Only set CACHE_INSTANCES or SCAN_INSTANCES when the database is mounted in PARALLEL or SHARED mode.

##### ORA-12810: PARALLEL_MAX_SERVERS must be less than or equal to num

Cause: An attempt was made to set the PARALLEL_MAX_SERVERS initialization parameter to a value higher than the maximum allowed by the system.

Action: See the accompanying message for the allowable maximum value.

##### ORA-12811: PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, num

Cause: An attempt was made to set the PARALLEL_WIN_SERVERS initialization parameter to a value higher than PARALLEL_MAX_SERVERS.

Action: See the accompanying message for the allowable maximum value.

##### 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, CREATE CLUSTER, CREATE INDEX, ALTER TABLE, ALTER CLUSTER statement, or a RECOVER command.

Action: Specify PARALLEL or NOPARALLEL only once.

##### ORA-12813: value for PARALLEL or DEGREE must be greater than 0

Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CREATE CLUSTER, CREATE INDEX, ALTER TABLE, ALTER CLUSTER statement, or a RECOVER command.

Action: Specify a value 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 CACHE and NOCACHE, were specified in a CREATE TABLE, CREATE CLUSTER, CREATE INDEX, ALTER TABLE, ALTER CLUSTER, or a RECOVER command.

Action: Specify CACHE or NOCACHE only once.

##### 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: You tried to attempt an operation that requires the parallel query option.

Action: Enable the parallel query option.

##### ORA-12818: invalid option in PARALLEL clause

Cause: An unrecognized option was specified with a PARALLEL clause.

Action: Specify any combination of DEGREE {<n> | DEFAULT } and INSTANCE { <n> | DEFAULT } within the PARALLEL clause.

##### ORA-12819: missing options in PARALLEL clause

Cause: The PARALLEL clause was specified without an option.

Action: Specify any combination of DEGREE { <n> | DEFAULT } and INSTANCE { <n> | DEFAULT } within the PARALLEL clause.

##### ORA-12820: invalid value for DEGREE

Cause: An invalid value for DEGREE was specified within a PARALLEL clause.

Action: Specify a positive integer or DEFAULT.

##### ORA-12821: invalid value for INSTANCES

Cause: An invalid value for INSTANCES was specified within a PARALLEL clause.

Action: Specify a positive integer or DEFAULT.

##### ORA-12822: duplicate option in PARALLEL clause

Cause: DEGREE or INSTANCE was specified more than once within a PARALLEL clause.

Action: Specify the option only once.

##### ORA-12823: default degree of parallelism may not be specified here

Cause: Either an ALTER DATABASE RECOVER command was specified with the DEGREE DEFAULT option in a PARALLEL clause or another command was specified with no option in the PARALLEL clause.

Action: Specify an explicit degree of parallelism.

##### ORA-12824: INSTANCES DEFAULT may not be specified here

Cause: An ALTER DATABASE RECOVER command was specified with the INSTANCES DEFAULT option.

Action: Specify 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: An ALTER DATABASE RECOVER command was specified without the DEGREE option.

Action: Specify 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 noted in the trace file to customer support 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.

  For more information about the PARALLEL_MIN_PERCENT parameter, see the index entry on "PARALLEL_MIN_PERCENT parameter" in Oracle8 Server SQL Reference.

##### ORA-12828: can't start parallel transaction - distributed transaction in progress

Cause: PDML transaction cannot be started because a distributed transaction is in progress.

Action: Change the DML statement to exclude updates to remote tables and reexecute the statement.

##### ORA-12829: deadlock - itls occupied by siblings at block name of file name

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 representative 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, name, too long, must be less than num 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 OPS_ADMIN_GROUP

Cause: There must be at least one instance in the OPS_ADMIN_GROUP in order to execute a query on global views.

Action: Change the value of OPS_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 remote table in a parallel transaction

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: An attempt was made to alter the session parallel DML state while a transaction was in progress.

Action: Commit or rollback transaction and then re-execute.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index