Oracle Database / Operations & Incident Response
ORA-08004: investigate an exhausted sequence boundary
A sequence can reach its configured maximum or minimum. Inspect its direction, bounds and cycle setting before planning a change.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT sequence_owner, sequence_name, min_value, max_value, increment_by, cycle_flag, last_number FROM all_sequences WHERE sequence_owner = 'APP_OWNER' AND sequence_name = 'ORDER_SEQ';Read the result
The metadata describes allocation limits. Cached LAST_NUMBER needs care and is not a precise committed-row high-water mark.
Resolve and verify
Check the target column capacity and business uniqueness rules, then plan a supported sequence-bound adjustment or identifier redesign.
Operational precautions
Do not enable CYCLE or reset values if old identifiers can collide with existing records.