Bug 20114306  Objects left in recyclebin after upgrade to 12.1.0.2 or with fix for bug 16851194 present - superseded

 This note gives a brief overview of bug 20114306. 
 The content was last updated on: 24-AUG-2017
 Click here for details of each of the sections below.

Affects:

Product (Component) Oracle Server (Rdbms)
Range of versions believed to be affected Versions BELOW 12.2
Versions confirmed as being affected

  • 12.1.0.2 (Server Patch Set)
Platforms affected Generic (all / most platforms affected)

 It is believed to be a  regression in  default behaviour thus:
   Regression introduced in 12.1.0.1

  Note that this fix can cause / expose the problem described in Bug:21498770 

  Note that this fix has been superseded by the fix in Bug:21498770 

  Note that this fix has been superseded by the fix in Bug:23100700 

Fixed:

This fix has been  superseded - please see the fixed version information for  Bug:21498770 /  Bug:23100700 . The box below only shows versions where the code change/s for 20114306 are first included - those versions may not contain the later improved fix.

The fix for 20114306 is first included in

  • 12.2.0.1 (Base Release)

  • 12.1.0.2.160419 (Apr 2016) Bundle Patch for Windows Platforms

Symptoms:

Related To:

  • Storage Space Usage Affected

  • Recycle Bin

Description

Unnecessary recycle bin entries may be present after the fix for bug 16851194 is installed 
or after upgrading to 12.1.0.2, as this fix was included in 12.1.0.2 patchset. 
Rediscovery Notes
  If you see table objects in recycle bin with names like WRI$_RCS* then this is same issue. 
Workaround
 None 
Note:
 This fix supersedes the fix originally made in bug 16851194. This fix is superceded by bug 21498770 and which is further 
 superceded by bug 23100700 fix. 
 
 For interim patches use the bug 23100700 fix instead of this bug to address issues reported by all these bugs.


Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. For questions about this bug please consult Oracle Support.