{"id":1920,"date":"2025-02-16T10:41:06","date_gmt":"2025-02-16T15:41:06","guid":{"rendered":"https:\/\/molecularsciences.org\/content\/?p=1920"},"modified":"2025-03-03T15:10:55","modified_gmt":"2025-03-03T20:10:55","slug":"how-to-solve-pls-00103-encountered-the-symbol-when-expecting-one-of-the-following","status":"publish","type":"post","link":"https:\/\/molecularsciences.org\/content\/how-to-solve-pls-00103-encountered-the-symbol-when-expecting-one-of-the-following\/","title":{"rendered":"How to Solve PLS-00103: Encountered the Symbol When Expecting Once of the Following"},"content":{"rendered":"\n

The PLS-00103<\/strong> error is a syntax error<\/strong> in PL\/SQL that occurs when the PL\/SQL compiler encounters an unexpected symbol<\/strong> while parsing the code. This means that something in the code is incorrectly placed<\/strong>, misspelled<\/strong>, or missing<\/strong>.<\/p>\n\n\n\n

This error message is often accompanied by a list of expected symbols<\/strong>, which helps in identifying the issue.<\/p>\n\n\n\n

Common Causes and Solutions<\/strong><\/h2>\n\n\n\n

1. Missing or Incorrect Keywords<\/strong><\/h3>\n\n\n\n

Cause:<\/strong><\/h4>\n\n\n\n

Using an incorrect or missing keyword in a PL\/SQL block.<\/p>\n\n\n\n

Example: Incorrect DECLARE<\/code> Usage<\/strong><\/h4>\n\n\n\n
DECLARE v_name VARCHAR2(50)
BEGIN
    v_name := 'John Doe';
    DBMS_OUTPUT.PUT_LINE(v_name);
END;
\/
<\/code><\/pre>\n\n\n\n
Error Output:<\/strong><\/h4>\n\n\n\n
PLS-00103: Encountered the symbol \"BEGIN\" when expecting one of the following: := ; not null constant default
<\/code><\/pre>\n\n\n\n
Solution:<\/strong><\/h4>\n\n\n\n
Add a semicolon (;<\/code>) after the variable declaration.<\/p>\n\n\n\n
DECLARE 
    v_name VARCHAR2(50);  -- Fixed: Added semicolon
BEGIN
    v_name := 'John Doe';
    DBMS_OUTPUT.PUT_LINE(v_name);
END;
\/
<\/code><\/pre>\n\n\n\n
2. Using a Reserved Keyword as an Identifier<\/strong><\/h3>\n\n\n\n
Cause:<\/strong><\/h4>\n\n\n\n
Using an Oracle reserved keyword<\/strong> as a variable or table name.<\/p>\n\n\n\n
Example: Using SELECT<\/code> as a Variable Name<\/strong><\/h4>\n\n\n\n
DECLARE 
    select VARCHAR2(50);
BEGIN
    select := 'PL\/SQL Error';
    DBMS_OUTPUT.PUT_LINE(select);
END;
\/
<\/code><\/pre>\n\n\n\n
Error Output:<\/strong><\/h4>\n\n\n\n
PLS-00103: Encountered the symbol \"SELECT\" when expecting an identifier
<\/code><\/pre>\n\n\n\n
Solution:<\/strong><\/h4>\n\n\n\n
Use double quotes or rename the variable.<\/p>\n\n\n\n
DECLARE 
    v_select VARCHAR2(50);  -- Fixed: Changed variable name
BEGIN
    v_select := 'PL\/SQL Error';
    DBMS_OUTPUT.PUT_LINE(v_select);
END;
\/
<\/code><\/pre>\n\n\n\n
Or:<\/p>\n\n\n\n
DECLARE 
    \"SELECT\" VARCHAR2(50);  -- Fixed: Used double quotes
BEGIN
    \"SELECT\" := 'PL\/SQL Error';
    DBMS_OUTPUT.PUT_LINE(\"SELECT\");
END;
\/
<\/code><\/pre>\n\n\n\n
However, using double quotes is not recommended<\/strong>, as it makes maintenance difficult.<\/p>\n\n\n\n
3. Missing IS<\/code> or AS<\/code> in a Procedure or Function Declaration<\/strong><\/h3>\n\n\n\n
Cause:<\/strong><\/h4>\n\n\n\n
A stored procedure is declared without IS<\/code> or AS<\/code><\/strong> before the BEGIN<\/code> block.<\/p>\n\n\n\n
Example: Procedure Without IS<\/code> or AS<\/code><\/strong><\/h4>\n\n\n\n
CREATE OR REPLACE PROCEDURE my_proc 
BEGIN
    DBMS_OUTPUT.PUT_LINE('Hello');
END;
\/
<\/code><\/pre>\n\n\n\n
Error Output:<\/strong><\/h4>\n\n\n\n
PLS-00103: Encountered the symbol \"BEGIN\" when expecting one of the following: IS AS AUTHID
<\/code><\/pre>\n\n\n\n
Solution:<\/strong><\/h4>\n\n\n\n
Add IS<\/code> or AS<\/code> after the procedure name.<\/p>\n\n\n\n
CREATE OR REPLACE PROCEDURE my_proc IS  -- Fixed: Added IS
BEGIN
    DBMS_OUTPUT.PUT_LINE('Hello');
END;
\/
<\/code><\/pre>\n\n\n\n
4. Incorrect Usage of IF<\/code> Statement<\/strong><\/h3>\n\n\n\n
Cause:<\/strong><\/h4>\n\n\n\n
Not using THEN<\/code> in an IF<\/code> statement.<\/p>\n\n\n\n
Example: Missing THEN<\/code><\/strong><\/h4>\n\n\n\n
DECLARE
    v_salary NUMBER := 5000;
BEGIN
    IF v_salary > 4000  -- Missing THEN
        DBMS_OUTPUT.PUT_LINE('High Salary');
    END IF;
END;
\/
<\/code><\/pre>\n\n\n\n
Error Output:<\/strong><\/h4>\n\n\n\n
PLS-00103: Encountered the symbol \"DBMS_OUTPUT.PUT_LINE\" when expecting one of the following: THEN
<\/code><\/pre>\n\n\n\n
Solution:<\/strong><\/h4>\n\n\n\n
Add THEN<\/code> after the IF<\/code> condition.<\/p>\n\n\n\n
DECLARE
    v_salary NUMBER := 5000;
BEGIN
    IF v_salary > 4000 THEN  -- Fixed: Added THEN
        DBMS_OUTPUT.PUT_LINE('High Salary');
    END IF;
END;
\/
<\/code><\/pre>\n\n\n\n
5. Incorrect Placement of EXCEPTION<\/code> Block<\/strong><\/h3>\n\n\n\n
Cause:<\/strong><\/h4>\n\n\n\n
Placing EXCEPTION<\/code> outside a BEGIN-END<\/code> block.<\/p>\n\n\n\n
Example: Incorrect Exception Placement<\/strong><\/h4>\n\n\n\n
DECLARE
    v_number NUMBER := 10;
EXCEPTION
    WHEN OTHERS THEN
        DBMS_OUTPUT.PUT_LINE('An error occurred');
BEGIN
    v_number := v_number \/ 0;
END;
\/
<\/code><\/pre>\n\n\n\n
Error Output:<\/strong><\/h4>\n\n\n\n
PLS-00103: Encountered the symbol \"EXCEPTION\" when expecting one of the following: ...<\/code><\/pre>\n\n\n\n
Solution:<\/strong><\/h4>\n\n\n\n
Move EXCEPTION<\/code> inside the BEGIN-END<\/code> block.<\/p>\n\n\n\n
DECLARE
    v_number NUMBER := 10;
BEGIN
    v_number := v_number \/ 0;
EXCEPTION
    WHEN OTHERS THEN  -- Fixed: Placed inside BEGIN-END
        DBMS_OUTPUT.PUT_LINE('An error occurred');
END;
\/
<\/code><\/pre>\n\n\n\n
6. Incorrect Loop Syntax<\/strong><\/h3>\n\n\n\n
Cause:<\/strong><\/h4>\n\n\n\n
Not using LOOP<\/code> or END LOOP<\/code>.<\/p>\n\n\n\n
Example: Missing LOOP<\/code> Keyword<\/strong><\/h4>\n\n\n\n
DECLARE
    v_counter NUMBER := 1;
BEGIN
    WHILE v_counter <= 5  -- Missing LOOP
        DBMS_OUTPUT.PUT_LINE(v_counter);
        v_counter := v_counter + 1;
    END LOOP;
END;
\/
<\/code><\/pre>\n\n\n\n
Error Output:<\/strong><\/h4>\n\n\n\n
PLS-00103: Encountered the symbol \"DBMS_OUTPUT.PUT_LINE\" when expecting one of the following: LOOP
<\/code><\/pre>\n\n\n\n
Solution:<\/strong><\/h4>\n\n\n\n
Add LOOP<\/code> after the WHILE<\/code> condition.<\/p>\n\n\n\n
DECLARE
    v_counter NUMBER := 1;
BEGIN
    WHILE v_counter <= 5 LOOP  -- Fixed: Added LOOP
        DBMS_OUTPUT.PUT_LINE(v_counter);
        v_counter := v_counter + 1;
    END LOOP;
END;
\/
<\/code><\/pre>\n\n\n\n
Summary of Solutions<\/strong><\/h2>\n\n\n\n
Cause<\/strong><\/th>Solution<\/strong><\/th><\/tr><\/thead>
Missing semicolon (;<\/code>)<\/strong><\/td>Add ;<\/code> where required<\/td><\/tr>
Using reserved keywords<\/strong><\/td>Rename variables or use double quotes<\/td><\/tr>
Incorrect procedure\/function syntax<\/strong><\/td>Ensure IS<\/code> or AS<\/code> is present<\/td><\/tr>
Missing THEN<\/code> in IF<\/code> statement<\/strong><\/td>Add THEN<\/code> after the condition<\/td><\/tr>
Placing EXCEPTION<\/code> outside BEGIN-END<\/code><\/strong><\/td>Move EXCEPTION<\/code> inside the block<\/td><\/tr>
Incorrect LOOP<\/code> structure<\/strong><\/td>Ensure LOOP<\/code> and END LOOP<\/code> are used<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\n\n\n\n
Conclusion<\/strong><\/h2>\n\n\n\n
The PLS-00103<\/strong> error is one of the most common PL\/SQL errors, but it is also one of the easiest to fix<\/strong> once you identify the cause. By carefully checking for syntax issues, missing keywords, misplaced statements, and incorrect variable names<\/strong>, you can quickly resolve this error and ensure that your PL\/SQL code runs smoothly.<\/p>\n","protected":false},"excerpt":{"rendered":"
The PLS-00103 error is a syntax error in PL\/SQL that occurs when the PL\/SQL compiler encounters an unexpected symbol while parsing the code. This means that something in the code is incorrectly placed, misspelled, or missing. This error message is often accompanied by a list of expected symbols, which helps in identifying the issue. Common […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[515],"tags":[529],"class_list":["post-1920","post","type-post","status-publish","format-standard","hentry","category-oracle","tag-pl-sql"],"_links":{"self":[{"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/posts\/1920","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/comments?post=1920"}],"version-history":[{"count":2,"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/posts\/1920\/revisions"}],"predecessor-version":[{"id":1935,"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/posts\/1920\/revisions\/1935"}],"wp:attachment":[{"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/media?parent=1920"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/categories?post=1920"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/tags?post=1920"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}