Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
Cause: SQL*Module was unable to open a temporary file for internal use. There might be insufficient disk space, too many files, or read-only protection on the output directory.
Action: Check that there is enough disk space, that the limit for open files is set high enough (check with the system manager) and that protection on the directory allows opening a file for writing.
Cause: There is a syntax error in the SQL statement or the statement is not properly terminated in the module file.
Action: Correct the syntax of the SQL statement. If the error occurred at the end of the input file, check that the last SQL statement is properly terminated.
Cause: The symbol in a SQL descriptor is invalid.
Action: Check the statement syntax and spelling of the identifier and check that a reserved word was not accidentally used. If necessary, define the identifier in the declaration section of the module file.
Cause: A host variable defined in the procedure definition of the module file has an unsupported datatype or has a scale or precision outside the supported range.
Action: Redefine the host variable using a supported datatype. Check that the scale and precision of a numeric variable are in the accepted range.
Cause: A host variable used in SQL statement was not defined in the procedure definition or has an unsupported datatype.
Action: Declare the host variable in the procedure definition of the module file, making sure it has one of the supported datatypes.
Cause: The syntax in the SQL statement is faulty. The module compiler was expecting a host variable, but found something else.
Action: Check the syntax and the spelling, then correct the SQL statement.
Cause: SQL*Module is not able to open the input file that was specified with the INAME option. This error can result from any of the following:
Action: Check that the appropriate permission to read the file has been granted. Check that the name and directory hierarchy have been specified correctly. Rerun the compiler.
Cause: SQL*Module is not able to create the listing output file. This usually happens when write permissions do not exist on the current directory or on the directory specified for the LNAME option. It can also happen if the name or directory path is not legal or a directory on the path does not exist.
Action: Check the permissions on the specified path and file, or on the current directory if the LNAME option is not used.
Cause: SQL*Module is not able to create an output file, such as the specification file or the output code file. This usually happens when write permissions on the current directory or on the directory specified for the ONAME or SNAME options do not exist. It can also happen if the name or directory path is not legal or a directory on the path does not exist.
Action: Check the permissions on the specified path and file, or on the current directory if the ONAME or SNAME options are not used.
Cause: This is caused by a syntax error in the Module Language file. For example, if the SQL statement
SELECT ename INTO :name FORM emp WHERE ...
is in a module procedure, this message is raised. This message is not triggered by semantic errors. See MOD-00075.
Action: Correct the syntax error, then recompile.
Cause: The syntax in a SQL statement is faulty. The module compiler found an unexpected or illegal token.
Action: Check the syntax and the spelling, then correct the SQL statement.
Cause: The module compiler was unable to find information about an input host variable (bind variable) used in a SQL statement.
Action: Check that the input host variable is declared in the procedure definition of the module file and used properly in the SQL statement.
Cause: This message results from an internal error: an invalid value for the mode of a bind variable.
Action: Contact Oracle Support Services.
Cause: SQL*Module could not allocate enough memory to run or to perform some required action.
Action: Try killing some non-essential processes, then rerunning SQL*Module. On some operating systems, there may be a quota for the amount of memory the processes can allocate. See the system administrator. If necessary, increase memory for the machine.
Cause: The database connection or the username or the password that was specified was not correct. This message can result from an incorrect command-line specification or an incorrect specification of the username and/or password in the module AUTHORIZATION clause.
Action: Look up the error number in the ORA message chapters of this manual for more specific information on the failure. Correct the identifiers, then rerun SQL*Module.
Cause: An Oracle connection error occurred while the module was trying to log off, probably because Oracle has been shut down.
Action: Check that Oracle is available, then retry.
Cause: An indicator variable was not declared in the procedure definition as a 2-byte integer. Indicator variables must be defined as 2-byte integers.
Action: Redefine the indicator variable as a 2-byte integer.
Cause: A precompiler option was specified inline in an EXEC ORACLE statement. Some options can be specified only on the command line. For example, INAME cannot be specified inline.
Action: Respecify the precompiler option on the command line, instead of in an EXEC ORACLE statement. To see an online display of the precompiler options, enter the precompiler command (with no options) at the operating-system prompt.
Cause: The name of module command line option is used ambiguously.
Action: Respecify the full option name or an unambiguous abbreviation. To see an online display of module options, enter the MODADA command (with no options) at the operating system prompt.
Cause: The value specified for the module option is incorrect. That value is not appropriate for this module option.
Action: Respecify the option value appropriately.
Cause: The module compiler found an invalid module option name. Some possible causes follow:
Action: Check that the option exists and that its name is spelled correctly. To see an online display of the module options, enter the MODADA command (with no options) at the operating system prompt. Also check there is an equal sign between the option name and value.
Cause: No value was specified for a module option. Either the value is missing or there is space around the equal sign.
Action: Check that a value for each option has been specified and there is no space around the equal sign.
Cause: The module was unable to open the output file specified in the module option.
Action: Check that the search path to the file is correct, that sufficient privileges have been granted to access the file, and it is not locked by another user. Also check there is enough disk space and that the limit for open files is set high enough (check with the system manager).
Cause: The host language name is not specified in the LANGUAGE clause of the module file.
Action: Specify Ada (case is not significant) for the LANGUAGE clause.
Cause: The STORE_PACKAGE=YES option was entered, but an input file using the INAME option was not specified.
Action: Use INAME on the command line.
Cause: A host variable used in a SQL statement was not declared in the procedure definition or has an unsupported datatype.
Action: Declare the host variable in the procedure definition, making sure it has one of the supported datatypes.
Cause: The declared size of VARCHAR host variable exceeds the module limit of 65533 bytes.
Action: Check the declarations, making sure the size of each VARCHAR variable does not exceed the limit of 65533 bytes.
Cause: Two AT clauses, one in a DECLARE STATEMENT statement, the other in a DECLARE CURSOR statement, pertain to the same SQL statement. The AT clause may be specified with either DECLARE STATEMENT or DECLARE CURSOR, but not with both.
Action: Remove the AT clause from one of the statements.
Cause: The module found an error in a SQL statement or PL/SQL block.
Action: Refer to the indicated PL/SQL error message to correct the SQL statement or PL/SQL block.
Cause: The module found a PL/SQL block when expecting a SQL statement.
Action: Rewrite the statement using SQL syntax by replacing PL/SQL block.
Cause: While reading the input file, the module found a line longer than IRECLEN.
Action: Either shorten the input line or specify a larger IRECLEN value on the command line.
Cause: The authorization or license to run the MODADA compiler has expired.
Action: Call Oracle Support Services for assistance.
Cause: The authorization or license to run the MODADA compiler is about to expire.
Action: Call Oracle Support Services for assistance.
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
Cause: The module expected to find a statement terminator at the end of SQL statement or PL/SQL block but found something else. This can happen if tabs were embedded in the module file.
Action: If tabs are embedded in the source code, replace them with spaces. Check the statement syntax and check that each SQL statement has a terminator.
Cause: A MODULE clause was not specified in the module source file, or a name for the module was not provided.
Action: Specify the module name in the module file.
Cause: SQL*Module is not able to create the specifications (header) output file. This usually happens when write permissions on the current directory or on the directory specified for the SNAME option do not exist. It can also happen if the name or directory path is not legal, a directory on the path does not exist, or the disk or file system is full.
Action: Check the permissions on the specified path and file or on the current directory if the SNAME options are not used. Check that the disk or file system is not full.
Cause: The LANGUAGE clause is not specified in the module source file.
Action: Specify the language clause in the module file.
Cause: FIPS=YES was specified, and part of the module code was not compliant with the ANSI SQL92 Entry Level standard.
Action: Specify FIPS=NO (the default) or correct the code.
Cause: The cursor named in the message was declared more than once in the module file.
Action: Check that each cursor names (not just in the module file, but in the entire application) is unique.
Cause: A procedure named X was declared more than once in the module file.
Action: Check that each procedure name (not just in the module file, but in the entire application) is unique.
Cause: In the procedure named in the message, a parameter was declared with a name that duplicates another parameter's name.
Action: Check that each parameter name in a procedure is unique.
Cause: For a char[n] host variable, a length of less than 2 characters was specified. The length must be at least 2 characters.
Action: Correct the declaration so that it specifies the length of at least 2 characters.
Cause: In the module file, an OPEN, FETCH, or CLOSE was attempted on a cursor that had not yet been declared.
Action: Insert an appropriate cursor declaration in the module file. Remember that cursors must be declared in the file before they are acted upon.
Cause: More than one procedure in this module contains an OPEN command on the named cursor.
Action: Remove one of the OPEN commands, as there is no need for redundancy.
Cause: No OPEN command exists in the module for the cursor named in this message.
Action: Add an OPEN command or remove the cursor if it is not needed.
Cause: This message usually results when SQL*Module cannot connect to the database, using the username and password mentioned either in the module's AUTHORIZATION clause or on the command line with the USERID option.
Action: If connection is made using Net8, check that a listener process is running and that the service name specified in the AUTHORIZATION clause or on the command line is in the TNSNAMES.ORA file. If the connect parameters are correct and this problem persists, contact Oracle Support Services.
Cause: A formal parameter was declared in a procedure, but never used.
Action: Remove the parameter declaration or use it in the procedure.
Cause: The mode of this parameter is illegal. The mode should be one of IN, OUT, or IN OUT.
Action: Correct the reference mode to one of IN, OUT, or IN OUT appropriately.
Cause: The module was not able to store the package in the database.
Cause: An attempt was made to OPEN a cursor that had not been declared.
Action: Declare the cursor or remove the erroneous reference to it.
Cause: Incorrect array index was specified.
Cause: Respecify the array index by making sure that the index must be greater than 0.
Cause: The target of an INTO clause in a SELECT statement is not a parameter of the procedure.
Action: Declare the parameter using the correct datatype in the procedure's parameter list.
Cause: A semantic error occurred in the PL/SQL parse phase when running SQL*Module.
Action: Check that all database objects are valid. To get more information, rerun SQL*Module with OUTPUT=PACKAGE, and check the output PL/SQL code specification file (it has a .pks extension). See the PL/SQL User's Guide and Reference for more information.
Cause: A semantic error occurred in the PL/SQL parse phase when running SQL*Module.
Action: Check that all database objects are valid. To get more information, rerun SQL*Module with OUTPUT=PACKAGE, and check the output PL/SQL code file (it has a .pkb extension). See the PL/SQL User's Guide and Reference for more information.
Cause: A host variable that was used as an indicator variable was not declared.
Action: Declare the host variable or, if possible, remove the indicator variable from the SQL statement.
Cause: When attempting to generate an interface procedures (stubs) file, the WITH INTERFACE PROCEDURE clause in the referenced stored package or stored procedure contained a parameter having an illegal datatype.
Action: Correct the datatype. Datatypes in a WITH INTERFACE clause must be SQL datatypes, not PL/SQL datatypes.
Cause: An unused parameter was declared in the WITH INTERFACE clause of a stored package or a stored procedure.
Action: Correct the WITH INTERFACE clause in the package.
Cause: An attempt was made to generate stubs for a package that does not contain a WITH INTERFACE clause for one or more procedures.
Action: Add the WITH INTERFACE clause to the package specification.
Cause: The package name that was specified using the PNAME option is not correct, or SQL*Module could not access the database schema required.
Action: Check that the specified package exists and has a valid status. Check the STATUS column of the USER_OBJECTS table for that schema to check that the package is valid.
Cause: The options and values RPC_GENERATE=YES and STORE_PACKAGE=YES were specified, but a package name using the PNAME option was not specified.
Action: Add the PNAME option.
Cause: This is a warning message. SQL*Module is not able to find the system configuration file or is not able to open the file. The location of the system configuration file is system specific. See your operating system-specific documentation for the location on your system.
Action: Check that the file exists and that read permission or the appropriate access rights are set for it. The file must exist to avoid this warning message; however, it can be empty.
Cause: SQL*Module's attempt to store the package in the database failed.
Action: Look up the error number in this manual and correct the problem.
Cause: An indicator variable was specified in the WITH INTERFACE clause, but the associated main variable was not declared there.
Action: Modify the WITH INTERFACE clause. Either remove the indicator variable or declare a host variable for it.
Cause: The name of a package stored in the database was not mentioned. This is required to generate stubs out of stored packages.
Action: Specify the name of the package stored in the database.
Cause: The PNAME option was used when there was no need for it. The PNAME option is only required when you specify RPC_GENERATE, STORE_PACKAGE, or both.
Action: Correct the command line.
Cause: The INAME option was used when it was not required. For example, INAME is not required when RPC_GENERATE=YES and the PNAME option are specified.
Action: Do not use the INAME option.
Cause: The ONAME option was used when it was not required. For example, the ONAME option is not required when RPC_GENERATE=NO, and STORE_PACKAGE=YES, or the OUTPUT values list does not contain the CODE value.
Action: Do not use the ONAME option.
Cause: A semantic error occurred in the PL/SQL parse phase when running SQL*Module.
Action: Check that all database objects are valid. To get more information, rerun SQL*Module with OUTPUT=PACKAGE, and check the output PL/SQL code file (it has a .pkb extension). See the PL/SQL User's Guide and Reference for more information.
Cause: FIPS=YES was specified and part of the module code is not compliant with the ANSI SQL92 Entry Level standard.
Action: Specify FIPS=NO (the default) or correct the code.
Cause: Include a status parameter -- SQLCODE, SQLSTATE, or both -- in every parameter definition.
Action: Include SQLCODE or SQLSTATE.
Cause: Because no USERID was specified, SQL*Module cannot connect to the server to create stubs (an interface procedures file) from the stored package.
Action: Specify the service name (if not connecting to the default database), and the username and password. Do this either on the command line or in a configuration file.
Cause: SQLCHECK=SYNTAX (or SQLCHECK=NONE) cannot be specified when creating a stubs file.
Action: Remove the SQLCHECK=SYNTAX or SQLCHECK=NONE specification from the command line or the configuration file.
Cause: OUTPUT=PACKAGE was requested on the command line or in a configuration file, and a package of the name specified does not exist in the schema or is marked as INVALID.
Action: Check that the named package exists and is valid.
Cause: Some part of the input to SQL*Module caused an error or warning condition. This message always follows a specific error or warning message.
Action: No action required for this message. Correct the previous errors.
Cause: This is an informational message.
Action: No action is required.
Cause: This is an informational message.
Action: No action is required.
Cause: This is an informational message.
Action: No action is required.
Cause: This is an informational message.
Action: No action is required.
Cause: The server rejected a username.
Action: If the username is valid, contact Oracle Support Services.
Cause: This is an informational message.
Action: No action is required.
Cause: SQL*Module encountered a SQL statement that it can compile, but that uses a feature not yet implemented.
Action: Contact Oracle Languages Product Management.
Cause: This is an informational message.
Action: No action is required.
Cause: This is an informational message.
Action: No action is required.
Cause: This is an informational message.
Action: No action is required.
Cause: This is an informational message.
Action: No action is required.
Cause: The SNAME option was used when it was not required. For example, no SNAME option is required if the values list of the OUTPUT option does not include the value SPECIFICATION.
Action: Do not use the SNAME option.
Cause: A filename extension was included in the value of a PNAME option. Packages are database objects, not files.
Action: Remove the extension.
Cause: A datatype was used that is not supported for the host language. For example, NUMERIC is not a supported datatype for Ada and C.
Action: Refer to your language-specific Precompiler Programmer's Guide for a list of the datatypes supported in each host language.
Cause: The OUTPUT option list does not contain the value LIST.
Action: Add LIST to the list of values of the OUTPUT option.
Cause: A PL/SQL package or function specification did not have a WITH INTERFACE clause. Currently, MODADA requires the WITH INTERFACE clause to be present in order to create calls to a PL/SQL function or package.
Action: Rewrite PL/SQL package or function specification to include a WITH INTERFACE clause. Alternatively, write a PL/SQL package or function specification which has a WITH INTERFACE clause and have it call the original PL/SQL package.
Cause: A Command line option, "bind=early" was specified while creating calls to a PL/SQL package or function without a WITH INTERFACE clause.
Action: Change the command line option to "bind=late", or include a WITH INTERFACE clause in the PL/SQL specification (see error 97 action).
Cause: The module contained a type for which there is currently no equivalent PL/SQL type; it may not be stored in the database.
Action: Set the command line option to STORE=NO or move the procedures containing the offending type to another module and compile that module with STORE=NO.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
