{"id":1989,"date":"2025-05-25T00:59:42","date_gmt":"2025-05-25T04:59:42","guid":{"rendered":"https:\/\/molecularsciences.org\/content\/?p=1989"},"modified":"2025-05-22T01:02:07","modified_gmt":"2025-05-22T05:02:07","slug":"solving-pls-00364-loop-index-variable-must-be-an-integer","status":"publish","type":"post","link":"https:\/\/molecularsciences.org\/content\/solving-pls-00364-loop-index-variable-must-be-an-integer\/","title":{"rendered":"Solving PLS-00364: Loop Index Variable Must Be an Integer<\/name>"},"content":{"rendered":"\n

In PL\/SQL, FOR<\/code> loops are a powerful control structure used to iterate over a defined range of numbers or rows. However, this construct has specific syntactic rules. One common error developers encounter is:<\/p>\n\n\n\n

\n

PLS-00364: Loop index variable <name><\/code> must be an integer<\/strong><\/p>\n<\/blockquote>\n\n\n\n

This article explains why this error occurs<\/strong>, provides examples<\/strong>, and offers clear solutions<\/strong> to fix it.<\/p>\n\n\n\n

What Causes PLS-00364?<\/strong><\/h2>\n\n\n\n

The error occurs when the loop index variable in a FOR<\/code> loop is either:<\/p>\n\n\n\n

    \n
  • Explicitly declared<\/strong> as a non-integer type (like NUMBER<\/code>, FLOAT<\/code>, DECIMAL<\/code>, VARCHAR2<\/code>, etc.)<\/li>\n\n\n\n
  • Or, when the range provided in the loop is not an integer range<\/strong><\/li>\n<\/ul>\n\n\n\n

    PL\/SQL requires that FOR<\/code> loop index variables are always implicitly<\/strong> created and treated as integers<\/strong>. You cannot use decimal values or user-declared non-integer loop counters in a FOR<\/code> loop.<\/p>\n\n\n\n

    Examples That Produce PLS-00364<\/strong><\/h2>\n\n\n\n

    Example 1: Loop Range with Decimal Values<\/h3>\n\n\n\n
    BEGIN
       FOR i IN 1.1 .. 5.1 LOOP
          DBMS_OUTPUT.PUT_LINE(i);
       END LOOP;
    END;
    \/
    <\/code><\/pre>\n\n\n\n
    Error Message:<\/strong><\/p>\n\n\n\n
    PLS-00364: loop index variable 'I' must be an integer
    <\/code><\/pre>\n\n\n\n
    Example 2: Loop Index Variable Declared as NUMBER<\/h3>\n\n\n\n
    DECLARE
       i NUMBER := 1;
    BEGIN
       FOR i IN 1 .. 5 LOOP
          DBMS_OUTPUT.PUT_LINE(i);
       END LOOP;
    END;
    \/
    <\/code><\/pre>\n\n\n\n
    Why this fails:<\/strong> Even though i<\/code> is declared as NUMBER<\/code>, the compiler does not allow this conflict because the loop control variable is implicitly managed by the FOR<\/code> loop construct.<\/p>\n\n\n\n
    Correct Usage: Use Integer Values Only<\/strong><\/h2>\n\n\n\n
    Solution 1: Use Integer Range Without Declaring the Index<\/h3>\n\n\n\n
    BEGIN
       FOR i IN 1 .. 5 LOOP
          DBMS_OUTPUT.PUT_LINE('Value: ' || i);
       END LOOP;
    END;
    \/
    <\/code><\/pre>\n\n\n\n
    This works correctly because:<\/p>\n\n\n\n
      \n
    • The index i<\/code> is implicitly declared<\/strong><\/li>\n\n\n\n
    • The range is a pair of integer literals<\/strong><\/li>\n<\/ul>\n\n\n\n
      Solution 2: Use Integer Variables in Range<\/h3>\n\n\n\n
      DECLARE
         v_start INTEGER := 1;
         v_end   INTEGER := 5;
      BEGIN
         FOR i IN v_start .. v_end LOOP
            DBMS_OUTPUT.PUT_LINE('Value: ' || i);
         END LOOP;
      END;
      \/
      <\/code><\/pre>\n\n\n\n
      Again, the range resolves to integers, and the loop variable i<\/code> is not explicitly declared.<\/p>\n\n\n\n
      Solution 3: Use WHILE Loop for Non-Integer Increments<\/h3>\n\n\n\n
      If your logic involves non-integer increments (e.g., 0.5 or 2.7), a FOR<\/code> loop cannot be used. Instead, use a WHILE<\/code> loop with a floating-point variable.<\/p>\n\n\n\n
      DECLARE
         v_counter NUMBER := 1.5;
      BEGIN
         WHILE v_counter <= 5.0 LOOP
            DBMS_OUTPUT.PUT_LINE('Counter: ' || v_counter);
            v_counter := v_counter + 0.5;
         END LOOP;
      END;
      \/
      <\/code><\/pre>\n\n\n\n
      Why this works:<\/strong> WHILE<\/code> loops allow more flexibility with data types and control logic, unlike FOR<\/code> loops that enforce integer control variables.<\/p>\n\n\n\n
      Summary: Do’s and Don’ts<\/h2>\n\n\n\n
      Do<\/strong><\/th>Don\u2019t<\/strong><\/th><\/tr><\/thead>
      Use implicit loop variables (FOR i IN...<\/code>)<\/td>Declare loop index as NUMBER<\/code>, FLOAT<\/code>, etc.<\/td><\/tr>
      Use INTEGER<\/code>, PLS_INTEGER<\/code>, or literals<\/td>Use decimals like 1.1 .. 5.5<\/code> in loop range<\/td><\/tr>
      Use WHILE<\/code> loop for decimal counters<\/td>Expect FOR<\/code> loop to handle non-integer logic<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      Conclusion<\/h2>\n\n\n\n
      The PLS-00364<\/strong> error is a strict PL\/SQL constraint that enforces loop index variables to be integers only<\/strong> within FOR<\/code> loops. To fix this:<\/p>\n\n\n\n
        \n
      • Let Oracle implicitly create the index variable<\/li>\n\n\n\n
      • Ensure loop bounds are integers<\/li>\n\n\n\n
      • Use WHILE<\/code> loops if your logic needs floating-point arithmetic<\/li>\n<\/ul>\n\n\n\n
        By following these guidelines, your loops will compile cleanly and behave as expected.<\/p>\n","protected":false},"excerpt":{"rendered":"
        In PL\/SQL, FOR loops are a powerful control structure used to iterate over a defined range of numbers or rows. However, this construct has specific syntactic rules. One common error developers encounter is: PLS-00364: Loop index variable <name> must be an integer This article explains why this error occurs, provides examples, and offers clear solutions […]<\/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-1989","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\/1989","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=1989"}],"version-history":[{"count":1,"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/posts\/1989\/revisions"}],"predecessor-version":[{"id":1990,"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/posts\/1989\/revisions\/1990"}],"wp:attachment":[{"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/media?parent=1989"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/categories?post=1989"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/tags?post=1989"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}