Oracle8 Error Messages
Release 8.0
A54625_01

Library

Product

Contents


Prev Next

ORA-04045: errors during recompilation/revalidation of name.name

Cause: Errors occurred during the implicit recompilation/revalidation of the object named in the message.

Action: More descriptive messages follow this one. Check the causes mentioned in the messages that follow and take the appropriate actions.

ORA-04046: results of compilation are too large to support

Cause: An attempt to compile and store a large stored procedure resulted in compilation data that is too large for the system to support or store.

Action: Reduce the size of the store procedure by splitting it into smaller stored procedures.

ORA-04050: invalid or missing procedure, function, or package name

Cause: The required procedure, function, or package name is invalid or missing.

Action: Specify a valid name.

ORA-04051: user name cannot use database link name

Cause: An attempt was made to access a non-existent database link, or a link not owned by the user logging in or PUBLIC, while attempting to access a remote object.

Action: Change the database link structure, so all indirect remote access requests are done from the same user originating the request or PUBLIC.

ORA-04052: error occurred when looking up remote object name

Cause: An error occurred looking up a remote object.

Action: Fix the error. Check that the remote database system has run the script to create necessary views used for querying/looking up objects stored in the database. See the Oracle8 Server Administrator's Guide.

ORA-04053: error occurred when validating remote object name

Cause: An error occurred trying to validate a remote object.

Action: Fix the error. Check that the remote database system has run the script to create necessary views used for querying/looking up objects stored in the database. See the Oracle8 Server Administrator's Guide.

ORA-04054: database link name does not exist

Cause: During compilation of a PL/SQL block, an attempt was made to use a non-existent database link.

Action: Use a different database link or create the database link.

ORA-04055: aborted: name formed a non-REF mutually-dependent cycle with name

Cause: This compilation was aborted because the library unit that was compiled would have formed a non-REF mutually-dependent cycle with some other library units. This happens when an attempt is made to compile types that have attributes of other types that may participate in a cycle with this type. For example:

create type t1;

create type t2 (a t1);

create type t1 (a t2);

Action: Break the cycle (possibly by adding a REF or by using another type).

04060-04069: Stored Procedure Execution Messages

ORA-04060: insufficient privileges to execute name

Cause: An attempt was made to execute a stored procedure without sufficient privileges.

Action: Obtain the necessary privileges through direct grants of the privileges, not through roles.

ORA-04061: existing state of name has been invalidated

Cause: An attempt was made to resume the execution of a stored procedure using the existing state, which has become invalid or inconsistent because the stored procedure has been altered or dropped.

Action: Attempt the action again. This action should cause the existing state of all packages to be reinitialized.

ORA-04062: name of name has been changed

Cause: An attempt was made to execute a stored procedure to service a remote procedure call stub that specifies a timestamp or signature that is different from the current timestamp or signature of the procedure.

Action: Recompile the caller to obtain the new timestamp.

For more information about obtaining a timestamp, see the index entry on "timestamp conflict resolution method" in Oracle8 Server Distributed Systems.

ORA-04063: name has errors

Cause: An attempt was made to execute a stored procedure that has errors. For stored procedures, the problem could be syntax or references to other, non-existent procedures. For views, the problem could be a reference in the view's defining query to a non-existent table.

Can also be a table which has references to non-existent or inaccessible types.

Action: Fix the errors and create referenced objects as necessary.

ORA-04064: not executed, invalidated name

Cause: An attempt was made to execute a stored procedure that has been invalidated.

Action: Recompile the procedure and its dependents.

ORA-04065: not executed, altered, or dropped name

Cause: An attempt was made to execute a stored procedure that has been altered or dropped.

Action: Recompile the procedure's dependents.

ORA-04066: non-executable object, name

Cause: An attempt was made to execute an object that is not a package, procedure, or function.

Action: Check that a correct name is used.

ORA-04067: not executed, name does not exist

Cause: An attempt was made to execute a package, procedure, or function that does not exist.

Action: Check the name in the command.

ORA-04068: existing state of packages has been discarded

Cause: An error occurred when attempting to execute a stored procedure.

Action: Refer to the accompanying messages and fix the error mentioned. Try the procedure again after proper reinitialization of any application's state.

04070-04099: Trigger Messages

This section lists messages generated when triggers are accessed. For more trigger messages, see "25000-25099: Trigger Messages" on page 2¬629.

ORA-04070: invalid trigger name

Cause: An invalid trigger name was specified.

Action: Check that the trigger name is not a reserved keyword.

ORA-04071: missing BEFORE or AFTER keyword

Cause: The trigger statement is missing the BEFORE/AFTER clause.

Action: Specify either BEFORE or AFTER.

ORA-04072: invalid trigger type

Cause: An invalid trigger type was given.

Action: Specify either INSERT, UPDATE, or DELETE as the trigger type.

ORA-04073: column list not valid for this trigger type

Cause: A column list was specified for a trigger type other than UPDATE.

Action: Remove the column list from the trigger.

ORA-04074: invalid REFERENCING name

Cause: An invalid name was given in the REFERENCING clause.

Action: Check that the REFERENCING name is not a reserved word.

ORA-04075: invalid trigger action

Cause: A statement was given for the trigger action.

Action: Specify another trigger action that is not a statement.

ORA-04076: invalid NEW or OLD specification

Cause: An invalid NEW or OLD specification was given for a column.

Action: Respecify the column using a correct NEW or OLD specification.

ORA-04077: WHEN clause cannot be used with table level triggers

Cause: The WHEN clause can only be specified for row-level triggers.

Action: Remove the WHEN clause or specify it for each row.

ORA-04078: OLD and NEW values cannot be identical

Cause: The REFERENCING clause specifies identical values for NEW and OLD.

Action: Specify the REFERENCING clause again with a different value for either NEW or OLD.

ORA-04079: invalid trigger specification

Cause: The CREATE TRIGGER statement is invalid.

Action: Refer to Oracle8 Server SQL Reference for the correct syntax of the CREATE TRIGGER statement.

ORA-04080: trigger name does not exist

Cause: The trigger name specified is invalid, or the trigger does not exist.

Action: Check the trigger name.

ORA-04081: trigger name already exists

Cause: The trigger name or type already exists.

Action: Use a different trigger name or drop the trigger that is of the same type.

ORA-04082: NEW or OLD references not allowed in table level triggers

Cause: The trigger is accessing NEW or OLD values in a table trigger.

Action: Remove any new or old references.

ORA-04083: invalid trigger variable name

Cause: The variable referenced in the trigger body is invalid.

Action: See Oracle8 Server SQL Reference for valid trigger variable types.

ORA-04084: cannot change trigger NEW values in after row triggers

Cause: New trigger variables can only be changed in before-row triggers.

Action: Change trigger type or remove the variable reference.

ORA-04085: cannot change the value of an OLD reference variable

Cause: OLD values can only be read and not changed.

Action: Do not attempt to change an OLD variable.

ORA-04086: trigger description too long, move Comments into triggering code

Cause: The trigger description is limited to 2000 characters, for dictionary storage reasons. The description does not include the text of the "when" clause or the text of the PL/SQL code executed for the trigger.

Action: If the trigger description contains a large Comment, move that Comment into the PL/SQL code for the trigger.

ORA-04087: cannot change the value of ROWID reference variable

Cause: ROWIDs can only be read and not changed.

Action: Do not attempt to change a ROWID value.

ORA-04088: error during execution of trigger name.name

Cause: A runtime error occurred during execution of a trigger.

Action: Check the triggers that were involved in the operation.

ORA-04089: cannot create triggers on objects owned by SYS

Cause: An attempt was made to create a trigger on an object owned by SYS.

Action: Do not create triggers on objects owned by SYS.

ORA-04090: name specifies same table, event and trigger time as name

Cause: The named trigger has a duplicate event and trigger time as another trigger.

Action: Combine both triggers into one trigger.

ORA-04091: table name is mutating, trigger/function may not see it

Cause: A trigger or a user-defined PL/SQL function that is referenced in the statement attempted to query or modify a table that was in the middle of being modified by the statement that fired the trigger.

Action: Rewrite the trigger or function so it does not read the table.

ORA-04092: cannot COMMIT or ROLLBACK in a trigger

Cause: A trigger attempted to COMMIT or ROLLBACK. This is not permitted.

Action: Rewrite the trigger so that COMMIT or ROLLBACK statements are not used.

ORA-04093: references to columns of type LONG are not allowed in triggers

Cause: A trigger attempted to reference a LONG column in the triggering table.

Action: Do not reference the LONG column.

ORA-04094: table name is constraining, trigger may not modify it

Cause: A trigger attempted to modify a table that was constraining for some referential constraint of a parent SQL statement.

Action: Rewrite the trigger so that it does not modify that table.

ORA-04095: trigger name already exists on another table, cannot replace

Cause: An attempt was made to replace a trigger that exists on another table.

Action: Re-create the trigger on the other table using the CREATE OR REPLACE TRIGGER statement.

ORA-04096: trigger name has a WHEN clause that is larger than 2K

Cause: A trigger's WHEN clause is limited to 2K for dictionary storage reasons.

Action: Use a smaller WHEN clause. Note, the trigger body could perform the same limiting action as the WHEN clause.

ORA-04097: DDL conflict while trying to drop or alter a trigger

Cause: An attempt was made to concurrently perform two DDL operations on a trigger or trigger table.

Action: Investigate the new state of the trigger and retry the DDL operation, if still appropriate.

ORA-04098: trigger name is invalid and failed re-validation

Cause: A trigger was attempted to be retrieved for execution and was found to be invalid. This also means that compilation/authorization failed for the trigger.

Action: The options are to resolve the compilation/authorization errors, disable the trigger, or drop the trigger.

For more information about enabling and disabling triggers, see the index entries on "enabling, triggers," "disabling, triggers," and "DROP TRIGGER command" in Oracle8 Server SQL Reference.

ORA-04099: trigger name is valid but not stored in compiled form

Cause: A trigger was attempted to be retrieved for execution and was found to be valid, but not stored. This may mean the an upgrade was done improperly from a non-stored trigger release.

Action: Execute the ALTER <triggername> COMPILE command to compile the trigger. The trigger will then be in stored form. Also, you may want to review that a proper upgrade was done.

For more information about ALTER TRIGGER, see the index entry on "ALTER TRIGGER" in Oracle8 Server SQL Reference.

06000-06429: SQL*Net Messages

ORA-06165: datafile name is too old to recover, restore a more recent copy

Cause: The archived logs and/or incremental backup sets required to recover the datafile do not exist, but a more recent backup of the datafile exists which can be recovered.

Action: Issue a RESTORE for the datafile, then reissue the RECOVER command.

ORA-06166: datafile name cannot be recovered

Cause: Incremental backups or archived redo logs needed to recover the datafile cannot be found, and no recoverable full backup or datafile copy exists.

Action: Use the LIST command to see if there is a backup set or datafile copy that can be made AVAILABLE. If not, then the datafile is unrecoverable. If a full or datafile copy exists, then a point-in-time recovery may be possible.

ORA-06167: already connected

Cause: A CONNECT command was issued, but RMAN is already connected to the specified database.

Action: RMAN has no DISCONNECT command, so to connect to a different instance, exit RMAN and start it again.

ORA-06168: no backup pieces with this tag found: name

Cause: A tag was used to specify a list of backup pieces, but no backup pieces with this tag could be found.

Action: Make sure the tag is specified correctly.

ORA-06169: could not read file header for datafile %s error reason %s

Cause: The specified datafile could not be accessed. The reason codes are:

1 - filename is MISSINGxx in the controlfile
2 - file is offline
3 - file is not verified
4 - DBWR could not find the file
5 - unable to open file
6 - I/O error during read
7 - file header is corrupt
8 - file is not a datafile
9 - file does not belong to this database
10 - file number is incorrect
12 - wrong file version
15 - controlfile is not current

Action: If the error can be corrected, do so and retry the operation. The SKIP option can be used to ignore this error during a backup.

ORA-06170: no controlfile copy found with offline range recid num stamp name datafile name

Cause: This offline range is needed for recovering the specified datafile, but the offline range record has aged out of the current controlfile and no controlfile copy with the record could be accessed. At least 1 controlfile copy containing the offline range was found in the recovery catalog and was in AVAILABLE status.

Action: Query the RC_CONTROLFILE_COPY view for the names of all controlfile copies, then issue a CHANGE CONTROLFILECOPY ... VALIDATE; command for them. Then reissue the RECOVER command.

ORA-06171: not connected to target database

Cause: A command was issued but no connection to the target database has been established.

Action: Issue a CONNECT TARGET command to connect to the target database.

ORA-06172: not connected to recovery catalog database

Cause: A command was issued but no connection to the recovery catalog database has been established.

Action: Issue a CONNECT RCVCAT command to connect to the recovery catalog database. If you are not have a recovery catalog, then you must use the NOCATALOG option when starting RMAN.

ORA-06173: no set newname command has been issued for datafile name when restore clone

Cause: Clone type was specified for the controlfile, but no SET NEWNAME command has been previously issued for a datafile.

Issue SET NEWNAME command for every datafile in the recovery set.

06430-06449: NCR System 3000 Messages

ORA-06430: ssaio: seals do not match

Cause: A function was called with an invalid argument.

Action: Contact Oracle Support.

ORA-06431: ssaio: invalid block number

Cause: The file block number is out of range of the file. The additional information returns the block number.

Action: Verify that the block number is correct. Run dbfsize, and verify that the block number is in that range. Contact Oracle Support.

ORA-06432: ssaio: buffer not aligned

Cause: The I/O buffer is not aligned on a 2K boundary.

Action: Contact Oracle Support.

ORA-06433: ssaio: LSEEK error, unable to seek to requested block

Cause: The additional information returns the block number.

Action: Look up the additional information returned in operating system reference manual. Verify that the block number is correct.

ORA-06434: ssaio: read error, unable to read requested block from database file

Cause: The read system call returned an error.

Action: The additional information indicates the block number. Look up the additional information returned in operating system manual.

ORA-06435: ssaio: write error, unable to write requested block to database file

Cause: The write system call returned an error.

Action: The additional information indicates the block number. Look up the additional information returned in operating system manual.

ORA-06436: ssaio: asynchronous I/O failed due to incorrect parameters

Cause: The asynchronous I/O system call returned an error.

Action: The additional information indicates the block number. Look up the additional information returned in operating system manual.

ORA-06437: ssaio: the asynchronous write was unable to write to the database file

Cause: The asynchronous I/O system call returned an error.

Action: The additional information indicates the block number. Look up the additional information returned in operating system manual.

ORA-06438: ssaio: the asynchronous read was unable to read from the database file

Cause: The asynchronous I/O system call returned an error.

Action: The additional information indicates the block number. Look up the additional information returned in operating system manual.

ORA-06439: ssaio: the asynchronous write returned incorrect number of bytes

Cause: This write call may have been truncated.

Action: The additional information returns the block number and number of bytes. Verify that the block number and the number of bytes written are correct.

ORA-06440: ssaio: the asynchronous read returned incorrect number of bytes

Cause: This read call may have been truncated.

Action: The additional information returns the block number and number of bytes. Verify that the block number and the number of bytes read are correct.

ORA-06441: ssvwatev: incorrect parameter passed to function call

Cause: Either the oracle process ID, the wait time, or the event ID is invalid.

Action: The additional information indicates the process ID, time, and event ID.

ORA-06442: ssvwatev: failed with unexpected error number

Cause: System problems may exist on system. Examine error logs.

Action: The additional information indicates the error number. Look up the additional information returned in operating system manual.

ORA-06443: ssvpstev: incorrect parameter passed to function call

Cause: An invalid event ID is passed in to this routine.

Action: The additional information indicates the event ID.

ORA-06444: ssvpstev: failed with unexpected error number

Cause: System problems may exist on system. Examine error logs.

Action: The additional information indicates the error number. Look up the additional information returned in operating system manual.

ORA-06445: ssvpstevrg: incorrect parameters passed to function call

Cause: An invalid event ID, or the low and high event ID, do not exist.

Action: The additional information indicates the error number. It also contains the event ID, low boundary, and high boundary.

ORA-06446: ssvpstevrg: failed with unexpected error number

Cause: System problems may exist on system.

Action: Examine error logs. The additional information indicates the error number. Look up the additional information returned in operating system manual.

ORA-06447: ssvpstp: incorrect parameter passed to function call

Cause: Invalid oracle process ID is passed in to this routine.

Action: The additional information indicates the process ID.

ORA-06448: ssvpstp: failed with unexpected error number

Cause: System problems may exist on system.

Action: Examine error logs. The additional information indicates the error number. Look up the additional information returned in operating system manual.

ORA-06449: the list I/O or the sysvendor is not installed

Cause: The oracle executable tries to use the sysvendor interface (init.ora PARAMETER USE_SYSVENDOR=TRUE), but the UNIX kernel does not have the oracle executable sysvendor interface linked in.

Action: Set USE_SYSTVENDOR=FLASE in init.ora if you don't want to use this interface or you don't want to link the UNIX kernel with this interface for the

06500-06580: PL/SQL Messages

This section lists messages generated when Oracle detects a problem with
PL/SQL code. These ORA-nnnnn messages are usually followed by
PLS-nnnnn messages, which are listed in Chapter 16, "PL/SQL and FIPS Messages".

ORA-06500: PL/SQL: storage error

Cause: This is a rare internal error message. Memory has been exhausted or corrupted.

Action: Contact customer support.

ORA-06501: PL/SQL: program error

Cause: This is an internal error message. An error has been detected in a PL/SQL program.

Action: Contact customer support.

ORA-06502: PL/SQL: numeric or value error

Cause: An arithmetic, numeric, string, conversion, or constraint error occurred. For example, this error occurs if an attempt is made to assign the value NULL to a variable declared NOT NULL, or if an attempt is made to assign an integer larger than 99 to a variable declared NUMBER(2).

Action: Change the data, how it is manipulated, or how it is declared so that values do not violate constraints.

ORA-06503: PL/SQL: Function returned without value

Cause: A call to a PL/SQL function completed, but no RETURN statement was executed.

Action: Rewrite the PL/SQL function, making sure that it always returns a value of a proper type.

ORA-06504: PL/SQL: Return types of Result Set variables or query do not match

Cause: Number and/or types of columns in a query do not match the declared return type of a Result Set variable, or the declared types of two Result Set variables do not match.

Action: Change the program statement or declaration. Identify the query to which the variable, during execution, actually refers.

ORA-06505: PL/SQL: variable requires more than 32767 bytes of contiguous memory

Cause: A PL/SQL variable was declared with a constraint which required more than 32767 bytes of memory. PL/SQL does not currently support allocations of contiguous memory greater than 32767 bytes.

Action: Consider reducing the constraint in the variable declaration. If that is not possible, try changing the database or national character set to such, that requires less memory for the same constraint. Note: changing the character set will impact execution of all PL/SQL code.

ORA-06508: PL/SQL: could not find program unit being called

Cause: An attempt was made to call a stored program that could not be found. The program may have been dropped or incompatibly modified, or have compiled with errors.

Action: Check that all referenced programs, including their package bodies, exist and are compatible.

ORA-06509: PL/SQL: ICD vector missing for this package

Cause: This indicates a version clash between some package distributed with an Oracle product and the product executable.

Action: Contact customer support.

ORA-06510: PL/SQL: unhandled user-defined exception str

Cause: A user-defined exception was raised by PL/SQL code, but not handled.

Action: Fix the problem causing the exception or write an exception handler for this condition. It may be necessary to contact the application or database administrator.

ORA-06511: PL/SQL: cursor already open

Cause: An attempt was made to open a cursor that was already open.

Action: Close the cursor before attempting to reopen it.

ORA-06512: at str line num

Cause: This is usually the last of a message stack and indicates where a problem occurred in the PL/SQL code.

Action: Fix the problem causing the exception or write an exception handler for this condition. It may be necessary to contact the application or database administrator.

ORA-06513: PL/SQL: index for PL/SQL table out of range for host language array

Cause: An attempt was made to copy a PL/SQL table to a host language array, but an index in the table is either less than one or greater than the maximum size of the host language array. When copying PL/SQL tables to host language arrays, the table entry at index 1 is placed in the first element of the array, the entry at index 2 is placed in the second element of the array, and so on. If a table entry was not assigned, then the corresponding element in the host language array is set to NULL.

Action: Increase the size of the host language arrays or decrease the size of the PL/SQL table. Also make sure that you do not use index values less than 1.

ORA-06514: PL/SQL: The remote call cannot be handled by the server

Cause: The remote call had parameters that were cursor variables. This cannot be handled by stored procedures on your server.

Action: Avoid using cursor variables as parameters for stored procedures on this server or upgrade your server to a version that supports this.

For more information about using cursor variables, see the index entry on "cursor variable" in the PL/SQL User's Guide and Reference.

ORA-06515: PL/SQL: unhandled exception error

Cause: An exception was raised by PL/SQL code, but not handled. The exception number is outside the legal range of Oracle errors.

Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or DBA.

ORA-06516: PL/SQL: the Probe packages do not exist or are invalid

Cause: A Probe operation, probably an attempt to initialize the ORACLE server to debug PL/SQL, could not be completed because the Probe packages were not loaded or have become invalid.

Action: DBA should load the Probe packages. This can be done by running the PBLOAD.SQL script supplied with the RDBMS.

ORA-06517: PL/SQL: Probe error - error

Cause: An error occurred while passing a Probe operation to the server for execution.

Action: Refer to the entry for the embedded error message.

ORA-06518: PL/SQL: Probe version num incompatible with version num

Cause: The current version of Probe is incompatible with the version on the ORACLE server.

Action: Refer to the documentation to ensure that this degree of compatibility is supported.

ORA-06520: PL/SQL: Error loading external library

Cause: An error was detected by PL/SQL trying to load the external library dynamically.

Action: Check the following messages (if any) for more details.

ORA-06521: PL/SQL: Error mapping function

Cause: An error was detected by PL/SQL trying to map the specified function dynamically.

Action: Check the following messages (if any) for more details about the error.

ORA-06522: num

Cause: ORA-06520 or ORA-0652: 1 could provide more messages with a system specific error string.

Action: This message should give the cause for errors ORA-06520 or ORA-06521.

ORA-06523: Maximum number of arguments exceeded

Cause: There is an upper limit on the number of arguments that one can pass to the external function.

Action: Check the port specific documentation on how to calculate the upper limit.

ORA-06524: unsupported option: name

Cause: The option specified is an unsupported feature for external procedures.

Action: Correct the syntax in the external specification.

ORA-06525: length mismatch for CHAR or RAW data

Cause: The length specified in the length variable has an illegal value. This can happen if you have requested a PL/SQL INOUT, OUT or RETURN raw variable to be passed as a RAW with no corresponding length variable. This error can also happen if there is a mismatch in the length value set in the length variable and the length in the orlvstr or orlraw.

Action: Correct the external procedure code and set the length variable correctly.

ORA-06526: unable to load PL/SQL library

Cause: PL/SQL was unable to instantiate the library referenced by this referenced in the EXTERNAL syntax. This is a serious error and should normally not happen.

Action: Report this problem to customer support.

ORA-06530: reference to uninitialized composite

Cause: An object, LOB, or other composite was referenced as a left hand side without having been initialized.

Action: Initialize the composite with an appropriate constructor or whole-object assignment.

ORA-06531: reference to uninitialized collection

Cause: An element or member function of a nested table or VARRAY was referenced (where an initialized collection is needed) without the collection having been initialized.

Action: Initialize the collection with an appropriate constructor or whole-object assignment.

ORA-06532: subscript outside of limit

Cause: A subscript was greater than the limit of a VARRAY or non-positive for a varray or nested table.

Action: Check the program logic and increase the varray limit if necessary.

ORA-06533: subscript beyond count

Cause: An in-limit subscript was greater than the count of a varray or too large for a nested table.

Action: Check the program logic and explicitly extend if necessary.

ORA-06534: cannot access Serially Reusable package name in the context of a trigger

Cause: The program attempted to access a Serially Reusable package in the context of a trigger. Such an access is currently unsupported.

Action: Check the program logic and remove any references to Serially Reusable packages (procedure, function or variable references) which might happen n the context of a trigger.

ORA-06540: PL/SQL compilation error

Cause: A PL/SQL compilation error occurred. However, the user generally will not see this error message. Instead, there will be accompanying PLS-nnnnn error messages.

Action: See accompanying PLS-nnnnn error messages.

ORA-06541: PL/SQL: compilation error - compilation aborted

Cause: A PL/SQL compilation error occurred and the compilation was aborted. However, the user generally will not see this error message. Instead, there will be accompanying PLS-nnnnn error messages.

Action: See accompanying PLS-nnnnn error messages.

ORA-06544: PL/SQL: internal error, arguments:arg1, arg2, arg3, arg4, arg5, arg6, arg7, arg8

Cause: A PL/SQL internal error occurred.

Action: Report this as a bug; the first argument is the internal error number.

ORA-06545: PL/SQL: compilation error - compilation aborted

Cause: A PL/SQL compilation error occurred and the compilation was aborted completely without the compilation unit being written out to the backing store. Unlike ORA-06541, the user will always see this error along with the accompanying PLS-nnnnn error messages.

Action: See accompanying PLS-nnnnn error messages.

ORA-06550: line num, column num: str

Cause: A PL/SQL compilation error has occurred. The numbers given for line and column are the location in the PL/SQL block where the error occurred.

Action: Refer to the following PL/SQL messages for more information about the error.

ORA-06554: package DBMS_STANDARD must be created before using PL/SQL

Cause: The data dictionary script required by PL/SQL has not yet been run.

Action: See the Oracle8 Server Administrator's Guide and your Oracle operating system-specific documentation for more information.

ORA-06555: this name is currently reserved for use by user SYS

Cause: An attempt was made to create a user-owned package named STANDARD, DBMS_STANDARD, or DBMS_OUTPUT. This is not allowed.

Action: Choose another name for the package.

ORA-06556: the pipe is empty, cannot fulfill the UNPACK_MESSAGE request

Cause: There are no more items in the pipe.

Action: Check that the sender and receiver agree on the number and types of items placed on the pipe.

ORA-06557: null values are not allowed for any parameters to pipe ICD's

Cause: Internal error from the DBMS_PIPE package.

Action: Contact customer support.

ORA-06558: buffer in DBMS_PIPE package is full. No more items allowed

Cause: The pipe buffer size has been exceeded.

Action: Inspect the program to analyze the rate of input and output to the pipe. You might need to take items out of the pipe by executing RECEIVE_MESSAGE, or empty the entire pipe by executing PURGE on the pipe.

ORA-06559: wrong datatype requested, type, actual datatype is type

Cause: The sender put a different datatype on the pipe than that being requested, package DBMS_PIPE. The recognized datatypes and the corresponding numbers are: 6 - number, 9 - char, 12 - date.

Action: Check that the sender and receiver agree on the number and types of items placed on the pipe.

ORA-06560: pos, num, is negative or larger than the buffer size, num

Cause: Internal error from the DBMS_PIPE package.

Action: Contact Oracle customer support.

ORA-06561: given statement is not supported by package DBMS_SQL

Cause: Attempting to parse an unsupported statement using procedure PARSE provided by package DBMS_SQL.

Action: Only statements which begin with SELECT, DELETE, INSERT, UPDATE, LOCK, BEGIN, DECLARE or <= (PL/SQL label delimiter) are supported.

ORA-06562: type of OUT argument must match type of column or bind variable

Cause: An attempt was made to get the value of a column or a bind variable by calling procedure COLUMN_VALUE or VARIABLE_VALUE of package DBMS_SQL. However, the type of the given out argument was different from the type of the column or bind variable that was previously defined by calling procedure DEFINE_COLUMN, for defining a column, or BIND_VARIABLE, for binding a bind variable, of package DBMS_SQL.

Action: Pass in an OUT argument of the correct type when calling procedure COLUMN_VALUE or VARIABLE_VALUE. The right type is the type that was provided when defining the column or binding the bind variable.

ORA-06563: specified object cannot have subparts

Cause: The name to be resolved was specified with three parts (a.b.c) but the a.b part resolves to an object that does not have nested attributes. This can also happen with a two-part name, a.b.

Action: Specify a valid object.

ORA-06564: object name does not exist

Cause: The named object could not be found. Either it does not exist or you do not have permission to access it.

Action: Create the object or get permission to access it.

ORA-06565: cannot execute name from within stored procedure

Cause: The named procedure cannot be executed from within a stored procedure, function, or package. This function can only be used from PL/SQL anonymous blocks.

Action: Remove the procedure from the calling stored procedure.

ORA-06566: invalid number of rows specified

Cause: An invalid number of rows was specified in a call to the procedures DEFINE_COLUMN in the package DBMS_SQL. For a given parsed statement in a given cursor, all columns must be defined to have the same number of rows, so all the calls to DEFINE_COLUMN must specify the same number of rows.

Action: Specify a number that matches the number for previously defined columns.

ORA-06567: invalid number of values specified

Cause: An invalid number of values to be bound was specified in a call to the procedure BIND_VARIABLE in the package DBMS_SQL. For a given parsed statement in a given cursor, the same number of values must be bound for all bind variables, so all the calls to BIND_VARIABLE must specify the same number of values.

Action: Make sure that the same number of values are given for each of the bind variables.

ORA-06568: obsolete ICD procedure called

Cause: An obsolete ICD procedure was called by a PL/SQL program. The PL/SQL program was probably written for an earlier release of Oracle.

Action: Ensure that all PL/SQL packages are upgraded to the latest release of Oracle by following the upgrade instructions noted in the README document or by running the CATPROC.SQL script.

ORA-06569: collection bound by bind_array contains no elements

Cause: A collection with zero elements was bound to a bind variable in a call to procedure BIND_ARRAY in the package DBMS_SQL. In order to execute a bind of a collection, the collection must contain at least one element. If no elements are present then at execute time there will be no value for this bind and the statement is meaningless.

Action: Fill the collection with the elements you want to bind and try the bind call again.

ORA-06570: shared pool object does not exist, cannot be pinned

Cause: The specified shared pool shared cursor could not be found. Therefore, it cannot be pinned.

Action: Make sure that a correct shared cursor name is given. Names are a string of the form "HHHHHHHH,SDDDDDDDDDD" where the Hs are an 8-digit hex number from the "address" column of V$SQLAREA, and the Ds are a 1- to 10-digit decimal number with an optional leading sign from the "hash_value" column.

ORA-06571: function name does not guarantee not to update database

Cause: There are two possible causes for this message:

Action: If the referenced function is a packaged PL/SQL function: Recreate the PL/SQL function with the required pragma; be certain to include the "Write No Database State" (WNDS) argument in the argument list of the pragma.

If the referenced function is a stand-alone PL/SQL function: Do not use the function.

ORA-06572: function name has out arguments

Cause: A SQL statement references either a packaged or a stand-alone PL/SQL function that contains an OUT parameter in its argument list. PL/SQL functions referenced by SQL statements must not contain the OUT parameter.

Action: Recreate the PL/SQL function without the OUT parameter in the argument list.

ORA-06573: function name modifies package state, cannot be used here

Cause: There are two possible causes for this message:

Action: If the function is a packaged PL/SQL function: recreate the function and include a pragma containing the "Write no Package State" (WNPS).

If the function is a stand-alone PL/SQL function: delete the function from the SQL statement.

ORA-06574: function name references package state, cannot execute remotely

Cause: There are two possible causes for this message:

    Only local functions that are referenced in a SELECT list, VALUES clause of an INSERT statement, or SET clause of an UPDATE statement can modify a package state.

Action: If the function is a packaged function: Recreate the function and include a pragma containing the "Write no Package State" (WNPS) and "Read no Package State" (RNPS) arguments.

If the function is a stand-alone function: Do not call the function.

ORA-06575: function name is in an invalid state

Cause: A SQL statement references a PL/SQL function that is in an invalid state. Oracle attempted to compile the function, but detected errors.

Action: Check the SQL statement and the PL/SQL function for syntax errors or incorrectly assigned, or missing, privileges for a referenced object.

ORA-06580: Hash Join ran out of memory while keeping large rows in memory

Cause: Hash Join reserved 3 slots (each slot size = DB_BLOCK_SIZE * HASH_JOIN_MULTIBLOCK_IO_COUNT) for a row. If a row is larger than that, this error will be raised.

Action: Increase HASH_JOIN_MULTIBLOCK_IO_COUNT so that each joined row fits in a slot. HASH_AREA_SIZE may also need to be increased.

For more information about hashing and managing hash clusters, see the index entries on "hash clusters" in the Oracle8 Server Application Developer's Guide and on "hashing, how to use" in Oracle8 Server Tuning.

06581-06591: European OEM Ports Messages

The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.

06600-06699: SQL*Net Messages

The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.

06700-06899: SQL*Net TLI Messages

The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.

06900-06939: CMX Messages

The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.

06950-06999: SQL*Net AppleTalk Messages

The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.

07000-07099: SQL*Connect for DB2 Messages

The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.

07100-07199: SQL*Connect for IMS Messages

The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.

07200-07499: UNIX Messages

ORA-07200: slsid: ORACLE_SID not set

Cause: The environment variable (ORACLE_SID) is not set.

Action: Set ORACLE_SID environment variable.

ORA-07201: slhom: $ORACLE_HOME variable not set in environment

Cause: $(ORACLE_HOME) environment variable not set.

Action: Set $ORACLE_HOME.

ORA-07202: sltln: invalid parameter to sltln

Cause: The sltln name translation routine was called with invalid arguments. The input or output strings were either NULL or 0 length. This is probably an internal error.

Action: Contact Oracle Support.

ORA-07203: sltln: attempt to translate a long environment variable

Cause: A string was passed to sltln containing a long environment variable. sltln accepts environment names of 30 or less characters.

Action: Shorten environment variable name to less than 30 characters.

ORA-07204: sltln: name translation failed due to lack of output buffer space

Cause: The sltln routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred. This is possibly an internal error.

Action: Verify output buffer length stored in sercose[0]. Path names are limited to 255 characters.

ORA-07205: slgtd: time error, unable to obtain time

Cause: Time() system call returned an error. This is possibly an OS error.

Action: Examine additional information returned. Contact Oracle Support.

ORA-07206: slgtd: gettimeofday error, unable to obtain time

Cause: gettimeofday() system call returned an error. This is possibly an OS error.

Action: Examine additional information returned. Contact Oracle Support.

ORA-07207: sigpidu: process ID string overflows internal buffer

Cause: The sigpidu routine is given a maximum length buffer to hold process ID string. An overflow of this buffer occurred. This is an internal error.

Action: Contact Oracle Support.

ORA-07208: sfwfb: failed to flush dirty buffers to disk

Cause: The fsync system call returned an error. This is possibly an OS error.

Action: Examine additional information returned. Contact Oracle Support.

ORA-07209: sfofi: file size limit was exceeded

Cause: The size of the file to be opened exceeded the OS limit imposed on this process.

Action: Run osh to increase the file size limit.

ORA-07210: slcpu: getrusage error, unable to get cpu time

Cause: Getrusage system call returned an error. This is possibly an OS error.

Action: Examine additional information returned. Contact Oracle Support.

ORA-07211: slgcs: gettimeofday error, unable to get wall clock

Cause: gettimeofday system call returned an error. This is possibly an OS error.

Action: Examine additional information returned in OS reference manual. Contact Oracle Support.

ORA-07212: slcpu: times error, unable to get cpu time

Cause: Times system call returned an error. This is possibly an OS error.

Action: Examine additional information returned. Contact Oracle Support.

ORA-07213: slgcs: times error, unable to get wall clock

Cause: Times system call returned an error. This is possibly an OS error.

Action: Examine additional information returned in OS reference manual. Contact Oracle Support.

ORA-07214: slgunm: uname error, unable to get system information

Cause: uname system call returned an error. This is possibly an OS error.

Action: Examine additional information returned in OS reference manual. Contact Oracle Support.

ORA-07215: slsget: getrusage error

Cause: Getrusage system call returned an error. This is possibly an OS error.

Action: Examine additional information returned. Look for information in OS reference. Contact Oracle Support.

ORA-07216: slghst: gethostname error, unable to get name of current host

Cause: Gethostname system call returned an error. This is possibly an OS error.

Action: Examine additional information returned in OS reference manual. Contact Oracle Support.

ORA-07217: sltln: environment variable cannot be evaluated

Cause: Getenv call returned a null pointer.

Action: Set the environment variable and try again.

ORA-07218: slkhst: could not perform host operation

Cause: UNIX system() call failed.

Action: Examine system error message.

ORA-07219: slspool: unable to allocate spooler argument buffer

Cause: Malloc failed to allocate space to hold spooler arguments. The process may have run out of heap space.

Action: Examine additional information returned in OS reference manual. Contact Oracle Support.

ORA-07220: slspool: wait error

Cause: Wait returned an error when waiting for spool job to complete. This is possibly a spooler program error.

Action: Examine additional information returned. Refer to the OS reference manual. Contact Oracle Support.

ORA-07221: slspool: exec error, unable to start spooler program

Cause: Exec failed when starting line printer spooler command. It is likely that either the default line printer command, or ORACLE_LPPROG, is incorrectly set.

Action: Verify that the default line printer command and ORACLE_LPPROG are set correctly. Set ORACLE_LPPROG to working line printer spooler.

ORA-07222: slspool: line printer spooler command exited with an error

Cause: The line printer spooler exited with a non-zero return value. This probably indicates an error in spooling file.

Action: Verify that line printer spooler is up. Verify that ORACLE_LPPROG, and ORACLE_LPARG are set properly. Examine exit value returned for additional information.

ORA-07223: slspool: fork error, unable to spawn spool process

Cause: Fork system call failed to create additional process. It is probable that the resource limit has been reached.

Action: Examine additional information returned. Retry operation. Contact system administrator.

ORA-07224: sfnfy: failed to obtain file size limit; errno = numbers

Cause: The ulimit system call returned an error.

Action: Examine errno. Contact Oracle Support.

ORA-07225: sldext: translation error, unable to expand file name

Cause: Additional information returned is error returned from sltln.

Action: Examine additional information.

ORA-07226: rtneco: unable to get terminal mode

Cause: The ioctl call returned an error. The process may have run out of heap space.

Action: Examine additional information for errno. Contact Oracle Support.

ORA-07227: rtneco: unable to set noecho mode

Cause: The ioctl call returned an error. The process may have run out of heap space.

Action: Examine additional information for errno. Contact Oracle Support.

ORA-07228: rtecho: unable to restore terminal to echo mode

Cause: The ioctl call returned an error. The process may have run out of heap space.

Action: Examine additional information for errno. Contact Oracle Support.

ORA-07229: slcpuc: error in getting number of CPUs

Cause: Error in mpcntl system call.

Action: Examine errno. Contact system administrator.

ORA-07230: slemcr: fopen error, unable to open error file

Cause: Fopen failed to open file.

Action: Try to determine which file was not opened. Verify that the file exists and is accessible.

ORA-07231: slemcc: invalid file handle, seals do not match

Cause: Function was called with an invalid argument. The file handle used was not obtained be slemcr. This is an internal error.

Action: Contact Oracle Support.

ORA-07232: slemcc: fclose error

Cause: An error was encountered when closing the file. The process may have run out of heap space.

Action: Contact system administrator.

ORA-07233: slemcw: invalid file handle, seals do not match

Cause: Function was called with an invalid file handle. File handle was not obtained by slemcr. This is an internal error.

Action: Contact Oracle Support.

ORA-07234: slemcw: fseek error

Cause: Failure to seek to desired position in file. The process may have run out of heap space. This is possibly an internal error.

Action: Verify that the error message file is intact. Try to regenerate error message file. Contact Oracle Support.

ORA-07235: slemcw: fwrite error

Cause: Failure to write item to file. The process may have run out of heap space. This is possibly a permissions problem.

Action: Retry operation.

ORA-07236: slemop: open error

Cause: Failure to open error file. This is possibly a permissions problem.

Action: Verify permission on error message file. Examine additional information for errno.

ORA-07237: slemcl: invalid file handle, seals do not match

Cause: Function was called with an invalid file handle. Handle was not obtained by previous call to slemop. This is an internal error.

Action: Contact Oracle Support.

ORA-07238: slemcl: close error

Cause: Failure to close file. This is possibly an OS error.

Action: Contact system administrator. Examine additional information for errno.

ORA-07239: slemrd: invalid file handle, seals do not match

Cause: Function was called with invalid file handle. Handle was not obtained by call to slemop. This is an internal error.

Action: Contact Oracle Support.

ORA-07240: slemrd: seek error

Cause: Failure to seek to desired position in file. This is possibly an OS error.

Action: Verify that error file is still intact. Verify space on device. Contact system administrator. Examine additional information for errno.

ORA-07241: slemrd: read error

Cause: Failure to read file. This is possibly an OS error.

Action: Verify that error file is intact. Regenerate error message file. Contact Oracle Support. Examine additional information for errno.

ORA-07242: slembfn: translation error, unable to translate error file name

Cause: Additional information indicates error returned from sltln.

Action: Examine additional information.

ORA-07243: sftget: supplied buffer not big enough to hold entire line

Cause: The fgets call read only part of the line, because the supplied buffer was not big enough. This is an internal error.

Action: Contact Oracle Support. Additional information indicates how big the supplied buffer was.

ORA-07244: ssfccf: create file failed, file size limit reached

Cause: An attempt was made to create a file that exceeds the process's file size limit.

Action: Run osh to raise the file size limit.

ORA-07245: sfccf: unable to lseek and write the last block

Cause: An attempt was made to move and write to a bad device address.

Action: Examine errno. There may be a lack of space on device.

ORA-07246: sfofi: open error, unable to open database file

Cause: sfofi returns an error. This is an internal error.

Action: Contact Oracle Support.

ORA-07247: sfrfb: read error, unable to read requested block from database file

Cause: sfrfb returns an error. This is an internal error.

Action: Contact Oracle Support.

ORA-07248: sfwfb: write error, unable to write database block

Cause: sfwfb returns an error. This is an internal error.

Action: Contact Oracle Support.

ORA-07249: slsget: open error, unable to open /proc/pid

Cause: Open() returns an error. This is an internal error.

Action: Verify that /proc has the correct permissions.

ORA-07250: spcre: semget error, unable to get first semaphore set

Cause: An error occurred when trying to get first semaphore set.

Action: Examine errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested.

ORA-07251: spcre: semget error, could not allocate any semaphores

Cause: Semget failed to even allocate a single semaphore. Either they are all in use, or the system is not configured to have any semaphores.

Action: Verify that all semaphores are in use. Verify that system is configured to have semaphores. Examine errno.

ORA-07252: spcre: semget error, could not allocate semaphores

Cause: semget system call returned an error. There is possibly a resource limit problem.

Action: Examine errno. Verify that enough semaphores are available in system. If additional errors occur in destroying the semaphore sets, then sercose[0] will be non-zero. If this occurs, remove the semaphore sets using ipcrm.

ORA-07253: spdes: semctl error, unable to destroy semaphore set

Cause: semctl system call returned an error.

Action: Verify semaphore sets. This may require manual cleanup. Examine additional information returned. Consult OS reference manual.

ORA-07254: spdcr: translation error while expanding $ORACLE_HOME/bin/oracle

Cause: An error occurred while translating the name of the oracle executable.

Action: Examine sercose[0] for error returned from sltln. Perhaps $(ORACLE_HOME) is not set correctly.

ORA-07255: spini: cannot set up signal handler

Cause: System failed to set up signal handler.

Action: Examine errno and sercose[0] for the signal number that failed.

ORA-07256: sptrap: cannot set up signal handler to catch exceptions

Cause: System failed to set up signal handler to catch exceptions.

Action: Examine errno and sercose[0] for the signal number that failed.

ORA-07257: spdcr: translation error expanding program name

Cause: Error occurred when expanding program name ora_PNAME_sid. The result of this translation is put in argv[0] of oracle process.

Action: Examine error returned by sltln returned in sercose[0].

ORA-07258: spdcr: fork error, unable to create process

Cause: An error occurred when creating a new process.

Action: Examine errno. Perhaps a system limit on the number of processes has been exceeded.

ORA-07259: spdcr: exec error, detached process failed in startup

Cause: An oracle detached process died shortly after startup. Wait() indicates that a child process terminated.

Action: Examine $ORACLE_HOME/dbs directory for trace or core files. Examine errno.

ORA-07260: spdcr: wait error

Cause: Wait system call returned an error.

Action: Examine errno.

ORA-07261: spdde: kill error, unable to send signal to process

Cause: Kill system call returned an error. This is possibly an attempt to destroy an already gone process.

Action: Examine errno.

ORA-07262: sptpa: sptpa called with invalid process ID

Cause: This is an internal error.

Action: Contact Oracle Support.

ORA-07263: sptpa: kill error

Cause: Kill system call returned an error. This is possibly an OS error.

Action: Examine errno. Additional information indicates the process ID tested.

ORA-07264: spwat: semop error, unable to decrement semaphore

Cause: Semop system call returned an error. Semaphore set may not exist.

Action: Examine errno. Semaphore ID is returned in sercose[0]. Verify semaphore set exists. A possible cause for this error is that a "shutdown abort" was done while this process was running.

ORA-07265: sppst: semop error, unable to increment semaphore

Cause: Semop system call returned an error. Semaphore set may not exist.

Action: Examine errno. Semaphore ID is returned in sercose[0]. Verify semaphore set existence. A possible cause for this error is that a "shutdown abort" was done while this process was running.

ORA-07266: sppst: invalid process number passed to sppst

Cause: Function was passed an invalid oracle process ID. This is an internal error.

Action: Contact Oracle Support.

ORA-07267: spwat: invalid process number

Cause: Function was passed an invalid oracle process ID. This is an internal error.

Action: Additional information indicates the invalid process ID.

ORA-07268: szguns: getpwuid error

Cause: Getpwuid() failed to find an entry in the passwd file for a user.

Action: Add an entry for the user in the passwd file.

ORA-07269: spdcr: detached process died after exec

Cause: Detached process successfully execed, but died shortly thereafter.

Action: Examine termination code for information about why process exited. Look for core dump or trace file. Additional information indicates exit code and termination status.

ORA-07270: spalck: setitimer error, unable to set interval timer

Cause: An error occurred while trying to set an interval timer. This is probably a porting problem.

Action: Examine errno.

ORA-07271: spwat: invalid oracle process number

Cause: Function was called with an invalid oracle process number (0). This is an internal error.

Action: Contact Oracle Support.

ORA-07272: spwat: invalid semaphore set ID

