sqlcl (ver. 22.1.0.90.1611) throws error upon running lb update for apex app

wes_fdny

SQLcl version: 22.1.0.90.1611 - April 5, 2022

java version "16.0.2" 2021-07-20

database version:Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

steps to reproduce:

SQL> lb update -changelog YOURAPPEXAPPID.xml

--Starting Liquibase at 12:51:41 (version 4.7.1 #0 built at 2022-01-25 22:12+0000)

2022-05-03 12:51:41.247 SEVERE liquibase.parser cvc-complex-type.3.2.2: Attribute 'runInTrans' is not allowed to appear in element 'changeSet'.

cvc-complex-type.3.2.2: Attribute 'runInTrans' is not allowed to appear in element 'changeSet'.

There is no problem in previous sqlcl version:SQLcl version: 21.4.1.0 build: 21.4.1.17.1458

SQL> lb update -changelog YOURAPPEXAPPID.xml

ScriptRunner Executing: YOURAPPEXAPPID.xml::def123a94ee3657bcd71ee6ee51ce4dc28f2af9b::(WTC_APP)-Generated

-- DONE

2022-05-03 13:14:09.625 INFO liquibase.changelog Script executed successfully

2022-05-03 13:14:09.633 INFO liquibase.changelog ChangeSet YOURAPPEXAPPID.xml::def123a94ee3657bcd71ee6ee51ce4dc28f2af9b::(USER)-Generated ran successfully in 3319ms

2022-05-03 13:14:09.654 INFO liquibase.lockservice Successfully released change log lock

######## ERROR SUMMARY ##################

Errors encountered:0

######## END ERROR SUMMARY ##################

code difference within YOURAPPEXAPPID.xml between latest and previous sqlcl build:

...

<changeSet id="5076b7d8... runInTrans="false" >

...

Anyone else run into this with their apex app migration after downloading the new sqlcl version?

wes_fdny

Bug confirmed by Oracle and fix is targeted for next release

User_ACXNB

I experienced the same issue with 22.1.0.90.1611. I dowloaded the previous version, ran the same commands and there is no error. 'runInTrans' property doesn't show up in the xml with 21.4.1.17.1458.

wes_fdny

Exactly.

I opened a bug with Oracle SR.

wes_fdny

Bug confirmed by Oracle and fix is targeted for next release

wes_fdny

22.1.1.131.0820 released and bug fixed.

will try this out later