Skip to Main Content

SQLcl: MCP Server & SQL Prompt

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Debugging errors on Project Deploy

Plamen MushkovFeb 27 2025

Hi all,

I am at the stage where I deploy a release to a new database (username and schema are the same in both databases). I have few question related to the different types of error I have faced and I hope I could get some help.

  • First of all, I am running “project deploy” in debug and verbose mode. However, I often can't find the exact error that caused the deploy failure. The error messages in the console is too vague, so I hoped there could be another place to find more details. Here is an example:
Please review automatically generated error log:
sqlcl-lb-error1740673175572.log
For additional information run using -debug and/or -log parameters.


An error has occurred: 
liquibase.exception.LiquibaseException: liquibase.exception.MigrationFailedException: Migration failed for changeset releases/apex/f522/f522xml::INSTALL_522::SQLCL-Generated:
Reason: liquibase.exception.DatabaseException: Error occurred and failonerror set to true, stopping execution.
PL/SQL procedure successfully completed.

I was looking for this sqlcl-lb-error1740673175572.log file, but couldn't find it. I also checked the DATABASECHANGELOG and DATABASECHANGELOG_ACTIONS tables in the destination database, but the exact error wasn't available too.

What I understand from the console message is that deployment failed while installing APEX app 522, but that's all.

  • Other type of error I face is with triggers. They fail during installation, although I have no issue with the trigger code and it gets compiled without any errors if I run it manually. Is that a common error?

  • I need a general advice on starting a new project and doing deployments to a database that already has some of the object from the source database in place. When I start using the project feature and create the initial release, I'd grab all database object. What I intend to do is exclude from the XML changelog the ones that are already in the destination database. What's the best approach to such situation and do I need to take care of this in consecutive deployments?

Besr regards, Plamen

Comments
Post Details
Added on Feb 27 2025
1 comment
272 views