Date parsing exception on Windows (requires SEPT for month)

General Discussion
1

Hi

In my project I use Liquibase to populate database for my integration tests.
The jdbc url: “jdbc:h2:mem:dev;MODE=Oracle”

The development finished at some stage, everything was fine.
After I returned to it after a year, my integration tests stopped working with the following exception:

liquibase.exception.LiquibaseException: liquibase.exception.MigrationFailedException: Migration failed for changeset db/billrun8324586/tem_bill_run.sql::raw::includeAll:
     Reason: liquibase.exception.DatabaseException: Function "TO_TIMESTAMP": Invalid date format: 
" Tried to parse one of '[Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sept, Oct, Nov, Dec, ]' but failed 
(may be an internal error?). 
Details: \000a    TO_TIMESTAMP('27-SEP-21 10.00.00.000000000 PM', 'DD-MON-RR HH.MI.SSXFF AM')\000a                     ^                            ,                                      ^ <-- Parsing failed at this point";

While it is not clear from this excerpt, the arrows point to month name SEP/Sept.
After changing month in the scripts from SEP to SEPT the tests pass.

BUT
The problem only occurs on Windows. On Ubuntu in our CI everything worked and works without any change. What’s more when I do the build with modified month (SEPT), the tests fail on some assertions. Definitely the scripts do not do what they are supposed to.

And using “SEPT” is clearly wrong, not conforming to format specification. When I try to use different formats, like YYYY-MM-DD, I get the same exception requiring me to use months from this set: [Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sept, Oct, Nov, Dec, ].
Looks like to format in TO_TIMESTAMP function is ignored.

Many thanks for your help with this!
Ewa