LiquibasePro未生成Package、PackageBody至changeLog文件该如何解决？

Hey there, I’ve run into this exact issue with Liquibase Pro before—frustrating when those critical PL/SQL objects don’t show up in your auto-generated changelog! Let me break down the most common fixes that got this working for me and other devs I’ve collaborated with:

• Ensure you’re explicitly including PL/SQL object types
  Liquibase doesn’t always scan for packages, package bodies, or functions by default. You need to tell it to include these objects either via command line flags or your liquibase.properties file.
  For example, when running the generateChangeLog command, add:

  liquibase generateChangeLog --includeObjects=package,packageBody,function
  

  Or add this line to your liquibase.properties to make it a default:

  includeObjects=package,packageBody,function
  

  Note: Double-check the object type names for your specific database—for Oracle, you might need to use PACKAGE and PACKAGE BODY (uppercase) instead of the lowercase versions.

• Verify your Liquibase Pro version and database compatibility
  Older versions of Liquibase Pro had limited support for scanning complex PL/SQL objects. Make sure you’re on the latest stable release. You can check your current version with:

  liquibase --version
  

  Upgrading often resolves edge-case scanning issues, especially if you’re working with newer database versions (like Oracle 19c+/PostgreSQL 14+).

• Use Liquibase’s dedicated PL/SQL change types (or manual SQL entries)
  If auto-scanning still fails, you can manually define these objects in your changelog using Liquibase Pro’s built-in change types. For example, to create a package:

  <changeSet id="create_employee_pkg" author="your-name">
    <createPackage schemaName="HR" packageName="EMPLOYEE_PKG">
      <sql>
        CREATE OR REPLACE PACKAGE HR.EMPLOYEE_PKG AS
          PROCEDURE get_emp_details(p_emp_id IN NUMBER, p_result OUT VARCHAR2);
        END EMPLOYEE_PKG;
      </sql>
    </createPackage>
  </changeSet>
  

  For package bodies or functions, use <createPackageBody> or <createFunction> respectively. If you prefer full control, you can also use a plain <sql> tag to embed your PL/SQL code directly.

• Check your database user permissions
  The database user Liquibase is using needs sufficient privileges to read metadata about PL/SQL objects. For example, in Oracle, the user needs SELECT access to ALL_OBJECTS and ALL_SOURCE views, or the SELECT_CATALOG_ROLE role. If permissions are missing, Liquibase can’t detect these objects during scanning.

Start with the first two checks—they’re the quickest wins. If those don’t work, move to manual changelog entries or verifying permissions.

内容的提问来源于stack exchange，提问作者Timur