Migration to UTF-8 DB fails due to problem with date format
search cancel

Migration to UTF-8 DB fails due to problem with date format

book

Article ID: 377778

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

The migration fails in PCK.AUTOMIC_UTF-8.MIG-STEP05.COPY.INIT.DATA.NOILM.DST with the following error:

2024-05-18 03:14:32       commit
2024-05-18 03:14:32       insert /*\+ APPEND \*/ into MELD NOLOGGING select * from MELD@uc4source where meld_timestamp <= to_date('16.05.24')
2024-05-18 03:14:33       ORA-01843: not a valid month

The DB has set the NLS DATE to DD.MM.RR

These are the NLS parameters of the source DB:

U00029110 UCUDB - Session-Parameter:
U00003535 DB-INFO: 'NLS_LANGUAGE          = GERMAN'
U00003535 DB-INFO: 'NLS_TERRITORY          = GERMANY'
U00003535 DB-INFO: 'NLS_CURRENCY          = €'
U00003535 DB-INFO: 'NLS_ISO_CURRENCY        = GERMANY'
U00003535 DB-INFO: 'NLS_NUMERIC_CHARACTERS     = ,.'
U00003535 DB-INFO: 'NLS_CALENDAR          = GREGORIAN'
U00003535 DB-INFO: 'NLS_DATE_FORMAT         = DD.MM.RR'
U00003535 DB-INFO: 'NLS_DATE_LANGUAGE        = GERMAN'
U00003535 DB-INFO: 'NLS_SORT            = GERMAN'
U00003535 DB-INFO: 'NLS_TIME_FORMAT         = HH24:MI:SSXFF'
U00003535 DB-INFO: 'NLS_TIMESTAMP_FORMAT      = DD.MM.RR HH24:MI:SSXFF'
U00003535 DB-INFO: 'NLS_TIME_TZ_FORMAT       = HH24:MI:SSXFF TZR'
U00003535 DB-INFO: 'NLS_TIMESTAMP_TZ_FORMAT     = DD.MM.RR HH24:MI:SSXFF TZR'
U00003535 DB-INFO: 'NLS_DUAL_CURRENCY        = €'
U00003535 DB-INFO: 'NLS_COMP            = BINARY'
U00003535 DB-INFO: 'NLS_LENGTH_SEMANTICS      = BYTE'
U00003535 DB-INFO: 'NLS_NCHAR_CONV_EXCP       = FALSE'
U00003535 DB-INFO: 'SID               = 10'
U00029111 UCUDB - Datenbank-Parameter:
U00003535 DB-INFO: 'NLS_RDBMS_VERSION        = 19.0.0.0.0'
U00003535 DB-INFO: 'NLS_NCHAR_CONV_EXCP       = FALSE'
U00003535 DB-INFO: 'NLS_LENGTH_SEMANTICS      = BYTE'
U00003535 DB-INFO: 'NLS_COMP            = BINARY'
U00003535 DB-INFO: 'NLS_DUAL_CURRENCY        = ?'
U00003535 DB-INFO: 'NLS_TIMESTAMP_TZ_FORMAT     = DD.MM.RR HH24:MI:SSXFF TZR'
U00003535 DB-INFO: 'NLS_TIME_TZ_FORMAT       = HH24:MI:SSXFF TZR'
U00003535 DB-INFO: 'NLS_TIMESTAMP_FORMAT      = DD.MM.RR HH24:MI:SSXFF'
U00003535 DB-INFO: 'NLS_TIME_FORMAT         = HH24:MI:SSXFF'
U00003535 DB-INFO: 'NLS_SORT            = GERMAN'
U00003535 DB-INFO: 'NLS_DATE_LANGUAGE        = GERMAN'
U00003535 DB-INFO: 'NLS_DATE_FORMAT         = DD.MM.YY'
U00003535 DB-INFO: 'NLS_CALENDAR          = GREGORIAN'
U00003535 DB-INFO: 'NLS_NUMERIC_CHARACTERS     = ,.'
U00003535 DB-INFO: 'NLS_NCHAR_CHARACTERSET     = AL16UTF16'
U00003535 DB-INFO: 'NLS_CHARACTERSET        = WE8ISO8859P15'
U00003535 DB-INFO: 'NLS_ISO_CURRENCY        = GERMANY'
U00003535 DB-INFO: 'NLS_CURRENCY          = ?'
U00003535 DB-INFO: 'NLS_TERRITORY          = GERMANY'
U00003535 DB-INFO: 'NLS_LANGUAGE          = GERMAN'

Cause

This is a defect

Resolution

The issue has been fixed in v1.0.4 of the UTF-8 Migration Package which is available for download.

Additional Information

The reference for the fix is DE128511