Cause: Semaphore ID fetched from SGA was not initialized to valid value. Additional information returned is semaphore set index, and oracle process number. This is an internal error.

Action: Verify semaphore set index. Verify oracle process number.

ORA-07273: sppst: invalid semaphore ID

Cause: Semaphore ID fetched from SGA contained an invalid value. Additional information returned is semaphore set index and oracle process number. This is an internal error.

Action: Verify semaphore set index. Verify oracle process number.

ORA-07274: spdcr: access error, access to oracle denied

Cause: Failure to access oracle program. Verify that $ORACLE_HOME/bin/oracle or $ORABCKPRG exist and are executable.

Action: Examine errno.

ORA-07275: unable to send signal to process

Cause: The kill system call returned an error. This is possibly an attempt to signal a process which does not exist.

Action: Examine errno.

ORA-07276: no dba group in /etc/group

Cause: A group has not been set up for dba users.

Action: Contact system administrator. Set up dba group in /etc/group.

ORA-07277: spdde: illegal pid passed as argument

Cause: A 0 pid was passed to spdde. This is an internal error.

Action: Contact Oracle Support.

ORA-07278: splon: ops$username exceeds buffer length

Cause: Splon constructed an ops$username logon which exceeded the allotted buffer space.

Action: Use a shorter UNIX username or use an Oracle username. Contact Oracle Support.

ORA-07279: spcre: semget error, unable to get first semaphore set

Cause: An error occurred when trying to get first semaphore set.

Action: Examine errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested.

ORA-07280: slsget: unable to get process information

Cause: The ioctl call returned an error. This is possibly an OS error.

Action: Examine additional information for errno. Contact Oracle Support.

ORA-07281: slsget: times error, unable to get cpu time

Cause: Times system call returned an error. This is possibly an OS error.

Action: Examine additional information returned. Contact Oracle Support.

ORA-07282: sksaprd: string overflow

Cause: The internal buffer is not big enough to hold the archive control string. This is an internal restriction.

Action: Try a shorter archive control string.

ORA-07283: sksaprd: invalid volume size for archive destination

Cause: An invalid volume size was specified.

Action: Specify a valid volume size in the archive control string.

ORA-07284: sksaprd: volume size specification not terminated properly

Cause: Some non-numeric text follows the volume size specification.

Action: Enter a correct archive control string.

ORA-07285: sksaprd: volume size should not be specified for a disk file

Cause: Volume size was specified for a disk file.

Action: If archiving to a disk file, do not specify its volume size.

ORA-07286: sksagdi: cannot obtain device information

Cause: Stat on the log archiving device failed.

Action: Examine the returned OSD error for the reason of failure.

ORA-07287: sksagdi: unsupported device for log archiving

Cause: Log archiving to this device is unsupported.

Action: Try log archiving to a supported device.

ORA-07290: sksagdi: specified directory for archiving does not exist

Cause: The specified path name is not a directory.

Action: Verify that the archive destination directory exists.

ORA-07300: smscre: translation error while expanding $ORACLE_HOME/dbs/sgadefsid.dbf

Cause: Failure of sltln($ORACLE_HOME/dbs/sgadefsid.dbf) in smscre.

Action: Examine additional return error for more information.

ORA-07301: smscre: $ORACLE_HOME/dbs/sgadefsid.dbf file already exists when creating sga

Cause: The sgadef file should not exist when trying to create the SGA. Otherwise a running instance could be clobbered. The error from sltln is stored in sercose[0].

Action: Verify that database is really down, and delete the sgadef file. This should only happen when system has crashed with the database up. Cleaning up sgadef files can be done out of /etc/rc.

ORA-07302: smscre: create failure in creating $ORACLE_HOME/dbs/sgadefsid.dbf

Cause: Create() failed when trying to create the sgadef file.

Action: Verify permissions on $(ORACLE_HOME)/dbs directory.

ORA-07303: smscre: illegal database buffer size

Cause: The database buffer size must be a multiple of the database block size and less than the maximum block size.

Action: DB_BLOCK_SIZE parameter is correct in init.ora.

ORA-07304: smscre: illegal redo buffer size

Cause: The redo buffer size must be a multiple of machine block size.

Action: Verify that the LOG_BUFFER init.ora parameter is correct.

ORA-07305: sms1sg: ftok error in creating sga

Cause: The ftok() library call failed in sms1sg().

Action: Verify that the $ORACLE_HOME/dbs/sgadefsid.dbf file exists. If it does, then this is a possible system failure. Perhaps System V compatibility is not enabled.

ORA-07306: sms1sg: shmget error, unable to get a shared memory segment

Cause: Error in shmget. The code fails to find a single segment large enough for the entire SGA, but cannot continue to the next allocation model because of a fatal error.

Action: Examine errno. Verify that enough shared memory is available on the system to fit the entire SGA.

ORA-07307: sms1sg: shmat error, unable to attach sga

Cause: Failed to attach shared memory segment, after having gotten it.

Action: Examine errno. Verify that the SGA attach address is valid.

ORA-07308: smscre: write error when writing $ORACLE_HOME/dbs/sgadefsid.dbf file

Cause: Write call failed in smscre. Possibly, the device is out of space.

Action: Examine errno.

ORA-07309: smscre: close error, unable to close $ORACLE_HOME/dbs/sgadefsid.dbf file

Cause: Close system call returned an error. This is possibly an operating system failure.

Action: Examine errno.

ORA-07310: smscre: unable to create sga

Cause: All SGA allocation models have been tried, but none succeeded. This is possibly an Oracle system error.

Action: Try reconfiguring the UNIX kernel to fit the entire SGA into one segment.

ORA-07311: smsdes: name translation failure of sgadef.dbf file name

Cause: Failure to expand out $ORACLE_HOME/dbs/sgadefsid.dbf file name.

Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are properly set. Examine error number from sltln returned for additional error.

ORA-07312: smsdes: open error, unable to open sgadef.dbf file

Cause: Open failed when trying to open sgadef.dbf file. This is possibly a permission problem.

Action: Verify errno. Verify that sgadef.dbf file exists.

ORA-07313: smsdes: read error, unable to read sgadef.dbf file

Cause: Read system call returned an error when attempting to read $ORACLE_HOME/dbs/sgadefsid.dbf.

Action: Examine errno. Sgadef file may be corrupted or incompatible with Oracle version.

ORA-07314: smsdes: shmctl error when trying to destroy shared memory segment

Cause: Shmctl(IPC_RMID) called failed when trying to destroy shared memory segment. This is possibly a permission problem.

Action: Examine errno. Verify that shared exist. It may be necessary to manually remove segments.

ORA-07315: smsdes: close error, unable to close sgadef.dbf file

Cause: An error occurred in close(), when closing sgadef.dbf file. This is possibly an operating system error.

Action: Verify that sgadef.dbf file has been deleted.

ORA-07316: smsdes: unlink error, unable to destroy sgadef.dbf file

Cause: Unlink() error occurred when attempting to destroy sgadef.dbf file.

Action: Examine errno. Verify that sgadef.dbf file has been destroyed. This may require manual cleanup.

ORA-07317: smsget: translation error when expanding sgadef.dbf filename

Cause: Error occurred translating $ORACLE_HOME/dbs/sgadefsid.dbf.

Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are set correctly. Examine error returned from sltln for additional error.

ORA-07318: smsget: open error when opening sgadef.dbf file

Cause: Failure to open sgadef.dbf file. This is possibly a permission problem.

Action: Examine errno. Verify that sgadef.dbf file exists.

ORA-07319: smsget: read error when trying to read sgadef.dbf file

Cause: Read had an error when reading sgadef.dbf file.

Action: Examine errno. Verify that the file exists and is correct size.

ORA-07320: smsget: shmat error when trying to attach sga

Cause: Failure to attach segment. This is possibly an operating system error.

Action: Examine errno. Sercose[0] returns segment ID. Verify that segment exists and that permissions are correct.

ORA-07321: smsget: shmat error, unable to attach segment at requested address

Cause: sercose[0] returns segment ID.

Action: Examine errno.

ORA-07322: smsget: close error, unable to close sgadef.dbf file

Cause: Failure to close sgadef.dbf file. This is possibly an OS error.

Action: Retry.

ORA-07323: smsfre: shmdt error, unable to delete sga

Cause: Problem deleting shared segments.

Action: Retry. Examine errno. This may require manual cleanup of shared memory segments.

ORA-07324: smpall: malloc error while allocating pga

Cause: Malloc library routine returned an error. Possibly, it is out of swap space.

Action: Examine errno.

ORA-07325: smsacx: malloc error when allocating context area

Cause: Malloc library routine returned an error. Possibly, it is out of swap space.

Action: Examine errno.

ORA-07326: smsfre: attempt to free un-mapped sga

Cause: Smsfre was called when the SGA was not mapped. This is an internal error.

Action: Contact Oracle Support.

ORA-07327: smpdal: attempt to destroy pga when it was not mapped

Cause: smpdal was called when the PGA had not been previously created. This is an internal error.

Action: Contact Oracle Support.

ORA-07328: smsmax: cannot guess the maximum size for a segment

Cause: shmget system call returned a fatal error.

Action: Examine errno. Additional information indicates the SGA model attempted.

ORA-07329: smscsg: too many shared memory segments

Cause: The internal data structure which holds segment information is full.

Action: Reconfigure the UNIX kernel to have bigger segments.

ORA-07330: smsnsg: unable to allocate the fixed portion of the SGA

Cause: The fixed portion of the SGA is too big to fit contiguously into one segment.

Action: Reconfigure the UNIX kernel to have bigger segments.

ORA-07331: smsnsg: unable to allocate the variable portion of the SGA

Cause: The variable portion of the SGA is too big to fit contiguously into one segment.

Action: Reconfigure the UNIX kernel to have bigger segments.

ORA-07332: smsnsg: unable to allocate redo buffers

Cause: Redo block size is too big, preventing each buffer from being allocated contiguously.

Action: Reconfigure the UNIX kernel to have bigger segments, or reduce the value of LOG_BUFFER parameter in init.ora.

ORA-07333: smsnsg: unable to allocate database buffers

Cause: Database block size is too big, preventing each buffer from being allocated contiguously.

Action: Reconfigure the UNIX kernel to have bigger segments, or reduce the value of DB_BLOCK_SIZE parameter in init.ora.

ORA-07334: smsnsg: too many shared memory segments

Cause: The internal data structure which holds segment information is full.

Action: Reconfigure the UNIX kernel to have bigger segments.

ORA-07335: smsmat: ftok error in creating sga

Cause: The ftok() library call failed in smsmat().

Action: Verify that sgadef.dbf file exists. If it does, then this is a possible system failure. Perhaps System V compatibility is not enabled. Additional information indicates the SGA model attempted.

ORA-07336: smsmat: shmget error, unable to get a shared memory segment

Cause: Error in shmget.

Action: Examine errno. Verify that enough shared memory is available on the system to fit the entire SGA. Additional information indicates the SGA model attempted.

ORA-07337: smsmat: shmat error, unable to attach sga

Cause: Failed to attach shared memory segment, after having gotten it.

Action: Examine errno. Verify that SGA attach address is valid. Additional information indicates the SGA model attempted.

ORA-07338: smscre: cannot test for existence of the sga file

Cause: The access system call returned an error. This is possibly an OS error.

Action: Examine errno returned and verify the permission on the sga file.

ORA-07339: spcre: maximum number of semaphore sets exceeded

Cause: The internal buffer is not big enough to hold the number of semaphore set identifiers requested.

Action: Reconfigure OS to have more semaphores per set.

ORA-07390: sftopn: translate error, unable to translate file name

Cause: An error occurred while expanding the file name to open. Additional information returns error generated in translation routine.

Action: Lookup additional error code for further information.

ORA-07391: sftopn: fopen error, unable to open text file

Cause: fopen library routine returned an error.

Action: Verify existence and permissions.

ORA-07392: sftcls: fclose error, unable to close text file

Cause: fclose library routine returned an error. This is possibly an internal error.

Action: Contact Oracle Support.

ORA-07400: slemtr: translated name for the message file is too long

Cause: The name for the message file overflows internal buffer.

Action: Try making the complete path-name of the message file shorter by reorganizing the directory hierarchy.

ORA-07401: sptrap: cannot restore user exception handlers

Cause: The system failed to restore user exception handlers.

Action: Examine errno and sercose[0] for the signal number that failed.

ORA-07402: sprst: cannot restore user signal handler

Cause: The system failed to restore user signal handlers.

Action: Examine errno and sercose[0] for the signal number that failed.

ORA-07403: sfanfy: db_writers parameter not valid

Cause: The DB_WRITERS parameter in init.ora exceeds the system-dependent maximum, or is less than 0.

Action: Change the DB_WRITERS parameter in init.ora.

ORA-07404: sfareq: Timeout occurred waiting for request to complete

Cause: The master database writer timed out waiting for a write or close to complete. One of the database writers may have stopped running.

Action: Examine all database writer trace files. Shut down the database and try to warm start.

ORA-07406: slbtpd: invalid number

Cause: An impossible request for binary to decimal conversion was made.

Action: This conversion cannot be performed.

ORA-07407: slbtpd: invalid exponent

Cause: An impossible request for binary to decimal conversion was made.

Action: This conversion cannot be performed.

ORA-07408: slbtpd: overflow while converting to packed decimal

Cause: An impossible request for binary to decimal conversion was made.

Action: This conversion cannot be performed.

ORA-07409: slpdtb: invalid packed decimal nibble

Cause: An impossible request for decimal to binary conversion was made.

Action: This conversion cannot be performed.

ORA-07410: slpdtb: number too large for supplied buffer

Cause: An impossible request for decimal to binary conversion was made.

Action: This conversion cannot be performed.

ORA-07411: slgfn: full path name too big for supplied buffer

Cause: The supplied buffer is not big enough to hold the full path name.

Action: The construction of the full path name cannot be performed.

ORA-07412: sfaslv: error getting entry in asynchronous write array

Cause: One of the database writer processes failed to locate its entry in the SGA.

Action: Contact Oracle Support.

ORA-07415: slpath: allocation of memory buffer failed

Cause: Malloc() failed to allocate buffer for storing ORACLE_PATH. System has run out of heap space.

Action: Additional information indicates errno.

ORA-07416: slpath: pathname construction failed; lack of output buffer space

Cause: The slpath routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred. This is possibly an internal error.

Action: Examine output buffer length stored in sercose[0] and constructed pathname length in sercose[1].

ORA-07417: sfareq: One or more database writers not active

Cause: One or more of the database writer processes is no longer running.

Action: Examine the trace files for the database writers. Shut down the database and try to warm start.

ORA-07418: sfareq: database writer got error in timing function

Cause: An error occurred when the database writer called the system timing function.

Action: Examine the database writer trace file. Shut down database and try to warm start.

ORA-07419: sfareq: database writer got error in timing function

Cause: An error occurred when the database writer called the system timing function.

Action: Examine the database writer trace file. Shut down database and try to warm start.

ORA-07425: sdpri: error names in translating dump file location

Cause: An oracle error occurred when translating the location of the dump file.

Action: Examine the error code.

ORA-07426: spstp: cannot obtain the location of dbs directory

Cause: An oracle error occurred when translating the location of the dbs directory.

Action: Examine additional information for the error returned from sltln.

ORA-07427: spstp: cannot change directory to dbs

Cause: chdir system call returned an error. This is possibly a permission problem.

Action: Examine additional information for the OS error code.

ORA-07428: smsgsg: ftok() returned error in calculating key for sga

Cause: The ftok() library call failed in smsgsg().

Action: Verify that the $ORACLE_HOME/sgadefsid.dbf file exists. If it does, this is a possible system failure. Perhaps System V compatibility is not enabled. The additional information indicates the segment where the error occurred.

ORA-07429: smsgsg: shmget() failed to get segment

Cause: A shared memory segment used for all or part of the SGA failed to be retrieved.

Action: Use the system error number in the error message to determine why the segment failed to be retrieved. If it does not exists, shutdown the database using the "abort" option, and then restart it. If the get failed because the permissions are incorrect, verify that the ownership of the oracle executable is the same as that on the shared memory segment.

ORA-07430: smsgsg: calculated and stored keys do not match

Cause: When smsgsg() gets a segment, it re-calculates the key for the segment. It then compares the value against the value stored in the sgadef file. If they do not match, then the file is probably corrupt.

Action: Shutdown the database and restart it.

ORA-07431: fork failed

Cause: The server process failed to fork a child process.

Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.

ORA-07432: unable to perform nested sleep

Cause: An attempt was made to make a process sleep when it was already sleeping. This platform does not support this capability.

Action: Try the SLEEP command when the process is not sleeping.

ORA-07440: WMON process terminated with error

Cause: The wakeup monitor process died.

Action: Warm start instance.

ORA-07441: function address must be aligned on address byte boundary

Cause: An improperly aligned function address was specified.

Action: Use a properly aligned function address.

ORA-07442: function address must be in the range number to number

Cause: An invalid function address was specified.

Action: Use a valid function address.

ORA-07443: function function not found

Cause: An invalid function name was specified.

Action: Use a valid function name.

ORA-07444: function address address is not readable

Cause: An invalid function name/address was specified.

Action: Use a valid function name/address.

ORA-07445: exception encountered: core dump [exception]

Cause: An OS exception occurred which should result in the creation of a core file. This is an internal error.

Action: Contact Oracle Support.

ORA-07446: sdnfy: bad value 'value' for parameter name

Cause: The directory specified as the value for the stated parameter failed to be used.

Action: Verify that the directory specified is a valid directory/file specification.

ORA-07447: ssarena: usinit failed

Cause: oracle failed to create a shared arena file.

Action: Use sercerrno field to determine cause of failure.

ORA-07448: ssarena: maximum number of shared arenas exceeded

Cause: oracle attempted to create more shared arena files than permitted.

Action: Raise the value for MAX_ARENA in init.ora.

ORA-07449: sc: usnewlock failed

Cause: oracle failed to acquire a shared arena lock.

Action: Examine result code in sercerrno to determine the cause of failure.

ORA-07450: sms1sg: vm_mapmem error, unable to create shared memory

Cause: Error in vm_mapmem. Failed to create SGA as a single shared memory segment.

Action: Examine result code returned in sercose[0].

ORA-07451: sms1sg: shared memory attach address incorrect

Cause: The vm_mapmem system call attached the SGA at an incorrect location.

Action: Verify that the SGA attach address is valid.

ORA-07452: sms1sg: failed to change SGA inheritance

Cause: The vm_inherit system called failed to change the inheritance of the SGA. This is possibly an operating system failure.

Action: Examine result code returned in sercose[0].

ORA-07453: smsmat: vm_mapmem error, unable to create shared memory

Cause: Error in vm_mapmem. Failure to create a segment of the SGA.

Action: Examine result code returned in sercerrno.

ORA-07454: smsmat: shared memory attach address incorrect

Cause: The vm_mapmem system call attached an SGA segment at an incorrect location.

Action: Verify that the SGA attach address is valid.

ORA-07455: smsmat: failed to change SGA segment inheritance

Cause: The vm_inherit system call failed to change the inheritance of a segment of the SGA. This is possibly an operating system failure.

Action: Examine result code returned in sercerrno.

ORA-07456: smsmax: cannot get cluster size

Cause: The cluster_stat system call failed to return status for the cluster. This is possibly an operating system failure.

Action: Examine result code in sercose[0].

ORA-07457: smsdes: name translation failure of sgadef.dbf file name

Cause: Failure to expand out $ORACLE_HOME/dbs/sgadefsid.dbf file name.

Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are properly set. Examine error number returned from sltln in sercose[0].

ORA-07458: smsdes: close error, unable to close sgadef.dbf

Cause: An error occurred in close while closing the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly an operating system error.

Action: Verify that the sgadef.dbf file has been deleted.

ORA-07459: smsvmfcre: name translation failure of sgadef.dbf file name

Cause: Failure to expand out $ORACLE_HOME/dbs/sgadefsid.dbf file name.

Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are properly set. Examine error number returned from sltln in sercose[0].

ORA-07460: smsvmfcre: sgadef.dbf already exists when creating SGA

Cause: The file $ORACLE_HOME/dbs/sgadefsid.dbf should not exist when trying to create the SGA; otherwise, a running instance could be clobbered.

Action: Verify that the database is down, and delete the sgadef.dbf file. This should only happen when the machine crashed with the database up.

ORA-07461: smsvmfcre: create failure in creating sgadef.dbf file

Cause: Open failed when trying to create the file $ORACLE_HOME/dbs/sgadefsid.dbf.

Action: Verify permissions on the $(ORACLE_HOME)/dbs directory.

ORA-07462: smsget: name translation error of sgadef.dbf file name

Cause: Failure to expand out $ORACLE_HOME/dbs/sgadefsid.dbf file name.

Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are properly set. Examine error number returned from sltln in sercose[0].

ORA-07463: smsget: open error when opening sgadef.dbf file

Cause: Open failed when opening the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly a permission problem.

Action: Examine errno. Verify that the file $ORACLE_HOME/dbs/sgadefsid.dbf exists.

ORA-07464: smsget: vm_mapmem or vm_allocate error when trying to attach SGA

Cause: The vm_mapmem or vm_allocate system call failed when attempting to attach a segment of the SGA.

Action: Examine result code returned in sercerrno. SGA segment number returned in sercose[1].

ORA-07465: smsget: shared memory attach address incorrect

Cause: The vm_mapmem system call attached an SGA segment at an incorrect location.

Action: Verify that the segment exists and that the SGA attach address is valid.

ORA-07466: smsget: failed to change SGA segment inheritance

Cause: The vm_inherit system call failed to change the inheritance of a segment of the SGA. This is possibly an operating system failure.

Action: Examine result code returned in sercerrno.

ORA-07467: smsget: close error, unable to close sgadef.dbf file

Cause: An error occurred in close while closing the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly an operating system failure.

Action: Examine errno.

ORA-07468: spwat: mset error, unable to set semaphore

Cause: The mset routine returned an error. Semaphore may not exist.

Action: Examine result code in sercerrno. Semaphore number returned in sercose[0].

ORA-07469: sppst: mclear error, unable to clear semaphore

Cause: The mclear routine returned an error. Semaphore may not exist.

Action: Examine result code in sercerrno. Semaphore number returned in sercose[0].

ORA-07470: snclget: cannot get cluster number

Cause: The cluster_status system call failed to get status information for the current cluster. This is possibly an operating system failure.

Action: Examine result code in sercose[0].

ORA-07471: snclrd: name translation error of sgadef.dbf file name

Cause: Failure to expand out $ORACLE_HOME/dbs/sgadefsid.dbf file name.

Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are properly set. Examine error number returned from sltln in sercose[0].

ORA-07472: snclrd: open error when opening sgadef.dbf file

Cause: Open failed when opening the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly a permission problem.

Action: Examine errno. Verify that the file $ORACLE_HOME/dbs/sgadefsid.dbf exists.

ORA-07473: snclrd: read error when trying to read sgadef.dbf file

Cause: Read had an error when reading sgadef.dbf file.

Action: Examine errno. Verify that file exists and is correct size.

ORA-07474: snclrd: close error, unable to close sgadef.dbf file

Cause: An error occurred in close, while closing the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly an operating system failure.

Action: Examine errno.

ORA-07475: slsget: cannot get vm statistics

Cause: The vm_statistics system call failed to get virtual memory statistics. This is possibly an operating system failure.

Action: Examine result code in sercerrno.

