ORA-04027: self-deadlock during automatic validation for object string.string

ORA-04027: self-deadlock during automatic validation for object string.string

Cause: An attempt was made to validate an invalidated object but it failed because of a self-deadlock.

Action: , e.g. compile the invalidated object separately.

ORA-04022: nowait requested, but had to wait to lock dictionary object

ORA-04022: nowait requested, but had to wait to lock dictionary object

Cause: Had to wait to lock a library object during a nowait request.

Action: Retry the operation later.

ORA-04021: timeout occurred while waiting to lock object stringstringstringstringstring

ORA-04021: timeout occurred while waiting to lock object stringstringstringstringstring

Cause: While waiting to lock a library object, a timeout is occurred.

Action: Retry the operation later.

ORA-04020: deadlock detected while trying to lock object stringstringstringstringstring

ORA-04020: deadlock detected while trying to lock object stringstringstringstringstring

Cause: While trying to lock a library object, a deadlock is detected.

Action: Retry the operation later.

ORA-04017: invalid value string (length = string) for parameter max_dump_file_size

ORA-04017: invalid value string (length = string) for parameter max_dump_file_size

Cause: neither did the string supplied for max_dump_file_size parameter match the UNLIMITED string value nor did it represent a base 10 integer.

Action: reassign a proper value to this parameter.

ORA-04016: sequence string no longer exists

ORA-04016: sequence string no longer exists

Cause: sequence was dropped while processing its next value.

Action: re-create the sequence

ORA-04015: ascending sequences that CYCLE must specify MAXVALUE

ORA-04015: ascending sequences that CYCLE must specify MAXVALUE

Cause: sequences that cycle must have their wrap-wrap specified

Action: re-create the sequence, specifying its wrap-value

ORA-04014: descending sequences that CYCLE must specify MINVALUE

ORA-04014: descending sequences that CYCLE must specify MINVALUE

Cause: sequences that cycle must have their wrap-wrap specified

Action: re-create the sequence, specifying its wrap-value

ORA-04013: number to CACHE must be less than one cycle

ORA-04013: number to CACHE must be less than one cycle

Cause: number to CACHE given is larger than values in a cycle

Action: enlarge the cycle, or cache fewer values

ORA-04012: object is not a sequence

ORA-04012: object is not a sequence

Cause: the object specified cannot have sequence ddl s performed on it

Action: re-enter the statement being careful with the spelling of the name

ORA-04011: sequence string must range between string and string

ORA-04011: sequence string must range between string and string

Cause: the value specified for one of the sequence parameters exceeds limits

Action: specify parameter within these limits

ORA-04010: the number of values to CACHE must be greater than 1

ORA-04010: the number of values to CACHE must be greater than 1

Cause: the value in the CACHE clause was one

Action: specify NOCACHE, or a value larger than one

ORA-04009: MAXVALUE cannot be made to be less than the current value

ORA-04009: MAXVALUE cannot be made to be less than the current value

Cause: the current value exceeds the given MAXVALUE

Action: make sure that the new MAXVALUE is larger than the current value

ORA-04008: START WITH cannot be more than MAXVALUE

ORA-04008: START WITH cannot be more than MAXVALUE

Cause: the starting value would be larger than MAXVALUE

Action: make sure that the starting value is less than MAXVALUE

ORA-04007: MINVALUE cannot be made to exceed the current value

ORA-04007: MINVALUE cannot be made to exceed the current value

Cause: the given MINVALUE would be greater than the current value

Action: always make sure that MINVALUE is lamp;lt;lamp;nbsp;= the current value

ORA-04006: START WITH cannot be less than MINVALUE

ORA-04006: START WITH cannot be less than MINVALUE

Cause: the given starting value is less than MINVALUE

Action: make sure that the starting value is lamp;gt;= MINVALUE

ORA-04005: INCREMENT must be less than MAXVALUE minus MINVALUE

ORA-04005: INCREMENT must be less than MAXVALUE minus MINVALUE

Cause: the INCREMENT specified is lamp;gt;= MAXVALUE-MINVALUE

Action: specify an INCREMENT that is lamp;lt;lamp;nbsp; MAXVALUE-MINVALUE

ORA-04004: MINVALUE must be less than MAXVALUE

ORA-04004: MINVALUE must be less than MAXVALUE

