I summarized a list of (ORA) oracle error codes list with cause and
action, use browser find (CTRL+F) to get your desire error code, cause and
possible action.
Her are the complete list of ORA error codes link
ORA-06501: PL/SQL: program error
Cause: This is an internal error
message. An error has been detected in a PL/SQL program.
Action: Contact Oracle Support
Services.
ORA-06502: PL/SQL: numeric or value errorstring
Cause: An arithmetic, numeric,
string, conversion, or constraint error occurred. For example, this error
occurs if an attempt is made to assign the value NULL to a variable declared
NOT NULL, or if an attempt is made to assign an integer larger than 99 to a
variable declared NUMBER(2).
Action: Change the data, how it is
manipulated, or how it is declared so that values do not violate constraints.
ORA-06503: PL/SQL: Function returned without value
Cause: A call to PL/SQL function
completed, but no RETURN statement was executed.
Action: Rewrite PL/SQL function,
making sure that it always returns a value of a proper type.
ORA-06504: PL/SQL: Return types of Result Set variables or query
do not match
Cause: Number and/or types of columns
in a query does not match declared return type of a result set variable, or
declared types of two Result Set variables do not match.
Action: Change the program statement
or declaration. Verify what query the variable actually refers to during
execution.
ORA-06505: PL/SQL: variable requires more than 32767 bytes of
contiguous memory
Cause: A PL/SQL variable was declared
with a constraint which required more than 32767 bytes of memory. PL/SQL does
not currently support allocations of contiguous memory greater than 32767
bytes.
Action: Consider reducing the
constraint in the variable declaration. If that is not possible, try changing
the database or national character set to such, that requires less memory for
the same constraint. Note: changing the character set will impact execution of
all PL/SQL code.
ORA-06510: PL/SQL: unhandled user-defined exception
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. Or you may need to
contact your application administrator or DBA.
ORA-06511: PL/SQL: cursor already open
Cause: An attempt was made to open a
cursor that was already open.
Action: Close cursor first before
reopening.
ORA-06512: at stringline string
Cause: Backtrace message as the stack
is unwound by unhandled exceptions.
Action: Fix the problem causing the
exception or write an exception handler for this condition. Or you may need to
contact your application administrator or DBA.
ORA-06513: PL/SQL: index for PL/SQL table out of range for host
language array
Cause: An attempt is being 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, etc. If an table entry has not been
assigned then the corresponding element in the host language array is set to
null.
Action: Increase size of host language
array, or decrease size of PL/SQL table. Also make sure that you don't use
index values less than 1.
ORA-06514: PL/SQL: The remote call cannot be handled by the
server
Cause: The remote call has parameters
that are cursor variables or lob variables. This cannot be handled by stored
procedures on your server.
Action: Avoid using cursor variables
or lob variables as parameters for stored procedures on this server or upgrade
your server to a version that supports this.
ORA-06515: PL/SQL: unhandled exception string
Cause: An exception was raised by
PL/SQL code, but not handled. The exception number is outside the legal range
of Oracle errors.
Action: Fix the problem causing the
exception or write an exception handler for this condition. Or you may need to
contact your application administrator or DBA.
ORA-06516: PL/SQL: the Probe packages do not exist or are
invalid
Cause: A Probe operation, probably an
attempt to initialize the ORACLE server to debug PL/SQL, could not be completed
because the Probe packages were not loaded or have become invalid.
Action: DBA should load the Probe
packages. This can be done by running the pbload.sql script supplied with the
RDBMS.
ORA-06517: PL/SQL: Probe error - string
Cause: An error occurred while
passing a Probe operation to the server for execution.
Action: Refer to the entry for the
embedded error message.
ORA-06518: PL/SQL: Probe version string incompatible
with version string
Cause: The current version of Probe
is incompatible with the version on the ORACLE server.
Action: Refer to the documentation to
ensure that this degree of compatibility is supported.
ORA-06519: active autonomous transaction detected and rolled
back
Cause: Before returning from an
autonomous PL/SQL block, all autonomous transactions started within the block
must be completed (either committed or rolled back). If not, the active
autonomous transaction is implicitly rolled back and this error is raised.
Action: Ensure that before returning
from an autonomous PL/SQL block, any active autonomous transactions are
explicitly committed or rolled back.
----------------------------------------------------------------------- 06520
through 06529 reserved for Foreign function errors
ORA-06520: PL/SQL: Error loading external library
Cause: An error was detected by
PL/SQL trying to load the external library dynamically.
Action: Check the stacked error (if
any) for more details.
ORA-06521: PL/SQL: Error mapping function
Cause: An error was detected by
PL/SQL trying to map the mentioned function dynamically.
Action: Check the stacked error (if
any) for more details.
ORA-06522: string
Cause: or could stack this error
with a system specific error string.
Action: This error string should give
the cause for errors or
ORA-06523: Maximum number of arguments exceeded
Cause: There is an upper limit on the
number of arguments that one can pass to the external function.
Action: Check the port specific
documentation on how to calculate the upper limit.
ORA-06524: Unsupported option : string
Cause: The option specified is an
unsupported feature for external procedures.
Action: Correct the syntax in the
external specification
ORA-06525: Length Mismatch for CHAR or RAW data
Cause: The length specified in the
length variable has an illegal value. This can happen if you have requested
requested a PL/SQL INOUT, OUT or RETURN raw variable to be passed as a RAW with
no corresponding length variable. This error can also happen if there is a
mismatch in the length value set in the length variable and the length in the
orlvstr or orlraw.
Action: Correct the external procedure
code and set the length variable correctly.
ORA-06526: Unable to load PL/SQL library
Cause: PL/SQL was unable to
instantiate the library referenced by this referenced in the EXTERNAL syntax.
This is a serious error and should normally not happen.
Action: Report this problem to
customer support.
ORA-06527: External procedure SQLLIB error: string
Cause: An error occurred in sqllib
during execution of a Pro* external procedure.
Action: The message text indicates the
actual SQLLIB error that occurred. Consult the Oracle Error Messages and Codes
manual for a complete description of the error message and follow the
appropriate action.
ORA-06528: Error executing PL/SQL profiler
Cause: An error occurred in during
execution of a PL/SQL profiler procedure.
Action: Check the stacked errors for
more details.
ORA-06529: Version mismatch - PL/SQL profiler
Cause: The PL/SQL profiler package
(dbmspb.sql, prvtpbp.plb) does not match the version of the code in the server
implementing the profiler.
Action: Run the package profload.sql
in $ORACLE_HOME/rdbms/admin to load the correct version of the PL/SQL profiler
packages
ORA-06530: Reference to uninitialized composite
Cause: An object, LOB, or other
composite was referenced as a left hand side without having been initialized.
Action: Initialize the composite with
an appropriate constructor or whole-object assignment.
ORA-06531: Reference to uninitialized collection
Cause: An element or member function
of a nested table or varray was referenced (where an initialized collection is
needed) without the collection having been initialized.
Action: Initialize the collection with
an appropriate constructor or whole-object assignment.
ORA-06532: Subscript outside of limit
Cause: A subscript was greater than
the limit of a varray or non-positive for a varray or nested table.
Action: Check the program logic and
increase the varray limit if necessary.
ORA-06533: Subscript beyond count
Cause: An in-limit subscript was
greater than the count of a varray or too large for a nested table.
Action: Check the program logic and
explicitly extend if necessary.
ORA-06534: Cannot access Serially Reusable package string
Cause: The program attempted to
access a Serially Reusable package in PL/SQL called from SQL context (trigger
or otherwise). 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 in PL/SQL called from sql context
(trigger or otherwise).
ORA-06535: statement string in string is NULL
or 0 length
Cause: The program attempted to use a
dynamic statement string that was either NULL or 0 length.
Action: Check the program logic and
ensure that the dynamic statement string is properly initialized.
ORA-06536: IN bind variable bound to an OUT position
Cause: The program attempted to bind
an IN bind variable to a statement that was expecting an OUT bind variable at
that position.
Action: Make sure that an OUT or IN
OUT bind mode is specified for the bind argument.
ORA-06537: OUT bind variable bound to an IN position
Cause: The program attempted to bind
an OUT bind variable to a statement that was expecting an IN bind variable at
that position.
Action: Make sure that an IN or IN OUT
bind mode is specified for the bind argument.
ORA-06538: statement violates string RESTRICT_REFERENCES
pragma
Cause: The program attempted to
execute a dynamic statement which does not meet the purity level specified (in
the pragma RESTRICT_REFERENCES directive) for the module executing the
statement.
Action: Ensure that the dynamic
statement meets the purity level specified for the module executing the
statement.
ORA-06539: target of OPEN must be a query
Cause: The program attempted to
perform an OPEN cursor operation on a dynamic statement that was not a query.
Action: Ensure that the OPEN cursor
operation is done on a dynamic query statement.
-------------------------------------------------------- 06540 through 06549
reserved for pl/sql error handling
ORA-06540: PL/SQL: compilation error
Cause: A pl/sql compilation error
occurred. However, the user generally will not see this error message. Instead,
there will be accompanying PLS-nnnnn error messages.
Action: See accompanying PLS-nnnnn
error messages.
ORA-06541: PL/SQL: compilation error - compilation aborted
Cause: A pl/sql compilation error
occurred and the compilation was aborted; but the compilation unit was written
out to the backing store. However, unlike , the user generally will not
see this error message. Instead, there will be accompanying PLS-nnnnn error
messages.
Action: See accompanying PLS-nnnnn
error messages.
ORA-06544: PL/SQL: internal error, arguments: [string], [string],
[string], [string], [string], [string], [string],
[string]
Cause: A pl/sql internal error
occurred.
Action: Report as a bug; the first
argument is the internal error nuber.
ORA-06545: PL/SQL: compilation error - compilation aborted
Cause: A pl/sql compilation error
occurred and the compilation was aborted completely without the compilation
unit being written out to the backing store. Unlike , the user will always
see this error along with the accompaning PLS-nnnnn error messages.
Action: See accompanying PLS-nnnnn
error messages.
ORA-06546: DDL statement is executed in an illegal context
Cause: DDL statement is executed
dynamically in illegal PL/SQL context.
- Dynamic OPEN cursor for a DDL in PL/SQL
- Bind variable's used in USING clause to EXECUTE
IMMEDIATE a DDL
- Define variable's used in INTO clause to EXECUTE
IMMEDIATE a DDL
Action: Use EXECUTE IMMEDIATE without
USING and INTO clauses to execute the DDL statement.
ORA-06547: RETURNING clause must be used with INSERT, UPDATE, or
DELETE statements
Cause: EXECUTE IMMEDIATE with a
RETURNING clause is used to execute dynamic UPDATE, INSERT, or DELETE
statements only.
Action: use RETURNING clause in
EXECUTE IMMEDIATE for INSERT, UPDATE, or DELETE statements only. For other
statements, use USING clause instead.
ORA-06548: no more rows needed
Cause: The caller of a pipelined
function does not need more rows to be produced by the pipelined function.
Action: Catch the NO_DATA_NEEDED exception
is an exception handling block.
ORA-06549: PL/SQL: failed to dynamically open shared object
(DLL): string:string
Cause: One possible cause might be
there are too many DLLs open at the same time.
Action: --------------------------------------------------------
ORA-06550: line string, column string: string
Cause: Usually a PL/SQL compilation
error.
Action: None
ORA-06554: package DBMS_STANDARD must be created before using
PL/SQL
Cause: The DBMS specific extensions
to PL/SQL's package "STANDARD" are in package
"DBMS_STANDARD". This package must be created before using PL/SQL.
Action: Create package
"DBMS_STANDARD". The source for this PL/SQL stored package is
provided with the distribution.
ORA-06555: this name is currently reserved for use by user SYS
Cause: You tried to create a package
named "STANDARD", "DBMS_STANDARD" or "DEBUG_IO".
These are currently reserved for use by user SYS.
Action: Choose another name for your
package.
ORA-06556: the pipe is empty, cannot fulfill the unpack_message
request
Cause: There are no more items in the
pipe.
Action: Check that the sender and
receiver agree on the number and types of items placed on the pipe.
ORA-06557: null values are not allowed for any parameters to
pipe icd's
Cause: Internal error from the dbms_pipe
package.
Action: None
ORA-06558: buffer in dbms_pipe package is full. No more items
allowed
Cause: The pipe buffer size has been
exceeded.
Action: None
ORA-06559: wrong datatype requested, string, actual
datatype is string
Cause: The sender put different
datatype on the pipe than that being requested (package 'dbms_pipe'). The
numbers are: 6 - number, 9 - char, 12 - date.
Action: Check that the sender and
receiver agree on the number and types of items placed on the pipe.
ORA-06560: pos, string, is negative or larger than
the buffer size, string
Cause: Internal error from the
dbms_pipe package.
Action: None
ORA-06561: given statement is not supported by package DBMS_SQL
Cause: Attempting to parse an
unsupported statement using procedure PARSE provided by package DBMS_SQL.
Action: Only statements which begin
with SELECT, DELETE, INSERT, UPDATE, LOCK, BEGIN, DECLARE or << (PL/SQL
label delimiter) are supported.
ORA-06562: type of out argument must match type of column or
bind variable
Cause: Attempting to get the value of
a column or a bind variable by calling procedure COLUMN_VALUE or VARIABLE_VALUE
of package DBMS_SQL but the type of the given out argument where to place the
value is different from the type of the column or bind variable that was previously
defined by calling procedure DEFINE_COLUMN (for defining a column) or
BIND_VARIABLE (for binding a bind variable) of package DBMS_SQL.
Action: Pass in an out argument of the
correct type when calling procedure COLUMN_VALUE or VARIABLE_VALUE. The right
type is the type that was provided when defining the column or binding the bind
variable.
ORA-06563: top level procedure/function specified, cannot have
subparts
Cause: The name to be resolved was
specified with three parts (a.b.c) but the a.b part resolves to a top level
procedure or function (which don't have nested procedures). This can also
happen with a two-part name, a.b, where a is a synonym for a top level package
or procedure.
Action: Specify a procedure/function
within a package, or a top level procedure/function.
ORA-06564: object string does not exist
Cause: The named object could not be
found. Either it does not exist or you do not have permission to access it.
Action: Create the object or get
permission to access it.
ORA-06565: cannot execute string from within
stored procedure
Cause: The named procedure cannot be
executed from within a stored procedure, function or package. This function can
only be used from pl/sql anonymous blocks.
Action: Remove the procedure from the
calling stored procedure.
ORA-06566: invalid number of rows specified
Cause: An invalid number of rows was
specified in a call to the procedure 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
that for previously defined columns.
ORA-06567: invalid number of values specified
Cause: An invalid number of values to
be bound was specified in a call to the procedure BIND_VARIABLE in the package
DBMS_SQL. In order to execute a given parsed statement in a given cursor, the
same number of values must have been bound for all bind variables, so when
EXECUTE is called, the latest calls to BIND_VARIABLE must must have specified
the same number of values to be bound for all bind variables.
Action: Make sure that the same number
of values have been bound for all of the bind variables.
ORA-06568: obsolete ICD procedure called
Cause: An obsolete ICD procedure was
called by a PL/SQL program. The PL/SQL program was probably written for an
eralier release of RDBMS.
Action: Make sure that all PL/SQL
programs have been upgraded to the latest release of the RDBMS. This can be
accomplished by following upgrade instructions in the README file, or by
running the catproc.sql script supplied with the RDBMS.
ORA-06569: Collection bound by bind_array contains no elements
Cause: A collection with zero
elements was bound to a bind variable in a call to procedure BIND_ARRAY in the
package DBMS_SQL. In order to execute a bind of a collection, the collection
must contain at least one element. If no elements are present then at execute
time there will be no value for this bind and the statement is meaningless.
Action: Fill the collection with the
elements you want to bind and try the bind call again.
ORA-06570: shared pool object does not exist, cannot be
pinned/purged
Cause: The specified shared pool
shared cursor could not be found, therefore it cannot be pinned/purged.
Action: Remove the procedure from the
calling stored procedure.
ORA-06571: Function string does not guarantee
not to update database
Cause: There are two possible causes
for this message:
* A SQL statement references a packaged, PL/SQL function
that does not contain a pragma that prevents the database from being updated.
* A SQL statement references a stand-alone, PL/SQL
function that contains an instruction to update the database.
Action: If the referenced function is
a packaged, PL/SQL function: Recreate the PL/SQL function with the required
pragma; be certain to include the 'Write No Database State' (WNDS) argument in
the argument list of the pragma. If the referenced function is a stand-alone,
PL/SQL function: Do not use the function.
ORA-06572: Function string has out arguments
Cause: A SQL statement references
either a packaged, or a stand-alone, PL/SQL function that contains an OUT
parameter in its argument list. PL/SQL functions referenced by SQL statements
must not contain the OUT parameter.
Action: Recreate the PL/SQL function
without the OUT parameter in the argument list.
ORA-06573: Function string modifies package
state, cannot be used here
Cause: There are two possible causes
for this message:
* A SQL statement references a packaged, PL/SQL function
that does not contain a pragma containing the 'Write no Package State' (WNPS).
* A SQL statement references a stand-alone, PL/SQL
function that modifies a package state. A stand-alone, PL/SQL function
referenced by a SQL statement cannot modify a package state.
Action: If the function is a packaged,
PL/SQL function: Recreate the function and include a pragma containing the
'Write no Package State' (WNPS). If the function is a stand-alone, PL/SQL
function: Delete the function from the SQL statement.
ORA-06574: Function string references package
state, cannot execute remotely
Cause: There are two possible causes
for this message:
* A remote, packaged function or a remote-mapped, local,
packaged function that does not contain a pragma with the 'Write no Package
State' (WNPS) and 'Read no Package State' (RNPS) arguments references a package
state.
* A remote, stand-alone function or a remote-mapped,
local, stand-alone function contains a reference to a package state (reads or
writes a package variable). Only local functions that are referenced in a
SELECT list, VALUES clause of an INSERT statement, or SET clause of an UPDATE
statement can modify a package state.
Action: If the function is a packaged
function: Recreate the function and include a pragma containing the 'Write no
Package State' (WNPS) and 'Read no Package State' (RNPS) arguments. If the
function is a stand-alone function: Do not call the function.
ORA-06575: Package or function string is in an
invalid state
Cause: A SQL statement references a
PL/SQL function that is in an invalid state. Oracle attempted to compile the
function, but detected errors.
Action: Check the SQL statement and
the PL/SQL function for syntax errors or incorrectly assigned, or missing,
privileges for a referenced object.
ORA-06576: not a valid function or procedure name
Cause: Could not find a function (if
an INTO clause was present) or a procedure (if the statement did not have an
INTO clause) to call.
Action: Change the statement to invoke
a function or procedure
ORA-06577: output parameter not a bind variable
Cause: The argument corresponding to
an IN/OUT or OUT parameter for a function or a procedure or a function return
value in a CALL statement must be a bind variable.
Action: Change the argument to a bind
variable
ORA-06578: output parameter cannot be a duplicate bind
Cause: The bind variable
corresponding to an IN/OUT or OUT parameter for a function or a procedure or a
function return value in a CALL statement cannot be a duplicate bind variable.
Action: Change the bind variable to be
unique
ORA-06579: Bind variable not big enough to hold the output value
Cause: The bind variable specified by
the user is not large enough to hold the output returned by the function or a
procedure.
Action: Specify a bind variable of
larger size.
ORA-06580: Hash Join ran out of memory while keeping large rows
in memory
Cause: Hash Join reserves 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 increaed.
ORA-06592: CASE not found while executing CASE statement
Cause: A CASE statement must either
list all possible cases or have an else clause.
Action: Add all missing cases or an
else clause.
ORA-06593: string is not supported with
natively compiled PL/SQL modules
Cause: Specified feature is not yet
supported for natively compiled PL/SQL modules yet.
Action: Recompile the relevant PL/SQL
modules in non-native mode by setting the parameter plsql_compiler_flags to
INTERPRETED.
ORA-06595: REF CURSOR parameters are not supported in forwarded
RPC calls
Cause: An attempt was made to make a
forwarded RPC call with a REF CURSOR parameter.
Action: Either call the remote
function directly (i.e., not by way of forwarding), or move the remote function
to a database where it can be called directly.
ORA-06596: object cannot be purged, object is permanently kept
in shared pool
Cause: The specified object was
permanently kept, therefore, cannot be purged.
Action: Use DBMS_SHARED_POOL.UNKEEP
procedure to unkeep the object and then purge it.
ORA-06600: LU6.2 Driver: SNA software is not loaded
Cause: The SNA software is not running.
Action: Start the SNA software and try
again.
ORA-06601: LU6.2 Driver: Invalid database ID string
Cause: The database string in the
connect was invalid.
Action: Provide a valid database
string, as defined in documentation.
ORA-06602: LU6.2 Driver: Error allocating context area
Cause: Context area failure.
Action: Contact your local service
representative.
ORA-06603: LU6.2 Driver: Error allocating memory
Cause: Operating system refused
request for memory.
Action: Contact you local service
representative.
ORA-06604: LU6.2 Driver: Unable to allocate session with remote
LU
Cause: Allocate system call failed.
Action: Ensure that the SNA software
is running and that sessions are free. If this is the case, then check your SNA
configuration data for errors. You may have entered an incorrect parameter.
ORA-06605: LU6.2 Driver: Unexpected line turnaround
Cause: SNA software switched from
send to receive unexpectedly.
Action: Check the SNA configuration
data, particularly parameters associated with a session.
ORA-06606: LU6.2 Driver: Unexpected response from SNA
Cause: A parameter in an SNA call
returned an unexpected value.
Action: Attempt to reproduce problem,
debug and record the value of the 'what' data parameter at the time of error.
Then contact your service representative.
ORA-06607: LU6.2 Driver: Reset occurred in send state
Cause: A reset was issued whilst in
send state.
Action: Check the SNA LOG data, if
relevent, for further information.
ORA-06608: LU6.2 Driver: Reset occurred in receive state
Cause: A reset was received from the
partner whilst in receive state. This may be because the partner deallocated.
Action: Check the SNA LOG data, if
relevent, for further information.
ORA-06610: LU6.2 Driver: Failed during deallocation
Cause: LU6.2 driver was unable to
deallocate gracefully.
Action: Check the reason for
deallocation. Consult the SNA LOG data.
ORA-06616: LU6.2 Driver: Attach to LU failed
Cause: The SQL*Net LU6.2 driver was
unable to attach to the LU specified in the connect string, or was unable to
attach to the default LU.
Action: Check that the LU name
specified in the connect string, or the default LU name if no LU was specified,
is correctly configured and operational.
ORA-06622: LU6.2 Driver: Unable to attach to SNA
Cause: The SQL*Net LU6.2 driver could
not attach to the SNA software on your machine. The most likely cause is that
the SNA software is not operational.
Action: Check the status of the SNA
software, ensure that it is operational and then try again.
ORA-06700: TLI Driver: incorrect message type from host
Cause: TLI received a message with an
unrecognizable message type.
Action: Contact your customer support
representative.
ORA-06701: TLI Driver: incorrect number of bytes written
Cause: TLI sent a message that was
apparently successful, but the number of bytes transmitted did not match the
number of bytes supplied to the driver.
Action: Contact your customer support
representative.
ORA-06702: TLI Driver: cannot allocate context area
Cause: TLI could not allocate heap
space for the context area.
Action: Contact your customer support
representative.
ORA-06703: TLI Driver: send break message failed
Cause: TLI failed to send a break
message across the connection.
Action: Contact your customer support
representative.
ORA-06704: TLI Driver: receive break message failed
Cause: TLI failed to receive an
expected break message.
Action: Contact your customer support
representative.
ORA-06705: TLI Driver: remote node is unknown
Cause: TLI could not find your remote
host information.
Action: Make sure you specified the
hostname correctly on the command line. (Also, check your capitalization and
spelling.)
ORA-06706: TLI Driver: service not found
Cause: TLI could not find service
information for the specified service name.
Action: If you specified the service
name on the command line or with the environment variable TLI_SERVER, make sure
you specified it correctly. If the service name is not in the SERVICES file for
your protocol, ask your system adminstrator to add it.
ORA-06707: TLI Driver: connection failed
Cause: TLI failed to establish the
connection to a SQL*Net TCP/IP server due to an error encountered by the remote
server, which has supplied a string describing the remote error.
Action: See the SQL*Net TCP/IP User's
Guide section "orasrv Messages" for the specific cause and action.
ORA-06708: TLI Driver: message receive failure
Cause: TLI encountered an error
receiving a message from the communication channel.
Action: Contact your customer support
representative.
ORA-06709: TLI Driver: message send failure
Cause: TLI encountered an error
sending a message across the communication channel.
Action: Contact your customer support
representative.
ORA-06710: TLI Driver: send interrupt break message failed
Cause: TLI failed to send a break
message while handling an interrupt signal from the user.
Action: Contact your customer support
representative.
ORA-06711: TLI Driver: error on bind
Cause: TLI failed to assign a network
address to the communication channel.
Action: Contact your customer support
representative.
ORA-06712: TLI Driver: error on accept
Cause: TLI failed to accept a
connection request from the client.
Action: Contact your customer support
representative.
ORA-06713: TLI Driver: error on connect
Cause: TLI failed to connect the
client to the remote server. The network line to the remote host may be down.
Action: Use other network login
programs to make sure that the remote host is accessible.
ORA-06720: TLI Driver: SID lookup failure
Cause: The database SID supplied in
the database login string was not recognized by the remote host.
Action: Ask your system administrator
to add the appropriate SID entry to oratab on the remote host.
ORA-06721: TLI Driver: spurious client req
Cause: The remote TLI server received
an undefined request.
Action: Contact your customer support
representative.
ORA-06722: TLI Driver: connection setup failure
Cause: The remote TLI server rejected
the connection request, and the client was unable to retrieve an error code or
message.
Action: Contact your customer support
representative.
ORA-06730: TLI Driver: unable to open clone device
Cause: TLI failed to open the Streams
clone device associated with the transport provider.
Action: Contact your customer support
representative.
ORA-06731: TLI Driver: cannot alloc t_call
Cause: TLI cannot allocate space for
the client's connection information.
Action: Contact your customer support
representative.
ORA-06732: TLI Driver: cannot alloc t_discon
Cause: TLI cannot allocate space for
the client's disconnection information.
Action: Contact your customer support
representative.
ORA-06733: TLI Driver: failed to receive disconnect
Cause: TLI failed to receive an
expected disconnection message during connection release.
Action: Contact your customer support
representative.
ORA-06734: TLI Driver: cannot connect
Cause: TLI failed to connect the
client to the remote server.
Action: Check that the remote TLI
server is running.
ORA-06735: TLI Driver: client failed to close error conn
Cause: TLI failed to properly close a
connection after an error was received.
Action: Contact your customer support
representative.
ORA-06736: TLI Driver: server not running
Cause: TLI timed out while attempting
to connect to the remote TLI server.
Action: Check that the remote TLI server
is running with the status utility for the transport provider you are using. If
it is not, ask your system adminstrator to start it.
ORA-06737: TLI Driver: connection failed
Cause: TLI could not establish a
connection to the remote TLI server.
Action: Check that the remote TLI
server is running with the status utility for the transport provider you are
using.
ORA-06741: TLI Driver: unable to open protocol device
Cause: The TLI server failed to open
the Streams device associated with the transport provider.
Action: Contact your customer support
representative.
ORA-06742: TLI Driver: cannot alloc t_bind
Cause: The TLI server cannot allocate
space for its requested network address.
Action: Contact your customer support
representative.
ORA-06743: TLI Driver: cannot alloc t_bind
Cause: The TLI server cannot allocate
space for its actual network address.
Action: Contact your customer support
representative.
ORA-06744: TLI Driver: listener cannot bind
Cause: The TLI server failed to
assign the correct network address on which to listen for connections.
Action: Contact your customer support
representative.
ORA-06745: TLI Driver: listener already running
Cause: The network address on which
the TLI server awaits connection requests is in use, possibly because the
server is already running.
Action: Ensure that the TLI server is
not already running. If it is not running and this error message recurs,
contact your customer support representative.
ORA-06746: TLI Driver: cannot alloc t_call
Cause: TLI cannot allocate space for
the TLI server's connection information.
Action: Contact your customer support
representative.
ORA-06747: TLI Driver: error in listen
Cause: The TLI server encountered an
error while listening for connection requests.
Action: Contact your customer support
representative.
ORA-06748: TLI Driver: cannot allocate t_discon
Cause: TLI cannot allocate space for
the TLI server's disconnection information.
Action: Contact your customer support
representative.
ORA-06749: TLI Driver: option not allowed across network
Cause: The requested TLI server
command must be issued from the same host on which the server is running.
Action: Log in to the remote host and
try again.
ORA-06750: TLI Driver: sync failed
Cause: The ORACLE process started by
the TLI server was unable to synchronize its inherited connection.
Action: Contact your customer support
representative.
ORA-06751: TLI Driver: bound addresses unequal
Cause: The osn check server address
failed. The bound server address was not the same as the requested binding
address.
Action: Contact your customer support
representative.
ORA-06752: TLI: error in signal setup
Cause: A call to sigaction() returned
with a system error.
Action: Contact your customer support
representative.
ORA-06753: TLI Driver: name-to-address mapping failed
Cause: For SVR4, the
netdir_getbyname() call failed for some unknown reason.
Action: Contact your custumer service
representative.
ORA-06754: TLI Driver: unable to get local host address
Cause: The name of the remote host to
connect to was not specified, and the name of the local host cannot be
retrieved from the HOSTS file.
Action: Contact your system
administrator.
ORA-06755: TLI Driver: cannot close transport endpoint
Cause: The TLI server was unable to
close a connection after passing it to an ORACLE process.
Action: Contact your customer support
representative.
ORA-06756: TLI Driver: cannot open oratab
Cause: The TLI server could not open
the file used to define the locations of remotely accessible databases.
Action: Ask your system administrator
to check that the file exists and has the correct permissions.
ORA-06757: TLI Driver: server got bad command
Cause: The TLI server received an
invalid command.
Action: Contact your customer support
representative.
ORA-06760: TLI Driver: timeout reading orderly release
Cause: TLI was not able to retreive
an expected disconnect message while closing the communication channel.
Action: Contact your customer support
representative.
ORA-06761: TLI Driver: error sending orderly release
Cause: TLI encountered an error
sending a disconnect message closing the communication channel.
Action: Contact your customer support
representative.
ORA-06762: TLI Driver: error reading orderly release
Cause: TLI encountered an error
receiving an expected disconnect message while closing the communication
channel.
Action: Contact your customer support
representative.
ORA-06763: TLI Driver: error sending disconnect
Cause: TLI encountered an error
sending a disconnect message closing the communication channel.
Action: Contact your customer support
representative.
ORA-06764: TLI Driver: error reading disconnect
Cause: TLI was not able to retreive
an expected disconnect message while closing the communication channel.
Action: Contact your customer support
representative.
ORA-06765: TLI Driver: error awaiting orderly release
Cause: TLI encountered an error
awaiting a disconnect message while closing the communication channel.
Action: Contact your customer support
representative.
ORA-06766: TLI Driver: close failed during release
Cause: TLI failed to close the
communication channel after receiving a disconnect message.
Action: Contact your customer support
representative.
ORA-06767: TLI Driver: alloc failed during release
Cause: TLI cannot allocate space for
disconnection information while closing the communication channel.
Action: Contact your customer support
representative.
ORA-06770: TLI Driver: error sending version
Cause: TLI encountered an error while
sending its version information during connection establishment.
Action: Contact your customer support
representative.
ORA-06771: TLI Driver: error reading version
Cause: TLI encountered an error while
awaiting the expected version information during connection establishment.
Action: Contact your customer support
representative.
ORA-06772: TLI Driver: error sending command
Cause: TLI encountered an error while
sending a command message during connection establishment.
Action: Contact your customer support
representative.
ORA-06773: TLI Driver: error reading command
Cause: TLI encountered an error while
awaiting the expected command message during connection establishment.
Action: Contact your customer support
representative.
ORA-06774: TLI Driver: error sending break mode
Cause: TLI encountered an error while
sending break-mode message during connection establishment.
Action: Contact your customer support
representative.
ORA-06775: TLI Driver: error reading break mode
Cause: TLI encountered an error while
awaiting the expected break-mode message during connection establishment.
Action: Contact your customer support
representative.
ORA-06776: TLI Driver: error sending parms
Cause: TLI encountered an error while
sending the connection parameters during connection establishment.
Action: Contact your customer support
representative.
ORA-06777: TLI Driver: error reading parms
Cause: TLI encountered an error while
awaiting the expected connection parameter message during connection
establishment.
Action: Contact your customer support
representative.
ORA-06778: TLI Driver: error sending ccode
Cause: TLI encountered an error while
sending the completion status message during connection establishment.
Action: Contact your customer support
representative.
ORA-06779: TLI Driver: error reading ccode
Cause: TLI encountered an error while
awaiting the expected completion status message during connection
establishment.
Action: Contact your customer support
representative.
ORA-06780: TLI Driver: recv error code failed
Cause: TLI encountered an error while
awaiting an expected error message during connection establishment.
Action: Contact your customer support
representative.
ORA-06781: TLI Driver: error reading negotation string
Cause: TLI encountered an error while
awaiting the expected negotiation message during connection establishment.
Action: Contact your customer support
representative.
ORA-06790: TLI Driver: poll failed
Cause: TLI was unable to poll the
communication channel for possible incoming messages.
Action: Contact your customer support
representative.
ORA-06791: TLI Driver: poll returned error event
Cause: TLI received an unexpected
event while polling the communication channel for possible incoming messages.
Action: Contact your customer support
representative.
ORA-06792: TLI Driver: server cannot exec oracle
Cause: The remote TLI server was
unable to start an ORACLE process on behalf of the client.
Action: Note the operating system
error message or number and contact your system adminstrator. The permissions
on the remote ORACLE program may be set incorrectly.
ORA-06793: TLI Driver: server cannot create new process
Cause: The remote TLI server was
unable to start an ORACLE process on behalf of the client.
Action: Note the operating system
error message or number and contact your system adminstrator. The remote host
may be unable to create any new processes due to a full process table.
ORA-06794: TLI Driver: shadow process could not retrieve
protocol info
Cause: The ORACLE process either
failed to allocate memory to store the protocol information record, or the
protocol rejected the request for some unknown reason.
Action: Contact your customer support
representative.
ORA-06800: TLI Driver: SQL*Net SPX client went away during
reconnect
Cause: The client process was aborted
by the system or the user, and was unable to complete the connection
establishment with the server listener process.
Action: Determine cause of client
exit, and reattempt connection.
ORA-06801: TLI Driver: listen for SPX server reconnect failed
Cause: An unknown event occurred on
the client's listening socket.
Action: Contact your customer support
representative.
ORA-06802: TLI Driver: could not open the
/etc/netware/yellowpages file
Cause: The /etc/netware/yellowpages
file does not exist, or is not readable by the TLI listener process.
Action: Insure the file exists and is
readable. Make sure that the server machine's node name, network number,
ethernet address, and listening socket number are encoded in the file.
ORA-06803: TLI Driver: the IPX device file could not be opened
Cause: The /dev/ipx file does not
exist, or the driver has not been installed in the kernel correctly.
Action: Reinvoke the Oracle root
installation. If problem continues, contact your customer support
representative.
ORA-06804: TLI Driver: could not bind an IPX address at
initialization
Cause: The IPX driver has not been
correctly installed.
Action: Reinvoke the Oracle root
installation. If problem continues, contact your customer support
representative.
ORA-06805: TLI Driver: could not send datagram SAP packet for
SPX
Cause: The socket endpoint for
sending SAP packet was corrupted for some unknown reason.
Action: Contact your customer support
representative.
ORA-06806: TLI Driver: could not complete protocol
initialization for SPX
Cause: A step in the SPX/IPX protocol
initialization failed.
Action: Check the previous error
reported, and follow corrective action.
ORA-06807: TLI Driver: could not open ethernet device driver
file
Cause: The file /dev/eth does not
exist, or the driver it references could not be opened.
Action: The system's real ethernet
device file, for example /dev/wd, for the Western Digital ethernet driver,
should be linked to the file /dev/eth. If this has been done, insure that the
ethernet driver has been installed by completing the TCP/IP installation on
your system, and testing a connection. If problem continues, contact your
customer support representative for a list of supported ethernet drivers.
ORA-06808: TLI Driver: could not link IPX and ethernet streams
Cause: Either the ethernet driver has
not been installed in the system correctly, or the ethernet driver is not
supported.
Action: Insure that the ethernet
driver has been installed by completing the TCP/IP installation on your system,
and testing a connection. If problem continues, contact your customer support
representative for a list of supported ethernet drivers.
ORA-06809: TLI Driver: could not clear the IPX ethernet SAP at
init
Cause: The IPX driver has not been
correctly installed.
Action: Reinvoke the Oracle root
installation. If problem continues, contact your customer support
representative.
ORA-06810: TLI Driver: could not set the IPX ethernet SAP at
init
Cause: The IPX driver has not been
correctly installed.
Action: Reinvoke the Oracle root
installation. If problem continues, contact your customer support
representative.
ORA-06811: TLI Driver: could not set the IPX network number at
init
Cause: The IPX driver has not been
correctly installed, or the network number encoded in the
/etc/netware/yellowpages file is invalid.
Action: The network number in the
yellowpages file should match the four-byte network number of your Novell file
server. If this is configured correctly, reinvoke the Oracle root installation.
If problem continues, contact your customer support representative.
ORA-06812: TLI Driver: could not read the ethernet driver's node
address
Cause: The ethernet driver is not
installed correctly, or does not support this operation.
Action: Contact your customer support
representative for a list of supported ethernet drivers.
ORA-06813: TLI Driver: the configured ethernet address is
incorrect
Cause: The node address read from the
ethernet driver does not match the value encoded in the
/etc/netware/yellowpages file for this server.
Action: Confirm the correct ethernet
node address for your LAN card, and enter this value in the yellowpages file.
ORA-06814: TLI Driver: the SPX device file could not be opened
Cause: The /dev/nspxd file does not
exist, or the driver has not been installed in the kernel correctly.
Action: Reinvoke the Oracle root
installation. If problem continues, contact your customer support
representative.
ORA-06815: TLI Driver: could not link SPX and IPX streams
Cause: The SPX driver has not been
correctly installed.
Action: Reinvoke the Oracle root
installation. If problem continues, contact your customer support
representative.
ORA-06816: TLI Driver: could not set the SPX SAP address
Cause: The SPX driver has not been
correctly installed.
Action: Reinvoke the Oracle root
installation. If problem continues, contact your customer support
representative.
ORA-06817: TLI Driver: could not read the Novell network address
Cause: The file
$ORACLE_HOME/spx/address could not be opened for reading and writing.
Action: Make sure ORACLE_HOME is set,
and the permissions on the ORACLE_HOME are read, write. If this file has been
unintentially deleted, run spxctl (net option) to reset the configured Novell
network number for SQL*Net SPX.
ORA-06900: CMX: cannot read tns directory
Cause: CMX is not started on your
system.
Action: Install and/or start CMX on
your system.
ORA-06901: CMX: no local name assigned to local application
Cause: Local application oracmx has
no local name assigned
Action: Enter unique local name for
oracmx in the tns directory
ORA-06902: CMX: cannot attach to cmx subsystem
Cause: ccp-xxxx is not started
Action: start your ccp software on the
communication controller
ORA-06903: CMX: cannot read transport address of remote
application
Cause: remote application not entered
in tns directory
Action: enter remote application in
tns directory
ORA-06904: CMX: no transport address available for remote
application
Cause: no local name assigned to
remote application
Action: assign local name to remote
application
ORA-06905: CMX: connect error
Cause: remote partner not listening
Action: make sure remote node has CMX
installed and running make sure oracmx is running on remote host
ORA-06906: CMX: cannot get maximum packet size from CMX
Cause: internal error in CMX
Action: contact your customer support
representative
ORA-06907: CMX: error during connect confirmation
Cause: remote partner aborted
Action: contact your customer support
representative
ORA-06908: CMX: error during transfer of ORACLE_SID
Cause: remote partner aborted
Action: contact your customer support
representative
ORA-06909: CMX: error during acknowledge of ORACLE_SID
Cause: remote partner aborted
Action: contact your customer support
representative
ORA-06910: CMX: Cannot start oracle process on remote machine
Cause: oracle process not found or
wrong mode (should be 4751)
Action: change /etc/oratab or set mode
to 4751
ORA-06911: CMX: t_event returns ERROR
Cause: internal error in CMX
Action: contact your customer support
representative
ORA-06912: CMX: write error in datarq
Cause: internal error in CMX
Action: contact your customer support
representative
ORA-06913: CMX: error during redirection of connection
Cause: oracmx has been stopped, or
user process has been aborted
Action: contact your customer support
representative
ORA-06914: CMX: unexepected event during start of oracle
Cause: connect sequence out of sync
Action: contact your customer support
representative
ORA-06915: CMX: unknown t_event in datarq
Cause: internal error in CMX
Action: contact your customer support
representative
ORA-06916: CMX: error in data read (t_datain)
Cause: remote partner aborted
Action: contact your customer support
representative
ORA-06917: CMX: error in data read (too many bytes read)
Cause: internal error in CMX
Action: contact your customer support
representative
ORA-06918: CMX: T_NOEVENT during wait for read event
Cause: internal error in CMX
Action: contact your customer support
representative
ORA-06919: CMX: error during write request (unknown event)
Cause: internal error in CMX
Action: contact your customer support
representative
ORA-06920: CMX: getbrkmsg illegal datatype
Cause: received packets are corrupted
Action: contact your customer support
representative
ORA-06921: CMX: getdatmsg illegal datatype
Cause: received packets are corrupted
Action: contact your customer support
representative
ORA-06922: CMX: bad write length
Cause: internal error in CMX
Action: contact your customer support
representative
ORA-06923: CMX: illegal break condition
Cause: break handling out of sync
Action: contact your customer support
representative
ORA-06924: CMX: wrong break message length
Cause: received packets are corrupted
Action: contact your customer support
representative
ORA-06925: CMX: disconnect during connect request
Cause: partner is not responding
Action: make sure partner is up and
running and reachable
ORA-06926: CMX: T_ERROR during read data
Cause: internal error in CMX
Action: contact your customer support
representative
ORA-06927: CMX: T_DATAIN received before all data written
Cause: internal error in CMX
Action: contact your customer support
representative
ORA-06928: CMX: wrong ORACLE_SID
Cause: ORACLE_SID is not entered in
remote oratab
Action: add ORACLE_SID to remote
oratab
ORA-06929: CMX: error when sending ORACLE_SID
Cause: internal error in CMX
Action: contact your customer support
representative
ORA-06930: CMX: error when checking ORACLE_SID
Cause: internal error in CMX
Action: contact your customer support
representative
ORA-06931: CMX: error during read_properties for server
Cause: internal error in CMX
Action: contact your customer support
representative
ORA-06932: CMX: error in local name
Cause: internal error in CMX
Action: contact your customer support
representative
ORA-06933: CMX: error during attach
Cause: internal error in CMX
Action: contact your customer support
representative
ORA-06950: No error
Cause: SQL*Net AppleTalk error codes
base. This is not an error.
Action: None
ORA-06951: Operating system call error
Cause: AppleTalk API received error
in VMS system service.
Action: Contact Oracle Customer
Support representative.
ORA-06952: Remote end of the communication issued a
forward-reset packet.
Cause: Peer program may have aborted
Action: Investigate network problems
and try again.
ORA-06953: Not enough virtual memory
Cause: Not enough memory available.
Action: Check VMS process quotas
and/or sysgen parameters
ORA-06954: Illegal file name
Cause: Erroneous file name
Action: Check path name for server
output file, or SQL*Net Appletalk Logical names and symbols.
ORA-06955: Number of database servers exceed limit
Cause: Too many database connections.
Action: Check ATKSRV_MAXCONparameter
in configuration file.
ORA-06956: Failed to get local host name
Cause: Unable to get Appletalk host
name.
Action: Check Appletalk configuration.
ORA-06957: No SID is currently available
Cause: Incoming SQL*Net connection
specified invalid SID name.
Action: Specify correct SID in connect
string and retry.
ORA-06958: Failed to access configuration file
Cause: Unable to access CONFIG.ATK
Action: Check file protections.
ORA-06959: Buffer I/O quota is too small
Cause: Buffered I/O quota exceeded.
Action: Increase BIOlm using AUTHORIZE
utility and retry.
ORA-06960: Failed to access log file
Cause: SQL*Net Appletalk listener
could not create log file.
Action: Check directory path and
protections.
ORA-06970: X.25 Driver: remote host is unknown
Cause: Host name specified in the
login (connect string) is unknown.
Action: Check spelling; make sure name
is in the X.25 HOST file.
ORA-06973: X.25 Driver: invalid buffer size
Cause: The buffer size specified in
the login string must be between 5 and 4096.
Action: Re-submit with valid buffer
size.
ORA-06974: X.25 Driver: SID lookup failure
Cause: From the remote host's SQL*Net
X.25 server: the database SID, specified in the login (connect) string, was not
recognized.
Action: Add the appropriate SID entry
to the CONFIG.ORA file on the remote host (and restart the SQL*Net X.25
server).
ORA-06975: X.25 Driver: connect to host failed
Cause: Connection attempt to remote
host has failed. Probably means that the SQL*Net X.25 server on the remote host
is not up, or the host itself is not up.
Action: Start the SQL*Net X.25 server
process on the remote host.
ORA-06976: X.25 Driver: endpoint creation failure
Cause: Process open file quota
probably exceeded.
Action: Contact your customer support
representative.
ORA-06977: X.25 Driver: X.25 Level 2 failure
Cause: X.25 level 2 is down. X.25
link is not working.
Action: Run system checks to verify
functioning of X.25 software. Contact your hardware vendor.
ORA-06978: X.25 Driver: Too many callback tries
Cause: Call back address probably
same as called address.
Action: Verify that callback address
and called address are different.
ORA-06979: X.25 Driver: server cannot start oracle
Cause: The remote X.25 server was
unable to start an ORACLE process on behalf of the client.
Action: Make sure permissions on the
remote ORACLE program are correctly set. Contact your system administrator.
ORA-07200: slsid: oracle_sid not set.
Cause: The environment variable
$(ORACLE_SID) is not set.
Action: Set ORACLE_SID environment
variable.
ORA-07201: slhom: oracle_home variable not set in environment.
Cause: $(ORACLE_HOME) environment
variable not set.
Action: Set ORACLE_HOME.
ORA-07202: sltln: invalid parameter to sltln.
Cause: The sltln name translation
routine was called with invalid arguments. The input, or output stings were
either NULL or 0 length.
Action: Probable internal oracle
error. Contact customer support.
ORA-07203: sltln: attempt to translate a long environment
variable.
Cause: A string was passed to sltln
containing a long environment variable. sltln accepts environment names of 30
or less characters.
Action: Shorten environment variable
name to less than 30 characters.
ORA-07204: sltln: name translation failed due to lack of output
buffer space.
Cause: The sltln routine is given a
maximum length buffer to expand the name into. An overflow of this buffer
occurred.
Action: Possible internal error. Check
output buffer length stored in sercose[0]. Pathnames are limited to 255
characters.
ORA-07205: slgtd: time error, unable to obtain time.
Cause: Time() system call returned an
error. Possible OS error.
Action: Check additional information
returned. Contact customer support.
ORA-07206: slgtd: gettimeofday error, unable to obtain time.
Cause: Gettimeofday() system call
returned an error. Possible OS error.
Action: Check additional information
returned. Contact customer support.
ORA-07207: sigpidu: process ID string overflows internal buffer.
Cause: The sigpidu routine is given a
maximum length buffer to hold process ID string. An overflow of this buffer
occurred.
Action: Internal error. Contact
customer support.
ORA-07208: sfwfb: failed to flush dirty buffers to disk.
Cause: The fsync system call returned
an error. Possible OS error.
Action: Check additional information
returned. Contact customer support.
ORA-07209: sfofi: file size limit was exceeded.
Cause: The size of the file to be
opened exceeded the OS limit imposed on this process.
Action: Run osh to increase the file
size limit.
ORA-07210: slcpu: getrusage error, unable to get cpu time.
Cause: Getrusage system call returned
an error. Possible OS error.
Action: Check additional information
returned. Contact customer support.
ORA-07211: slgcs: gettimeofday error, unable to get wall clock.
Cause: Gettimeofday system call
returned an error. Possible OS error.
Action: Check additional information
returned in OS reference manual. Contact customer support.
ORA-07212: slcpu: times error, unable to get cpu time.
Cause: times system call returned an
error. Possible OS error.
Action: Check additional information
returned. Contact customer support.
ORA-07213: slgcs: times error, unable to get wall clock.
Cause: times system call returned an
error. Possible OS error.
Action: Check additional information
returned in OS reference manual. Contact customer support.
ORA-07214: slgunm: uname error, unable to get system
information.
Cause: uname system call returned an
error. Possible OS error.
Action: Check additional information
returned in OS reference manual. Contact customer support.
ORA-07215: slsget: getrusage error.
Cause: Getrusage system call returned
an error. Possible OS error.
Action: Check additional information
returned. Look for information in OS reference. Contact customer support.
ORA-07216: slghst: gethostname error, unable to get name of
current host.
Cause: gethostname system call
returned an error. Possible OS error.
Action: Check additional information
returned in OS reference manual. Contact customer support.
ORA-07217: sltln: environment variable cannot be evaluated.
Cause: getenv call returned a null
pointer.
Action: Set the environment variable
and try again.
ORA-07218: slkhst: could not perform host operation
Cause: Unix system() call failed
Action: Examine system error message
ORA-07219: slspool: unable to allocate spooler argument buffer.
Cause: Malloc failed to allocate
space to hold spooler arguments.
Action: Check additional information
returned in OS reference manual. The process may have run out of heap space.
Contact customer support.
ORA-07220: slspool: wait error.
Cause: Wait returned an error, when
waiting for spool job to complete. Possible spooler program error.
Action: Check additional information
returned. Refer to OS reference manual. Contact customer support.
ORA-07221: slspool: exec error, unable to start spooler program.
Cause: Exec failed when starting line
printer spooler command. Likely that either the default line printer command,
or ORACLE_LPPROG, is incorrectly set.
Action: Verify default line printer
command and ORACLE_LPPROG are set correctly. Set ORACLE_LPPROG to working line
printer spooler.
ORA-07222: slspool: line printer spooler command exited with an
error.
Cause: The line printer spooler
exited with a non-zero return value. This probably indicates an error in
spooling file.
Action: Verify that line printer
spooler is up. Verify that ORACLE_LPPROG, and ORACLE_LPARG are set properly.
Check exit value returned as additional informatin.
ORA-07223: slspool: fork error, unable to spawn spool process.
Cause: Fork system call failed to
create additional process. Probable resource limit reached.
Action: Check additional information
returned. Retry operation. Contact system administrator.
ORA-07224: sfnfy: failed to obtain file size limit; errno
= string.
Cause: The ulimit system call
returned an error.
Action: Check errno and contact
customer support.
ORA-07225: sldext: translation error, unable to expand file
name.
Cause: Additional information
returned is error returned from sltln.
Action: Check additional information.
ORA-07226: rtneco: unable to get terminal mode.
Cause: The ioctl call returned an
error. Possible OS error.
Action: Check additional information
for errno. Contact customer support.
ORA-07227: rtneco: unable to set noecho mode.
Cause: The ioctl call returned an
error. Possible OS error.
Action: Check additional information
for errno. Contact customer support.
ORA-07228: rtecho: unable to restore terminal to echo mode.
Cause: The ioctl call returned an
error. Possible OS error.
Action: Check additional information
for errno. Contact customer support.
ORA-07229: slcpuc: error in getting number of CPUs.
Cause: error in mpcntl system call
Action: check errno and contact system
administrator
ORA-07230: slemcr: fopen error, unable to open error file.
Cause: Fopen failed to open file.
Action: Try to determine which file
was not opened. Check that file exists and is accessible.
ORA-07231: slemcc: invalid file handle, seals do not match.
Cause: Function was called with an
invalid argument. The file handle used was not obtained be slemcr.
Action: Internal error. Contact
customer support.
ORA-07232: slemcc: fclose error.
Cause: An error was encountered when
closing the file. Possible OS error.
Action: Contact system administator.
ORA-07233: slemcw: invalid file handle, seals do not match.
Cause: Function was called with an
invalid file handle. File handle was not obtained by slemcr.
Action: Internal error. Contact
customer support.
ORA-07234: slemcw: fseek error.
Cause: Unable to seek to desired
position in file. Possible OS error. Possible internal error.
Action: Verify that error message file
is intact. Try to regenerate error message file. Contact customer support.
ORA-07235: slemcw: fwrite error.
Cause: Unable to write item to file.
Possible OS error. Possible permissions problem.
Action: Retry operation.
ORA-07236: slemop: open error.
Cause: Unable to open error file.
Possible permissions problem.
Action: Verify permission on error
message file. Check additional information for errno.
ORA-07237: slemcl: invalid file handle, seals do not match.
Cause: Function was called with an
invalid file handle. Handle was not obtained by previous call to slemop.
Action: Internal error.
ORA-07238: slemcl: close error.
Cause: Unable to close file. Possible
OS error.
Action: Contact system administator.
Check additional information for errno.
ORA-07239: slemrd: invalid file handle, seals do not match.
Cause: Function was called with invalid
file handle. Handle was not obtained by call to slemop.
Action: Internal error. Contact
customer support.
ORA-07240: slemrd: seek error.
Cause: Unable to seek to desired
position in file. Possible OS error.
Action: Check that error file is still
intact. Verify space on device. Contact system administrator. Check additional
information for errno.
ORA-07241: slemrd: read error.
Cause: Unable to read file. Possible
OS error.
Action: Verify that error file is
intact. Regenerate error message file. Contact customer support. Check
additional information for errno.
ORA-07242: slembfn: translation error, unable to translate error
file name.
Cause: Additional information
indicates error returned from sltln.
Action: Check additional information.
ORA-07243: supplied buffer not big enough to hold entire line
Cause: supplied buffer was not big
enough
Action: Internal error. Contact
customer support. Additional information indicates how big the supplied buffer
was.
ORA-07244: ssfccf: create file failed, file size limit reached.
Cause: An attempt was made to create
a file that exceeds the process's file size limit.
Action: Run osh to raise the file size
limit.
ORA-07245: sfccf: unable to lseek and write the last block.
Cause: An attempt was made to move
and write to a bad device address.
Action: Check errno. Possible lack of
space on device.
ORA-07246: sfofi: open error, unable to open database file.
Cause: sfofi returns an error.
Action: This is an oracle internal
error.
ORA-07247: skgfrfms, skgfrnms: read error, unable to read block
from database file
Cause: The ioctl() system call
returned an error doing VOL_READ_MIRRORS.
Action: Check errno.
ORA-07248: sfwfb: write error, unable to write database block.
Cause: sfwfb returns an error.
Action: This is an oracle internal
error.
ORA-07249: slsget: open error, unable to open /proc/pid.
Cause: The open() system call
returned an error.
Action: Check that /proc has the right
permissions.
ORA-07250: spcre: semget error, unable to get first semaphore
set.
Cause: An error occurred when trying
to get first semaphore set.
Action: Check errno. Verify that
system is configured to have semaphores. Verify that enough semaphores are
available. Additional information indicates how many semaphores were requested.
ORA-07251: spcre: semget error, could not allocate any
semaphores.
Cause: Semget failed to even allocate
a single semaphore. Either they are all in use or the system is not configured
to have any semaphores.
Action: Check to see if all semaphores
are in use. Check to see if system is configured to have semaphores. Check
errno.
ORA-07252: spcre: semget error, could not allocate semaphores.
Cause: Semget system call returned an
error. Possible resource limit problem.
Action: Check errno. Verify that
enough semaphores are available in system. If additional errors occur in
destroying the semaphore sets then sercose[0] will be non-zero. If this occurs,
remove the semaphore sets using ipcrm.
ORA-07253: spdes: semctl error, unable to destroy semaphore set.
Cause: Semctl system call returned an
error.
Action: Check semaphore sets. May
require manual cleanup. Check additional information returned. Consult OS
reference manual.
ORA-07254: spdcr: translation error while expanding
?/bin/oracle.
Cause: An error occurred while translating
the name of the oracle executable.
Action: Check sercose[0] for error
returned from sltln. Perhaps $(ORACLE_HOME) is not set correctly.
ORA-07255: spini: cannot set up signal handler.
Cause: System failed to set up signal
handler.
Action: Check errno and sercose[0] for
the signal number that failed.
ORA-07256: sptrap: cannot set up signal handler to catch
exceptions.
Cause: System failed to set up signal
handler to catch exceptions.
Action: Check errno and sercose[0] for
the signal number that failed.
ORA-07257: spdcr: translation error expanding program name.
Cause: Error ocurred when expanding
program name ora_PNAME_@. The result of this translation is put in argv[0] of
oracle process.
Action: Check error returned by sltln
returned in sercose[0].
ORA-07258: spdcr: fork error, unable to create process.
Cause: An error occurred when
creating a new process.
Action: Check errno. Perhaps a system
limit on the number of processes has been exceeded.
ORA-07259: spdcr: exec error, detached process failed in
startup.
Cause: An oracle detached process
died shortly after startup. Wait() indicated that a child process terminated.
Action: Check ?/dbs directory for
trace or core files. Check errno.
ORA-07260: spdcr: wait error.
Cause: Wait system call returned an
error.
Action: Check errno.
ORA-07261: spdde: kill error, unable to send signal to process.
Cause: Kill system call returned an
error. Possibly an attempt to destroy an already gone process.
Action: Check errno.
ORA-07262: sptpa: sptpa called with invalid process id.
Cause: This is an internal error.
Action: This is an oracle internal
error.
ORA-07263: sptpa: kill error.
Cause: Kill system call returned an
error. Possible OS error.
Action: Check errno. Additional
information indicates the process ID tested.
ORA-07264: spwat: semop error, unable to decrement semaphore.
Cause: Semop system call returned an
error. Semaphore set may not exist.
Action: Check errno. Semaphore ID is
returned in sercose[0]. Verify semaphore set exists. A possible cause for this
error is that a "shutdown abort" was done while this process was
running.
ORA-07265: sppst: semop error, unable to increment semaphore.
Cause: Semop system call returned an
error. Semaphore set may not exist.
Action: Check errno. Semaphore ID is
returned in sercose[0]. Check semaphore set existence. A possible cause for
this error is that a "shutdown abort" was done while this process was
running.
ORA-07266: sppst: invalid process number passed to sppst.
Cause: Function was passed an invalid
oracle process id.
Action: Internal error.
ORA-07267: spwat: invalid process number.
Cause: Function was passed an invalid
oracle process id.
Action: Internal error. Additional
information indicates the invalid process id.
ORA-07268: szguns: getpwuid error.
Cause: Getpwuid() could not find an
entry in the passwd file for a user.
Action: Add an entry for the user in
the passwd file.
ORA-07269: spdcr: detached process died after exec.
Cause: Detached process succesfully
execed, but died shortly thereafter. Additional information indicates exit
code, and termination status.
Action: Check termination code for
information as to why process exited. Check for core dump or trace file.
ORA-07270: spalck: setitimer error, unable to set interval
timer.
Cause: An error occurred while trying
to set an interval timer. Probable porting problem.
Action: Check errno.
ORA-07271: spwat: invalid oracle process number.
Cause: Function was called with an
invalid oracle process number (0).
Action: Internal oracle error.
ORA-07272: spwat: invalid semaphore set id.
Cause: Semaphore ID fetched from SGA
was not initialized to valid value. Additional information returned is
semaphore set index, and oracle process number.
Action: Oracle internal error. Check
semaphore set index. Check oracle process number.
ORA-07273: sppst: invalid semaphore id.
Cause: Semaphore ID fetched from SGA
contained an invalid value. Additional information returned is semaphore set
index, and oracle process number.
Action: Oracle internal error. Check
semaphore set index. Check oracle process number.
ORA-07274: spdcr: access error, access to oracle denied.
Cause: Unable to access
"oracle" program. Verify ?/bin/oracle or $ORABCKPRG exist, and are
executable.
Action: Check errno returned.
ORA-07275: unable to send signal to process
Cause: The kill system call returned
an error. Possibly an attempt to signal a process which does not exist.
Action: Check errno.
ORA-07276: no dba group in /etc/group.
Cause: A group has not been set up
for dba users.
Action: Contact system administrator.
Set up dba group in /etc/group.
ORA-07277: spdde: illegal pid passed as argument.
Cause: A 0 pid was passed to spdde.
Action: Internal error. .
ORA-07278: splon: ops$username exceeds buffer length.
Cause: Splon constructed an ops$username
logon which exceeded the alloted buffer space.
Action: Use a shorter Unix username,
or use an oracle username. Contact customer support.
ORA-07279: spcre: semget error, unable to get first semaphore
set.
Cause: An error occurred when trying
to get first semaphore set.
Action: Check errno. Verify that
system is configured to have semaphores. Verify that enough semaphores are
available. Additional information indicates how many semaphores were requested.
ORA-07280: slsget: unable to get process information.
Cause: The ioctl call returned an
error. Possible OS error.
Action: Check additional information
for errno. Contact customer support.
ORA-07281: slsget: times error, unable to get cpu time.
Cause: times system call returned an
error. Possible OS error.
Action: Check additional information
returned. Contact customer support.
ORA-07282: sksaprd: string overflow.
Cause: The internal buffer is not big
enough to hold the archive control string.
Action: Internal restriction. Try a
shorter archive control string.
ORA-07283: sksaprd: invalid volume size for archive destination.
Cause: An invalid volume size was
specified.
Action: Specify a valid volume size in
archive control string.
ORA-07284: sksaprd: volume size specification not terminated
properly.
Cause: Some non-numeric text follows
the volume size specification.
Action: Enter a correct archive
control string.
ORA-07285: sksaprd: volume size should not be specified for a
disk file.
Cause: Volume size was specified for
a disk file.
Action: If you are archiving to a disk
file, do not specify its volume size.
ORA-07286: sksagdi: cannot obtain device information.
Cause: Stat on the log archiving
device failed.
Action: Check the returned OSD error
for the reason of failure.
ORA-07287: sksagdi: unsupported device for log archiving.
Cause: Log archiving to this device
is unsupported.
Action: Try log archiving to a
supported device.
ORA-07290: sksagdi: specified directory for archiving does not
exist.
Cause: The specified pathname is not
a directory.
Action: Verify that the archive
destination directory exists.
ORA-07303: ksmcsg: illegal database buffer size.
Cause: The database buffer size must
be a multiple of the database block size, and less than the maximum block size.
Action: Verify that the db_block_size
parameter is correct in INIT.ORA.
ORA-07304: ksmcsg: illegal redo buffer size.
Cause: The redo buffer size must be a
multiple of machine block size.
Action: Verify that the log_buffer
INIT.ORA parameter is correctly set.
ORA-07305: ksmcsg: illegal database buffer size.
Cause: The database buffer size must
be a multiple of the extended cache mapping size for indirect data buffers to
be used.
Action: Verify that the db_block_size
parameter is correct in INIT.ORA, or disable the use_indirect_data_buffers
parameter.
ORA-07324: smpall: malloc error while allocating pga.
Cause: Malloc library routine
returned an error.
Action: Check errno. Possibly out of
swap space.
ORA-07327: smpdal: attempt to destroy pga when it was not
mapped.
Cause: Smpdal was called when the PGA
had not been previously created.
Action: Internal error.
ORA-07339: spcre: maximum number of semaphore sets exceeded.
Cause: The internal buffer is not big
enough to hold the number of semaphore set identifiers requested.
Action: Reconfigure OS to have more
semaphores per set.
ORA-07345: The datafile name must not contain the string '..'.
Cause: The specified datafile name
contains '..'.
Action: Correct the datafile name and
retry the operation.
ORA-07346: slnrm: normalized file name is too long
Cause: After normalizing the
specified file name, the resulting file name was too long.
Action: Specify the shorter file name
and retry the operation.
ORA-07390: sftopn: translate error, unable to translate file
name.
Cause: An error occurred while
expanding the file name to open. Additional information returns error generated
in translation routine.
Action: Lookup additional error code
for further information.
ORA-07391: sftopn: fopen error, unable to open text file.
Cause: Fopen library routine returned
an error.
Action: Verify existence and
permissions.
ORA-07392: sftcls: fclose error, unable to close text file.
Cause: Fclose library routine
returned an error.
Action: Possible internal oracle
error.
ORA-07393: unable to delete text file
Cause: An error occurred while
deleting a text file.
Action: Verify that the file exists
and check additional errors.
ORA-07394: unable to append string to text file
Cause: An error occurred while
performing a string put operation.
Action: This is an internal error.
Check additional information.
ORA-07400: slemtr: translated name for the message file is too
long.
Cause: The name for the message file
overflows internal buffer.
Action: Try making the complete
path-name of the message file shorter by reorganizing the directory hierarchy.
ORA-07401: sptrap: cannot restore user exception handlers.
Cause: The system failed to restore
user exception handlers.
Action: Check errno and sercose[0] for
the signal number that failed.
ORA-07402: sprst: cannot restore user signal handler.
Cause: The system failed to restore
user signal handlers.
Action: Check errno and sercose[0] for
the signal number that failed.
ORA-07403: sfanfy: db_writers parameter not valid.
Cause: The db_writers parameter in
INIT.ORA exceeds the system-dependent maximum or is less than 0.
Action: Change the db_writers
parameter in INIT.ORA.
ORA-07404: sfareq: Timeout occurred waiting for request to
complete.
Cause: The master database writer
timed out waiting for a write or close to complete. One of the database writers
may have stopped running.
Action: Check all database writer
trace files. Shut down the database and try to warm start.
ORA-07405: sptrap: cannot setup alternate signal stack.
Cause: The system failed to setup an
alternate signal stack.
Action: Check errno and sercose[0] for
the location where it failed.
ORA-07406: slbtpd: invalid number.
Cause: An impossible request for
binary to decimal conversion was made.
Action: This conversion cannot be
performed.
ORA-07407: slbtpd: invalid exponent.
Cause: An impossible request for
binary to decimal conversion was made
Action: This conversion cannot be
performed.
ORA-07408: slbtpd: overflow while converting to packed decimal.
Cause: An impossible request for
binary to decimal conversion was made.
Action: This conversion cannot be
performed.
ORA-07409: slpdtb: invalid packed decimal nibble.
Cause: An impossible request for
decimal to binary conversion was made.
Action: This conversion cannot be
performed.
ORA-07410: slpdtb: number too large for supplied buffer.
Cause: An impossible request for
decimal to binary conversion was made.
Action: This conversion cannot be
performed.
ORA-07411: slgfn: full path name too big for supplied buffer.
Cause: The supplied buffer is not big
enough to hold the full path name.
Action: The construction of the full
path name cannot be performed.
ORA-07412: sfaslv: Error getting entry in asynchronous write
array.
Cause: One of the database writer
processes could not locate its entry in the SGA.
Action: Contact customer support.
ORA-07415: slpath: allocation of memory buffer failed.
Cause: Malloc() failed to allocate
buffer for storing ORACLE_PATH.
Action: System has run out of heap
space. Additional information indicates errno.
ORA-07416: slpath: pathname construction failed; lack of output
buffer space.
Cause: The slpath routine is given a
maximum length buffer to expand the name into. An overflow of this buffer
occurred.
Action: Possible internal error. Check
output buffer length stored in sercose[0] and constructed pathname length in
sercose[1].
ORA-07417: sfareq: One or more database writers not active.
Cause: One or more of the database
writer processes is no longer running.
Action: Check the trace files for the
database writers. Shut down the database and try to warm start.
ORA-07418: sfareq: Database writer got error in timing function.
Cause: An error occurred when the
database writer called the system timing function.
Action: Check the database writer
trace file. Shut down database and try to warm start.
ORA-07419: sfareq: Database writer got error in timing function.
Cause: An error occurred when the
database writer called the system timing function.
Action: Check the database writer
trace file. Shut down database and try to warm start.
ORA-07425: sdpri: error string in translating
dump file location.
Cause: An oracle error occurred when
translating the location of the dump file.
Action: Check the oracle error code.
ORA-07426: spstp: cannot obtain the location of dbs directory.
Cause: An oracle error occurred when
translating the location of the dbs directory.
Action: Check additional information
for the error returned from sltln.
ORA-07427: spstp: cannot change directory to dbs.
Cause: Chdir system call returned an
error. Possible permission problems.
Action: Check additional information
for the OS error code.
ORA-07431: fork failed
Cause: The server process was unable
to fork a child process.
Action: Verify that there are enough
system resources to support another process. The user or system process limit
may have been exceeded, or the amount of free memory or swap space may be
temporarily insufficient.
ORA-07432: unable to perform nested sleep
Cause: An attempt was made to make a
process sleep when it was already sleeping. This platform does not support this
capability.
Action: Try the SLEEP command when the
process is not sleeping.
ORA-07440: WMON process terminated with error
Cause: The wakeup monitor process
died.
Action: Warm start instance.
ORA-07441: function address must be aligned on string byte
boundary
Cause: An improperly aligned function
address was specified.
Action: Use a properly aligned
function address.
ORA-07442: function address must be in the range string to string
Cause: An invalid function address
was specified.
Action: Use a valid function address.
ORA-07443: function string not found
Cause: An invalid function name was
specified.
Action: Use a valid function name.
ORA-07444: function address string is not
readable
Cause: An invalid function
name/address was specified.
Action: Use a valid function
name/address.
ORA-07445: exception encountered: core dump [string] [string]
[string] [string] [string] [string]
Cause: An OS exception occurred which
should result in the creation of a core file. This is an internal error.
Action: Contact your customer support
representative.
ORA-07446: sdnfy: bad value 'string' for parameter string.
Cause: The directory specified as the
value for the stated parameter could not be used.
Action: Make sure the directory you
have specified is a valid directory/file specification.
ORA-07447: ssarena: usinit failed.
Cause: Oracle failed to create a
shared arena file.
Action: Use sercerrno field to
determine cause of failure.
ORA-07448: ssarena: maximum number of shared arenas exceeded.
Cause: Oracle attempted to create
more shared arena files than permitted.
Action: Raise the value for max_arena
in INIT.ORA.
ORA-07449: sc: usnewlock failed.
Cause: Oracle failed to acquire a
shared arena lock.
Action: Check result code in sercerrno
to determine the cause of failure.
ORA-07451: slskstat: unable to obtain load information.
Cause: kstat library returned an
error. Possible OS failure
Action: Check result code in
sercose[0] for more information.
ORA-07452: specified resource manager plan does not exist in the
data dictionary
Cause: User tried to load a resource
manager plan that does not exist.
Action: Use a resource manager plan
that exists in the data dictionary.
ORA-07453: requested resource manager plan schema does not
contain OTHER_GROUPS
Cause: User tried to load a resource
manager plan schema that does not contain the OTHER_GROUPS group.
Action: Use a resource manager plan
schema that contains the OTHER_GROUPS group.
ORA-07454: queue timeout, string second(s),
exceeded
Cause: User session queued for longer
than maximum specified queue queue duration time for consumer group.
Action: Re-submit job at a later time
or increase queue timeout.
ORA-07455: estimated execution time (string secs),
exceeds limit (string secs)
Cause: User attempted to execute an
operation whose estimated execution time exceeds the limit specified for the
consumer group.
Action: Execute job on behalf of
another group, or increase limit.
ORA-07456: cannot set RESOURCE_MANAGER_PLAN when database is
closed
Cause: An attempt was made to turn on
the Resource Manager when the database was closed.
Action: Open the database and try
again.
ORA-07457: cannot set _INTERNAL_RESOURCE_MANAGER_PLAN because of
FORCE
Cause: An attempt was made to set the
_INTERNAL_RESOURCE_MANAGER_PLAN parameter, however this failed because the
current RESOURCE_MANAGER_PLAN has the FORCE prefix.
Action: Remove the FORCE prefix from
the RESOURCE_MANAGER_PLAN parameter.
ORA-07458: cannot set the RESOURCE_MANAGER_PLAN parameter
Cause: An attempt was made to set the
RESOURCE_MANAGER_PLAN parameter, however, this failed because the database was
quiesced.
Action: Unquiesce the database.
ORA-07459: cannot restore the RESOURCE_MANAGER_PLAN parameter
Cause: An attempt was made to
internally restore the RESOURCE_MANAGER_PLAN parameter to the value before it
was internally set. This failed because the current plan was set by the user
and therefore did not need to be restored.
Action: No action needed.
ORA-07460: cannot set the RESOURCE_MANAGER_PLAN parameter
Cause: An attempt was made to
internally set the RESOURCE_MANAGER_PLAN parameter, however, this failed
because the current RESOURCE_MANAGER_PLAN has the FORCE prefix.
Action: Remove the FORCE prefix from
the RESOURCE_MANAGER_PLAN parameter.
ORA-07468: spwat: mset error, unable to set semaphore.
Cause: The mset routine returned an
error. Semaphore may not exist.
Action: Check result code in
sercerrno. Semaphore number returned in sercose[0].
ORA-07469: sppst: mclear error, unable to clear semaphore.
Cause: The mclear routine returned an
error. Semaphore may not exist.
Action: Check result code in
sercerrno. Semaphore number returned in sercose[0].
ORA-07470: snclget: cannot get cluster number.
Cause: The cluster_status system call
failed to get status information for the current cluster.
Action: Check result code in
sercose[0]. Possible operating system failure.
ORA-07471: snclrd: name translation error of sgadef.dbf file
name.
Cause: Unable to expand out
?/dbs/sgadef@.dbf file name.
Action: Verify $(ORACLE_HOME) and
$(ORACLE_SID) are properly set. Check error number returned from sltln in
sercose[0].
ORA-07472: snclrd: open error when opening sgadef.dbf file.
Cause: open failed when opening the
file ?/dbs/sgadef@.dbf
Action: Check errno. Possible
permission problem. Verify that the file ?/dbs/sgadef@.dbf exists.
ORA-07473: snclrd: read error when trying to read sgadef.dbf
file.
Cause: Read had an error when reading
sgadef.dbf file.
Action: Check errno. Verify file
exists, and is correct size.
ORA-07474: snclrd: close error, unable to close sgadef.dbf file.
Cause: An error occurred in close,
while closing the file "?/dbs/sgadef@.dbf"
Action: Check errno. Possible
operating system error.
ORA-07475: slsget: cannot get vm statistics.
Cause: The vm_statistics system call
failed to get virtual memory statistics.
Action: Check result code in
sercerrno. Possible operating system failure.
ORA-07476: slsget: cannot get mapped memory statistics.
Cause: The vm_mapmem system call
failed to get mapped memory statistics.
Action: Check result code in
sercerrno. Possible operating system failure.
ORA-07477: scgcmn: lock manager not initialized.
Cause: Lock manager must be
initialized before converting locks.
Action: Check result code in
sercerrno. Possible lock manager failure.
ORA-07478: scgcmn: cannot get lock status.
Cause: lm_stat_lock failed.
Action: Check result code in
sercerrno. Possible lock manager failure.
ORA-07479: scgcmn: cannot open or convert lock.
Cause: lm_open or lm_open_convert
failed.
Action: Check result code in sercerrno.
Possible lock manager failure.
ORA-07480: snchmod: cannot change permissions on
?/dbs/sgalm.dbf.
Cause: When creating an instance,
snlmini could not change the permissions on ?/dbs/sgalm.dbf
Action: Contact your customer support
representative.
ORA-07481: snlmatt: cannot attach to lock manager instance.
Cause: lm_attach failed to attach to
lock manager instance.
Action: Check result code in
sercerrno. Possible lock manager failure.
ORA-07482: snlmini: cannot create lock manager instance.
Cause: lm_create failed to create
lock manager instance.
Action: Check permissions on ?/dbs,
and remove ?/dbs/sgalm.dbf if it exists, then retry.
ORA-07483: snlkget: cannot convert(get) lock.
Cause: lm_convert failed to
convert(get) lock.
Action: Check result code in
sercerrno. Possible lock manager failure.
ORA-07484: snlkput: cannot convert(put) lock.
Cause: lm_convert failed to put lock
value.
Action: Check result code in
sercerrno. Possible lock manager failure.
ORA-07485: scg_get_inst: cannot open instance number lock.
Cause: lm_open failed.
Action: Check result code in
sercerrno. Possible lock manager failure.
ORA-07486: scg_get_inst: cannot convert(get) instance number
lock.
Cause: lm_convert failed to get lock
value.
Action: Check result code in sercerrno.
Possible lock manager failure.
ORA-07487: scg_init_lm: cannot create lock manager instance.
Cause: lm_create failed.
Action: Check result code in
sercerrno. Possible lock manager failure.
ORA-07488: scgrcl: lock manager not initialized.
Cause: Lock manager must be
initialized before releasing locks.
Action: Check result code in
sercerrno. Possible lock manager failure.
ORA-07489: scgrcl: cannot get lock status.
Cause: lm_stat_lock failed during
lock release/cancel.
Action: Check result code in sercerrno.
Possible lock manager failure.
ORA-07490: scgrcl: cannot convert lock.
Cause: lm_convert failed during lock
release/cancel.
Action: Check result code in
sercerrno. Possible lock manager failure.
ORA-07491: scgrcl: cannot cancel lock request.
Cause: lm_cancel failed during lock
release/cancel.
Action: Check result code in
sercerrno. Possible lock manager failure.
ORA-07492: scgrcl: cannot close lock.
Cause: lm_close failed during lock
release/cancel.
Action: Check result code in
sercerrno. Possible lock manager failure.
ORA-07493: scgrcl: lock manager error.
Cause: An error was encountered
releasing the lock.
Action: Check result code in
sercerrno. Possible lock manager failure.
ORA-07494: scgcm: unexpected error.
Cause: Unknown or unexpected error code.
Action: Check result code in
sercerrno. Possible lock manager failure.
ORA-07495: spwat: lm_wait failed.
Cause: lm_wait failed.
Action: Check result code in
sercerrno. Possible lock manager failure.
ORA-07496: sppst: lm_post failed.
Cause: lm_post failed.
Action: Check result code in
sercerrno. Possible lock manager failure.
ORA-07497: sdpri: cannot create trace file 'string';
errno = string.
Cause: 1. The trace file could not be
created for writing.
2. The trace file is a symbolic link.
Action: 1. Check if the dump directory
exists and whether it is writable.
2. Remove the symbolic link.
ORA-07498: spstp: Unable to open /dev/resched.
Cause: The rescheduling driver
/dev/resched is not found or is not working properly.
Action: Check installation of the
ORACLE rescheduling driver in the AIX kernel.
ORA-07499: spglk: Cannot reschedule.
Cause: The rescheduling driver
/dev/resched is not open. This is an internal error and should not occur.
Action: Contact your customer support
representative.
ORA-07500:
scglaa: $cantim unexpected return
Cause: VMS system service $CANTIM
returned an unexpected value
Action: Check for system error message
and refer to VMS documentation
ORA-07501:
scgtoa: $deq unexpected return
Cause: VMS system service $DEQ
returned an unexpected value
Action: Check for system error message
and refer to VMS documentation
ORA-07502:
scgcmn: $enq unexpected return
Cause: VMS system service $ENQ
returned an unexpected value
Action: Check for system error message
and refer to VMS documentation
ORA-07503:
scgcmn: $setimr unexpected return
Cause: VMS system service $SETIMR
returned an unexpected value
Action: Check for system error message
and refer to VMS documentation
ORA-07504:
scgcmn: $hiber unexpected return
Cause: VMS system service $HIBER
returned an unexpected value
Action: Check for system error message
and refer to VMS documentation
ORA-07505:
scggt: $enq parent lock unexpected return
Cause: VMS system service $ENQ
returned an unexpected value
Action: Check for system error message
and refer to VMS documentation
ORA-07506:
scgrl: $deq unexpected return on lockid string
Cause: VMS system service $DEQ
returned an unexpected value
Action: Check for system error message
and refer to VMS documentation
ORA-07507:
scgcm: unexpected lock status condition
Cause: A global locking system
service returned an unexpected value.
Action: Check for system error message
(if any) and refer to VMS documentation, or contact your customer support
representative.
ORA-07508:
scgfal: $deq all unexpected return
Cause: VMS system service $DEQ
returned an unexpected value
Action: Check for system error message
and refer to VMS documentation
ORA-07509:
scgfal: $deq parent lock unexpected return
Cause: VMS system service $DEQ
returned an unexpected value
Action: Check for system error message
and refer to VMS documentation
ORA-07510:
scgbrm: $getlki unexpected return on lockid string
Cause: VMS system service $GETLKI
returned an unexpected value
Action: Check for system error message
and refer to VMS documentation
ORA-07511:
sscggtl: $enq unexpected return for master termination lock
Cause: VMS system service $ENQ
returned an unexpected value
Action: Check for system error message
and refer to VMS documentation
ORA-07512:
sscggtl: $enq unexpected return for client termination lock
Cause: VMS system service $ENQ
returned an unexpected value
Action: Check for system error message
and refer to VMS documentation
ORA-07513:
sscgctl: $deq unexpected return on cancel of term. lock
Cause: VMS system service $DEQ returned
an unexpected value
Action: Check for system error message
and refer to VMS documentation
ORA-07514:
scgcan: $deq unexpected return while canceling lock
Cause: VMS system service $DEQ
returned an unexpected value
Action: Check for system error message
and refer to VMS documentation
ORA-07534:
scginq: $getlki unexpected return on lockid string
Cause: VMS system service $GETLKI
returned an unexpected value
ORA-07548:
sftopn: Maximum number of files already open
Cause: Too many test files open
Action: This is an internal error,
please report to Oracle
ORA-07549:
sftopn: $OPEN failure
Cause: VMS system service $OPEN
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07550:
sftopn: $CONNECT failure
Cause: VMS system service $OPEN
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07551:
sftcls: $CLOSE failure
Cause: VMS system service $CLOSE
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07552:
sftget: $GET failure
Cause: VMS system service $GET failed
Action: Examine system error message
and refer to VMS documentation
ORA-07561:
szprv: $IDTOASC failure
Cause: VMS system service $IDTOASC
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07562:
sldext: extension must be 3 characters
Cause: An extension was found but it
is of improper length
Action: This is an internal error,
please report to Oracle
ORA-07563:
sldext: $PARSE failure
Cause: VMS system service $PARSE
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07564:
sldext: wildcard in filename or extension
Cause: A wildcard was used in the
file name
Action: Reenter the file name
completely
ORA-07565:
sldext: $SEARCH failure
Cause: VMS system service $SEARCH
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07568:
slspool: $OPEN failure
Cause: VMS system service $OPEN
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07569:
slspool: $CLOSE failure
Cause: VMS system service $CLOSE
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07570:
szrfc: $IDTOASC failure
Cause: VMS system service $IDTOASC
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07571:
szrfc: $FIND_HELD failure
Cause: VMS system service $FIND_HELD
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07572:
szrfc: insufficient rolename buffer space
Cause: An OS role name was too long.
Action: Re-define the role name to be
of correct length.
ORA-07573:
slkhst: could not perform host operation
Cause: VMS system service LIB$SPAWN
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07574:
szrfc: $GETUAI failure
Cause: VMS system service $GETUAI
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07576:
sspexst: $GETJPIW failure on process ID string
Cause: VMS system service $GETJPIW
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07577:
no such user in authorization file
Cause: An attempt was made to set an
INTERNAL password (for either DBA or OPER privilege), but the corresponding VMS
account (either ORA__DBA or ORA__OPER) hasn't been
created yet.
Action: Add a VMS account for
ORA__DBA and/or ORA__OPER before trying to set a password
for them.
ORA-07578:
szprv: $FIND_HELD failure
Cause: VMS system service $FIND_HELD
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07579:
spini: $DCLEXH failure
Cause: VMS system service $PARSE
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07580:
spstp: $GETJPIW failure
Cause: VMS system service $GETJPIW
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07581:
spstp: cannot derive SID from unexpected process name
Cause: A background process did not
have name of correct form
Action: If the job name was changed,
restore it, otherwise this is an internal error, please report to Oracle.
ORA-07582:
spstp: ORA_SID has illegal value
Cause: The ORA_SID must exist and be
less than 6 characters
Action: Consult the VMS Installation
guide for information on setting the SID.
ORA-07584:
spdcr: invalid value for ORA_sid_(proc_)PQL$_item
Cause: A logical name used to set a
detached process quota value has an invalid value (probably non-numeric).
Action: Examine the values of these
logical names, correct the one in error, and retry.
ORA-07585:
spdcr: $PARSE failure
Cause: VMS system service $PARSE
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07586:
spdcr: $SEARCH failure
Cause: VMS system service $SEARCH
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07587:
spdcr: $CREPRC failure
Cause: VMS system service $CREPRC
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07588:
spdcr: $GETJPIW get image name failure
Cause: VMS system service $GETJPIW
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07589:
spdde: system ID not set
Cause: The logical name ORA_SID
doesn't translate to a valid value.
Action: Check the value of ORA_SID in
the process that gets the error, and correct the installation or command
procedures that caused ORA_SID to be set incorrectly.
ORA-07590:
spdde: $DELPRC failure
Cause: VMS system service $DELPRC
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07591:
spdde: $GETJPIW failure
Cause: VMS system service $GETJPIW
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07592:
sspgprv: Error obtaining required privileges
Cause: While obtaining needed
privileges, an error was returned from SYS$SETPRV.
Action: This is an internal error.
Please report to Oracle
ORA-07593:
ssprprv: Error release privileges
Cause: While releasing privileges, an
error was returned from SYS$SETPRV.
Action: This is an internal error.
Please report to Oracle
ORA-07594:
spiip: $GETJPIW failure
Cause: VMS system service $GETJPIW
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07595:
sppid: $GETJPIW failure
Cause: VMS system service $GETJPIW
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07596:
sptpa: $GETJPIW failure
Cause: VMS system service $GETJPIW
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07597:
spguns: $GETJPIW failure
Cause: VMS system service $GETJPIW
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07598:
spwat: $SETIMR failure
Cause: VMS system service $GETJPIW
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07599:
spwat: $SCHDWK failure
Cause: VMS system service $SCHDWK
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07600:
slkmnm: $GETSYIW failure
Cause: VMS system service $GETSYIW failed
Action: Examine system error message
and refer to VMS documentation
ORA-07601:
spguno: $GETJPIW failure
Cause: VMS system service $GETJPIW
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07602:
spgto: $GETJPIW failure
Cause: VMS system service $GETJPIW
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07605:
szprv: $ASCTOID failure
Cause: VMS system service $ASCTOID
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07606:
szprv: $CHKPRO failure
Cause: VMS system service $CHKPRO
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07607:
szaud: $SNDOPR failure
Cause: VMS system service $SNDOPR
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07608:
szprv: $GETUAI failure
Cause: VMS system service $GETUAI
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07609:
szprv: $HASH_PASSWORD failure
Cause: VMS system service $HASH_PASSWORD
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07610:
$GETJPIW failed in retrieving the user's MAC priviledges
Cause: VMS system service $GETJPIW
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07612:
$GETUAI failed in retrieving the user's clearance level
Cause: VMS system service $GETUAI
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07613:
$GETJPIW failed in retrieving the user's process label
Cause: VMS system service $GETJPIW
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07614:
$CHANGE_CLASS failed in retrieving the user's process label
Cause: VMS system service
$CHANGE_CLASS failed
Action: Examine system error message
and refer to SEVMS documentation
ORA-07615:
$CHANGE_CLASS failed in retrieving the specified file label
Cause: VMS system service
$CHANGE_CLASSS failed
Action: Examine system error message
and refer to SEVMS documentation
ORA-07616:
$CHANGE_CLASS failed in retrieving the specified device label
Cause: VMS system service
$CHANGE_CLASS failed
Action: Examine system error message
and refer to SEVMS documentation
ORA-07617:
$FORMAT_CLASS failed translating the binary label to a string
Cause: VMS system service
$FORMAT_CLASS failed because the given binary classification was not valid.
Action: Examine system error message
and refer to SEVMS documentation
ORA-07618:
$IDTOASC failed translating a secrecy level
Cause: VMS system service $IDTOASC
failed while looking up the string representation in the rights database of a
secrecy level.
Action: Define the entry in the rights
database which the binary label you specified references.
ORA-07619:
$IDTOASC failed translating an integrity level
Cause: VMS system service $IDTOASC
failed while looking up the string representation in the rights database of an
integrity level.
Action: Define the entry in the rights
database which the binary label you specified references.
ORA-07620:
smscre: illegal database block size
Cause: An illegal database block size
was specified in the parameter file. It must be positive, a multiple of 512,
and less than the maximum physical i/o data size.
Action: Change db_block_size in the
parameter file to conform to these limits.
ORA-07621:
smscre: illegal redo block size
Cause: An illegal redo log buffer
size was specified in the parameter file. It must be positive and a multiple of
512.
Action: Change log_buffer in the
parameter file to conform to these limits.
ORA-07622:
smscre: $CREATE failure
Cause: While creating the system
global area (SGA) backing file, VMS system service $CREATE failed.
Action: Examine the system error
message and refer to VMS documentation.
ORA-07623:
smscre: $CRMPSC failure
Cause: While creating the system
global area (SGA), VMS system service $CRMPSC failed.
Action: Examine the system error
message and refer to VMS documentation.
ORA-07624:
smsdes: $DGBLSC failure
Cause: While deleting the system
global area (SGA), VMS system service $DGBLSC failed.
Action: Examine the system error
message and refer to VMS documentation.
ORA-07625:
smsget: $MGBLSC failure
Cause: While mapping the system
global area (SGA) during logon, VMS system service $MGBLSC failed. The usual
reason is that Oracle has not been started up.
Action: Examine the system error
message and refer to VMS documentation. Start up Oracle if it is not already
started.
ORA-07626:
smsget: sga already mapped
Cause: An attempt to map the SGA
during logon failed because it was already mapped. This is an internal error.
Action: Exit your program and try
again, and report this to your customer support representative.
ORA-07627:
smsfre: $CRETVA failure
Cause: While unmapping the system
global area (SGA) during logoff, VMS system service $CRETVA failed.
Action: Examine the system error
message and refer to VMS documentation.
ORA-07628:
smsfre: sga not mapped
Cause: An attempt to unmap the SGA
during logoff failed because it was not mapped. This is an internal error.
Action: Exit your program and try
again, and report this to your customer support representative.
ORA-07629:
smpall: $EXPREG failure
Cause: While extending the program
global area (PGA), VMS system service $EXPREG failed. This often happens when
the virtual memory page count quota is exceeded.
Action: Examine the system error
message and refer to VMS documentation.
ORA-07630:
smpdal: $DELTVA failure
Cause: While deleting the program
global area (PGA) during logoff, VMS system service $DELTVA failed.
Action: Examine the system error
message and refer to VMS documentation.
ORA-07631:
smcacx: $EXPREG failure
Cause: While creating or extending a
context area, VMS system service $EXPREG failed. This often happens when the
virtual memory page count quota is exceeded.
Action: Examine the system error
message and refer to VMS documentation.
ORA-07632:
smsrcx: $DELTVA failure
Cause: While deleting a context area,
VMS system service $DELTVA failed.
Action: Examine the system error
message and refer to VMS documentation.
ORA-07633:
smsdbp: illegal protection value
Cause: The buffer debug function was
called with an illegal value. This is an internal error.
Action: Contact your customer support
representative.
ORA-07634:
smsdbp: $CRETVA failure
Cause: While attempting to set
protection in the database buffer debug mechanism, VMS system service $CRETVA
failed.
Action: Contact your customer support
representative.
ORA-07635:
smsdbp: $SETPRT failure
Cause: While attempting to set
protection in the database buffer debug mechanism, VMS system service $SETPRT
failed.
Action: Contact your customer support
representative.
ORA-07636:
smsdbp: $MGBLSC failure
Cause: While attempting to set
protection in the database buffer debug mechanism, VMS system service $MGBLSC
failed.
Action: Contact your customer support
representative.
ORA-07637:
smsdbp: buffer protect option not specified when sga created
Cause: Trying to change the buffer
protect mode when the SGA was not created with buffer protect debug option.
This is an internal error.
Action: Contact your customer support
representative.
ORA-07638:
smsget: SGA pad area not large enough for created SGA
Cause: An attempt was made to map an
SGA with software in which the SGA pad area isn't large enough.
Action: Create a smaller SGA, or
relink the software with a larger pad.
ORA-07639:
smscre: SGA pad area not large enough (string bytes required)
Cause: An attempt was made to create
an SGA with software in which the SGA pad area isn't large enough.
Action: Create a smaller SGA, or
relink the software with a larger pad.
ORA-07640:
smsget: SGA not yet valid. Initialization in progress
Cause: An attempt was made to map to
the SGA while it was being initialized.
Action: Wait until initialization is
complete, and try again.
ORA-07641:
smscre: Unable to use the system pagefile for the SGA
Cause: The system global area (SGA)
backing file could not be allocated using the system pagefile because the
system-wide limit on global pages has been exceeded.
Action: Either increase the VMS system
parameter GBLPAGFIL or use a disk file as the SGA backing file.
ORA-07642:
smprtset: $CMKRNL failure
Cause: While attempting to set the
protection of a region of memory, an error was returned from the $CMKRNL system
service.
Action: Examine the system error
message and refer to VMS documentation.
ORA-07643:
smsalo: SMSVAR is invalid
Cause: an internal error
Action: Report this error to Oracle
Support Services, provide your INIT.ORA file.
ORA-07645:
sszfsl: $CHANGE_CLASS failure
Cause: While attempting to set the
label on a file, SEVMS service $CHANGE_CLASS failed.
Action: Examine the system message and
refer to SEVMS system documentation.
ORA-07646:
sszfck: $CREATE failure
Cause: While attempting to create a
file, VMS system service $CREATE failed.
Action: Examine the system message and
refer to VMS system documentation.
ORA-07647:
sszfck: $OPEN failure
Cause: While attempting to reopen a
file, VMS system service $OPEN failed.
Action: Examine the system message and
refer to VMS system documentation.
ORA-07650:
sigunc: $GETJPIW failure
Cause: While attempting to get the
user's terminal device name, user name, user program name, or process name
during logon, VMS system service $GETJPIW failed.
Action: Examine the system error
message and refer to VMS documentation.
ORA-07655:
slsprom:$TRNLOG failure
Cause: While attempting to translate
SYS$INPUT during a prompt for a password, VMS system service $TRNLOG failed.
Action: Examine the system error
message and refer to VMS documentation.
ORA-07656:
slsprom:$GETDVI failure
Cause: While attempting to get device
characteristics during a prompt for a password, VMS system service $GETDVI
failed.
Action: Examine the system error
message and refer to VMS documentation.
ORA-07657:
slsprom:$ASSIGN failure
Cause: While prompting for a
password, VMS system service $ASSIGN failed.
Action: Examine the system error
message and refer to VMS documentation.
ORA-07658:
slsprom:$QIOW read failure
Cause: While prompting for a
password, VMS system service $QIOW failed.
Action: Examine the system error
message and refer to VMS documentation.
ORA-07665:
ssrexhd: recursive exception encountered string string string string string string
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 your customer support
representative.
ORA-07670:
$IDTOASC failed translating a secrecy category
Cause: VMS system service $IDTOASC
failed while looking up the string representation in the rights database of a
secrecy category.
Action: Define the entry in the rights
database which the binary label you specified references.
ORA-07671:
$IDTOASC failed translating an integrity category
Cause: VMS system service $IDTOASC
failed while looking up the string representation in the rights database of an
integrity category.
Action: Define the entry in the rights
database which the binary label you specified references.
ORA-07672:
$PARSE_CLASS failed translating the string into a binary label
Cause: SEVMS system service
$PARSE_CLASS failed because the given string did not represent a valid
classification.
Action: Examine system error message
and refer to SEVMS documentation.
ORA-07680:
sou2os: another call to Oracle currently executing
Cause: A call to the Oracle shared
image entry point occurred from within the shared image. This is an internal
error.
Action: Contact your customer support
representative.
ORA-07681:
sou2os: An error occurred while initializing Oracle
Cause: While attempting to set up the
dispatch vectors for the shared image, an error occurred. This is an internal
error.
Action: Contact your customer support
representative.
ORA-07682:
sou2os: set kernel dispatch fail err
Cause: During Oracle shared image
entry, a dispatch to kernel mode failed.
Action: Make sure that your shared
image is installed with the CMKRNL privilege, then contact your customer
support representative.
ORA-07683:
sou2os: $SETPRV reset error
Cause: During an attempt to restore
user privileges at Oracle shared image exit, VMS system service $SETPRV failed.
This is an internal error.
Action: Contact your customer support
representative.
ORA-07684:
sou2os: supervisor stack reset error
Cause: During an attempt to restore
the supervisor-mode stack at Oracle shared image exit, VMS system service
$SETSTK failed. This is an internal error.
Action: Contact your customer support
representative.
ORA-07685:
sou2os: supervisor stack set error
Cause: During an attempt to set the
Oracle supervisor-mode stack at Oracle shared image entry, VMS system service
$SETSTK failed. This is an internal error.
Action: Contact your customer support
representative.
ORA-07700:
sksarch: interrupt received
Cause: An interrupt was received
while archiving the logs
Action: Retry operation
ORA-07701:
sksatln: internal exception: output buffer too small
Cause: Overflow of buffer for parsing
archive control text string
Action: This is an internal error,
please report to Oracle
ORA-07702:
unrecognized device type in archive text
Cause: Unrecognized device type in
archive text
Action: This is an internal error,
please report to Oracle
ORA-07703:
error in archive text: need '/' after device type
Cause: The archive control text in
the ARCHIVE command is invalid; the device type (to indicate a file or tape)
must be followed by a '/'.
Action: Refer to the SQLDBA Guide for
the proper syntax of the text.
ORA-07704:
error in archive text: need ':' after device name
Cause: The archive control text in
the ARCHIVE command is invalid; the device name must be followed by a ':'.
Action: Refer to the SQLDBA Guide for
the proper syntax of the text.
ORA-07705:
sksaprs: device name buffer too small
Cause: The buffer supplied for the
device name is too small. This is an internal error.
Action: Contact your customer support
representative.
ORA-07706:
error in archive text: need disk file name
Cause: The archive control text in
the ARCHIVE command is invalid; the disk file name is missing.
Action: Refer to the SQLDBA Guide for
the proper syntax of the text.
ORA-07707:
error in archive text: need tape label name
Cause: The archive control text in
the ARCHIVE command is invalid; the tape label name is missing.
Action: Refer to the SQLDBA Guide for
the proper syntax of the text.
ORA-07708:
sksaprs: tape label name buffer too small
Cause: The buffer supplied for the
tape label is too small. This is an internal error.
Action: Contact your customer support
representative.
ORA-07709:
sksaprs: archiving to a remote host is not allowed
Cause: The user specified a remote
disk for archiving via DECnet.
Action: Archive to a disk on the local
host.
ORA-07710:
sksaprs: file name buffer too small
Cause: The buffer supplied for the
file name is too small. This is an internal error.
Action: Contact your customer support
representative.
ORA-07713:
sksamtd: could not mount archival device (SYS$MOUNT failure)
Cause: VMS system service SYS$MOUNT
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07715:
sksadtd: could not dismount archival device (SYS$DISMNT failure)
Cause: VMS system service SYS$DISMNT
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07716:
sksachk: invalid device specification for ARCHIVE
Cause: VMS system service SYS$GETDVI
failed"
Action: Specify a valid device in
ARCHIVE control string
ORA-07717:
sksaalo: error allocating memory
Cause: VMS system service LIB$GET_VM
failed"
Action: Examine system error message
and refer to VMS documentation
ORA-07718:
sksafre: error freeing memory
Cause: VMS system service LIB$FREE_VM
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07721:
scgcm: not enough OS resource to obtain system enqueue
Cause: d by the messages SS$_EXENQLM
or SS$_INSFMEM.
Action: Free up some of the required
resource to allow the creation of the required lock.
ORA-07740:
slemop: incorrect handle size (programming error)
Cause: structures used for reading
error message files do not match
Action: this is an internal error,
please report to Oracle
ORA-07741:
slemop: $OPEN failure
Cause: VMS system service $OPEN
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07742:
slemop: $CONNECT failure
Cause: VMS system service $CONNECT
failed
Action: Examine system error message
and refer to VMS documentation
ORA-07743:
slemop: incorrect error file attributes
Cause: An error message file is of
incorrect format
Action: Unless an error file has been
changed, report this to Oracle
ORA-07744:
slemcl: invalid error message file handle
Cause: seal in passed in handle does
not match correct value
Action: this is an internal error,
please report to Oracle
ORA-07745:
slemcl: $CLOSE failure
Cause: VMS system service $CLOSE
failed
Action: Check system error and refer
to VMS documentation
ORA-07746:
slemrd: invalid error message file handle
Cause: seal in passed in handle does
not match correct value
Action: this is an internal error,
please report to Oracle
ORA-07747:
slemrd: $READ failure
Cause: VMS system service $READ
failed
Action: Check system error and refer
to VMS documentation
ORA-07750:
slemcr: fopen failure
Cause: An attempt to create a message
file failed. This is an internal error.
Action: Contact your customer support
representative.
ORA-07751:
slemcr: malloc failure
Cause: An attempt to allocate a cache
for a newly-created message file failed. This is an internal error.
Action: Contact your customer support
representative.
ORA-07753:
slemcf: fseek before write failure
Cause: An attempt to seek before
writing a message file cache element failed. This is an internal error.
Action: Contact your customer support
representative.
ORA-07754:
slemcf: fwrite failure
Cause: An attempt to write a message
file cache element failed. This is an internal error.
Action: Contact your customer support
representative.
ORA-07755:
slemcf: fseek before read failure
Cause: An attempt to seek before
reading a message file cache element failed. This is an internal error.
Action: Contact your customer support
representative.
ORA-07756:
slemcf: fread failure
Cause: An attempt to read a message
file cache element failed. This is an internal error.
Action: Contact your customer support
representative.
ORA-07757:
slemcc: invalid handle
Cause: The seal in a passed-in handle
does not match correct value. This is an internal error.
Action: Contact your customer support
representative.
ORA-07758:
slemcw: invalid handle
Cause: The seal in a passed-in handle
does not match correct value. This is an internal error.
Action: Contact your customer support
representative.
ORA-07759:
slemtr: invalid destination
Cause: The destination string
provided to the function is too short This is an internal error.
Action: Contact your customer support
representative.
ORA-07760:
slemtr: $open failure
Cause: the $open service failed. This
is an internal error
Action: Contact your customer support
representative.
ORA-07800:
slbtpd: invalid number
Cause: An impossible request for
binary to decimal conversion was made
Action: This conversion cannot be
performed
ORA-07801:
slbtpd: invalid exponent
Cause: An impossible request for
binary to decimal conversion was made
Action: This conversion cannot be
performed
ORA-07802:
slbtpd: overflow while converting to packed decimal
Cause: An impossible request for
binary to decimal conversion was made
Action: This conversion cannot be
performed
ORA-07803:
slpdtb: invalid packed decimal nibble
Cause: An impossible request for
decimal to binary conversion was made
Action: This conversion cannot be
performed
ORA-07804:
slpdtb: number too large for supplied buffer
Cause: An impossible request for
decimal to binary conversion was made
Action: This conversion cannot be
performed
ORA-07820:
sspscn: SYS$CRELNM failure
Cause: An error was returned from the
SYS$CRELNM function
Action: Check system error and refer
to VMS documentation
ORA-07821:
sspsdn: SYS$DELLNM failure
Cause: An error was returned from the
SYS$DELLNM function
Action: Check system error and refer
to VMS documentation
ORA-07822:
sspscm: SYS$CREMBX failure
Cause: An error was returned from the
SYS$CREMBX function while trying to create the process dump mailbox.
Action: Check system error and refer
to VMS documentation
ORA-07823:
sspsqr: $QIO failure
Cause: An error was returned from
$QIO while trying to queue a read to the process dump mailbox.
Action: Check system error and refer
to VMS documentation
ORA-07824:
sspain: $SETIMR failure
Cause: An error was returned from
SYS$SETIMR while trying to queue a process spin-watch timer.
Action: Check system error and refer
to VMS documentation
ORA-07825:
sspsck: $QIO failure at AST level
Cause: An error was returned from
SYS$QIO while trying to read the process dump mailbox.
Action: Check system error and refer
to VMS documentation
ORA-07826:
sspscm: SYS$GETDVIW failure
Cause: An error was returned from SYS$GETDVIW
while trying to get information about the process dump mailbox.
Action: Check system error and refer
to VMS documentation
ORA-07840:
sllfop: LIB$GET_VM failure
Cause: An error was returned from
LIB$GET_VM while attempting to allocate memory for an i/o vector.
Action: Check system error and refer
to VMS documentation
ORA-07841:
sllfop: SYS$OPEN failure
Cause: An error was returned from
SYS$OPEN while attempting to open the data file for reading
Action: Check system error and refer
to VMS documentation
ORA-07842:
sllfcl: SYS$CLOSE failure
Cause: An error was returned from
SYS$CLOSE while attempting to close the input data file
Action: Check system error and refer
to VMS documentation
ORA-07843:
sllfcl: LIB$FREE_VM failure
Cause: An error was returned from
LIB$FREE_VM while attempting to free the memory for the i/o vector
Action: Check system error and refer
to VMS documentation
ORA-07844:
sllfop: LIB$GET_VM failure
Cause: An error was returned from
LIB$GET_VM while attempting to allocate memory for data and index buffers
Action: Check system error and refer
to VMS documentation
ORA-07845:
sllfcl: LIB$FREE_VM failue
Cause: An error was returned from
LIB$FREE_VM while attempting to free memory used by data and index buffers
Action: Check system error and refer
to VMS documentation
ORA-07846:
sllfop: string byte record too big for string byte
user buffer
Cause: The longest record in the file
will not fit into the largest data buffer that can be allocated
Action: Modify the RMS file to have
smaller records
ORA-07847:
sllfop: $CONNECT failure
Cause: An error was returned by
SYS$CONNECT while attempting to open the data file
Action: Check system error and refer
to VMS documentation
ORA-07848:
sllfrb: $GET failure
Cause: An error was returned by
SYS$GET while attempting to read the data file
Action: Check system error and refer
to VMS documentation
ORA-07849:
sllfsk: $GET failure
Cause: An error was returned by
SYS$GET while attempting to skip records in the input file
Action: Check system error and refer
to VMS documentation
ORA-07850:
sllfop: bad option
Cause: You are using a bad option to
loader Fixed= is one legal option. Check documentation for others.
Action: Check documentation
ORA-07860:
osnsoi: error setting up interrupt handler
Cause: An error occurred while
setting up the control interrupt handler
Action: This is an internal error.
Contact your Oracle representative.
ORA-07880:
sdopnf: internal error
Cause: A list of all files open by
this process could not be obtained.
Action: This is an internal error.
Contact your customer support representative.
ORA-08000:
maximum number of session sequence lists exceeded
Cause: the sequence parent state
objects for this session are all used
Action: an internal error; quit the
session and begin a new one
ORA-08001:
maximum number of sequences per session exceeded
Cause: the limit on the number of
sequences usable by session has been hit
Action: increase INIT.ORA parameter
user_sequences to get more
ORA-08002:
sequence string.CURRVAL is not yet defined in this session
Cause: sequence CURRVAL has been
selected before sequence NEXTVAL
Action: select NEXTVAL from the
sequence before selecting CURRVAL
ORA-08003:
sequence string.NEXTVAL exceeds internal limits
Cause: The sequence was created with
unsafe values for some of the parameters. The calculation of NEXTVAL cannot be
made because it exceeds the legal represention size.
Action: Alter or recreate the sequence
number with legal limits.
ORA-08004:
sequence string.NEXTVAL string stringVALUE
and cannot be instantiated
Cause: instantiating NEXTVAL would
violate one of MAX/MINVALUE
Action: alter the sequence so that a
new value can be requested
ORA-08005:
specified row does not exist
Cause: A row with the given rowid
does not exist in any of the tables given
Action: check the query for
misspellings of table names and the rowid
ORA-08006:
specified row no longer exists
Cause: the row has been deleted by
another user since the operation began
Action: re-try the operation
ORA-08007:
Further changes to this block by this transaction not allowed
Cause: Max locks have been reached
for this transaction in this block
Action: Commit changes
ORA-08008:
another instance is mounted with USE_ROW_ENQUEUES = string
Cause: the shared instance being
started does not have the same value for use_row_enqueues as already running
instances
Action: ensure that all instances'
INIT.ORA files specify the same value for the parameter 'use_row_enqueues'
ORA-08100:
index is not valid - see trace file for diagnostics
Cause: Validate Index detected an
inconsistency in its argument index
Action: Send trace file to your
customer support representative
ORA-08101:
index key does not exist file string: (root string,
node string) blocks (string)
Cause: Internal error: possible
inconsistency in index
Action: Send trace file to your
customer support representative, along with information on reproducing the
error
ORA-08102:
index key not found, obj# string, file string,
block string (string)
Cause: Internal error: possible
inconsistency in index
Action: Send trace file to your
customer support representative, along with information on reproducing the
error
ORA-08103:
object no longer exists
Cause: The object has been deleted by
another user since the operation began, or a prior incomplete recovery restored
the database to a point in time during the deletion of the object.
Action: Delete the object if this is
the result of an incomplete recovery.
ORA-08104:
this index object string is being online built or rebuilt
Cause: the index is being created or
rebuild or waited for recovering from the online (re)build
Action: wait the online index build or
recovery to complete
ORA-08105:
Oracle event to turn off smon cleanup for online index build
Cause: set this event only under the
supervision of Oracle development
Action: debugging only
ORA-08106:
cannot create journal table string.string
Cause: The online index builder could
not create its journal table
Action: rename your table in conflict
or rerun the SQL statement
* there may
be a concurrent online index rebuild on the same object.
ORA-08108:
may not build or rebuild this type of index online
Cause: only support normal index or
IOT top-level index
Action: change your index type
ORA-08109:
nosort is not a supported option for online index build
Cause: may not specify nosort for
online index build
Action: get rid of nosort in the index
creation command
ORA-08110:
Oracle event to test SMON cleanup for online index build
Cause: Oracle Kernel test only
Action: Donot set this event(for test
only)
ORA-08111:
a partitioned index may not be coalesced as a whole
Cause: User attempted to coalesce a
partitioned index using ALTER INDEX COALESCE statement, which is illegal
Action: Coalesce the index a
(sub)partition at a time (using ALTER INDEX MODIFY (sub)PARTITION COALESCE)
ORA-08112:
a composite partition may not be coalesced as a whole
Cause: User attempted to coalesce a
composite partition
Action: Coalesce the index a
subpartition at a time (using ALTER INDEX MODIFY SUBPARTITION COALESCE)
ORA-08113:
composite partition index may not be compressed
Cause: User attempted to compress a
composite partition index
Action: create uncompressed composite
partition index
ORA-08114:
can not alter a fake index
Cause: User attempted to alter a fake
index
Action: drop fake index
ORA-08115:
can not online create/rebuild this index type
Cause: User attempted to create index
type that online doesnot support
Action: use offline index
create/rebuild command
ORA-08116:
can not acquire dml enough lock(S mode) for online index build
Cause: User attempted to create index
online without allowing DML Share lock
Action: allow DML share lock on the
base table
ORA-08117:
Index Organized Table operation released its block pin
Cause: Block maintenance forced the
release of a block pin
Action: Contact your customer support
representative
ORA-08118:
Deferred FK constraints cannot be enforced, index too big (string)
Cause: Deferred Foreign Key
constraints cannot be enforced due to the index key being too big and built on
a non-default DB_BLOCK_SIZE.
Action: First try to drop the Foreign
Key and then the primary key.
ORA-08119:
The new initrans will make the index too big
Cause: Specifying the initrans need
additional space to hold the index key which might make the index too big
Action: Try giving a smaller initrans
value
ORA-08120:
Need to create SYS.IND_ONLINE$ table in order to (re)build index
Cause: Alter index Build/Rebuild
online require existing of SYS.IND_ONLINE$ table.
Action: User/DBA needs to create
sys.ind_online$ before alter the index /rdbms/admin/catcio.sql contains script
to create ind_online$.
ORA-08121:
Number of indexes need to be maintained offline exceeds limit for DML
Cause: Too many indexes needed to be
maintained. The limit is 2^16 indexes for each DML statement
Action: Make sure the index
maintainance is online. If indexes need to be maintained offline, drop some
indexes.
ORA-08122:
Online (re)build of index rolled back due to DML conflict
Cause: The online (re)build journal
is inconsistent with ongoing DML and cannot be used successfully to complete
the online index (re)build.
Action: Reissue the online (re)build
operation, after performing any cleanup, if needed.
ORA-08175:
discrete transaction restriction violated (string)
Cause: An attempt was made to perform
an action that is not currently supported in a discrete transaction.
Action: Rollback the transaction, and
retry it as a normal transaction.
ORA-08176:
consistent read failure; rollback data not available
Cause: Encountered data changed by an
operation that does not generate rollback data : create index, direct load or
discrete transaction.
Action: In read/write transactions,
retry the intended operation. Read only transactions must be restarted.
ORA-08177:
can't serialize access for this transaction
Cause: Encountered data changed by an
operation that occurred after the start of this serializable transaction.
Action: In read/write transactions,
retry the intended operation or transaction.
ORA-08178:
illegal SERIALIZABLE clause specified for user INTERNAL
Cause: Serializable mode is not
supported for user INTERNAL.
Action: Reconnect as another user and
retry the SET TRANSACTION command.
ORA-08179:
concurrency check failed
Cause: Encountered data changed by an
operation that occurred after a specific snapshot. This is usually used to
indicate that a particular cached copy of a datablock is stale. This is used
for internal use for now.
Action: refresh the cached copy of the
datablock and retry operation.
ORA-08180:
no snapshot found based on specified time
Cause: Could not match the time to an
SCN from the mapping table.
Action: try using a larger time.
ORA-08181:
specified number is not a valid system change number
Cause: supplied scn was beyond the
bounds of a valid scn.
Action: use a valid scn.
ORA-08182:
operation not supported while in Flashback mode
Cause: user tried to do dml or ddl
while in Flashback mode
Action: disable Flashback and
re-attempt the operation
ORA-08183:
Flashback cannot be enabled in the middle of a transaction
Cause: user tried to do Flashback in
the middle of a transaction
Action: do a commit
ORA-08184:
attempting to re-enable Flashback while in Flashback mode
Cause: as stated above
Action: disable first before
re-enabling
ORA-08185:
Flashback not supported for user SYS
Cause: user logged on as SYS
Action: logon as a different (non SYS)
user.
ORA-08186:
invalid timestamp specified
Cause: as stated above
Action: enter a valid timestamp
ORA-08187:
snapshot expression not allowed here
Cause: A snapshot expression using AS
OF was specified when not allowed.
Action: Do not use the AS OF clause
ORA-08189:
cannot flashback the table because row movement is not enabled
Cause: An attempt was made to perform
Flashback Table operation on a table for which row movement has not been
enabled. Because the Flashback Table does not preserve the rowids, it is
necessary that row movement be enabled on the table.
Action: Enable row movement on the
table
ORA-08190:
restore point string is from a different incarnation of the
database
Cause: An attempt was made to perform
Flashback Table operation using a restore point from a different incarnation of
the database
Action: Provide a restore point from
the current database incarnation
ORA-08191:
Flashback Table operation is not supported on remote tables
Cause: An attempt was made to perform
Flashback Table operation on a remote table. This is not permitted.
Action: Do not perform a Flashback
Table operation on remote tables.
ORA-08192:
Flashback Table operation is not allowed on fixed tables
Cause: An attempt was made to perform
Flashback Table operation on a fixed table. This is not permitted.
Action: Do not perform a Flashback
Table operation on fixed tables.
ORA-08193:
Flashback Table operation is not allowed on temporary tables
Cause: An attempt was made to perform
Flashback Table operation on a temporary table. This is not permitted.
Action: Do not perform a Flashback
Table operation on temporary tables.
ORA-08194:
Flashback Table operation is not allowed on materialized views
Cause: An attempt was made to perform
Flashback Table operation on a materialized view. This is not permitted.
Action: Do not perform a Flashback
Table operation on materialized views or snapshot logs.
ORA-08195:
Flashback Table operation is not supported on partitions
Cause: An attempt was made to perform
Flashback Table operation on a partition. This is not permitted.
Action: Do not perform a Flashback
Table operation on partitions.
ORA-08196:
Flashback Table operation is not allowed on AQ tables
Cause: An attempt was made to perform
Flashback Table operation on AQ tables. This is not permitted.
Action: Do not perform a Flashback
Table operation on AQ tables.
ORA-08197:
Flashback Table operation is not supported on clustered tables
Cause: An attempt was made to perform
Flashback Table operation on a clustered table. This is not permitted.
Action: Do not perform a Flashback
Table operation on clustered tables.
ORA-08198:
Flashback Table is not supported on object tables, nested tables
Cause: An attempt was made to perform
Flashback Table operation on a object table or a nested table or a table with
nested table column. This is not permitted.
Action: Do not perform a Flashback
Table operation on such tables.
ORA-08199:
Flashback Table operation is not supported on this object
Cause: An attempt was made to perform
Flashback Table operation on an object on which the operation is not supported.
Action: Do not perform a Flashback
Table operation on such objects.
ORA-08205:
ora_addr: $ORACLE_SID not set in environment
Cause: The environment variable
ORACLE_SID is not set.
Action: Set the ORACLE_SID environment
variable.
ORA-08206:
ora_addr: cannot translate address file name
Cause: Cannot translate
$ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf.
Action: Ensure that ORACLE_HOME and
ORACLE_SID are properly set.
ORA-08207:
ora_addr: cannot open address file
Cause: The address file could not be
opened.
Action: Check that ORACLE is up. Check
that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and has correct
permissions.
ORA-08208:
ora_addr: cannot read from address file
Cause: The address file could not be
read.
Action: Check that the file
$(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and contains a single line of
text.
ORA-08209:
scngrs: SCN not yet initialized
Cause: The System Commit Number has
not yet been initialized.
Action: Contact your customer support
representative.
ORA-08210:
Requested I/O error
Cause: Oracle requested that an I/O
error be returned for this operation.
Action: This should not occur in
normal Oracle operation. Contact support.
ORA-08230:
smscre: failed to allocate SGA
Cause: The n_core system call failed,
maybe due to insufficient memory.
Action: Specify a smaller number of
buffers. Check INIT.ORA parameters.
ORA-08231:
smscre: unable to attach to SGA
Cause: The process cannot attach to
the SGA. This can happen if either the listener can't attach, or the process
cannot communicate with the listener.
Action: Verify that the instance is up
and running. Contact your customer support representative.
ORA-08232:
smsdes: cannot detach from SGA
Cause: Probably, the listener process
has died.
Action: Contact your customer support
representative.
ORA-08233:
smsdes: cannot unmap SGA
Cause: The n_core system call failed
while detaching from the SGA.
Action: Note nCX error returned;
contact your customer support representative.
ORA-08234:
smsget: cannot get instance listener address
Cause: The instance listener address
cannot be read from the sgadef file.
Action: Verify $(ORACLE_HOME) and
$(ORACLE_SID) are set correctly. Additional information gives error return from
ora_addr.
ORA-08235:
smsget: listener not on this node
Cause: A process wishing to attach to
the SGA is on a different node from its instance's listener.
Action: Verify $(ORACLE_HOME) and
$(ORACLE_SID) are set correctly. Contact your customer support representative.
ORA-08236:
smsget: cannot share subcube with listener
Cause: The n_share call failed,
probably because the listener has died.
Action: Check if the listener is
running, and contact your customer support representative.
ORA-08237:
smsget: SGA region not yet created
Cause: Attempting to attach to an SGA
which has not yet been created.
Action: Verify that the instance is
running. Contact your customer support representative.
ORA-08238:
smsfre: cannot detach from SGA
Cause: The n_core system call failed
while detaching from the SGA.
Action: Check nCX error, and contact
your customer support representative.
ORA-08243:
recursive audit operation attempted
Cause: A recursive operation
requiring audit was attempted in the middle of an auditing operation. The most
likely reason is space management operations needed to free up space in the
audit tablespace.
Action: Check space in the tablespace
for SYS.AUD$ and correct the problem.
ORA-08260:
ora_addr: cannot open nameserver
Cause: A process could not connect to
the nameserver.
Action: Make sure the nameserver is up
and running. Additional information gives nameserver's returned status.
ORA-08261:
ora_addr: cannot find name in nameserver
Cause: The listener nameserver entry
for an instance could not be found.
Action: Make sure the nameserver is up
and running. Additional information gives nameserver's returned status.
ORA-08263:
ora_addr: cannot free listener address
Cause: The listener nameserver entry
could not be freed
Action: Additional information gives
nameserver's returned status. Contact your customer support representative.
ORA-08264:
ora_addr: cannot close nameserver
Cause: The connection to the
nameserver could not be closed.
Action: Additional information gives
nameserver's returned status. Contact your customer support representative.
ORA-08265:
create_ora_addr: cannot open nameserver
Cause: A process could not connect to
the nameserver.
Action: Make sure the nameserver is up
and running. Additional information gives nameserver's returned status.
ORA-08266:
create_ora_addr: cannot register name in nameserver
Cause: The listener's addressing
information could not be registered.
Action: Make sure the nameserver is up
and running. Additional information gives nameserver's returned status.
ORA-08267:
destroy_ora_addr: cannot close nameserver
Cause: The connection to the
nameserver could not be closed.
Action: Additional information gives
nameserver's returned status. Contact your customer support representative.
ORA-08268:
create_ora_addr: cannot close nameserver
Cause: The connection to the
nameserver could not be closed.
Action: Additional information gives
nameserver's returned status. Contact your customer support representative.
ORA-08269:
destroy_ora_addr: cannot destroy name
Cause: The listener's addressing
information could not be removed.
Action: Additional information gives
nameserver's returned status. Contact your customer support representative.
ORA-08270:
sksachk: Illegal archival control string
Cause: Archive files cannot be
created with the given archival control string.
Action: Check that the volume exists
ORA-08271:
sksabln: Buffer size not large enough for archive control string
Cause: The given archival control
string expands into too many characters.
Action: Reduce archive control string
length.
ORA-08274:
Out of memory for environment variable
Cause: There is insufficient memory
to return the requested value
Action: Reduce memory usage and retry.
ORA-08275:
Environment variable unset
Cause: The requested environment
variable is not set
Action: Ensure that the variable name
requested is correct.
ORA-08276:
No room in nameserver for pid
Cause: There is no room to record the
pid for a background process
Action: Shutdown abort and restart the
database.
ORA-08277:
Cannot set environment variable
Cause: There is insufficient memory
to expand the environment.
Action: Reduce memory usage and retry.
ORA-08278:
Cannot get CPU statistics
Cause: Could not retrieve CPU times
because n_stat failed.
Action: Contact customer support.
ORA-08308:
sllfop: Cannot open file
Cause: Oracle could not open a file.
Action: Check the Unix errno returned
as additional information.
ORA-08309:
sllfop: Cannot fstat file
Cause: Oracle could not obtain
information about an open file.
Action: Check the Unix errno returned
as additional information.
ORA-08310:
sllfop: Bad value for recsize
Cause: An illegal value for the
record size was specified.
Action: Specify a value for the
recsize option that is greater than 0.
ORA-08311:
sllfop: bad value for maxrecsize
Cause: An illegal value for the
maximum record size was specified.
Action: Specify a value for the
maxrecsize option that is greater than 0.
ORA-08312:
sllfop: unrecognized processing option
Cause: An unrecognized processing
option was specified.
Action: Check the Oracle for nCUBE 2
User's Guide for valid options.
ORA-08313:
sllfop: could not allocate buffers
Cause: Memory for the load buffers
could not be allocated.
Action: Reduce the maximum record
size. Eliminate any unnecessary processes on your current node before running
SQL*Loader again.
ORA-08314:
sllfcf: Error closing file
Cause: An error occurred trying to
close a file.
Action: Check the Unix errno returned
as additional information.
ORA-08315:
sllfrb: Error reading file
Cause: An error occurred trying to
read from a file.
Action: Check the Unix errno returned
as additional information.
ORA-08316:
sllfsk: Error seeking in file.
Cause: The lseek system call returned
an error.
Action: Check the Unix errno returned
as additional information.
ORA-08317:
sllfsk: Error seeking in file.
Cause: The lseek system call returned
an error.
Action: Check the Unix errno returned
as additional information.
ORA-08318:
sllfsk: Error reading file
Cause: An error occurred trying to
read from a file.
Action: Check the Unix errno returned
as additional information.
ORA-08319:
sllfsk: Error reading file
Cause: An error occurred trying to
read from a file.
Action: Check the Unix errno returned
as additional information.
ORA-08320:
scnget: Call to scnget before scnset or scnfnd.
Cause: An internal error
Action: Contact your customer support
representative.
ORA-08321:
scnmin: NOT IMPLEMENTED YET
Cause: An internal error
Action: Contact your customer support
representative.
ORA-08322:
scnmin: open/convert of bias lock failed
Cause: A call to the lkmgr failed to
open and convert the bias lock
Action: Check to make sure the lkmgr
is up.
ORA-08323:
scnmin: close of bias lock failed
Cause: A call to the lkmgr failed to
close the bias lock
Action: Check to make sure the lkmgr
is up.
ORA-08330:
Printing not supported
Cause: An attempt was made to
automatically spool a file to the printer
Action: None
ORA-08331:
Wait operation timed out
Cause: Oracle timed out waiting for
an event
Action: Contact your Oracle support
representative
ORA-08332:
rollback segment #string specified not available
Cause: (same as 1545)
Action: (same as 1545). Also, make
sure you have created enough rollback segments for the number of instances you
are trying to start.
ORA-08340:
This command not allowed on nCUBE, only one thread is ever used.
Cause: An illegal command was
executed for the nCUBE platform.
Action: There is no need to issue this
command.
ORA-08341:
On nCUBE, this command can only be executed from instance 1.
Cause: A command that can only be
issued on instance 1 was issued elsewhere.
Action: Log on to instance 1 and
repeat the command.
ORA-08342:
sropen: failed to open a redo server connection
Cause: An error occurred trying to
connect to the redo server.
Action: The OS specific error message
should tell you what to do.
ORA-08343:
srclose: failed to close a redo server connection
Cause: An error occurred trying to
close the redo server connection.
Action: The OS specific error message
should tell you what to do.
ORA-08344:
srapp: failed to send redo data to the redo server
Cause: An error occurred trying to
send redo to the redo server.
Action: The OS specific error message
should tell you what to do.
ORA-08401:
invalid compiler name: string
Cause: An invalid compiler name
was passed to a UTL_PG conversion routine.
Action: Correct the compiler name
parameter in the PL/SQL code that called the conversion routine.
ORA-08412:
error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning
message
Cause: The WMSGBSIZ is the maximun
size for warning message block, it is recommanded to be 1024 bytes to 8 kbytes.
Action: Defined WMSGBLK of size
between 1k to 8k bytes and update the WMSGBSIZ to the sizeof(WMSGBLK).
ORA-08413:
invalid compiler type in FORMAT parameter at string
Cause: An invalid compiler type is
defined in format control block. The format control block is invalid.
Action: Check to be sure that the
format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or
MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or
modified by the PL/SQL procedure.
ORA-08414:
error encountered in string
Cause: The function
returned an error. Where may be: RAW_TO_NUMER NUMBER_TO_RAW
RAW_TO_NUMBER_FORMAT NUMBER_TO_RAW_FORMAT MAKE_NUMBER_TO_RAW_FORMAT
MAKE_RAW_TO_NUMBER_FORMAT
Action: to take.
ORA-08429:
raw data has invalid digit in display type data
Cause: The input raw buffer passed to
a UTL_PG RAW_TO_NUMBER conversion routine contained invalid data. The picture
mask parameter specified a digit, but the corresponding input from the raw data
did not contain a valid digit.
Action: Either the input data is
incorrect, or the picture mask is incorrect. Correct the appropriate item.
ORA-08430:
raw data missing leading sign
Cause: The input raw buffer passed to
a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask
options parameter specified a leading sign.
Action: Correct the input raw data or
the mask options so that they match.
ORA-08431:
raw data missing zero as defined in picture
Cause: The picture mask parameter
passed to a UTL_PG RAW_TO_NUMBER conversion routine contained a zero, but the
corresponding input from the raw data was not a zero.
Action: Either the input data is
incorrect, or the picture mask is incorrect. Correct the appropriate item.
ORA-08432:
raw data has invalid floating point data
Cause: The input raw data passed to a
UTL_PG RAW_TO_NUMBER conversion routine contained invalid floating point data.
Action: Correct the input raw data.
ORA-08433:
invalid picture type in convert raw to number
Cause: The picture mask parameter
passed to a UTL_PG RAW_TO_NUMBER conversion routine contained non-numeric
characters, but the conversion was to a numeric data type.
Action: Correct the picture mask
parameter.
ORA-08434:
raw data has invalid trailing sign
Cause: The input raw buffer passed to
a UTL_PG RAW_TO_NUMBER conversion routine had no trailing sign, but the mask
options parameter specified a trailing sign.
Action: Correct the input raw data or
the mask options so that they match.
ORA-08435:
PICTURE MASK missing the leading sign when SIGN IS LEADING specified
Cause: The input MASK passed to a
UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask
options parameter specified a leading sign.
Action: Correct the input raw data or
the mask options so that they match.
ORA-08436:
raw data has invalid sign digit
Cause: The input raw buffer passed to
a UTL_PG RAW_TO_NUMBER conversion routine had an invalid sign digit in the
position where the picture mask specified a sign.
Action: Correct the input raw data or
the picture mask so that they match.
ORA-08437:
invalid picture type in picture mask
Cause: The picture mask parameter
passed to a UTL_PG NUMBER_TO_RAW conversion routine contained non-numeric
characters, but the conversion was to a numeric data type.
Action: Correct the picture mask
parameter.
ORA-08440:
raw buffer is too short to hold converted data
Cause: The output raw buffer passed
to a UTL_PG NUMBER_TO_RAW conversion routine was not large enough to contain
the results of the conversion based on the picture mask.
Action: Increase the raw buffer size
to the size necessary to hold the entire result of the conversion.
ORA-08441:
closed parenthesis missing in picture mask
Cause: A closed parenthesis was
missing from the picture mask passed to a UTL_PG conversion routine.
Action: Correct the picture mask.
ORA-08443:
syntax error in BLANK WHEN ZERO clause in mask options
Cause: A syntax error was found in
the BLANK WHEN ZERO clause in the mask options parameter passed to a UTL_PG
conversion routine. Valid specifications are: BLANK ZERO BLANK ZEROS BLANK
ZEROES BLANK WHEN ZERO BLANK WHEN ZEROS BLANK WHEN ZEROES
Action: Correct the mask options
parameter.
ORA-08444:
syntax error in JUSTIFIED clause in mask options
Cause: A syntax error was found in
the JUSTIFIED clause in the mask options parameter passed to a UTL_PG
conversion routine. Valid specifications are: JUST JUST RIGHT JUSTIFIED
JUSTIFIED RIGHT
Action: Correct the mask options
parameter.
ORA-08445:
syntax error in SIGN clause in mask options
Cause: A syntax error was found in
the SIGN clause in the mask options parameter passed to a UTL_PG conversion
routine. Valid specifications are: SIGN LEADING SIGN LEADING SEPARATE SIGN
LEADING SEPARATE CHARACTER SIGN TRAILING SIGN TRAILING SEPARATE SIGN TRAILING
SEPARATE CHARACTER SIGN IS LEADING SIGN IS LEADING SEPARATE SIGN IS LEADING
SEPARATE CHARACTER SIGN IS TRAILING SIGN IS TRAILING SEPARATE SIGN IS TRAILING
SEPARATE CHARACTER
Action: Correct the mask options
parameter.
ORA-08446:
syntax error in SYNCHRONIZED clause in mask options
Cause: A syntax error was found in
the SYNCHRONIZED clause in the mask options parameter passed to a UTL_PG
conversion routine. Valid specifications are: SYNC SYNC LEFT SYNC RIGHT
SYNCHRONIZED SYNCHRONIZED LEFT SYNCHRONIZED RIGHT
Action: Correct the mask options
parameter.
ORA-08447:
syntax error in USAGE clause in mask options
Cause: A syntax error was found in
the USAGE clause in the mask options parameter passed to a UTL_PG conversion
routine. Valid specifications are: USAGE DISPLAY USAGE COMP USAGE COMP-3 USAGE
COMP-4 USAGE COMPUTATIONAL USAGE COMPUTATIONAL-3 USAGE COMPUTATIONAL-4 USAGE IS
DISPLAY USAGE IS COMP USAGE IS COMP-3 USAGE IS COMP-4 USAGE IS COMPUTATIONAL
USAGE IS COMPUTATIONAL-3 USAGE IS COMPUTATIONAL-4
Action: Correct the mask options
parameter.
ORA-08448:
syntax error in DECIMAL-POINT environment clause
Cause: A syntax error was found in the
DECIMAL-POINT environment clause parameter passed to a UTL_PG conversion
routine. Valid specifications are: DECIMAL-POINT IS COMMA
Action: Correct the environment clause
parameter.
ORA-08449:
invalid numeric symbol found in picture mask
Cause: An invalid numeric symbol was
found in the picture mask parameter passed to a UTL_PG conversion routine.
Action: Correct the picture mask
parameter.
ORA-08450:
invalid specification of CR in picture mask
Cause: The CR suffix was incorrectly
specified in the picture mask parameter passed to a UTL_PG conversion routine.
The CR suffix can only appear at the end of a picture mask.
Action: Correct the picture mask
parameter.
ORA-08451:
invalid specification of DB in picture mask
Cause: The DB suffix was incorrectly
specified in the picture mask parameter passed to a UTL_PG conversion routine.
The DB suffix can only appear at the end of a picture mask.
Action: Correct the picture mask
parameter.
ORA-08452:
specification of E in picture mask is unsupported
Cause: The floating point exponent
symbol 'E' was specified in the picture mask parameter passed to a UTL_PG
conversion routine. The floating point data type is currently not supported by
the UTL_PG conversion routines.
Action: Correct the picture mask
parameter, and the data, if necessary.
ORA-08453:
more than one V symbol specified in picture mask
Cause: The picture mask passed to a
UTL_PG conversion routine contained more than one decimal point indicator
('V'). Only one decimal point indicator is allowed in the picture mask.
Action: Correct the picture mask
parameter.
ORA-08454:
more than one S symbol specified in picture mask
Cause: The picture mask passed to a
UTL_PG conversion routine contained more than one operational sign indicator
('S'). Only one operational sign indicator is allowed in the picture mask.
Action: Correct the picture mask
parameter.
ORA-08455:
syntax error in CURRENCY SIGN environment clause
Cause: A syntax error was found in
the CURRENCY SIGN environment clause parameter passed to a UTL_PG conversion
routine. Valid specifications are: CURRENCY SIGN IS x where x is a valid
currency sign
Action: Correct the environment clause
parameter.
ORA-08456:
no sign in picture mask but SIGN clause in mask options
Cause: The picture mask parameter
passed to a UTL_PG conversion routine contained no sign symbol ('S', '+', or
'-'), but the mask options parameter contained a SIGN clause. A sign symbol is
required in the picture mask parameter when the mask options parameter contains
a SIGN clause.
Action: Correct the picture mask
parameter or the mask options parameter.
ORA-08457:
syntax error in SEPARATE CHARACTER option of SIGN clause
Cause: A syntax error was found in
the SEPARATE CHARACTER option of the SIGN clause in the mask options parameter
passed to a UTL_PG conversion routine. Valid specifications are: SEPARATE
SEPARATE CHARACTER
Action: Correct the mask options
parameter.
ORA-08458:
invalid format parameter
Cause: The format parameter passed to
a UTL_PG conversion routine was invalid. The format parameter should have been
built by a prior call to either MAKE_RAW_TO_NUMBER_FORMAT or
MAKE_NUMBER_TO_RAW_FORMAT.
Action: Check to be sure that the
format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or
MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or
modified by the PL/SQL procedure.
ORA-08459:
invalid format parameter length
Cause: The format parameter passed to
a UTL_PG conversion routine was not the correct length. Format parameters must
be 2048 bytes in length.
Action: Check to be sure that the
format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or
MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or
modified by the PL/SQL procedure.
ORA-08460:
invalid environment clause in environment parameter
Cause: The environment parameter
passed to a UTL_PG conversion routine contained an unsupported or invalid
environment clause. Only the CURRENCY SIGN and the DECIMAL-POINT IS COMMA
environment clauses are supported.
Action: Correct the environment
parameter.
ORA-08462:
raw buffer contains invalid decimal data
Cause: The input raw buffer passed to
a UTL_PG RAW_TO_NUMBER conversion routine contains invalid decimal data.
Action: Correct the input data.
ORA-08463:
overflow converting decimal number to Oracle number
Cause: The output variable passed to
a UTL_PG RAW_TO_NUMBER was not large enough to hold the Oracle number resulting
from the input decimal number.
Action: Be sure that the input decimal
number is valid, and besure that the output variable is large enough to hold
the Oracle number value.
ORA-08464:
input raw decimal data contains more than 42 digits
Cause: The input raw buffer passed to
a UTL_PG RAW_TO_NUMBER conversion routine contained more than 42 digits. This
exceeds the maximum size of an Oracle number.
Action: Correct the raw input buffer.
ORA-08465:
input mask contains more than 32 characters
Cause: The input mask passed to
UTL_PG numeric conversion routine contained more the 32 characters.
Action: Correct the mask input buffer.
ORA-08466:
raw buffer length string is too short for string
Cause: The input raw buffer passed to
a UTL_PG RAW_TO_NUMBER conversion routine was less than %s bytes long, but the
picture mask parameter specified that %s bytes of input data were to be
converted.
Action: Either the input data is
incorrect, or the picture mask is incorrect. Correct the appropriate item.
ORA-08467:
error converting Oracle number to string
Cause: An error occurred when
converting an Oracle number to a COBOL of: DISPLAY COMP-3 or
character variable. The Oracle number was not in the correct format.
Action: Correct the call to the
conversion routine. The input must be a valid Oracle number variable.
ORA-08468:
mask option string is not supported
Cause: The mask option
was passed to a UTL_PG conversion routine, but is not supported by UTL_PG. The
can be: USAGE IS POINTER USAGE IS INDEX USAGE IS COMP-1 USAGE IS
COMP-2 POINTER
Action: Remove the from
the mask options parameter in the PL/SQL call to UTL_PG.
ORA-08469:
must use the SIGN IS SEPARATE clause in mask options
Cause: A signed numeric entry with
DISPLAY usage was converted using a non-defaulted character set and its PICTURE
character-string contains an S. In these circumstances, a SIGN IS SEPARATE
clause must be specified in the mask options.
Action: Either specify a valid SIGN IS
SEPARATE clause in the mask options, use the defaulted character set, or don't
specify an S in the PICTURE character-string.
ORA-08498:
Warning: picture mask 'string' overrides picture mask option 'USAGE
IS string' to 'USAGE IS DISPLAY'
Cause: Picture mask USAGE option was
overridden by the picture mask.
Action: This is an informational
message only. The message may be eliminated by changing the USAGE option to
match the picture mask.
ORA-08499:
Warning: picture mask options 'string' ignored by UTL_PG
Cause: Picture mask options such as
OCCUR, SYNC and others are not processed by the UTL_PG numeric conversion
routines.
Action: This is an informational
message only. The message may be eliminated by removing the unnecessary picture
mask options from the parameter list passed to the UTL_PG routine.