Note that there are some explanatory texts on larger screens.

plurals
  1. POOracle 10g claiming that a package body has errors when it does not
    primarykey
    data
    text
    <p>I have a few packages on my oracle instance. When I recreate my database from scratch, I get zero invalid objects, and no warnings from liquibase.</p> <p>Then, when I call a package method, like so:</p> <pre><code>new SimpleJdbcCall(jdbcTemplate).withCatalogName(packageName).withProcedureName(storedProcedureName).execute(parameterMap); </code></pre> <p>It gives me the following error:</p> <pre><code>org.springframework.jdbc.UncategorizedSQLException: CallableStatementCallback; uncategorized SQLException for SQL [{call CALENDAR_MANAGEMENT.CREATE_SUMMARIES(?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}]; SQL state [72000]; error code [4063]; ORA-04063: package body "ETPDEV.CALENDAR_MANAGEMENT" has errors ORA-06508: PL/SQL: could not find program unit being called: "ETPDEV.CALENDAR_MANAGEMENT" ORA-06512: at line 1; nested exception is java.sql.SQLException: ORA-04063: package body "ETPDEV.CALENDAR_MANAGEMENT" has errors ORA-06508: PL/SQL: could not find program unit being called: "ETPDEV.CALENDAR_MANAGEMENT" ORA-06512: at line 1 Caused by: java.sql.SQLException: ORA-04063: package body "ETPDEV.CALENDAR_MANAGEMENT" has errors ORA-06508: PL/SQL: could not find program unit being called: "ETPDEV.CALENDAR_MANAGEMENT" ORA-06512: at line 1 </code></pre> <p>Checking for invalid objects again turns up nothing. Compiling CALENDAR_MANAGEMENT again completes normally without errors.</p> <p>I've tried a full schema recompile, but that did not work.</p> <p>When I call it from SQLDeveloper, it works normally.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload