Skip to content

Latest commit

 

History

History

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

README.md

layout default
title DBA Editioned Object Summary | Oracle EBS SQL Report
description Summary of editioned objects per edition from ADZDSHOWOBJS.sql There is a good blog: https://www.pythian.com/blog/technical-track/adop-edition-cleanup
keywords Oracle EBS, Oracle E-Business Suite, SQL report, Blitz Report, Enginatics, DBA, Editioned, Object, Summary, obj$, user$, dba_users
permalink /DBA%20Editioned%20Object%20Summary/

DBA Editioned Object Summary – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.

Overview

Summary of editioned objects per edition from ADZDSHOWOBJS.sql There is a good blog: https://www.pythian.com/blog/technical-track/adop-edition-cleanup

Report Parameters

Oracle EBS Tables Used

obj$, user$, dba_users

Report Categories

Enginatics

Related Reports

DBA SGA Blocking Session Summary, DBA AWR Blocking Session Summary, DBA AWR Active Session History, DBA SGA Active Session History, DIS Workbooks, Folders, Items and LOVs, DIS Folders, Business Areas, Items and LOVs, DBA Blocking Sessions, FND Applications, DBA AWR SQL Performance Summary

Running This SQL Without Blitz Report

Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.

Download & Import Options

Resource Link
Excel Example Output DBA Editioned Object Summary 22-Dec-2025 083843.xlsx
Blitz Report™ XML Import DBA_Editioned_Object_Summary.xml
Full SQL on Enginatics www.enginatics.com/reports/dba-editioned-object-summary/

Executive Summary

The DBA Editioned Object Summary report is essential for managing Oracle E-Business Suite 12.2+ environments, which use Edition-Based Redefinition (EBR) for online patching. It provides a summary of how many objects exist in each "Edition". This is critical for monitoring the cleanup process (adop phase=cleanup) and managing the growth of the database.

Business Challenge

  • Storage Growth: "Why is the database growing so fast? Are we keeping too many old patch editions?"
  • Patching Health: "Did the cleanup phase of the last patch cycle actually remove the obsolete objects?"
  • Performance: "Are we suffering from dictionary performance issues due to having 500 old editions?"

Solution

This report summarizes the count of editioned objects (Views, PL/SQL, Synonyms) per edition.

Key Features:

  • Edition Name: The name of the patch edition (e.g., V_20230101_1200).
  • Object Count: Number of actual objects vs. "stub" objects.
  • Active Status: Identifies the current Run and Patch editions.

Architecture

The report queries OBJ$, USER$, and DBA_USERS.

Key Tables:

  • OBJ$: The core object table (includes the EDITION_NAME column).
  • DBA_OBJECTS_AE: The view showing all editioned objects.

Impact

  • Space Reclamation: Identifies when it's safe (and necessary) to run a full cleanup to reclaim space.
  • System Hygiene: Ensures the database doesn't become cluttered with thousands of obsolete object versions.
  • Patching Success: Verifies that the Online Patching cycle is completing all its housekeeping tasks.

Useful Links

© 2026 Enginatics