About Application Updates
Application updates are available for major releases (quarterly basis), patches (monthly basis), and emergency fixes (as needed).
Except the emergency patches, you can decide when to apply the application updates. You can schedule the update for current and major releases to occur by a deadline. After that deadline, Oracle automatically updates your application. These updates have zero downtime.
The auto-update process updates the data model and then immediately after the data model update, this process updates the content. This process runs the incremental data pipelines as part of the data model upgrade process when upgrade is scheduled to run for the day. You can check the last refresh date either from the Console or the subject area to ensure that the data has been refreshed as part of the data model upgrade process.
To ensure a successful update, verify the connection between Oracle Fusion Data Intelligence and all of the sources is healthy. It's also required to define a data refresh schedule with a valid date, since the application update is triggered during the incremental load process. You must ensure that the Data Pipeline Status toggle is in enabled status before any release update. This toggle is available on the Pipeline Settings page, under Data Pipeline.
You can view the application updates and plan accordingly using the Release Updates tile under Service Administration on the Console. You also see a notification on the Data Configuration page when an application update is available. You can then plan to uptake using the Release Updates tile.You can specify the date and time (in your local time zone) the upgrade will begin. If the upgrade and an incremental refresh are scheduled at the same time,the upgrade runs first, followed by the incremental refresh.
During the application upgrade, the data gets refreshed to support new data model and content changes. This upgrade provides the ability to use new functionality such as functional areas, changes in the data model, changes in the content such as KPIs and dashboards. The upgrade deletes data related to any deactivated functional areas and you may potentially lose the data that was there in the warehouse for these functional areas. As part of application upgrade, the system also cleans up the data warehouse based on the relative initial extract date that you specified in the Pipeline Parameters.
The data pipelines for functional areas that have been activated are preserved during the upgrade. The data pipelines in Saved or Scheduled status are reset to Saved status. To activate these data pipelines, you must set them to Activated status. You can skip an upgrade for one release. However, you must upgrade when the next patch is available. The application upgrade adds new and replaces existing modified content with the latest version. If you've merged an external application, then as part of the upgrade some objects within the external semantic model get upgraded too. Hence after every upgrade, you're recommended to download the latest semantic model uploaded through the user interface and make any changes on top of it.