ORA-07476: slsget: cannot get mapped memory statistics

Cause: The vm_mapmem system call failed to get mapped memory statistics. This is possibly an operating system failure.

Action: Examine result code in sercerrno.

ORA-07477: scgcmn: lock manager not initialized

Cause: Lock manager must be initialized before converting locks. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07478: scgcmn: cannot get lock status

Cause: lm_stat_lock failed. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07479: scgcmn: cannot open or convert lock

Cause: lm_open or lm_open_convert failed. Possible lock manager failure.

Action: Examine result code in sercerrno.

ORA-07480: snchmod: cannot change permissions on $ORACLE_HOME/dbs/sgalm.dbf

Cause: When creating an instance, snlmini failed to change the permissions on $ORACLE_HOME/dbs/sgalm.dbf.

Action: Contact Oracle Support.

ORA-07481: snlmatt: cannot attach to lock manager instance

Cause: lm_attach failed to attach to lock manager instance. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07482: snlmini: cannot create lock manager instance

Cause: lm_create failed to create lock manager instance.

Action: Verify permissions on $ORACLE_HOME/dbs, and remove $ORACLE_HOME/dbs/sgalm.dbf if it exists, then retry.

ORA-07483: snlkget: cannot convert(get) lock

Cause: lm_convert failed to convert(get) lock. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07484: snlkput: cannot convert(put) lock

Cause: lm_convert failed to put lock value. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07485: scg_get_inst: cannot open instance number lock

Cause: lm_open failed. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07486: scg_get_inst: cannot convert(get) instance number lock

Cause: lm_convert failed to get lock value. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07487: scg_init_lm: cannot create lock manager instance

Cause: lm_create failed. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07488: scgrcl: lock manager not initialized

Cause: Lock manager must be initialized before releasing locks. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07489: scgrcl: cannot get lock status

Cause: lm_stat_lock failed during lock release/cancel. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07490: scgrcl: cannot convert lock

Cause: lm_convert failed during lock release/cancel. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07491: scgrcl: cannot cancel lock request

Cause: lm_cancel failed during lock release/cancel. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07492: scgrcl: cannot close lock

Cause: lm_close failed during lock release/cancel. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07493: scgrcl: lock manager error

Cause: An error was encountered releasing the lock. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07494: scgcm: unexpected error

Cause: Unknown or unexpected error code. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07495: spwat: lm_wait failed

Cause: lm_wait failed. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07496: sppst: lm_post failed

Cause: lm_post failed. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

ORA-07497: sdpri: cannot create trace file 'file'; errno = error

Cause: The trace file cannot be created for writing.

Action: Verify if the dump directory exists, and whether it is writable.

ORA-07498: spstp: unable to open /dev/resched

Cause: The rescheduling driver /dev/resched is not found or is not working properly.

Action: Examine installation of the Oracle rescheduling driver in the AIX kernel.

ORA-07499: spglk: cannot reschedule

Cause: The rescheduling driver /dev/resched is not open. This is an internal error.

Action: Contact Oracle Support.

07500-07999: VAX/VMS Messages

ORA-07500: scglaa: $cantim unexpected return

Cause: VMS system service $CANTIM returned an unexpected value.

Action: Look for system error message, and refer to VMS documentation.

ORA-07501: scgtoa: $deq unexpected return

Cause: VMS system service $DEQ returned an unexpected value.

Action: Look for system error message, and refer to VMS documentation.

ORA-07502: scgcmn: $enq unexpected return

Cause: VMS system service $ENQ returned an unexpected value.

Action: Look for system error message, and refer to VMS documentation.

ORA-07503: scgcmn: $setimr unexpected return

Cause: VMS system service $SETIMR returned an unexpected value.

Action: Look for system error message, and refer to VMS documentation.

ORA-07504: scgcmn: $hiber unexpected return

Cause: VMS system service $HIBER returned an unexpected value.

Action: Look for system error message, and refer to VMS documentation.

ORA-07505: scggt: $enq parent lock unexpected return

Cause: VMS system service $ENQ returned an unexpected value.

Action: Look for system error message, and refer to VMS documentation.

ORA-07506: scgrl: $deq unexpected return on lockid name

Cause: VMS system service $DEQ returned an unexpected value.

Action: Look for system error message, and refer to VMS documentation.

ORA-07507: scgcm: unexpected lock status condition

Cause: A global locking system service returned an unexpected value.

Action: Look for system error message (if any), and refer to VMS documentation, or contact Oracle Support.

ORA-07508: scgfal: $deq all unexpected return

Cause: VMS system service $DEQ returned an unexpected value.

Action: Look for system error message, and refer to VMS documentation.

ORA-07509: scgfal: $deq parent lock unexpected return

Cause: VMS system service $DEQ returned an unexpected value.

Action: Look for system error message, and refer to VMS documentation.

ORA-07510: scgbrm: $getlki unexpected return on lockid name

Cause: VMS system service $GETLKI returned an unexpected value.

Action: Look for system error message, and refer to VMS documentation.

ORA-07511: sscggtl: $enq unexpected return for master termination lock

Cause: VMS system service $ENQ returned an unexpected value.

Action: Look for system error message, and refer to VMS documentation.

ORA-07512: sscggtl: $enq unexpected return for client termination lock

Cause: VMS system service $ENQ returned an unexpected value.

Action: Look for system error message, and refer to VMS documentation.

ORA-07513: sscgctl: $deq unexpected return on cancel of term. lock

Cause: VMS system service $DEQ returned an unexpected value.

Action: Look for system error message, and refer to VMS documentation.

ORA-07514: scgcan: $deq unexpected return while canceling lock

Cause: VMS system service $DEQ returned an unexpected value.

Action: Look for system error message, and refer to VMS documentation.

ORA-07534: scginq: $getlki unexpected return on lockid name

Cause: VMS system service $GETLKI returned an unexpected value.

Action: Look for system error message, and refer to VMS documentation.

ORA-07548: sftopn: Maximum number of files already open

Cause: Too many test files open. This is an internal error.

Action: Contact Oracle Support.

ORA-07549: sftopn: $OPEN failure

Cause: VMS system service $OPEN failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07550: sftopn: $CONNECT failure

Cause: VMS system service $OPEN failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07551: sftcls: $CLOSE failure

Cause: VMS system service $CLOSE failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07552: sftget: $GET failure

Cause: VMS system service $GET failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07561: szprv: $IDTOASC failure

Cause: VMS system service $IDTOASC failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07562: sldext: extension must be 3 characters

Cause: An extension was found, but it is of improper length. This is an internal error.

Action: Contact Oracle Support.

ORA-07563: sldext: $PARSE failure

Cause: VMS system service $PARSE failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07564: sldext: wildcard in filename or extension

Cause: A wildcard was used in the file name.

Action: Reenter the file name completely.

ORA-07565: sldext: $SEARCH failure

Cause: VMS system service $SEARCH failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07568: slspool: $OPEN failure

Cause: VMS system service $OPEN failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07569: slspool: $CLOSE failure

Cause: VMS system service $CLOSE failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07570: szrfc: $IDTOASC failure

Cause: VMS system service $IDTOASC failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07571: szrfc: $FIND_HELD failure

Cause: VMS system service $FIND_HELD failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07572: szrfc: insufficient rolename buffer space

Cause: An OS role name was too long.

Action: Re-define the role name to be of correct length.

ORA-07573: slkhst: could not perform host operation

Cause: VMS system service LIB$SPAWN failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07574: szrfc: $GETUAI failure

Cause: VMS system service $GETUAI failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07576: sspexst: $GETJPIW failure on process ID number

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07577: no such user in authorization file

Cause: An attempt was made to set an INTERNAL password (for either DBA or OPER privilege), but the corresponding VMS account (either ORA__DBA or ORA__OPER) hasn't been created yet.

Action: Add a VMS account for ORA__DBA and/or ORA__OPER before trying to set a password for them.

ORA-07578: szprv: $FIND_HELD failure

Cause: VMS system service $FIND_HELD failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07579: spini: $DCLEXH failure

Cause: VMS system service $PARSE failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07580: spstp: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07581: spstp: cannot derive SID from unexpected process name

Cause: A background process did not have name of correct form.

Action: If the job name was changed, restore it. Otherwise, this is an internal error. Contact Oracle Support.

ORA-07582: spstp: ORA_SID has illegal value

Cause: The ORA_SID must exist and be less than 6 characters.

Action: Consult the VMS Installation Guide for information on setting the SID.

ORA-07584: spdcr: invalid value for ORA_sid_(proc_)PQL$_item

Cause: A logical name used to set a detached process quota value has an invalid value (probably non-numeric).

Action: Examine the values of these logical names. Correct the one in error and retry.

ORA-07585: spdcr: $PARSE failure

Cause: VMS system service $PARSE failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07586: spdcr: $SEARCH failure

Cause: VMS system service $SEARCH failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07587: spdcr: $CREPRC failure

Cause: VMS system service $CREPRC failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07588: spdcr: $GETJPIW get image name failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07589: spdde: system ID not set

Cause: The logical name ORA_SID doesn't translate to a valid value.

Action: Examine the value of ORA_SID in the process that gets the error, and correct the installation or command procedures that caused ORA_SID to be set incorrectly.

ORA-07590: spdde: $DELPRC failure

Cause: VMS system service $DELPRC failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07591: spdde: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07592: sspgprv: Error obtaining required privileges

Cause: While obtaining needed privileges, an error was returned from SYS$SETPRV. This is an internal error.

Action: Contact Oracle Support.

ORA-07593: ssprprv: Error release privileges

Cause: While releasing privileges, an error was returned from SYS$SETPRV. This is an internal error.

Action: Contact Oracle Support.

ORA-07594: spiip: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07595: sppid: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07596: sptpa: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07597: spguns: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07598: spwat: $SETIMR failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07599: spwat: $SCHDWK failure

Cause: VMS system service $SCHDWK failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07600: slkmnm: $GETSYIW failure

Cause: VMS system service $GETSYIW failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07601: spguno: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07602: spgto: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07605: szprv: $ASCTOID failure

Cause: VMS system service $ASCTOID failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07606: szprv: $CHKPRO failure

Cause: VMS system service $CHKPRO failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07607: szaud: $SNDOPR failure

Cause: VMS system service $SNDOPR failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07608: szprv: $GETUAI failure

Cause: VMS system service $GETUAI failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07609: szprv: $HASH_PASSWORD failure

Cause: VMS system service $HASH_PASSWORD failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07610: $GETJPIW failed in retrieving the user's MAC privileges

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07612: $GETUAI failed in retrieving the user's clearance level

Cause: VMS system service $GETUAI failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07613: $GETJPIW failed in retrieving the user's process label

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07614: $CHANGE_CLASS failed in retrieving the user's process label

Cause: VMS system service $CHANGE_CLASS failed.

Action: Examine system error message, and refer to SEVMS documentation.

ORA-07615: $CHANGE_CLASS failed in retrieving the specified file label

Cause: VMS system service $CHANGE_CLASSS failed.

Action: Examine system error message, and refer to SEVMS documentation.

ORA-07616: $CHANGE_CLASS failed in retrieving the specified device label

Cause: VMS system service $CHANGE_CLASS failed.

Action: Examine system error message, and refer to SEVMS documentation.

ORA-07617: $FORMAT_CLASS failed translating the binary label to a string

Cause: VMS system service $FORMAT_CLASS failed because the given binary classification was not valid.

Action: Examine system error message, and refer to SEVMS documentation.

ORA-07618: $IDTOASC failed translating a secrecy level

Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of a secrecy level.

Action: Define the entry in the rights database which the binary label specified references.

ORA-07619: $IDTOASC failed translating an integrity level

Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of an integrity level.

Action: Define the entry in the rights database which the binary label specified references.

ORA-07620: smscre: illegal database block size

Cause: An illegal database block size was specified in the parameter file. It must be positive, a multiple of 512, and less than the maximum physical I/O data size.

Action: Change db_block_size in the parameter file to conform to these limits.

ORA-07621: smscre: illegal redo block size

Cause: An illegal redo log buffer size was specified in the parameter file. It must be positive and a multiple of 512.

Action: Change log_buffer in the parameter file to conform to these limits.

ORA-07622: smscre: $CREATE failure

Cause: While creating the system global area (SGA) backing file, VMS system service $CREATE failed.

Action: Examine the system error message, and refer to VMS documentation.

ORA-07623: smscre: $CRMPSC failure

Cause: While creating the system global area (SGA), VMS system service $CRMPSC failed.

Action: Examine the system error message, and refer to VMS documentation.

ORA-07624: smsdes: $DGBLSC failure

Cause: While deleting the system global area (SGA), VMS system service $DGBLSC failed.

Action: Examine the system error message, and refer to VMS documentation.

ORA-07625: smsget: $MGBLSC failure

Cause: While mapping the system global area (SGA) during logon, VMS system service $MGBLSC failed. Probably, oracle has not been started up.

Action: Examine the system error message, and refer to VMS documentation. Start up oracle if it is not already started.

ORA-07626: smsget: sga already mapped

Cause: An attempt to map the SGA during logon failed, because it was already mapped. This is an internal error.

Action: Exit program and try again. Contact Oracle Support.

ORA-07627: smsfre: $CRETVA failure

Cause: While unmapping the system global area (SGA) during logoff, VMS system service $CRETVA failed.

Action: Examine the system error message, and refer to VMS documentation.

ORA-07628: smsfre: sga not mapped

Cause: An attempt to unmap the SGA during logoff failed, because it was not mapped. This is an internal error.

Action: Exit program and try again. Contact Oracle Support.

ORA-07629: smpall: $EXPREG failure

Cause: While extending the program global area (PGA), VMS system service $EXPREG failed. This often happens when the virtual memory page count quota is exceeded.

Action: Examine the system error message, and refer to VMS documentation.

ORA-07630: smpdal: $DELTVA failure

Cause: While deleting the program global area (PGA) during logoff, VMS system service $DELTVA failed.

Action: Examine the system error message, and refer to VMS documentation.

ORA-07631: smcacx: $EXPREG failure

Cause: While creating or extending a context area, VMS system service $EXPREG failed. This often happens when the virtual memory page count quota is exceeded.

Action: Examine the system error message, and refer to VMS documentation.

ORA-07632: smsrcx: $DELTVA failure

Cause: While deleting a context area, VMS system service $DELTVA failed.

Action: Examine the system error message, and refer to VMS documentation.

ORA-07633: smsdbp: illegal protection value

Cause: The buffer debug function was called with an illegal value. This is an internal error.

Action: Contact Oracle Support.

ORA-07634: smsdbp: $CRETVA failure

Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $CRETVA failed.

Action: Contact Oracle Support.

ORA-07635: smsdbp: $SETPRT failure

Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $SETPRT failed.

Action: Contact Oracle Support.

ORA-07636: smsdbp: $MGBLSC failure

Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $MGBLSC failed.

Action: Contact Oracle Support.

ORA-07637: smsdbp: buffer protect option not specified when sga created

Cause: An attempt was made to change the buffer protect mode, when the SGA was not created with buffer protect debug option. This is an internal error.

Action: Contact Oracle Support.

ORA-07638: smsget: SGA pad area not large enough for created SGA

Cause: An attempt was made to map an SGA with software in which the SGA pad area isn't large enough.

Action: Create a smaller SGA, or relink the software with a larger pad.

ORA-07639: smscre: SGA pad area not large enough (number bytes required)

Cause: An attempt was made to create an SGA with software where the SGA pad area isn't large enough.

Action: Create a smaller SGA, or relink the software with a larger pad.

ORA-07640: smsget: SGA not yet valid. initialization in progress

Cause: An attempt was made to map to the SGA while it was being initialized.

Action: Wait until initialization is complete, and try again.

ORA-07641: smscre: unable to use the system pagefile for the SGA

Cause: The system global area (SGA) backing file failed to allocate using the system pagefile, because the system-wide limit on global pages has been exceeded.

Action: Either increase the VMS system parameter GBLPAGFIL, or use a disk file as the SGA backing file.

ORA-07642: smprtset: $CMKRNL failure

Cause: While attempting to set the protection of a region of memory, an error was returned from the $CMKRNL system service.

Action: Examine the system error message, and refer to VMS documentation.

ORA-07643: smsalo: SMSVAR is invalid

Cause: This is an internal error.

Action: Report this error to Oracle Support; provide the init.ora file.

ORA-07645: sszfsl: $CHANGE_CLASS failure

Cause: While attempting to set the label on a file, SEVMS service $CHANGE_CLASS failed.

Action: Examine the system message, and refer to SEVMS system documentation.

ORA-07646: sszfck: $CREATE failure

Cause: While attempting to create a file, VMS system service $CREATE failed.

Action: Examine the system message, and refer to VMS system documentation.

ORA-07647: sszfck: $OPEN failure

Cause: While attempting to reopen a file, VMS system service $OPEN failed.

Action: Examine the system message, and refer to VMS system documentation.

ORA-07650: sigunc: $GETJPIW failure

Cause: While attempting to get the user's terminal device name, user name, user program name, or process name during logon, VMS system service $GETJPIW failed.

Action: Examine the system message, and refer to VMS documentation.

ORA-07655: slsprom:$TRNLOG failure

Cause: While attempting to translate SYS$INPUT during a prompt for a password, VMS system service $TRNLOG failed.

Action: Examine the system message, and refer to VMS documentation.

ORA-07656: slsprom:$GETDVI failure

Cause: While attempting to get device characteristics during a prompt for a password, VMS system service $GETDVI failed.

Action: Examine the system message, and refer to VMS documentation.

ORA-07657: slsprom:$ASSIGN failure

Cause: While prompting for a password, VMS system service $ASSIGN failed.

Action: Examine the system message, and refer to VMS documentation.

ORA-07658: slsprom:$QIOW read failure

Cause: While prompting for a password, VMS system service $QIOW failed.

Action: Examine the system message, and refer to VMS documentation.

ORA-07665: ssrexhd: recursive exception encountered exception

Cause: A VMS exception occurred while executing in the oracle exception handler. The message includes the signal number, first and second signal arguments, and exception PC, PSL and R0. This is an internal error.

Action: Contact Oracle Support.

ORA-07670: $IDTOASC failed translating a secrecy category

Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of a secrecy category.

Action: Define the entry in the rights database which the binary label specified references.

ORA-07671: $IDTOASC failed translating an integrity category

Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of an integrity category.

Action: Define the entry in the rights database which the binary label specified references.

ORA-07672: $PARSE_CLASS failed translating the string into a binary label

Cause: SEVMS system service $PARSE_CLASS failed because the given string did not represent a valid classification.

Action: Examine system error message, and refer to SEVMS documentation.

ORA-07680: sou2os: another call to oracle currently executing

Cause: A call to the oracle shared image entry point occurred from within the shared image. This is an internal error.

Action: Contact Oracle Support.

ORA-07681: sou2os: An error occurred while initializing oracle

Cause: While attempting to set up the dispatch vectors for the shared image, an error occurred. This is an internal error.

Action: Contact Oracle Support.

ORA-07682: sou2os: set kernel dispatch fail err

Cause: During oracle shared image entry, a dispatch to kernel mode failed.

Action: Verify that the shared image is installed with the CMKRNL privilege, then contact Oracle Support.

ORA-07683: sou2os: $SETPRV reset error

Cause: During an attempt to restore user privileges at oracle shared image exit, VMS system service $SETPRV failed. This is an internal error.

Action: Contact Oracle Support.

ORA-07684: sou2os: supervisor stack reset error

Cause: During an attempt to restore the supervisor-mode stack at oracle shared image exit, VMS system service $SETSTK failed. This is an internal error.

Action: Contact Oracle Support.

ORA-07685: sou2os: supervisor stack set error

Cause: During an attempt to set the oracle supervisor-mode stack at oracle shared image entry, VMS system service $SETSTK failed. This is an internal error.

Action: Contact Oracle Support.

ORA-07700: sksarch: interrupt received

Cause: An interrupt was received while archiving the logs.

Action: Retry operation.

ORA-07701: sksatln: internal exception: output buffer too small

Cause: Overflow of buffer for parsing archive control text string. This is an internal error.

Action: Contact Oracle Support.

ORA-07702: unrecognized device type in archive text

Cause: Unrecognized device type in archive text. This is an internal error.

Action: Contact Oracle Support.

ORA-07703: error in archive text: need '/' after device type

Cause: The archive control text in the ARCHIVE command is invalid. The device type (to indicate a file or tape) must be followed by a '/'.

Action: Refer to the SQLDBA Guide for the proper syntax of the text.

ORA-07704: error in archive text: need ':' after device name

Cause: The archive control text in the ARCHIVE command is invalid. The device name must be followed by a ':'.

Action: Refer to the SQLDBA Guide for the proper syntax of the text.

ORA-07705: sksaprs: device name buffer too small

Cause: The buffer supplied for the device name is too small. This is an internal error.

Action: Contact Oracle Support.

ORA-07706: error in archive text: need disk file name

Cause: The archive control text in the ARCHIVE command is invalid. The disk file name is missing.

Action: Refer to the SQLDBA Guide for the proper syntax of the text.

ORA-07707: error in archive text: need tape label name

Cause: The archive control text in the ARCHIVE command is invalid. The tape label name is missing.

Action: Refer to the SQLDBA Guide for the proper syntax of the text.

ORA-07708: sksaprs: tape label name buffer too small

Cause: The buffer supplied for the tape label is too small. This is an internal error.

Action: Contact Oracle Support.

ORA-07709: sksaprs: archiving to a remote host is not allowed

Cause: The user specified a remote disk for archiving via DECnet.

Action: Archive to a disk on the local host.

ORA-07710: sksaprs: file name buffer too small

Cause: The buffer supplied for the file name is too small. This is an internal error.

Action: Contact Oracle Support.

ORA-07713: sksamtd: could not mount archival device (SYS$MOUNT failure)

Cause: VMS system service SYS$MOUNT failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07715: sksadtd: could not dismount archival device (SYS$DISMNT failure)

Cause: VMS system service SYS$DISMNT failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07716: sksachk: invalid device specification for ARCHIVE

Cause: VMS system service SYS$GETDVI failed.

Action: Specify a valid device in ARCHIVE control string.

ORA-07717: sksaalo: error allocating memory

Cause: VMS system service LIB$GET_VM failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07718: sksafre: error freeing memory

Cause: VMS system service LIB$FREE_VM failed.

Action: Examine system error message, and refer to VMS documentation.

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-07740: slemop: incorrect handle size (programming error)

Cause: Structures used for reading error message files do not match. This is an internal error.

Action: Contact Oracle Support.

ORA-07741: slemop: $OPEN failure

Cause: VMS system service $OPEN failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07742: slemop: $CONNECT failure

Cause: VMS system service $CONNECT failed.

Action: Examine system error message, and refer to VMS documentation.

ORA-07743: slemop: incorrect error file attributes

Cause: An error message file has incorrect format.

Action: Unless an error file has been changed, contact Oracle Support.

ORA-07744: slemcl: invalid error message file handle

Cause: Seal in passed in handle does not match correct value. This is an internal error.

Action: Contact Oracle Support.

ORA-07745: slemcl: $CLOSE failure

Cause: VMS system service $CLOSE failed.

Action: Examine system error, and refer to VMS documentation.

ORA-07746: slemrd: invalid error message file handle

Cause: Seal in passed in handle does not match correct value. This is an internal error.

Action: Contact Oracle Support.

