Skip to content

0.8.0 breaks Oracle function #203

Closed
Closed

Description

@jacobat

After upgrading to 0.8.0 we're seeing an error when calling one of our Oracle functions. The function has the signature:

FUNCTION get_customers (customer_id               IN NUMBER,
                        user_id                   IN NUMBER,
                        p_customers_tab           OUT NOCOPY my_package.tab_CustomersType
                        )
                        RETURN NUMBER;

TYPE tab_CustomersType IS TABLE OF my_package.rec_CustomersType;

TYPE rec_CustomersType IS RECORD(
  customer_id  number(10),
  name    varchar2(255)
);

When calling it we see the error:

stmt.c:267:in oci8lib_300.so: ORA-06550: linje 12, kolonne 13: (OCIError)
PLS-00306: forkert antal eller typer af argumenter i kald til 'GET_CUSTOMERS'
ORA-06550: linje 12, kolonne 1:
PL/SQL: Statement ignored

Our Oracle version is:

 VERSION INFORMATION:
    TNS for Linux: Version 19.0.0.0.0 - Production
    Oracle Bequeath NT Protocol Adapter for Linux: Version 19.0.0.0.0 - Production
    TCP/IP NT Protocol Adapter for Linux: Version 19.0.0.0.0 - Production
 Version 19.7.0.0.0

I ran a git bisect that point to bfd14d4 as the offending commit.

Activity

  1. yahonda commented on Apr 13, 2026

    @yahonda
    Collaborator

    We tried to reproduce this issue with the following test case but it passes on all versions from v0.8.0 through current master (Oracle 23c Free and Oracle 11g XE):

    CREATE OR REPLACE PACKAGE test_out_record_pkg IS
      TYPE rec_customer IS RECORD (
        customer_id NUMBER(10),
        name VARCHAR2(255)
      );
      TYPE tab_customer IS TABLE OF rec_customer;
      FUNCTION get_customers(p_id IN NUMBER, p_customers OUT NOCOPY tab_customer) RETURN NUMBER;
    END;
    result = plsql.test_out_record_pkg.get_customers(42)

    Could you provide a minimal reproducible example (table DDL, type/package definition, and the Ruby call) that triggers the PLS-00306 error? There may be something specific to your schema setup that we are not capturing in our test.

  2. yahonda commented on Apr 13, 2026

    @yahonda
    Collaborator

    See #263 for the test case we used.

  3. jacobat commented on Apr 13, 2026

    @jacobat
    Author

    Sorry, I haven't been working with Oracle for a while so I'm not able to provide more detailed information about this issue. Perhaps just close the issue?

  4. yahonda commented on Apr 13, 2026

    @yahonda
    Collaborator

    Thanks for the update.

    Perhaps just close the issue?

    Yes. Let me close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions