Server Messages: ORA-02351 to ORA-29799

04000-04019: Invalid Command Parameter Messages

This section lists some of the messages generated when inconsistent values are used in a command.

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

Cause: The sum of the PCTUSED and PCTFREE values specified for a cluster or table exceeds 100.

Action: Create the table or cluster specifying values for PCTUSED and PCTFREE. The sum of these values cannot exceed 100.

ORA-04001: sequence parameter str must be an integer

Cause: The specified sequence parameter was not an integer.

Action: Create the sequence, giving the specified parameter an integer value.

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

Cause: A sequence increment was specified as zero.

Action: Specify the increment as a non-zero value.

ORA-04003: sequence parameter num exceeds the maximum size allowed num digits

Cause: The specified sequence parameter has too many digits.

Action: Specify the parameter with the allowed number of digits and try again.

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 and try again.

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

Cause: INCREMENT was specified as equal to or greater than MAXVALUE minus MINVALUE. This is not permitted.

Action: Specify INCREMENT as less than MAXVALUE minus MINVALUE and try again.

ORA-04006: START WITH cannot be less than MINVALUE

Cause: The given starting value is less than MINVALUE.

Action: Check that the starting value is not less than MINVALUE and try again.

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

Cause: The given MINVALUE is greater than the current value.

Action: Check that MINVALUE is not greater than the current value and try again.

ORA-04008: START WITH cannot be more than MAXVALUE

Cause: The starting value is larger than MAXVALUE.

Action: Check that the starting value is less than MAXVALUE and try again.

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

Cause: The current value exceeds the given MAXVALUE.

Action: Check that the new MAXVALUE is larger than the current value and try again.

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

Cause: The value specified in the CACHE clause of a CREATE SEQUENCE statement is 1. The default value is 20.

Action: Specify NOCACHE or a value greater than 1 and try again.

ORA-04011: sequence name must range between num and num

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

Action: Specify a parameter within these limits.

For more information about CREATE SEQUENCE, see the index entry on "CREATE SEQUENCE" in Oracle8 Server SQL Reference.

ORA-04012: object is not a sequence

Cause: The object specified cannot have sequence operations performed on it.

Action: Re-enter the statement, making sure to spell the sequence name correctly.

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

Cause: The number to CACHE specified in a CREATE SEQUENCE statement exceeds the number of values in a cycle.

Action: Enlarge the cycle or cache fewer values, and try again.

ORA-04014: descending sequences that CYCLE must specify MIN VALUE

Cause: A value was not specified in the CREATE SEQUENCE statement. Sequences that cycle must specify a value at which to begin again.

Action: Re-create the sequence, specifying the value at which it is to begin.

ORA-04015: ascending sequences that CYCLE must specify MAX VALUE

Cause: A value was not specified in the CREATE SEQUENCE statement. Sequences that cycle must specify a value at which to begin again.

Action: Recreate the sequence, specifying the value at which it is to begin.

ORA-04016: sequence name no longer exists

Cause: Sequence was dropped while processing its next value.

Action: Recreate the sequence.

For more information about CREATE SEQUENCE, see the index entry on "CREATE SEQUENCE" in Oracle8 Server SQL Reference.

ORA-04017: invalid value num (length = num) 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: Assign a valid value to this parameter.