32 ORA-60001 to ORA-60025

ORA-60001: adding (string) blocks to save undo segment in tablespace string with MAXSIZE (string): Cause: Save undo for the offline tablespace at segment MAXSIZE.; Action: Check the storage parameters for the system tablespace. The tablespace needs to be brought back online so the undo can be applied.

ORA-60002: adding (string) blocks to temporary segment in tablespace string with MAXSIZE (string): Cause: Extending a temporary segment violated MAXSIZE limit.; Action: Increase the MAXSIZE limit and retry command.

ORA-60003: adding (string) blocks to table string.string partition string with MAXSIZE (string): Cause: Extending a table partition violated MAXSIZE limit.; Action: Increase the MAXSIZE limit and retry command.

ORA-60004: adding (string) blocks to table string.string with MAXSIZE (string): Cause: Extending a table violated MAXSIZE limit.; Action: Increase the MAXSIZE limit and retry command.

ORA-60005: adding (string) blocks to cluster string.string with MAXSIZE (string): Cause: Extending a cluster violated MAXSIZE limit.; Action: Increase the MAXSIZE limit and retry command.

ORA-60006: adding (string) blocks to index string.string partition string with MAXSIZE (string): Cause: Extending an index partition violated MAXSIZE limit.; Action: Increase the MAXSIZE limit and retry command.

ORA-60007: adding (string) blocks to index string.string subpartition string with MAXSIZE (string): Cause: Extending an index subpartition violated MAXSIZE limit.; Action: Increase the MAXSIZE limit and retry command.

ORA-60008: adding (string) blocks to index string.string with MAXSIZE (string): Cause: Extending an index violated MAXSIZE limit.; Action: Increase the MAXSIZE limit and retry command.

ORA-60009: adding (string) blocks to LOB segment string.string partition string with MAXSIZE (string): Cause: Extending a LOB segment violated MAXSIZE limit.; Action: Increase the MAXSIZE limit and retry command.

ORA-60010: adding (string) blocks to LOB segment string.string with MAXSIZE (string): Cause: Extending a LOB segment violated MAXSIZE limit.; Action: Increase the MAXSIZE limit and retry command.

ORA-60011: adding (string) blocks to lob segment string.string subpartition string with MAXSIZE (string): Cause: Extending a LOB segment violated MAXSIZE limit.; Action: Increase the MAXSIZE limit and retry command.

ORA-60012: adding (string) blocks to table string.string subpartition string with MAXSIZE (string): Cause: Extending a table subpartition violated MAXSIZE limit.; Action: Increase the MAXSIZE limit and retry command.

ORA-60013: invalid MAXSIZE storage option value: Cause: Invalid value was specified for MAXSIZE storage clause.; Action: Correct the value and retry command.

ORA-60014: invalid MAXSIZE storage option value: Cause: Minimum of 1M should have been specified against the MAXSIZE storage clause.; Action: Correct the value and retry command.

ORA-60015: invalid RETENTION storage option value: Cause: Value of MIN retention should have been nonzero.; Action: Correct the value and retry command.

ORA-60016: Operation not supported on SECUREFILE segment: Cause: The operation to ALTER FREELIST/RETENTION was not supported on SECUREFILE segment.; Action: Check the LOB type and reissue the statement.

ORA-60018: adding string blocks to rollback segment string with MAXSIZE (string): Cause: Extending a rollback segment violated MAXSIZE limit.; Action: Increase the MAXSIZE limit and retry command.

ORA-60019: Creating initial extent of size string in tablespace of extent size string: Cause: Creation of SECUREFILE segment failed due to small tablespace extent size.; Action: Create tablespace with larger extent size and reissue command.

ORA-60025: Event for temp segment cleanup used for temp lobs: Cause: Temp LOB segments used for temporary LOBs are deleted only on session exit which may lead to large amounts of memory being held across multiple sessions.; Action: Setting this event will cause temporary LOB segments to be freed when there are no active temporary LOBs in the session. Setting this event will have a significant performance impact as it can cause temporary lob segments to be allocated and deleted many times during a session rather than once per session. Use this event only when temporary LOB segment memory use is an issue.