_messages

Oracle 11.1.0:

Oracle 10.2.0:

Oracle 10.1.0:

Oracle 9.2.0:

Oracle 8.1.7:

Oracle 8.0.6:

Oracle 7.3.4:

Related Error Messages:

Cause: This message reports the name file involved in other messages.

Action: See associated error messages for a description of the problem.

ORA-00283: recovery session canceled due to errors

Cause: An error during recovery was determined to be fatal enough to end the current recovery session.

Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action.

ORA-00284: recovery session still in progress

Cause: An error during recovery was determined to be minor enough to allow the current recovery session to continue.

Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action.

ORA-00290: operating system archival error occurred. See error below

Cause: While attempting to archive to a redo log file, the server encountered an unexpected operating system error.

Action: Correct the operating system error given in the messages and retry the operation. See also your operating system-specific Oracle documentation.

ORA-00311: cannot read header from archived log

Cause: An I/O error occurred when attempting to read the log file header from the specified archived redo log file.

Action: Other messages will accompany this message. See the associated messages for the appropriate action to take.

ORA-00312: online log %s thread %s: '%s'

Cause: This message reports the filename for details of another message.

Action: Other messages will accompany this message. See the associated messages for the appropriate action to take.

ORA-00334: archived log: '%s'

Cause: Reporting filename for details of another error

Action: See associated error messages

ORA-00335: online log %s: No log with this number, log does not exist

Cause: Reporting filename for details of another error

Action: See associated error messages

ORA-00343: too many errors, log member closed

Cause: The maximum number of errors on this log member has been exceeded.

Action: Correct the underlying problem by referring to the other error messages found with this one.

ORA-00346: log member marked as STALE

Cause: A log file member no longer is complete.

Action: Correct the underlying problem by referring to the other error messages found with this one.

ORA-01034: ORACLE not available

Cause: Oracle was not started up. Possible causes include the following: - The SGA requires more space than was allocated for it. - The operating-system variable pointing to the instance is improperly defined.

Action: Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. If Oracle has been initialized, then on some operating systems, verify that Oracle was linked correctly. See the platform specific Oracle documentation.

ORA-01186: file %s failed verification tests

Cause: The data file did not pass the checks to insure it is part of the database. See the accompanying error messages for the reason the verification failed.

Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES.

ORA-01201: file %s header failed to write correctly

Cause: An I/O error was reported for the file header. The error was trapped and a second attempt will be made.

Action: The file probably will require recovery. Further error messages will indicate what is needed.

ORA-01235: END BACKUP failed for %s file(s) and succeeded for %s

Cause: One or more of the files in an end backup command failed. Some other files given in the same command may have succeeded.

Action: See the accompanying error messages for the reason the backups could not be ended. Any files not listed in the error messages were successful.

ORA-01264: Unable to create %s file name

Cause: Unable to create an Oracle managed file name.

Action: Check previous error messages for the reason Oracle was unable to create the file name. Take corrective action, if possible, and retry the command.

ORA-01890: NLS error detected

Cause: An NLS error was detected.

Action: Look for additional error messages and take appropriate action. If there are no additional errors, call Oracle Worldwide Support.

ORA-02320: failure in creating storage table for nested table column %s

Cause: An error occurred while creating the storage table for the specified nested table column.

Action: See the messages that follow for more details. If the situation they describe can be corrected, do so; otherwise contact Oracle Support.

ORA-02322: failure in accessing storage table of the nested table column

Cause: An error occured while performing DML on the storage table of the nested table column.

Action: If the situation described in the following messages can be corrected, do so; otherwise contact Oracle Support.

ORA-06527: External procedure SQLLIB error: %s

Cause: An error occurred in sqllib during execution of a Pro* external procedure.//

Action: The message text indicates the actual SQLLIB error that occurred. Consult the Oracle Error Messages and Codes manual for a complete description of the error message and follow the appropriate action.//

ORA-07721: scgcm: not enough OS resource to obtain system enqueue

Cause: A call to sys$enq returned an error indicating that the operating system lacked the resources necessary to create a lock. This is caused by the messages SS$_EXENQLM or SS$_INSFMEM.

Action: Free up some of the required resource to allow the creation of the required lock.

ORA-08414: error encountered in %s

Cause: The function returned an error. Where may be: RAW_TO_NUMER NUMBER_TO_RAW RAW_TO_NUMBER_FORMAT NUMBER_TO_RAW_FORMAT MAKE_NUMBER_TO_RAW_FORMAT MAKE_RAW_TO_NUMBER_FORMAT

Action: This message will be preceded by messages providing details about the error. Check those messages to determine what action to take.

ORA-09747: pw_detachPorts: server call pws_detach failed.

Cause: The call pws_detach to (Oracle helper) failed.

Action: Make sure the server is still active. Check the error code returned in sercerrno, and look for error messages in the server log file.

ORA-09751: pw_attachPorts: server call pws_attach failed.

Cause: The call pws_attach to (Oracle helper) failed.

Action: Make sure the server is still active. Check the error code returned in sercerrno, and look for error messages in the server log file.

ORA-09761: pw_destroyPorts: server call pws_stop_instance failed.

Cause: The call pws_stop_instance to (Oracle helper) failed.

Action: Make sure the server is still active. Check the error code returned in sercerrno, and look for error messages in the server log file.

ORA-09829: pw_createPorts: server call pws_start_instance failed.

Cause: The call pws_start_instance to (Oracle helper) failed; system resources might be exhausted.

Action: Make sure the server is still active. Check the error code returned in sercerrno, and look for error messages in the server log file.

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.NLS_DO_NOT_TRANSLATE [10000,10999] - Tag to indicate messages shouldnot be translated.

ORA-10390: Trace parallel query slave execution

Cause: Pointer to skgmsdef struct used without validating it

Action: Assign a valid address to the skgmsdef struct pointer before using it.NLS_DO_NOT_TRANSLATE [10000,10999] - Tag to indicate messages shouldnot be translated.

ORA-10431: enable verification messages on pi consistency

Cause: Pointer to skgmsdef struct used without validating it

Action: Assign a valid address to the skgmsdef struct pointer before using it.NLS_DO_NOT_TRANSLATE [10000,10999] - Tag to indicate messages shouldnot be translated.

ORA-10433: global enqueue service testing event

Cause: Pointer to skgmsdef struct used without validating it

Action: Assign a valid address to the skgmsdef struct pointer before using it.NLS_DO_NOT_TRANSLATE [10000,10999] - Tag to indicate messages shouldnot be translated.

