PLS-00395: wrong number of values in VALUES clause of INSERT statement

PLS-00395: wrong number of values in VALUES clause of INSERT statement

Cause: The number of columns in an INSERT statement does not match the number of values in the VALUES clause. For example, the following statement is faulty because no column is specified for the value 20: INSERT INTO emp (empno, ename) VALUES (7788, SCOTT , 20);

Action: Change the number of items in the column list or the number of items in the VALUES list so that the numbers match.

PLS-00394: wrong number of values in the INTO list of a FETCH statement

PLS-00394: wrong number of values in the INTO list of a FETCH statement

Cause: The number of variables in the INTO clause of a FETCH statement does not match the number of columns in the cursor declaration.

Action: Change the number of variables in the INTO clause or the number of columns in the cursor declaration so that the numbers match.

PLS-00393: wrong number of columns in SELECT...INTO statement

PLS-00393: wrong number of columns in SELECT...INTO statement

Cause: The number of columns selected by a SELECT...INTO statement does not match the number of variables in the INTO clause.

Action: Change the number of columns in the select list or the number of variables in the INTO clause so that the numbers match.

PLS-00392: Type mismatch in arguments to BETWEEN

PLS-00392: Type mismatch in arguments to BETWEEN

Cause: In a comparison such as X BETWEEN Y AND Z, the expressions X, Y, and Z do not match in datatype, and it is unclear which implicit conversion is required to correct the mismatch.

Action: Change the expressions so that their datatypes match. You might want to use datatype conversion functions.

PLS-00391: undefined column string in UPDATE statement

PLS-00391: undefined column string in UPDATE statement

Cause: An UPDATE statement refers to a column not defined for the table or view being updated.

Action: Check the spelling of the column name, then revise the statement so that it refers only to defined columns.

PLS-00390: undefined column string in INSERT statement

PLS-00390: undefined column string in INSERT statement

Cause: Check the spelling of the column name, then change the expression so that it refers only to defined columns.

Action: Check the spelling of the column name, then change the expression so that it refers only to defined columns.

PLS-00388: undefined column string in subquery

PLS-00388: undefined column string in subquery

Cause: A subquery contains a column name that was not defined in the specified table.

Action: Change the expression to specify a column that was defined.

PLS-00387: INTO variable cannot be a database object

PLS-00387: INTO variable cannot be a database object

Cause: An item in the INTO list of a FETCH or SELECT statement was found to be a database object. INTO introduces a list of user-defined variables to which output values are assigned. Therefore, database objects cannot appear in the INTO list.

Action: Check the spelling of the INTO list item. If necessary, remove the item from the INTO list or replace it with a user-defined output variable.

PLS-00386: type mismatch found at string between FETCH cursor and INTO variables

PLS-00386: type mismatch found at string between FETCH cursor and INTO variables

Cause: An assignment target in the INTO list of a FETCH statement does not match in datatype with the corresponding column in the select list of the cursor declaration, and it is unclear which implicit conversion is required to correct the mismatch.

Action: Change the cursor declaration or change the datatype of the assignment target. You might want to use datatype conversion functions in the select list of the query associated with the cursor.

PLS-00385: type mismatch found at string in SELECT...INTO statement

PLS-00385: type mismatch found at string in SELECT...INTO statement

Cause: The expressions to the left and right of the INTO clause in a SELECT...INTO statement do not match in datatype, and it is unclear which implicit conversion is required to correct the mismatch.

Action: Change the expressions so that their datatypes match. You might want to use datatype conversion functions in the select list.

PLS-00384: type mismatch found at string in UPDATE s SET clause

PLS-00384: type mismatch found at string in UPDATE s SET clause

Cause: The column to the left of the equal sign in the SET clause of an UPDATE statement does not match in datatype with the column, expression, or subquery to the right of the equal sign, and it is unclear which implicit conversion is required to correct the mismatch.

Action: Change the expressions so that their datatypes match. You might want to use datatype conversion functions in the SET clause.