ORA-07747: slemrd: $READ failure

Cause: VMS system service $READ failed.

Action: Examine system error, and refer to VMS documentation.

ORA-07750: slemcr: fopen failure

Cause: An attempt to create a message file failed. This is an internal error.

Action: Contact Oracle Support.

ORA-07751: slemcr: malloc failure

Cause: An attempt to allocate a cache for a newly-created message file failed. This is an internal error.

Action: Contact Oracle Support.

ORA-07753: slemcf: fseek before write failure

Cause: An attempt to seek before writing a message file cache element failed. This is an internal error.

Action: Contact Oracle Support.

ORA-07754: slemcf: fwrite failure

Cause: An attempt to write a message file cache element failed. This is an internal error.

Action: Contact Oracle Support.

ORA-07755: slemcf: fseek before read failure

Cause: An attempt to seek before reading a message file cache element failed. This is an internal error.

Action: Contact Oracle Support.

ORA-07756: slemcf: fread failure

Cause: An attempt to read a message file cache element failed. This is an internal error.

Action: Contact Oracle Support.

ORA-07757: slemcc: invalid handle

Cause: The seal in a passed-in handle does not match correct value. This is an internal error.

Action: Contact Oracle Support.

ORA-07758: slemcw: invalid handle

Cause: The seal in a passed-in handle does not match correct value. This is an internal error.

Action: Contact Oracle Support.

ORA-07759: slemtr: invalid destination

Cause: The destination string provided to the function is too short. This is an internal error.

Action: Contact Oracle Support.

ORA-07760: slemtr: $open failure

Cause: the $open service failed. This is an internal error.

Action: Contact Oracle Support.

ORA-07800: slbtpd: invalid number

Cause: An impossible request for binary to decimal conversion was made.

Action: This conversion cannot be performed.

ORA-07801: slbtpd: invalid exponent

Cause: An impossible request for binary to decimal conversion was made.

Action: This conversion cannot be performed.

ORA-07802: slbtpd: overflow while converting to packed decimal

Cause: An impossible request for binary to decimal conversion was made.

Action: This conversion cannot be performed.

ORA-07803: slpdtb: invalid packed decimal nibble

Cause: An impossible request for decimal to binary conversion was made.

Action: This conversion cannot be performed.

ORA-07804: slpdtb: number too large for supplied buffer

Cause: An impossible request for decimal to binary conversion was made.

Action: This conversion cannot be performed.

ORA-07820: sspscn: SYS$CRELNM failure

Cause: An error was returned from the SYS$CRELNM function.

Action: Examine system error, and refer to VMS documentation.

ORA-07821: sspsdn: SYS$DELLNM failure

Cause: An error was returned from the SYS$DELLNM function.

Action: Examine system error, and refer to VMS documentation.

ORA-07822: sspscm: SYS$CREMBX failure

Cause: An error was returned from the SYS$CREMBX function while trying to create the process dump mailbox.

Action: Examine system error, and refer to VMS documentation.

ORA-07823: sspsqr: $QIO failure

Cause: An error was returned from $QIO while trying to queue a read to the process dump mailbox.

Action: Examine system error, and refer to VMS documentation.

ORA-07824: sspain: $SETIMR failure

Cause: An error was returned from SYS$SETIMR while trying to queue a process spin-watch timer.

Action: Examine system error, and refer to VMS documentation.

ORA-07825: sspsck: $QIO failure at AST level

Cause: An error was returned from SYS$QIO while trying to read the process dump mailbox.

Action: Examine system error, and refer to VMS documentation.

ORA-07826: sspscm: SYS$GETDVIW failure

Cause: An error was returned from SYS$GETDVIW while trying to get information about the process dump mailbox.

Action: Examine system error, and refer to VMS documentation.

ORA-07840: sllfop: LIB$GET_VM failure

Cause: An error was returned from LIB$GET_VM while attempting to allocate memory for an I/O vector.

Action: Examine system error, and refer to VMS documentation.

ORA-07841: sllfop: SYS$OPEN failure

Cause: An error was returned from SYS$OPEN while attempting to open the data file for reading.

Action: Examine system error, and refer to VMS documentation.

ORA-07842: sllfcl: SYS$CLOSE failure

Cause: An error was returned from SYS$CLOSE while attempting to close the input data file.

Action: Examine system error, and refer to VMS documentation.

ORA-07843: sllfcl: LIB$FREE_VM failure

Cause: An error was returned from LIB$FREE_VM while attempting to free the memory for the I/O vector.

Action: Examine system error, and refer to VMS documentation.

ORA-07844: sllfop: LIB$GET_VM failure

Cause: An error was returned from LIB$GET_VM while attempting to allocate memory for data and index buffers.

Action: Examine system error, and refer to VMS documentation.

ORA-07845: sllfcl: LIB$FREE_VM failure

Cause: An error was returned from LIB$FREE_VM while attempting to free memory used by data and index buffers.

Action: Examine system error, and refer to VMS documentation.

ORA-07846: sllfop: number byte record too big for number byte user buffer

Cause: The longest record in the file will not fit into the largest data buffer that can be allocated.

Action: Modify the RMS file to have smaller records.

ORA-07847: sllfop: $CONNECT failure

Cause: An error was returned by SYS$CONNECT while attempting to open the data file.

Action: Examine system error, and refer to VMS documentation.

ORA-07848: sllfrb: $GET failure

Cause: An error was returned by SYS$GET while attempting to read the data file.

Action: Examine system error, and refer to VMS documentation.

ORA-07849: sllfsk: $GET failure

Cause: An error was returned by SYS$GET while attempting to skip records in the input file.

Action: Examine system error, and refer to VMS documentation.

ORA-07850: sllfop: bad option

Cause: A bad option to loader Fixed= is one legal option.

Action: Examine documentation.

ORA-07860: osnsoi: error setting up interrupt handler

Cause: An error occurred while setting up the control interrupt handler. This is an internal error.

Action: Contact Oracle Support.

ORA-07880: sdopnf: internal error

Cause: A list of all files open by this process failed to be obtained. This is an internal error.

Action: Contact Oracle Support.

08000-08174: Data Accessing Messages

This section lists messages generated when Oracle is accessing data or database objects.

ORA-08000: maximum number of session sequence lists exceeded

Cause: This is an internal error message not normally issued.

Action: Contact customer support.

ORA-08001: maximum number of sequences per session exceeded

Cause: An operation requested a resource that was unavailable. The maximum number of user sequences per session is specified by the initialization parameter DC_SEQUENCES. When this maximum is reached, no more requests are processed.

Action: Try the operation again in a few minutes. If this error occurs often, shut down Oracle, increase the DC_SEQUENCES parameter in the initialization parameter file, and restart Oracle.

ORA-08002: name.CURRVAL is not yet defined in this session

Cause: Sequence CURRVAL was selected before sequence NEXTVAL was referenced.

Action: Select NEXTVAL from the sequence before selecting CURRVAL.

ORA-08003: sequence name.NEXTVAL exceeds internal limits

Cause: The sequence was created with unsafe values for some of the parameters. The calculation of NEXTVAL cannot be made because it exceeds the legal representation size.

Action: Alter or recreate the sequence number with legal limits.

ORA-08004: name.NEXTVAL str [MIN][MAX]VALUE and cannot be instantiated

Cause: The requested value of NEXTVAL is greater than MAXVALUE or less than MINVALUE.

Action: Alter the sequence so that a new value can be requested and try again.

ORA-08005: specified row does not exist

Cause: A row with the given ROWID does not exist in any of the specified tables.

Action: Check the query for a misspelled ROWID or table name and try again.

ORA-08006: specified row no longer exists

Cause: The row has been deleted by another user since the operation began.

Action: No action required.

ORA-08008: another instance is mounted with USE_ROW_ENQUEUES = num

Cause: The shared instance being started does not have the same value for the USE_ROW_ENQUEUES initialization parameter as already-running instances.

Action: Make sure all instances' initialization parameter files specify the same value for the USE_ROW_ENQUEUES parameter and try again.

ORA-08100: index is not valid - see trace file for diagnostics

Cause: There is an error in the index validated by VALIDATE INDEX.

Action: Check the relevant trace file. If the problem is not resolvable, contact customer support.

ORA-08101: index key does not exist root dba num, dba num num

Cause: The system detected a possible inconsistency in an index. This is an internal error message that is not normally issued.

Action: Send the trace file to customer support, along with a description of the circumstances that produced the error. Customer support will need the numbers given in the message.

ORA-08102: index key not found, obj# num, dba num num

Cause: The system detected a possible inconsistency in an index. This is an internal error message that is not normally issued.

Action: Send the trace file to customer support, along with a description of the circumstances that produced the error. Customer support will need the numbers given in the message.

ORA-08103: object no longer exists

Cause: The object has been deleted by another user since the operation began.

Action: Remove references to the object.

08175-08190: Discrete Transaction Messages

ORA-08175: discrete transaction restriction violated name

Cause: An attempt was made to perform an action that is not currently supported in a discrete transaction.

Action: Rollback the transaction and retry it as a normal transaction.

ORA-08176: cannot continue consistent read for the table/index - no undo records

Cause: Oracle encountered an operation that does not generate undo records. For example, the operation might have been an attempt to create an index by performing a direct load or executing a discrete mode transaction.

Action: Retry the operation with a different snapshot time. If using an index, retry the operation without using the index.

ORA-08177: cannot serialize access for this transaction

Cause: Oracle encountered data changed by an operation that occurred after the start of this serializable transaction.

Action: In read/write transactions, retry the intended operation or transaction.

ORA-08178: illegal SERIALIZABLE clause specified for user INTERNAL

Cause: An attempt was made to specify the SERIALIZABLE mode for user INTERNAL. Serializable mode is not supported for user INTERNAL.

Action: Reconnect as another user and retry the SET TRANSACTION command.

08200-08399: nCUBE Messages

ORA-08200: scggc: failed to open lock

Cause: The lock manager failed to open a lock.

Action: Verify that enough memory is available, and retry the operation.

ORA-08201: scggc: failed to convert lock

Cause: The lock manager failed to convert a lock.

Action: Retry the operation.

ORA-08202: scgcc: failed to close lock

Cause: The lock manager encountered an error closing a lock.

Action: Examine the lock manager status returned for additional information.

ORA-08203: scgcan: failed to cancel a pending convert request

Cause: The lock manager encountered an error cancelling a convert request.

Action: Examine the lock manager status returned for additional information.

ORA-08204: scgcm: unexpected lock manager return code

Cause: The lock manager returned an unexpected value.

Action: Examine the lock manager status returned for additional information.

ORA-08205: ora_addr: ORACLE_SID not set in environment

Cause: The environment variable ORACLE_SID is not set.

Action: Set the ORACLE_SID environment variable.

ORA-08206: ora_addr: cannot translate address file name

Cause: Failure to translate $ORACLE_HOME/dbs/sgadefsid.dbf.

Action: Ensure that $ORACLE_HOME and ORACLE_SID are properly set.

ORA-08207: ora_addr: cannot open address file

Cause: The address file failed to open.

Action: Verify that ORACLE is up. Verify that the file $(ORACLE_HOME)/dbs/sgadefsid.dbf exists and has correct permissions.

ORA-08208: ora_addr: cannot read from address file

Cause: The address file could not be read.

Action: Verify that the file $(ORACLE_HOME)/dbs/sgadefsid.dbf exists and contains a single line of text.

ORA-08209: scngrs: SCN not yet initialized

Cause: The System Commit Number has not yet been initialized.

Action: Contact Oracle Support

ORA-08210: requested I/O error

Cause: The oracle executable requested that an I/O error be returned for this operation.

Action: Contact Oracle Support.

ORA-08230: smscre: failed to allocate SGA

Cause: The n_core system call failed. This is possibly due to insufficient memory.

Action: Specify a smaller number of buffers. Verify init.ora parameters.

ORA-08231: smscre: unable to attach to SGA

Cause: The process cannot attach to the SGA. This happens if either the listener cannot attach, or if the process cannot communicate with the listener.

Action: Verify that the instance is up and running. Contact Oracle Support.

ORA-08232: smsdes: cannot detach from SGA

Cause: Probably, the listener process has died.

Action: Contact Oracle Support.

ORA-08233: smsdes: cannot unmap SGA

Cause: The n_core system call failed while detaching from the SGA.

Action: Note nCX error. Contact Oracle Support.

ORA-08234: smsget: cannot get instance listener address

Cause: The instance listener address failed to be read from the sgadef file.

Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are set correctly. Additional information gives error return from ora_addr.

ORA-08235: smsget: listener not on this node

Cause: A process is wishing to attach to the SGA is on a different node from its instance's listener.

Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are set correctly. Contact Oracle Support.

ORA-08236: smsget: cannot share subcube with listener

Cause: The n_share call failed. This is possibly because the listener has died.

Action: Verify that the listener is running, and contact Oracle Support.

ORA-08237: smsget: SGA region not yet created

Cause: Attempting to attach to an SGA which has not yet been created.

Action: Verify that the instance is running. Contact Oracle Support.

ORA-08238: smsfre: cannot detach from SGA

Cause: The n_core system call failed while detaching from the SGA.

Action: Examine nCX error, and contact Oracle Support.

ORA-08240: snlmatt: parallel server name too long

Cause: The file name of the lock manager address file is too long.

Action: Use a shorter parallel server name.

ORA-08241: snlmatt: cannot attach to lock manager

Cause: Failure to attach to lock manager. This is possibly because it is not running.

Action: Additional information is lock manager return code. Verify that lock manager is running.

ORA-08242: snlmdet: cannot detach from lock manager

Cause: An error was encountered detaching from the lock manager.

Action: Additional information is lock manager return code. Contact Oracle Support.

ORA-08260: ora_addr: cannot open nameserver

Cause: A process failed to connect to the nameserver.

Action: Verify that the nameserver is up and running. Additional information gives nameserver's returned status.

ORA-08261: ora_addr: cannot find name in nameserver

Cause: The listener nameserver entry for an instance failed to be found.

Action: Verify that the nameserver is up and running. Additional information gives nameserver's returned status.

ORA-08262: ora_addr: ORACLE_PSRV undefined

Cause: The parallel server name ORACLE_PSRV was undefined.

Action: Set the environment variable ORACLE_PSRV, and try again.

ORA-08263: ora_addr: cannot free listener address

Cause: The listener nameserver entry failed to free.

Action: Additional information gives nameserver's returned status. Contact Oracle Support.

ORA-08264: ora_addr: cannot close nameserver

Cause: The connection to the nameserver failed to close.

Action: Additional information gives nameserver's returned status. Contact Oracle Support.

ORA-08265: create_ora_addr: cannot open nameserver

Cause: A process failed to connect to the nameserver.

Action: Verify that the nameserver is up and running. Additional information gives nameserver's returned status.

ORA-08266: create_ora_addr: cannot register name in nameserver

Cause: The listener's addressing information failed to register.

Action: Verify that the nameserver is up and running. Additional information gives nameserver's returned status.

ORA-08267: destroy_ora_addr: cannot close nameserver

Cause: The connection to the nameserver failed to close.

Action: Additional information gives nameserver's returned status. Contact Oracle Support.

ORA-08268: create_ora_addr: cannot close nameserver

Cause: The connection to the nameserver failed to close.

Action: Additional information gives nameserver's returned status. Contact Oracle Support.

ORA-08269: destroy_ora_addr: cannot destroy name

Cause: The listener's addressing information failed to be removed.

Action: Additional information gives nameserver's returned status. Contact Oracle Support.

ORA-08270: sksachk: Illegal archival control string

Cause: Archive files failed to be created with the given archival control string.

Action: Verify that the volume exists.

ORA-08271: sksabln: buffer size not large enough for archive control string

Cause: The given archival control string expands into too many characters.

Action: Reduce archive control string length.

ORA-08274: out of memory for environment variable

Cause: There is insufficient memory to return the requested value.

Action: Reduce memory usage and retry.

ORA-08275: environment variable unset

Cause: The requested environment variable is not set.

Action: Ensure that the variable name requested is correct.

ORA-08276: no room in nameserver for pid

Cause: There is no room to record the pid for a background process.

Action: Shutdown abort, and restart the database.

ORA-08277: cannot set environment variable

Cause: There is insufficient memory to expand the environment.

Action: Reduce memory usage and retry.

ORA-08278: cannot get CPU statistics

Cause: Failure to retrieve CPU times, because n_stat failed.

Action: Contact Oracle Support.

ORA-08308: sllfop: cannot open file

Cause: Oracle failed to open a file.

Action: Examine the UNIX errno returned for additional information.

ORA-08309: sllfop: cannot fstat file

Cause: Oracle failed to obtain information about an open file.

Action: Examine the UNIX errno returned for additional information.

ORA-08310: sllfop: bad value for recsize

Cause: An illegal value for the record size was specified.

Action: Specify a value for the recsize option that is greater than 0.

ORA-08311: sllfop: bad value for maxrecsize

Cause: An illegal value for the maximum record size was specified.

Action: Specify a value for the maxrecsize option that is greater than 0.

ORA-08312: sllfop: unrecognized processing option

Cause: An unrecognized processing option was specified.

Action: Examine the Oracle for nCUBE 2 User's Guide for valid options.

ORA-08313: sllfop: could not allocate buffers

Cause: Memory for the load buffers failed to allocate.

Action: Reduce the maximum record size. Eliminate any unnecessary processes on the current node before running SQL*Loader again.

ORA-08314: sllfcf: error closing file

Cause: An error occurred trying to close a file.

Action: Examine the UNIX errno returned for additional information.

ORA-08315: sllfrb: error reading file

Cause: An error occurred trying to read from a file.

Action: Examine the UNIX errno returned for additional information.

ORA-08316: sllfsk: error seeking in file

Cause: The lseek system call returned an error.

Action: Examine the UNIX errno returned for additional information.

ORA-08317: sllfsk: error seeking in file

Cause: The lseek system call returned an error.

Action: Examine the UNIX errno returned for additional information.

ORA-08318: sllfsk: error reading file

Cause: An error occurred trying to read from a file.

Action: Examine the UNIX errno returned for additional information.

ORA-08319: sllfsk: error reading file

Cause: An error occurred trying to read from a file.

Action: Examine the UNIX errno returned for additional information.

ORA-08320: scnget: call to scnget before scnset or scnfnd

Cause: This is an internal error.

Action: Contact Oracle Support.

ORA-08321: scnmin: NOT IMPLEMENTED YET

Cause: This is an internal error.

Action: Contact Oracle Support.

ORA-08322: scnmin: open/convert of bias lock failed

Cause: A call to the lkmgr failed to open and convert the bias lock.

Action: Verify that the lkmgr is up.

ORA-08323: scnmin: close of bias lock failed

Cause: A call to the lkmgr failed to close the bias lock.

Action: Verify that the lkmgr is up.

ORA-08330: printing not supported

Cause: An attempt was made to automatically spool a file to the printer.

Action: None.

ORA-08331: wait operation timed out

Cause: The oracle executable timed out waiting for an event.

Action: Contact Oracle Support.

ORA-08332: rollback segment number specified not available

Cause: (same as 1545)

Action: (same as 1545). Also, verify that enough rollback segments have been created for the number of instances you are trying to start.

ORA-08340: this command not allowed on nCUBE, only one thread is ever used

Cause: An illegal command was executed for the nCUBE platform.

Action: There is no need to issue this command.

ORA-08341: on nCUBE, this command can only be executed from instance 1

Cause: A command that can only be issued on instance 1 was issued elsewhere.

Action: Log on to instance 1 and repeat the command.

ORA-08342: sropen: failed to open a redo server connection

Cause: An error occurred trying to connect to the redo server.

Action: The OS specific error message should tell you what to do.

ORA-08343: srclose: failed to close a redo server connection

Cause: An error occurred trying to close the redo server connection.

Action: The OS specific error message should tell you what to do.

ORA-08344: srapp: failed to send redo data to the redo server

Cause: An error occurred trying to send redo to the redo server.

Action: The OS specific error message should tell you what to do.

ORA-08362: scgcm: out of memory in lock manager

Cause: The lock manager ran out of memory.

Action: Reduce the number of locks specified in the GC_FILES_TO_LOCKS and GC_ROLLBACK_LOCKS init.ora parameters, or increase the number of lock manager processes.

08401-08499: PL/SQL Utility Packages for Procedural Gateway Messages

ORA-08401: invalid compiler name: name

Cause: An invalid compiler name was passed to a UTL_PG conversion routine.

Action: Correct the compiler name parameter in the PL/SQL code that called the conversion routine.

ORA-08412: error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message

Cause: The WMSGBSIZ is the maximum size for warning message block, it is recommended to be 1024 bytes to 8 kbytes.

Action: Defined WMSGBLK of size between 1k to 8k bytes and update the WMSGBSIZ to the size of WMSGBLK.

ORA-08413: invalid compiler type in FORMAT parameter at name

Cause: An invalid compiler type was defined in the format control block. The format control block is invalid.

Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT and that it was not accidentally overwritten or modified by the PL/SQL procedure.

ORA-08414: error encountered in name

Cause: The function <routine> returned an error. Where <routine> may be:
RAW_TO_NUMBER
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-08429: raw data has invalid digit in display type data

Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid data. The picture mask parameter specified a digit, but the corresponding input from the raw data did not contain a valid digit.

Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item.

ORA-08430: raw data missing leading sign

Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign.

Action: Correct the input raw data or the mask options so that they match.

ORA-08431: raw data missing zero as defined in picture

Cause: The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained a zero, but the corresponding input from the raw data was not a zero.

Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item.

ORA-08432: raw data has invalid floating point data

Cause: The input raw data passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid floating point data.

Action: Correct the input raw data.

ORA-08433: invalid picture type in convert raw to number

Cause: The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained non-numeric characters, but the conversion was to a numeric data type.

Action: Correct the picture mask parameter.

ORA-08434: raw data has invalid trailing sign

Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no trailing sign, but the mask options parameter specified a trailing sign.

Action: Correct the input raw data or the mask options so that they match.

ORA-08435: PICTURE MASK missing the leading sign when SIGN IS LEADING specified

Cause: The input MASK passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign.

Action: Correct the input raw data or the mask options so that they match.

ORA-08436: raw data has invalid sign digit

Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had an invalid sign digit in the position where the picture mask specified a sign.

Action: Correct the input raw data or the picture mask so that they match.

ORA-08437: invalid picture type in picture mask

Cause: The picture mask parameter passed to a UTL_PG NUMBER_TO_RAW conversion routine contained non-numeric characters, but the conversion was to a numeric data type.

Action: Correct the picture mask parameter.

ORA-08440: raw buffer is too short to hold converted data

Cause: The output raw buffer passed to a UTL_PG NUMBER_TO_RAW conversion routine was not large enough to contain the results of the conversion based on the picture mask.

Action: Increase the raw buffer size to the size necessary to hold the entire result of the conversion.

ORA-08441: closed parenthesis missing in picture mask

Cause: A closed parenthesis was missing from the picture mask passed to a UTL_PG conversion routine.

Action: Correct the picture mask.

ORA-08443: syntax error in BLANK WHEN ZERO clause in mask options

Cause: A syntax error was found in the BLANK WHEN ZERO clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: BLANK ZERO, BLANK ZEROS, BLANK ZEROES, BLANK WHEN ZERO, BLANK WHEN ZEROS, and BLANK WHEN ZEROES.

Action: Correct the mask options parameter.

