Oracle Error Messages: 01/22/12

Sunday 22 January 2012

ORA-02176: invalid option for CREATE ROLLBACK SEGMENT

ORA-02176: invalid option for CREATE ROLLBACK SEGMENT

Cause: An invalid option was specified in a CREATE ROLLBACK SEGMENT statement.

Action: Specify one of the valid options: TABLESPACE and STORAGE.

ORA-02175: invalid rollback segment name

ORA-02175: invalid rollback segment name

Cause: In the CREATE or DROP ROLLBACK SEGMENT statements, an identifier was not found following ROLLBACK SEGMENT.

Action: Place the segment name following ROLLBACK SEGMENT.

ORA-02174: Missing required thread number

ORA-02174: Missing required thread number

Cause: Must specify thread number after THREAD keyword

Action: none

ORA-02173: invalid option for DROP TABLESPACE

ORA-02173: invalid option for DROP TABLESPACE

Cause: Either a token other than INCLUDING was found following the tablespace name or some text was found following INCLUDING CONTENTS.

Action: Place nothing or only INCLUDING CONTENTS after the tablespace name.

ORA-02172: The PUBLIC keyword is not appropriate for a disable thread

ORA-02172: The PUBLIC keyword is not appropriate for a disable thread

Cause: The PUBLIC keyword was specified for a disable.

Action: Remove the keyword and resubmit.

ORA-02171: invalid value for MAXLOGHISTORY

ORA-02171: invalid value for MAXLOGHISTORY

Cause: A number does not follow MAXLOGHISTORY

Action: Specify a number after MAXLOGHISTORY

ORA-02170: FREELIST GROUPS storage option not allowed

ORA-02170: FREELIST GROUPS storage option not allowed

Cause: The user attempted to specify the FREELIST GROUPS storage option. This option may only be specified during create table and when allow_freelist_groups INIT.ORA is specified.

Action: Remove this option and retry the statement or set the allow_freelist_ groups INIT.ORA parameter.

ORA-02169: FREELISTS storage option not allowed

ORA-02169: FREELISTS storage option not allowed

Cause: The user attempted to specify the FREELISTS storage option. This option may only be specified during create table or create index.

Action: Remove these options and retry the statement.

ORA-02168: invalid value for FREELISTS

ORA-02168: invalid value for FREELISTS

Cause: A number does not follow FREELISTS

Action: Specify a number after FREELISTS

ORA-02167: LOGFILE clause specified more than once

ORA-02167: LOGFILE clause specified more than once

Cause: The CREATE DATABASE command contains more than one LOGFILE clause.

Action: Specify at most one LOGFILE clause.

ORA-02166: ARCHIVELOG and NOARCHIVELOG specified

ORA-02166: ARCHIVELOG and NOARCHIVELOG specified

Cause: Both ARCHIVELOG and NOARCHIVELOG are specified in a CREATE DATABASE statement.

Action: Specify at most one of these two options.

ORA-02165: invalid option for CREATE DATABASE

ORA-02165: invalid option for CREATE DATABASE

Cause: An invalid CREATE DATABASE option is present.

Action: Specify only valid CREATE DATABASE options.

ORA-02164: DATAFILE clause specified more than once

ORA-02164: DATAFILE clause specified more than once

Cause: The CREATE DATABASE command contains more than one DATAFILE clause.

Action: Specify at most one DATAFILE clause.

ORA-02163: invalid value for FREELIST GROUPS

ORA-02163: invalid value for FREELIST GROUPS

Cause: A number does not follow FREELIST GROUPS.

Action: Specify a number after FREELIST GROUPS.

ORA-02162: invalid value for MAXDATAFILES

ORA-02162: invalid value for MAXDATAFILES

Cause: A number does not follow MAXDATAFILES.

Action: Specify a number after MAXDATAFILES.

ORA-02161: invalid value for MAXLOGFILES

ORA-02161: invalid value for MAXLOGFILES

Cause: A number does not follow MAXLOGFILES.

Action: Specify a number after MAXLOGFILES.

ORA-02160: index-organized table can not contain columns of type LONG

ORA-02160: index-organized table can not contain columns of type LONG

Cause: A column of type LONG defined for index-organized table.

Action: Do not use columns of type LONG in index-organized tables.

ORA-02159: installed DLM does not support releasable locking mode

ORA-02159: installed DLM does not support releasable locking mode

Cause: The parameter file specified gc_* parameters that allow locks to be release by the LCK process when not in use. This mode requires additional support from the DLM that is not available.

Action: Specify configuration parameters that do not require the additional function.

ORA-02158: invalid CREATE INDEX option

ORA-02158: invalid CREATE INDEX option

Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified.

Action: Choose one of the valid CREATE INDEX options.

ORA-02157: no options specified for ALTER USER

ORA-02157: no options specified for ALTER USER

Cause: No options were specified.

Action: Specify at least one ALTER USER option.

ORA-02156: invalid TEMPORARY tablespace identifier

ORA-02156: invalid TEMPORARY tablespace identifier

Cause: An identifier does not follow TEMPORARY TABLESPACE.

Action: Place a tablespace name after TEMPORARY TABLESPACE.

ORA-02155: invalid DEFAULT tablespace identifier

ORA-02155: invalid DEFAULT tablespace identifier

Cause: An identifier does not follow DEFAULT TABLESPACE.

Action: Place a tablespace name after DEFAULT TABLESPACE.

ORA-02154: a tablespace with the name string is found

ORA-02154: a tablespace with the name string is found

Cause: An attempt to rename a tablespace to a new name failed because the new name is already used by some other tablespace.

Action: Retry with a different new name.

