|Oracle8i Error Messages
Release 2 (8.1.6)
Part Number A76999-01
PG2-00010 found end-of-file while scanning string literal
Cause: A string in a SQL statement, which should be delimited by single quotation marks, was not terminated properly.
Action: Check that all strings are delimited.
PG2-00011 found identifier greater than 128 characters (truncated)
Cause: The precompiler found an identifier that was too long.
Action: Shorten the identifier. SQL identifiers should be limited to 18 characters.
PG2-00012 did not find matching quote for char constant
Cause: A character constant with a single quotation mark was not terminated.
Action: Terminate the character constant.
PG2-00013 unknown escape sequence
Cause: The precompiler found an escape sequence that it could not process inside a string literal. This error can arise when multibyte character strings that can contain shift-in or shift-out escape sequences are used.
Action: Correct the string representation.
PG2-00014 Syntax error at line number, column number, file string:
Cause: The precompiler detected an error in C or embedded SQL syntax. This message is followed by a more specific error message.
Action: Correct the syntax error.
PG2-00015 unable to open include file
Cause: The precompiler could not open a header file that was specified using the #include preprocessor directive or the EXEC SQL INCLUDE statement. This can happen if the file specification is inaccurate or if read permission or read access rights on the file or on one or more of the directories in the path were not granted.
Action: Make sure the file specification is correct, that the file exists, and that read permission has been granted so that the file can be read.
PG2-00016 include file pathname is too long
Cause: The path name for include files exceeded the maximum length of 80 characters.
Action: Move the include file, or create an environment variable or logical to shorten the path name.
PG2-00017 unable to open output file
Cause: The precompiler could not open an output file. This could be a generated code output file (.c file) or a listing file. This message can result from many causes. For example:
Action: Track down the cause of the error, as suggested above, and correct it.
PG2-00018 found end-of-file while scanning comment
Cause: A C comment either in C code or in an embedded SQL statement, was not terminated.
Action: Find the unterminated comment and terminate it with */.
PG2-00019 Preprocessor warning at line number, column number, file string:
Cause: A warning condition occurred as the precompiler was doing the preprocessor pass. A more specific warning message will follow this message.
Action: Correct the condition according to the action specified for the message that follows.
PG2-00020 Preprocessor error at line number, column number, file string:
Cause: An error condition occurred as the precompiler was in the preprocessing phase. A more specific error message will follow this message.
Action: Correct the error according to the action specified for the message that follows.
PG2-00021 Found newline while scanning string literal
Cause: A string constant contains a newline character, For example:
Action: Remove the newline character.
PG2-00022 Found end of file while scanning a SQL statement
Cause: The precompiler encountered an end of file while parsing an EXEC SQL statement.
Action: Add statement terminator(;) or complete the EXEC SQL statement.
PG2-00023 Found end of file while scanning a PL/SQL statement
Cause: The precompiler encountered an end of file while parsing a PL/SQL statement (EXEC SQL EXECUTE ...).
Action: Complete the PL/SQL statement.