ORA-08444: syntax error in JUSTIFIED clause in mask options

Cause: A syntax error was found in the JUSTIFIED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: JUST, JUST RIGHT, JUSTIFIED, and JUSTIFIED RIGHT.

Action: Correct the mask options parameter.

ORA-08445: syntax error in SIGN clause in mask options

Cause: A syntax error was found in the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SIGN, LEADING SIGN, LEADING SEPARATE SIGN, LEADING SEPARATE CHARACTER SIGN, TRAILING SIGN, TRAILING SEPARATE SIGN, TRAILING SEPARATE CHARACTER SIGN IS LEADING, SIGN IS LEADING, SEPARATE SIGN IS LEADING, SEPARATE CHARACTER SIGN IS TRAILING, SIGN IS TRAILING, SEPARATE SIGN IS TRAILING, and SEPARATE CHARACTER.

Action: Correct the mask options parameter.

ORA-08446: syntax error in SYNCHRONIZED clause in mask options

Cause: A syntax error was found in the SYNCHRONIZED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SYNC, SYNC LEFT, SYNC RIGHT, SYNCHRONIZED, SYNCHRONIZED LEFT, and SYNCHRONIZED RIGHT.

Action: Correct the mask options parameter.

ORA-08447: syntax error in USAGE clause in mask options

Cause: A syntax error was found in the USAGE clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: USAGE, DISPLAY USAGE, COMP USAGE, COMP-3 USAGE, COMP-4 USAGE, COMPUTATIONAL USAGE, COMPUTATIONAL-3 USAGE, COMPUTATIONAL-4 USAGE IS, DISPLAY USAGE IS, COMP USAGE IS, COMP-3 USAGE IS, COMP-4 USAGE IS, COMPUTATIONAL USAGE IS, COMPUTATIONAL-3 USAGE IS, and COMPUTATIONAL-4.

Action: Correct the mask options parameter.

ORA-08448: syntax error in DECIMAL-POINT environment clause

Cause: A syntax error was found in the DECIMAL-POINT environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: DECIMAL-POINT IS COMMA.

Action: Correct the environment clause parameter.

ORA-08449: invalid numeric symbol found in picture mask

Cause: An invalid numeric symbol was found in the picture mask parameter passed to a UTL_PG conversion routine.

Action: Correct the picture mask parameter.

ORA-08450: invalid specification of CR in picture mask

Cause: The CR suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The CR suffix can only appear at the end of a picture mask.

Action: Correct the picture mask parameter.

ORA-08451: invalid specification of DB in picture mask

Cause: The DB suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The DB suffix can only appear at the end of a picture mask.

Action: Correct the picture mask parameter.

ORA-08452: specification of E in picture mask is unsupported

Cause: The floating point exponent symbol "E" was specified in the picture mask parameter passed to a UTL_PG conversion routine. The floating point data type is currently not supported by the UTL_PG conversion routines.

Action: Correct the picture mask parameter, and the data, if necessary.

ORA-08453: more than one V symbol specified in picture mask

Cause: The picture mask passed to a UTL_PG conversion routine contained more than one decimal point indicator "V". Only one decimal point indicator is allowed in the picture mask.

Action: Correct the picture mask parameter.

ORA-08454: more than one S symbol specified in picture mask

Cause: The picture mask passed to a UTL_PG conversion routine contained more than one operational sign indicator "S". Only one operational sign indicator is allowed in the picture mask.

Action: Correct the picture mask parameter.

ORA-08455: syntax error in CURRENCY SIGN environment clause

Cause: A syntax error was found in the CURRENCY SIGN environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: CURRENCY SIGN IS x, where x is a valid currency sign.

Action: Correct the environment clause parameter.

ORA-08456: no sign in picture mask but SIGN clause in mask options

Cause: The picture mask parameter passed to a UTL_PG conversion routine contained no sign symbol, "S", "+", or "-", but the mask options parameter contained a SIGN clause. A sign symbol is required in the picture mask parameter when the mask options parameter contains a SIGN clause.

Action: Correct the picture mask parameter or the mask options parameter.

ORA-08457: syntax error in SEPARATE CHARACTER option of SIGN clause

Cause: A syntax error was found in the SEPARATE CHARACTER option of the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SEPARATE and SEPARATE CHARACTER.

Action: Correct the mask options parameter.

ORA-08458: invalid format parameter

Cause: The format parameter passed to a UTL_PG conversion routine was invalid. The format parameter should have been built by a prior call to either MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT.

Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT and that it was not accidentally overwritten or modified by the PL/SQL procedure.

ORA-08459: invalid format parameter length

Cause: The format parameter passed to a UTL_PG conversion routine was not the correct length. Format parameters must be 2048 bytes in length.

Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT and that it was not accidentally overwritten or modified by the PL/SQL procedure.

ORA-08460: invalid environment clause in environment parameter

Cause: The environment parameter passed to a UTL_PG conversion routine contained an unsupported or invalid environment clause. Only the CURRENCY SIGN and the DECIMAL-POINT IS COMMA environment clauses are supported.

Action: Correct the environment parameter.

ORA-08462: raw buffer contains invalid decimal data

Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contains invalid decimal data.

Action: Correct the input data.

ORA-08463: overflow converting decimal number to Oracle number

Cause: The output variable passed to a UTL_PG RAW_TO_NUMBER was not large enough to hold the Oracle number resulting from the input decimal number.

Action: Be sure that the input decimal number is valid, and be sure that the output variable is large enough to hold the Oracle number value.

ORA-08464: input raw decimal data contains more than 42 digits

Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained more than 42 digits. This exceeds the maximum size of an Oracle number.

Action: Correct the raw input buffer.

ORA-08465: input mask contains more than 32 characters

Cause: The input mask passed to UTL_PG numeric conversion routine contained more the 32 characters.

Action: Correct the mask input buffer.

ORA-08466: raw buffer length num is too short for name

Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine was less than num bytes long, but the picture mask parameter specified that num bytes of input data were to be converted.

Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item.

ORA-08467: error converting Oracle number to num

Cause: An error occurred when converting an Oracle number to a COBOL <type> of:
DISPLAY
COMP-3
or character variable.

The Oracle number was not in the correct format.

Action: Correct the call to the conversion routine. The input must be a valid Oracle number variable.

ORA-08468: mask option name is not supported

Cause: The mask option <clause> was passed to a UTL_PG conversion routine, but is not supported by UTL_PG. The <clause> can be:
USAGE IS POINTER
USAGE IS INDEX
USAGE IS COMP-1
USAGE IS COMP-2
POINTER

Action: Remove the <clause> from the mask options parameter in the PL/SQL call to UTL_PG.

ORA-08498: Warning: picture mask name overrides picture mask option USAGE IS name to USAGE IS DISPLAY

Cause: Picture mask option is overridden by Picture mask.

Action: No action required. This is an informational message.

ORA-08499: Warning: picture mask options name ignored by UTL_PG

Cause: Picture mask options such as OCCUR, SYNC and others are not processed by the UTL_PG numeric conversion routines.

Action: This is an informational message only. The message may be eliminated by removing the unnecessary picture mask options from the parameter list passed to the UTL_PG routine.

08500-08599: Protocol Procedural Gateway for MQ Series Messages

The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.

08600-09099: SQL*Connect Messages

The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.

09100-09199: Oracle Gateways Messages

The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.

09200-09499: DOS, OS/2, and Novell Messages

ORA-09200: sfccf: error creating file

Cause: Possibly, there is a shortage of disk space.

Action: Examine the OSD error accompanying this message.

ORA-09201: sfcopy: error copying file

Cause: Block sizes may not match.

Action: Examine the OSD error accompanying this message.

ORA-09202: sfifi: error identifying file

Cause: DB_BLOCK_SIZE specified in init.ora could be incorrect.

Action: Examine the OSD error accompanying this message.

ORA-09203: sfofi: error opening file

Cause: File attributes may have changed.

Action: Examine the OSD error accompanying this message.

ORA-09204: sfotf: error opening temporary file

Cause: Incorrect path may have been specified for the file.

Action: Examine the OSD error accompanying this message.

ORA-09205: sfqio: error reading or writing to disk

Cause: File may have been truncated or corrupted.

Action: Examine the OSD error accompanying this message.

ORA-09206: sfrfb: error reading from file

Cause: File may have been truncated or corrupted.

Action: Examine the OSD error accompanying this message.

ORA-09207: sfsrd: error reading from file

Cause: File may have been truncated or corrupted.

Action: Examine the OSD error accompanying this message.

ORA-09208: sftcls: error closing file

Cause: File may have been corrupted.

Action: Examine the OSD error accompanying this message.

ORA-09209: sftget: error reading from file

Cause: File may have been truncated or corrupted.

Action: Examine the OSD error accompanying this message.

ORA-09210: sftopn: error opening file

Cause: Incorrect path may have been specified for the file.

Action: Examine the OSD error accompanying this message.

ORA-09211: sfwfb: error writing to file

Cause: File may have been truncated or corrupted.

Action: Examine the OSD error accompanying this message.

ORA-09212: sfwfbmt: error writing to file

Cause: File may have been truncated or corrupted.

Action: Examine the OSD error accompanying this message.

ORA-09213: slgfn: error fabricating file name

Cause: Filename may be too long.

Action: Examine the OSD error accompanying this message.

ORA-09214: sfdone: I/O error detected

Cause: File may have been truncated or corrupted.

Action: Examine the OSD error accompanying this message.

ORA-09215: sfqio: error detected in I/O completion routine

Cause: File may have been truncated or corrupted.

Action: Examine the OSD error accompanying this message.

ORA-09216: sdnfy: bad value 'value' for parameter name

Cause: The directory specified as the value for the stated parameter failed to be used.

Action: Verify that the directory specified is a valid directory/file specification.

ORA-09217: sfsfs: failed to resize file

Cause: Possibly, there is a shortage of disk space.

Action: Examine the OSD error accompanying this message.

ORA-09218: sfrfs: failed to refresh file size

Cause: File may be corrupted or truncated.

Action: Examine the OSD error accompanying this message. Memory allocation errors: 9240 - 9259.

ORA-09240: smpalo: error allocating PGA memory

Cause: Possibly, there is a shortage of memory.

Action: Examine the OSD error accompanying this message.

ORA-09241: smsalo: error allocating SGA memory

Cause: Possibly, there is a shortage of memory.

Action: Examine the OSD error accompanying this message.

ORA-09242: smscre: error creating SGA

Action: Examine the OSD error accompanying this message.

ORA-09243: smsget: error attaching to SGA

Cause: SGA may not have been created (database not started).

Action: Examine the OSD error accompanying this message.

ORA-09244: smprset: error setting memory protections

Action: Examine the OSD error accompanying this message.

ORA-09245: smcstk: error switching stacks

Action: Examine the OSD error accompanying this message.

ORA-09246: sfsmap: unable to map SGA

Action: Examine the OSD error accompanying this message.

ORA-09247: smsdes: error destroying the SGA

Action: Examine the OSD error accompanying this message Process control errors: 9260 - 9269.

ORA-09260: sigpidu: error obtaining process ID

Cause: Possibly, there is a shortage of resources.

Action: Examine the OSD error accompanying this message.

ORA-09261: spdcr: error creating detached (background) process

Cause: Possibly, there is a shortage of resources.

Action: Examine the OSD error accompanying this message.

ORA-09262: spdde: error terminating detached (background) process

Cause: Possibly, there is a shortage of resources.

Action: Examine the OSD error accompanying this message.

ORA-09263: spini: error initializing process

Cause: Possibly, there is a shortage of memory.

Action: Examine the OSD error accompanying this message.

ORA-09264: sptpa: error flagging process

Cause: Possibly, there is a shortage of resources.

Action: Examine the OSD error accompanying this message.

ORA-09265: spwat: error temporarily suspending process

Cause: Possibly, there is a shortage of resources.

Action: Examine the OSD error accompanying this message.

ORA-09266: spawn: error starting an oracle process

Cause: Possibly, there is a shortage of memory.

Action: Examine the OSD error accompanying this message Security errors: 9270 - 9279.

ORA-09270: szalloc: error allocating memory for security

Cause: Possibly, there is a shortage of memory.

Action: Examine the OSD error accompanying this message.

ORA-09271: szlon: error verifying user name

Cause: Username may be too long.

Action: Examine the OSD error accompanying this message.

ORA-09272: remote os logon is not allowed

Cause: Remote OS login attempted when not allowed.

Action: Examine the OSD error accompanying this message.

ORA-09273: szrfc: error verifying role name

Cause: An OS error was returned when verifying the role name.

Action: Examine the OSD error accompanying this message.

ORA-09274: szrfc: insufficient role name buffer space

Cause: An OS role name was too long.

Action: Examine the OSD error accompanying this message Direct loader errors: 9280 - 9289.

ORA-09280: sllfcf: error closing file

Cause: File may be corrupted.

Action: Examine the OSD error accompanying this message.

ORA-09281: sllfop: error opening file

Cause: Possibly, incorrect path specified to the file.

Action: Examine the OSD error accompanying this message.

ORA-09282: sllfrb: error reading records

Cause: File could be corrupted.

Action: Examine the OSD error accompanying this message.

ORA-09283: sllfsk: error skipping records

Cause: File could be corrupted.

Action: Examine the OSD error accompanying this message. Archiving errors: 9290 - 9299.

ORA-09290: sksaalo: error allocating memory for archival

Cause: Possibly, there is a shortage of memory.

Action: Examine the OSD error accompanying this message.

ORA-09291: sksachk: invalid device specified for archive destination

Cause: Failure to access directory.

Action: Specify a valid device in ARCHIVE control string.

ORA-09292: sksabln: unable to build archive file name

Cause: Bad directory or format specified.

Action: Specify a valid directory in LOG_ARCHIVE_FORMAT and a valid format string in LOG_ARCHIVE_FORMAT in init.ora.

ORA-09293: sksasmo: unable to send message to console

Cause: An error was returned while attempting to send a message to the console operator.

Action: Examine the OSD error accompanying this message. Windows specific errors: 9300 - 9309.

ORA-09300: osncon: unable to connect, DPMI not available

Cause: Failure to detect the presence of DPMI.

Action: Restart Windows and retry.

ORA-09301: osncon: local kernel only supported in standard mode

Cause: An attempt was made to connect to S: while in enhanced mode.

Action: Restart Windows in standard mode. Miscellaneous errors: 9310 - 9339.

ORA-09310: sclgt: error freeing latch

Cause: This is an internal error.

Action: Examine the OSD error accompanying this message.

ORA-09311: slsleep: error temporarily suspending process

Cause: Possibly, there is a shortage of resources.

Action: Examine the OSD error accompanying this message.

ORA-09312: slspool: error spooling file to printer

Cause: Possibly, there is a shortage of resources.

Action: Examine the OSD error accompanying this message.

ORA-09313: slsprom: error prompting user

Cause: Possibly, there is a shortage of resources.

Action: Examine the OSD error accompanying this message.

ORA-09314: sltln: error translating logical name

Cause: Internal buffer may have overflowed.

Action: Examine the OSD error accompanying this message.

ORA-09315: sql2tt: two-task error translating ORACLE_EXECUTABLE

Cause: This is an internal error.

Action: Examine the OSD error accompanying this message.

ORA-09316: szrpc: unable to verify password for role

Cause: OS roles may not be supported for this platform.

Action: Examine the OSD error accompanying this message.

ORA-09317: szprv: insufficient privileges

Cause: The password specified is invalid.

Action: Examine the OSD error accompanying this message.

ORA-09318: slkhst: unable to host out to operating system

Cause: There might not be enough memory for the command, or hosting out may not be supported on this platform.

Action: Examine the OSD error accompanying this message.

ORA-09319: slgtd: unable to obtain the current date and time

Cause: The system time might be set incorrectly.

Action: Examine the OSD error accompanying this message.

ORA-09320: szrfc: unable to obtain the list of valid OS roles

Cause: OS roles may not be supported on this platform.

Action: Examine the OSD error accompanying this message.

ORA-09321: slzdtb: unable to convert zoned decimal to binary

Cause: This is an internal error.

Action: Examine the OSD error accompanying this message.

ORA-09322: slpdtb: unable to convert packed decimal to binary

Cause: This is an internal error.

Action: Examine the OSD error accompanying this message.

ORA-09330: Session terminated internally by oracle or by an Oracle DBA

Cause: A client workstation that is abnormally disconnected would cause oracle to terminate that session after about a minute. This message also appears in the trace file if a shutdown abort is performed.

ORA-09331: scgcan: unable to process lk_sync_cancel return code

Cause: An invalid lock status was returned by the lock manager, and the locks may no longer be consistent.

ORA-09332: scgcc: unable to process lk_close return code

Cause: An invalid lock status was returned by the lock manager, and the locks may no longer be consistent.

ORA-09333: scggc: unable to process lk_open_convert return code

Cause: An invalid lock status was returned by the lock manager, and the locks may no longer be consistent.

ORA-09334: scggc: unable to process lk_convert return code

Cause: An invalid lock status was returned by the lock manager, and the locks may no longer be consistent.

ORA-09335: scgcm: unable to process return code in completion procedure

Cause: An invalid lock status was returned by the lock manager, and the locks may no longer be consistent.

ORA-09340: Specified ORACLE_SID is either invalid or too long

Cause: ORACLE_SID must be at the most 4 alphanumeric characters.

ORA-09341: scumnt: unable to mount database

Cause: Another instance is currently mounting the database.

ORA-09342: detached process terminated by oracle during shutdown abort

Cause: The user performed a shutdown abort. Windows 32-bit two-task driver: 9350 - 9359.

ORA-09350: Windows 32-bit Two-Task driver unable to allocate context area

Cause: Examine the OSD error accompanying this message.

ORA-09351: Windows 32-bit two-task driver unable to allocate shared memory

Cause: Examine the OSD error accompanying this message.

ORA-09352: Windows 32-bit two-task driver unable to spawn new oracle task

Cause: Examine the OSD error accompanying this message.

ORA-09353: Windows 32-bit two-task driver unable to open event semaphore

Cause: Examine the OSD error accompanying this message.

ORA-09354: Windows 32-bit two-task driver: oracle task unexpectedly died

Cause: Examine the OSD error accompanying this message. Windows 3.1 two-task driver: 9360 - 9379.

ORA-09360: Windows 3.1 two-task driver unable to allocate context area

Cause: Examine the OSD error accompanying this message.

ORA-09361: Windows 3.1 two-task driver unable to lock context area

Cause: Examine the OSD error accompanying this message.

ORA-09362: Windows 3.1 two-task driver unable to deallocate context area

Cause: Examine the OSD error accompanying this message.

ORA-09363: Windows 3.1 two-task driver invalid context area

Cause: Examine the OSD error accompanying this message.

ORA-09364: Windows 3.1 two-task driver unable to create hidden window

Cause: Examine the OSD error accompanying this message.

ORA-09365: Windows 3.1 two-task driver unable to destroy hidden window

Cause: Examine the OSD error accompanying this message.

ORA-09366: Windows 3.1 two-task driver unable to allocate shared memory

Cause: Examine the OSD error accompanying this message.

ORA-09367: Windows 3.1 two-task driver unable to deallocate shared memory

Cause: Examine the OSD error accompanying this message.

ORA-09368: Windows 3.1 two-task driver unable to spawn oracle

Cause: Examine the OSD error accompanying this message.

ORA-09369: Windows 3.1 two-task driver bad instance handle

Cause: Examine the OSD error accompanying this message.

ORA-09370: Windows 3.1 two-task driver oracle task timed out

Cause: Examine the OSD error accompanying this message.

09500-09699: MPE/XL Messages

The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.

09700-09999: UNIX Messages

ORA-09700: sclin: maximum number of latches exceeded

Cause: oracle wants to use more latches then are available.

Action: Increase init.ora parameter LATCH_PAGES, or decrease the amount of shared memory you are using.

ORA-09701: scnfy: maximum number of processes exceeded

Cause: PROCESSES init.ora parameter exceeded.

Action: Decrease the PROCESSES parameter and restart.

ORA-09702: sem_acquire: cannot acquire latch semaphore

Cause: The semaphore used for accessing latches failed to be seized.

Action: Send trace file to your customer support representative, along with information on reproducing the error.

ORA-09703: sem_release: cannot release latch semaphore

Cause: The semaphore used for accessing latches failed to release.

Action: Send trace file to your customer support representative, along with information on reproducing the error.

ORA-09704: sstascre: ftok error in creating test and set pages

Cause: the ftok() library call failed in sstastcre().

Action: Verify that the tasdefsid.dbf file exists. If it does, then this is a possible system failure. Perhaps System V compatibility is not enabled.

ORA-09705: spcre: cannot initialize latch semaphore

Cause: The semaphore used for accessing latches failed to initialize.

Action: Send trace file to your customer support representative, along with information on reproducing the error.

ORA-09706: slsget: get_process_stats error

Cause: get_process_stats system call returned an error.This is possibly an OS error.

Action: Examine additional information returned. Look for information in OS reference. Contact Oracle Support.

ORA-09708: soacon: failed to bind socket to port

Cause: The bind system call failed on the socket.

Action: Examine additional information for OS error. Try connecting again.

ORA-09709: soacon: failed to accept a connection

Cause: The accept system call failed on the socket.

Action: Examine additional information for OS error. Try connecting again.

ORA-09710: soarcv: buffer overflow

Cause: The internal buffer is not big enough to hold the message read. This is an internal error.

Action: Contact Oracle Support.

ORA-09712: orasrv: log archiver already connected

Cause: An existing connection has already been made from log archiver to orasrv.

Action: Stop trying to connect.

ORA-09714: two task interface: cannot obtain puname

Cause: The TXIPC driver cannot obtain the name of the PU. This is possibly an OS error.

Action: Verify that the PUs are named (consistent).

ORA-09715: orasrv: cannot obtain puname

Cause: Orasrv cannot obtain the name of the PU. This is possibly an OS error.

Action: Verify that the PUs are named (consistent).

ORA-09716: kslcll: unable to fix in-flux lamport latch

Cause: One oracle process died while still holding a lamport latch.

Action: Exit (kill) all oracle user processes. Shutdown (abort) and restart Oracle RDBMS kernel.

ORA-09717: osnsui: maximum number of user interrupt handlers exceeded

Cause: The internal limit on the number of user interrupt handlers has been exceeded.

Action: Reduce the number of simultaneous logons, or reduce the number of user interrupt handlers.

ORA-09718: osnsui: cannot set up user interrupt handler

Cause: Malloc() failed to allocate space to hold user interrupt handler.

Action: Possibly, there is a memory resource shortage.

ORA-09719: osncui: invalid handle

Cause: The handle passed to osncui is out of the valid range.

Action: Use a valid handle.

ORA-09740: slsget: cannot get virtual memory region statistics

Cause: The vm_region system call failed to get virtual memory region statistics.

Action: Examine return code in sercerrno. Possible operating system failure.

ORA-09741: spwat: error waiting for a post

Cause: Msg_receive system call returned an error. This is an internal error.

Action: Examine return code in sercerrno. Port name is returned in sercose[0].

ORA-09742: sppst: error during a post

Cause: Msg_send system call returned an error. This is an internal error.

Action: Examine return code in sercerrno. Port name is returned in sercose[0].

ORA-09743: smscre: could not attach shared memory

Cause: The mmap or write system call returned an error. This is an internal error.

Action: Contact Oracle Support.

ORA-09744: smsget: mmap returned an error