Cause: MINVALUE was specified to be greater than or equal to MAXVALUE

Action: specify a MINVALUE that is less than MAXVALUE

ORA-04003: sequence parameter string exceeds maximum size allowed (string digits)

ORA-04003: sequence parameter string exceeds maximum size allowed (string digits)

Cause: %s (a sequencer parameter) had too many digits

Action: specify the parameter with the allowed number of digits

ORA-04002: INCREMENT must be a non-zero integer

ORA-04002: INCREMENT must be a non-zero integer

Cause: a sequence increment was specified to be zero

Action: specify the increment to be a non-zero value

ORA-04001: sequence parameter string must be an integer

ORA-04001: sequence parameter string must be an integer

Cause: %s (a sequence parameter) specified was not an integer

Action: create the sequence, giving the specified parameter an integer value

ORA-04000: the sum of PCTUSED and PCTFREE cannot exceed 100

ORA-04000: the sum of PCTUSED and PCTFREE cannot exceed 100

Cause: the sum of PCTUSED and PCTFREE for a cluster or table exceeds 100

Action: create the table or cluster specifying values whose sum is lamp;lt;lamp;nbsp;= 100

ORA-03299: cannot create dictionary table string

ORA-03299: cannot create dictionary table string

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.

ORA-03298: cannot shrink datafile - file string is under hot backup

ORA-03298: cannot shrink datafile - file string is under hot backup

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.

ORA-03297: file contains used data beyond requested RESIZE value

ORA-03297: file contains used data beyond requested RESIZE value

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.

ORA-03296: cannot resize datafile - file string not found

ORA-03296: cannot resize datafile - file string not found

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.

ORA-03293: Cluster to be truncated is a HASH CLUSTER

ORA-03293: Cluster to be truncated is a HASH CLUSTER

Cause: Only INDEX CLUSTERS can be truncated.

Action: Drop and recreate the HASH CLUSTER instead of using truncate.

ORA-03292: Table to be truncated is part of a cluster

ORA-03292: Table to be truncated is part of a cluster

Cause: The table being truncated is a member of a cluster.

Action: Either use TRUNCATE CLUSTER or DROP TABLE

ORA-03291: Invalid truncate option - missing STORAGE keyword

ORA-03291: Invalid truncate option - missing STORAGE keyword

Cause: Expected STORAGE keyword

Action: Either specify DROP STORAGE or REUSE STORAGE

ORA-03290: Invalid truncate command - missing CLUSTER or TABLE keyword

ORA-03290: Invalid truncate command - missing CLUSTER or TABLE keyword

Cause: Invalid object specification given.

Action: Either specify TRUNCATE CLUSTER or TRUNCATE TABLE

ORA-03289: partition name and segment type do not match

ORA-03289: partition name and segment type do not match

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

ORA-03288: both FREELIST GROUP and INSTANCE parameters may not be specified

ORA-03288: both FREELIST GROUP and INSTANCE parameters may not be specified

Cause: Both FREELIST GROUP and INSTANCE were specified in clause

Action: Remove one of the two parameters

ORA-03287: invalid FREELIST GROUP specified

ORA-03287: invalid FREELIST GROUP specified

Cause: The specified FREELIST GROUP number is invalid

Action: Choose a number between 1 and # freelist groups for this object

ORA-03286: ALLOCATE EXTENT not valid for HASH CLUSTERS

ORA-03286: ALLOCATE EXTENT not valid for HASH CLUSTERS

Cause: The cluster is a hash cluster, and can not use the allcoate extent option.

Action: none

ORA-03284: datafile string is not a member of tablespace string

ORA-03284: datafile string is not a member of tablespace string

Cause: The specified datafile does not belong to the tablespace that the object resides in.

Action: Retry the option with the correct datafile.

ORA-03283: specified datafile string does not exist

ORA-03283: specified datafile string does not exist

Cause: The datafile does not exist

Action: Retry the option with the correct datafile

ORA-03282: missing ALLOCATE EXTENT option

ORA-03282: missing ALLOCATE EXTENT option

Cause: No ALLOCATE EXTENT options were specified.

Action: Specified one or more of the following options: DATAFILE, SIZE or INSTANCE.

ORA-03281: invalid ALLOCATE EXTENT option

ORA-03281: invalid ALLOCATE EXTENT option

