Skip to content

Fatih Acar's blog

About of Database Systems and Information Technologies

Menu
  • Home
  • About Me
  • Contact Me
Menu

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-10614 to ORA-10707

Posted on 07/09/201623/01/2017 by Fatih Acar

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-10614 to ORA-10707

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-10621: specify retry count for online index build cleanup DML lock get
ORA-10624: Disable UJV invalidation on drop index
ORA-10625: Turn off redo log dump for the index when OERI 12700
ORA-10626: specify timeout for online index rebuild to wait for DML
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-10629: force online index build to backoff and retry DML lock upgrade
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-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: n/a

ORA-10638: Index status is invalid

Cause: Cannot shrink an index which is being rebuilt or disabled is an unusable state.

Action: n/a

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

ORA-10650: disable cache-callback optimisation
ORA-10651: incorrect file number block number specified

Cause: The dba specified is not valid

Action: Check if the dba specified belongs to the segment and is under the segment HWM and reissue the statement

ORA-10652: Object has on-commit materialized views

Cause: It is illegal to issue shrink on an object with on-commit materialized views

Action: n/a

ORA-10653: Table is in a cluster

Cause: It is illegal to shrink a table belonging to a cluster

Action: n/a

ORA-10654: Table is of type temporary or external

Cause: It is illegal to shrink a temporary table or an external table

Action: n/a

ORA-10655: Segment can be shrunk

Cause: Error message returned when called in probe mode by OEM

Action: n/a

ORA-10656: Table is in unusable state due to incomplete operation

Cause: ALTER TABLE SHRINK operation was tried on the table which is in unusable state because of previously failed/incomplete operation.

Action: If the previous operation was – DROP COLUMN, resubmit DROP COLUMN CONTINUE – DROP TABLE, resubmit DROP TABLE table PURGE

ORA-10657: Lob column to be shrunk does not exist

Cause: Shrink was issued on a lob segment that did not exist

Action: n/a

ORA-10658: Lob column to be shrunk is marked unused

Cause: Shrink was issued on a lob segment that is marked as unused

Action: n/a

ORA-10659: Segment being shrunk is not a lob

Cause: Shrink was issued on a segment that should be a first class lob or other data type stored in lob

Action: n/a

ORA-10660: Segment is a shared lob segment

Cause: Shrink was issued on a segment that was being shared by multiple lob columns

Action: n/a

ORA-10661: Invalid option specified

Cause: Check option can be specified for one segment only

Action: n/a

ORA-10662: Segment has long columns

Cause: Shrink was issued on a segment with long columns. This is not supported.

Action: n/a

ORA-10663: Object has rowid based materialized views

Cause: Shrink was issued on an object with rowid based materialized views.

Action: Drop the rowid based materialized views and issue shrink on the object

ORA-10664: Table has bitmap join indexes

Cause: SHRINK was issued on a table with bitmap join indexes.

Action: Drop bitmap join indexes and reissue SHRINK on the object.

ORA-10665: Inject Evil Literals

Cause: Event 10665 is set to some number > 0, causing 1/(value-1) of all literals to be replaced by 2000 letter ‘A’s. A value of 1 does not corrupt anything.

Action: never set this event

ORA-10666: Do not get database enqueue name
ORA-10667: Cause sppst to check for valid process ids
ORA-10668: Inject Evil Identifiers

Cause: event 10668 is set to some number > 0, causing 1/(value-1) of all identifiers to be replaced by a maximum amount of x’s. It is common for an identifier to be parsed once with a max of 30 bytes, then reparsed later with a max of 4000, so it may not be possible to inject such an identifier without the aid of this event. A value of 1 causes no identifiers to be corrupted.

Action: never set this event

ORA-10690: Set shadow process core file dump type (Unix only)

Cause: Control core file size for shadow processes

Action: Level 1: Detach SGA before dumping core Level 2: Do not produce any core

ORA-10691: Set background process core file type (Unix only)

Cause: Control core file size file for background processes

Action: Level 1: Detach SGA before dumping core

ORA-10700: Alter access violation exception handler

Cause: Use this event to control what the VMS exception handler does when it encounters an access violation.

Action: Level: >=10 Suspend current process on access violation *** SET THIS EVENT ONLY UNDER THE SUPERVISION OF ORACLE DEVELOPMENT ***