Cause: The mmap system call returned an error. This is an internal error.

Action: Contact Oracle Support.

ORA-09745: smscre: vm_allocate error, unable to create shared memory

Cause: Error in system call vm_allocate. Failed to create SGA as a single shared memory segment.

Action: Examine result code returned in sercerrno. Verify that the SGA attach address is valid.

ORA-09746: smscre: shared memory attach address incorrect

Cause: The vm_allocate system call attached the SGA at an incorrect location.

Action: Verify that the SGA attach address is valid.

ORA-09747: pw_detachPorts: server call pws_detach failed

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

Action: Verify that the server is still active. Examine the error code returned in sercerrno, and look for error messages in the server log file.

ORA-09748: pws_look_up: fork failed

Cause: The pws_look_up call failed to fork the (Oracle helper) process.

Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.

ORA-09749: pws_look_up: port lookup failure

Cause: The pws_look_up failed to find a port (to Oracle helper).

Action: Verify that the (Oracle helper) server has been started correctly by pws_look_up, and that the network name server is still running.

ORA-09750: pw_attachPorts: port_rename failed

Cause: The port_rename system call failed. This is possibly an internal error.

Action: Examine return code in sercerrno. Contact Oracle Support.

ORA-09751: pw_attachPorts: server call pws_attach failed

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

Action: Verify that the server is still active. Examine the error code returned in sercerrno, and look for error messages in the server log file.

ORA-09752: pw_attachPorts: port_allocate failed

Cause: The port_allocate system call failed. This is possibly due to resource exhaustion.

Action: Examine return code in sercerrno. Contact Oracle Support.

ORA-09753: spwat: invalid process number

Cause: Function was passed an invalid oracle process ID. This is an internal error.

Action: Additional information indicates the invalid process ID.

ORA-09754: sppst: invalid process number passed to sppst

Cause: Function was passed an invalid oracle process ID. This is an internal error.

Action: Contact Oracle Support.

ORA-09755: osngpn: port allocation failure

Cause: The port_allocate system call failed. This is possibly due to a system resource shortage.

Action: Examine the error code in sercerrno.

ORA-09756: osnpns: no port in the name server

Cause: Osnpns failed to find the given named port in the name server.

Action: Examine the error code in sercerrno. Verify that the shadow process and network name server are still running.

ORA-09757: osnipn: port allocation failure

Cause: The port_allocate system call failed. This is possibly due to a system resource shortage.

Action: Examine the error code in sercerrno.

ORA-09758: osnipn: could not check port in name server

Cause: The netname_check_in call failed.

Action: Examine the error code in sercerrno. Verify that the network name server is running.

ORA-09759: osnsbt: bad message received

Cause: The msg_receive system call failed or received a bad message. This is an internal error.

Action: Report the error code returned in sercerrno.

ORA-09760: osnpui: cannot send break message

Cause: The pipe driver failed to send a break message to the oracle shadow process break thread.

Action: Contact Oracle Support.

ORA-09761: pw_destroyPorts: server call pws_stop_instance failed

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

Action: Verify that the server is still active. Examine the error code returned in sercerrno, and look for error messages in the server log file.

ORA-09762: sNeXT_instanceName: translation error

Cause: A failure was detected while translating the value of ORACLE_SID.

Action: Verify that ORACLE_SID is defined and that it is of legal length.

ORA-09763: osnmpx: send/receive error exchanging mach ports

Cause: The mach driver failed to exchange port information with the other side of the connection. Either msg_send (sercose[0] == 1) or msg_receive (sercose[0] == 2) failed.

Action: Examine return code in sercerrno. Verify that both sides of the connection are still running.

ORA-09764: osnmop: access error on oracle executable

Cause: The mach driver failed to access the oracle executable.

Action: Verify the permissions on the oracle executable and each component of the $ORACLE_HOME/bin path.

ORA-09765: osnmop: fork failed

Cause: The mach driver failed to fork the oracle shadow process.

Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.

ORA-09766: osnmop: buffer allocation failure

Cause: The mach driver failed to allocate enough vm space for its I/O buffers.

Action: Decrease the value of buffer_size parameter in the two-task driver hoststring.

ORA-09767: osnmfs: bad return code from msg_send

Cause: The msg_send system call failed while flushing the mach driver's send buffer. This is an internal error.

Action: Contact Oracle Support.

ORA-09768: osnmgetmsg: could not read a message

Cause: The msg_receive system call returned a failure code while waiting for a message in the mach driver. This is an internal error.

Action: Contact Oracle Support.

ORA-09769: osnmbr: cannot send break message

Cause: The mach driver failed to send a break message to the oracle shadow process break thread. This is an internal error.

Action: Contact Oracle Support.

ORA-09770: pws_look_up: translation failure

Cause: The pws_look_up routine failed to translate the name of the (Oracle helper) executable.

Action: Verify that ORACLE_SID and $ORACLE_HOME are set and correct. Additional information gives the translation error code.

ORA-09771: osnmwrtbrkmsg: bad return code from msg_send

Cause: The msg_send system call failed while sending a mach driver break. This is an internal error.

Action: Contact Oracle Support.

ORA-09772: osnpmetbrkmsg: message from host had incorrect message type

Cause: The mach driver received a message having an unrecognizable message type. This is an internal error.

Action: Contact Oracle Support.

ORA-09773: osnmgetdatmsg: message from host had incorrect message type

Cause: The mach driver received a message having an unrecognizable message type. This is an internal error.

Action: Contact Oracle Support.

ORA-09774: osnmui: cannot send break message

Cause: The mach driver failed to send a break message to the oracle shadow process break thread. This is an internal error.

Action: Contact Oracle Support.

ORA-09775: osnmrs: reset protocol error

Cause: The mach two-task driver failed to reset the connection. This is an internal error.

Action: Contact Oracle Support.

ORA-09776: pws_look_up: access error on (Oracle helper) executable

Cause: The pws_look_up call failed to access the (Oracle helper) executable.

Action: Verify the permissions on the (Oracle helper) executable and each component of the $ORACLE_HOME/bin path.

ORA-09777: osnpbr: cannot send break message

Cause: The pipe driver failed to send a break message to the oracle shadow process break thread. This is an internal error.

Action: Contact Oracle Support.

ORA-09778: snynfyport: failure allocating the notify port

Cause: The routine failed to allocate or set the task's notify port.

Action: Possible operating system error. Contact Oracle Support.

ORA-09779: snyGetPort: failure to allocate a port

Cause: The port_allocate system call failed; system resources might be exhausted. This is possibly an operating system error.

Action: Contact Oracle Support.

ORA-09786: sllfop: open error, unable to open file

Cause: Open system call returned an error.

Action: Examine errno.

ORA-09787: sllfop: unrecognizable processing option, incorrect format

Cause: Processing option passed is of incorrect format.

Action: Consult IUG for permissible formats.

ORA-09788: sllfrb: unable to read file

Cause: Read system call returned an error.

Action: Examine errno. Verify that file exists.

ORA-09789: sllfsk: unable to read file

Cause: Read system call returned an error.

Action: Examine errno. Verify that file exists.

ORA-09790: sllfcf: unable to close file

Cause: Close system call returned an error.

Action: Examine errno.

ORA-09791: slembdf: translation error, unable to translate error file name

Cause: Additional information indicates error returned from sltln.

Action: Examine additional information.

ORA-09792: sllfop: cannot allocate read buffer

Cause: Malloc system call returned an error. The system might have run out of heap space.

Action: Examine additional information for the OS error.

ORA-09793: szguns: length of user name is greater than buffer

Cause: The length of the name of the user being looked up is longer than size of the buffer provided by the calling routine. This is an internal error.

Action: Contact Oracle Support.

ORA-09794: szrbuild: length of role name is greater than buffer

Cause: The length of the name of the role being looked up is longer than size of the buffer provided by the calling routine. This is an internal error.

Action: Contact Oracle Support.

ORA-09795: szrbuild: malloc of role structure failed

Cause: The allocation of memory for an internal structure used to hold a role descriptor failed.

Action: Examine the UNIX error number for a possible operating system failure.

ORA-09796: szrbuild: malloc of role name failed

Cause: The allocation of memory for an internal buffer used to hold the name of a role failed.

Action: Examine the UNIX error number for a possible operating system failure.

ORA-09797: failed to get O/S MAC privileges

Cause: The operating system would not allow the retrieval of this process' privileges.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support.

ORA-09798: label comparison failed

Cause: The comparison of two binary labels failed.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support.

ORA-09799: file label retrieval failed

Cause: The oracle executable failed to get a label attached to a file.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support.

ORA-09800: process sensitivity label retrieval failed

Cause: The oracle executable failed to get the sensitivity label for a process.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support.

ORA-09801: unable to get user ID from connection

Cause: The oracle executable failed to retrieve the user's ID number from the Oracle Net connection.

Action: Examine the UNIX error number for a possible operating system error. Also examine the "additional information" field for the Oracle Net error. If there is no error, then contact Oracle Support.

ORA-09802: conversion of binary label to string failed

Cause: The oracle executable failed to convert a binary label to a string.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support.

ORA-09803: allocation of string buffer failed

Cause: A buffer used to hold the name of the file for which a label was to be obtained failed to allocate.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support. The number of bytes that oracle attempted to allocate is in the "additional information" field.

ORA-09804: class conversion from binary to oracle failed

Cause: The oracle executable failed to convert a class component from binary format to Oracle format.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support.

ORA-09805: conversion of category number to string failed

Cause: The oracle executable failed to translate a category number to its corresponding string representation failed.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support. The category number is contained in the "additional information" field.

ORA-09806: allocation of label string buffer failed

Cause: A temporary buffer used to hold a label failed to allocate.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support. The number of bytes that oracle attempted to allocate is in the "additional information" field.

ORA-09807: conversion of label from string to binary failed

Cause: The oracle executable failed to convert the string representation of a label to binary format.

Action: Re-enter a valid label.

ORA-09808: could not obtain user clearance

Cause: The oracle executable failed to get a user's clearance level.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support.

ORA-09809: unable to get user's group ID from connection

Cause: The oracle executable failed to retrieve the user's group ID number from the Oracle Net connection.

Action: Examine the UNIX error number for a possible operating system error. Also examine the "additional information" field for the Oracle Net error. If there is no error, then contact Oracle Support.

ORA-09810: unable to get process ID from connection

Cause: The oracle executable failed to retrieve the user's process ID number from the Oracle Net connection.

Action: Examine the UNIX error number for a possible operating system error. Also examine the "additional information" field for the Oracle Net error. If there is no error, then contact Oracle Support.

ORA-09811: unable to initialize package

Cause: The oracle executable failed to initialize the library used to obtain security information. This is an internal error.

Action: Contact Oracle Support.

ORA-09812: unable to get user clearance from connection

Cause: The oracle executable failed to retrieve the user's operating system session clearance from the Oracle Net connection.

Action: Examine the UNIX error number for a possible operating system error. Also examine the "additional information" field for the Oracle Net error. If there is no error, then contact Oracle Support.

ORA-09813: unable to get directory status

Cause: The oracle executable failed to determine if a directory is multilevel.

Action: Examine the UNIX error number for a possible operating system error. If there is no error, then contact Oracle Support.

ORA-09814: unable to expand file name

Cause: The oracle executable failed to expand the name of a file that resides in multilevel directory.

Action: Examine the UNIX error number for a possible operating system error. If there is no error, then contact Oracle Support. This is an internal error.

ORA-09815: file name buffer overflow

Cause: The buffer that oracle uses to hold the expanded name of a too small.

Action: Contact Oracle Support.

ORA-09816: unable to set effective privileges

Cause: This is an internal error.

Action: Contact Oracle Support.

ORA-09817: write to audit file failed.

Cause: The oracle executable failed to write an entry to the file used for the audit trail.

Action: Examine the UNIX error number for a possible operating system error. If there is no error, then contact Oracle Support.

ORA-09818: number is too large

Cause: The oracle executable failed to convert a component string to a number, because the number is larger than the largest possible value for an integer. The additional information field specifies the maximum.

Action: Correct the string and repeat the conversion.

ORA-09819: number exceeds maximum legal value

Cause: The number specified for a component was greater than the maximum value allowed for that component.

Action: Change the component to a value less than the maximum and repeat the conversion. The maximum component number is contained in the "additional information" field.

ORA-09820: conversion of class string to numeric representation failed

Cause: The oracle executable failed to convert a class string to a number because all of the characters in the string were not numeric.

Action: Change the string to be either all numbers or all non-numeric characters, and repeat the conversion.

ORA-09821: numeric label is not valid

Cause: A label specified in Oracle numeric format was found not to be valid.

Action: Re-enter a valid label. Consult system's encodings for valid numeric component values.

ORA-09822: translation of audit file name failed

Cause: The oracle executable failed to translate the value of the AUDIT_TRAIL_DEST initialization parameter.

Action: Examine the UNIX error number for a possible operating system error. If there is no error, then contact Oracle Support.

ORA-09823: device name is too long

Cause: The name of a device was too long to fit into an internal buffer. The additional information field contains the length of the device name. This is an internal error.

Action: Contact Oracle Support.

ORA-09824: unable to enable allowmacaccess privilege

Cause: The oracle executable failed to turn on allowmacaccess privilege, so that it could do a label comparison.

Action: Examine the UNIX error number. If it indicates that Oracle does not have the allowmacaccess privilege, then add the allowmacaccess privilege to the potential privilege set of $ORACLE_HOME/bin/oracle using chpriv (1M). If the executable already has the allowmacaccess privilege, then contact Oracle Support.

ORA-09825: unable to disable allowmacaccess privilege

Cause: The oracle executable failed to turn off the allowmacaccess privilege after doing a label comparison. This is an internal error.

Action: Contact Oracle Support.

ORA-09826: SCLIN: cannot initialize atomic latch

Cause: System call atomic_op() return error.

Action: Examine additional information in the trace file.

ORA-09827: SCLGT: atomic latch return unknown error

Cause: System call atomic_op() return unexpected error.

Action: Examine additional information in the trace file.

ORA-09828: SCLFR: atomic latch return error

Cause: System call atomic_op() return unexpected error.

Action: Examine additional information in the trace 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: Verify that the server is still active. Examine the error code returned in sercerrno, and look for error messages in the server log file.

ORA-09830: snyAddPort: failed to perform a remote procedure call

Cause: The msg_rpc system call returned an error. This is an internal error.

Action: Contact Oracle Support.

ORA-09831: snyStartThread: failed to build the server port set

Cause: The routine failed to build a port set on which to listen for requests. This is possibly an operating system failure.

Action: Contact Oracle Support.

ORA-09832: infoCallback: bad message format

Cause: The routine received an incorrectly formatted request. This is an internal error.

Action: Contact Oracle Support.

ORA-09833: addCallback: bad message format

Cause: The routine received an incorrectly formatted request. This is an internal error.

Action: Contact Oracle Support.

ORA-09834: snyGetPortSet: failed to collect info on a port

Cause: The port_status system called failed. This is possibly an operating system error.

Action: Contact Oracle Support.

ORA-09835: addCallback: callback port is already in a set

Cause: The port to be added to the callback list is already in a port set. This is an internal error.

Action: Contact Oracle Support.

ORA-09836: addCallback: could not add a port to the callback set

Cause: The port_set_add system called failed. This is possibly an operating system error.

Action: Contact Oracle Support.

ORA-09837: addCallback: could not add allocate a callback link

Cause: The malloc library call failed to allocate space for a callback link. This is possibly an operating system error.

Action: Contact Oracle Support.

ORA-09838: removeCallback: failure removing the callback port

Cause: The port port_set_remove system call failed. This is possibly an operating system error.

Action: Contact Oracle Support.

ORA-09839: removeCallback: callback port is not in the callback set

Cause: The port to be removed to the callback list is not in the callback port set. This is an internal error.

Action: Contact Oracle Support.

ORA-09840: soacon: name translation failure

Cause: sltln() failed to translate the named pipe $ORACLE_HOME/dbs/mon2arch_sid.

Action: Verify that the $ORACLE_HOME specified for this ORACLE_SID in oratab is correct.

ORA-09841: soacon: name translation failure

Cause: sltln() failed to translate the named pipe $ORACLE_HOME/dbs/arch2mon_sid.

Action: Verify that the $ORACLE_HOME specified for this ORACLE_SID in oratab is correct.

ORA-09846: soacon: ARCH unable to open named pipe

Cause: Open() failed to open named pipe $ORACLE_HOME/dbs/mon2arch_sid. The max number of open files may have been exceeded.

Action: Verify that the OS userid of the currently running database has search permission for the $ORACLE_HOME/dbs directory.

ORA-09847: soacon: ARCH unable to open named pipe

Cause: Open() failed to open named pipe $ORACLE_HOME/dbs/arch2mon_sid. The max number of open files may have been exceeded.

Action: Verify that the OS userid of the currently running database has search permission for the $ORACLE_HOME/dbs directory.

ORA-09848: soawrt: unable to write to named pipe

ORA-09849: soarcv: unable to read from named pipe

ORA-09853: snyRemovePort: bad return code from request

Cause: The request to remove a port from the callback set returned a failure code. This is possibly an operating system error.

Action: Contact Oracle Support.

ORA-09854: snyPortInfo: bad return code from request

Cause: The request to collect info on a port in the callback set returned a failure code. This is possibly an operating system error.

Action: Contact Oracle Support.

ORA-09855: removeCallback: bad message format

Cause: The routine received an incorrectly formatted request. This is an internal error.

Action: Contact Oracle Support.

ORA-09856: smpalo: vm_allocate error while allocating pga

Cause: The vm_allocate system call returned an error. Possibly, there is a shortage of system resources.

Action: Examine error.

ORA-09857: smprset: vm_protect error while protecting pga

Cause: The vm_protect system call returned an error. This is an internal error.

Action: Contact Oracle Support.

ORA-09870: spini: failure initializing maximum number of open files

Cause: ulimit system call returned an error.

Action: Examine errno.

ORA-09871: TASDEF_NAME: translation error while expanding $ORACLE_HOME/dbs/tasdefsid.dbf

Cause: Failure of sltln($ORACLE_HOME/tasdefsid.dbf) while creating test and set pages.

Action: Examine additional return error for more information.

ORA-09872: TASDEF_CREATE: create failure in creating $ORACLE_HOME/dbs/tasdefsid.dbf

Cause: Create() failed when trying to create the tasdef file.

Action: Verify permissions on $(ORACLE_HOME)/dbs directory.

ORA-09873: TASDEF_OPEN: open error when opening tasdefsid.dbf file

Cause: Failure to open tasdefsid.dbf file. This is possibly a permission problem.

Action: Examine errno. Verify that tasdefsid.dbf file exists.

ORA-09874: TASDEF_READ: read error, unable to read tasdefsid.dbf file

Cause: Read system call returned an error when attempting to read $ORACLE_HOME/dbs/tasdefsid.dbf.

Action: Examine errno. sgadef file may be corrupted or incompatible with Oracle version.

ORA-09875: TASDEF_WRITE: write error when writing $ORACLE_HOME/dbs/tasdefsid.dbf file

Cause: Write call failed. Possibly, there is a shortage of space on device.

Action: Examine errno.

ORA-09876: TASDEF_CLOSE: unable to close $ORACLE_HOME/dbs/tasdefsid.dbf file

Cause: Close system call returned an error. Possibly this is an operating system failure.

Action: Examine errno.

ORA-09877: sstascre: shmget error, unable to get a shared memory segment

Cause: Error in shmget.

Action: Examine errno. Verify that enough shared memory is available on the system.

ORA-09878: sstascre/sstasat: shmat error, unable to attach tas write page

Cause: Error in shmat.

Action: Examine errno.Verify that enough shared memory is available on the system.

ORA-09879: sstascre/sstasat: shmat error, unable to attach tas read page

Cause: Error in shmat.

Action: Examine errno.Verify that enough shared memory is available on the system.

ORA-09880: sstasfre/sstasdel: shmdt error, unable to detach tas write page

Cause: Error in shmdt.

Action: Examine errno.

ORA-09881: sstasfre/sstasdel: shmdt error, unable to detach tas read page

Cause: Error in shmdt.

Action: Examine errno.

ORA-09882: sstasfre/sstasdel: shmctl error, unable to remove tas shm page

Cause: Error in shmctl.

Action: Examine errno.

ORA-09883: two task interface: oratab file does not exist

Cause: The oratab file does not exist.

Action: Install Oracle before using it, or recreate the oratab file.

ORA-09884: two task interface: SID doesn't match current PU

Cause: The oracle executable is being started on another PU than oracle was configured on, or there is no entry for this SID in oratab file.

Action: Start oracle with this SID on its designated PU (see oratab file). Or install the new database with SID.

ORA-09885: osnTXtt: cannot create TXIPC channel

Cause: The TXIPC driver failed to create pipes for two-task communications with the oracle shadow process.

Action: Probably, the maximum number of open file descriptors per user has been exceeded, or the system file table is full. Examine the operating system error code, and contact system administrator.

ORA-09886: osnTXtt: translation error while expanding txipcsid.trc

Cause: Failure of sltln(txipcsid.trc) while creating debug channel.

Action: Examine additional return error for more information.

ORA-09887: osnTXtt: failed to create/open debug channel

ORA-09888: osnTXtt: txipc channel creation failed

Cause: The txipc driver failed to create channels for two-task communications with the oracle shadow process.

Action: Probably, the maximum number of open file descriptors per user has been exceeded. Examine the system file table operating system error code, and contact system administrator.

ORA-09889: osnTXtt: access error on oracle executable

Cause: The txipc driver failed to access the oracle executable.

Action: Verify the permissions on the oracle executable and each component of the $ORACLE_HOME/bin path.

ORA-09890: osnTXtt: malloc failed

Cause: The txipx driver failed to allocate enough heap space for its context area buffers.

Action: Contact Oracle Support.

ORA-09908: slkmnm: gethostname returned error code

Cause: The system call gethostname returned an error. This is most likely an internal error.

Action: Verify that gethostname is successful in other contexts, and if so contact Oracle Support.

ORA-09909: malloc of scratch buffer failed

Cause: Memory needed for a temporary buffer failed to allocate. The additional information field contains the number of bytes that oracle attempted to allocate. It is probable that the system has run out of memory.

Action: Examine the UNIX error number. If there is no error, contact Oracle Support.

ORA-09910: unable to find oracle password file entry for user

Cause: No entry exists for the user in the oracle password file.

Action: Have the database administrator install a password entry by running orapasswd.

ORA-09911: incorrect user password

Cause: The password entered by the user was incorrect.

Action: Enter the correct password.

ORA-09912: malloc of name buffer(s) failed

Cause: The oracle executable failed to allocate memory for one or both of the buffers that are used to hold the name of DBA and the operator users. It is probable that the system has run out of memory.

Action: Examine the UNIX error number. If there is no error, contact Oracle Support.

ORA-09913: malloc of dummy name failed

Cause: The oracle executable failed to allocate memory for the user name that is to be used in the encryption of the user's password. It is probable that the system has run out of memory.

Action: Examine the UNIX error number. If there is no error, contact Oracle Support.

ORA-09914: unable to open the oracle password file

Cause: The oracle executable failed to open the password file for reading.

Action: Examine the UNIX error number. If the error number indicates that the file does not exist, have the database administrator create the file by running orapasswd. If the error number indicates insufficient permissions, ask the database administrator to change the permissions. Otherwise, contact Oracle Support.