PLS-00383: type mismatch found at string inside an IN or NOT IN clause

PLS-00383: type mismatch found at string inside an IN or NOT IN clause

Cause: In a test for set membership such as X NOT IN (SELECT Y ... ), the expressions X and Y do not match in datatype, and it is unclear which implicit conversion is required to correct the mismatch.

Action: Change the expressions so that their datatypes match. You might want to use datatype conversion functions in the select list.

PLS-00382: expression is of wrong type

PLS-00382: expression is of wrong type

Cause: An expression has the wrong datatype for the context in which it was found.

Action: Change the datatype of the expression. You might want to use datatype conversion functions.

PLS-00381: type mismatch found at string between column and variable in subquery or INSERT

PLS-00381: type mismatch found at string between column and variable in subquery or INSERT

Cause: The datatypes of a column and a variable do not match. The variable was encountered in a subquery or INSERT statement.

Action: Change the variable datatype to match that of the column.

PLS-00380: functions and procedures are not included in this release of PL or SQL

PLS-00380: functions and procedures are not included in this release of PL or SQL

Cause: The program being compiled contains a declaration of a FUNCTION or PROCEDURE.

Action: none

PLS-00379: CASE statements are not included in this release of PL or SQL

PLS-00379: CASE statements are not included in this release of PL or SQL

Cause: The unit being compiled contains a CASE statement. However, the current release of PL or SQL does not support CASE statements.

Action: Remove the CASE statement from the compilation unit.

PLS-00378: invalid compilation unit for this release of PL or SQL

PLS-00378: invalid compilation unit for this release of PL or SQL

Cause: A compilation unit is a file containing PL or SQL source code that is passed to the compiler. Only compilation units containing blocks, declarations, statements, and subprograms are allowed. This error occurs when some other language construct is passed to the compiler.

Action: Make sure the compilation unit contains only blocks, declarations, statements, and subprograms.

PLS-00377: internal type PLS_INTEGER is not included in this release of PL or SQL

PLS-00377: internal type PLS_INTEGER is not included in this release of PL or SQL

Cause: The type-name INTEGER was used in a declaration.

Action: none

PLS-00376: illegal EXIT statement; it must appear inside a loop

PLS-00376: illegal EXIT statement; it must appear inside a loop

Cause: An EXIT statement was found outside of a loop construct. The EXIT statement is used to exit prematurely from a loop and so must always appear within a loop.

Action: Either remove the EXIT statement or place it inside a loop.

PLS-00375: illegal GOTO statement; this GOTO cannot branch to label string

PLS-00375: illegal GOTO statement; this GOTO cannot branch to label string

Cause: The line and column numbers accompanying the error message refer to a GOTO that branches from outside a construct (a loop or exception handler, for example) that contains a sequence of statements to a label inside that sequence of statements. Such a branch is not allowed.

Action: Either move the GOTO statement inside the sequence of statements or move the labeled statement outside the sequence of statements.

PLS-00110: bind variable string not allowed in this context

PLS-00110: bind variable string not allowed in this context

Cause: A bind variable, that is, an identifier prefixed with a colon, was found in an inappropriate context.

Action: Remove the colon or replace the bind variable with the appropriate object.

PLS-00109: unknown exception name string in PRAGMA EXCEPTION_INIT

PLS-00109: unknown exception name string in PRAGMA EXCEPTION_INIT

Cause: No declaration for the exception name referenced in an EXCEPTION_INIT pragma was found within the scope of the pragma.

Action: Make sure the pragma follows the exception declaration and is within the same scope.

PLS-00108: declarative units must be a single variable declaration

PLS-00108: declarative units must be a single variable declaration

Cause: While checking a declarative unit (a top-level declare block without the BEGIN...END), PL or SQL found that there was more than one item declared or that the item was not a variable declaration. A table is a common variable declaration at the unit level. To define a TABLE, compile a DECLARE compilation unit, but only one at a time is allowed.

Action: Declare variables in separate declarative units.

PLS-00105: at most one forward declaration of type string is permitted

