Oracle 11g Error Codes and Solution Suggestions from ORA-10200 to ORA-10500
- ORA-10243: simulated error for test string of K2GTAB latch cleanup
- Cause: levels 1..6 for insert, 7..11 for delete
- Action: None
- ORA-10244: make tranids in error msgs print as 0.0.0 (for testing)
- Cause: also makes “alter system enable distributed recovery” synchronous
- Action: None
- ORA-10259: get error message text from remote using explicit call
- Cause: for npigem coverage testing (normally called only for V5 remote)
- Action: None
- ORA-10260: limit size (string) of the PGA heap set by event 10261 exceeded
- Cause: The PGA memory use exceeded the limit set by the event 10261.
- Action: Check event 10261 settings.
- ORA-10261: Limit the size of the PGA heap
- Cause: the limit is one kilobyte times the level of the event. If the pga grows bigger than this signal an internal error.
- Action: None
- ORA-10262: Don’t check for memory leaks
- 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: None
- ORA-10263: Don’t free empty PGA heap extents
- Cause: This is useful for debugging since watchpoints are lost on free
- Action: None
- ORA-10265: Keep random system generated output out of error messages
- Cause: so test system files don’t diff
- Action: None
- ORA-10266: Trace OSD stack usage
- Cause: Porters should implement this to help them debug their stack implementations. It should be used in at least smcstk().
- Action: None
- ORA-10267: Inhibit KSEDMP for testing
- Cause: Some tests may generate internal or fatal errors on purpose.
- Action: LEVEL used by KSEDMP is one less than level of this event.
- ORA-10268: Don’t do forward coalesce when deleting extents
- Cause: setting this event keeps kts from coalescing forward at each extent when dropping a temp segment.
- Action: None
- ORA-10269: Don’t do coalesces of free space in SMON
- Cause: setting this event prevents SMON from doing free space coalesces
- Action: None
- ORA-10270: Debug shared cursors
- Cause: Enables debugging code in shared cursor management modules
- Action: None
- ORA-10281: maximum time to wait for process creation
- Cause: used to override the default SPMXWAIT, level = timeout in sec.
- Action: None
- ORA-10282: Inhibit signalling of other backgrounds when one dies
- Cause: Used in KSB
- Action: None
- ORA-10284: simulate zero/infinite asynch I/O buffering
- Cause: Used in KCF, level=1 out of space (red), level=2 infinite (green)
- Action: None
- 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.
- ORA-10456: cannot open standby database; media recovery session may be in progress
- 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.
- ORA-10457: cannot close standby database due to active media recovery
- 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.
- ORA-10458: standby database requires recovery
- 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.
- ORA-10459: cannot start media recovery on standby database; conflicting state detected
- 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-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.
- ORA-10481: Backup data block for data file has an unlogged change
- 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.
- ORA-10482: Automatic block repair cannot repair an offline or read-only data file
- 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.
- ORA-10485: Real-Time Query cannot be enabled while applying migration redo.
- 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-10546: Cannot perform block media recovery; standby database does not have requisite redo.
- 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.
- ORA-10547: Cannot perform block media recovery; standby database is not caught up with primary.
- 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.
- ORA-10548: Cannot perform block media recovery on a read-only plugged-in datafile.
- 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.
- ORA-10549: Cannot perform block media recovery using a read-only plugged-in backup datafile.
- 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.