Oracle 12c R2 Error Codes and Solution Suggestions from ORA-03200 to ORA-03300
- ORA-03200: the segment type specification is invalid
Cause: segment type is not TABLE, INDEX, or CLUSTER
Action: use a correct segment type
Cause: the freelist group number was either negative or larger than the the number of freelist groups in the segment
Action: use a correct group number
Cause: the scan limit did not have a positive integer value the number of freelist groups in the segment
Action: use a correct scan limit
Cause: high volume of user updates interfere with the space analysis
Action: retry the command or lock the underlying objects
Cause: partition name is specified for the space analysis, but the object type does not indicate parttitioning
Action: specify PARTITION in the segment type, if the object is partitioned, otherwise, omit the partition name
Cause: partition name is not specified for the space analysis, but the object type indicates parttitioning
Action: specify partition name, if the object is partitioned, otherwise, specify a non-partitioned type
Cause: The maximum file size for an autoextendable file has exceeded the maximum number of blocks allowed.
Action: Reduce the size and retry.
Cause: partition type is specified for the space analysis, but the object type indicates composite partitioning
Action: specify subpartition name and subpartition type
Cause: subpartition type is specified for the space analysis, but the object type indicates non-composite partitioning
Action: specify partition name and partition type
Cause: The value of file number or block number is outside of limits or inconsistent
Action: Fix the file number/block number value
Cause: The value of one of the option parameters is incorrect
Action: Fix the option value
Cause: The segment specified in the DBMS_SPACE_ADMIN or DBMS_SPACE operation does not exist or is not in a state appropriate for this operation
Action: Fix the segment specification, or put the segment in the appropriate state.
Cause: Attempt to create a temporary segment for sort/hash/lobs in in permanent tablespace of kind locally-managed
Action: Alter temporary tablespace of user to a temporary tablespace or a dictionary-managed permanent tablespace
Cause: The Lob Segment specified in the DBMS_SPACE operation does not exist.
Action: Fix the Segment Specification
Cause: File Size specified for add/resize datafile/tempfile does not allow for the minimum required of one allocation unit.
Action: Increase the specification for file size
Cause: File Size specified for resize datafile/tempfile causes bitmap control structures to overlap
Action: Increase the specification for file size
Cause: Corruptions detected during verification whch cannot be dealt with
Action: Do manual verification
Cause: invalid option for alter of temporary tablespace was specified
Action: Specify one of the valid options: ADD TEMPFILE, TEMPFILE ONLINE, TEMPFILE OFFLINE
Cause: invalid option for create/alter tablespace of type locally-managed
Action: Specify one of the valid options.
Cause: Operation which is only applicable to permanent, online, locally-managed tablespaces is specified for a tablespace which is either dictionary-managed, offline or temporary
Action: Reissue operation for a different tablespace, mount the tablespace or do not issue it at all, since it does not apply for the given tablespace
Cause: Some of the procedures was called with missing or NULL parameters
Action: Specify the missing parameter
Cause: An attempt was made to do one of the following : (1) create a temporary tablespace with a non-standard block size or, (2) alter an existing permanent tablespace of non-standard block size to a temporary tablespace or, (3) issue a DDL statement that would result in the creation of a temporary segment in a tablespace of non-standard block size.
Action: (1) If creating a temporary tablespace, do not specify a block size different from the standard block size. (2) If altering an existing permanent tablespace to a temporary tablespace, ensure that it is of standard block size. (3) Ensure that the user’s temporary tablespace is a tablespace having the standard block size.
Cause: Either a bad value passed to dbms_space.create_table_cost() or explain plan did not pass through size information.
Action: Check the row size parameter in dbms_space.create_table_cost(). For explain plan, make sure statistics have been computed for all source tables in the CREATE TABLE AS SELECT statement.
Cause: The limitation of addressability of BMIB (Bitmap Index Block) was reached for the current blocksize.
Action: If the segment size has grown greater than addressability of BMIB (Bitmap Index Block), do the following: (1) Partition the table. (2) Move the segment to a tablespace having bigger blocksize.
Cause: Attempt to preserve too many blocks.
Action: reduce the KEEP amount.
Cause: Attempt to deallocate space from the segment which was truncated prior to the 7.3 release.
Action: increase the KEEP amount, or truncate the segment, and reissue the command.
Cause: Failed to allocate an extent for table subpartition segment in tablespace.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
Cause: Failed to allocate an extent for index subpartition segment in tablespace.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
Cause: A table subpartition tried to extend past maxextents
Action: If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params
Cause: An index subpartition tried to extend past maxextents
Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params.
Cause: Too large a size for an initial extent due to freelist group specification
Action: Reduce number of freelist groups specified for segment
- ORA-03238: unable to extend LOB segment string.string subpartition string by string in tablespace string
Cause: An attempt was made to allocate an extent for LOB subpartition segment in tablespace, but the extent could not be allocated because there is not enough space in the tablespace indicated.
Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
Cause: A LOB subpartition segment tried to extend past maxextents.
Action: If maxextents is less than the system maximum, raise it. Otherwise, recreate the subpartition with larger INITIAL, NEXT, or PCTINCREASE parameters.
Cause: Users default temporary tablespace must be different from the tablespace being migrated.
Action: alter users default temporary tablespace to be different.
Cause: User specified an invalid unit size for the tablespace
Action: Specify the correct unit size. To estimate unit size please refer to Oracle Server Administrator’s Guide.
Cause: For migration to complete, temporary segments should not be present in the tablespace at the time of migration.
Action: Avoid migrating the tablespace when there is heavy temporary segment creation going on as with object drops.
Cause: Cannot overlap control information during relocation
Action: Please chose another destination address
Cause: During migration of tablespace found no place to put the control information. If during bitmaps relocation, found no space at the specified destination.
Action: If during migration, add more space to the tablespace and retry migration. If during bitmaps relocation, specify a destination address where there is enough free space.
Cause: Tablespace was not dictionary managed or online or permanent.
Action: Make sure the tablespace is online, permanent and dictionary managed
Cause: Control information cannot be placed at the specified dba either because the block number specified is beyond the file end or the file is not large enough to accomodate the control information at that location
Action: specify a correct block number
Cause: Relocation of bitmaps to the said destination will make the tablespace self descriptive
Action: Choose another destination dba.
Cause: Temporary segments were attempted to be created during migration
Action: The error is signalled after retrying migration for 500 times. Run migration when there is less of segment creation activity is going on.
Cause: For the given blocksize, uniform size specified is insufficient
Action: Specify larger extent size and retry
Cause: This segment cannot be marked corrupt because it contains data dictionary objects
Action: Check the segment information and reissue the command.
Cause: It is not permitted to migrate SYSTEM tablespace from locally managed format to dictionary managed format or relocate bitmaps.
Action: Check the tablespace name and procedure name
Cause: Fatblock size of LOB segment is too big to fit into the initial extent.
Action: Specify a smaller fatblock size or create the LOB segment in other tablespaces with bigger initial extent size.
Cause: Unable to create a consistent snapshot of the object in a read only database. Transaction recovery must be performed before opening the database read only.
Action: Open the database read write, allow dead transaction recovery to complete and then open the database read only.
Cause: Dropping file from ts which has a single file extent.
Action: Cannot make a tablespace fileless
Cause: Trying to drop a non-empty datafile
Action: Cannot drop a non empty datafile
Cause: Trying to drop the first datafile with which ts is created
Action: Cannot drop the first datafile with which ts is created
Cause: Trying to drop offline datafile in lmts
Action: Try to drop file afetr making it online
Cause: The DEALLOCATE option and the ALLOCATE option are specified in the same command.
Action: Choose one of the options or issue two separate commands.
Cause: The DEALLOCATE UNUSED option to ALTER TABLE or ALTER INDEX is specified more than once.
Action: Specify the option at most once.
Cause: The ALLOCATE EXTENT option to ALTER TABLE or ALTER INDEX is specified more than once.
Action: Specify the option at most once.
Cause: The specified value must be an integer.
Action: Choose an appropriate integer value.
Cause: An option (DATAFILE, SIZE or INSTANCE) was specified more than once.
Action: Specify each option at most once.
Cause: The specified value is not recognized as a valid instance name.
Action: Use a valid name.
Cause: A character string literal is expected, but not found.
Action: Specify filenames using character string literals.
Cause: An option other than DATAFILE, SIZE or INSTANCE was specified.
Action: Remove invalid option and retry the command.
Cause: No ALLOCATE EXTENT options were specified.
Action: Specified one or more of the following options: DATAFILE, SIZE or INSTANCE.
Cause: The datafile does not exist
Action: Retry the option with the correct datafile
Cause: The specified datafile or tempfile did not belong to the tablespace that the object resides in.
Action: Retry the option with the correct datafile or tempfile.
Cause: The cluster is a hash cluster, and can not use the allcoate extent option.
Action: n/a
Cause: The specified FREELIST GROUP number is invalid
Action: Choose a number between 1 and # freelist groups for this object
Cause: Both FREELIST GROUP and INSTANCE were specified in clause
Action: Remove one of the two parameters
Cause: Partition name and segment type specified for space analysis do not match
Action: Specify type PARTITION if the object is partitioned, specify SUBPARTITION if the object is composite
Cause: Invalid object specification given.
Action: Either specify TRUNCATE CLUSTER or TRUNCATE TABLE
Cause: Expected STORAGE keyword
Action: Either specify DROP STORAGE or REUSE STORAGE
Cause: The table being truncated is a member of a cluster.
Action: Either use TRUNCATE CLUSTER or DROP TABLE
Cause: Only INDEX CLUSTERS can be truncated.
Action: Drop and recreate the HASH CLUSTER instead of using truncate.
Cause: The specified datafile is not available for resizing.
Action: Ensure that the datafile name is valid, and if so, ensure the file is accessible.
Cause: Some portion of the file in the region to be trimmed is currently in use by a database object
Action: Drop or move segments containing extents in this region prior to resizing the file, or choose a resize value such that only free space is in the trimmed.
Cause: Attempt to shrink a datafile while it is under hot backup. This is not allowed.
Action: Retry shrinking the file after the hot backup completes.
Cause: A dictionary table is created upon the first execution of the command ‘alter database datafile autoextend on’ for a database. This operation did not succeed. The most probable cause for this is insufficient space in the system tablespace.
Action: See action for next error message in error stack.