PLS-00105: at most one forward declaration of type string is permitted

Cause: More than one forward declaration of a type is redundant.

Action: Remove all but one forward declaration.

PLS-00104: empty argument list in call of procedure string must be omitted

PLS-00104: empty argument list in call of procedure string must be omitted

Cause: In a subprogram call, the name of the subprogram was followed by an empty parameter list. For example, procedure P was called as P(). This is not allowed.

Action: Remove the empty parameter list. In the example, change the procedure call to P.

PLS-00103: %s

PLS-00103: %s

Cause: This error message is from the parser. It found a token (language element) that is inappropriate in this context.

Action: Check previous tokens as well as the one given in the error message. The line and column numbers given in the error message refer to the end of the faulty language construct.

PLS-00102: parser stack overflow because nesting is too deep

PLS-00102: parser stack overflow because nesting is too deep

Cause: The parser, which checks the syntax of PL or SQL statements, uses a data structure called a stack; the number of levels of nesting in the PL or SQL block exceeded the stack capacity.

Action: Reorganize the block structure to avoid nesting at too deep a level. For example, move the lowest-level sub-block to a higher level.

PLS-00101: reserved for future use

PLS-00101: reserved for future use

Cause: This error message is not used yet. (Heh, heh, that s a joke, son.)

Action: none

PLS-00049: bad bind variable string

PLS-00049: bad bind variable string

Cause: The client (caller) of PL or SQL has parsed a bind variable that it has informed to be bad .

Action: none

LFI-01523: rename() failed.

LFI-01523: rename() failed.

Cause: A call to lficstd() had failed.

Action: Contact development service

LFI-01522: opendir() failed.

LFI-01522: opendir() failed.

Cause: The function opendir() returned an error condition.

Action: Contact the development organization.

LFI-01521: fsync() failed(OSD return value = string) in string.

LFI-01521: fsync() failed(OSD return value = string) in string.

Cause: The function fsync() returned an error condition.

Action: Contact the development organization.

LFI-01520: close() failed(OSD return value = string) in string.

LFI-01520: close() failed(OSD return value = string) in string.

Cause: The function close() returned an error condition.

Action: Contact the development organization.

LFI-01519: llseek() failed(OSD return value = string) in string.

LFI-01519: llseek() failed(OSD return value = string) in string.

Cause: The llseek() function returned an error.

Action: Contact Oracle Worldwide Support.

LFI-01518: write() failed(OSD return value = string) in string.

LFI-01518: write() failed(OSD return value = string) in string.

Cause: Call to write() failed.

Action: Contact the development organization.

LFI-01517: open() failed(OSD return value = string).

LFI-01517: open() failed(OSD return value = string).

Cause: Call to open() failed.

Action: Contact the development organization.

LFI-01516: read() failed (OSD return value = string) in string.

LFI-01516: read() failed (OSD return value = string) in string.

Cause: Call to read() failed.

Action: Contact the development organization.

LFI-01515: truncate() failed.

LFI-01515: truncate() failed.

Cause: The function truncate() returned an error condition.

Action: Contact the development organization.

LFI-01514: ftell() failed in string

LFI-01514: ftell() failed in string

Cause: The ftell() function returned an error.

Action: Contact Oracle Worldwide Support.

LFI-01512: stat() failed

LFI-01512: stat() failed

Cause: Call to stat() failed.

Action: Contact Oracle Worldwide Support.

LFI-01511: unlink() failed(OSD errno = string) in string.

LFI-01511: unlink() failed(OSD errno = string) in string.

Cause: Call to unlink() failed.

Action: Contact the development organization.

LFI-01510: fread() failed(OSD return value = string) in string.

LFI-01510: fread() failed(OSD return value = string) in string.

Cause: Call to fread() failed.

Action: Contact Oracle Worldwide Support.

LFI-01509: fopen() failed(OSD return value = string).

LFI-01509: fopen() failed(OSD return value = string).

Cause: Call to fopen() failed.

Action: Contact Oracle Worldwide Support.

LFI-01508: access() failed.

