Results for “user_comment”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_OAM_GCS_JOBS is a table owned by the APPLSYS schema within the FND — Application Object Library product of Oracle E-Business Suite. As documented in the ETRM repository for release 12.2.2, its purpose is to persist job details generated by the Oracle Applications Manager (OAM) Generic Collection Service (GCS) framework. In practical terms, the table records the lifecycle of background collection jobs — the scripts that were dispatched, the nodes on which they executed, their runtime parameters, and their resulting phase and status. Because these jobs frequently run Perl-based collection scripts across multiple application tier nodes, the table serves as the central execution log and audit trail for OAM diagnostic and monitoring activities.

From a Data Vault modeling perspective, the heuristic mined from the foreign-key structure classifies this object as standalone. This classification is offered as a modeling suggestion rather than an enforced design; it indicates that the table is best treated as a self-contained record of job activity rather than a classic hub or link in a normalized enterprise model. Its relationships to FND_LOGINS and FND_SECURITY_GROUPS are informational references — the invoking session and the security grouping under which the job ran — rather than strict dependency chains.

Key Information Stored

The table contains 26 documented columns. The most consequential are summarized below.

• JOB_ID — the surrogate primary key uniquely identifying each collection job instance.
• PERL_SCRIPT_NAME — the name of the Perl script dispatched for the job, identifying which collector executed.
• NODE_NAME — the application tier host on which the job ran, essential for multi-node topologies.
• PHASE and STATUS — the current execution phase and completion status, the primary monitorable attributes.
• START_TIME and END_TIME — the wall-clock boundaries used for duration and performance analysis.
• PARAMETERS, OPTIONS, and TOKENS — the argument payload, runtime switches, and substitution tokens passed to the script.
• LOG_FILE and OUT_FILE — filesystem references to the diagnostic log and result output produced by the job.
• REQUESTED_BY, LOGIN_ID, RESPONSIBILITY_ID, and RESP_APPLICATION_ID — the initiating user and the responsibility context (with its application) under which the request was submitted. LOGIN_ID carries a foreign key to FND_LOGINS.
• SECURITY_GROUP_ID — the security group governing visibility, referencing FND_SECURITY_GROUPS.
• GROUP_ID and USER_COMMENT — grouping and free-text annotation for the job.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — the standard EBS audit columns.
• NLS_LANGUAGE and NLS_TERRITORY — localization settings in force at execution.

The only documented unique index, SYS_IL0000319289C00008$$, is an internal LOB index rather than a business-key constraint. Consequently JOB_ID remains the sole documented surrogate key, and no alternate business key is formally declared in the ETRM metadata.

Common Use Cases and Queries

DBAs and support engineers query this table to diagnose failed or long-running OAM collection jobs. A typical pattern retrieves jobs still in progress:

SELECT job_id, node_name, perl_script_name, phase, status, start_time
  FROM applsys.fnd_oam_gcs_jobs
 WHERE status NOT IN ('COMPLETE','FAILED')
 ORDER BY start_time;

Duration trending across nodes is another common report, computing (END_TIME − START_TIME) grouped by NODE_NAME. Historical auditing joins the audit columns and LOGIN_ID back to session data. Because the table can accumulate substantial volume, purging strategies frequently target rows with END_TIME older than a retention threshold.

Related Objects

• FND_LOGINS — joined on LOGIN_ID to resolve the originating database session user.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID to resolve the security grouping in force.
• FND_RESPONSIBILITY — resolves RESPONSIBILITY_ID and RESP_APPLICATION_ID to the responsibility context.
• FND_USER — resolves REQUESTED_BY and CREATED_BY to the requesting user account.
• OAM Generic Collection Service runtime and viewer components that read and render job status from this table.