H2T Partitioning With Fic_mis_date And N_load_run_id
(Doc ID 2919978.1)
Last updated on JANUARY 15, 2023
Applies to:
Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.7.5.0 and laterInformation in this document applies to any platform.
Goal
After partitioned the table with fic_mis_date and put entries in rev_tab_partitions tables.
H2T can execute successfully.
customer has a requirement to keep rows of the same fic_mis_date with mutiple n_load_run_id in the same table
but when we run the second time, rows of the first n_load_run_id are deleted then rows of second n_load_run_id are inserted.
example
first time we run H2T with fic_mis_date = 31-MAY-2020 and n_load_run_id = 1
second time we run H2T with fic_mis_date = 31-MAY-2020 and n_load_run_id = 0
rows of fic_mis_date = 31-MAY-2020 and n_load_run_id = 1 are deleted
rows of fic_mis_date = 31-MAY-2020 and n_load_run_id = 0 are inserted
the table only remains rows of n_load_run_id = 0 because H2T execute delete from table where fic_mis_date = 31-MAY-2020
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! |
In this Document
Goal |
Solution |
References |