Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 238 Big Data Appliance
- 1.9K Data Science
- 450.2K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 544 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.8K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.5K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 154 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 437 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
sqlcl (22.1.1.131.0820) SEVERE liquibase.parser Invalid byte 1 of 1-byte UTF-8 sequence
Oracle SQLDeveloper Command-Line (SQLcl) version: 22.1.1.0 build: 22.1.1.131.0820
Liquibase at 11:53:51 (version 4.9.1 #0 built at 2022-05-03 17:23+0000)
openjdk version "11.0.14" 2022-01-18 LTS
Hi,
I get the following error when running a changelog:
SQL> lb update -changelog controller.xml
--Starting Liquibase at 12:05:46 (version 4.9.1 #0 built at 2022-05-03 17:23+0000)
2022-05-30 12:05:49.302 SEVERE liquibase.parser Invalid byte 1 of 1-byte UTF-8 sequence.
Invalid byte 1 of 1-byte UTF-8 sequence.
Any ideas what the root cause might be?
Comments
-
Hi everyone,
I was able to solve this puzzle myself.
Please find the mistakes I made which led to the error.
1st: I created a scheduler job using SQL Developer and used the standard NLS setting which was set to German. This led to one attribute becoming a €-value which was not supported. I changed NLS settings in SQL developer to American and this issue was gone.
2nd: there was a comment line including a German letter ü which also led to the error. When I replaced that it worked fine.
One more thin I would like to point out.
I think in an earlier version (21.4.1) the error message was more conclusive:
SQL> lb updatesql -changelog controller.xml
2022-04-04 14:05:30.141 SEVERE liquibase.parser Invalid byte 1 of 1-byte UTF-8 sequence.
Processing has failed for
your request.
liquibase.exception.SetupException: Error parsing line 23 column 138 of job/job_p_fill_t_cicd_user3_job.xml: Invalid byte 1 of 1-byte UTF-8 sequence.
I think this topic could be closed.
-
here an interesting older entry with similar issue
https://community.oracle.com/tech/developers/discussion/4284265/liquibase-issues-in-sqlcl-19-2