Oracle 11g Error Codes and Solution Suggestions from ORA-10600 to ORA-10650
- ORA-10614: Operation not allowed on this segment
- Cause: This procedure can be used only on segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT
- Action: Recheck the segment name and type and re-issue the statement
- ORA-10615: Invalid tablespace type for temporary tablespace
- Cause: Tablespace with AUTO SEGMENT SPACE MANAGENEMT specified cannot be used as a temporary tablespace
- Action: Recheck the tablespace name and re-issue the statement
- ORA-10616: Operation not allowed on this tablespace
- Cause: Cannot perform the operation on tablespace with AUTO SEGMENT SPACE MANAGEMENT
- Action: Recheck the tablespace name and re-issue the statement
- ORA-10617: Cannot create rollback segment in dictionary managed tablespace
- Cause: Rollback segments cannot be created in dictionary managed tablespaces when SYSTEM tablespace is locally managed
- Action: Recheck the tablespace name and re-issue the statement
- ORA-10618: Operation not allowed on this segment
- Cause: This DBMS_SPACE operation is not permitted on segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT
- Action: Recheck the segment name and type and re-issue the statement
- ORA-10619: Avoid assertions when possible
- Cause: A bug (or upgrade) hits unicode assertions (csid, csform, bfc)
- Action: Event makes RDBMS skip assertions and patch up datastructures
- ORA-10620: Operation not allowed on this segment
- Cause: Cannot alter freelist storage parameter for segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT
- Action: Recheck the segment name and re-issue the statement
- ORA-10627: Dump the content of the index leaf block
- Cause: Generate a complete index tree dump, not just an overview during alter session set events immediate trace name treedump
- Action: This event is recommended only for small table/index since it
- ORA-10628: Turn on sanity check for kdiss index skip scan state
- Cause: Will do sanity checking on the kdiss state.
- Action: set this event only under the supervision of Oracle development
- ORA-10630: Illegal syntax specified with SHRINK clause
- Cause: An illegal option was specified with the SHRINK clause
- Action: Verify the SQL Reference Manual and reissue the command
- ORA-10631: SHRINK clause should not be specified for this object
- Cause: It is incorrect to issue shrink on the object
- Action: Verify the object name and type and reissue the command
- ORA-10632: Invalid rowid
- Cause: Segment Highwatermark was overwritten due to shrink and space reused
- Action: Reissue this command.
- ORA-10633: No space found in the segment
- Cause: Raised while trying to find space during segment shrink
- Action: This error should be trapped internally and treated. The user should not be able to see the error.
- ORA-10634: Segment is already being shrunk
- Cause: Only one invocation of shrink can be in progress on a segment at any time
- Action: Reissue the command after the first shrink is over
- ORA-10635: Invalid segment or tablespace type
- Cause: Cannot shrink the segment because it is not in auto segment space managed tablespace or it is not a data, index or lob segment.
- Action: Check the tablespace and segment type and reissue the statement
- ORA-10636: ROW MOVEMENT is not enabled
- Cause: To shrink a data segment, row movement must be enabled.
- Action: Enable row movement and reissue this command.
- ORA-10637: The segment does not exist
- Cause: Segment to be shrunk has been dropped
- Action: None
- ORA-10638: Index status is invalid
- Cause: Cannot shrink an index which is being rebuilt or disabled is an unusable state.
- Action: None
- ORA-10639: Dump library cache during reparse loops
- Cause: During this error a library cache dump is necessary , so enable librarycache dump if event is set.
- Action: Dump a library cache if this event is set when reparse error.
- ORA-10640: Operation not permitted during SYSTEM tablespace migration
- Cause: SYSTEM tablespace is being migrated to locally managed format.
- Action: Reissue this command once SYSTEM tablespace migration is over.
- ORA-10641: Cannot find a rollback segment to bind to
- Cause: SYSTEM tablespace migration requires rollback segment in locally managed tablespace.
- Action: Drop rollback segments in dictionary managed tablespaces other than SYSTEM and create rollback segments in locally managed tablespace and retry migration.
- ORA-10642: Found rollback segments in dictionary managed tablespaces
- Cause: When SYSTEM tablespace is migrated found rollback segments in dictionary managed tablespaces.
- Action: Drop the rollback segments in dictionary managed tablespaces and reissue the command
- ORA-10643: Database should be mounted in restricted mode and Exclusive mode
- Cause: When SYSTEM tablespace is being migrated database should be mounted in Exclusive mode and in Restricted mode.
- Action: Reissue this command after mounting the database in right mode.
- ORA-10644: SYSTEM tablespace cannot be default temporary tablespace
- Cause: When SYSTEM tablespace is being migrated no user should have SYSTEM as the default temporary tablespace.
- Action: Reissue this command after altering the default temporary tablespace setting for all users.
- ORA-10645: Recursive Extension in SYSTEM tablespace during migration
- Cause: When SYSTEM tablespace is being migrated, dictionary tables tried to extend recursively. Must be caught and processed internally. Should not be thrown to the user.
- Action: Report the error as a bug.
- ORA-10646: Too many recursive extensions during SYSTEM tablespace migration
- Cause: When SYSTEM tablespace is being migrated, dictionary tables tried to extend recursively more than 1000 times.
- Action: If SYSTEM tablespace is very large, then simply reissue the tablespace migration command.
- ORA-10647: Tablespace other than SYSTEM, string, string not found in read only mode
- Cause: When SYSTEM tablespace is being migrated, tablespaces other than the three should be ALTERed to read only.
- Action: Alter the tablespace status to read only and retry migration.
- ORA-10648: Tablespace SYSAUX is not offline
- Cause: The SYSAUX tablespace was online while SYSTEM tablespace was being migrated.
- Action: Alter the SYSAUX tablespace status to offline and retry migration.
- ORA-10649: Turn off/trace lob index freelist coalesce
- Cause: Will turn off or trace lob index freelist coalescing
- Action: set this event only under the supervision of Oracle development