Search Results fnd_stats

Overview

The concurrent program FNDPGHST — presented to users as Purge FND_STATS History Records — is owned by the FND - Application Object Library module within Oracle E-Business Suite. Its function is administrative and maintenance-oriented: it removes obsolete history rows that the FND_STATS utility accumulates as it collects and stores optimizer statistics for Oracle EBS database schemas. The program is documented in the ETRM as enabled (Enabled: Yes), meaning it may be scheduled and submitted without further configuration in both the 12.1.1 and 12.2.2 release lines.

FND_STATS is the framework Oracle EBS uses to gather statistics against database objects underlying the application tables. Each gathering operation stores a record describing the object analyzed, the date and time of collection, the operation performed, and related informational data. Over time, these FND_STATS history records grow, consuming space in the application schema and lengthening queries that reference the history. FNDPGHST exists to prune that historical data, keeping the statistics repository at a manageable size while preserving the current statistics themselves. Because it is an FND-owned utility rather than a functional business program, it is typically invoked by database administrators or system administrators during routine housekeeping rather than by end users.

Execution Details

The ETRM metadata records the following execution attributes for FNDPGHST:

• User-facing name: Purge FND_STATS History Records
• Product: FND - Application Object Library
• Execution Method: PL/SQL Stored Procedure
• Argument Method: Standard
• Executable: FNDPGHST
• Execution Filename: FND_STATS.PURGE_STAT_HISTORY

The execution method is significant. Because the program runs a PL/SQL stored procedure rather than an external executable, Oracle EBS invokes FND_STATS.PURGE_STAT_HISTORY directly inside the database session created for the concurrent request. No operating-system-level binary, shell script, or Java class is involved, and the request completes entirely within the database tier. The Standard argument method indicates that the program's parameters are normal concurrent program arguments passed through the Standard Request Submission (SRS) framework.

How to Run

Administrators submit FNDPGHST through the standard concurrent manager infrastructure. In the EBS navigation, this is reached via System Administrator > Requests > Run, where the request name Purge FND_STATS History Records can be selected and submitted. The request can also be scheduled as a recurring concurrent request so that history is purged on a fixed cadence without manual intervention.

The ETRM documents the argument method as Standard; specific parameter prompts are defined by the underlying procedure and are generally used to scope the purge — for example, by specifying a cutoff date or an object/schema restriction so that only records older than the intended retention window are deleted. Because the program deletes rows from the FND_STATS history tables, it should be run deliberately, ideally during a period of low activity, and the parameter values should be reviewed before submission. Users should confirm the program is assigned to a concurrent manager in their environment, since disabled or unassigned programs will never be picked up by the manager.

Related Objects

FNDPGHST is tightly coupled to the FND_STATS statistics-gathering facility. Commonly associated objects include the FND_STATS package itself, its history storage tables, and the companion statistics-gathering programs that populate those tables. Related concurrent programs typically include the FND_STATS-driven statistics collection requests used by the Gather Statistics and Gather Schema Statistics utilities, which write the very history rows that FNDPGHST later removes. Database-level DBMS_STATS routines are the underlying engine that most FND_STATS operations wrap.

Because the program manipulates history rather than the live statistics dictionary, no interface tables, open interfaces, or reporting APIs are required to use it. Its output is transactional: rows are deleted from the FND_STATS history, and the concurrent request log records the completion of the purge.