Oracle 12c R2 Error Codes and Solution Suggestions from ORA-10260 to ORA-10590
- ORA-10260: PGA limit (string MB) exceeded – process terminated
Cause: The Resource Manager SESSION_PGA_LIMIT directive was exceeded because the process used too much program global area (PGA) memory.
Action: Reduce the complexity of the update or query, or contact your database administrator for more information.
Cause: The limit was one kilobyte times the level of the event. If the PGA grows bigger than this, signal an external error.
Action: n/a
Cause: Setting this event to level one causes memory leak checking to be disabled. Setting this event to any other non-zero number allows that number to be used as a threshold value when checking for memory leaks in the PGA, SGA, and UGA heaps.
Action: n/a
Cause: This is useful for debugging since watchpoints are lost on free
Action: n/a
Cause: so test system files don’t diff
Action: n/a
Cause: Porters should implement this to help them debug their stack implementations. It should be used in at least smcstk().
Action: n/a
Cause: Some tests may generate internal or fatal errors on purpose.
Action: LEVEL used by KSEDMP is one less than level of this event.
Cause: setting this event keeps kts from coalescing forward at each extent when dropping a temp segment.
Action: n/a
Cause: setting this event prevents SMON from doing free space coalesces
Action: n/a
Cause: Enables debugging code in shared cursor management modules
Action: n/a
- ORA-10271: distributed transaction after COLLECT
- ORA-10272: distributed transaction before PREPARE
- ORA-10273: distributed transaction after PREPARE
- ORA-10274: distributed transaction before COMMIT
- ORA-10275: distributed transaction after COMMIT
- ORA-10276: distributed transaction before FORGET
- ORA-10277: Cursor sharing (or not) related event (used for testing)
- ORA-10278: Internal testing
- ORA-10279: Simulate block corruption in kdb4chk
- ORA-10280: Internal testing – segmentation fault during crash recovery
- ORA-10281: maximum time to wait for process creation
Cause: used to override the default SPMXWAIT, level = timeout in sec.
Action: n/a
Cause: Used in KSB
Action: n/a
Cause: Used in KCF, level=1 out of space (red), level=2 infinite (green)
Action: n/a
- ORA-10285: Simulate control file header corruption
- ORA-10286: Simulate control file open error
- ORA-10287: Simulate archiver error
- ORA-10288: Do not check block type in ktrget
- ORA-10289: Do block dumps to trace file in hex rather than fromatted
- ORA-10290: Internal sequence tracing event
- ORA-10291: die in tbsdrv to test control file undo
- ORA-10294: ksrpc tracing
- ORA-10296: disable ORA-379
- ORA-10298: ksfd i/o tracing
- ORA-10299: Trace prefetch tracking decisions made by CKPT
- ORA-10301: Enable LCK timeout table consistency check
- ORA-10319: Trace PGA statistics maintenance
- ORA-10320: Enable data layer (kdtgrs) tracing of space management calls
- ORA-10322: CBO don’t simplify inlist predicates
- ORA-10323: before committing an add datafile command
- ORA-10324: Enable better checking of redo logs errors
- ORA-10336: Do remote object transfer using remote SQL
- ORA-10338: CBO don’t use inlist iterator with function-based indexes
- ORA-10339: CBO disable DECODE simplification
- ORA-10341: Simulate out of PGA memory in DBWR during object reuse
- ORA-10342: Raise unknown exception in ACQ_ADD when checkpointing
- ORA-10343: Raise an out of memory exception-OER 4031 in ACQ_ADD
- ORA-10345: validate queue when linking or unlinking a buffer
- ORA-10346: check that all buffers for checkpoint have been written
- ORA-10347: dump active checkpoint entries and checkpoint buffers
- ORA-10349: do not allow ckpt to complete
- ORA-10350: Simulate more than one object & tsn id in object reuse
- ORA-10351: size of slots
- ORA-10352: report direct path statistics
- ORA-10353: number of slots
- ORA-10354: turn on direct read path for parallel query
- ORA-10355: turn on direct read path for scans
- ORA-10356: turn on hint usage for direct read
- ORA-10357: turn on debug information for direct path
- ORA-10358: Simulate out of PGA memory in cache advisory reset
- ORA-10359: turn off updates to control file for direct writes
- ORA-10365: turn on debug information for adaptive direct reads
- ORA-10366: kgnfs tracing
- ORA-10367: kgodm tracing
- ORA-10368: maximum number of internal errors a process will tolerate
- ORA-10369: test SQL monitoring feature
- ORA-10375: turn on checks for statistics rollups
- ORA-10376: enable archive compression loads
- ORA-10378: force hard process/range affinity
- ORA-10380: kxfp latch cleanup testing event
- ORA-10381: kxfp latch cleanup testing event
- ORA-10383: auto parallelization testing event
- ORA-10384: parallel dataflow scheduler tracing
- ORA-10385: parallel table scan range sampling method
- ORA-10386: parallel SQL hash and range statistics
- ORA-10390: Trace parallel query slave execution
- ORA-10391: trace PX granule allocation/assignment
- ORA-10392: parallel query debugging bits
- ORA-10393: print parallel query statistics
- ORA-10394: generate a fake load to test adaptive and load balancing
- ORA-10395: adjust sample size for range table queues
- ORA-10397: suppress verbose parallel coordinator error reporting
- ORA-10398: enable timeouts in parallel query threads
- ORA-10399: trace buffer allocation
- ORA-10400: turn on system state dumps for shutdown debugging
- ORA-10401: turn on IPC (ksxp) debugging
- ORA-10402: turn on IPC (skgxp) debugging
- ORA-10403: fake CPU number for default degree of parallelism
- ORA-10404: crash dbwr after write
- ORA-10405: emulate broken mirrors
- ORA-10406: enable datetime TIMESTAMP, INTERVAL datatype creation
- ORA-10407: enable datetime TIME datatype creation
- ORA-10408: disable OLAP builtin window function usage
- ORA-10409: enable granule memset and block invalidation at startup
- ORA-10450: signal ctrl-c in kdddca (drop column) after n rows
- ORA-10451: Force heap segment compression bypassing compatibility checks
- ORA-10452: Cannot do block media recovery; media recovery session may be in progress
Cause: A media recovery, RMAN, or flashback database session may have been in progress when an attempt was made to perform block media recovery on the standby database.
Action: Check for and cancel any conflicting recovery session and perform block media recovery on the standby database.
Cause: A media recovery, RMAN, or flashback database session may have been in progress on a mounted instance of a standby database when an attempt was made to open the standby database.
Action: Check for and cancel any conflicting recovery session and open the standby database.
Cause: A media recovery session was in progress on a standby database when an attempt was made to close the standby database.
Action: Cancel the media recovery session and close the standby database.
Cause: A standby database was in a state requiring media recovery when an attempt was made to open the standby database.
Action: Perform the necessary recovery and open the standby database.
Cause: An attempt was made to perform media recovery on a standby database while another instance was performing recovery on the standby database, had the standby database open, or a data file move operation was in progress.
Action: Close the standby on all other instances, cancel any conflicting recovery session or data file move operation, and perform manual recovery.
- ORA-10460: Perform backward tablescans for consistent read reduction
- ORA-10461: Simulate control file corruption during write operation
- ORA-10462: enable recovery debug module
- ORA-10469: error creating control file backup, no checkpoint
Cause: The control file being backed up did not contain a valid control file checkpoint. Therefore the control file could not be backed up, as such a backup would not be usable later for recovery. A common cause for this situation is that you executed CREATE CONTROLFILE, which mounts the database, but not ALTER DATABASE OPEN, to open the database. The latter operation generates a valid control file checkpoint.
Action: Open the database with ALTER DATABASE OPEN …, which results in a valid control file checkpoint. Run the backup operation again.
Cause: Flashback was enabled for the data file when the backup data block used for block media recovery had an unlogged change.
Action: Remove the data file from the flashback set or use a backup block that does not contain an unlogged change to perform block media recovery.
Cause: Automatic block repair failed when trying to repair an offline or read-only data file.
Action: Bring the data file online in read/write mode.
Cause: The Real-Time Query feature was enabled when an attempt was made to recover through migration redo generated during primary upgrades or downgrades.
Action: Close the standby database in order to recover through migration redo. Reenable the Real-Time Query feature afterwards.
- ORA-10493: Return empty define buffers on 1422
- ORA-10496: Turn off fix for bug 2554178
- ORA-10498: Trim blank characters including contol characters
- ORA-10501: periodically check selected heap
- ORA-10502: CBO disable the fix for bug 2098120
- ORA-10503: enable user-specified graduated bind lengths
- ORA-10504: CBO disable the fix for bug 2607029
- ORA-10505: CBO enable dynamic sampling dump to table
- ORA-10506: Disable fix for bug 2588217
- ORA-10507: Trace bind equivalence logic
- ORA-10508: Enable fix for bug 14772545
- ORA-10509: Check kghu subheaps at call boundaries
- ORA-10510: turn off SMON check to offline pending offline rollback segment
- ORA-10511: turn off SMON check to cleanup undo dictionary
- ORA-10512: turn off SMON check to shrink rollback segments
- ORA-10515: turn on event to use physical cleanout
- ORA-10519: enable ALTER TYPE RESET support
- ORA-10520: recreate view only if definition has changed
- ORA-10522: turn off wrap source compression
- ORA-10523: force recreate package even if definition is unchanged
- ORA-10525: Disable automatic object validation for describe
- ORA-10526: enables lightweight thread tracing
Cause: Used in ksolt.
Action: Set this event only under the supervision of Oracle Support Services.
Cause: Used for logging events during SGA allocation.
Action: Set this event only under the supervision of Oracle Support Services.
Cause: Used in ksmg module.
Action: Set this event only under the supervision of Oracle Support Services.
Cause: A lightweight thread spawn failed.
Action: Check the alert or trace files for more information.
Cause: A lightweight thread unit test failed.
Action: Check the alert or trace files for more information.
Cause: A lighweight thread encountered an internal error.
Action: Check the alert or trace files for more information and contact Oracle Support Services.
Cause: An attempt was made to perform block media recovery on the standby database when the necessary redo was not available.
Action: Wait until the necessary redo is available and reattempt block media recovery.
Cause: An attempt was made to perform block media recovery on the standby database up to scn %s, which is greater than the highest scn of %s yet applied at the standby.
Action: Recover the standby up to scn %s and reattempt block media recovery.
Cause: An attempt was made to perform block media recovery on a read-only plugged-in datafile.
Action: Convert the plugged-in datafile to read/write and reattempt block media recovery.
Cause: An attempt was made to perform block media recovery using a backup of a read-only plugged-in datafile.
Action: Reattempt block media recovery using a backup taken after the plugged-in datafile has been converted to read/write.
- ORA-10550: signal error during create as select/create index after n rows
- ORA-10551: Internal testing for ORA-1551 error handling
- ORA-10553: Incompatible UNTIL CONSISTENT clause
Cause: RECOVER UNTIL CONSISTENT required database-level recovery with a backup control file.
Action: Omit the UNTIL CONSISTENT clause and retry recovery.
Cause: Media recovery couldn’t recover database to a consistent point due to the specified datafile.
Action: Restore a backup of the datafile.
Cause: Report block type for details of another error.
Action: See associated error message.
Cause: Report block type and data object number for details of another error.
Action: See associated error message.
Cause: See other errors on error stack.
Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block.
- ORA-10563: Test recovery had to corrupt data block (file# string, block# string) in order to proceed
Cause: Test recovery completed.
Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary of the result of the test recovery.
Cause: Report tablespace name for details of another error.
Action: See associated error message.
Cause: There can only be one test recovery session at any time. Another test recovery session is active.
Action: Wait till the other test recovery session completes.
Cause: Test recovery tests redo in memory. It can no longer proceed because it has consumed all the memory it can use.
Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary result of the test recovery.
- ORA-10567: Redo is inconsistent with data block (file# string, block# string, file offset is string bytes)
Cause: There are two possible causes of this error: (1) A write issued by Oracle was lost by the underlying OS or storage system. (2) an Oracle internal error.
Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block.
Cause: out of SGA memory
Action: Restart the instance. If problem persists, call Oracle support.
Cause: Test recovery completed.
Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary result of the test recovery.
Cause: User canceled test recovery.
Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary of the result of the test recovery.
Cause: See other errors on the error stack.
Action: See other messages on error stack. It is possible that no action is needed. See other messages on error stack for a summary of the result of the test recovery so far.
Cause: This message show the range of test recovery have tested.
Action: No action is needed. See other messages on error stack.
Cause: This message summarizes test recovery result.
Action: No action is needed. See other messages on error stack.
Cause: There were not enough memory to restore recovered datafiles to consistent state
Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again.
Cause: See alert file or other errors on the stack for a cause of the problem.
Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again.
Cause: Test recovery option is used for managed standby database recovery.
Action: Either remove the test recovery option or invoke manual test standby database recovery.
Cause: You used the allow corruption option for managed standby database recovery.
Action: Either remove the allow corruption option or invoke manual standby database recovery.
Cause: To proceed with recovery, test recovery needs to modify the control file. But test recovery is not allowed to modify control file.
Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.
Cause: To proceed with recovery, test recovery needs to modify a datafile header. But test recovery is not allowed to modify datafile headers.
Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.
Cause: To proceed with recovery, test recovery needs to modify a redo log header. But test recovery is not allowed to modify redo log headers.
Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.
Cause: User requested backup control file test recovery, but the control file is not a backup control file.
Action: Use a backup control file, or do not use USING BACKUP CONTROLFILE option.
Cause: One of the files to be recovered is renamed as missing.
Action: Rename the file to the correct file or offline it.
Cause: Both test recovery and parallel recovery are requested.
Action: Drop either one of the two recovery options.
Cause: Test recovery has encountered a special redo that may modify control file.
Action: No action is needed. Test recovery has proceeded successfully as far as it could from its starting point.
Cause: This message summarizes test recovery result: Oracle may have to corrupt one block in order to apply the range of redo tested.
Action: See alert log for details of the problem.
Cause: The number specified in the ALLOW n CORRUPTION option is too big.
Action: Use a smaller number.
- ORA-10588: media recovery file header validation
- ORA-10589: Test recovery had to corrupt string data blocks in order to proceed
Cause: This message summarizes test recovery result: Oracle may have to corrupt a number of data blocks as specified in the message in order to apply the range of redo tested.
Action: See alert log for details of the problems.