ORA-09915: password encryption failed

Cause: The oracle executable failed to encrypt a password. This is an internal error.

Action: Contact Oracle Support.

ORA-09916: required password was not specified

Cause: A user attempted to connect as "internal", but did not specify a password.

Action: Connect as internal again and specify a password.

ORA-09918: unable to get user privileges from Oracle Net

Cause: The oracle executable failed to retrieve the user's privilege set from the Oracle Net connection.

Action: Examine the UNIX error number for a possible operating system error. Also examine the "additional information" field for the Oracle Net error. If there is no error, contact Oracle Support.

ORA-09919: unable to set label of dedicated server

Cause: The oracle executable failed to set the label of the dedicated to server to the required value.

Action: Examine the UNIX error number for a possible operating system error. Also, verify the privileges on the oracle executable. It should have at least "allowmacaccess" privilege.

ORA-09920: unable to get sensitivity label from connection

Cause: The oracle executable failed to retrieve the user's sensitivity label from the Oracle Net connection.

Action: Examine the UNIX error number for a possible operating system error. Also examine the "additional information" field for the Oracle Net error. If there is no error, contact Oracle Support.

ORA-09921: unable to get information label from connection

Cause: The oracle executable failed to retrieve the user's information label from the Oracle Net connection.

Action: Examine the UNIX error number for a possible operating system error. Also examine the "additional information" field for the Oracle Net error. If there is no error, contact Oracle Support.

ORA-09922: can't spawn process - background log directory not created properly

Cause: The oracle executable failed to spawn a background process because the directory that will hold trace files of the background processes was not created properly.

Action: Examine the directory pointed to by the initialization parameter BACKGROUND_DUMP_DEST. Verify that all of the following is true: 1) The directory exists. 2) The name indeed points to a directory, and is not a file. 3) The directory is accessible and writable to the Oracle user.

ORA-09923: can't spawn process - user log directory not created properly

Cause: The oracle executable failed to spawn a background process because the directory that holds the trace files of the dedicated server processes was not created properly.

Action: Examine the directory pointed to by the initialization parameter USER_DUMP_DEST. Verify that all of the following is true: 1) The directory exists. 2) The name indeed points to a directory, and is not a file. 3) The directory is accessible and writable to the Oracle user.

ORA-09924: can't spawn process - core dump directory not created properly

Cause: The oracle executable failed to spawn a background process because the directory that holds the core dumps produced by oracle processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter CORE_DUMP_DEST. Verify that all of the following is true: 1) The directory exists. 2) The name indeed points to a directory, and is not a file. 3) The directory is accessible and writable to the Oracle user.

ORA-09925: unable to create audit trail file

Cause: The oracle executable failed to create the file being used to hold audit trail records.

Action: Examine the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support.

ORA-09926: unable to set effective privilege set of the server

Cause: A dedicated server failed to set it's own privilege set.

Action: Verify that the privileges granted to the oracle executable. It must have at least "allowmacacess" privilege.

ORA-09927: Unable to set label of server

Cause: The oracle executable failed to set the label of a server to a new value.

Action: Verify that the privileges on $ORACLE_HOME/bin/oracle. Verify that it has "allowmacaccess" privilege.

ORA-09928: unable to restore the label of server

Cause: The oracle executable failed to restore the label of the server to the value that it had before raising it to database high. This is an internal error.

Action: Contact Oracle Support.

ORA-09929: GLB of two labels is invalid

Cause: The result of a greatest lower bound operation on two labels was not valid.

Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels.

ORA-09930: LUB of two labels is invalid

Cause: The result of a least upper bound operation on two labels was not valid.

Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels.

ORA-09931: unable to open oracle password file for reading

Cause: An attempt to open a password file for reading failed.

Action: Verify that the permissions on the file have not been changed so that the Oracle user cannot open it.

ORA-09932: close of oracle password file failed

Cause: An attempt to close a password file failed.

Action: Examine the UNIX error number for the specific reason.

ORA-09933: deletion of old password file failed

Cause: The removal of the old password file failed.

Action: Examine the UNIX error number for the specific reason.

ORA-09934: link of current password file to old failed

Cause: The oracle executable failed to create a link so that the old password file could be saved.

Action: Examine the UNIX error number for the specific reason.

ORA-09935: unlink of current password file failed

Cause: The oracle executable failed to complete the saving of the current password file.

Action: Examine the UNIX error number for the specific reason.

ORA-09936: open of oracle password file for write failed

Cause: The oracle executable failed to create a password file.

Action: Examine the UNIX error number for the specific reason.

ORA-09937: chmod of oracle password file failed

Cause: The oracle executable failed to change a password file to be read only.

Action: Examine the UNIX error number for the specific reason.

ORA-09938: save of signal handlers failed

Cause: The oracle executable failed to save the previous values of selected signal handlers. This is an internal error.

Action: Contact Oracle Support.

ORA-09939: restoration of signal handlers failed

Cause: The oracle executable failed to restore the previous values of selected signal handlers. This is an internal error.

Action: Contact Oracle Support.

ORA-09940: oracle password file header is corrupt

Cause: The header of one of the password files was not in the format that the oracle executable expected.

Action: Examine the headers of both files. The header should be in the format FILE VERSION: N.N.N.N.N EXECUTABLE VERSION: N.N.N.N.N where N is a number. Remove the corrupt file(s) and re-run "orapasswd".

ORA-09941: version of orapasswd or installer is older than file

Cause: The version of orapasswd or installer that is being run is older than that of the oracle password file. Since the file version is only changed when the format is changed, this error means that the executable is using a different format than that with which the file was created.

Action: Run a version of the installer or orapasswd whose version is the same or later than that of the file.

ORA-09942: write of oracle password file header failed

Cause: The attempt to write out the header of the oracle password file failed.

Action: Examine the operating system error number. It is possible that the file system became full.

ORA-09943: allocation of memory for password list component failed

Cause: When it is building a list of password file entries, the oracle executable allocates memory for various components. One of the allocations failed. The system has probably run out of memory.

Action: Examine the operating system error number.

ORA-09944: password entry is corrupt

Cause: An entry in an oracle password file was not in the format that the oracle executable expected.

Action: Removed the corrupt file(s) and re-run "orapasswd."

ORA-09945: unable to initialize the audit trail file

Cause: The oracle executable failed to write header information to the file being used for the audit trail.

Action: Examine the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support.

ORA-09946: file name too long for buffer

Cause: The buffer that was to be used to hold a file name was determined to be too short for the generated name. This will happen if the translated name for either a trace file or an audit file is longer than the maximum allowed, which on many ports is 256 characters.

Action: Use a shorter file name.

ORA-09947: unable to allocate connection attributes structure

Cause: The oracle executable failed to allocate the memory needed to hold the attributes of the Oracle Net connection. The "additional information" field holds the number of bytes that oracle attempted to allocate. It is probable that the system has run out of memory.

Action: Examine the UNIX error number.If there is no error, contact Oracle Support.

ORA-09948: process information label retrieval failed

Cause: The oracle executable failed to get the information label for a process.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support.

ORA-09949: unable to get client operating system privileges

Cause: The oracle executable failed to get the operating system privileges for the client process.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support.

ORA-09950: unable to get server operating system privileges

Cause: The oracle executable failed to get its privileges from the operating system.

Action: Contact Oracle Support.

ORA-09951: unable to create file

Cause: The oracle executable failed to create a file.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support.

ORA-09952: scgcmn: lk_open_convert unexpected return: open failed

Cause: The distributed lock manager returned an unexpected value.

Action: Examine for system error message and refer to the distributed lock manager documentation, or contact Oracle Support.

ORA-09953: scggc: unexpected return of a lock convert

Cause: The distributed lock manager returned an unexpected value.

Action: Look for lock manager error message and refer to DLM documentation. Refer to the distributed lock manager documentation, or contact Oracle Support.

ORA-09954: scgcc: unexpected return status to callback of lock close

Cause: The distributed lock manager returned an unexpected value.

Action: Look for lock manager error message and refer to DLM documentation. Refer to the distributed lock manager documentation, or contact Oracle Support.

ORA-09955: scgcan: unexpected return status when canceling a lock

Cause: DLM system service x returned an unexpected value.

Action: Look for system error message and refer to DLM documentation refer to the distributed lock manager documentation, or contact Oracle Support.

ORA-09956: scgcm: unexpected lock status condition

Cause: A global locking system service returned an unexpected value.

Action: Look for system error message (if any) and refer to refer to the distributed lock manager documentation, or contact Oracle Support.

ORA-09957: unable to send termination request to IMON

Cause: The attempt to send a termination signal to IMON failed. This is an internal error.

Action: Contact Oracle Support.

ORA-09958: IMON: two processes with the same oracle pid are active

Cause: The IMON process failed to add an entry for a server process, because another active process occupies the slot. This is an internal error.

Action: Contact Oracle Support.

ORA-09959: IMON: deletion of a process failed

Cause: The IMON process failed to delete a server process from its process ID array, because no entry for the process could be found. This is an internal error.

Action: Contact Oracle Support.

ORA-09960: unable to establish signal handler for termination signal

Cause: The oracle executable failed to set up a handler for the signal used to notify it that the instance was shutting down. This is an internal error.

Action: Contact Oracle Support.

ORA-09961: unable to restore termination signal handler

Cause: The oracle executable failed to set the handler for the termination signal to its previous value. This is an internal error.

Action: Contact Oracle Support.

ORA-09962: lk_group_create error in scggrc

ORA-09963: lk_group_attach error in scggra

ORA-09964: lk_group_detach error in scggrd

ORA-09965: scumnt: db lock name space parameter is null

ORA-09966: scumnt: translation error while expanding $ORACLE_HOME/dbs/lk

Cause: Failure of sltln in scumnt.

Action: Examine additional return error for more information.

ORA-09967: scumnt: unable to create or open file

Cause: Open system call returned an error.

Action: Examine errno

ORA-09968: scumnt: unable to lock file

Cause: Lock file operating system call returned an error.

Action: Examine errno.

ORA-09974: skxfidini: error initializing SDI channel

Cause: The process failed to initialize the SDI channel properly.

Action: Correct the operating system error and retry the operation.

ORA-09975: kxfspini: error initializing SDI process

Cause: The process failed to attach to the SDI channel.

Action: Verify that the SDI process specific limits correctly configured. Correct the operating system error and retry the operation.

ORA-09976: skxfqdini: error creating port

Cause: The process failed to create a communications endpoint.

Action: Verify that the SDI port specific limits correctly configured. Correct the operating system error and retry the operation.

ORA-09977: skxfqhini: error connecting

Cause: The process failed to connect to another endpoint.

Action: Verify that the SDI port specific limits correctly configured. Verify that the other node(s) is part of the cluster and operating properly. Correct the operating system error and retry the operation.

ORA-09978: skxfqhdel: error disconnecting from another endpoint

Cause: The process failed to disconnect cleanly from another endpoint.

Action: Verify that the other node(s) are part of the cluster and operating properly. Verify the instance and processes on the other node(s). Correct the operating system error and retry the operation.

ORA-09979: skxfqhsnd: error sending a message to another endpoint

Cause: The process failed to send a message to an existing endpoint.

Action: Verify that the other node(s) are part of the cluster and operating properly. Verify the instance and processes on the other node(s). Correct the operating system error and retry the operation.

ORA-09980: skxfqdrcv: error receiving a message from another endpoint

Cause: The process encountered an error while trying to receive a message.

Action: Verify that the other node(s) are part of the cluster and operating properly. Verify the instance and processes on the other node(s). Correct the operating system error and retry the operation.

ORA-09981: skxfqdreg: error adding a page to the SDI buffer pool

Cause: The process failed to add a page to the SDI buffer pool.

Action: Correct the operating system error and retry the operation.

ORA-09982: skxfqddrg: error removing a page from the SDI buffer pool

Cause: The process failed to remove a page to the SDI buffer pool.

Action: Correct the operating system error and retry the operation.

ORA-09983: skxfidsht: error shutting down SDI channel

Cause: The process failed shut down the SDI channel

Action: Examine the SDI persistent resources using SDI tools. Verify that all processes exited cleanly and the instance is safely shut down. Delete any remaining SDI channel IDs associated with the current instance.

ORA-09984: SGA file $ORACLE_HOME/dbs/sgadefsid.dbf does not exist

Cause: File does not exist or is not accessible.

Action: Restart the instance to create the SGA definition file.

ORA-09985: SGA definition file could not be read

Cause: Read() operation failed.

Action: Examine errno, and take appropriate action.

ORA-09986: wrong number of bytes read from SGA definition file

Cause: Struct skgmsdef size differs from number of bytes read from SGA file.

Action: Compare the two struct definitions and ensure that they are identical in size and structure.

ORA-09987: unable to attach to SGA in READ-ONLY mode

Cause: The instance is not up, or SGA segments are not read-accessible.

Action: Verify that the instance is up and read permissions for the SGA segments are set.

ORA-09988: error while detaching SGA

Cause: skgmsdef struct is corrupted and/or segment addresses are modified.

Action: Safely shut down instance and mount SGA segments again.

ORA-09989: attempt to use invalid skgmsdef struct pointer

Cause: Pointer to skgmsdef struct used without validating it.

Action: Assign a valid address to the skgmsdef struct pointer before using it.

10000-10999: Internal Messages

This range is for internal error messages which should not normally occur. Internal messages are not documented in this manual.

11000-11999: Net8 MVS Messages

The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.

12000-12099: Table Snapshot Messages

This section lists messages generated when table snapshots are accessed.

ORA-12000: a snapshot log already exists on table name

Cause: An attempt was made to create a snapshot log on a table that already has a snapshot log. Each master table can have only one snapshot log.

Action: All snapshots on a table can use the same snapshot log for that table. To make changes to the existing log, use the ALTER SNAPSHOT LOG command or drop the snapshot log and create it again.

ORA-12001: cannot create log: table name already has a trigger

Cause: An attempt was made to create a snapshot log on a table when the table already had an AFTER ROW trigger. Snapshot logs are filled by an AFTER ROW trigger on the master table, so the trigger cannot be created.

Action: If it is necessary to create a snapshot log, drop the current trigger on the master table.

ORA-12002: there is no snapshot log on table name

Cause: An attempt was made to drop a snapshot that does not exist.

Action: Check spelling, syntax, and use an existing snapshot name.

ORA-12003: snapshot name does not exist

Cause: An attempt was made to reference a snapshot that does not exist.

Action: Check the name of the snapshot in the statement for typing errors. Retry the statement with an existing snapshot name.

ORA-12004: REFRESH FAST cannot be used

Cause: An attempt to fast refresh a snapshot was made when the master table for the snapshot has no snapshot log, or the snapshot log cannot be used.

Action: To REFRESH FAST, first create a snapshot log on the master table. Otherwise, use the REFRESH COMPLETE option of the ALTER SNAPSHOT command. If these options are omitted, Oracle decides the appropriate method for refreshing.

ORA-12005: may not schedule automatic refresh for times in the past

Cause: An attempt was made to schedule an automated snapshot refresh for a time in the past.

Action: Choose a time in the future instead.

ORA-12006: a snapshot with the same user.name already exists

Cause: An attempt was made to create a snapshot with the name of an existing snapshot.

Action: Create the snapshot using a different name or drop the existing snapshot.

ORA-12007: snapshot reuse parameters are inconsistent

Cause: During Import or Export, the CREATE SNAPSHOT or CREATE SNAPSHOT LOG.. REUSE command was given inconsistent parameters immediately after the REUSE.

Action: Other messages will accompany this message. Examine the other messages for a more complete description of the problem.

ORA-12008: error in snapshot refresh path

Cause: Table SNAP$_<snapshot_name> reads rows from the view MVIEW$_<snapshot_name>, 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 <master_owner>.MLOG$_<master> is also referenced.

Action: Examine the other returned messages to find the problem. See if the objects SNAP$_<snapshot_name>, MVIEW$_<snapshot_name>, <mowner>.<master>@<dblink>, <mowner>.MLOG$_<master>@<dblink> still exist.

ORA-12009: snapshots may not contain long columns

Cause: An attempt was made to create a snapshot with a long column.

Action: Do not attempt to create snapshot logs with long columns.

ORA-12010: cannot create snapshot log on table owned by SYS

Cause: CREATE SNAPSHOT LOG attempts to create a trigger on the table, but triggers can not be created on SYS tables.

Action: Do not create snapshot logs on SYS tables.

ORA-12011: execution of name jobs failed

Cause: Some kind of error was caught in DBMS_IJOB.RUN. One or more jobs that were due to be run produced errors that they could not handle.

Action: Look at the alert log for details on which jobs failed and why.

ORA-12012: error on auto execute of job name

Cause: Some kind of error was caught while doing an automatic execute of a job.

Action: Look at the accompanying errors for details on why the execute failed.

ORA-12013: updatable snapshots must be simple enough to do fast refresh

Cause: The updatable snapshot query statement is specified with a join, subquery, union, CONNECT BY, ORDER BY, or GROUP BY.

Action: Specify a simpler snapshot statement. If a join is needed, create multiple simple snapshots, and then create a view on top of the multiple snapshots.

ORA-12014: table name does not contain a primary key constraint

Cause: The CREATE SNAPSHOT LOG command was issued with the WITH PRIMARY KEY option and the master table does not contain a primary key constraint or the constraint is disabled.

Action: Reissue the command using only the WITH ROWID option, create a primary key constraint on the master table, or enable an existing primary key constraint.

ORA-12015: cannot create a fast refresh snapshot from a complex query

Cause: Neither ROWIDs and nor primary key constraints are supported for complex queries.

Action: Reissue the command with the REFRESH FORCE or REFRESH COMPLETE option or create a simple snapshot.

ORA-12016: snapshot does not include all primary key columns

Cause: The query that instantiates the snapshot does not include all of the columns in the master's primary key constraint.

Action: Include all of the master's primary key columns in the snapshot query or create a ROWID snapshot.

ORA-12017: cannot alter primary key snapshot name to a ROWID snapshot

Cause: Conversion of a primary key snapshot to a ROWID snapshot is not supported.

Action: Create a new snapshot or drop and recreate the snapshot.

ORA-12018: following error encountered during code generation for name.name

Cause: The refresh operations for the indicated snapshot could not be regenerated due to errors. See following error text.

Action: Correct the indicated problem and repeat the operation.

ORA-12019: master table is a synonym to a remote object

Cause: Snapshot of remote synonyms or snapshot logs on remote synonym are not supported.

Action: Do not create the snapshot or snapshot log on a remote synonym.

ORA-12020: snapshot name is not registered

Cause: Attempt to unregister a snapshot that is not registered.

Action: Nothing needs to be done.

ORA-12021: snapshot name.name is corrupt

Cause: The snapshot indicated is no longer valid.

Action: Contact your customer support representative.

ORA-12022: snapshot log on name.name already has ROWID

Cause: Snapshot log on the indicated table already has ROWID information.

Action: No action required.

ORA-12023: missing index on snapshot name.name\

Cause: The specified ROWID snapshot does not have the required index on the ROWID column of its underlying table.

Action: The snapshot is corrupted. Drop and recreate the snapshot.

ORA-12024: snapshot log on name.name does not have primary key columns

Cause: Snapshot log on the indicated table does not have primary key information.

Action: Add primary keys to snapshot log using the ALTER SNAPSHOT command.

ORA-12025: snapshot log on name.name already has primary keys

Cause: Snapshot log on the indicated table already has primary key columns.

Action: No action required.

ORA-12026: invalid filter column detected

Cause: One or more of the specified filter columns does not exist or is a primary key column.

Action: Ensure that all specified filter columns exist in the master table and ensure that primary key columns are not included in the list of filter columns.

ORA-12027: duplicate filter column

Cause: One or more of the specified filter columns is already recorded in the snapshot log.

Action: Describe the snapshot log table and reissue the SQL command specifying the filter columns that are already recorded in the snapshot log.

ORA-12028: snapshot type is not support by master site name.

Cause: Pre-Oracle8 master sites are not able to support primary key or subquery snapshots that are able to perform a fast refresh.

Action: Create a ROWID snapshot or use a master table from an Oracle8 site.

ORA-12029: LOB columns may not be used as filter columns

Cause: LOB columns may not be used as filter columns.

Action: Remove LOB columns from the filter columns list and retry the command.

ORA-12030: cannot create a fast refresh snapshot

Cause: The snapshot log does not exist or does not log the information needed by the snapshot to perform a fast refresh.

Action: Ensure that the snapshot log exists and logs the necessary information. For ROWID snapshots, the master table's ROWID must be logged. For primary key, snapshots the master table's primary key columns must be logged. For subquery snapshots filter, primary key, and ROWID values must all be logged.

ORA-12031: cannot use primary key columns from snapshot log on name.name

Cause: The snapshot log either does not have primary columns logged, or the timestamp associated with the primary key columns is more recent than the last refresh time.

Action: A complete refresh is required before the next fast refresh.

ORA-12032: cannot use ROWID column from snapshot log on name.name

Cause: The snapshot log either does not have primary columns logged, or the timestamp associated with the primary key columns is more recent than the last refresh time.

Action: A complete refresh is required before the next fast refresh.

ORA-12033: cannot use filter columns from snapshot log on name.name

Cause: The snapshot log either does not have primary columns logged, or the timestamp associated with the primary key columns is more recent than the last refresh time.

Action: A complete refresh is required before the next fast refresh.

ORA-12034: snapshot log on name.name more recent than last refresh

Cause: The snapshot log is more recent than the last refresh and cannot be used for fast refresh. The snapshot log is more recent than the last refresh.

Action: Perform a complete refresh of the snapshot before attempting another fast refresh.

ORA-12035: could not use snapshot log on name.name

Cause: The snapshot log does not exist or cannot be used for fast refresh.

Action: Perform a complete refresh of the snapshot before attempting another fast refresh. If a snapshot log does exist and the snapshot is capable of fast refresh, then the snapshot will be fast refreshable once the complete refresh is performed.

ORA-12036: updatable snapshot log is not empty, refresh snapshot

Cause: The updatable snapshot log must be empty before an updatable ROWID snapshot can be altered to a primary key snapshot.

Action: Ensure that updatable snapshot log is empty by refreshing the snapshot before converting the updatable ROWID snapshot to a primary key snapshot.

ORA-12037: unknown export format

Cause: An attempt was made to import a snapshot exported by an unknown export version (e.g., from a newer release than the importing site).

Action: Re-export the file using a version of export known by the importing site.

ORA-12038: string literal has unexpected length

Cause: Corrupt or invalid information was detected during import of a snapshot.

Action: Ensure that the export log file has not been corrupted and that no errors were raised during export. Contact customer support if the problem persists.

ORA-12039: unable to use local rollback segment name

Cause: A local rollback segment was specified in the CREATE SNAPSHOT command, but automatic refresh parameters were not specified. Therefore, a refresh group was not created to automatically refresh the snapshot and the local rollback segment cannot be registered for future use.

Action: Either supply the automatic refresh parameters so that a refresh group will be created or do not specify a local rollback segment.

ORA-12040: master rollback segment option not support by master site name

Cause: The master site of the current snapshot does not allow users to specify a rollback segment to be used for snapshot operations. This feature is only supported by Oracle8 or later master sites.

Action: Do not specify a master rollback segment in the current operation or choose a new master site.




Prev

Next
Oracle
Copyright © 1997 Oracle Corporation.
All Rights Reserved.

Library

Product

Contents