Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
This section lists messages generated when using the UPI to the Oracle Server. Precompilers and SQL*Forms are examples of products that use the UPI.
If you are using Trusted Oracle, see the Trusted Oracle documentation for information about error messages in that environment.
Cause: A host language program attempted to open too many cursors. The initialization parameter OPEN_CURSORS determines the maximum number of cursors per user.
Action: Modify the program to use fewer cursors. If this error occurs often, shut down Oracle, increase the value of OPEN_CURSORS, and then restart Oracle.
Cause: Either a host language program call specified an invalid cursor or the values of the AREASIZE and MAXOPENCURSORS options in the precompiler command were too small. All cursors must be opened using the OOPEN call before being referenced in any of the following calls: SQL, DESCRIBE, NAME, DEFINE, BIND, EXEC, FETCH, and CLOSE. The Logon Data Area (LDA) must be defined by using OLON or OLOGON. If the LDA is not defined, this message is issued for the following calls: OPEN, COM, CON, ROL, and LOGOFF.
Action: Check the erroneous call statement. Specify a correct LDA area or open the cursor as required. If there is no problem with the cursor, it may be necessary to increase the AREASIZE and MAXOPENCURSORS options before precompiling.
Cause: In a host language program, a FETCH call was issued out of sequence. A successful parse-and-execute call must be issued before a fetch. This can occur if an attempt was made to FETCH from an active set after all records have been fetched. This may be caused by fetching from a SELECT FOR UPDATE cursor after a commit. A PL/SQL cursor loop implicitly does fetches and may also cause this error.
Action: Parse and execute a SQL statement before attempting to fetch the data.
Cause: A host language program call referenced a cursor with no associated parsed SQL statement. A SQL call (for example, OSQL3) must be used to pass a SQL statement to Oracle and to associate the statement with an open cursor. A cursor must already have an associated SQL statement if referenced in any of the following calls: DESCRIBE, NAME, DEFINE, BIND, EXECUTE, and FETCH.
Action: Do the SQL call, for example, OSQL, to pass the required SQL statement before referencing the cursor.
Cause: An attempt was made to use automatic logon on a system not supporting this feature.
Action: Provide the complete username and password to log on to Oracle.
Cause: An invalid password was given when logging on.
Action: Provide a valid password.
Cause: A program issued a BIND call for a variable not listed in the associated SQL statement. Only those variables prefixed by either a colon (:) or ampersand (&) in the SQL statement may be referenced in a BIND call, OBIND or OBINDN. This error may also be caused by a mismatch between a Precompiler program and the related library, SQLLIB.
Action: Modify the BIND call to reference one of the substitute variables specified in the associated SQL statement.
Cause: A reference was made to a variable not listed in the SELECT clause. In OCI, this can occur if the number passed for the position parameter is less than one or greater than the number of variables in the SELECT clause in any of the following calls: DESCRIBE, NAME, or DEFINE. In SQL*Forms or SQL*Report, specifying more variables in an INTO clause than in the SELECT clause also causes this error.
Action: In OCI, specify a position number between 1 and the number of variables in the SELECT clause. In SQL*Forms or SQL*Report, specify an equal number of variables in the SELECT and INTO clauses.
Cause: A SQL statement containing substitution variables was executed without all variables bound. All substitution variables must have a substituted value before the SQL statement is executed.
Action: In OCI, use an OBIND or OBINDN call to substitute the required values.
Cause: A host language program call did not pass all required parameters. The syntax and parameter description for each call is shown in the Programmer's Guide to the Oracle Precompilers.
Action: Check the syntax for the call and enter all required parameters.
Cause: One of the following:
Action: For the above causes:
Cause: An attempt was made to use Oracle7 compatibility mode when accessing Oracle Version 6.
Action: Use V6 SQL language type. You may need to use the SET COMPATIBILITY V6 command.
Cause: A host language program issued an Oracle call, other than OLON or OLOGON, without being logged on to Oracle. This can occur when a user process attempts to access the database after the instance it is connected to terminates, forcing the process to disconnect.
Action: Log on to Oracle, by calling OLON or OLOGON, before issuing any Oracle calls. When the instance has been restarted, retry the action.
Cause: The user interrupted an Oracle operation by entering CTRL-C, Control-C, or another canceling operation. This forces the current operation to end. This is an informational message only.
Action: Continue with the next operation.
Cause: A user tried to log on to Oracle while an instance shutdown was in progress. Oracle logons are disabled while Oracle is being shut down.
Action: Wait until Oracle is brought back up before attempting to log on.
Cause: This is an internal error message not usually issued.
Action: Contact customer support.
Cause: The cursor is in an invalid state.
Action: Ensure the appropriate OCI/UPI function is called after the fetch and before the offending function.
Cause: An invalid username or password was entered in an attempt to log on to Oracle. The username and password must be the same as was specified in a GRANT CONNECT statement. If the username and password are entered together, the format is: username/password.
Action: Enter a valid username and password combination in the correct format.
Cause: An attempt was made to fetch data using the LONG fetch option, but the specified column was not LONG.
Action: Re-execute the fetch without the LONG fetch option or create the table with a LONG column.
Cause: The user side memory allocator returned an error.
Action: Increase the size of the process heap or switch to the old set of calls.
Cause: This is an internal error message not usually issued.
Action: Contact customer support.
Cause: This is an internal error message not usually issued.
Action: Contact customer support.
Cause: The attempted database operation does not conform to the user programming interface (UPI) for the two communicating Oracle servers.
This problem occurs when you use a 7.0.13 server and try to use PL/SQL or remote procedure calls on a 7.0.12 server.
Action: You may need to upgrade one or more of your Oracle servers or relink your user-side application with new libraries.
Cause: The cursor number is not a valid open cursor.
Action: Make sure that the cursor is open.
Cause: An OCI program call specified an invalid datatype. In OCI calls, Oracle datatypes are specified as numbers between 1 and 7. Datatypes are described in the Programmer's Guide to the Oracle Precompilers.
Action: Check the datatype description and enter the correct number for the datatype.
Cause: An integer parameter to a UPI function is out of range. This is an internal error message not usually issued.
Action: Contact customer support.
Cause: There is more than one long buffer in the bind list.
Action: Change the buffer size to be less than 255 for the bind variable bound to a normal column.
Cause: An attempt was made to use a bind variable in a SQL data definition statement; for example, a CREATE TABLE AS SELECT statement in which the SELECT's WHERE clause refers to a variable.
Action: Remove the bind variable. Then retry the SQL statement.
Cause: The SELECT... INTO specified in the bind call does not correspond to a variable in the SQL statement.
Action: If it is not possible to correct the statement, call customer support.
Cause: An attempt was made to change the current username or password without the appropriate privilege. This error also occurs if attempting to UPDATE a table with only SELECT privileges, if attempting to CONNECT INTERNAL, or if attempting to install a database without the necessary operating-system privileges.
Action: Ask the database administrator to perform the operation or grant the required privileges.
Cause: This is an internal error message related to Export/Import.
Action: Contact customer support.
Cause: An attempt was made to log on while Oracle is being started up or shut down.
Action: Wait a few minutes. Then retry the operation.
Cause: Oracle was not started up. Possible causes include the following:
The SGA requires more space than was allocated for it.
The operating system variable pointing to the instance was improperly defined.
Action: Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. Retry after Oracle has been initialized.
If Oracle has been initialized, then on some operating systems, verify that Oracle was linked correctly. See the platform-specific Oracle documentation.
Cause: Logins were disallowed because an instance started in restricted mode. Only users with the RESTRICTED SESSION system privilege can log on.
Action: Request that Oracle be restarted without the restricted option or obtain the RESTRICTED SESSION system privilege.
Cause: Unable to find bind context on user side.
Action: Make sure that the variable being bound is in the SQL statement.
Cause: An attempt was made to process a complex SQL statement that consumed all available memory of the cursor.
Action: Simplify the complex SQL statement.
Cause: An attempt was made to write datafile headers in an old format. The new format cannot be used until after the database has been verified as being compatible with this software version.
Action: Open the database to advance to the new file formats, then repeat the operation. If the operation is required before the database can be opened, use the previous software release to do the operation.
Cause: An attempt was made to use another user's view without the necessary privileges on the underlying objects of the view.
Action: Obtain the necessary privileges or do not perform the offending operation.
Cause: There are multi-byte characters in the password or some characters in the password are not in the US7ASCII range.
Action: Retry password with valid characters.
Cause: The pointer to the HOSTDEF extension in HOSTDEF is null.
Action: Report as a bug to customer support.
Cause: An attempt was made to detach a session that has open cursors.
Action: Close all the cursors before detaching the session.
Cause: The application code corrupted some of the user memory.
Action: Make certain that the application code is not overwriting memory. Contact customer support.
Cause: An attempt was made to bind a buffer whose total size would exceed the maximum size allowed. The total array size for arrays is calculated as (element_size) * (number of elements).
Action: Reduce the buffer size.
Cause: An attempt was made to connect to a userid that does not have create session privilege.
Action: If required, GRANT the user the CREATE SESSION privilege.
Cause: Oracle could not extend the current area any further because the operating system would not supply any more space. A system-specific message should appear following this message.
Action: Close some cursors and try again or check operating system quotas to use more virtual memory. See your operating system-specific Oracle documentation.
Cause: This message is displayed after a previous message to provide more specific information.
Action: See the cause and action for the previous message.
Cause: The user of the procedure specified a deferred RPC that does not exist.
Action: Ensure that the procedure was specified correctly and that the replication process can locate the procedure.
Cause: This error occurs when a newer server version requests from an older server version an operation that is not supported.
Action: You may need to upgrade one or more of your Oracle servers or relink your user application with new libraries.
Cause: Oracle could not open a new context area because the operating system would not supply any more space. A system-specific message should appear following this message.
Action: Close some cursors and try again or check operating system quotas to use more virtual memory. See your operating system-specific Oracle documentation.
Cause: The deferred RPC data in SYS.DEF$_CALL is corrupted.
Action: Contact customer support.
Cause: LOG_ARCHIVE_DUPLEX_DEST is not specified while LOG_ARCHIVE_MIN_SUCCEED_DEST is set to 2.
Action: Either specify LOG_ARCHIVE_DUPLEX_DEST or reduce LOG_ARCHIVE_MIN_SUCCEED_DEST to 1.
Cause: A bind variable or other user area could not be read by Oracle.
Action: Check that binds are done correctly on valid user buffers, then retry the operation.
Cause: A define, FETCH... INTO or SELECT... INTO, variable or other user area could not be written to by Oracle.
Action: Check that INTO variables and indicators are correctly specified. Then retry the operation.
Cause: The reference to a block.field identifier in a user exit is incorrect or ambiguous, probably because it is misspelled or incomplete.
Action: Check syntax and identifier spelling. Then correct the reference.
Cause: An attempt was made to delete a non-existent HSTDEF extension.
Action: Contact customer support.
Cause: The client application attempted to bind a variable or execute a cursor opened in a PL/SQL block before the statement was parsed.
Action: Ensure the statement is parsed before a bind or execute.
Cause: The client application attempted to bind an array of cursors or attempted to repeatedly execute against a PL/SQL block with a bind variable of type cursor.
Action: Bind a single cursor or execute the PL/SQL block one.
Cause: You are using an Oracle client application linked with version 7 (or lower) libraries and you attempted to start up a V8 (or higher) server.
Action: Use a client application linked with V8 (or higher) libraries.
Cause: An attempt was made to run an older, obsolete Oracle Server.
Action: Upgrade the server.
Cause: An attempt was made to perform an operation before Oracle was started.
Action: Start up Oracle. Then retry the operation.
Cause: An attempt was made to stop Oracle, but Oracle was not running.
Action: No action required.
Cause: An illegal internal operation was attempted. This is an internal error message not usually issued.
Action: Contact customer support.
Cause: An attempt was made to shut down Oracle inside a logon session.
Action: Log off before shutting down Oracle.
Cause: An attempt was made to log on while already logged on.
Action: No action required.
Cause: Oracle does not support multiple logons per process.
Action: No action required.
Cause: A failure occurred during initialization of the background processes.
Action: Refer to the diagnostic information in the accompanying message stack or in the trace file and take appropriate action.
Cause: A failure occurred during processing of the initialization parameters during system startup.
Action: Refer to the diagnostic information in the accompanying message stack and take appropriate action.
Cause: There was an error when the database or control file was created.
Action: Check the message signaled when the database was first created or when the control file was re-created. Take appropriate actions to re-create the database or a new control file.
Cause: A failure occurred during system shutdown.
Action: Refer to the diagnostic information in the accompanying message stack and take appropriate action.
Cause: An attempt was made to start Oracle while it was already running.
Action: Shut down Oracle first, if you want to restart it.
Cause: ROW_LOCKING = ALWAYS is specified in INIT.ORA file. This feature is not supported by ORACLE without the transaction processing option.
Action: Remove ROW_LOCKING = ALWAYS from the INIT.ORA file or set it to DEFAULT or INTENT.
Cause: The value of the given initialization parameter is required to be the same for all servers in the parallel configuration.
Action: Change the value in the initialization parameter file to match that of the other control files.
Cause: The failing OCI call contains an argument with an invalid value.
Action: Use valid argument values. For more information, see the Programmer's Guide to the Oracle Call Interface, Volume II: OCI Reference and the appropriate programming language supplement.
Cause: Errors were encountered when the named procedure was executed as a deferred, remote procedure call.
Action: Correct the cause of the preceding errors.
Cause: An attempt was made to roll back to a savepoint that was never established.
Action: No action required.
Cause: An attempt was made to start up Oracle by a user who is currently logged on.
Action: Log off. Then issue the STARTUP command.
Cause: Users are still logged on to the instance.
Action: Either wait for all users to log off or issue the SHUTDOWN IMMEDIATE command to force the users off the system. Alternatively, issue the SHUTDOWN ABORT command to shut down the database without waiting for users to be forced off.
Cause: The SHUTDOWN IMMEDIATE command was used to shut down a running Oracle instance, terminating any active operations.
Action: Wait for the instance to be restarted or contact the database administrator.
Cause: The SHUTDOWN command was used to shut down a running Oracle instance, disallowing any connects to Oracle.
Action: Wait for the instance to restart or contact the database administrator.
Cause: Unable to destroy the old SGA.
Action: Manually remove the old SGA. See your operating system-specific Oracle documentation for instructions. Then retry the STARTUP command.
Cause: The instance connected to was terminated abnormally, probably due to a SHUTDOWN ABORT. The current process was forced to disconnect from the instance.
Action: Contact the database administrator to determine when the instance is restarted. Attempt to reconnect after the instance is running again.
Cause: There is at lease one more session, other than the current one, logged in to the instance. ALTER DATABASE CLOSE is not permitted when other sessions are active.
Action: Find the other sessions and disconnect them. Then retry the ALTER DATABASE CLOSE command. Also, issue the SHUTDOWN IMMEDIATE command to force users off the system, or issue the SHUTDOWN ABORT command to shut down the database without waiting for users to be forced off.
Cause: An attempt was made to connect while the database is being closed with the ALTER DATABASE CLOSE command.
Action: Attempt to connect again when the database is open. Contact the database administrator to find out when the database will be open.
Cause: A DML cursor from the OTEX() call processed 0 rows when executed.
Action: Caller can either do a rollback or ignore the message and execute the rest of the cursors in the cursor array.
Cause: The program was linked with a different version of the server than the instance to which it is attempting to connect.
Action: Relink the program against the same version of Oracle as the instance or restart (startup force) the database using the program's version of the SERVER.
Cause: An attempt was made to shut down the database while a transaction was in progress.
Action: Either commit or rollback the current transaction and then attempt to shut down the database.
Cause: The application program interface could not insert or update a LONG column because of an internal error when a TTCGETV call fails. For example, a network read error or one of the parameters passed to the call is invalid.
Action: Retry the insert or update.
Cause: An attempt was made to mount a database in parallel mode with the initialization parameter SINGLE_PROCESS set to TRUE.
Action: Either mount the database in EXCLUSIVE mode or set the initialization parameter SINGLE_PROCESS to FALSE before starting the instance in parallel (shared) mode.