ORA-10701: Dump direct loader index keys

Cause: Dumps index keys at various points in a direct load based on the value of this event.

Action: n/a

ORA-10702: Application continuity debugging was not enabled

Cause: Enable application continuity debugging

Action: Level indicates details. Level: 0x0001: Transaction intention debugging 0x1000: Failure injection testing 0x2000: Failure injection testing 0x4000: Failure injection testing

ORA-10704: Print out information about what enqueues are being obtained

Cause: When enabled, prints out arguments to calls to ksqcmi and ksqlrl and the return values.

Action: Level indicates details: Level: 1-4: print out basic info for ksqlrl, ksqcmi 5-9: also print out stuff in callbacks: ksqlac, ksqlop 10+: also print out time for each line

ORA-10706: Print out information about global enqueue manipulation

Cause: When enabled, prints out activity in ksi routines.

Action: INternal system parameter (_ksi_trace) can be used in addition to setting this event to limit output information on selected set of global enqueue server enqueue type(s) For example: _ksi_trace = RTXA output information only for RT and XA lock types. Level indicates details: 0-4: show args for each main call 5-9: also indicate callbacks 10+: also printout time for each line

ORA-10707: Simulate process death for instance registration

Cause: When enabled, process commits suicide to test instance registration recovery code.

Action: Level indicates where the process will die

Share this:

  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on X (Opens in new window) X
  • Click to share on Facebook (Opens in new window) Facebook

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.



View Fatih ACAR's profile on LinkedIn

Categories

  • Databases (329)
    • MsSQL Server (18)
      • Administration (16)
      • Errors and Solutions (4)
      • SQL (2)
    • MySQL (5)
      • Administration (4)
      • Backup And Recovery (1)
      • Errors and Solutions (1)
    • Oracle (290)
      • Administration (79)
      • Backup And Recovery (29)
      • Errors and Solutions (195)
      • Procedure (10)
      • SQL (32)
    • PostgreSQL (16)
      • Administration (15)
      • Errors and Solutions (3)
      • SQL (2)
    • Redis (1)
  • Microsotf Dynamics CRM (1)
  • Operating Systems (47)
    • Linux & Unix (34)
    • Windows (13)
  • Programing (5)
    • Python (5)
  • SAP (15)
    • Errors and Solutions (4)
    • SAP Basis (12)
  • Security (8)
    • Database Security (6)
    • Information Security (1)
    • System Security (4)
  • VMware (4)

Recent Posts

  • Redis 7 Sentinel Infrastructure Installation
  • Oracle Database 19c Multi Data Guard and DML Redirect, Switchover-Failover Operations on Oracle Linux 8
  • Oracle Database 23ai Free Installation Steps on Oracle Linux 9
  • Oracle Database 19c Active Data Guard Installation and DML Redirect, Switchover-Failover Operations on Oracle Linux 8
  • Oracle Database 19c Installation and 19.22 RU Patch Apply on Oracle Linux 8

Resources

  • Oracle
  • PostgreSQL

Blogroll

  • Gökhan Atıl
  • H. Koray Gündüz
  • Hakan Talip Öztürk
  • Zekeriya Beşiroğlu

Web Pages

  • BT Çözümleri

Tag Cloud

Administration Backup and Recovery Cluster Systems Database Administration Database Security Linux Linux Administration MsSQL Server MsSQL Server Error and Solutions MySQL MySQL Administration ORA-00018 ORA-00020 Oracle Oracle 12c Oracle 19c Oracle Administration Oracle Backup and Restore Oracle Data Guard Oracle Data Guard Failover Oracle Data Guard Switchover Oracle Error Solutions Oracle Linux Oracle Rman Backup Oracle Security Oracle SQL Query PostgreSQL PostgreSQL Administration PostgreSQL High Availability PostgreSQL Hot Standby Python SAP Basis Sap Errors and Solutions Sap System Administration SQL SQL Server Administration SQL Server Availability Group Stored Procedure System Administration System Security VMware VMware Administration Windows Windows Batch Script Windows Server

Social

  • View facar1987’s profile on Twitter
  • View facar’s profile on LinkedIn

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 17 other subscribers
©2026 Fatih Acar's blog | Built using WordPress and Responsive Blogily theme by Superb