ORA-01940: cannot drop a user that is currently connected
Cause: Attempt was made to drop a user that is currently logged in.
Action: Make sure user is logged off, then repeat command.
ORA-01941: SEQUENCE keyword expected
Cause: keyword missing
Action: supply missing keyword
ORA-01942: IDENTIFIED BY and EXTERNALLY cannot both be specified
Cause: A user cannot be specified to have and not have a password.
Action: Specify only one of the options.
ORA-01943: IDENTIFIED BY already specified
Cause: The identified clause has been given twice.
Action: Use only one identified by clause.
ORA-01944: IDENTIFIED EXTERNALLY already specified
Cause: The identified externaly clause has been given twice.
Action: Use only one identified clause.
ORA-01945: DEFAULT ROLE[S] already specified
Cause: The default roles clause has been given twice.
Action: Use only on default role clause.
ORA-01946: DEFAULT TABLESPACE already specified
Cause: The default tablespace clause has been given twice.
Action: Use only one default tablespace clause.
ORA-01947: TEMPORARY TABLESPACE already specified
Cause: The temporary tablespace clause has been given twice.
Action: Use only one temporary tablespace clause.
ORA-01948: identifier's name length (string) exceeds maximum (string)
Cause: A name has been specified that is too long. For example, dbms_session.is_role_enabled() specifies a role name that is too long.
Action: Change the application or command to use a correct identifier.
ORA-01949: ROLE keyword expected
Cause: The role keyword is required here.
Action: Specify the role keyword.
ORA-01950: no privileges on tablespace 'string'
Cause: User does not have privileges to allocate an extent in the specified tablespace.
Action: Grant the user the appropriate system privileges or grant the user space resource on the tablespace.
ORA-01951: ROLE 'string' not granted to 'string'
Cause: The role you tried to revoke was not granted to the user.
Action: Don't try to revoke a privilege which is not granted.
ORA-01952: system privileges not granted to 'string'
Cause: A system privilege you tried to revoke was not granted to the user.
Action: Make sure the privileges you are trying to revoke are granted.
ORA-01953: command no longer valid, see ALTER USER
Cause: The syntax for assigning quotas on tablespaces has changed. The ALTER USER command is now used to perform the functionality
Action: Use the alter user command instead.
ORA-01954: DEFAULT ROLE clause not valid for CREATE USER
Cause: Default roles cannot be specified for create user.
Action: Grant and alter the user's default roles after creating the user.
ORA-01955: DEFAULT ROLE 'string' not granted to user
Cause: The user being altered does not have the specified role granted directly to the user. Note, sub-roles cannot be used in the default role clause.
Action: Grant the role to the user.
ORA-01956: invalid command when OS_ROLES are being used
Cause: This command cannot be used when the INIT.ORA parameter OS_ROLES is TRUE.
Action: Grant the role to the user in the operating system.
ORA-01967: invalid option for CREATE CONTROLFILE
Cause: An invalid CREATE CONTROLFILE option is present.
Action: Specify only valid CREATE CONTROLFILE options.
ORA-01968: Only specify RESETLOGS or NORESETLOGS once
Cause: The keyword RESETLOGS or NORESETLOGS has appeared more than once
Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once.
ORA-01969: You must specify RESETLOGS or NORESETLOGS
Cause: Missing a RESETLOGS or a NORESETLOGS
Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once.
ORA-01970: You must specify a database name for CREATE CONTROLFILE
Cause: Missing a database name
Action: Retype CREATE CONTROLFILE command with the DATABASE keyword.
ORA-01973: Missing change number
Cause: Keyword "CHANGE" found but change number not specified.
Action: Fix command line and resubmit
ORA-01974: Illegal archive option
Cause: Not a valid option to the "ALTER SYSTEM ARCHIVE" command
Action: None
ORA-01977: Missing thread number
Cause: Keyword "THREAD" found but thread number not specified.
Action: Fix command line and resubmit
ORA-01978: Missing sequence number
Cause: Keyword "SEQUENCE" found but sequence number not specified.
Action: Fix command line and resubmit
ORA-01979: missing or invalid password for role 'string'
Cause: An attempt was made to enable a role without giving
Action: Use the "identified by" clause in set role to specify the correct password.
ORA-01980: error during OS ROLE initialization
Cause: An OS error occurred while loading a users OS ROLES.
Action: Check the OS error.
ORA-01981: CASCADE CONSTRAINTS must be specified to perform this revoke
Cause: During this revoke some foreign key contraints will be removed. In order to perform this automatically, CASCADE CONSTRAINTS must be specified.
Action: Remove the constraints or specify CASCADE CONSTRAINTS.
ORA-01982: invalid auditing option for tables
Cause: AUDIT or NOAUDIT on a table specifies an auditing option that is not legal for tables.
Action: The following options may not be used for tables and should be removed: REFERENCES, EXECUTE
ORA-01983: invalid auditing option for DEFAULT
Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not legal for DEFAULT.
Action: The following options may not be used for DEFAULT and should be removed: REFERENCES
ORA-01984: invalid auditing option for procedures/packages/functions
Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not legal for procedures, packages, or functions.
Action: The following options may not be used for procedures, packages, and functions and should be removed: all but EXECUTE
ORA-01985: cannot create user as LICENSE_MAX_USERS parameter exceeded
Cause: Maximum users in the database license limit exceeded.
Action: Increase license limit.
ORA-01986: OPTIMIZER_GOAL is obsolete
Cause: An obsolete parameter, OPTIMIZER_GOAL, was referenced.
Action: Use the OPTIMIZER_MODE parameter.
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.
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-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-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-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-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-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-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-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-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-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 tablename@remotedbname ...".
Action: To alter the remote database structure, you must connect to the remote database with the appropriate privileges.
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 view@remote.
ORA-02024: database link not found
Cause: Database link to be dropped is not found in dictionary
Action: Correct the database link name
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-02026: missing LINK keyword
Cause: keyword missing
Action: supply missing keyword
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-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-02029: missing FILE keyword
Cause: keyword missing
Action: supply missing keyword
ORA-02030: can only select from fixed tables/views
Cause: An attempt is being made to perform an operation other than a retrieval from a fixed table/view.
Action: You may only select rows from fixed tables/views.
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-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-02033: a cluster index for this cluster already exists
Cause: A cluster index already exists for the cluster.
Action: None
ORA-02034: speed bind not permitted
Cause: Speed bind not allowed with supplied bind variables. Trapped internally by the system.
Action: None
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-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-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-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-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-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-02041: client database did not begin a transaction
Cause: internal error
Action: contact support
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/restart would be a work-around.
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-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-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-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-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-02048: attempt to begin distributed transaction without logging on
Cause: client program must issue a distributed transaction login.
Action: contact support.
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-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-02051: another session in same transaction failed
Cause: a session at the same site with same global transaction ID failed; It can also be caused by application error if an attempt was made to update database while another tightly coupled transaction branch with same global transaction ID has been finalized.
Action: none necessary, transaction automatically recovered. In case of application error, make sure no more updates to database once transaction manager has started two-phase commit for tightly coupled distributed transaction.
ORA-02052: remote transaction failure at string
Cause: error in remote transaction at given DBLINK
Action: retry
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-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-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-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-02057: 2PC: string: bad two-phase recovery state number string from string
Cause: internal error in two-phase recovery protocol
Action: contact support
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-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-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-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-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-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-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-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-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-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-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-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-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-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-02072: distributed database network protocol mismatch
Cause: This should never happen between different PRODUCTION releases of ORACLE, but may happen between alpha and beta releases, for example.
Action: Upgrade the older release.
ORA-02073: sequence numbers not supported in remote updates
Cause: Sequence numbers may not be used in INSERTS, UPDATES, or DELETES on remote tables.
Action: None
ORA-02074: cannot string in a distributed transaction
Cause: A commit or rollback was attempted from session other than the parent of a distributed transaction.
Action: Only commit or rollback from the parent session.
ORA-02075: another instance changed state of transaction string
Cause: A commit force or rollback force was issued from a session in another instance.
Action: Check if another Oracle instance is performing recovery of pending transactions. Query DBA_2PC_PENDING to determine the new state of the transaction.
ORA-02076: sequence not co-located with updated table or long column
Cause: all referenced sequences must be co-located with the table with the long column.
Action: None
ORA-02077: selects of long columns must be from co-located tables
Cause: if a select returns long columns from multiple tables, all the tables must be co-located
Action: None
ORA-02079: cannot join a committing distributed transaction
Cause: Once a transaction branch is prepared, no more new transaction branches are allowed to start, nor is the prepared transaction branch allowed to be joined.
Action: Check the application code as this is an XA protocol violation.
ORA-02080: database link is in use
Cause: a transaction is active or a cursor is open on the database link given in the alter session close database link <link> command.
Action: commit or rollback, and close all cursors
ORA-02081: database link is not open
Cause: dblink given is not currently open.
Action: None
ORA-02082: a loopback database link must have a connection qualifier
Cause: attempt to create a database link with the same name as the current database.
Action: a loopback database link needs a trailing qualifier, e.g. MYDB.DEV.US.ORACLE.COM@INST1 - the '@INST1' is the qualifier
ORA-02083: database name has illegal character 'string'
Cause: supplied database name can contain only A-Z, 0-9, '_', '#', '$' '.' and '@' characters.
Action: None
ORA-02084: database name is missing a component
Cause: supplied database name cannot contain a leading '.', trailing '.' or '@', or two '.' or '@' in a row.
Action: None
ORA-02085: database link string connects to string
Cause: a database link connected to a database with a different name. The connection is rejected.
Action: create a database link with the same name as the database it connects to, or set global_names=false.
ORA-02086: database (link) name is too long
Cause: database/database link name can have at most 128 characters.
Action: None
ORA-02087: object locked by another process in same transaction
Cause: A database link is being used in the cluster database environment that loops back to the same instance. One session is trying to convert a lock that was obtained by the other session.
Action: Get the more restrictive lock first. For example, if session 1 gets a share lock and session 2 gets an exclusive lock on the same object, get the exclusive lock first. Or, simply use the same session to access the object.
ORA-02088: distributed database option not installed
Cause: Remote and distributed updates and transactions are a separately priced option in ORACLE V7.
Action: None
ORA-02089: COMMIT is not allowed in a subordinate session
Cause: COMMIT was issued in a session that is not the two-phase commit global coordinator.
Action: Issue commit at the global coordinator only.
ORA-02090: network error: attempted callback+passthru
Cause: internal error.
Action: None
ORA-02091: transaction rolled back
Cause: Also see error 2092. If the transaction is aborted at a remote site then you will only see 2091; if aborted at host then you will see 2092 and 2091.
Action: Add rollback segment and retry the transaction.
ORA-02092: out of transaction table slots for distributed transaction
Cause: The transaction is assigned to the system rollback segment and is trying to get into the PREPARED state, but the required number of non-PREPARED slots are not available, hence the transaction is rolled back.
Action: Add a rollback segment and retry the transaction.
ORA-02093: TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) more than maximum possible(string)
Cause: Value of parameter specified is greater than allowed on this port.
Action: Use default or reduce it to less than max.
No hay comentarios:
Publicar un comentario