Oracle 11g Error Codes and Solution Suggestions from ORA-12900 to ORA-13000
- 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-12999: cannot DROP or SET UNUSED a column that has been set unused
- Cause: An attempt was made to DROP or SET UNUSED a column that has already been ‘set unused’.
- Action: Use the DROP UNUSED COLUMNS option to remove the column.
- 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.