Saturday 21 January 2012

ORA-02071: error initializing capabilities for remote database string

ORA-02071: error initializing capabilities for remote database string

Cause: Could not load a remote-specified capability table.

Action: Contact support for the remote SQL*Connect product.

ORA-02070: database stringstring does not support string in this context

ORA-02070: database stringstring does not support string in this context

Cause: The remote database does not support the named capability in the context in which it is used.

Action: Simplify the SQL statement.

ORA-02069: global_names parameter must be set to TRUE for this operation

ORA-02069: global_names parameter must be set to TRUE for this operation

Cause: A remote mapping of the statement is required but cannot be achieved because global_names should be set to TRUE for it to be achieved

Action: Issue alter session set global_names = true if possible

ORA-02068: following severe error from stringstring

ORA-02068: following severe error from stringstring

Cause: A severe error (disconnect, fatal Oracle error) received from the indicated database link. See following error text.

Action: Contact the remote system administrator.

ORA-02067: transaction or savepoint rollback required

ORA-02067: transaction or savepoint rollback required

Cause: A failure (typically a trigger or stored procedure with multiple remote updates) occurred such that the all-or-nothing execution of a previous Oracle call cannot be guaranteed.

Action: rollback to a previous savepoint or rollback the transaction and resubmit.

ORA-02066: missing or invalid DISPATCHERS text

ORA-02066: missing or invalid DISPATCHERS text

Cause: A character string literal was expected, but not found, following ALTER SYSTEM SET DISPATCHERS

Action: place the string literal containing the dispatcher s specification after ALTER SYSTEM SET DISPATCHERS

ORA-02065: illegal option for ALTER SYSTEM

ORA-02065: illegal option for ALTER SYSTEM

Cause: The option specified for ALTER SYSTEM is not supported

Action: refer to the user manual for option supported

ORA-02064: distributed operation not supported

ORA-02064: distributed operation not supported

Cause: One of the following unsupported operations was attempted: 1. array execute of a remote update with a subquery that references a dblink, or 2. an update of a long column with bind variable and an update of a second column with a subquery that both references a dblink and a bind variable, or 3. a commit is issued in a coordinated session from an RPC procedure call with OUT parameters or function call.

Action: simplify remote update statement

ORA-02063: preceding stringstring from stringstring

ORA-02063: preceding stringstring from stringstring

Cause: an Oracle error was received from a remote database link.

Action: refer to the preceding error message(s)

ORA-02062: distributed recovery received DBID string, expected string

ORA-02062: distributed recovery received DBID string, expected string

Cause: a database link at a coordinator no longer points to the expected database. Link may have been redefined, or a different DB mounted.

Action: restore link definition or remote database.

ORA-02061: lock table specified list of distributed tables

ORA-02061: lock table specified list of distributed tables

Cause: tables in a lock table statement must reside at the same DB.

Action: issue multiple lock table commands.

ORA-02060: select for update specified a join of distributed tables

ORA-02060: select for update specified a join of distributed tables

Cause: tables in a join with the for update clause must reside at the same DB.

Action: none

ORA-02059: ORA-2PC-CRASH-TEST-string in commit comment

ORA-02059: ORA-2PC-CRASH-TEST-string in commit comment

Cause: This is a special comment used to test the two phase commit.

Action: Don t use this special comment (%s a number 1-10)

ORA-02058: no prepared transaction found with ID string

ORA-02058: no prepared transaction found with ID string

Cause: no transaction with local_tran_id or global_tran_id found in the pending_ trans$ table in prepared state.

Action: check the pending_trans$ table.

ORA-02057: 2PC: string: bad two-phase recovery state number string from string

ORA-02057: 2PC: string: bad two-phase recovery state number string from string

Cause: internal error in two-phase recovery protocol

Action: contact support

ORA-02056: 2PC: string: bad two-phase command number string from string

ORA-02056: 2PC: string: bad two-phase command number string from string

Cause: two-phase commit protocol error.

Action: recovery of transaction attempted. Monitor pending_trans$ table to ensure correct resolution. Contact support.

ORA-02055: distributed update operation failed; rollback required

ORA-02055: distributed update operation failed; rollback required

Cause: a failure during distributed update operation may not have rolled back all effects of the operation. Since some sites may be inconsistent, the transaction must roll back to a savepoint or entirely

Action: rollback to a savepoint or rollback transaction and resubmit

ORA-02054: transaction string in-doubt

ORA-02054: transaction string in-doubt

Cause: network or remote failure in 2PC.

Action: Notify operations; DBs will automatically re-sync when the failure is repaired. Monitor pending_trans$ for final outcome.

ORA-02053: transaction string committed, some remote DBs may be in-doubt

ORA-02053: transaction string committed, some remote DBs may be in-doubt

Cause: network or remote failure in 2PC.

Action: Notify operations; remote DBs will automatically re-sync when the failure is repaired.

ORA-02052: remote transaction failure at string

ORA-02052: remote transaction failure at string

Cause: error in remote transaction at given DBLINK

Action: retry

ORA-02051: another session in same transaction failed

ORA-02051: another session in same transaction failed

Cause: a session at the same site with same global transaction ID failed.

Action: none necessary, transaction automatically recovered.

ORA-02050: transaction string rolled back, some remote DBs may be in-doubt

ORA-02050: transaction string rolled back, some remote DBs may be in-doubt

Cause: network or remote failure in 2PC.

Action: Notify operations; remote DBs will automatically re-sync when the failure is repaired.

ORA-02049: timeout: distributed transaction waiting for lock

ORA-02049: timeout: distributed transaction waiting for lock

Cause: exceeded INIT.ORA distributed_lock_timeout seconds waiting for lock.

Action: treat as a deadlock

ORA-02048: attempt to begin distributed transaction without logging on

ORA-02048: attempt to begin distributed transaction without logging on

Cause: client program must issue a distributed transaction login.

Action: contact support.

ORA-02047: cannot join the distributed transaction in progress

ORA-02047: cannot join the distributed transaction in progress

Cause: Either a transaction is in progress against a remote database that does not fully support two phase commit, and an update is attempted on another database, or updates are pending and and an attempt is made to update a different database that does not fully support two phase commit.

Action: complete the current transaction and then resubmit the update request.

ORA-02046: distributed transaction already begun

ORA-02046: distributed transaction already begun

Cause: internal error or error in external transaction manager. A server session received a begin_tran RPC before finishing with a previous distributed tran.

Action: none

ORA-02045: too many local sessions participating in global transaction

ORA-02045: too many local sessions participating in global transaction

Cause: too many sessions at this site for this transaction.

Action: use an existing link so another session need not be created.

ORA-02044: transaction manager login denied: transaction in progress

ORA-02044: transaction manager login denied: transaction in progress

Cause: a remote transaction manager tried to log in while a distributed transaction is in progress.

Action: end the current transaction (this is a protocol error from a remote transaction manager)

ORA-02043: must end current transaction before executing string

ORA-02043: must end current transaction before executing string

Cause: a transaction is in progress and one of the following commands commands is issued: COMMIT FORCE, ROLLBACK FORCE, or ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY in single process mode.

Action: COMMIT or ROLLBACK the current transaction and resubmit command.

ORA-02042: too many distributed transactions

ORA-02042: too many distributed transactions

Cause: the distributed transaction table was full because too many distributed transactions were active.

Action: Run fewer transactions. If you are sure you don t have too many concurrent distributed transactions, this indicates an internal error and support should be notified. Instance shutdown or restart would be a work-around.

ORA-02041: client database did not begin a transaction

ORA-02041: client database did not begin a transaction

Cause: internal error

Action: contact support

ORA-02040: remote database string does not support two-phase commit

ORA-02040: remote database string does not support two-phase commit

Cause: the database was potentially updated but does not support prepare to commit (as determined by its logon transaction traits). The transaction was rolled back.

Action: Do not attempt to update the remote database unless it is the only database updated in one transaction.

ORA-02039: bind by value is not allowed for array type

ORA-02039: bind by value is not allowed for array type

Cause: User attempted to bind an array host variable by value. Arrays may only be bound by reference.

Action: none

ORA-02038: define is not allowed for array type

ORA-02038: define is not allowed for array type

Cause: User attempted to define a select list variable of type array . Arrays may only serve as host bind variables.

Action: none

ORA-02037: uninitialized speed bind storage

ORA-02037: uninitialized speed bind storage

Cause: User attempted a UPI bundled execution call containing a standalone execute operation without first performing a UPI bundled execution call containing a bind operation.

Action: perform a UPI bundled execution call with bind before performing a bundled execution call with execute

ORA-02036: too many variables to describe with automatic cursor open

ORA-02036: too many variables to describe with automatic cursor open

Cause: User requested that the UPI bundled execution call perform automatic cursor open and close on a describe operation. There were too many select-list items or bind variables to do this.

Action: open and close cursor explicitly

ORA-02035: illegal bundled operation combination

ORA-02035: illegal bundled operation combination

Cause: User requested that the UPI bundled execution call perform an an illegal combination of operations.

Action: See documentation for legal operation combinations.

ORA-02034: speed bind not permitted

ORA-02034: speed bind not permitted

Cause: Speed bind not allowed with supplied bind variables. Trapped internally by the system.

Action: none

ORA-02033: a cluster index for this cluster already exists

ORA-02033: a cluster index for this cluster already exists

Cause: A cluster index already exists for the cluster.

Action: None.

ORA-02032: clustered tables cannot be used before the cluster index is built

ORA-02032: clustered tables cannot be used before the cluster index is built

Cause: User attempted to perform a DML statement on a clustered table for which no cluster index has yet been created.

Action: Create the cluster index.

