The Oracle 12.2 version has a feature called 'Application Continuity'. Application Continuity is used to improve the user experience when handling both unplanned outages and planned maintenance. It masks outages from end users and applications by recovering the in-flight work for impacted database sessions following outages. Application Continuity performs this recovery beneath the application so that the outage appears to the application as a slightly delayed execution.
The impact for this will be for anybody who is connecting Data Stage to an Oracle database 12.2 version.
|Who would benefit from this IDEA?||As end user of Data Stage application who is doing reporting on Oracle database version 12.2, I don't want to be impacted by database outages.|
How should it work?
1. The proposed solution is stated in the oracle documentation https://www.oracle.com/technetwork/database/options/clustering/applicationcontinuity/overview/application-continuity-wp-12c-1966213.pdf page 19 - "Configuring Application Continuity". For more details please check the link.
2. The measurable benefits will be for users who are connecting Data Stage jobs to an Oracle database 12.2 version. Application Continuity masks outages from end users and applications by recovering the in-flight work for impacted database sessions following outages.
3. There is no workaround.
|Priority Justification||Idea is ranked "high" since it avoids the impact on users in case of certain Oracle database 12.2 maintenance activities.|
|Customer Name||ING Tech|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions