AIF DATA - Standalone - CALENDAR_LOAD_ADHOC - CREATE_PARTITION_PRESETUP_JOB Fails with "Invalid Date"
(Doc ID 2998819.1)
Last updated on JANUARY 24, 2024
Applies to:
Oracle Retail AI Foundation Cloud Service - Version 23.2 and laterOracle Retail Insights Cloud Service Advanced Edition - Version 23.2 and later
Oracle Retail Science Platform Cloud Service - Version 23.1 and later
Information in this document applies to any platform.
Goal
Consider the following scenario:
- Successfully ran RDE_EXTRACT_DIM_INITIAL_ADHOC to extract calendar and other hierarchy info from MFCS to the staging tables in RI.
- However, upon running the CALENDAR_LOAD_ADHOC to partition the environment, CREATE_PARTITION_PRESETUP_JOB is failing with a date of 2-Feb-2020. This date was chosen because this was the first day in the CALENDAR table in MFCS. However, when querying W_MCAL_PERIOD_DS, it looks like the MCAL_PERIOD_ST_DT is 1-Mar-2020 (first day of the second month in CALENDAR in MFCS). Why doesn't W_MCAL_PERIOD_DS start from 2-Feb-2020 like CALENDAR table in MFCS?
- Additional context, the history that will be loaded will be starting 25-Apr-2021 and it is desirable to run CALENDAR_LOAD_ADHOC with a CREATE_PARTITION_PRESETUP_JOB date of 1-Mar-2020.
The CREATE_PARTITION_PRESETUP_JOB error is "errorInfo":"EXT_PROG_SYS_ERR:partitionpresetup.ksh: date: invalid date 'CREATE_PARTITION_PRESETUP_JOB=2020-02-02'"
How should this be resolved? Is it possible to rerun the failed CREATE_PARTITION_PRESETUP_JOB or is it required to rerun the whole CALENDAR_LOAD_ADHOC process?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |