Search Results validate_continued_execution

Overview

FND_OAM_DSCRAM_BUNDLES_PKG is an Oracle E-Business Suite packages belonging to the Application Object Library (FND) schema, classified under the Oracle Applications Manager (OAM) subsystem. Its name derives from "DSCRAM" — the Diagnostic Scrubbing and Resource Allocation Manager framework used to coordinate parallel execution of diagnostic, maintenance, and data-collection tasks within EBS. The package provides the public interface through which a session obtains, validates, and consumes a "bundle" assignment: a logical grouping of work units dispatched across a controlled number of concurrent workers on one or more application tier nodes.

The package exposes a small, well-defined API surface (eight documented routines) that separates state initialization from state access. The initialization routines, EXECUTE_BUNDLE and EXECUTE_HOST_BUNDLES, establish the session-scoped bundle and worker context; the remaining accessor and validation routines allow callers to interrogate and confirm that context. The single-row control table FND_OAM_DSCRAM_BUNDLES is the persistent anchor for bundle definitions and assignments.

Key Procedures and Functions

• GET_BUNDLE_ID — Accessor returning the numerical identifier of the bundle to which the current session is assigned. It requires that EXECUTE_BUNDLE was previously invoked in the session, otherwise NO_DATA_FOUND is raised.
• GET_WORKER_ID — Accessor returning the numerical identifier of the worker assigned to the bundle within the current session; subject to the same initialization invariant.
• GET_WORKERS_ALLOWED — Accessor returning the maximum number of concurrent workers permitted for the bundle, governing the degree of parallelism enforced by the framework.
• GET_BATCH_SIZE — Accessor returning the default batch size, expressed as a number of rows, for an AD API unit of work.
• GET_MIN_PARALLEL_UNIT_WEIGHT — Accessor returning the minimum parallel unit weight threshold used by DSCRAM when deciding whether a unit of work is large enough to justify parallel dispatch.
• VALIDATE_CONTINUED_EXECUTION — Validation routine that confirms the current session is still entitled to continue processing its assigned bundle and worker. This is the routine most commonly referenced by callers that must decide whether to loop, terminate, or release their worker slot.
• EXECUTE_BUNDLE — The principal entry point that initializes session state for a single bundle, populating the values subsequently returned by the accessor functions.
• EXECUTE_HOST_BUNDLES — Entry point that initializes and drives the execution of all bundles assigned to the current host, coordinating multiple bundle invocations from a single call site.

Tables Accessed

• FND_OAM_DSCRAM_BUNDLES — The core control table holding bundle definitions, worker assignments, concurrency limits, and batch sizing. All state published by the accessor functions is ultimately derived from this table.
• V$INSTANCE — Consulted to identify the instance (host and instance name) on which the session is running, supporting host-scoped bundle execution through EXECUTE_HOST_BUNDLES.
• DBMS_SQL — Used for dynamic SQL construction and execution, allowing the package to evaluate bundle criteria and process units generically.
• PLITBLM — A PL/SQL internal table library utility used for in-memory list and collection handling during bundle processing.

Usage Notes

FND_OAM_DSCRAM_BUNDLES_PKG is not an end-user-facing API. It is invoked programmatically by the diagnostic scrubbing framework and by a small set of dependent packages — ETRM records five packages referencing it. Typical invocation patterns are:

• From DSCRAM worker and dispatcher concurrent programs that call EXECUTE_BUNDLE or EXECUTE_HOST_BUNDLES to claim work, then use GET_BUNDLE_ID, GET_WORKER_ID, and GET_WORKERS_ALLOWED to drive their processing loop.
• Inside custom or Oracle-delivered code that repeatedly calls VALIDATE_CONTINUED_EXECUTION between batches to determine whether the session's bundle assignment remains valid — for example, after an administrator pauses or cancels a bundle.
• Within host-level coordinating logic that enumerates and starts all bundles associated with the current node via EXECUTE_HOST_BUNDLES.

Because session state is established only by a prior call to EXECUTE_BUNDLE, callers must not assume the accessor functions are usable at arbitrary points in a session; the documented NO_DATA_FOUND exception applies when the initialization invariant is violated. Given the 2005 header revision date and the package's noship designation, this is legacy infrastructure that remains stable across 12.1.1 and 12.2.2, and integrators should treat it as internal framework plumbing rather than a supported public extension point.