Скачать или смотреть Resolving PLS-00103: Encountered the symbol "end-of-file" Error in PL/SQL

Learn how to fix the `PLS-00103` error that occurs in PL/SQL code execution. Follow our structured guide to identify and correct common issues in your PL/SQL blocks.
---
This video is based on the question https://stackoverflow.com/q/63234248/ asked by the user 'Caleb' ( https://stackoverflow.com/u/13611607/ ) and on the answer https://stackoverflow.com/a/63235617/ provided by the user 'Littlefoot' ( https://stackoverflow.com/u/9097906/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: PLS-00103: Encountered the symbol "end-of-file" when expecting one of the following: begin function pragma procedure subtype type an identifier

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding the PLS-00103 Error in PL/SQL

When working with PL/SQL in SQL Developer, encountering errors can be frustrating, especially when the error message is cryptic. One common issue developers may face is the error message PLS-00103: Encountered the symbol "end-of-file" when expecting one of the following: begin function pragma procedure subtype type <an identifier>. This typically indicates a problem with the structure of your PL/SQL code. In this guide, we’ll delve into the causes of this error and how to resolve it.

What Does This Error Mean?

The PLS-00103 error is a compilation error in PL/SQL that signifies there is an unexpected end of the code block. Essentially, the PL/SQL compiler is expecting a certain keyword (like BEGIN, FUNCTION, or PROCEDURE) but encounters an unexpected end instead. This kind of error can be due to multiple factors, including:

Missing keywords

Misplaced characters or symbols

Incorrect structure of the PL/SQL block

In the case shared in the code, it appears that the SQL Developer encountered an error right at the DECLARE section.

Analyzing the Problematic Code

Let’s examine the provided PL/SQL block that produced this error:

[[See Video to Reveal this Text or Code Snippet]]

Issues in the Code:

Typo in Variable Name: CUSTOMET_NAME should be changed to CUSTOMER_NAME in the INTO clause.

Structure and Placement: Ensure the BEGIN and END keywords are correctly placed and there are no missing or extra characters.

Solution: Corrected Code

To fix the issues, let’s rewrite the PL/SQL block with the necessary corrections. Below is the updated code snippet:

[[See Video to Reveal this Text or Code Snippet]]

Key Changes Made:

Correct Variable Name: Fixed CUSTOMET_NAME to l_customer_name.

Enhanced Readability: Improved SQL joins by using the JOIN syntax, which is clearer.

Added Exception Handling: Included exception handling to gracefully manage cases where no data is found or when too many rows match the query.

Testing the Modified Code

To ensure your code runs without errors, execute it in your SQL Developer environment. Note that if your tables are empty, you may see "Nothing matches," but this does not indicate an error in your code structure.

Conclusion

Errors like PLS-00103 in PL/SQL can often stem from simple mistakes in code structure or variable names. By carefully reviewing your PL/SQL blocks and ensuring all elements are correctly placed, you can resolve these issues effectively. Remember, structured exception handling not only improves your code's robustness but also aids in debugging.

If you continue to face challenges, consider checking your database schema or providing a test case to validate against.