{"id":1991,"date":"2025-05-26T01:03:32","date_gmt":"2025-05-26T05:03:32","guid":{"rendered":"https:\/\/molecularsciences.org\/content\/?p=1991"},"modified":"2025-05-22T01:12:20","modified_gmt":"2025-05-22T05:12:20","slug":"solving-pls-00410-duplicate-fields-in-record-table-or-argument-list-are-not-allowed","status":"publish","type":"post","link":"https:\/\/molecularsciences.org\/content\/solving-pls-00410-duplicate-fields-in-record-table-or-argument-list-are-not-allowed\/","title":{"rendered":"Solving PLS-00410: Duplicate Fields in RECORD, TABLE, or Argument List Are Not Allowed"},"content":{"rendered":"\n

The PL\/SQL error PLS-00410<\/strong> is encountered when the compiler finds duplicate identifiers<\/strong> in a RECORD<\/code>, TABLE<\/code>, or subprogram argument list<\/strong>. Since PL\/SQL does not allow two fields or parameters to share the same name within the same scope or structure, this error flags such issues.<\/p>\n\n\n\n

This article will explain the causes of this error, demonstrate examples that produce it, and show how to fix the problem effectively.<\/p>\n\n\n\n

Error Message Explained<\/strong><\/h2>\n\n\n\n

PLS-00410:<\/strong><\/p>\n\n\n\n

\n

Duplicate fields in RECORD, TABLE, or argument list are not allowed<\/p>\n<\/blockquote>\n\n\n\n

What it means:<\/h3>\n\n\n\n

This error occurs when two or more identifiers<\/strong> (field names or parameters) have the same name<\/strong> in a RECORD<\/code>, TABLE<\/code>, or subprogram definition.<\/p>\n\n\n\n

Common Scenarios That Trigger PLS-00410<\/strong><\/h2>\n\n\n\n

1. Duplicate Fields in RECORD<\/h3>\n\n\n\n

Example (Incorrect):<\/h4>\n\n\n\n
DECLARE
   TYPE employee_rec IS RECORD (
      emp_id NUMBER,
      emp_name VARCHAR2(100),
      emp_id NUMBER  -- \u274c Duplicate field name
   );
BEGIN
   NULL;
END;
\/
<\/code><\/pre>\n\n\n\n
Error:<\/h3>\n\n\n\n
PLS-00410: duplicate fields in RECORD, TABLE or argument list are not allowed
<\/code><\/pre>\n\n\n\n
Fix:<\/h3>\n\n\n\n
Change one of the field names to be unique.<\/p>\n\n\n\n
DECLARE
   TYPE employee_rec IS RECORD (
      emp_id NUMBER,
      emp_name VARCHAR2(100),
      emp_dept_id NUMBER  -- \u2705 Unique field name
   );
BEGIN
   NULL;
END;
\/
<\/code><\/pre>\n\n\n\n
2. Duplicate Parameters in a Procedure or Function<\/h3>\n\n\n\n
Example (Incorrect):<\/h4>\n\n\n\n
CREATE OR REPLACE PROCEDURE update_salary (
   emp_id NUMBER,
   emp_id NUMBER  -- \u274c Duplicate parameter
)
IS
BEGIN
   NULL;
END;
\/
<\/code><\/pre>\n\n\n\n
Error:<\/h3>\n\n\n\n
PLS-00410: duplicate fields in RECORD, TABLE or argument list are not allowed
<\/code><\/pre>\n\n\n\n
Fix:<\/h3>\n\n\n\n
Rename one of the parameters:<\/p>\n\n\n\n
CREATE OR REPLACE PROCEDURE update_salary (
   p_emp_id NUMBER,
   p_new_salary NUMBER
)
IS
BEGIN
   DBMS_OUTPUT.PUT_LINE('Updating employee ' || p_emp_id || ' salary to ' || p_new_salary);
END;
\/
<\/code><\/pre>\n\n\n\n
3. Duplicate Fields in a TABLE Type<\/h3>\n\n\n\n
Just like RECORD<\/code>, if you define a PL\/SQL TABLE type or VARRAY<\/code> with duplicate fields, the error will be raised.<\/p>\n\n\n\n
\n
However, note that TABLE<\/code> and VARRAY<\/code> structures do not allow multiple fields. The confusion often arises when people try to define composite types improperly.<\/p>\n<\/blockquote>\n\n\n\n
Special Note: Shadowing Doesn\u2019t Apply<\/strong><\/h2>\n\n\n\n
PL\/SQL does not allow field shadowing inside composite types. Even if you’re used to shadowing variable names in nested blocks, that doesn’t apply to parameter lists or RECORD definitions. Every field must be uniquely named.<\/p>\n\n\n\n
Best Practices to Avoid PLS-00410<\/h2>\n\n\n\n
    \n
  • Use prefixes<\/strong> like p_<\/code> for parameters, v_<\/code> for variables, r_<\/code> for records to avoid naming collisions.<\/li>\n\n\n\n
  • Avoid copy-pasting<\/strong> without checking for duplicate names in parameter lists or record structures.<\/li>\n\n\n\n
  • Use meaningful field names<\/strong> to distinguish attributes (e.g., emp_id<\/code>, dept_id<\/code>, mgr_id<\/code>).<\/li>\n<\/ul>\n\n\n\n
    Example: Correct Use in RECORD and Procedure<\/h2>\n\n\n\n
    DECLARE
       TYPE employee_rec IS RECORD (
          emp_id     NUMBER,
          emp_name   VARCHAR2(100),
          dept_id    NUMBER
       );

       r_emp employee_rec;

       PROCEDURE print_employee(p_emp_id NUMBER, p_emp_name VARCHAR2) IS
       BEGIN
          DBMS_OUTPUT.PUT_LINE('ID: ' || p_emp_id || ', Name: ' || p_emp_name);
       END;

    BEGIN
       r_emp.emp_id := 101;
       r_emp.emp_name := 'Alice';
       r_emp.dept_id := 10;

       print_employee(r_emp.emp_id, r_emp.emp_name);
    END;
    \/<\/code><\/pre>\n\n\n\n
    Summary Table<\/h2>\n\n\n\n
    Mistake<\/strong><\/th>Error<\/strong><\/th>Fix<\/strong><\/th><\/tr><\/thead>
    Two fields with same name in RECORD<\/td>PLS-00410<\/td>Rename one field<\/td><\/tr>
    Two procedure parameters with same name<\/td>PLS-00410<\/td>Use distinct parameter names<\/td><\/tr>
    Misuse of TABLE or VARRAY syntax<\/td>PLS-00410<\/td>Use scalar values or RECORD properly<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    Conclusion<\/h2>\n\n\n\n
    The PLS-00410<\/strong> error is a clear indicator of poor naming or a copy-paste mistake in field or parameter lists. It\u2019s simple to fix by renaming the duplicate identifiers<\/strong> to make each one distinct and meaningful<\/strong>. Keeping your naming conventions consistent and readable helps avoid such conflicts and improves maintainability.<\/p>\n\n\n\n
    <\/p>\n","protected":false},"excerpt":{"rendered":"
    The PL\/SQL error PLS-00410 is encountered when the compiler finds duplicate identifiers in a RECORD, TABLE, or subprogram argument list. Since PL\/SQL does not allow two fields or parameters to share the same name within the same scope or structure, this error flags such issues. This article will explain the causes of this error, demonstrate […]<\/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-1991","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\/1991","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=1991"}],"version-history":[{"count":2,"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/posts\/1991\/revisions"}],"predecessor-version":[{"id":1996,"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/posts\/1991\/revisions\/1996"}],"wp:attachment":[{"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/media?parent=1991"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/categories?post=1991"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/molecularsciences.org\/content\/wp-json\/wp\/v2\/tags?post=1991"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}