FSDF 8.1 Upgrade Questions on the Handling of Custom Tables and Columns by the ModelUpgrade Utility
(Doc ID 2735587.1)
Last updated on JULY 13, 2021
Applies to:Oracle Financial Services Data Foundation - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Oracle Financial Services Data Foundation (FSDF)
Table to Table (T2T) Data Mapping
Data Management Tools (DMT)
Slowly Changing Dimensions (SCD)
With reference to "OFSAA_FSDF_220.127.116.11.0_Upgrade_Guide.pdf" document Page 10, the Model upgrade utility's PRE/POST scripts takes backup, clear metadata and restore data and metadata.
How will the model upgrade utility PRE scripts handle / impact any custom tables and columns, actual custom data and the METADATA created on custom tables and columns?
After reviewing the documentation, have downloaded the setup kit and went through the ModelUpgrade utility PRE and POST scripts at a high level, while custom tables are a concern, looks like it is dealing with the dropped columns and tables and need to confirm support of these scripts on the custom tables.
As per the current understanding (Page 13) the PRE Script will create a table called DROPPED_DATAELEMENTS_CUSTOMIZATION_81, while referring the corresponding dropped table column Excel sheet there is a column called RETAIN_AS_CUSTOMIZATION, if the table or column, this column should be updated as 'Y', (Page 17, note section paragraph 2), however, there is no specific mention, at what stage of the upgrade process this flag should be set in order to retain these dropped tables/columns or is it required to add all custom tables to this list?
As per the flow this table DROPPED_DATAELEMENTS_CUSTOMIZATION_81 is created after post scripts and the Backup and clean up of data is already taken place, in the PRE scripts there are DELETE statements used (instead of TRUNCATE or DROP Partition) on the entire table data, this very much could MAX out redo log (in the dropped column list there is even Fct Common Acct summary table, which is one of the biggest tables with several Million records), and are therefore trying to avoid an entire deletion of the table scenario and UNDO log overflow.
Can the Model Upgrade utility PRE and POST scripts be skipped if no Table or columns are dropped in the merging process?
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