Search Results sy_purg_err




Overview
Explore in AI Chat

Overview

The SY_PURG_ERR table is a Process Manufacturing (GMA) data object within Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It functions as a critical error logging repository for the data purge operations managed by the GMA_PURGE_ENGINE package. In the context of Process Manufacturing, periodic data purges are essential for maintaining system performance and managing database growth by archiving or removing obsolete transactional and master data. This table captures detailed diagnostic output generated by the purge engine during its execution, providing administrators with a persistent audit trail of any warnings, errors, or informational messages encountered. Its role is to facilitate troubleshooting, ensure the integrity of purge processes, and support post-purge validation.

Key Information Stored

The table's structure is designed to catalog error messages sequentially for each purge session. Its primary columns, as indicated by the primary and foreign key metadata, are fundamental to this purpose. The PURGE_ID column serves as a foreign key linking each error record to a specific purge session or master control record in the related SY_PURG_MST table. The LINE_NO column provides sequential ordering for multiple messages generated within a single purge session, ensuring the output is stored and can be retrieved in its original sequence. While the specific content columns are not detailed in the provided excerpt, the table's description confirms it stores "database output," which typically includes columns for an error message text, a timestamp, the database object or program unit involved, and potentially a severity code. The composite primary key (PURGE_ID, LINE_NO) guarantees uniqueness of each logged message.

Common Use Cases and Queries

The primary use case is the investigation of failed or problematic data purge runs in the Process Manufacturing module. System administrators query this table to diagnose why a purge job did not complete successfully or to review warnings generated during a successful run. A common reporting pattern involves joining to the master purge table to get contextual session information. A typical diagnostic query would be:

SELECT err.line_no, err.message_text, err.creation_date, mst.purge_name
FROM gma.sy_purg_err err,
gma.sy_purg_mst mst
WHERE err.purge_id = mst.purge_id
AND mst.purge_id = :p_purge_id
ORDER BY err.line_no;

This table is also crucial for generating purge audit reports, validating that purge cycles have completed without critical errors, and providing evidence for compliance related to data lifecycle management.

Related Objects

  • SY_PURG_MST: This is the primary related table, as documented by the foreign key relationship. The SY_PURG_ERR.PURGE_ID column references the SY_PURG_MST table. This relationship ties every error log entry to a master purge control record, which contains high-level information about the purge request, such as parameters, status, and request date.
  • GMA_PURGE_ENGINE Package: As explicitly stated in the description, this is the sole programmatic source of data for the SY_PURG_ERR table. All records are inserted by procedures within this package during its execution.