Can We Drop a Table that Has Been Enabled for Online Patching?
(Doc ID 3074852.1)
Last updated on MARCH 12, 2025
Applies to:
Oracle Applications DBA - Version 12.2.6 and laterInformation in this document applies to any platform.
Goal
Scenario 1
-------------
E-Business was upgraded to 12.2 and some temporary backup tables which had been used in the prior EBS releases were enabled for Online Patching with an editioning view MV# and an APPS synonym
The temporary backup tables were never integrated as part of a custom spliced application and contain obsolete backup data which will never been used anymore.
Scenario 2
-----------
On 12.2.X, CST spliced a custom application XXCST with a custom database account XXCST and created a custom table XXCST.XXCST_HR_EMPLOYEES
Following Note 1577661.1, Section 1.4.3.1, the custom table was prepped for Online Patching by running AD_ZD_TABLE.UPGRADE
However the business needs have changed and the table with its data is not needed anymore.
There is also a custom package code accessing the table through the APPS synonym and the editioning view _MV#
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 |