ORA-10563: Test recovery had to corrupt data block (file# %s, block# %s) 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-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-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: 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.

ORA-10573: Test recovery tested redo from change %s to %s

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-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-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-12018: following error encountered during code generation for \"%s\".\"%s\"

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-12048: error encountered while refreshing materialized view \"%s\".\"%s\"

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-12096: error in materialized view log on \"%s\".\"%s\"

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-12322: unable to mount database (link name %s)

Cause: This message should be accompanied by additional error messages that indicate the cause of the problem.

Action: Follow the steps outlined in the accompanying error messages to resolve the problem.

ORA-12323: unable to open database (link name %s)

Cause: This message should be accompanied by additional error messages that indicate the cause of the problem.

Action: Follow the steps outlined in the accompanying error messages to resolve the problem.

ORA-12403: invalid internal label

Cause: An internal label could not be converted to a valid label for the policy.

Action: Analyze any additional messages on the error stack and consult the policy documentation.

ORA-13184: failed to initialize tessellation package

Cause: Initialization of the tessellation package failed.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13185: failed to generate initial HHCODE

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13186: fixed tile size tessellation failed

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13187: subdivision failed

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13188: cell decode failed

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13189: recursive SQL parse failed

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13190: recursive SQL fetch failed

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13191: failed to read SDO_ORDCNT value

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13192: failed to read number of element rows

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13193: failed to allocate space for geometry

Cause: There was insufficient memory to read the geometry from the database.

Action: Validate the geometry. Record the error messages that are returned and contact Oracle Support Services.

ORA-13195: failed to generate maximum tile value

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-15032: not all alterations performed

Cause: At least one ALTER DISKGROUP action failed.

Action: Check the other messages issued along with this summary error.//

ORA-15039: diskgroup not dropped

Cause: An attempt to drop a diskgroup failed.

Action: See the associated messages for details about why the drop was not successful.//

ORA-15062: ASM disk is globally closed

Cause: The disk to which the I/O request was issued has gone offline or has been globally closed by the background process. Check other messages in the trace files for more information.

Action: Bring the disk online for I/Os to get through.//

ORA-15064: communication failure with ASM instance

Cause: There was a failure to communicate with the ASM instance, most likely because the connection went down.

Action: Check the accompanying error messages for more information on the reason for the failure. Note that database instances will always return this error when the ASM instance is terminated abnormally.//

ORA-15066: offlining disk \"%s\" may result in a data loss

Cause: Following I/O failures, the disks holding all copies of a data block were attempted to be taken offline.

Action: Check the accompanying error messages for more information on the reason for the disk I/O failures.//

ORA-15082: ASM failed to communicate with database instance

Cause: There was a failure when ASM tried to communicate with a database instance (most likely because the connection went down).

Action: Check the accompanying error messages for more information on the reason for the failure. Note that the ASM instances may return this error when a database instance is terminated abnormally.//

ORA-15131: block %s of file %s in diskgroup %s could not be read

Cause: A block could not be read because the disk containing the block is either offline or an I/O error occured while reading the block. If this is mirrored file, then all disks that contain a copy of the block are either offline or received errors.

Action: Repair the affected disk and bring it back online. Refer to accompanying error messages to determine which disk has failed.//

ORA-15132: block %s of file %s in diskgroup %s could not be written

Cause: A block could not be written because the disk containing the block is either offline or an I/O error occured while writing the block. If this is mirrored file, then insufficient disks which contain a copy of the block are either offline or received errors.

Action: Repair the affected disk and bring it back online. Refer to accompanying error messages to determine which disk has failed.//

ORA-16038: log %s sequence# %s cannot be archived

Cause: An attempt was made to archive the named file, but the file could not be archived. Examine the secondary error messages to determine the cause of the error.

Action: No action is required.

ORA-16043: managed recovery session canceled

Cause: The standby database managed recovery operation has been canceled per user request or operation timeout.

Action: More specific messages will accompany this message.

ORA-16501: the Data Guard broker operation failed

Cause: The Data Guard broker operation failed.

Action: See accompanying messages for details.

ORA-16502: the Data Guard broker operation succeeded with warnings

Cause: The Data Guard broker operation succeeded with warnings.

Action: See accompanying messages for details.

ORA-17502: ksfdcre:%s Failed to create file %s

Cause: file creation failed due to either insufficient OS permission or the file already exists

Action: check additional error messages

ORA-17503: ksfdopn:%s Failed to open file %s

Cause: file open failed due to either insufficient OS permission or the name of file exceeds maximum file name length.

Action: check additional error messages

ORA-17504: ksfddel:Failed to delete file %s

Cause: The file that was being deleted is still in use or the process has insufficient permission to delete file.

Action: check additional error messages

ORA-17505: ksfdrsz:%s Failed to resize file to size %s blocks

Cause: There is insufficient space left on the device or the process has insufficient permission to resize file.

Action: check additional error messages

ORA-17507: I/O request size %s is not a multiple of logical block size

Cause: i/o's are done in multiple of logical block size

Action: Check additional error messages

ORA-17509: Attempt to do i/o beyond block1 offset

Cause: When a file is identified with logical block size of 0, only i/o's to block1 is allowed.

Action: check additional error messages and call Oracle Support Services

ORA-17510: Attempt to do i/o beyond file size

Cause: The i/o request points to a block beyond End Of File

Action: check additional error messages and call Oracle Support Services

ORA-17618: Unable to update block 0 to version 10 format

Cause: An attempt was made to update block 0 to version 10 format.

Action: Check additional error messages and call Oracle Support Services

ORA-19508: failed to delete file \"%s\"

Cause: call to delete the file returned an error

Action: check additional messages

ORA-19509: failed to delete sequential file, handle=\"%s\", parms=\"%s\"

Cause: call to delete the sequential file returned an error

Action: check additional messages

ORA-19510: failed to set size of %s blocks for file \"%s\" (blocksize=%s)

Cause: call to resize the file returned an error

Action: check additional messages

ORA-19554: error allocating device, device type: %s, device name: %s

Cause: The specified device could not be allocated.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19557: device error, device type: %s, device name: %s

Cause: An error occurred in the platform-specific device code

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19558: error de-allocating device

Cause: The specified device could not be de-allocated.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19559: error sending device command: %s

Cause: An error occurred while sending the indicated command to the session device.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19564: error occurred writing %s bytes at block number %s

Cause: An error occurred while writing to a file.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error if possible, then retry the copy, backup, or restore operation.

ORA-19583: conversation terminated due to error

Cause: An error occurred which forced the termination of the current backup or restore conversation.

Action: There should be other error messages to help identify the cause of the problem. Correct the error and begin another conversation.

ORA-19587: error occurred reading %s bytes at block number %s

Cause: An error occurred while reading from a file.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error then retry the copy, backup, or restore operation.

ORA-19646: cannot change size of datafile %s from %s to %s

Cause: The indicated file was resized before this incremental backup was taken, but the incremental backup failed to set the file to the new size.

Action: Examine the other messages which should be present to indicate the cause of the failure.

ORA-19650: Offline-range record recid %s stamp %s in file %s has SCN %s

Cause: This messages identifies the offline-clean SCN from the indicated offline-range record in the indicated file.

Action: See other error message.

ORA-19660: some files in the backup set could not be verified

Cause: A restore conversation was made to verify all the files in a backup set, and the files which were printed in messages 19661 or 19662 could not be verified because corrupt blocks for those files were found in the backup set.

Action: Unless the damage to the backup set can be repaired, the indicated files cannot be restored from this backup set.

ORA-19664: file type: %s, file name: %s

Cause: This message is issued to identify the file which is the subject of an error.

Action: None - this is an informational message. There should be other Oracle messages explaining the cause of the error.

ORA-19676: one or more files failed during proxy backup or restore

Cause: During a proxy backup or restore, errors were encountered while processing some files. The files for which no error messages are shown were processed successfully.

Action: Examine the messages regarding the specific files to determine the cause of the problems.

ORA-19750: change tracking file: '%s'

Cause: This message reports the name of a file involved in other messages.

Action: See associated error messages for a description of the problem.

ORA-19753: error writing to change tracking file

Cause: An I/O error occurred while writing to the change tracking file.

Action: There will be other messages on the error stack that show details of the problem.

ORA-19754: error reading from change tracking file

Cause: An I/O error occurred while reading from the change tracking file.

Action: There will be other messages on the error stack that show details of the problem.

ORA-19755: could not open change tracking file

Cause: The change tracking file could not be opened.

Action: There will be other messages on the error stack that show details of the problem.

ORA-19756: corrupt block number %s found in change tracking file

Cause: The specified block number is corrupt in the change tracking file.

Action: There will be other messages on the error stack that show details of the problem. There will also be a trace file that contains a complete dump of the corrupt block.

ORA-19757: could not resize change tracking file to %s blocks

Cause: An error occurred while trying to change the size of the change tracking file.

Action: There will be other messages on the error stack that show details of the problem.

ORA-19773: must specify change tracking file name

Cause: No file name was specified with the ALTER DATABASE ENABLE CHANGE TRACKING command, and the DB_CREATE_FILE_DEST parameter was not set.

Action: Either specify a file name, or set the DB_CREATE_FILE_DEST parameter.Do not use messages 19774 and 19775. They are krc events.

ORA-19800: Unable to initialize Oracle Managed Destination

Cause: The name given for an Oracle managed files destination cannot be initialized.

Action: Check previous error messages for the reason Oracle was unable to initialize destination. Take corrective action, if possible, and retry the command or use a different name for destination.

ORA-19813: cannot have unavailable file %s in DB_RECOVERY_FILE_DEST

Cause: An attempt was made to change backuppiece or image copy in recovery area to UNAVAILABLE.

Action: Correct and resubmit the RMAN command.Do not use messages 19814; it is used for simulating crash.

ORA-19816: WARNING: Files may exist in %s that are not known to database.

Cause: One of the following events caused this:1. A database crash happened during file creation.2. A backup control file was restored.3. The control file was re-created.4. DB_RECOVERY_FILE_DEST has previously been enabled and then disabled.

Action: Use RMAN command CATALOG RECOVERY AREA to re-catalog any such files. If the file header is corrupted, then delete those files using an OS utility.Do not use messages 19817; it is used for simulating lock failureDo not use messages 19818; it is used for space reclaimation before backup

ORA-19914: unable to encrypt backup

Cause: RMAN could not create an encrypted backup. This message will be accompanied by other messages that give more details about why the encrypted backup could not be created. The most common reason for this message is that you are trying to create a backup that can be transparently decrypted, and the database external security device is not open.

Action: If the external security device is not open, then open it. If the external security device is not configured, then the only type of encrypted backup that you can create is a password-based backup.

ORA-23603: STREAMS enqueue aborted due to low SGA

Cause: An attempt to enqueue a STREAMS message was aborted because ORACLE is running low on memory allotted for STREAMS.

Action: Either start consuming messages by enabling any STREAMS propagation or apply which might be disabled. An alternative is to allot more memory to STREAMS, which can be done by increasing the streams_pool_size initialization parameter if one was defined or by increasing the shared_pool_size.

ORA-24058: cannot downgrade QUEUE_TABLE that has propagation in a prepared state

Cause: An attempt was made to downgrade the queue table when there were messages being propagated that were in the prepared state.

Action: Wait for the propagation to complete before retrying the operation.

ORA-24077: cannot create propagation schedule for EXCEPTION queue %s.%s

Cause: A SCHEDULE_PROPAGATION was issued for an EXCEPTION queue. Propagation schedules can be created only for NORMAL queues.

Action: To propagate messages from a queue specify the queue type as NORMAL.//

ORA-24199: message store is overflow

Cause: An attemp was made to access too many messages at the same time.

Action: Use the CLEAN procedure to clean up some of the messages.

ORA-25211: invalid DELAY specified when using sequence deviation

Cause: The DELAY specified in the enqueue is greater than the delay of the message with the given relative message id.

Action: Set the DELAY to be less than or equal to the delay of the message with the given relative message id. If the TOP option is used the delay must be less than or equal to the delay of all the messages in the queue.//

ORA-25212: invalid PRIORITY specified when using sequence deviation

Cause: The PRIORITY specified in the enqueue is less than the priority of the message with the given relative message id.

Action: Set the PRIORITY to be less than the delay of the message with the given relative message id. If the TOP option is used the prioirty must be greater than or equal to the priority of all the messages in the queue.

ORA-25233: invalid parameter specified for NAVIGATION

Cause: An invalid parameter has been specified for NAVIGATION.

Action: Choose one of FIRST_MESSAGE, NEXT_MESSAGE or NEXT_TRANSACTION. Use FIRST_MESSAGE for dequeuing the first message that satisifies the criterion, NEXT_MESSAGE for dequeuing the next message that satisifies the criterion and NEXT_TRANSACTION for moving to a set of messages enqueued by another transaction.//

ORA-25234: NEXT_TRANSACTION navigation option invalid for queue table %s.%s

Cause: The NEXT_TRANSACTION navigation option was used in a dequeue from a queue in a queue table that was not created for transactional grouping.

Action: Specify either FIRST_MESSAGE or NEXT_MESSAGE as the navigation option. If you want to dequeue messages using transactional grouping create the queue in a queue table that has transactional grouping enabled.//

ORA-25235: fetched all messages in current transaction

Cause: The NEXT_TRANSACTION navigation option was used in a dequeue when there were no more messages that belong to the same transaction.

Action: Use the NEXT_TRANSACTION navigation option to move to the next also use the FIRST_MESSAGE option to start from the head of the queue again.//

ORA-25254: time-out in LISTEN while waiting for a message

Cause: The specified wait time has elapsed and there were no messages for any of the agents in the agent-list.

Action: Try the LISTEN call with an appropriate time-out.

ORA-25294: Cannot propagate user buffered messages to a database with version lower than 10.2

Cause: Propagation of user buffered messages was attempted to a database with version lower than 10.2.

Action: Do not propagate buffered messages to the database.

ORA-25295: Subscriber is not allowed to dequeue buffered messages

Cause: Subscriber is only allowed to dequeue persistent messages

Action: Drop the subscriber and re-create it, or dequeue only persistent messages for the subscriber

ORA-25301: Cannot enqueue or dequeue user buffered messages to a database with version lower than 10.2

Cause: Enqueue or dequeue of user buffered messages was attempted to queues in a database with version lower than 10.2.

Action: Do not attempt to enqueue or dequeue user buffered messages.

ORA-25315: unsupported configuration for propagation of buffered messages

Cause: An attempt was made to propagate buffered messages with the database link pointing to an instance in the destination database which is not the owner instance of the destination queue.

Action: Use queue to queue propagation for buffered messages.

ORA-25333: Buffered Queue to Queue propagation did not connect to the correct instance

Cause: Queue to Queue propagation for buffered messages didn't connect to the correct instance, most likely because service was not started for the destination queue.

Action: No user action is required. Propagation will start the service for the destination queue and retry.

ORA-25335: AQ array operations not allowed for buffered messages

Cause: An array enqueue/dequeue was attempted for buffered messages

Action: Use single enqueue/dequeue for buffered messages or an array size of one.

ORA-26522: rpc execution error

Cause: An error occurred during the execution of a PL/SQL rpc.

Action: Check the error messages from the remote procedure and fix any remote site problems that may be preventing the execution of the invoked rpc.

ORA-27018: BLKSIZE is not a multiple of the minimum physical block size

Cause: User-specified BLKSIZE (blocking factor) is not a multiple of the minimum block size that is permitted on this platform.

Action: Two ADDITIONAL INFORMATION messages are displayed which show the blocking factor provided by the user and the minimum physical block size. Specify a BLKSIZE that is an integral multiple of the minimum block size.

ORA-27024: skgfqsbi: sbtinit2 returned error

Cause: sbtinit2 returned an error. This happens during a backup or restore operation.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27026: skgfrls: sbtend returned error

Cause: sbtend returned an error. This happens during a backup or restore operation.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27027: sbtremove2 returned error

Cause: sbtremove2 returned an error. This happens when deleting a backup file.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27028: skgfqcre: sbtbackup returned error

Cause: sbtbackup returned an error. This happens when creating a backup file during a backup operation.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27029: skgfrtrv: sbtrestore returned error

Cause: sbtrestore returned an error. This happens when retrieving a backup file during a restore operation.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27030: skgfwrt: sbtwrite2 returned error

Cause: sbtwrite2 returned an error. This happens while writing a backup file during a backup operation.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27190: skgfrd: sbtread2 returned error

Cause: sbtread returned an error. This happens while reading a backup file during a restore operation.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27191: sbtinfo2 returned error

Cause: sbtinfo2 returned an error. This happens while retrieving backup file information from the media manager's catalog.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27192: skgfcls: sbtclose2 returned error - failed to close file

Cause: sbtclose2 returned an error. This happens while closing a backup file during a backup or restore operation.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27194: skgfdvcmd: sbtcommand returned error

Cause: sbtcommand returned an error. This happens when an rman SEND command is issued.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27196: skgfpbk: sbtpcbackup returned error

Cause: sbtpcbackup returned an error. This happens when a proxy backup is begun.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27197: skgfprs: sbtpcrestore returned error

Cause: sbtpcrestore returned an error. This happens when a proxy restore is begun.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27198: skgfpvl: sbtpcvalidate returned error

Cause: sbtpcvalidate returned an error. This happens during a proxy backup or restore.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27199: skgfpst: sbtpcstatus returned error

Cause: sbtpcstatus returned an error. This happens during a proxy backup or restore.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27200: skgfpgo: sbtpcstart returned error

Cause: sbtpcstart returned an error. This happens during a proxy backup or restore.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27201: skgfpcm: sbtpccommit returned error

Cause: sbtpccommit returned an error. This happens during a proxy backup or restore.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27202: skgfpen: sbtpcend returned error

Cause: sbtpcend returned an error. This happens during a proxy backup or restore.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27203: skgfpqb: sbtpcquerybackup returned error

Cause: sbtpcquerybackup returned an error. This happens during a proxy backup.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27204: skgfpqr: sbtpcqueryrestore returned error

Cause: sbtpcqueryrestore returned an error. This happens during a proxy restore.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27205: skgfpcn: sbtpccancel returned error

Cause: sbtpccancel returned an error. This happens during a proxy restore.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27550: Target ID protocol check failed. tid vers=%d, type=%d, remote instance number=%d, local instance number=%d

Cause: The local Oracle Real Application Cluster instance and remote instance are running with incompatible implementation of the inter-instance IPC protocol library. A misconfiguration or installation error occurred.

Action: Check additional error messages in the alert log and the process trace file.

ORA-29382: validation of pending area failed

Cause: Invalid changes were attempted in the pending area.

Action: See documentation and the error messages that follow this one.

ORA-29730: use global enqueue converts to determine highest held mode

Cause: Invalid changes were attempted in the pending area.

Action: See documentation and the error messages that follow this one.

ORA-29902: error in executing ODCIIndexStart() routine

Cause: The execution of ODCIIndexStart routine caused an error.

Action: Examine the error messages produced by the indextype code and take appropriate action.

ORA-29903: error in executing ODCIIndexFetch() routine

Cause: The execution of ODCIIndexFetch routine caused an error.

Action: Examine the error messages produced by the indextype code and take appropriate action.

ORA-29904: error in executing ODCIIndexClose() routine

Cause: The execution of ODCIIndexClose routine caused an error.

Action: Examine the error messages produced by the indextype code and take appropriate action.

ORA-29913: error in executing %s callout

Cause: The execution of the specified callout caused an error.

Action: Examine the error messages take appropriate action.

ORA-29961: too many warnings occurred in the execution of ODCIIndex DDL routine

Cause: The number of warnings during the ODCIIndex DDL routine is too high.

Action: Query table SYS.ODCI_WARNINGS$ to get more warning messages

ORA-30113: error when processing file '%.*s'

Cause: A problem occurred when processing this file.

Action: Examine the additional error messages and correct the problem.

ORA-30114: error when processing from command line

Cause: A problem occurred when processing the command line.

Action: Examine the additional error messages and correct the problem.

ORA-30115: error when processing an environment variable

Cause: A problem occurred when processing an environment variable.

Action: Examine the additional error messages and correct the problem.

ORA-31199: Warning in processing file %s

Cause: A warning was raised while operating on the specifed file. However, the current operation was completed successfully.

Action: This is primarily an informational message. Look at the next error on the stack to obtain further information.//////////////////////////////DBMS_LDAP & OiD messages

ORA-31399: Cannot contact LDAP server %s at port %d

Cause: The LDAP server specified could not be contacted. This can happen if the server is down or inaccessible.

Action: Contact the administrator of the LDAP server//////////////////////////End of DBMS_LDAP & OiD messages

ORA-31495: error in synchronous change table on \"%s\".\"%s\"

Cause: There was an error originating from this synchronous change table. One possible cause is that schema redefinition has occurred on the source table and one or more columns in the change table are now a different type than corresponding source columns. Another possible cause is that there is a problem accessing the synchronous change table.

Action: Check further error messages in stack for more detail about the cause. If there has been schema redefinition, drop and recreate the synchronous change table.//

ORA-31613: Master process %s failed during startup.

Cause: The master process whose name is listed failed during startup.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31617: unable to open dump file \"%s\" for write

Cause: Export was unable to open the export file for writing. This message is usually followed by device messages from the operating system.

Action: Take appropriate action to restore the device.

ORA-31621: error creating master process

Cause: Setup to create a master process failed.

Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31625: Schema %s is needed to import this object, but is unaccessible

Cause: An error occurred when attempting to import objects. The schema specified is needed to import this object, but access to this schema is not available.

Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31626: job does not exist

Cause: An invalid reference to a job which is no longer executing, is not executing on the instance where the operation was attempted, or that does not have a valid Master Table. Refer to any following error messages for clarification.

Action: Start a new job, or attach to an existing job that has a valid Master Table.

ORA-31628: error getting worker process exception

Cause: Attempt to get a worker process exception failed.

Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31631: privileges are required

Cause: The necessary privileges are not available for operations such as: restarting a job on behalf of another owner, using a device as a member of the dump file set, or ommiting a directory object associated with any of the various output files. Refer to any following error messages for additional information.

Action: Select a different job to restart, try a different operation, or contact a database administrator to acquire the needed privileges.

ORA-31632: master table \"%s.%s\" not found, invalid, or inaccessible

Cause: A Master Table is required but no such table exists, or the content is not consistent with that of a valid Master Table, or the table is not accessible. Refer to any following error messages for clarification.

Action: Make sure a valid Master Table exists, and eliminate any problems indicated by the following error messages.

ORA-31633: unable to create master table \"%s.%s\"

Cause: Job creation failed because a Master Table and its indexes could not be created, most commonly due to the pre-existance of a table with the same name (job name) in the user schema. Refer to any following error messages for clarification.

Action: Select a different job name, DROP the existing table, or eliminate any problems indicated by the following error messages.

ORA-31634: job already exists

Cause: Job creation or restart failed because a job having the selected name is currently executing. This also generally indicates that a Master Table with that job name exists in the user schema. Refer to any following error messages for clarification.

Action: Select a different job name, or stop the currently executing job and re-try the operation (may require a DROP on the Master Table).

ORA-31637: cannot create job %s for user %s

Cause: Unable to create or restart a job. Refer to any following or prior error messages for clarification.

Action: Eliminate the problems indicated.

ORA-31638: cannot attach to job %s for user %s

Cause: Unable to attach a job to a session. Refer to any following or prior error messages for clarification.

Action: Eliminate the problems indicated.

ORA-31640: unable to open dump file \"%s\" for read

Cause: Import was unable to open the export file for reading. This message is usually followed by device messages from the operating system.

Action: Take appropriate action to restore the device.

ORA-31643: unable to close dump file \"%s\"

Cause: Export or Import was unable to close the dump file. This message is usually followed by device messages from the operating system.

Action: Take appropriate action to restore the device.

ORA-31644: unable to position to block number %s in dump file \"%s\"

Cause: Export or Import was unable to position its file pointer to a specific block within the dump file. This message is usually followed by device messages from the operating system.

Action: Take appropriate action based on the device messages.

ORA-31648: Timeout before master process %s finished initialization.

Cause: The master process whose name is listed started up but did not finish its initialization within the allowed time limit.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31649: Master process %s violated startup protocol.

Cause: The master process whose name is listed started up but then exited before notifying the creating process that it was finished with initialization.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31666: Master process %s had an unhandled exception.

Cause: A Data Pump process model master process had an unhandled exception condition.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31668: Timeout before worker process %s finished initialization.

Cause: The worker process whose name is listed started up but did not finish its initialization within the allowed time limit.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31669: Worker process %s violated startup protocol.

Cause: The worker process whose name is listed started up but then exited before notifying the creating process that it was finished with initialization.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31671: Worker process %s had an unhandled exception.

Cause: A Data Pump process model worker process had an unhandled exception condition.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31686: error creating worker processes

Cause: Setup to create worker processes failed.

Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31687: error creating worker process %s with worker id %s

Cause: Attempt to create the listed worker process failed.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31688: Worker process %s failed during startup.

Cause: The worker process whose name is listed failed during startup.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-32848: foreign queue DOMAIN required for JMS unified connections

Cause: A DOMAIN was not specified when registering a foreign queue for a messaging system link that is configured to use the JMS unified messaging model.

Action: Specify a non-NULL value for the DOMAIN parameter.//Copyright (c) 2001, 2005, Oracle. All rights reserved. //NAME olap33k.msg - OLAP messages in the 33,000 range//DESCRIPTION Provides the OLAP error messages for inclusion in the RDBMS//NOTES Concatenated with other files to build the RDBMS message file If you change this: cd rdbms/mesg gmake concat gmake oraus.msb//MODIFIED (MM/DD/YY)ghicks 04/19/05 - add _XSINPUTERR_dpeltier 04/21/05 - some new EIF messages ghicks 04/19/05 - _XSAGGCNTMOVE01_ .. 06_ghicks 03/25/05 - add XSLANGDM02cchiappa 03/30/05 - Remove 37081 akociube 03/17/05 - add XSTBLFUNC09ghicks 03/18/05 - update list of valid types for _XSMCSESS04_cjohnson 03/16/05 - remove xscgrank05 ghicks 03/17/05 - add XSLANGDM*; tinker with XSSPROP* punctuation.dpeltier 03/17/05 - really complicated iterators cchiappa 03/15/05 - Add XSAGDNGLPREC (33009) cjohnson 03/11/05 - remove unused errors cwelton 03/11/05 - add XSAGDNGL49, XSAGDNGL50cchiappa 03/10/05 - Add XSPQEXPRESS (37069)cjohnson 03/02/05 - xscgrank05ghicks 03/02/05 - add OPCREATE01, O2; remove PPENG04cchiappa 03/01/05 - Tweak sps adv errors based on errors_us feedbackcjohnson 02/16/05 - delete mxcgaf04 cchiappa 02/15/05 - Tweak sparsity advisor messages dpeltier 02/15/05 - partitioning / aggcount stuffghicks 02/12/05 - add _LOCKCHECK01_cchiappa 02/10/05 - Add DELDENTANON cchiappa 02/08/05 - Move errors out of reserved ranges ruqtang 01/31/05 - add _XSCGMDLAGG09-13_dpeltier 01/24/05 - add messages for _mvtopart ghicks 01/20/05 - add XSFCAST28 (36951)cchiappa 01/10/05 - More sparsity advisor messages wechen 12/28/04 - add 37118 through 37120, 37150 through 37158ilyubash 12/09/04 - add DBERR07 (33274)cchiappa 11/29/04 - Sparsity advisor errors ckearney 11/01/04 - add 36849 & 36850, add %a to 36886ghicks 10/31/04 - spelling; remove MXSQL25, XSAGDNGL45dpeltier 10/13/04 - MXMSERR01 takes a qon node pludwig 10/04/04 - Fix assignments of scalar to temp scalar variablesruqtang 09/14/04 - correct more mesg for XSRELTBL/XSRELGIDruqtang 09/08/04 - XSRELGID17esoyleme 09/07/04 - message for transportable platform mismatch cchiappa 08/20/04 - Move bad error messagesghicks 07/28/04 - slight adjustment to MXRECAP09ghicks 07/19/04 - delete EIFEXPRT00cjohnson 07/13/04 - Add XSBASLIM00cchiappa 06/29/04 - Add XSAGGRFORMghicks 06/30/04 - eliminate MODGONE00, add MDQUERY01dpeltier 06/25/04 - xsLmsMesg changescwelton 06/24/04 - XSCCOMP11 thru XSCCOMP15zqiu 06/23/04 - more action for DBERRBSZckearney 06/23/04 - Add XSSRF04, XSSRF05 & XSSRF06cwelton 06/28/04 - Cleanup cc error messagesghicks 06/17/04 - add SNSYN205cchiappa 06/17/04 - Fix XSAGGR33 argumentscchiappa 06/09/04 - Tweak cause for XSAGGCNTPROPcchiappa 06/07/04 - Add XSAGGCNTPROPghicks 06/03/04 - remove obsolete PRMPINIT initializersdpeltier 06/01/04 - XSCCOMP0[456] wording, add XSCCOMP10dpeltier 05/17/04 - aw_upgrade -> polymorphic convertcchiappa 05/14/04 - Add XSAGPROPFROMdpeltier 05/12/04 - AGGCOUNTghicks 05/03/04 - XSSQLMDQ messagesdpeltier 04/15/04 - AWUPG messagescchiappa 04/09/04 - Add XSSPROPDTYPEcchiappa 04/09/04 - Fix text for XSMXAGGR10cchiappa 04/09/04 - Add XSAGGRRUVCVcchiappa 03/29/04 - Spell correct DBERR18, text for 33269ruqtang 03/29/04 - RELTBL15dpeltier 03/16/04 - make EIFEXPRT01 more generaldpeltier 03/03/04 - XSMXAGGR06cjohnson 03/02/04 - obsolete errorsilyubash 03/15/04 - Allow add SESSION in MULTIcjohnson 02/18/04 - obsolete errorscjohnson 02/23/04 - obsolete errorsghicks 02/05/04 - delete obsolete messages, add XSSPFC01dpeltier 01/30/04 - MAINTCHK messagesilyubash 12/29/03 - Add messages delayed since 10gR1jcarey 12/19/03 - add XSDBVALID 05, 06cwelton 08/18/03 - Add XSCCOMP00 - XSCCOMP09dpeltier 08/07/03 - add compressed composite messagesckearney 08/06/03 - add _XSSRF03_ message & update other SRF messagesghicks 08/05/03 - fix %p (-> %%p) in VCFMT005wechen 08/04/03 - add 37117 for xsldolapcjohnson 07/23/03 - MAXDIMS 256 cchiappa 07/31/03 - Fix XSDPART24esoyleme 07/29/03 - add 37100pludwig 07/29/03 - txn107486: Concat custom membersghicks 07/22/03 - reintroduce QFHEAD01 in case of needckearney 07/21/03 - add _XSTBLFUNC08_zqiu 07/22/03 - change err text of 36770rtang 07/24/03 - add XSAGDNGL48ghicks 07/17/03 - reword QFHEAD06; 86 QFHEAD01; QFHEAD causes/actionsjcarey 07/16/03 - More cause and actionsjcarey 07/15/03 - add finegrained access control error messagezqiu 07/09/03 - add DBERRBSZilyubash 07/03/03 - Add Bad Expression error to Table Fucntionscchiappa 06/24/03 - Eliminate XSPQRO (37071)ghicks 06/23/03 - drop word 'dimension' from PERMIT06wechen 06/17/03 - add 37116 for xsldolapilyubash 06/13/03 - Add Rollback support error messagespludwig 06/09/03 - txn107433: dup concat leaves in model DIMENSION stmtrtang 06/05/03 - add more errs for XSCGMDLAGGghicks 05/29/03 - fix run-on sentence in 37002cchiappa 05/28/03 - Eliminate session sharing stuffwechen 05/27/03 - add 37115 for xsldolappludwig 05/27/03 - txn106886: More UNIQUE Concatsrtang 05/19/03 - XSMCSESS08dpeltier 05/19/03 - 9i2 compatibility & EIFghicks 05/15/03 - 86 FCREATE06ghicks 05/09/03 - 86 QFGET04cwelton 05/08/03 - XSCCUBE01/02ghicks 05/07/03 - PERMIT06dpeltier 05/07/03 - add ESDREAD17, XSVPART07dpeltier 05/07/03 - partition list maintenancecjohnson 05/06/03 - TRGPRG02ghicks 04/29/03 - edit causes/actions for 4/21/03 messagescjohnson 04/29/03 - TRGSET01cchiappa 04/21/03 - Add XSPQROghicks 04/21/03 - CINSERT06/07, CMOVE03; reword XSMCSESS messagescjohnson 04/21/03 - TRIGGERrtang 04/21/03 - Add more XSRELGID err msgrtang 04/16/03 - XSMCSESS07dpeltier 04/08/03 - list partitioning changescwelton 04/08/03 - pludwig 04/07/03 - txn105869: Unique CONCATsrtang 03/28/03 - More err msg for custmemcwelton 04/03/03 - cchiappa 03/26/03 - Add DBERRTABLEcjohnson 03/26/03 - TRANSLATEBYTES cchiappa 03/19/03 - DBERRLEN 8 byte argumentsghicks 03/19/03 - Add Hide/unhide model msgdpeltier 03/14/03 - change some partitioning messagescchiappa 03/13/03 - Add DBERRLENcchiappa 03/06/03 - Reword DBDESC06esoyleme 02/06/03 - SQL spreadsheet errorcjohnson 02/24/03 - chgdfn invertedcwelton 03/26/03 - XSAGPARTDEP - aggregate + recursive partitionscwelton 03/03/03 - XSAGHIERPART - aggregate + partitionsdpeltier 02/14/03 - more partitioning stuffdpeltier 02/13/03 - bad compatibility settings for object definedpeltier 02/10/03 - some small partitioning stuffilyubash 01/20/03 - New-gen-present errorsghicks 01/15/03 - remove (very) obsolete MAINTAIN COMPACT referencecjohnson 01/10/03 - sharemap zqiu 01/13/03 - remove _XSAWRENAME_*cchiappa 01/15/03 - Add message for text ag var reuseesoyleme 12/24/02 - fix message for 37080cjohnson 12/22/02 - TEMP dimensionzqiu 01/03/03 - add 37060, 37061 for aw_renamewechen 12/19/02 - add 37111, 37112, 37113 & 37114 for xsldolapdpeltier 12/09/02 - multiwriter dimension maintenanceilyubash 12/02/02 - Multiwriter workdpeltier 11/19/02 - more partitioningghicks 12/04/02 - substitution marker in MXCGVAR01cjohnson 11/26/02 - export partition templatepludwig 11/19/02 - txn105041ghicks 11/16/02 - various small fixesrtang 11/15/02 - Fix MCSESS Error Msgrtang 11/12/02 - add XSMCSESS02ckearney 11/12/02 - Updated MXSQL24 & SQLOUT11ilyubash 11/11/02 - Add more Multiwriter errorscchiappa 11/04/02 - Optional aggmap in allocate (SNSYN163)dpeltier 11/04/02 - LIST partitioningdpeltier 11/02/02 - Add DELDENT05pludwig 11/01/02 - txn104999ghicks 10/28/02 - add QFSVNS01ilyubash 10/24/02 - More Multiwriter error msgspludwig 10/23/02 - txn104769cchiappa 10/21/02 - Add BADSPROP, NOAGMcjohnson 10/19/02 - sort hierarchyghicks 10/17/02 - add 'missing or' to MXIMPORT04dpeltier 10/16/02 - BASE -> CONCATdpeltier 10/14/02 - more partitioningrtang 10/14/02 - messages for mnt sessionpludwig 10/12/02 - txn104553cchiappa 10/08/02 - Add _XSAGDIMBREAK_esoyleme 10/04/02 - more advisor messagesdpeltier 09/30/02 - subpartitioningcchiappa 09/27/02 - Flow -> Dropcjohnson 09/27/02 - chgdims limit argesoyleme 09/23/02 - aggregate advisor messagesilyubash 09/20/02 - Add more XSACQUIRE messagesghicks 09/19/02 - texts for AW LIST and AW(LISTALL)cchiappa 09/19/02 - Add 37003 - May not xeq in pq sessckearney 09/12/02 - Change _XSSRF01 messagedpeltier 09/11/02 - fix MXPSHPOP03ilyubash 09/05/02 - added multiwriter error msgsilyubash 09/11/02 - Adding new DTB error messagesilyubash 09/04/02 - Add table function describe error messagesdpeltier 09/04/02 - more partitioningdpeltier 08/28/02 - more partitioningcchiappa 09/04/02 - Add XSAGDIMFLOWrtang 08/22/02 - Add more error for GroupingIDdpeltier 08/19/02 - Partitioned variables messagescchiappa 09/03/02 - Modify PHYS0{0,1}cchiappa 08/15/02 - Add autoupdate & autocommit errordpeltier 08/08/02 - More partitioning messagesrtang 08/05/02 - Change RELTBL mesgcwelton 08/05/02 - Add XSTBLFUNC06ckearney 08/07/02 - Add _XSSRF02_ & _XSTBLFUNC07_cchiappa 08/02/02 - Add 37002, OLAP failed to initializecchiappa 08/02/02 - Fix XSAGDNGL24, XSAGDNGL43cchiappa 08/01/02 - Add 36961, OLAP not availableckearney 08/01/02 - Add _XSSRF01_dpeltier 07/10/02 - XSDPART messagesghicks 07/30/02 - MAKEDCL35 - "date dimension" -> "time dimension"cchiappa 07/30/02 - Add XSUNUPDATEDghicks 07/25/02 - change MXPROPER04 to substitute min/maxilyubash 07/24/02 - Added MXDSS29pludwig 07/25/02 - txn103641rtang 07/23/02 - Add XSAGDNGL47pludwig 07/23/02 - pludwig_txn103382cwelton 07/24/02 - Add XSTBLFUNC05cjohnson 07/22/02 - XSSCLLEV09cwelton 07/17/02 - Add XSTBLFUNC04cchiappa 07/16/02 - Modify XSMXAGGRFROMpludwig 07/15/02 - pludwig_txn103382cchiappa 07/08/02 - Remove text from XSAGGR33 & XSAGGR34ghicks 07/02/02 - fix OFCENG02 ("specifiy")ckearney 06/27/02 - Added _SQLOUT20_ - ORA-35587.ckearney 07/10/02 - Added _XSSRF00_ esoyleme 06/20/02 - Fix XSAGGR33cchiappa 06/20/02 - Add dataflow XSMXAGGR messagescchiappa 05/24/02 - Kill XSAGINFO01, add headerjcarey 05/24/02 - LRG97582 - bad memory references past end-of-bufferdpeltier 05/23/02 - Fix NTEXT garbage in error messagesedashevs ??/??/?? - edashevs_txn102340zqiu 05/14/02 - change OLAP_PAGE_POOL_SIZE to big intcwelton 05/04/02 - Implement LMINFO functioncchiappa 05/02/02 - Alias dimension for parents in allocateckearney 05/02/02 - sql SELECT workcchiappa 04/25/02 - Allow agg of unlike-dimensioned vars in one commandcwelton 04/12/02 - obj(aggmaplist) functionrtang 04/07/02 - Single dimension model only as dynamic modelrtang ??/??/?? - rtang_txn105656ghicks ??/??/?? - ghicks_txn105486cchiappa ??/??/?? - cchiappa_txn105431cjohnson 03/27/02 - LEVELREL args for LAG/MOVING functionsghicks 03/13/02 - AIX porting bug 2194536 (again);ilyubash 02/01/02 - Gracefully handle out-of-temp-space problems.ghicks 01/26/02 - eversion and eifversion;ghicks 01/19/02 - allow obj(numvals) etc. to return > MINSB8MAXVAL;-cjohnson 01/18/02 - remove h filesghicks 01/18/02 - new Geneva functionalityghicks 01/11/02 - remove STRIP command;cchiappa 01/08/02 - Fix allocate bugsdpeltier 12/14/01 - More AW name: aliases, different semantics, etc.edashevs ??/??/?? - edashevs_txn101085pludwig 12/12/01 - Fix Bug 2139758 - 64bit problem in xskvbn.cdpeltier 12/11/01 - AW names / attachnamesedashevs ??/??/?? - edashevs_txn100848jcarey 12/05/01 - causes and actions.dpeltier 12/05/01 - EIF export, FILEREAD, implicit conversion exceptionsahopeman 11/29/01 - Table functions use xsinterp to execute commandsdpeltier 11/29/01 - Surrogate bug 2110865ghicks 11/29/01 - filequeryilyubash 11/29/01 - Segv in EIF code without running CDAcwelton 11/27/01 - Table Function error msgdpeltier 11/20/01 - Clean up LMS messaging; remove OS translationpludwig 11/20/01 - CONCAT base add and export excludertang 11/20/01 - New requirement of dynamic model at current stagecjohnson 11/19/01 - olint fixesjcarey ??/??/?? - jcarey_txn100717ilyubash 11/16/01 - Further support for directory aliasesghicks 11/16/01 - allow (slightly crippled) multi-file EIF export;rtang 11/14/01 - fill cause and action fields in error message.rtang 11/13/01 - number dimesnioned destination relation GIDdpeltier 11/12/01 - NUMBER dimscjohnson 11/01/01 - remove .h files from xseng/globals.hdpeltier 10/31/01 - NTEXT: UNISTR(), output functionsghicks 10/31/01 - BUG2075951 - INFO(PARSE TYPE) for program/extcalldpeltier 10/29/01 - Surrogates: unit tests and bug fixescjohnson 10/26/01 - GUARD/ONEXIT bugsghicks 10/26/01 - porting grp changes for variable name conflicts etc.rtang 10/26/01 - hierheight & groupingid support multidim relationsdpeltier 10/24/01 - Remove data gatherer messages from olap33k.msgcjohnson 10/21/01 - fix qa testscjohnson 10/19/01 - remove obsolete code and fix txengcdd.tstilyubash 10/19/01 - Fix AW DELETE and link it into enqueuescjohnson 10/16/01 - fix QA log files/ CGETPOS05 xsOOPSdpeltier 10/15/01 - Some NTEXT import / export fixesdpeltier 10/11/01 - Fix log files for message difsdpeltier 10/10/01 - Messages from rdbms/ora*.msb, not olap/aps*.msbabatakis ??/??/?? - Created from old files//

ORA-33084: (XSAGDNGL42) %a %j %j\nIn AGGMAP %1p, you cannot qualify the dimensioned valueset %2p.

Cause: The VALUESET line referred to a dimensioned valueset.

Action: Use a non-dimensioned valueset to limit the status of the dimensioned one./XSAGINIT and XSAGCOMP messages (379-539) from xsagcomp.c

ORA-36914: (XSAGDNGL50) %a %j %j\nIn AGGMAP %1p, LOAD_STATUS valueset %2p contains both a child and it's ancestor.

Cause: The LOAD_STATUS valueset is not allowed to contain both a dimension value and an ancestor of that value.

Action: Perform a limit remove ancestors on the valueset and confirm that the result matches the intended load.36920 - 36929 reserved for _mvtopartartition messages

ORA-37603: (XSPGERRTEMPSYSTEM) Ran out of temporary storage while writing to a system temporary analytic workspace. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.

Cause: Ran out of temporary tablespace storage.

Action: Increase the amount of temporary tablespace storage./THE FOLLOWING MESSAGES ARE OPERATING SYSTEM DEPENDENT AND/SHOULD MOSTLY BE REPLACED OR REMOVED FOR 9i2. PLEASE ADD NEW/MESSAGES ABOVE THE LINE.

ORA-37603: (XSPGERRTEMPSYSTEM) Ran out of temporary storage while writing to a system temporary analytic workspace. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.

Cause: Something unexpected occurred in the OLAP system

Action: Contact Oracle technical support/STOP!!!! DON'T ADD NEW MESSAGES HERE, ADD THEM WAY BACK ABOVE THE/DASHED LINE//////////Optimizer///////////

ORA-38701: Flashback database log %s seq %s thread %s: \"%s\"

Cause: This message reports the filename for details of another message.

Action: Other messages will accompany this message. See the associated messages for the appropriate action to take.

ORA-38706: Cannot turn on FLASHBACK DATABASE logging.

Cause: An ALTER DATABASE FLASHBACK ON command failed. Other messages in the alert log describe the problem.

Action: Fix the problem and retry.

ORA-38771: unnamed datafile(s) added to control file by flashback recovery

Cause: The recovery step of FLASHBACK DATABASE encountered the creation of a datafile that could not be added to the control file. An entry has been added to the control file for the new datafile, but with the file name UNNAMEDnnnn, where nnnn is the file number. Related error messages provide the file names that were originally used to create the files.

Action: Rename the file in the control file, or use the ALTER ALTER DATABASE CREATE DATAFILE command to create a file suitable for recovery. If the file is not going to be recovered, then take it offline with the FOR DROP option. The recovery step of Flashback can be resumed by entering a RECOVERY command with the same SCN or timestamp as used in the FLASHBACK DATABASE command. For example, RECOVER AUTOMTAIC DATABASE UNTIL CHANGE .

ORA-38798: Cannot perform partial database recovery

Cause: See other other messages on error stack for the cause.

Action: See other other messages on error stack for the action.

ORA-38959: Failed to update block 0 to new version 10 format

Cause: An attempt was made to update block 0 to version 10 format.

Action: check additional error messages and contact Oracle Support Services.//////////Data Pump///////////

ORA-39000: bad dump file specification

Cause: The user specified a dump file that could not be used in the current job. Subsequent error messages describe the inadequacies of the dump file.

Action: Specify a dump file that is usable for the job.

ORA-39001: invalid argument value

Cause: The user specified API parameters were of the wrong type or value range. Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further describe the error.

Action: Correct the bad argument and retry the API.

ORA-39002: invalid operation

Cause: The current API cannot be executed because of inconsistencies between the API and the current definition of the job. Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further describe the error.

Action: Modify the API call to be consistent with the current job or redefine the job in a manner that will support the specified API.

ORA-39003: unable to get count of total workers alive

Cause: Attempt to get count of total worker processes alive failed.

Action: Check the additional error messages to see what caused the failure. Correct the error, if possible, and try the operation again. If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39005: inconsistent arguments

Cause: The current API cannot be executed because of inconsistencies between arguments of the API call. Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further describe the error.

Action: Modify the API call to be consistent with itself.

ORA-39006: internal error

Cause: An unexpected error occurred while processing a Data Pump job. Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further describe the error.

Action: Contact Oracle Customer Support.

ORA-39029: worker %s with process name \"%s\" prematurely terminated

Cause: The specified worker process terminated unexpectedly. Subsequent messages describe the reason for the termination.

Action: If problem persists, contact Oracle Customer Support.

ORA-39062: error creating master process %s

Cause: An attempt to create the listed master process failed.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39063: unable to write to the bad file

Cause: Errors were detecting while writing to the bad file. Subsequent messages will detail the problems.

Action: Fix the problems outlined in the secondary messages.

ORA-39064: unable to write to the log file

Cause: Errors were detecting while writing to the log file. Subsequent messages will detail the problems.

Action: Fix the problems outlined in the secondary messages.

ORA-39065: unexpected master process exception in %s

Cause: An unhandled exception was detected internally within the master control process for the Data Pump job. This is an internal error. messages will detail the problems.

Action: If problem persists, contact Oracle Customer Support.

ORA-39066: Unable to close the bad file.

Cause: Errors were detecting while closing the bad file. Subsequent messages will detail the problems.

Action: Fix the problems outlined in the secondary messages.

ORA-39067: Unable to close the log file.

Cause: Errors were detecting while closing the log file. Subsequent messages will detail the problems.

Action: Fix the problems outlined in the secondary messages.

ORA-39069: Unable to open the bad file.

Cause: Errors were detecting while opening the bad file. Subsequent messages will detail the problems.

Action: Fix the problems outlined in the secondary messages.

ORA-39070: Unable to open the log file.

Cause: Errors were detecting while opening the log file. Subsequent messages will detail the problems.

Action: Fix the problems outlined in the secondary messages.

ORA-39071: Value for %s is badly formed.

Cause: The value of the user specified filter did not contain a legitimate SQL clause. Subsequent messages will detail the problems.

Action: Fix the problems outlined in the secondary messages.

ORA-39076: cannot delete job %s for user %s

Cause: Unable to delete a job. Refer to the any following or prior error messages for clarification.

Action: Eliminate the problems indicated.

ORA-39077: unable to subscribe agent %s to queue \"%s\"

Cause: The Data Pump's communication layer was unable to attach one of its processes to the control or status queue. Subsequent messages will detail the problem.

Action: Fix the problem if possible, or contact Oracle Customer Support.

ORA-39078: unable to dequeue message for agent %s from queue \"%s\"

Cause: The Data Pump's communication layer was unable to retrieve a message from the control or status queue. Subsequent messages will detail the problem.

Action: Fix the problem if possible, or contact Oracle Customer Support.

ORA-39079: unable to enqueue message %s

Cause: The Data Pump's communication layer was unable to send the specified message on the control or status queue. Subsequent messages will detail the problem.

Action: Fix the problem if possible, or contact Oracle Customer Support.

ORA-39080: failed to create queues \"%s\" and \"%s\" for Data Pump job

Cause: The Data Pump's communication layer was unable to create the status and control queues required for interprocess communication. Subsequent messages will detail the problem.

Action: Fix the problem if possible, or contact Oracle Support.

ORA-39081: failed to unsubscribe agent %s from queue \"%s\"

Cause: The Data Pump's communication layer was unable to unsubscribe a process from the control or status queue. Subsequent messages will detail the problem.

Action: Fix the problem if possible, or contact Oracle Customer Support.

ORA-39084: cannot detach job %s for user %s

Cause: Unable to detach a job from the session. Refer to any following error messages for clarification.

Action: Eliminate the problems indicated.

ORA-39085: cannot update job %s for user %s

Cause: Unable to update the fixed table information for a job. Refer to any following or prior error messages for clarification.

Action: Eliminate the problems indicated.

ORA-39086: cannot retrieve job information

Cause: Unable to retrieve fixed table information for a job. Refer to the secondary error messages that follow this one for clarification.

Action: Eliminate the problems indicated by the secondary errors.

ORA-39098: Worker process received data objects while loading metadata. Invalid process order range is %s..%s

Cause: This is an internal error. Messages will detail the problem.

Action: If problem persists, contact Oracle Customer Support.

ORA-39099: cannot create index for \"%s\" on master table %s

Cause: One or more indexes couldn't be created on the master table. subsequent error messages describe the failure.

Action: Correct the condition that is preventing the indexes from being created.

ORA-39102: Timeout before master process %s finished initialization. Master error:

Cause: The master process whose name is listed started up but did not finish its initialization within the allowed time limit.

Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39103: Timeout before worker process %s finished initialization. Worker error:

Cause: The worker process whose name is listed started up but did not finish its initialization within the allowed time limit.

Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39105: Master process %s failed during startup. Master error:

Cause: The master process whose name is listed failed during startup.

Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39106: Worker process %s failed during startup. Worker error:

Cause: The worker process whose name is listed failed during startup.

Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39107: Master process %s violated startup protocol. Master error:

Cause: The master process whose name is listed started up but then exited before notifying the creating process that it was finished with initialization.

Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39107: Master process %s violated startup protocol. Master error:

Cause: The worker process whose name is listed started up but then exited before notifying the creating process that it was finished with initialization.

Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39107: Master process %s violated startup protocol. Master error:

Cause: An attempt to delete the worker processes failed.

Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39127: unexpected error from call to %s \n%s

Cause: The exception was raised by the function invocation, a procedural action extension of export.

Action: Record the accompanying messages and report this as a Data Pump internal error to customer support.

ORA-39128: unexpected DbmsJava error %d from statement %s

Cause: The error was returned from a call to a DbmsJava procedure.

Action: Record the accompanying messages and report this as a Data Pump internal error to customer support.

ORA-39155: error expanding dump file name \"%s\"

Cause: Export was unable to expand the directory object and dump file name into a full file name. Subsequent messages will detail the problems.

Action: Fix the problems outlined in the secondary messages.

ORA-39156: error parsing dump file name \"%s\"

Cause: Export was unable to parse the dump file name. Subsequent messages will detail the problems.

Action: Fix the problems outlined in the secondary messages.

ORA-39157: error appending extension to file \"%s\"

Cause: Export or Import was unable to append the default extension to create the file name. The given file name could be too long or contain illegal characters. Subsequent messages will detail the problems.

Action: Fix the problems outlined in the secondary messages.

ORA-39159: cannot call this function from a non-Data Pump process

Cause: Called a Data Pump process model function from a process which is not a Data Pump process.

Action: Refer to any other error messages for additional information. If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39160: error on whats my name call

Cause: Attempt to get the Data Pump process name failed.

Action: Refer to any following error messages for additional information. If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-39180: unable to encrypt ENCRYPTION_PASSWORD

Cause: The specified encryption password was unable to be encrypted for placement within the master table or decrypted when it was to be restored from the master table. Subsequent messages will describe the actual error that caused the encryption to fail.

Action: Fix the problems referenced by the subsequent messages. The most common reason for the encryption to fail is the lack of a security wallet.

ORA-39200: Link name \"%s\" is invalid.

Cause: The name of the network link supplied for a Data Pump job was not usable. Secondary messages identify the problem.

Action: Rerun the job using a valid network link.

ORA-39218: type check on object type \"%s\".\"%s\" failed

Cause: The type check on a type failed. Therefore, the table create for the table which uses the type also fails.

Action: Refer to any following error messages for additional information. Correct the error, if possible, and try the action again.

ORA-39962: invalid parameter for PLSQL_CCFLAGS

Cause: The type check on a type failed. Therefore, the table create for the table which uses the type also fails.

Action: Refer to any following error messages for additional information. Correct the error, if possible, and try the action again.

This parameter is not documented and should not be used. Search for more info about [ _messages ] on the Oracle FAQ.