ORA-02031: no ROWID for fixed tables or for external-organized tables

ORA-02031: no ROWID for fixed tables or for external-organized tables

Cause: An attempt is being made to access rowid from a fixed table or from a external-organized table.

Action: Do not access ROWID from a fixed table or from a external-organized table.

ORA-02030: can only select from fixed tables or views

ORA-02030: can only select from fixed tables or views

Cause: An attempt is being made to perform an operation other than a retrieval from a fixed table or view.

Action: You may only select rows from fixed tables or views.

ORA-02029: missing FILE keyword

ORA-02029: missing FILE keyword

Cause: keyword missing

Action: supply missing keyword

ORA-02028: fetching an exact number of rows is not supported by the server

ORA-02028: fetching an exact number of rows is not supported by the server

Cause: The server does not support UPIALL, so the fetch of an exact number of rows cannot be emulated on the user side.

Action: Connect to a valid server or do not use an exact fetch.

ORA-02027: multi-row UPDATE of LONG column is not supported

ORA-02027: multi-row UPDATE of LONG column is not supported

Cause: A bind variable with length greater than 4000 bytes is being used to update a column, and the update statement updates more than one row.

Action: You may only update a single row with such a bind variable.

ORA-02026: missing LINK keyword

ORA-02026: missing LINK keyword

Cause: keyword missing

Action: supply missing keyword

ORA-02025: all tables in the SQL statement must be at the remote database

ORA-02025: all tables in the SQL statement must be at the remote database

Cause: The user s SQL statement references tables from multiple databases. The remote database is not Oracle V7 or above, and can perform updates only if it can reference all tables in the SQL statement.

Action: none

ORA-02024: database link not found

ORA-02024: database link not found

Cause: Database link to be dropped is not found in dictionary

Action: Correct the database link name

ORA-02022: remote statement has unoptimized view with remote object

ORA-02022: remote statement has unoptimized view with remote object

Cause: The local view is unoptimized and contains references to objects at the remote database and the statement must be executed at the remote database.

Action: Create a similar view on the remote database and modify the violating view in the SQL statement with the new viewremote.

ORA-02021: DDL operations are not allowed on a remote database

ORA-02021: DDL operations are not allowed on a remote database

Cause: An attempt was made to use a DDL operation on a remote database. For example, CREATE TABLE tablenameremotedbname ... .

Action: To alter the remote database structure, you must connect to the remote database with the appropriate privileges.

ORA-02020: too many database links in use

ORA-02020: too many database links in use

Cause: The current session has exceeded the INIT.ORA open_links maximum.

Action: Increase the open_links limit, or free up some open links by committing or rolling back the transaction and canceling open cursors that reference remote databases.

ORA-02009: the size specified for a file must not be zero

ORA-02009: the size specified for a file must not be zero

Cause: A value of zero was specified in a SIZE or RESIZE clause of a file specification.

Action: Use correct syntax, or, if allowed, omit the SIZE or RESIZE clause.

ORA-02007: can t use ALLOCATE or DEALLOCATE options with REBUILD

ORA-02007: can t use ALLOCATE or DEALLOCATE options with REBUILD

Cause: Allocate or deallocate storage and rebuild index are not compatible.

Action: Choose one or the other.

ORA-02004: security violation

ORA-02004: security violation

Cause: This error code is never returned to a user. It is used as a value for column, audit_trail.returncode, to signal that a security violation occurred.

Action: None.

ORA-02001: user SYS is not permitted to create indexes with freelist groups

ORA-02001: user SYS is not permitted to create indexes with freelist groups

Cause: user tried to create an index while running with sys authorization.

Action: none

ORA-01999: password file cannot be updated in SHARED mode

ORA-01999: password file cannot be updated in SHARED mode

Cause: The operation failed because the INIT.ORA parameter REMOTE_LOGIN_ PASSWORDFILE was set to SHARED.

Action: Set the INIT.ORA parameter to EXCLUSIVE.

ORA-01994: GRANT failed: password file missing or disabled

ORA-01994: GRANT failed: password file missing or disabled

Cause: The operation failed either because the INIT.ORA parameter REMOTE_ LOGIN_PASSWORDFILE was set to NONE or else because the password file was missing.

Action: Create the password file using the orapwd tool and set the INIT.ORA parameter REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE.

ORA-01989: role string not authorized by operating system

ORA-01989: role string not authorized by operating system

Cause: The os role does not exist, is not granted to you, or you did not provide the correct password.

Action: Re-attempt the SET ROLE with a valid os role and password, if necessary.

ORA-01988: remote os logon is not allowed

ORA-01988: remote os logon is not allowed

Cause: Remote os login attempted when not allowed.

Action: Use a local client, or use the remote_os_authent system parameter to turn on remote os logon.

ORA-01987: client os username is too long

ORA-01987: client os username is too long

Cause: A client s os username is too long for the os logon to succeed.

Action: Use a shorter os username.