Release 8.0
A54625_01
 Library |
 Product |
 Contents |
| Oracle8
Error Messages Release 8.0 A54625_01 |
|
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.
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.
Cause: The required procedure, function, or package name is invalid or missing.
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.
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.
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.
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.
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).
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.
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.
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.
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.
Cause: An attempt was made to execute a stored procedure that has been invalidated.
Action: Recompile the procedure and its dependents.
Cause: An attempt was made to execute a stored procedure that has been altered or dropped.
Action: Recompile the procedure's dependents.
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.
Cause: An attempt was made to execute a package, procedure, or function that does not exist.
Action: Check the name in the command.
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.
This section lists messages generated when triggers are accessed. For more trigger messages, see "25000-25099: Trigger Messages" on page 2¬629.
Cause: An invalid trigger name was specified.
Action: Check that the trigger name is not a reserved keyword.
Cause: The trigger statement is missing the BEFORE/AFTER clause.
Action: Specify either BEFORE or AFTER.
Cause: An invalid trigger type was given.
Action: Specify either INSERT, UPDATE, or DELETE as the trigger type.
Cause: A column list was specified for a trigger type other than UPDATE.
Action: Remove the column list from the trigger.
Cause: An invalid name was given in the REFERENCING clause.
Action: Check that the REFERENCING name is not a reserved word.
Cause: A statement was given for the trigger action.
Action: Specify another trigger action that is not a statement.
Cause: An invalid NEW or OLD specification was given for a column.
Action: Respecify the column using a correct NEW or OLD specification.
Cause: The WHEN clause can only be specified for row-level triggers.
Action: Remove the WHEN clause or specify it for each row.
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.
Cause: The CREATE TRIGGER statement is invalid.
Action: Refer to Oracle8 Server SQL Reference for the correct syntax of the CREATE TRIGGER statement.
Cause: The trigger name specified is invalid, or the trigger does not exist.
Action: Check the trigger name.
Cause: The trigger name or type already exists.
Action: Use a different trigger name or drop the trigger that is of the same type.
Cause: The trigger is accessing NEW or OLD values in a table trigger.
Action: Remove any new or old references.
Cause: The variable referenced in the trigger body is invalid.
Action: See Oracle8 Server SQL Reference for valid trigger variable types.
Cause: New trigger variables can only be changed in before-row triggers.
Action: Change trigger type or remove the variable reference.
Cause: OLD values can only be read and not changed.
Action: Do not attempt to change an OLD variable.
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.
Cause: ROWIDs can only be read and not changed.
Action: Do not attempt to change a ROWID value.
Cause: A runtime error occurred during execution of a trigger.
Action: Check the triggers that were involved in the operation.
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.
Cause: The named trigger has a duplicate event and trigger time as another trigger.
Action: Combine both triggers into one trigger.
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.
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.
Cause: A trigger attempted to reference a LONG column in the triggering table.
Action: Do not reference the LONG column.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: A function was called with an invalid argument.
Action: Contact Oracle Support.
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.
Cause: The I/O buffer is not aligned on a 2K boundary.
Action: Contact Oracle Support.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: An invalid event ID is passed in to this routine.
Action: The additional information indicates the event ID.
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.
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.
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.
Cause: Invalid oracle process ID is passed in to this routine.
Action: The additional information indicates the process ID.
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.
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
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".
Cause: This is a rare internal error message. Memory has been exhausted or corrupted.
Action: Contact customer support.
Cause: This is an internal error message. An error has been detected in a PL/SQL program.
Action: Contact customer support.
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.
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.
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.
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.
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.
Cause: This indicates a version clash between some package distributed with an Oracle product and the product executable.
Action: Contact customer support.
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.
Cause: An attempt was made to open a cursor that was already open.
Action: Close the cursor before attempting to reopen it.
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.
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.
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.
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.
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.
Cause: An error occurred while passing a Probe operation to the server for execution.
Action: Refer to the entry for the embedded error message.
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.
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.
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.
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.
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.
Cause: The option specified is an unsupported feature for external procedures.
Action: Correct the syntax in the external specification.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: A PL/SQL internal error occurred.
Action: Report this as a bug; the first argument is the internal error number.
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.
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.
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.
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.
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.
Cause: Internal error from the DBMS_PIPE package.
Action: Contact customer support.
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.
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.
Cause: Internal error from the DBMS_PIPE package.
Action: Contact Oracle customer support.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.
The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.
The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.
The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.
The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.
The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.
The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.
Cause: The environment variable (ORACLE_SID) is not set.
Action: Set ORACLE_SID environment variable.
Cause: $(ORACLE_HOME) environment variable not set.
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.
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.
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.
Cause: Time() system call returned an error. This is possibly an OS error.
Action: Examine additional information returned. Contact Oracle Support.
Cause: gettimeofday() system call returned an error. This is possibly an OS error.
Action: Examine additional information returned. Contact Oracle Support.
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.
Cause: The fsync system call returned an error. This is possibly an OS error.
Action: Examine additional information returned. Contact Oracle Support.
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.
Cause: Getrusage system call returned an error. This is possibly an OS error.
Action: Examine additional information returned. Contact Oracle Support.
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.
Cause: Times system call returned an error. This is possibly an OS error.
Action: Examine additional information returned. Contact Oracle Support.
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.
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.
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.
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.
Cause: Getenv call returned a null pointer.
Action: Set the environment variable and try again.
Cause: UNIX system() call failed.
Action: Examine system error message.
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.
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.
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.
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.
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.
Cause: The ulimit system call returned an error.
Action: Examine errno. Contact Oracle Support.
Cause: Additional information returned is error returned from sltln.
Action: Examine additional information.
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.
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.
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.
Cause: Error in mpcntl system call.
Action: Examine errno. Contact system administrator.
Cause: Fopen failed to open file.
Action: Try to determine which file was not opened. Verify that the file exists and is accessible.
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.
Cause: An error was encountered when closing the file. The process may have run out of heap space.
Action: Contact system administrator.
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.
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.
Cause: Failure to write item to file. The process may have run out of heap space. This is possibly a permissions problem.
Cause: Failure to open error file. This is possibly a permissions problem.
Action: Verify permission on error message file. Examine additional information for errno.
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.
Cause: Failure to close file. This is possibly an OS error.
Action: Contact system administrator. Examine additional information for errno.
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.
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.
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.
Cause: Additional information indicates error returned from sltln.
Action: Examine additional information.
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.
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.
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.
Cause: sfofi returns an error. This is an internal error.
Action: Contact Oracle Support.
Cause: sfrfb returns an error. This is an internal error.
Action: Contact Oracle Support.
Cause: sfwfb returns an error. This is an internal error.
Action: Contact Oracle Support.
Cause: Open() returns an error. This is an internal error.
Action: Verify that /proc has the correct permissions.
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.
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.
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.
Cause: semctl system call returned an error.
Action: Verify semaphore sets. This may require manual cleanup. Examine additional information returned. Consult OS reference manual.
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.
Cause: System failed to set up signal handler.
Action: Examine errno and sercose[0] for the signal number that failed.
Cause: System failed to set up signal handler to catch exceptions.
Action: Examine errno and sercose[0] for the signal number that failed.
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].
Cause: An error occurred when creating a new process.
Action: Examine errno. Perhaps a system limit on the number of processes has been exceeded.
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.
Cause: Wait system call returned an error.
Cause: Kill system call returned an error. This is possibly an attempt to destroy an already gone process.
Cause: This is an internal error.
Action: Contact Oracle Support.
Cause: Kill system call returned an error. This is possibly an OS error.
Action: Examine errno. Additional information indicates the process ID tested.
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.
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.
Cause: Function was passed an invalid oracle process ID. This is an internal error.
Action: Contact Oracle Support.
Cause: Function was passed an invalid oracle process ID. This is an internal error.
Action: Additional information indicates the invalid process ID.
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.
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.
Cause: An error occurred while trying to set an interval timer. This is probably a porting problem.
Cause: Function was called with an invalid oracle process number (0). This is an internal error.
Action: Contact Oracle Support.
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.
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.
Cause: Failure to access oracle program. Verify that $ORACLE_HOME/bin/oracle or $ORABCKPRG exist and are executable.
Cause: The kill system call returned an error. This is possibly an attempt to signal a process which does not exist.
Cause: A group has not been set up for dba users.
Action: Contact system administrator. Set up dba group in /etc/group.
Cause: A 0 pid was passed to spdde. This is an internal error.
Action: Contact Oracle Support.
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.
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.
Cause: The ioctl call returned an error. This is possibly an OS error.
Action: Examine additional information for errno. Contact Oracle Support.
Cause: Times system call returned an error. This is possibly an OS error.
Action: Examine additional information returned. Contact Oracle Support.
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.
Cause: An invalid volume size was specified.
Action: Specify a valid volume size in the archive control string.
Cause: Some non-numeric text follows the volume size specification.
Action: Enter a correct archive control string.
Cause: Volume size was specified for a disk file.
Action: If archiving to a disk file, do not specify its volume size.
Cause: Stat on the log archiving device failed.
Action: Examine the returned OSD error for the reason of failure.
Cause: Log archiving to this device is unsupported.
Action: Try log archiving to a supported device.
Cause: The specified path name is not a directory.
Action: Verify that the archive destination directory exists.
Cause: Failure of sltln($ORACLE_HOME/dbs/sgadefsid.dbf) in smscre.
Action: Examine additional return error for more information.
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.
Cause: Create() failed when trying to create the sgadef file.
Action: Verify permissions on $(ORACLE_HOME)/dbs directory.
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.
Cause: The redo buffer size must be a multiple of machine block size.
Action: Verify that the LOG_BUFFER init.ora parameter is correct.
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.
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.
Cause: Failed to attach shared memory segment, after having gotten it.
Action: Examine errno. Verify that the SGA attach address is valid.
Cause: Write call failed in smscre. Possibly, the device is out of space.
Cause: Close system call returned an error. This is possibly an operating system failure.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: Failure to open sgadef.dbf file. This is possibly a permission problem.
Action: Examine errno. Verify that sgadef.dbf file exists.
Cause: Read had an error when reading sgadef.dbf file.
Action: Examine errno. Verify that the file exists and is correct size.
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.
Cause: sercose[0] returns segment ID.
Cause: Failure to close sgadef.dbf file. This is possibly an OS error.
Cause: Problem deleting shared segments.
Action: Retry. Examine errno. This may require manual cleanup of shared memory segments.
Cause: Malloc library routine returned an error. Possibly, it is out of swap space.
Cause: Malloc library routine returned an error. Possibly, it is out of swap space.
Cause: Smsfre was called when the SGA was not mapped. This is an internal error.
Action: Contact Oracle Support.
Cause: smpdal was called when the PGA had not been previously created. This is an internal error.
Action: Contact Oracle Support.
Cause: shmget system call returned a fatal error.
Action: Examine errno. Additional information indicates the SGA model attempted.
Cause: The internal data structure which holds segment information is full.
Action: Reconfigure the UNIX kernel to have bigger segments.
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.
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.
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.
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.
Cause: The internal data structure which holds segment information is full.
Action: Reconfigure the UNIX kernel to have bigger segments.
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.
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.
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.
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.
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.
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.
Cause: fopen library routine returned an error.
Action: Verify existence and permissions.
Cause: fclose library routine returned an error. This is possibly an internal error.
Action: Contact Oracle Support.
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.
Cause: The system failed to restore user exception handlers.
Action: Examine errno and sercose[0] for the signal number that failed.
Cause: The system failed to restore user signal handlers.
Action: Examine errno and sercose[0] for the signal number that failed.
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.
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.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for decimal to binary conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for decimal to binary conversion was made.
Action: This conversion cannot be performed.
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.
Cause: One of the database writer processes failed to locate its entry in the SGA.
Action: Contact Oracle Support.
Cause: Malloc() failed to allocate buffer for storing ORACLE_PATH. System has run out of heap space.
Action: Additional information indicates errno.
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].
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.
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.
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.
Cause: An oracle error occurred when translating the location of the dump file.
Action: Examine the error code.
Cause: An oracle error occurred when translating the location of the dbs directory.
Action: Examine additional information for the error returned from sltln.
Cause: chdir system call returned an error. This is possibly a permission problem.
Action: Examine additional information for the OS error code.
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.
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.
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.
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.
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.
Cause: The wakeup monitor process died.
Cause: An improperly aligned function address was specified.
Action: Use a properly aligned function address.
Cause: An invalid function address was specified.
Action: Use a valid function address.
Cause: An invalid function name was specified.
Action: Use a valid function name.
Cause: An invalid function name/address was specified.
Action: Use a valid function name/address.
Cause: An OS exception occurred which should result in the creation of a core file. This is an internal error.
Action: Contact Oracle Support.
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.
Cause: oracle failed to create a shared arena file.
Action: Use sercerrno field to determine cause of failure.
Cause: oracle attempted to create more shared arena files than permitted.
Action: Raise the value for MAX_ARENA in init.ora.
Cause: oracle failed to acquire a shared arena lock.
Action: Examine result code in sercerrno to determine the cause of failure.
Cause: Error in vm_mapmem. Failed to create SGA as a single shared memory segment.
Action: Examine result code returned in sercose[0].
Cause: The vm_mapmem system call attached the SGA at an incorrect location.
Action: Verify that the SGA attach address is valid.
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].
Cause: Error in vm_mapmem. Failure to create a segment of the SGA.
Action: Examine result code returned in sercerrno.
Cause: The vm_mapmem system call attached an SGA segment at an incorrect location.
Action: Verify that the SGA attach address is valid.
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.
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].
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].
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.
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].
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.
Cause: Open failed when trying to create the file $ORACLE_HOME/dbs/sgadefsid.dbf.
Action: Verify permissions on the $(ORACLE_HOME)/dbs directory.
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].
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.
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].
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.
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.
Cause: An error occurred in close while closing the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly an operating system failure.
Cause: The mset routine returned an error. Semaphore may not exist.
Action: Examine result code in sercerrno. Semaphore number returned in sercose[0].
Cause: The mclear routine returned an error. Semaphore may not exist.
Action: Examine result code in sercerrno. Semaphore number returned in sercose[0].
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].
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].
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.
Cause: Read had an error when reading sgadef.dbf file.
Action: Examine errno. Verify that file exists and is correct size.
Cause: An error occurred in close, while closing the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly an operating system failure.
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.
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.
Cause: Lock manager must be initialized before converting locks. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_stat_lock failed. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_open or lm_open_convert failed. Possible lock manager failure.
Action: Examine result code in sercerrno.
Cause: When creating an instance, snlmini failed to change the permissions on $ORACLE_HOME/dbs/sgalm.dbf.
Action: Contact Oracle Support.
Cause: lm_attach failed to attach to lock manager instance. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
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.
Cause: lm_convert failed to convert(get) lock. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_convert failed to put lock value. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_open failed. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_convert failed to get lock value. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_create failed. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: Lock manager must be initialized before releasing locks. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_stat_lock failed during lock release/cancel. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_convert failed during lock release/cancel. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_cancel failed during lock release/cancel. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_close failed during lock release/cancel. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: An error was encountered releasing the lock. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: Unknown or unexpected error code. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_wait failed. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_post failed. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: The trace file cannot be created for writing.
Action: Verify if the dump directory exists, and whether it is writable.
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.
Cause: The rescheduling driver /dev/resched is not open. This is an internal error.
Action: Contact Oracle Support.
Cause: VMS system service $CANTIM returned an unexpected value.
Action: Look for system error message, and refer to VMS documentation.
Cause: VMS system service $DEQ returned an unexpected value.
Action: Look for system error message, and refer to VMS documentation.
Cause: VMS system service $ENQ returned an unexpected value.
Action: Look for system error message, and refer to VMS documentation.
Cause: VMS system service $SETIMR returned an unexpected value.
Action: Look for system error message, and refer to VMS documentation.
Cause: VMS system service $HIBER returned an unexpected value.
Action: Look for system error message, and refer to VMS documentation.
Cause: VMS system service $ENQ returned an unexpected value.
Action: Look for system error message, and refer to VMS documentation.
Cause: VMS system service $DEQ returned an unexpected value.
Action: Look for system error message, and refer to VMS documentation.
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.
Cause: VMS system service $DEQ returned an unexpected value.
Action: Look for system error message, and refer to VMS documentation.
Cause: VMS system service $DEQ returned an unexpected value.
Action: Look for system error message, and refer to VMS documentation.
Cause: VMS system service $GETLKI returned an unexpected value.
Action: Look for system error message, and refer to VMS documentation.
Cause: VMS system service $ENQ returned an unexpected value.
Action: Look for system error message, and refer to VMS documentation.
Cause: VMS system service $ENQ returned an unexpected value.
Action: Look for system error message, and refer to VMS documentation.
Cause: VMS system service $DEQ returned an unexpected value.
Action: Look for system error message, and refer to VMS documentation.
Cause: VMS system service $DEQ returned an unexpected value.
Action: Look for system error message, and refer to VMS documentation.
Cause: VMS system service $GETLKI returned an unexpected value.
Action: Look for system error message, and refer to VMS documentation.
Cause: Too many test files open. This is an internal error.
Action: Contact Oracle Support.
Cause: VMS system service $OPEN failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $OPEN failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $CLOSE failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GET failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $IDTOASC failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: An extension was found, but it is of improper length. This is an internal error.
Action: Contact Oracle Support.
Cause: VMS system service $PARSE failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: A wildcard was used in the file name.
Action: Reenter the file name completely.
Cause: VMS system service $SEARCH failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $OPEN failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $CLOSE failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $IDTOASC failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $FIND_HELD failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: An OS role name was too long.
Action: Re-define the role name to be of correct length.
Cause: VMS system service LIB$SPAWN failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETUAI failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message, and refer to VMS documentation.
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.
Cause: VMS system service $FIND_HELD failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $PARSE failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message, and refer to VMS documentation.
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.
Cause: The ORA_SID must exist and be less than 6 characters.
Action: Consult the VMS Installation Guide for information on setting the SID.
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.
Cause: VMS system service $PARSE failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $SEARCH failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $CREPRC failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message, and refer to VMS documentation.
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.
Cause: VMS system service $DELPRC failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: While obtaining needed privileges, an error was returned from SYS$SETPRV. This is an internal error.
Action: Contact Oracle Support.
Cause: While releasing privileges, an error was returned from SYS$SETPRV. This is an internal error.
Action: Contact Oracle Support.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $SCHDWK failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETSYIW failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $ASCTOID failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $CHKPRO failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $SNDOPR failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETUAI failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $HASH_PASSWORD failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETUAI failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $CHANGE_CLASS failed.
Action: Examine system error message, and refer to SEVMS documentation.
Cause: VMS system service $CHANGE_CLASSS failed.
Action: Examine system error message, and refer to SEVMS documentation.
Cause: VMS system service $CHANGE_CLASS failed.
Action: Examine system error message, and refer to SEVMS documentation.
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.
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.
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.
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.
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.
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.
Cause: While creating the system global area (SGA), VMS system service $CRMPSC failed.
Action: Examine the system error message, and refer to VMS documentation.
Cause: While deleting the system global area (SGA), VMS system service $DGBLSC failed.
Action: Examine the system error message, and refer to VMS documentation.
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.
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.
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.
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.
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.
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.
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.
Cause: While deleting a context area, VMS system service $DELTVA failed.
Action: Examine the system error message, and refer to VMS documentation.
Cause: The buffer debug function was called with an illegal value. This is an internal error.
Action: Contact Oracle Support.
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $CRETVA failed.
Action: Contact Oracle Support.
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $SETPRT failed.
Action: Contact Oracle Support.
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $MGBLSC failed.
Action: Contact Oracle Support.
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.
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.
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.
Cause: An attempt was made to map to the SGA while it was being initialized.
Action: Wait until initialization is complete, and try again.
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.
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.
Cause: This is an internal error.
Action: Report this error to Oracle Support; provide the init.ora file.
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.
Cause: While attempting to create a file, VMS system service $CREATE failed.
Action: Examine the system message, and refer to VMS system documentation.
Cause: While attempting to reopen a file, VMS system service $OPEN failed.
Action: Examine the system message, and refer to VMS system documentation.
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.
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.
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.
Cause: While prompting for a password, VMS system service $ASSIGN failed.
Action: Examine the system message, and refer to VMS documentation.
Cause: While prompting for a password, VMS system service $QIOW failed.
Action: Examine the system message, and refer to VMS documentation.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: An interrupt was received while archiving the logs.
Cause: Overflow of buffer for parsing archive control text string. This is an internal error.
Action: Contact Oracle Support.
Cause: Unrecognized device type in archive text. This is an internal error.
Action: Contact Oracle Support.
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.
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.
Cause: The buffer supplied for the device name is too small. This is an internal error.
Action: Contact Oracle Support.
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.
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.
Cause: The buffer supplied for the tape label is too small. This is an internal error.
Action: Contact Oracle Support.
Cause: The user specified a remote disk for archiving via DECnet.
Action: Archive to a disk on the local host.
Cause: The buffer supplied for the file name is too small. This is an internal error.
Action: Contact Oracle Support.
Cause: VMS system service SYS$MOUNT failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service SYS$DISMNT failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service SYS$GETDVI failed.
Action: Specify a valid device in ARCHIVE control string.
Cause: VMS system service LIB$GET_VM failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service LIB$FREE_VM failed.
Action: Examine system error message, and refer to VMS documentation.
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.
Cause: Structures used for reading error message files do not match. This is an internal error.
Action: Contact Oracle Support.
Cause: VMS system service $OPEN failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: VMS system service $CONNECT failed.
Action: Examine system error message, and refer to VMS documentation.
Cause: An error message file has incorrect format.
Action: Unless an error file has been changed, contact Oracle Support.
Cause: Seal in passed in handle does not match correct value. This is an internal error.
Action: Contact Oracle Support.
Cause: VMS system service $CLOSE failed.
Action: Examine system error, and refer to VMS documentation.
Cause: Seal in passed in handle does not match correct value. This is an internal error.
Action: Contact Oracle Support.
Cause: VMS system service $READ failed.
Action: Examine system error, and refer to VMS documentation.
Cause: An attempt to create a message file failed. This is an internal error.
Action: Contact Oracle Support.
Cause: An attempt to allocate a cache for a newly-created message file failed. This is an internal error.
Action: Contact Oracle Support.
Cause: An attempt to seek before writing a message file cache element failed. This is an internal error.
Action: Contact Oracle Support.
Cause: An attempt to write a message file cache element failed. This is an internal error.
Action: Contact Oracle Support.
Cause: An attempt to seek before reading a message file cache element failed. This is an internal error.
Action: Contact Oracle Support.
Cause: An attempt to read a message file cache element failed. This is an internal error.
Action: Contact Oracle Support.
Cause: The seal in a passed-in handle does not match correct value. This is an internal error.
Action: Contact Oracle Support.
Cause: The seal in a passed-in handle does not match correct value. This is an internal error.
Action: Contact Oracle Support.
Cause: The destination string provided to the function is too short. This is an internal error.
Action: Contact Oracle Support.
Cause: the $open service failed. This is an internal error.
Action: Contact Oracle Support.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for decimal to binary conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for decimal to binary conversion was made.
Action: This conversion cannot be performed.
Cause: An error was returned from the SYS$CRELNM function.
Action: Examine system error, and refer to VMS documentation.
Cause: An error was returned from the SYS$DELLNM function.
Action: Examine system error, and refer to VMS documentation.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: An error was returned by SYS$CONNECT while attempting to open the data file.
Action: Examine system error, and refer to VMS documentation.
Cause: An error was returned by SYS$GET while attempting to read the data file.
Action: Examine system error, and refer to VMS documentation.
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.
Cause: A bad option to loader Fixed= is one legal option.
Action: Examine documentation.
Cause: An error occurred while setting up the control interrupt handler. This is an internal error.
Action: Contact Oracle Support.
Cause: A list of all files open by this process failed to be obtained. This is an internal error.
Action: Contact Oracle Support.
This section lists messages generated when Oracle is accessing data or database objects.
Cause: This is an internal error message not normally issued.
Action: Contact customer support.
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.
Cause: Sequence CURRVAL was selected before sequence NEXTVAL was referenced.
Action: Select NEXTVAL from the sequence before selecting CURRVAL.
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.
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.
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.
Cause: The row has been deleted by another user since the operation began.
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.
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.
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.
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.
Cause: The object has been deleted by another user since the operation began.
Action: Remove references to the object.
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.
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.
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.
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.
Cause: The lock manager failed to open a lock.
Action: Verify that enough memory is available, and retry the operation.
Cause: The lock manager failed to convert a lock.
Cause: The lock manager encountered an error closing a lock.
Action: Examine the lock manager status returned for additional information.
Cause: The lock manager encountered an error cancelling a convert request.
Action: Examine the lock manager status returned for additional information.
Cause: The lock manager returned an unexpected value.
Action: Examine the lock manager status returned for additional information.
Cause: The environment variable ORACLE_SID is not set.
Action: Set the ORACLE_SID environment variable.
Cause: Failure to translate $ORACLE_HOME/dbs/sgadefsid.dbf.
Action: Ensure that $ORACLE_HOME and ORACLE_SID are properly set.
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.
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.
Cause: The System Commit Number has not yet been initialized.
Action: Contact Oracle Support
Cause: The oracle executable requested that an I/O error be returned for this operation.
Action: Contact Oracle Support.
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.
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.
Cause: Probably, the listener process has died.
Action: Contact Oracle Support.
Cause: The n_core system call failed while detaching from the SGA.
Action: Note nCX error. Contact Oracle Support.
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.
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.
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.
Cause: Attempting to attach to an SGA which has not yet been created.
Action: Verify that the instance is running. Contact Oracle Support.
Cause: The n_core system call failed while detaching from the SGA.
Action: Examine nCX error, and contact Oracle Support.
Cause: The file name of the lock manager address file is too long.
Action: Use a shorter parallel server name.
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.
Cause: An error was encountered detaching from the lock manager.
Action: Additional information is lock manager return code. Contact Oracle Support.
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.
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.
Cause: The parallel server name ORACLE_PSRV was undefined.
Action: Set the environment variable ORACLE_PSRV, and try again.
Cause: The listener nameserver entry failed to free.
Action: Additional information gives nameserver's returned status. Contact Oracle Support.
Cause: The connection to the nameserver failed to close.
Action: Additional information gives nameserver's returned status. Contact Oracle Support.
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.
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.
Cause: The connection to the nameserver failed to close.
Action: Additional information gives nameserver's returned status. Contact Oracle Support.
Cause: The connection to the nameserver failed to close.
Action: Additional information gives nameserver's returned status. Contact Oracle Support.
Cause: The listener's addressing information failed to be removed.
Action: Additional information gives nameserver's returned status. Contact Oracle Support.
Cause: Archive files failed to be created with the given archival control string.
Action: Verify that the volume exists.
Cause: The given archival control string expands into too many characters.
Action: Reduce archive control string length.
Cause: There is insufficient memory to return the requested value.
Action: Reduce memory usage and retry.
Cause: The requested environment variable is not set.
Action: Ensure that the variable name requested is correct.
Cause: There is no room to record the pid for a background process.
Action: Shutdown abort, and restart the database.
Cause: There is insufficient memory to expand the environment.
Action: Reduce memory usage and retry.
Cause: Failure to retrieve CPU times, because n_stat failed.
Action: Contact Oracle Support.
Cause: Oracle failed to open a file.
Action: Examine the UNIX errno returned for additional information.
Cause: Oracle failed to obtain information about an open file.
Action: Examine the UNIX errno returned for additional information.
Cause: An illegal value for the record size was specified.
Action: Specify a value for the recsize option that is greater than 0.
Cause: An illegal value for the maximum record size was specified.
Action: Specify a value for the maxrecsize option that is greater than 0.
Cause: An unrecognized processing option was specified.
Action: Examine the Oracle for nCUBE 2 User's Guide for valid options.
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.
Cause: An error occurred trying to close a file.
Action: Examine the UNIX errno returned for additional information.
Cause: An error occurred trying to read from a file.
Action: Examine the UNIX errno returned for additional information.
Cause: The lseek system call returned an error.
Action: Examine the UNIX errno returned for additional information.
Cause: The lseek system call returned an error.
Action: Examine the UNIX errno returned for additional information.
Cause: An error occurred trying to read from a file.
Action: Examine the UNIX errno returned for additional information.
Cause: An error occurred trying to read from a file.
Action: Examine the UNIX errno returned for additional information.
Cause: This is an internal error.
Action: Contact Oracle Support.
Cause: This is an internal error.
Action: Contact Oracle Support.
Cause: A call to the lkmgr failed to open and convert the bias lock.
Action: Verify that the lkmgr is up.
Cause: A call to the lkmgr failed to close the bias lock.
Action: Verify that the lkmgr is up.
Cause: An attempt was made to automatically spool a file to the printer.
Cause: The oracle executable timed out waiting for an event.
Action: Contact Oracle Support.
Action: (same as 1545). Also, verify that enough rollback segments have been created for the number of instances you are trying to start.
Cause: An illegal command was executed for the nCUBE platform.
Action: There is no need to issue this command.
Cause: A command that can only be issued on instance 1 was issued elsewhere.
Action: Log on to instance 1 and repeat the command.
Cause: An error occurred trying to connect to the redo server.
Action: The OS specific error message should tell you what to do.
Cause: An error occurred trying to close the redo server connection.
Action: The OS specific error message should tell you what to do.
Cause: An error occurred trying to send redo to the redo server.
Action: The OS specific error message should tell you what to do.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: A closed parenthesis was missing from the picture mask passed to a UTL_PG conversion routine.
Action: Correct the picture mask.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contains invalid decimal data.
Action: Correct the input data.
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.
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.
Cause: The input mask passed to UTL_PG numeric conversion routine contained more the 32 characters.
Action: Correct the mask input buffer.
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.
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.
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.
Cause: Picture mask option is overridden by Picture mask.
Action: No action required. This is an informational message.
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.
The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.
The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.
The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.
Cause: Possibly, there is a shortage of disk space.
Action: Examine the OSD error accompanying this message.
Cause: Block sizes may not match.
Action: Examine the OSD error accompanying this message.
Cause: DB_BLOCK_SIZE specified in init.ora could be incorrect.
Action: Examine the OSD error accompanying this message.
Cause: File attributes may have changed.
Action: Examine the OSD error accompanying this message.
Cause: Incorrect path may have been specified for the file.
Action: Examine the OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: Examine the OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: Examine the OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: Examine the OSD error accompanying this message.
Cause: File may have been corrupted.
Action: Examine the OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: Examine the OSD error accompanying this message.
Cause: Incorrect path may have been specified for the file.
Action: Examine the OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: Examine the OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: Examine the OSD error accompanying this message.
Cause: Filename may be too long.
Action: Examine the OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: Examine the OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: Examine the OSD error accompanying this message.
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.
Cause: Possibly, there is a shortage of disk space.
Action: Examine the OSD error accompanying this message.
Cause: File may be corrupted or truncated.
Action: Examine the OSD error accompanying this message. Memory allocation errors: 9240 - 9259.
Cause: Possibly, there is a shortage of memory.
Action: Examine the OSD error accompanying this message.
Cause: Possibly, there is a shortage of memory.
Action: Examine the OSD error accompanying this message.
Action: Examine the OSD error accompanying this message.
Cause: SGA may not have been created (database not started).
Action: Examine the OSD error accompanying this message.
Action: Examine the OSD error accompanying this message.
Action: Examine the OSD error accompanying this message.
Action: Examine the OSD error accompanying this message.
Action: Examine the OSD error accompanying this message Process control errors: 9260 - 9269.
Cause: Possibly, there is a shortage of resources.
Action: Examine the OSD error accompanying this message.
Cause: Possibly, there is a shortage of resources.
Action: Examine the OSD error accompanying this message.
Cause: Possibly, there is a shortage of resources.
Action: Examine the OSD error accompanying this message.
Cause: Possibly, there is a shortage of memory.
Action: Examine the OSD error accompanying this message.
Cause: Possibly, there is a shortage of resources.
Action: Examine the OSD error accompanying this message.
Cause: Possibly, there is a shortage of resources.
Action: Examine the OSD error accompanying this message.
Cause: Possibly, there is a shortage of memory.
Action: Examine the OSD error accompanying this message Security errors: 9270 - 9279.
Cause: Possibly, there is a shortage of memory.
Action: Examine the OSD error accompanying this message.
Cause: Username may be too long.
Action: Examine the OSD error accompanying this message.
Cause: Remote OS login attempted when not allowed.
Action: Examine the OSD error accompanying this message.
Cause: An OS error was returned when verifying the role name.
Action: Examine the OSD error accompanying this message.
Cause: An OS role name was too long.
Action: Examine the OSD error accompanying this message Direct loader errors: 9280 - 9289.
Action: Examine the OSD error accompanying this message.
Cause: Possibly, incorrect path specified to the file.
Action: Examine the OSD error accompanying this message.
Cause: File could be corrupted.
Action: Examine the OSD error accompanying this message.
Cause: File could be corrupted.
Action: Examine the OSD error accompanying this message. Archiving errors: 9290 - 9299.
Cause: Possibly, there is a shortage of memory.
Action: Examine the OSD error accompanying this message.
Cause: Failure to access directory.
Action: Specify a valid device in ARCHIVE control string.
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.
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.
Cause: Failure to detect the presence of DPMI.
Action: Restart Windows and retry.
Cause: An attempt was made to connect to S: while in enhanced mode.
Action: Restart Windows in standard mode. Miscellaneous errors: 9310 - 9339.
Cause: This is an internal error.
Action: Examine the OSD error accompanying this message.
Cause: Possibly, there is a shortage of resources.
Action: Examine the OSD error accompanying this message.
Cause: Possibly, there is a shortage of resources.
Action: Examine the OSD error accompanying this message.
Cause: Possibly, there is a shortage of resources.
Action: Examine the OSD error accompanying this message.
Cause: Internal buffer may have overflowed.
Action: Examine the OSD error accompanying this message.
Cause: This is an internal error.
Action: Examine the OSD error accompanying this message.
Cause: OS roles may not be supported for this platform.
Action: Examine the OSD error accompanying this message.
Cause: The password specified is invalid.
Action: Examine the OSD error accompanying this message.
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.
Cause: The system time might be set incorrectly.
Action: Examine the OSD error accompanying this message.
Cause: OS roles may not be supported on this platform.
Action: Examine the OSD error accompanying this message.
Cause: This is an internal error.
Action: Examine the OSD error accompanying this message.
Cause: This is an internal error.
Action: Examine the OSD error accompanying this message.
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.
Cause: An invalid lock status was returned by the lock manager, and the locks may no longer be consistent.
Cause: An invalid lock status was returned by the lock manager, and the locks may no longer be consistent.
Cause: An invalid lock status was returned by the lock manager, and the locks may no longer be consistent.
Cause: An invalid lock status was returned by the lock manager, and the locks may no longer be consistent.
Cause: An invalid lock status was returned by the lock manager, and the locks may no longer be consistent.
Cause: ORACLE_SID must be at the most 4 alphanumeric characters.
Cause: Another instance is currently mounting the database.
Cause: The user performed a shutdown abort. Windows 32-bit two-task driver: 9350 - 9359.
Cause: Examine the OSD error accompanying this message.
Cause: Examine the OSD error accompanying this message.
Cause: Examine the OSD error accompanying this message.
Cause: Examine the OSD error accompanying this message.
Cause: Examine the OSD error accompanying this message. Windows 3.1 two-task driver: 9360 - 9379.
Cause: Examine the OSD error accompanying this message.
Cause: Examine the OSD error accompanying this message.
Cause: Examine the OSD error accompanying this message.
Cause: Examine the OSD error accompanying this message.
Cause: Examine the OSD error accompanying this message.
Cause: Examine the OSD error accompanying this message.
Cause: Examine the OSD error accompanying this message.
Cause: Examine the OSD error accompanying this message.
Cause: Examine the OSD error accompanying this message.
Cause: Examine the OSD error accompanying this message.
Cause: Examine the OSD error accompanying this message.
The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.
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.
Cause: PROCESSES init.ora parameter exceeded.
Action: Decrease the PROCESSES parameter and restart.
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.
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.
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.
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.
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.
Cause: The bind system call failed on the socket.
Action: Examine additional information for OS error. Try connecting again.
Cause: The accept system call failed on the socket.
Action: Examine additional information for OS error. Try connecting again.
Cause: The internal buffer is not big enough to hold the message read. This is an internal error.
Action: Contact Oracle Support.
Cause: An existing connection has already been made from log archiver to orasrv.
Action: Stop trying to connect.
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).
Cause: Orasrv cannot obtain the name of the PU. This is possibly an OS error.
Action: Verify that the PUs are named (consistent).
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.
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.
Cause: Malloc() failed to allocate space to hold user interrupt handler.
Action: Possibly, there is a memory resource shortage.
Cause: The handle passed to osncui is out of the valid range.
Cause: The vm_region system call failed to get virtual memory region statistics.
Action: Examine return code in sercerrno. Possible operating system failure.
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].
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].
Cause: The mmap or write system call returned an error. This is an internal error.
Action: Contact Oracle Support.
Cause: The mmap system call returned an error. This is an internal error.
Action: Contact Oracle Support.
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.
Cause: The vm_allocate system call attached the SGA at an incorrect location.
Action: Verify that the SGA attach address is valid.
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.
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.
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.
Cause: The port_rename system call failed. This is possibly an internal error.
Action: Examine return code in sercerrno. Contact Oracle Support.
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.
Cause: The port_allocate system call failed. This is possibly due to resource exhaustion.
Action: Examine return code in sercerrno. Contact Oracle Support.
Cause: Function was passed an invalid oracle process ID. This is an internal error.
Action: Additional information indicates the invalid process ID.
Cause: Function was passed an invalid oracle process ID. This is an internal error.
Action: Contact Oracle Support.
Cause: The port_allocate system call failed. This is possibly due to a system resource shortage.
Action: Examine the error code in sercerrno.
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.
Cause: The port_allocate system call failed. This is possibly due to a system resource shortage.
Action: Examine the error code in sercerrno.
Cause: The netname_check_in call failed.
Action: Examine the error code in sercerrno. Verify that the network name server is running.
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.
Cause: The pipe driver failed to send a break message to the oracle shadow process break thread.
Action: Contact Oracle Support.
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.
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.
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.
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.
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.
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.
Cause: The msg_send system call failed while flushing the mach driver's send buffer. This is an internal error.
Action: Contact Oracle Support.
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.
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.
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.
Cause: The msg_send system call failed while sending a mach driver break. This is an internal error.
Action: Contact Oracle Support.
Cause: The mach driver received a message having an unrecognizable message type. This is an internal error.
Action: Contact Oracle Support.
Cause: The mach driver received a message having an unrecognizable message type. This is an internal error.
Action: Contact Oracle Support.
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.
Cause: The mach two-task driver failed to reset the connection. This is an internal error.
Action: Contact Oracle Support.
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.
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.
Cause: The routine failed to allocate or set the task's notify port.
Action: Possible operating system error. Contact Oracle Support.
Cause: The port_allocate system call failed; system resources might be exhausted. This is possibly an operating system error.
Action: Contact Oracle Support.
Cause: Open system call returned an error.
Cause: Processing option passed is of incorrect format.
Action: Consult IUG for permissible formats.
Cause: Read system call returned an error.
Action: Examine errno. Verify that file exists.
Cause: Read system call returned an error.
Action: Examine errno. Verify that file exists.
Cause: Close system call returned an error.
Cause: Additional information indicates error returned from sltln.
Action: Examine additional information.
Cause: Malloc system call returned an error. The system might have run out of heap space.
Action: Examine additional information for the OS error.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: The oracle executable failed to convert the string representation of a label to binary format.
Action: Re-enter a valid label.
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.
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.
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.
Cause: The oracle executable failed to initialize the library used to obtain security information. This is an internal error.
Action: Contact Oracle Support.
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.
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.
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.
Cause: The buffer that oracle uses to hold the expanded name of a too small.
Action: Contact Oracle Support.
Cause: This is an internal error.
Action: Contact Oracle Support.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: System call atomic_op() return error.
Action: Examine additional information in the trace file.
Cause: System call atomic_op() return unexpected error.
Action: Examine additional information in the trace file.
Cause: System call atomic_op() return unexpected error.
Action: Examine additional information in the trace file.
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.
Cause: The msg_rpc system call returned an error. This is an internal error.
Action: Contact Oracle Support.
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.
Cause: The routine received an incorrectly formatted request. This is an internal error.
Action: Contact Oracle Support.
Cause: The routine received an incorrectly formatted request. This is an internal error.
Action: Contact Oracle Support.
Cause: The port_status system called failed. This is possibly an operating system error.
Action: Contact Oracle Support.
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.
Cause: The port_set_add system called failed. This is possibly an operating system error.
Action: Contact Oracle Support.
Cause: The malloc library call failed to allocate space for a callback link. This is possibly an operating system error.
Action: Contact Oracle Support.
Cause: The port port_set_remove system call failed. This is possibly an operating system error.
Action: Contact Oracle Support.
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.
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.
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.
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.
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.
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.
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.
Cause: The routine received an incorrectly formatted request. This is an internal error.
Action: Contact Oracle Support.
Cause: The vm_allocate system call returned an error. Possibly, there is a shortage of system resources.
Cause: The vm_protect system call returned an error. This is an internal error.
Action: Contact Oracle Support.
Cause: ulimit system call returned an error.
Cause: Failure of sltln($ORACLE_HOME/tasdefsid.dbf) while creating test and set pages.
Action: Examine additional return error for more information.
Cause: Create() failed when trying to create the tasdef file.
Action: Verify permissions on $(ORACLE_HOME)/dbs directory.
Cause: Failure to open tasdefsid.dbf file. This is possibly a permission problem.
Action: Examine errno. Verify that tasdefsid.dbf file exists.
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.
Cause: Write call failed. Possibly, there is a shortage of space on device.
Cause: Close system call returned an error. Possibly this is an operating system failure.
Action: Examine errno. Verify that enough shared memory is available on the system.
Action: Examine errno.Verify that enough shared memory is available on the system.
Action: Examine errno.Verify that enough shared memory is available on the system.
Cause: The oratab file does not exist.
Action: Install Oracle before using it, or recreate the oratab file.
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.
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.
Cause: Failure of sltln(txipcsid.trc) while creating debug channel.
Action: Examine additional return error for more information.
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.
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.
Cause: The txipx driver failed to allocate enough heap space for its context area buffers.
Action: Contact Oracle Support.
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.
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.
Cause: No entry exists for the user in the oracle password file.
Action: Have the database administrator install a password entry by running orapasswd.
Cause: The password entered by the user was incorrect.
Action: Enter the correct password.
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.
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.
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.
Cause: The oracle executable failed to encrypt a password. This is an internal error.
Action: Contact Oracle Support.
Cause: A user attempted to connect as "internal", but did not specify a password.
Action: Connect as internal again and specify a password.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: An attempt to close a password file failed.
Action: Examine the UNIX error number for the specific reason.
Cause: The removal of the old password file failed.
Action: Examine the UNIX error number for the specific reason.
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.
Cause: The oracle executable failed to complete the saving of the current password file.
Action: Examine the UNIX error number for the specific reason.
Cause: The oracle executable failed to create a password file.
Action: Examine the UNIX error number for the specific reason.
Cause: The oracle executable failed to change a password file to be read only.
Action: Examine the UNIX error number for the specific reason.
Cause: The oracle executable failed to save the previous values of selected signal handlers. This is an internal error.
Action: Contact Oracle Support.
Cause: The oracle executable failed to restore the previous values of selected signal handlers. This is an internal error.
Action: Contact Oracle Support.
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".
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.
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.
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.
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."
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.
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.
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.
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.
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.
Cause: The oracle executable failed to get its privileges from the operating system.
Action: Contact Oracle Support.
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.
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.
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.
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.
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.
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.
Cause: The attempt to send a termination signal to IMON failed. This is an internal error.
Action: Contact Oracle Support.
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.
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.
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.
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.
Cause: Failure of sltln in scumnt.
Action: Examine additional return error for more information.
Cause: Open system call returned an error.
Cause: Lock file operating system call returned an error.
Cause: The process failed to initialize the SDI channel properly.
Action: Correct the operating system error and retry the operation.
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.
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.
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.
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.
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.
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.
Cause: The process failed to add a page to the SDI buffer pool.
Action: Correct the operating system error and retry the operation.
Cause: The process failed to remove a page to the SDI buffer pool.
Action: Correct the operating system error and retry the operation.
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.
Cause: File does not exist or is not accessible.
Action: Restart the instance to create the SGA definition file.
Cause: Read() operation failed.
Action: Examine errno, and take appropriate action.
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.
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.
Cause: skgmsdef struct is corrupted and/or segment addresses are modified.
Action: Safely shut down instance and mount SGA segments again.
Cause: Pointer to skgmsdef struct used without validating it.
Action: Assign a valid address to the skgmsdef struct pointer before using it.
This range is for internal error messages which should not normally occur. Internal messages are not documented in this manual.
The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.
This section lists messages generated when table snapshots are accessed.
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.
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.
Cause: An attempt was made to drop a snapshot that does not exist.
Action: Check spelling, syntax, and use an existing snapshot name.
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.
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.
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.
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.
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.
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.
Cause: An attempt was made to create a snapshot with a long column.
Action: Do not attempt to create snapshot logs with long columns.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: Attempt to unregister a snapshot that is not registered.
Action: Nothing needs to be done.
Cause: The snapshot indicated is no longer valid.
Action: Contact your customer support representative.
Cause: Snapshot log on the indicated table already has ROWID information.
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.
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.
Cause: Snapshot log on the indicated table already has primary key columns.
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.
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.
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.
Cause: LOB columns may not be used as filter columns.
Action: Remove LOB columns from the filter columns list and retry the command.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
|
 Copyright © 1997 Oracle Corporation. All Rights Reserved. |
|