LFI-01508: access() failed.

Cause: Call to access() failed.

Action: Contact the development organization.

LFI-01507: fwrite() failed(OSD return value = string) in string.

LFI-01507: fwrite() failed(OSD return value = string) in string.

Cause: File pointer may be null or may not be opened for write.

Action: Contact the development organization.

LFI-01506: fflush() failed(OSD return value = string).

LFI-01506: fflush() failed(OSD return value = string).

Cause: The function fflush() returned an error condition.

Action: Contact the development organization.

LFI-01505: fclose() failed(OSD return value = string) in string.

LFI-01505: fclose() failed(OSD return value = string) in string.

Cause: The function fclose() returned an error condition.

Action: Contact Oracle Worldwide Support.

LFI-01504: fseek() failed(OSD return value = string) in string.

LFI-01504: fseek() failed(OSD return value = string) in string.

Cause: The function fseek() returned an error condition.

Action: Contact Oracle Worldwide Support.

LFI-01503: Max filename size exceeded generating filename.

LFI-01503: Max filename size exceeded generating filename.

Cause: While building a filename we exceeded the buffer allocated to hold the new filename.

Action: Contact the development organization.

LFI-01502: Base filename does not exist.

LFI-01502: Base filename does not exist.

Cause: The filename that was parsed had no base file. It was either all path or extension.

Action: Check the filename being passed in to make sure it is correct.

LFI-01501: tmpnam() fails to generate temporary file name.

LFI-01501: tmpnam() fails to generate temporary file name.

Cause: Operating system was unable to create temporary file name.

Action: Contact the development organization.

LFI-01500: Error condition on call to OSD function string.

LFI-01500: Error condition on call to OSD function string.

Cause: An error condition arises in calling an OSD function. This message occurs if calls to malloc or free functions failed.

Action: Contact Oracle Worldwide Support.

LFI-01007: Line is too long; encountered in function string.

LFI-01007: Line is too long; encountered in function string.

Cause: The length of the line exceeds the maximum length.

Action: Examine underlying errors for more information.

LFI-01006: File ends in partial character in string.

LFI-01006: File ends in partial character in string.

Cause: A line ends in a partial character.

Action: Examine underlying errors for more information.

LFI-01005: Unable to fill buffer.

LFI-01005: Unable to fill buffer.

Cause: The buffer manager is probably unable to read from the underlying file.

Action: See the accompanying error messages for more information.

PLS-00236: Invalid external type specification for string.

PLS-00236: Invalid external type specification for string.

Cause: The external type specified is not valid for one of the following: INDICATOR, LENGTH, MAXLEN, TDO, DURATION, CHARSETID, or CHARSETFORM.

Action: Check the manual and specify an appropriate external type.

PLS-00235: the external type is not appropriate for the parameter

PLS-00235: the external type is not appropriate for the parameter

Cause: An unsuccessful attempt was made to convert a parameter to the specified external parameter type.

Action: Specify a different external type or parameter type.

PLS-00234: PARAMETER STYLE SQL may not be specified with a PARAMATERS list

PLS-00234: PARAMETER STYLE SQL may not be specified with a PARAMATERS list

Cause: A subprogram cannot specify both PARAMETER STYLE SQL and an explicit PARAMETERS list. Use PARAMETER STYLE GENERAL to supply default PARAMETERS list types.

Action: Change the subprogram specification.

PLS-00233: function name used as an exception name in when clause

PLS-00233: function name used as an exception name in when clause

Cause: The WHEN clause in an exception handler contains a function call instead of an exception name. A valid exception handler consists of a WHEN clause, which must specify an exception, followed by a sequence of statements to be executed when that exception is raised.

Action: Check the spelling of the identifier in the WHEN clause, then replace the function call with an exception name.

PLS-00232: nested packages not permitted

PLS-00232: nested packages not permitted

Cause: A package was declared inside another package, but package declarations are allowed only at the top level. In other words, packages cannot be nested.

Action: Move the package declaration outside the enclosing package.