Search Results ad_bugs




The AD_BUGS table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical repository for tracking bugs, patches, and fixes within the application framework. It serves as a centralized metadata table that stores information about known issues, their resolutions, and associated patch details. This table is part of the Oracle Applications DBA (AD) schema, which manages administrative and technical metadata for the EBS environment.

Structure and Key Columns

The AD_BUGS table contains several important columns that provide detailed information about each bug:
  • BUG_ID: A unique identifier for the bug, often referenced in Oracle Support documents.
  • BUG_NUMBER: The Oracle bug number, typically displayed in Metalink or My Oracle Support (MOS).
  • RELEASE_NAME: Indicates the EBS release (e.g., 12.1.1 or 12.2.2) where the bug was identified or fixed.
  • STATUS: Reflects the current state of the bug (e.g., OPEN, CLOSED, FIXED).
  • PATCH_NAME: The name of the patch that resolves the bug, if applicable.
  • CREATION_DATE: Timestamp when the bug was logged in Oracle's system.
  • LAST_UPDATE_DATE: The most recent modification date for the bug record.
  • DESCRIPTION: A brief summary of the issue, symptoms, or impact.

Purpose and Functionality

The AD_BUGS table plays a pivotal role in EBS administration by:
  • Providing a reference for troubleshooting known issues.
  • Facilitating patch management by linking bugs to their corresponding fixes.
  • Enabling impact analysis during upgrades or migrations by identifying unresolved bugs in the target environment.
  • Serving as a metadata source for Oracle's patching tools like AutoPatch (ADPATCH) and OAM (Oracle Applications Manager).

Integration with Other EBS Components

The table interacts with several EBS subsystems:
  • Patch Tools: AutoPatch consults AD_BUGS to determine if a patch is required or already applied.
  • OAM uses this table to display bug information in the "Applied Patches" section.
  • AD_APPLIED_PATCHES maintains a relationship with AD_BUGS to track which bugs were resolved by which patches.

Maintenance Considerations

For EBS administrators:
  • The table is automatically updated when patches are applied through standard Oracle tools.
  • Manual modifications are strongly discouraged as they may corrupt patch metadata.
  • Regular queries against this table should be part of pre-patch analysis to identify known issues in the environment.

Query Examples

Common diagnostic queries include: 
-- Check for open bugs in current release
SELECT bug_number, description 
FROM ad_bugs 
WHERE status = 'OPEN' 
AND release_name = '12.2.2';

-- Verify if a specific bug is fixed
SELECT patch_name, last_update_date 
FROM ad_bugs 
WHERE bug_number = '12345678';

Version-Specific Notes

Between 12.1.1 and 12.2.2:
  • 12.2.2 introduced additional columns for tracking online patch (OPatch) compatibility.
  • The table structure remained largely consistent, but bug metadata became more detailed in 12.2.x releases.
  • R12.2's online patching architecture changed how some bug fixes are applied, though the AD_BUGS tracking mechanism remained similar.
In summary, the AD_BUGS table is an essential component of Oracle EBS's patching and maintenance infrastructure, providing critical metadata that supports system stability and issue resolution across both 12.1.1 and 12.2.2 environments.