ORA-02153: invalid VALUES password string

ORA-02153: invalid VALUES password string

Cause: An encoded password string does not follow the VALUES clause.

Action: Place a proper encoded password string after the VALUES clause.

ORA-02152: Invalid ALTER TABLESPACE ... RENAME option

ORA-02152: Invalid ALTER TABLESPACE ... RENAME option

Cause: An option other than DATAFILE or TO follows by ALTER TABLESPACE ... RENAME.

Action: The user must specify either DATAFILE or TO following ALTER TABLESPACE ... RENAME.

ORA-02151: invalid tablespace name: string

ORA-02151: invalid tablespace name: string

Cause: Oracle cannot create a tablespace whose name starts with _$deleted$ .

Action: Try a different tablespace name.

ORA-02150: invalid new tablespace name

ORA-02150: invalid new tablespace name

Cause: The new tablespace name specified in ALTER TABLESPACE RENAME TO statement was invalid.

Action: Retry with a valid new tablespace name.

ORA-02149: Specified partition does not exist

ORA-02149: Specified partition does not exist

Cause: Partition not found for the object.

Action: Retry with correct partition name.

ORA-02148: EXCLUSIVE specified multiple times

ORA-02148: EXCLUSIVE specified multiple times

Cause: The EXCLUSIVE option was specified in a CREATE DATABASE statement multiple times.

Action: Only specify the EXCLUSIVE option once.

ORA-02147: conflicting SHARED or EXCLUSIVE options

ORA-02147: conflicting SHARED or EXCLUSIVE options

Cause: Both the SHARED and EXCLUSIVE options were specified in a CREATE DATABASE statement.

Action: Specify SHARED or EXCLUSIVE, but not both.

ORA-02146: SHARED specified multiple times

ORA-02146: SHARED specified multiple times

Cause: The SHARED option was specified in a CREATE DATABASE statement multiple times.

Action: Only specify the SHARED option once.

ORA-02145: missing STORAGE option

ORA-02145: missing STORAGE option

Cause: No STORAGE options were specified following STORAGE (

Action: Specify one or more STORAGE option between the parentheses.

ORA-02144: no option specified for ALTER CLUSTER

ORA-02144: no option specified for ALTER CLUSTER

Cause: No ALTER CLUSTER options are specified.

Action: Specify one or more of the following options: pctfree, pctused, size, storage.

ORA-02143: invalid STORAGE option

ORA-02143: invalid STORAGE option

Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or PCTINCREASE was specified in the STORAGE clause.

Action: Specify only valid options.

ORA-02142: missing or invalid ALTER TABLESPACE option

ORA-02142: missing or invalid ALTER TABLESPACE option

Cause: A valid option was not present.

Action: Use one of the valid options: add, rename, default, online, offline, read only, read write, begin, end, no, force, retention guarantee and retention noguarantee.

ORA-02141: invalid OFFLINE option

ORA-02141: invalid OFFLINE option

Cause: An option other than NORMAL or IMMEDIATE follows OFFLINE.

Action: The user must either specify no option following OFFLINE or one of the options NORMAL or IMMEDIATE.

ORA-02096: specified initialization parameter is not modifiable with this option ORA-02140: invalid tablespace name

ORA-02096: specified initialization parameter is not modifiable with this option ORA-02140: invalid tablespace name

Cause: An identifier does not follow ALTER TABLESPACE.

Action: Specify a tablespace name following ALTER TABLESPACE.

ORA-02095: specified initialization parameter cannot be modified

ORA-02095: specified initialization parameter cannot be modified

Cause: The specified initialization parameter is not modifiable

Action: none

ORA-02094: replication option not installed

ORA-02094: replication option not installed

Cause: The replication option was not installed at this site. Updatable materialized views, deferred RPCs, and other replication features were, therefore, unavailable.

Action: Install the replication option. The replication option is not part of the Oracle Server product and must be purchased separately. Contact an Oracle Sales representative if the replication option needs to be purchased.

ORA-02093: TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) more than maximum possible(string)

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.

ORA-02092: out of transaction table slots for distributed 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-02091: transaction rolled back

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-02090: network error: attempted callback+passthru

ORA-02090: network error: attempted callback+passthru

Cause: internal error.

Action: none

ORA-02089: COMMIT is not allowed in a subordinate session

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-02088: distributed database option not installed

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-02087: object locked by another process in same transaction

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-02086: database (link) name is too long

ORA-02086: database (link) name is too long

Cause: database or database link name can have at most 128 characters.

Action: none

ORA-02085: database link string connects to string

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-02084: database name is missing a component

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-02083: database name has illegal character string

ORA-02083: database name has illegal character string

Cause: supplied database name can contain only A-Z, 0-9, _ , # , $ . and characters.

Action: none

ORA-02082: a loopback database link must have a connection qualifier

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.COMINST1 - the INST1 is the qualifier

ORA-02081: database link is not open

ORA-02081: database link is not open

Cause: dblink given is not currently open.

Action: none

ORA-02080: database link is in use

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 lamp;lt;lamp;nbsp;linklamp;gt; command.

Action: commit or rollback, and close all cursors

ORA-02079: no new sessions may join a committing distributed transaction

ORA-02079: no new sessions may join a committing distributed transaction

Cause: A call to UPI2BG was issued in a session for a transaction that has begun to commit in a different branch; that is, a call to upi2en was issued for a branch of the same transaction in another session. This can only happen when using an external transaction manager.

Action: Contact support.

ORA-02077: selects of long columns must be from co-located tables

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-02076: sequence not co-located with updated table or long column

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-02075: another instance changed state of transaction string

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.