Cause: An option other than DATAFILE, SIZE or INSTANCE was specified.

Action: Remove invalid option and retry the command.

ORA-03280: invalid DATAFILE filename specified

ORA-03280: invalid DATAFILE filename specified

Cause: A character string literal is expected, but not found.

Action: Specify filenames using character string literals.

ORA-03279: invalid INSTANCE specified

ORA-03279: invalid INSTANCE specified

Cause: The specified value is not recognized as a valid instance name.

Action: Use a valid name.

ORA-03278: duplicate ALLOCATE EXTENT option specification

ORA-03278: duplicate ALLOCATE EXTENT option specification

Cause: An option (DATAFILE, SIZE or INSTANCE) was specified more than once.

Action: Specify each option at most once.

ORA-03277: invalid SIZE specified

ORA-03277: invalid SIZE specified

Cause: The specified value must be an integer.

Action: Choose an appropriate integer value.

ORA-03276: duplicate ALLOCATE EXTENT option specification

ORA-03276: duplicate ALLOCATE EXTENT option specification

Cause: The ALLOCATE EXTENT option to ALTER TABLE or ALTER INDEX is specified more than once.

Action: Specify the option at most once.

ORA-03275: duplicate DEALLOCATE option specification

ORA-03275: duplicate DEALLOCATE option specification

Cause: The DEALLOCATE UNUSED option to ALTER TABLE or ALTER INDEX is specified more than once.

Action: Specify the option at most once.

ORA-03274: both ALLOCATE EXTENT and DEALLOCATE UNUSED options are specified

ORA-03274: both ALLOCATE EXTENT and DEALLOCATE UNUSED options are specified

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.

ORA-03264: cannot drop offline datafile of locally managed tablespace

ORA-03264: cannot drop offline datafile of locally managed tablespace

Cause: Trying to drop offline datafile in lmts

Action: Try to drop file afetr making it online

ORA-03263: cannot drop the first file of tablespace string

ORA-03263: cannot drop the first file of tablespace string

Cause: Trying to drop the first datafile with which ts is created

Action: Cannot drop the first datafile with which ts is created

ORA-03262: the file is non-empty

ORA-03262: the file is non-empty

Cause: Trying to drop a non-empty datafile

Action: Cannot drop a non empty datafile

ORA-03261: the tablespace string has only one file

ORA-03261: the tablespace string has only one file

Cause: Dropping file from ts which has a single file extent.

Action: Cannot make a tablespace fileless

ORA-03254: unable to execute the sql in read only database

ORA-03254: unable to execute the sql in read only database

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.

ORA-03252: initial extent size not enough for LOB segment

ORA-03252: initial extent size not enough for LOB segment

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.

ORA-03251: Cannot issue this command on SYSTEM tablespace

ORA-03251: Cannot issue this command on SYSTEM tablespace

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

ORA-03250: Cannot mark this segment corrupt

ORA-03250: Cannot mark this segment corrupt

Cause: This segment cannot be marked corrupt because it contains data dictionary objects

Action: Check the segment information and reissue the command.

ORA-03249: Uniform size for auto segment space managed tablespace should have atleast string blocks

ORA-03249: Uniform size for auto segment space managed tablespace should have atleast string blocks

Cause: For the given blocksize, uniform size specified is insufficient

Action: Specify larger extent size and retry

ORA-03248: Too much of segment creation activity during migration

ORA-03248: Too much of segment creation activity during migration

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.

ORA-03247: Invalid block number specified

ORA-03247: Invalid block number specified

Cause: Relocation of bitmaps to the said destination will make the tablespace self descriptive

Action: Choose another destination dba.

ORA-03246: Invalid block number specified

ORA-03246: Invalid block number specified

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

ORA-03245: Tablespace has to be dictionary managed, online and permanent to be able to migrate

ORA-03245: Tablespace has to be dictionary managed, online and permanent to be able to migrate

Cause: Tablespace was not dictionary managed or online or permanent.

Action: Make sure the tablespace is online, permanent and dictionary managed

ORA-03244: No free space found to place the control information

ORA-03244: No free space found to place the control information

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.

ORA-03243: destination dba overlaps with existing control information

ORA-03243: destination dba overlaps with existing control information

Cause: Cannot overlap control information during relocation

Action: Please chose another destination address