ORA-09870 to ORA-12100
ORA-09870: spini: failure initializing maximum number of open files.
Cause: ulimit system call returned an error.
Action: Check errno.
ORA-09871: TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf.
Cause: Failure of sltln(?/tasdef@.dbf) while creating test and set pages.
Action: Check additional return error for more information.
ORA-09872: TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf.
Cause: Create() failed when trying to create the tasdef file.
Action: Verify permissions on $(ORACLE_HOME)/dbs directory.
ORA-09873: TASDEF_OPEN: open error when opening tasdef@.dbf file.
Cause: Unable to open tasdef@.dbf file.
Action: Check errno. Possible permission problem. Verify that tasdef@.dbf file
exists.
ORA-09874: TASDEF_READ: read error, unable to read tasdef@.dbf file.
Cause: Read system call returned an error when attempting to read
?/dbs/tasdef@.dbf.
Action: Check errno returned. Sgadef file may be corrupted or incompatible with
oracle version.
ORA-09875: TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file.
Cause: Write call failed.
Action: Check errno returned. Possibly out of space on device.
ORA-09876: TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file.
Cause: Close system call returned an error.
Action: Check errno returned. Possible operating system failure.
ORA-09877: sstascre: shmget error, unable to get a shared memory segment.
Cause: Error in shmget.
Action: Check errno returned. Verify that enough shared memory is available on
the system.
ORA-09878: sstascre/sstasat: shmat error, unable to attach tas write page
Cause: Error in shmat.
Action: Check errno returned.Verify that enough shared memory is available on
the system.
ORA-09879: sstascre/sstasat: shmat error, unable to attach tas read page
Cause: Error in shmat.
Action: Check errno returned.Verify that enough shared memory is available on
the system.
ORA-09880: sstasfre/sstasdel: shmdt error, unable to detach tas write page
Cause: Error in shmdt.
Action: Check errno returned.
ORA-09881: sstasfre/sstasdel: shmdt error, unable to detach tas read page
Cause: Error in shmdt.
Action: Check errno returned.
ORA-09882: sstasfre/sstasdel: shmctl error, unable to remove tas shm page
Cause: Error in shmctl.
Action: Check errno returned.
ORA-09883: Two Task interface: oratab file does not exist
Cause: The oratab file does not exist.
Action: Install oracle before you use it or recreate the oratab file.
ORA-09884: Two Task interface: SID doens”t match current PU
Cause: You are trying to start oracle on another PU than you configured oracle on
or there is no entry for this SID in oratab file.
Action: Start oracle with this SID on its designated PU (see oratab file). Or install
the new database with SID.
ORA-09885: osnTXtt: cannot create TXIPC channel
Cause: The TXIPC driver failed to create pipes for two-task communications with
the oracle shadow process.
Action: You have probably exceeded the maximum number of open file
descriptors per user or the system file table is full. Note the operating system error
code and contact your system administrator.
ORA-09886: osnTXtt: translation error while expanding txipc@.trc.
Cause: Failure of sltln(txipc@.trc) while creating debug channel.
Action: Check additional return error for more information.
ORA-09888: osnTXtt: txipc channel creation failed
Cause: The txipc driver failed to create channels for two-task communications
with the oracle shadow process.
Action: You have probably exceeded the maximum number of open file
descriptors per user or the system file table operating system error code and
contact your system administrator.
ORA-09889: osnTXtt: access error on oracle executable
Cause: The txipc driver could not access the oracle executable.
Action: Check the permissions on the ORACLE executable and each component
of the ORACLE_HOME/bin path.
ORA-09890: osnTXtt: malloc failed
Cause: The txipx driver failed to allocate enough heap space for its context area
buffers.
Action: Contact your customer support representative.
ORA-09908: slkmnm: gethostname returned error code.
Cause: The system call gethostname returned an error.
Action: This is most likely an internal error. Make sure gethostname is successful
in other contexts, and if so contact Oracle support.
ORA-09909: Malloc of scratch buffer failed.
Cause: Memory needed for a temporary buffer could not be allocated. The
additional information field contains the number of bytes that ORACLE attempted
to allocate.
Action: Check the UNIX error number. It is probable that the system has run out
of memory. If there is no error, contact ORACLE support.
ORA-09910: Unable to find ORACLE password file entry for user.
Cause: No entry exists for the user in the ORACLE password file.
Action: Have the database administrator install a password entry by running
orapasswd.
ORA-09911: Incorrect user password.
Cause: The password entered by the user was incorrect.
Action: Enter the correct password.
ORA-09912: Malloc of name buffer(s) failed.
Cause: ORACLE was unable to allocate memory for one or both of the buffers
that are used to hold the name of DBA and the operator users.
Action: Check the UNIX error number. It is probable that the system has run out
of memory. If there is no error, contact ORACLE support.
ORA-09913: Malloc of dummy name failed.
Cause: ORACLE was unable to allocate memory for the user name that is to to be
used in the encryption of the user”s password.
Action: Check the UNIX error number. It is probable that the system has run out
of memory. If there is no error, contact ORACLE support.
ORA-09914: Unable to open the ORACLE password file.
Cause: ORACLE could not open the password file for reading.
Action: Check the UNIX error number. If the error number indicates that the file
does not exist, have the database administrator create the file by running
orapasswd. If the error number indicates insufficient permissions, ask the database
administrator to change the permissions. Otherwise, contact ORACLE customer
support.
ORA-09915: Password encryption failed.
Cause: ORACLE was unable to encrypt a password.
Action: This is an internal error – contact ORACLE customer support.
ORA-09916: Required password was not specified.
Cause: A user attempted to connect as “internal,” but did not specify a password.
Action: Connect as internal again and specify a password.
ORA-09918: Unable to get user privileges from SQL*Net
Cause: ORACLE was unable to retrieve the user”s privilege set from the SQL*Net
connection.
Action: Check the UNIX error number for a possible operating system error. Also
check the “additional information” field for the SQL*Net error. If there is no error,
contact ORACLE support.
ORA-09919: Unable to set label of dedicated server
Cause: ORACLE was unable to set the label of the dedicated to server to the
required value.
Action: Check the UNIX error number for a possible operating system error. Also,
check the privileges on the oracle executable. It should have at least
“allowmacaccess” privilege.
ORA-09920: Unable to get sensitivity label from connection
Cause: ORACLE was unable to retrieve the user”s sensitivity label from the
SQL*Net connection.
Action: Check the UNIX error number for a possible operating system error. Also
check the “additional information” field for the SQL*Net error. If there is no error,
contact ORACLE support.
ORA-09921: Unable to get information label from connection
Cause: ORACLE was unable to retrieve the user”s information label from the
SQL*Net connection.
Action: Check the UNIX error number for a possible operating system error. Also
check the “additional information” field for the SQL*Net error. If there is no error,
contact ORACLE support.
ORA-09922: Can”t spawn process – background log directory not created properly
Cause: ORACLE was unable to spawn a background process because the
directory that will hold trace files of the background processes was not created
properly.
Action: Examine the directory pointed to by the initialization parameter
“background_dump_dest”. Make sure that all of the following is true:
1. The directory exists.
2. The name indeed points to a directory, and is not a file.
3. The directory is accessible and writable to the ORACLE user.
ORA-09923: Can”t spawn process – user log directory not created properly
Cause: ORACLE was unable to spawn a background process because the
directory that holds the trace files of the dedicated server processes was not
created properly.
Action: Examine the directory pointed to by the initialization parameter “user_
dump_dest”. Make sure that all of the following is true:
1. The directory exists.
2. The name indeed points to a directory, and is not a file.
3. The directory is accessible and writable to the ORACLE user.
ORA-09924: Can”t spawn process – core dump directory not created properly
Cause: ORACLE was unable to spawn a background process because the
directory that holds the core dumps produced by ORACLE processes in the event
of exceptions was not created properly.
Action: Examine the directory pointed to by the initialization parameter “core_
dump_dest”. Make sure that all of the following is true:
1. The directory exists.
2. The name indeed points to a directory, and is not a file.
3. The directory is accessible and writable to the ORACLE user.
ORA-09925: Unable to create audit trail file
Cause: ORACLE was not able to create the file being used to hold audit trail
records.
Action: Check the UNIX error number for a possible operating system error. If
there is no error, contact ORACLE customer support.
ORA-09926: Unable to set effective privilege set of the server
Cause: A dedicated server was unable to set it”s own privilege set.
Action: Check the privileges granted to the ORACLE executable. It must have at
least “allowmacacess” privilege.
ORA-09927: Unable to set label of server
Cause: ORACLE was not able to set the label of a server to a new value.
Action: Check the privileges on $ORACLE_HOME/bin/oracle. Make sure that it
has “allowmacaccess” privilege.
ORA-09928: Unable to restore the label of server
Cause: ORACLE was unable to restore the label of the server to the value that it
had before raising it to database high.
Action: This is an internal error – contact ORACLE support.
ORA-09929: GLB of two labels is invalid
Cause: The result of a greatest lower bound operation on two labels was not valid.
Action: Repeat the operation with two different labels. Consult the system
encoding file for the values of valid labels.
ORA-09930: LUB of two labels is invalid
Cause: The result of a least upper bound operation on two labels was not valid.
Action: Repeat the operation with two different labels. Consult the system
encoding file for the values of valid labels.
ORA-09931: Unable to open ORACLE password file for reading
Cause: An attempt to open a password file for reading failed.
Action: Make sure that the permissions on the file have not been changed so that
the ORACLE user cannot open it.
ORA-09932: Close of ORACLE password file failed.
Cause: An attempt to close a password file failed.
Action: Check the UNIX error number for the specific reason.
ORA-09933: Deletion of old password file failed.
Cause: The removal of the old password file failed.
Action: Check the UNIX error number for the specific reason.
ORA-09934: Link of current password file to old failed.
Cause: ORACLE was unable to create a link so that the old password file could be
saved.
Action: Check the UNIX error number for the specific reason.
ORA-09935: Unlink of current password file failed.
Cause: ORACLE was unable to complete the saving of the current password file.
Action: Check the UNIX error number for the specific reason.
ORA-09936: Open of ORACLE password file for write failed.
Cause: ORACLE was unable to create a password file.
Action: Check the UNIX error number for the specific reason.
ORA-09937: Chmod of ORACLE password file failed.
Cause: ORACLE was unable to change a password file to be readonly.
Action: Check the UNIX error number for the specific reason.
ORA-09938: Save of signal handlers failed.
Cause: ORACLE was unable to save the previous values of selected signal
handlers.
Action: This is an internal error. Contact ORACLE support.
ORA-09939: Restoration of signal handlers failed.
Cause: ORACLE was unable to restore the previous values of selected signal
handlers.
Action: This is an internal error. Contact ORACLE support.
ORA-09940: ORACLE password file header is corrupt
Cause: The header of one of the password files was not in the format that
ORACLE expected.
Action: Check the headers of both files. The header should be in the format “FILE
VERSION: N.N.N.N.N EXECUTABLE VERSION: N.N.N.N.N” where N is a
number. Remove the corrupt file(s) and re-run “orapasswd”.
ORA-09941: Version of orapasswd or installer is older than file.
Cause: The version of orapasswd or installer that is being run is older than that of
the ORACLE password file. Since the file version is only changed when the format
is changed, this error means that the executable is using a different format than
that with which the file was created.
Action: Run a version of the installer or orapasswd whose version is the same or
later than that of the file.
ORA-09942: Write of ORACLE password file header failed.
Cause: The attempt to write out the header of the ORACLE password file failed.
Action: Check the operating system error number. It is possible that the file
system became full.
ORA-09943: Allocation of memory for password list component failed.
Cause: When it is building a list of password file entries, ORACLE allocates
memory for various components. One of the allocations failed.
Action: Check the operating system error number. The system has probably run
out of memory.
ORA-09944: Password entry is corrupt.
Cause: An entry in an ORACLE password file was not in the format that
ORACLE expected.
Action: Removed the corrupt file(s) and re-run “orapasswd.”
ORA-09945: Unable to initialize the audit trail file
Cause: ORACLE unable to write header information to the file being used as the
audit trail.
Action: Check the UNIX error number for a possible operating system error. If
there is no error, contact ORACLE customer support.
ORA-09946: File name too long for buffer
Cause: The buffer that was to be used to hold a file name was determined to be
too short for the generated name. This will happen if the translated name for
either a trace file or an audit file is longer than the maximum allowed, which on
many ports is 256 characters.
Action: Use a shorter file name.
ORA-09947: Unable to allocate connection attributes structure
Cause: ORACLE was not able to allocate the memory needed to hold the
attributes of the SQL*Net connection. The “Additional Information” field holds the
number of bytes that ORACLE attempted to allocate.
Action: Check the UNIX error number. It is probable that the system has run out
of memory. If there is no error, contact ORACLE customer support.
ORA-09948: Process information label retrieval failed.
Cause: ORACLE was unable to get the information label for a process.
Action: Check the UNIX error number for a possible operating system failure. If
there is no error, contact ORACLE support.
ORA-09949: Unable to get client operating system privileges
Cause: ORACLE was unable to get the operating system privileges for the client
process.
Action: Check the UNIX error number for a possible operating system failure. If
there is no error, contact ORACLE support.
ORA-09950: Unable to get server operating system privileges
Cause: ORACLE was unable to get its privileges from the operating system.
Action: This is an error that should never happen. Contact ORACLE customer
support.
ORA-09951: Unable to create file
Cause: ORACLE was unable to create a file.
Action: Check the UNIX error number for a possible operating system failure. If
there is no error, contact ORACLE support.
ORA-09952: scgcmn: lk_open_convert unexpected return: open failed
Cause: The distributed lock manager returned an unexpected value
Action: Check for system error message and refer to the distributed lock manager
documentation or contact your customer support representative.
ORA-09953: scggc: unexpected return of a lock convert
Cause: The distributed lock manager returned an unexpected value
Action: Check for lock manager error message and refer to DLM documentation
refer to the distributed lock manager documentation or contact your customer
support representative.
ORA-09954: scgcc: unexpected return status to callback of lock close
Cause: The distributed lock manager returned an unexpected value
Action: Check for lock manager error message and refer to DLM documentation
refer to the distributed lock manager documentation or contact your customer
support representative.
ORA-09955: scgcan: unexpected return status when canceling a lock
Cause: DLM system service x returned an unexpected value
Action: Check for system error message and refer to DLM documentation refer to
the distributed lock manager documentation or contact your customer support
representative.
ORA-09956: scgcm: unexpected lock status condition
Cause: A global locking system service returned an unexpected value.
Action: Check for system error message (if any) and refer to refer to the
distributed lock manager documentation or contact your customer support
representative.
ORA-09957: Unable to send termination request to IMON
Cause: The attempt to send a termination signal to IMON failed.
Action: This is an internal error, contact ORACLE support.
ORA-09958: IMON: two processes with the same ORACLE pid are active
Cause: The IMON process was unable to add an entry for a server process
because another active process occupies the slot.
Action: This is an internal error, contact ORACLE support.
ORA-09959: IMON: deletion of a process failed.
Cause: The IMON process was unable to delete a server process from its process
ID array because no entry for the process could be found.
Action: This is an internal error, contact ORACLE support.
ORA-09960: Unable to establish signal handler for termination signal
Cause: ORACLE was unable to set up a handler for the signal used to notify it
that the instance was shutting down.
Action: This is an internal error, contact ORACLE support.
ORA-09961: Unable to restore termination signal handler
Cause: ORACLE failed to set the handler for the termination signal to its previous
value.
Action: This is an internal error, contact ORACLE support.
ORA-09966: falure in translation while expanding ?/dbs/lk for lock file
Cause: Oracle failed to translate ?/dbs/lk, when creating a file name for the
database mount lock or the instance startup/shutdown lock.
Action: Check additional return errors for more information.
ORA-09967: unable to create or open lock file
Cause: Oracle failed, when making an open system call, inorder to acquire a file
lock used by the database mount lock or the instance startup/shutdown lock.
Action: Check errno for more information.
ORA-09968: unable to lock file
Cause: The system call for locking a file returned an error when trying to acquire
a database mount lock or the instance startup/shutdown lock.
Action: Check errno for more information.
ORA-09969: unable to close or remove lock file
Cause: The close system call or unlink system call returned an error.
Action: Check errno for more information.
ORA-09974: skxfidini: Error Initializing SDI Channel
Cause: The process was unable to initialize the SDI channel properly.
Action: Correct the operating system error and retry the operation.
ORA-09975: kxfspini: Error Initializing SDI Process
Cause: The process was unable to attach to the SDI channel.
Action: Verify that the SDI process specific limits correctly configured. Correct the
operating system error and retry the operation.
ORA-09976: skxfqdini: Error Creating Port
Cause: The process was unable to create a communications endpoint.
Action: Verify that the SDI port specific limits correctly configured. Correct the
operating system error and retry the operation.
ORA-09977: skxfqhini: Error Connecting
Cause: The process was unable to connect to another endpoint.
Action: Verify that the SDI port specific limits correctly configured. Check that the
other node(s) is part of the cluster and operating properly. Correct the operating
system error and retry the operation.
ORA-09978: skxfqhdel: Error Disconnecting from another endpoint.
Cause: The process was unable to disconnect cleanly from another endpoint.
Action: Check that the other node(s) are part of the cluster and operating
properly. Check the instance and processes on the other node(s). Correct the
operating system error and retry the operation.
ORA-09979: skxfqhsnd: Error Sending a message to another endpoint
Cause: The process was unable to send a message to an existing endpoint.
Action: Check that the other node(s) are part of the cluster and operating
properly. Check the instance and processes on the other node(s). Correct the
operating system error and retry the operation.
ORA-09980: skxfqdrcv: Error Receiving a message from another endpoint
Cause: The process encountered an error while trying to receive a message.
Action: Check that the other node(s) are part of the cluster and operating
properly. Check the instance and processes on the other node(s). Correct the
operating system error and retry the operation.
ORA-09981: skxfqdreg: Error Adding a page to the SDI buffer pool
Cause: The process was unable to add a page to the SDI buffer pool.
Action: Correct the operating system error and retry the operation.
ORA-09982: skxfqddrg: Error Removing a page from the SDI buffer pool
Cause: The process was unable to remove a page to the SDI buffer pool.
Action: Correct the operating system error and retry the operation.
ORA-09983: skxfidsht: Error shutting down SDI channel
Cause: The process was unable shut down the SDI channel
Action: Check the SDI persistent resources using SDI tools. Verify that all
processes exited cleanly and the instance is safely shut down. Delete any
remaining SDI channel IDs associated with the current instance.
ORA-09984: SGA file $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf does not
exist
Cause: file does not exist or is not accessible
Action: Restart the instance to create the SGA definition file.
ORA-09985: SGA definition file could not be read
Cause: UNIX read() operation failed
Action: check errno and take appropriate action.
ORA-09986: wrong number of bytes read from SGA definition file
Cause: Struct skgmsdef size differs from no. of bytes read from SGA file
Action: Compare the two struct definitions and ensure that they are identical in
size and structure.
ORA-09987: unable to attach to SGA in READ-ONLY mode
Cause: The instance is not up, or SGA segments are not read-accessible
Action: Verify that the instance is up and read permissions for the SGA segments
are set.
ORA-09988: error while detaching SGA
Cause: skgmsdef struct is corrupted and/or segment addresses are modified
Action: Safely shut down instance and mount SGA segments again.
ORA-09989: attempt to use invalid skgmsdef struct pointer
Cause: Pointer to skgmsdef struct used without validating it
Action: Assign a valid address to the skgmsdef struct pointer before using it.
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-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-10360: enable dbwr consistency checking
Cause: internal use only
Action: enables consistency checking of buffers written by dbwriter and
consistency checking of LRU working sets
ORA-10361: check buffer change vector count consistency
Cause: internal use only
Action: invoke buffer change vector count consistency every 5 minutes
ORA-10362: simulate a write error to take a file offline
Cause: internal use only
Action: Enables testing of DBWR taking a file offline because of a write error. The
level is the absolute file number of the file to be taken offline when DBWR attemts
to write to it.
ORA-10364: Do not clear GIMH_STC_SHUT_BEGIN state during shutdown
Cause: internal use only
Action: Enables testing of shutdown begin event by not clearing GIMH_STC_
SHUT_BEGIN state before shutdown completes.
ORA-10370: parallel query server kill event
Cause: internal use only
Action: this event should never be set externally
ORA-10371: disable TQ hint
Cause: internal use only
Action: this event should never be set externally
ORA-10372: parallel query server kill event proc
Cause: internal use only
Action: this event should never be set externally
ORA-10373: parallel query server kill event
Cause: internal use only
Action: this event should never be set externally
ORA-10382: parallel query server interrupt (reset)
Cause: internal use only
Action: this event should never be set externally
ORA-10387: parallel query server interrupt (normal)
Cause: internal use only
Action: this event should never be set externally
ORA-10388: parallel query server interrupt (failure)
Cause: internal use only
Action: this event should never be set externally
ORA-10389: parallel query server interrupt (cleanup)
Cause: internal use only
Action: this event should never be set externally
ORA-10560: block type “string”
Cause: Report block type for details of another error.
Action: See associated error message.
ORA-10561: block type “string”, data object# string
Cause: Report block type and data object number for details of another error.
Action: See associated error message.
ORA-10562: Error occurred while applying redo to data block (file# string, block#
string)
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.
ORA-10564: tablespace string
Cause: Report tablespace name for details of another error.
Action: See associated error message.
ORA-10565: Another test recovery session is active
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.
ORA-10566: Test recovery has used all the memory it can use
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)
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.
ORA-10568: Failed to allocate recovery state object: out of SGA memory
Cause: out of SGA memory
Action: Restart the instance. If problem persists, call Oracle support.
ORA-10570: Test recovery complete
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.
ORA-10571: Test recovery canceled
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.
ORA-10572: Test recovery canceled due to errors
Cause: See other errors on the error stack.
Action: is needed. See other messages on error stack for a summary of the result
of the test recovery so far.
ORA-10573: Test recovery tested redo from change string to string
Cause: This message show the range of test recovery have tested.
Action: No action is needed. See other messages on error stack.
ORA-10574: Test recovery did not corrupt any data block
Cause: This message summarizes test recovery result.
Action: No action is needed. See other messages on error stack.
ORA-10575: Give up restoring recovered datafiles to consistent state: out of memory
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.
ORA-10576: Give up restoring recovered datafiles to consistent state: some error
occurred
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.
ORA-10577: Can not invoke test recovery for managed standby database recovery
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.
ORA-10578: Can not allow corruption for managed 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.
ORA-10579: Can not modify control file during test 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.
ORA-10580: Can not modify datafile header during test recovery
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.
ORA-10581: Can not modify redo log header during test recovery
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.
ORA-10582: The control file is not a backup control file
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.
ORA-10583: Can not recovery file string renamed as missing during test recovery
Cause: One of the files to be recovered is renamed as missing.
Action: Rename the file to the correct file or offline it.
ORA-10584: Can not invoke parallel recovery for test recovery
Cause: Both test recovery and parallel recovery are requested.
Action: Drop either one of the two recovery options.
ORA-10585: Test recovery can not apply redo that may modify control file
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.
ORA-10586: Test recovery had to corrupt 1 data block in order to proceed
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.
ORA-10587: Invalid count for ALLOW n CORRUPTION option
Cause: The number specified in the ALLOW n CORRUPTION option is too big.
Action: Use a smaller number.
ORA-10588: Can only allow 1 corruption for normal media/standby recovery
Cause: The number specified in the ALLOW n CORRUPTION option is too big.
Action: change to allow zero or one corruption.
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.
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 kksfbc-reparse-infinite-loop error
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-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: none
ORA-10653: Table is in a cluster
Cause: It is illegal to shrink a table belonging to a cluster
Action: none
ORA-10654: Table is of type temporary or external
Cause: It is illegal to shrink a temporary table or an external table
Action: none
ORA-10655: Segment can be shrunk
Cause: Error message returned when called in probe mode by OEM
Action: none
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 <tablename> PURGE
ORA-10657: Lob column to be shrunk does not exist
Cause: Shrink was issued on a lob segment that did not exist
Action: none
ORA-10658: Lob column to be shrunk is marked unused
Cause: Shrink was issued on a lob segment that is marked as unused
Action: none
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: none
ORA-10660: Segment is a shared lob segment
Cause: Shrink was issued on a segment that was being shared by multiple lob
columns
Action: none
ORA-10661: Invalid option specified
Cause: Check option can be specified for one segment only
Action: none
ORA-10662: Segment has long columns
Cause: Shrink was issued on a segment with long columns. This is not supported.
Action: none
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-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: none
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: 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
ORA-10841: Default un-inintialized charact set form to SQLCS_IMPLICIT
Cause: client side, such as JDBC-THIN 8i client sends 0 as charset form
Action: This event sets charset form as SQLCS_IMPLICIT when it is 0
ORA-10842: Event for OCI Tracing and Statistics Info
Cause: This event is meant for tracing OCI Calls and getting statistics
Action: This event sets tracing OCI Calls and gets statistics info
ORA-10852: Enable tracing for Enqueue Dequeue Operations
Cause: NA
Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT
NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR
INTERNAL TESTING.
ORA-10854: Sets poll count used for AQ listen code under RAC
Cause: NA
Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT
NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR
INTERNAL TESTING.
ORA-10862: resolve default queue owner to current user in enqueue/dequeue
Cause: resolve default queue owner to current user in enqueue/dequeue.
Action: turn on if client wish to resolve the default queue owner to the current
user. If not turned on, the default queue owner will be resolved to the login user.
ORA-10863: Control behavior of buffered background operations
Cause: NA
Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT
NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR
INTERNAL TESTING.
ORA-10865: Control tracing of notification operations
Cause: NA
Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT
NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR
INTERNAL TESTING.
ORA-10900: extent manager fault insertion event #string
Cause: causes faults to be generated in instrumented extent code
Action: this should only be enabled for internal testing
ORA-10902: disable seghdr conversion for ro operation
Cause: causes seghdr conversion to be turned off for ro ops(#555856)
Action: this should be enabled only if determined that bug 555856 has occured.
Table needs to be exported subsequently
ORA-10906: Unable to extend segment after insert direct load
Cause: This is a restriction with insert direct load transactions.
Action: When a segment has been insert direct loaded, avoid DMLs that could
cause more space to be consumed.
ORA-10914: invalid TABLESPACE GROUP clause
Cause: An invalid option appears for TABLESPACE GROUP clause.
Action: Specify a valid tablespace group name.
ORA-10915: TABLESPACE GROUP cannot be specified for this type of tablespace
Cause: In CREATE/ALTER TABLESPACE, the TABLESPACE GROUP clause was
used while creating/altering a tablespace that is not TEMPORARY.
Action: Remove the TABLESPACE GROUP clause.
ORA-10916: TABLESPACE GROUP already specified
Cause: In CREATE/ALTER TABLESPACE, the TABLESPACE GROUP option was
specified more than once.
Action: Remove all but one of the TABLESPACE GROUP specifications.
ORA-10917: TABLESPACE GROUP cannot be specified
Cause: The tablespace name specified in the command is actually the name of a
tablespace group.
Action: Please specify an appropriate tablespace name.
ORA-10918: TABLESPACE GROUP name cannot be the same as tablespace name
Cause: The tablespace group name specified in the command is the same as the
tablespace being CREATEd/ALTERed.
Action: Please specify an appropriate tablespace group name.
ORA-10919: Default temporary tablespace group must have at least one tablespace
Cause: An attempt was made to move the only tablespace in the default database
temporary tablespace group to another tablespace group.
Action: Either change the database default temporary tablespace or add another
tablespace to the group that this tablespace belongs to.
ORA-10920: Cannot offline tablespace belonging to default temporary tablespace
group
Cause: An attempt was made to offline a tablespace in the default database
temporary tablespace group.
Action: Either change the database default temporary tablespace or change the
tablespace group of this tablespace.
ORA-10921: Cannot drop tablespace belonging to default temporary tablespace
group
Cause: An attempt was made to drop a tablespace in the default database
temporary tablespace group.
Action: Either change the database default temporary tablespace or change the
tablespace group of this tablespace.
ORA-10922: Temporary tablespace group is empty
Cause: An attempt was made to allocate a temporary segment in a group, which
now no longer has any members.
Action: Either add some temporary tablespaces or change the temporary
tablespace for this user.
ORA-10924: import storage parse error ignore event
Cause: causes server to ignore specific error associated with freelists and freelist
groups when parsing
Action: this should be enabled by import code only
ORA-10925: trace name context forever
Cause: When enabled, turns off bugfix 237911
Action: set this event ONLY if necessary – after reading the README for this
release or under supervision of Oracle Support.
ORA-10926: trace name context forever
Cause: When enabled, turns off bugfix 190119
Action: set this event ONLY if necessary – after reading the README for this
release or under supervision of Oracle Support.
ORA-10927: trace name context forever
Cause: When enabled, turns off bugfix 235190
Action: set this event ONLY if necessary – after reading the README for this
release or under supervision of Oracle Support.
ORA-10929: trace name context forever
Cause: When enabled, turns off bugfix 343966
Action: set this event ONLY if necessary – after reading the README for this
release or under supervision of Oracle Support.
ORA-10930: trace name context forever
Cause: When enabled, provides V7 behavior for fixed char binds
Action: set this event ONLY if necessary – after reading the README for this
release or under supervision of Oracle Support.
ORA-10931: trace name context forever
Cause: When enabled, allows normal packages to be compiled with standard
extensions like “”
Action: Set this event only for a short amount of time. Once the packages are
compiled, this event should be turned off. Level 1 – Turn the event on Level > 1 –
Turn the event off
ORA-10932: trace name context forever
Cause: When enabled, disables one or more features or bug fixes available only in
version 8.x.
Action: set this event ONLY if necessary – after reading the README for this
release or under supervision of Oracle Support.
ORA-10933: trace name context forever
Cause: When enabled, disables one or more features or bug fixes available only in
version 8.x.
Action: set this event ONLY if necessary – after reading the README for this
release or under supervision of Oracle Support.
ORA-10936: trace name context forever
Cause: When enabled, disables one or more features or bug fixes available in
versions 7.x and 8.x.
Action: set this event ONLY if necessary – after reading the README for this
release or under supervision of Oracle Support.
ORA-10940: trace name context forever
Cause: Size of the PL/SQL tracing circular buffer, in kilobytes.
Action: Set this event in concert with the 10938 event and the _PLSQL_DUMP_
BUFFER_EVENTS init.ora parameter, under supervision of Oracle Support.
ORA-10941: trace name context forever
Cause: When enabled, turns on PL/SQL profiler
Action: set this event ONLY if necessary – after reading the README for this
release or under supervision of Oracle Support.
ORA-10943: trace name context forever
Cause: When enabled, disables one or more features or bug fixes available only in
version 8.x.
Action: set this event ONLY if necessary – after reading the README for this
release or under supervision of Oracle Support.
ORA-10944: trace name context forever
Cause: When enabled, allows or controls PL/SQL OPT code gen project. available
only in version 8.2+.
Action: set this event ONLY for development of the OPT project. This is not for
general use or deployment.
ORA-10945: trace name context forever
Cause: When enabled, disables the behaviour change introduced by the fix for
bug 822764, which traps and handles invalidations of packages whereas the
previous behaviour was to use stale invalidated instantiations of the stateful
package body.
Action: set this event ONLY if necessary – after reading the README for this
release or under supervision of Oracle Support.
ORA-10946: trace name context forever
Cause: When enabled, disables one or more features or bug fixes available only in
version 10.x.
Action: set this event ONLY if necessary – after reading the README for this
release or under supervision of Oracle Support.
ORA-10947: trace name context forever
Cause: When enabled, causes various PL/SQL warnings related debugging info
to be written in a trace file. Useful for debugging varous Oracle processes.
available only in version 10.x.
Action: set this event ONLY if necessary – after reading the README for this
release or under supervision of Oracle Support.
ORA-10948: trace name context forever
Cause: When enabled, inflate callout argument. available only in version 10.x.
Action: internal use only.
ORA-10970: backout event for bug 2133357
Cause: 2133357 dynamically sets the varying width flag and character width. Lob
data which is not migrated during migration from single byte to multibyte
charater set will be displayed as special characters.
Action: To help migrate lob data which was not migrated during migration by
backing out 2133357, so lob data can be selected and moved to multibyte character
set.
ORA-10973: backout evet for 2619509
Cause: 2619509 catches offsets when not reading/writing on full character
boundary. To facilitate backward compatiblity event is being introduced.
Action: To help upgrade/migrate issues which already have corrupt data
ORA-10979: trace flags for join index implementation
Cause: This is an informational message.
Action: Values are as follows: LEVEL ACTION
————————————————————————— > 1 Dump refresh
expressions (SQL) to trace file. > 999 If a complete refresh is invoked, it will not be
performed but the system will assume that a complete refresh was done, causing
the view to be VALID and updating timestamps. This should be used only under
Oracle Support supervision.
ORA-10997: another startup/shutdown operation of this instance inprogress
Cause: An Oracle Instance startup or shutdown operation failed to procure the
serialization primitive. Another foreground process may have attempted startup
or shutdown operation in parallel.
Action: Check additional error messages in the alert log and the process trace file.
ORA-12001: cannot create log: table “string” already has a trigger
Cause: Materialized view logs are filled by a trigger on the master table. That
trigger cannot be created.
Action: To create a materialized view log, drop the current trigger on the master.
ORA-12002: there is no materialized view log on table “string”.”string”
Cause: There was no materialized view log on the master table.
Action: Create a materialized view log on the master table.
ORA-12003: materialized view “string”.”string” does not exist
Cause: The materialized view with the given owner and name does not exist.
Action: Verify inputs and create a materialized view.
ORA-12004: REFRESH FAST cannot be used for materialized view “string”.”string”
Cause: The materialized view log does not exist or cannot be used. PCT refresh is
also not enabled on the materialized view
Action: Use just REFRESH, which will reinstantiate the entire table. If a
materialized view log exists and the form of the materialized view allows the use
of a materialized view log or PCT refresh is possible after a given set of changes,
REFRESH FAST will be available starting the next time the materialized view is
refreshed.
ORA-12005: may not schedule automatic refresh for times in the past
Cause: An attempt was made to schedule an automated materialized view refresh
for a time in the past.
Action: Choose a time in the future instead.
ORA-12007: materialized view reuse parameters are inconsistent
Cause: The CREATE MATERIALIZED VIEW .. or CREATE MATERIALIZED
VIEW LOG .. REUSE command was given inconsistent parameters immediately
after the REUSE.
Action: Examine the other messages on the stack to find the problem.
ORA-12008: error in materialized view refresh path
Cause: Table SNAP$_ reads rows from the view MVIEW$_
, which is a view on the master table (the master may be at a
remote site). Any error in this path will cause this error at refresh time. For fast
refreshes, the table .MLOG$_ is also referenced.
Action: Examine the other messages on the stack to find the problem. See if the
objects SNAP$_, MVIEW$_,
.@, .MLOG$_@ still
exist.
ORA-12010: cannot create materialized view log on table owned by SYS
Cause: An attempt was made to create a materialized view log on the table owned
by SYS. CREATE MATERIALIZED VIEW LOG attempts to create a trigger on the
table, but triggers can not be created on SYS tables.
Action: Do not create a materialized view log on SYS tables.
ORA-12011: execution of string jobs failed
Cause: An error was caught in dbms_ijob.run from one or more jobs which were
due to be run.
Action: Look at the alert log for details on which jobs failed and why.
ORA-12012: error on auto execute of job string
Cause: An error was caught while doing an automatic execution of a job.
Action: Look at the accompanying errors for details on why the execute failed.
ORA-12013: updatable materialized views must be simple enough to do fast refresh
Cause: The updatable materialized view query contained a join, subquery, union,
connect by, order by, or group by caluse.
Action: Make the materialized view simpler. If a join is really needed, make
multiple simple materialized views then put a view on top of them.
ORA-12014: table “string” does not contain a primary key constraint
Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the
WITH PRIMARY KEY option and the master table did not contain a primary key
constraint or the constraint was disabled.
Action: Reissue the command using only the WITH ROWID option, create a
primary key constraint on the master table, or enable an existing primary key
constraint.
ORA-12015: cannot create a fast refresh materialized view from a complex query
Cause: Neither ROWIDs and nor primary key constraints are supported for
complex queries.
Action: Reissue the command with the REFRESH FORCE or REFRESH
COMPLETE option or create a simple materialized view.
ORA-12016: materialized view does not include all primary key columns
Cause: The query that instantiates the materialized view did not include all of the
columns in the master”s primary key constraint.
Action: Include all of the master”s primary key columns in the materialized view
query or create a ROWID materialized view.
ORA-12017: cannot alter primary key mview “string” to a rowid mview
Cause: An attempt was made to convert the primary key of a materialized view to
a ROWID materialized view.
Action: Conversion of a primary key materialized view to a ROWID materialized
view is not supported. Create a new materialized view with ROWIDs or drop and
recreate the materialized view with ROWIDs.
ORA-12018: following error encountered during code generation for “string”.”string”
Cause: The refresh operations for the indicated materialized view could not be
regenerated due to errors.
Action: Correct the problem indicated in the following error messages and repeat
the operation.
ORA-12019: master table is a synonym to a remote object
Cause: An attempt was made to create a materialized view or a materialized view
log on a remote synonym which is unsupported.
Action: Do not create a materialized view or materialized view log on a remote
synonym.
ORA-12020: materialized view string is not registered
Cause: An attempt was made to unregister a materialized view that is not
registered.
Action: No action required.
ORA-12021: materialized view “string”.”string” is corrupt
Cause: The materialized view indicated is no longer valid.
Action: Contact Oracle Customer Support.
ORA-12022: materialized view log on “string”.”string” already has rowid
Cause: Materialized view log on the indicated table already has ROWID
information.
Action: No action required.
ORA-12023: missing index on materialized view “string”.”string”
Cause: The specified ROWID materialized view did not have the required index
on the ROWID column of its underlying table.
Action: Drop and recreate the materialized view.
ORA-12024: materialized view log on “string”.”string” does not have primary key
columns
Cause: Materialized view log on the indicated table does not have primary key
information.
Action: Add primary keys to the materialized view log using the ALTER
MATERIALIZED VIEW command.
ORA-12025: materialized view log on “string”.”string” already has primary keys
Cause: Materialized view log on the indicated table already has primary key
columns.
Action: No action required.
ORA-12026: invalid filter column detected
Cause: One or more of the specified filter columns did not exist or was a primary
key column or a primary key based object identifier.
Action: Ensure that all specified filter columns exist in the master table and
ensure that primary key columns or primary key based object identifiers are not
included in the list of filter columns.
ORA-12027: duplicate filter column
Cause: One or more of the specified filter columns were already being recorded in
the materialized view log.
Action: Describe the materialized view log table and reissue the SQL command
with the filter columns that are already being recorded in the materialized view
log.
ORA-12028: materialized view type is not supported by master site string
Cause: Pre-Oracle8 master sites are not able to support primary key or subquery
materialized views that are able to perform a fast refresh.
Action: Create a ROWID materialized view or use a master table from an Oracle8
site.
ORA-12029: LOB columns may not be used as filter columns
Cause: An attempt was made to use LOB columns as filter columns.
Action: Remove LOB columns from the filter columns list and retry command.
ORA-12030: cannot create a fast refresh materialized view
Cause: The materialized view log did not exist or did not log the information
needed by the materialized view to perform a fast refresh.
Action: Ensure that the materialized view log exists and logs the necessary
information.
– For ROWID materialized views, the master table”s ROWID must be logged.
– For primary key materialized views, the master table”s primary key columns
must be logged.
– For subquery materialized views, the filter columns, primary key, and ROWID
values must be logged.
– For object materialized views, object id must be logged.
ORA-12031: cannot use primary key columns from materialized view log on
“string”.”string”
Cause: The materialized view log either did not have primary key columns
logged, or the timestamp associated with the primary key columns was more
recent than the last refresh time.
Action: A complete refresh is required before the next fast refresh. Add primary
key columns to the materialized view log, if required.
ORA-12032: cannot use rowid column from materialized view log on
“string”.”string”
Cause: The materialized view log either does not have ROWID columns logged,
or the timestamp associated with the ROWID columns is more recent than the last
refresh time.
Action: A complete refresh is required before the next fast refresh. Add ROWID
columns to the materialized view log, if required.
ORA-12033: cannot use filter columns from materialized view log on
“string”.”string”
Cause: The materialized view log either did not have filter columns logged, or the
timestamp associated with the filter columns was more recent than the last refresh
time.
Action: A complete refresh is required before the next fast refresh. Add filter
columns to the materialized view log, if required.
ORA-12034: materialized view log on “string”.”string” younger than last refresh
Cause: The materialized view log was younger than the last refresh.
Action: A complete refresh is required before the next fast refresh.
ORA-12035: could not use materialized view log on “string”.”string”
Cause: The materialized view log did not exist or could not be used.
Action: Use just REFRESH, which will reinstantiate the entire table. If a
materialized view log exists and the form of the materialized view allows the use
of a materialized view log, REFRESH FAST will be available starting the next time
the materialized view is refreshed.
ORA-12036: updatable materialized view log is not empty, refresh materialized view
Cause: The updatable materialized view log was not empty. The updatable
materialized view log must be empty before an updatable rowid materialized
view can be altered to a primary key materialized view.
Action: Ensure that updatable materialized view log is empty by refreshing the
materialized view before converting the updatable ROWID materialized view to a
primary key materialized view.
ORA-12037: unknown export format
Cause: An attempt was made to import a materialized view exported by an
unknown export version (e.g., from a newer release than the importing site)
Action: Re-export the file using a version of export known by the importing site.
ORA-12039: unable to use local rollback segment “string”
Cause: A local rollback segment was specified in the CREATE MATERIALIZED
VIEW command, but automatic refresh parameters were not specified. Therefore a
refresh group was not created to automatically refresh the materialized view and
the local rollback segment can”t be registered for future use.
Action: Either supply the automatic refresh parameters so that a refresh group
will be created or do not specify a local rollback segment.
ORA-12040: master rollback segment option not support by master site string
Cause: An attempt was made to specify master rollback segment in the current
operation. The master site of the current materialized view does not allow users to
specify a rollback segment to be used for materialized view operations. This
feature is only supported by Oracle8 or later master sites.
Action: Do not specify a master rollback segment in the current operation or
choose a new master site.
ORA-12041: cannot record ROWIDs for index-organized table “string”.”string”
Cause: Index-organized tables do not have ROWIDs. Therefore a materialized
view log that records the ROWIDs of an index-organized table could not be
created.
Action: Do not include the WITH ROWID option when using the CREATE
MATERIALIZED VIEW command and do not include the ADD ROWID option
when using the ALTER MATERIALIZED VIEW command if the master table is
index-organized.
ORA-12042: cannot alter job_queue_processes in single process mode
Cause: An attempt was made to alter job_queue_processes in single process
mode.
Action: Do not attempt to set job_queue_processes in single process mode.
ORA-12043: invalid CREATE MATERIALIZED VIEW option
Cause: An invalid option was used in a CREATE MATERIALIZED VIEW
statement.
Action: Specify only valid options.
ORA-12044: invalid CREATE MATERIALIZED VIEW LOG option
Cause: An invalid option was used in a CREATE MATERIALIZED VIEW LOG
statement.
Action: Specify only valid options.
ORA-12045: invalid ALTER MATERIALIZED VIEW LOG option
Cause: An invalid option was used in an ALTER MATERIALIZED VIEW LOG
statement.
Action: Specify only valid options.
ORA-12046: cannot use trusted constraints for refreshing remote MV
Cause: REFRESH USING TRUSTED CONSTRAINTS specified in ALTER
MATERIALIZED VIEW or CREATE MATERIALIZED VIEW of a remote
materialized view
Action: remove this attribute from ALTER/ CREATE MATERIALIZED VIEW
DDL
ORA-12047: PCT FAST REFRESH cannot be used for materialized view
“string”.”string”
Cause: PCT refresh is either not enabled on this materialized view or not possible
after set of the base table changes since last refresh.
Action: Use just REFRESH FORCE, which will reinstantiate the entire table and
try to pick the best refresh method on the materialized view Do explain_mview to
look at the cause why PCT refresh is not possible on this materialized view
ORA-12048: error encountered while refreshing materialized view “string”.”string”
Cause: Some problem occurs during refresh of multiple materialized views in
atomic mode. The materialized view whose refresh failed has raised this error.
Action: Examine the other messages on the stack to find the refresh problem.
ORA-12051: ON COMMIT attribute is incompatible with other options
Cause: ON COMMIT refresh attribute, incompatible with other refresh options
such as automatic periodic refresh, was specified.
Action: Specify only valid options.
ORA-12052: cannot fast refresh materialized view string.string
Cause: Either ROWIDs of certain tables were missing in the definition or the inner
table of an outer join did not have UNIQUE constraints on join columns.
Action: Specify the FORCE or COMPLETE option. If this error is got during
creation, the materialized view definition may have be changed. Refer to the
documentation on materialized views.
ORA-12053: this is not a valid nested materialized view
Cause: The list of objects in the FROM clause of the definition of this materialized
view had some dependencies upon each other.
Action: Refer to the documentation to see which types of nesting are valid.
ORA-12054: cannot set the ON COMMIT refresh attribute for the materialized view
Cause: The materialized view did not satisfy conditions for refresh at commit
time.
Action: Specify only valid options.
ORA-12055: materialized view definition contains cyclic dependencies with existing
materialized views
Cause: The materialized view query definition introduced a cyclic dependency
with existing materialized view.
Action: Modify the materialized view query definition.
ORA-12056: invalid REFRESH method
Cause: The NEVER REFRESH option may not be used under the following
conditions:
* The materialized view is updatable
* The materialized view refreshes ON COMMIT
* Automatic refresh options are specified
Action: For updatable materialized views, reissue the SQL command using
REFRESH FORCE, REFRESH FAST, or REFRESH COMPLETE. For read-only
materialized views, reissue the SQL command using ON DEMAND.
ORA-12057: materialized view “string”.”string” is INVALID and must complete
refresh
Cause: The status of the materialized view was INVALID and an attempt was
made to fast refresh the materialized view.
Action: Perform a complete refresh of the materialized view. Check the value of
the STATUS column in dba_mviews, all_mviews, or user_mviews to verify that
the materialized view is VALID after the complete refresh.
ORA-12058: materialized view cannot use prebuilt table
Cause: An attempt was made to use the prebuilt tables.
Action: Reissue the SQL command using BUILD IMMEDIATE or BUILD
DEFERRED.
ORA-12059: prebuilt table “string”.”string” does not exist
Cause: The specified prebuilt table did not exist.
Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD
DEFERRED, or ensure that the prebuilt table exists.
ORA-12060: shape of prebuilt table does not match definition query
Cause: The number of columns or the type or the length semantics of a column in
the prebuilt table did not match the materialized view definition query.
Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD
DEFERRED, or ensure that the prebuilt table matches the materialized view
definition query.
ORA-12061: invalid ALTER MATERIALIZED VIEW option
Cause: An invalid option was used in an ALTER MATERIALIZED VIEW
statement.
Action: Specify only valid options.
ORA-12062: transaction string received out of sequence from site string
Cause: A transaction from the client site was received out of sequence. This
implies that one or more transactions were missing.
Action: Ensure that the transaction queue at the client site is valid and has not
been corrupted.
ORA-12063: unable to apply transaction from site string
Cause: The current transaction from the client site could not be applied to the
master site.
Action: Ensure that the client site is still valid and that it has not been dropped
from the master site.
ORA-12064: invalid refresh sequence number: string
Cause: The client site was attempting to perform a refresh with an invalid refresh
sequence.
Action: Perform a complete refresh to synchronize the refresh sequence number.
ORA-12065: unknown refresh group identifier string
Cause: The specified refresh group did not exist at the master site.
Action: Ensure that the client site is still valid and that it has not been dropped
from the master site.
ORA-12066: invalid CREATE MATERIALIZED VIEW command
Cause: The Replication API does not support the following options and types of
materialized view:
o ROWID materialized views
o REFRESH ON COMMIT
o ON PREBUILT TABLE
o BUILD DEFERRED
o NEVER REFRESH
o ENABLE QUERY REWRITE
Action: Create a PRIMARY KEY materialized view using REFRESH WITH
PRIMARY KEY and/or remove the invalid options.
ORA-12067: empty refresh groups are not allowed
Cause: The refresh group being instantiated did not contain any materialized
views.
Action: Modify the template to include at least one materialized view.
ORA-12068: updatable mview log for mview “string”.”string” does not exist
Cause: The updatable materialized view was missing the updatable materialized
view log required to track updates made to the materialized view.
Action: Create the updatable materialized view log.
ORA-12069: invalid object for offline instantiation
Cause: Only materialized views can be offline instantiated. The object being
offline instantiated was not a valid materialized view.
Action: Remove the object from the template or replace the object with a valid
materialized view.
ORA-12070: cannot offline instantiate materialized view “string”.”string”
Cause: Offline instantiation does not support materialized views using the
following options:
o ON PREBUILT TABLE
o BUILD DEFERRED
Action: Remove the invalid options.
ORA-12071: definition query of “string”.”string” is invalid for offline instantiation
Cause: Offline instantiation requires materialized view definition queries to
observe the following constraints:
o The database link that will be used by the materialized view site to connect to
the master site must be included with each master table referenced in the query.
o All master tables referenced must be located at the local site. References to other
sites are not allowed.
Action: Modify the materialized view definition query.
ORA-12072: updatable materialized view log data for “string”.”string” cannot be
created
Cause: The updatable materialized view was missing the updatable materialized
view log required to track updates made to the materialized view.
Action: Create an updatable materialized view log.
ORA-12073: request cannot be processed
Cause: An out-of-sequence request was made and it cannot be processed.
Action: Try again with a valid request.
ORA-12074: invalid memory address
Cause: An attempt was made to access an invalid memory region.
Action: Reconnect and try the command again.
ORA-12075: invalid object or field
Cause: An attempt was made to access an invalid field or object in the Java Virtual
Memory.
Action: Retry the request.
ORA-12076: invalid threshold value
Cause: The result set threshold or LOB threshold value is not supported.
Action: Specify a threshold value below 64K.
ORA-12077: temporary updatable materialized view log does not exist
Cause: Temporary updatable materialized view log was not created or was
dropped.
Action: Re-create the temporary updatable materialized view log. Warning: This
will cause a complete refresh of the materialized view.
ORA-12078: fast refresh of refresh group ID string failed
Cause: Refresh result set sent through client method REFRESH_REQ_RESULT
returned an unknown value.
Action: Re-issue the refresh request.
ORA-12079: materialized view options require COMPATIBLE parameter to be string
or greater
Cause: The following materialized view options require 8.1 or higher
compatibility setting:
o ON COMMIT
o ON PREBUILT TABLE
o BUILD DEFERRED
o NEVER REFRESH
o ENABLE QUERY REWRITE The following materialized view options require 8.2
or higher compatibility setting:
o materialized views with user-defined types The following materialized view
options require 9.2 or higher
o materialized views (query rewrite enabled) with set operators that are not inside
an inline view or named view The following materialized view options require
10.0 or higher
o materialized views which can be refreshed USING TRUSTED CONSTRAINTS
o materialized views with SELECT column alias clause In addition, ALTER
MATERIALIZED VIEW LOG can be used to add sequence number only if
compatibility is set to 10.0 or higher
Action: Shut down and restart with an appropriate compatibility setting.
ORA-12081: update operation not allowed on table “string”.”string”
Cause: An attempt was made to update a read-only materialized view.
Action: No action required. Only Oracle is allowed to update a read-only
materialized view.
ORA-12082: “string”.”string” cannot be index organized
Cause: An attempt was made to create an index-organized materialized aggregate
view or an index-organized updatable ROWID materialized view. This is not
supported.
Action: Try to create the materialized view without the index organization clause.
ORA-12083: must use DROP MATERIALIZED VIEW to drop “string”.”string”
Cause: An attempt was made to drop a materialized view using a command other
than DROP MATERIALIZED VIEW.
Action: Use the DROP MATERIALIZED VIEW command.
ORA-12084: must use ALTER MATERIALIZED VIEW to alter “string”.”string”
Cause: An attempt was made to alter a materialized view using a command other
than ALTER MATERIALIZED VIEW.
Action: Use the ALTER MATERIALIZED VIEW command.
ORA-12085: materialized view log on “string”.”string” already has object id
Cause: Materialized view log on the indicated table already has object id
information.
Action: No action required.
ORA-12086: table “string”.”string” is not an object table
Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the
WITH OBJECT ID option and the master table is not an object table.
Action: Either specify the name of an object table, or remove the WITH OBJECT
ID clause.
ORA-12087: online redefinition not allowed on tables owned by “string”
Cause: An attempt was made to online redefine a table owned by SYS or
SYSTEM.
Action: Do not attempt to online redefine a table owned by SYS or SYSTEM.
ORA-12088: cannot online redefine table “string”.”string” with unsupported
datatype
Cause: An attempt was made to online redefine a table containing a LONG
column, an ADT column, or a FILE column.
Action: Do not attempt to online redefine a table containing a LONG column, an
ADT column, or a FILE column.
ORA-12089: cannot online redefine table “string”.”string” with no primary key
Cause: An attempt was made to online redefine a table that does not have a
primary key defined on it.
Action: Do not attempt to online redefine a table that does not have a primary key
defined on it.
ORA-12090: cannot online redefine table “string”.”string”
Cause: An attempt was made to online redefine a table that is either a clustered
table, AQ table, temporary table, IOT overflow table or table with FGA/RLS
enabled.
Action: Do not attempt to online redefine a table that is a clustered table, AQ
table, temporary table, IOT overflow table or table with FGA/RLS enabled.
ORA-12091: cannot online redefine table “string”.”string” with materialized views
Cause: An attempt was made to online redefine a table that had materialized
views defined on it or had a materialized view log defined on it or is a master.
Action: Drop all materialized views and materialized view logs before attempting
to online redefine the table.
ORA-12092: cannot online redefine replicated table “string”.”string”
Cause: An attempt was made to online redefine a table that is either a
materialized view or a replicated table.
Action: Do not attempt to online redefine a table that is either a materialized view
or a replicated table.
ORA-12093: invalid interim table “string”.”string”
Cause: The table is not the interim table of the corresponding table to be online
redefined.
Action: Pass in the valid interim table.
ORA-12094: error during online redefinition
Cause: There was an error during the online redefinition process.
Action: Abort the online redefinition process.
ORA-12096: error in materialized view log on “string”.”string”
Cause: There was an error originating from this materialized view log. One
possible cause is that schema redefinition has occurred on the master table and
one or more columns in the log is now a different type than corresponding master
column(s). Another possible cause is that there is a problem accessing the
underlying materialized view log table.
Action: Check further error messages in stack for more detail about the cause. If
there has been schema redefinition, drop the materialized view log and recreate it.
ORA-12097: changes in the master tables during refresh, try refresh again
Cause: There are some changes (i.e., conventional DML, direct load, partition
maintenance operation) in the master tables during materialized view refresh.
Action: Refresh the affected materialized views again.
ORA-12098: cannot comment on the materialized view
Cause: An attempt was made to issue a COMMENT ON TABLE statement on a
materialized view.
Action: Issue a COMMENT ON MATERIALIZED VIEW statement instead.
ORA-12100: materialized view log on “string”.”string” already has sequence
Cause: Materialized view log on the indicated table already has sequence
information.
Action: No action required.
Good Luck !
Leave a Reply
You must be logged in to post a comment.