version 1.0.4 of the UTF8 migration action pack has been released and is available from our market place:
One of them addresses the issue with the date conversion.
Original Message:
Sent: Sep 16, 2024 03:17 AM
From: Markus Embacher
Subject: Migrate v21 Oracle 19c DB to UTF8 with Workflow PCK.AUTOMIC_UTF-8-MIG.START
Hi Rolf,
it looks like there is an issue with the date created by one of the queries. The date format is defined as YYYY-MM-DD, but XAO_IDNR_END shows
'2024-09-11 00:00:00.000'
which does not match the given data format.
Kindly open a case on that issue.
As a temporary workaround you can modify PCK.AUTOMIC_UTF-8.MIG.SQLI.GET.GET_XAO_IDNR_END.SRC and change the date settings to:
Regards, Markus
Original Message:
Sent: Sep 13, 2024 02:51 AM
From: Rolf Muther
Subject: Migrate v21 Oracle 19c DB to UTF8 with Workflow PCK.AUTOMIC_UTF-8-MIG.START
I run the utf8 migration first time in my test environment and get this error.
My source db is dgfc1 and target is dgfc3. Both connection tests are ok.
Service Pack is 1.03
Any ideas?
2024-09-12 10:35:55 - U02000005 Job 'PCK.AUTOMIC_UTF-8.MIG-STEP03.SUPPORT.NOILM.SRC' with RunID '6722756' is to be started.2024-09-12 10:35:55 - U02012001 Successfully established connection to 'lsdba02t.vt.ch:1528/DGFC1' with user 'uc4'.2024-09-12 10:35:55 Oracle2024-09-12 10:35:55 Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production2024-09-12 10:35:55 Version 19.18.0.0.02024-09-12 10:35:55 - U02012014 JDBC Driver version: 19.3.0.0.02024-09-12 10:35:55 delete from uc_migration2024-09-12 10:35:55 - U02012003 0 row(s) affected2024-09-12 10:35:55 alter session set nls_date_format = 'YYYY-MM-DD'2024-09-12 10:35:55 - U02012003 0 row(s) affected2024-09-12 10:35:55 insert into uc_migration values (1, '1997-04-27', '2024-08-27', 1000001, 6357227, '2024-09-11', '2024-09-11 00:00:00.000', upper('DGFC1'),'N')2024-09-12 10:35:55 ORA-01830: date format picture ends before converting entire input string2024-09-12 10:35:55 - U02004025 Job-script execution was aborted.2024-09-12 10:35:55 - U02012006 SQL Rollback executed