Copy of Oracle FAQ ORACLE RECOVERY without DUL
ORAFAQ HOME | ORAFAQ ASK QUESTION | ORAFAQ ADD INFO | ORAFAQ SEARCH | ORAFAQ E-MAIL
 

Index > ORACLE Server Parameters > _messages

_messages

NOTE: This is an internal Oracle parameter. Do NOT use it unless instructed to do so by Oracle Support. Playing with this parameter may be harmful.

Oracle 10.0.1:

Paramter Name:_messages
Description:message queue resources - dependent on # processes & # buffers
Type:NUMBER Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Oracle 9.2.0:

Paramter Name:_messages
Description:message queue resources - dependent on # processes & # buffers
Type:NUMBER Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Oracle 8.1.7:

Paramter Name:_messages
Description:message queue resources - dependent on # processes & # buffers
Type:NUMBER Obsoleted:TRUE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Oracle 8.0.6:

Paramter Name:_messages
Description:message queue resources - dependent on # processes & # buffers
Type:NUMBER Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Oracle 7.3.4:

Paramter Name:_messages
Description:message queue resources - dependent on # processes & # buffers
Type:NUMBER Obsoleted:FALSE
Can ALTER SESSION:FALSE Can ALTER SYSTEM:FALSE

Related Error Messages:

ORA-00202: controlfile: '%s'
    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 should not 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 should not 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 should not 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 should not 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-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-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.

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

ORAFAQ HOME | ORAFAQ ASK QUESTION | ORAFAQ ADD FAQ | ORAFAQ SEARCH | ORAFAQ E-MAIL
All content of this page is copy from www.orafaq.com