Results for “server_type_node_flag”

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

Overview

AD_APPL_TOPS is a core Applications DBA (AD) metadata table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name, description ("APPL_TOP names"), and column structure confirm that it serves as the master registry of APPL_TOP filesystem locations registered within an EBS instance. Every APPL_TOP — the directory tree containing the product-specific forms, reports, and Java files for a given node — is represented here by a single row, and that row's surrogate identifier becomes the anchor point against which numerous AD utilities, patching operations, snapshots, and session-tracking processes record their filesystem context.

Because AD_APPL_TOPS holds the distinct, non-overlapping set of APPL_TOP identities referenced by so many downstream AD tables, the object exhibits the characteristics of a Data Vault hub. Following the heuristic classification supplied in the metadata, it is modeled most naturally as a hub: the APPL_TOP_ID business key is stable, insert-only, and referenced by a wide constellation of satellite-style detail tables through foreign keys. In EBS 12.2.2 the dual filesystem layout (fs1 and fs2) increases the practical importance of this registry, since each edition maintains its own APPL_TOP row and associated metadata.

Key Information Stored

The table comprises 14 documented columns. The most significant are:

• APPL_TOP_ID — the surrogate primary key, uniquely constrained by AD_APPL_TOPS_PK and the unique index AD_APPL_TOPS_U1. It is the value propagated to every dependent AD table.
• NAME — the APPL_TOP directory name or path label, part of the natural business-key candidate.
• APPLICATIONS_SYSTEM_NAME — the EBS system name (typically the SID) to which the APPL_TOP belongs; part of the same business key with NAME and APPL_TOP_TYPE.
• APPL_TOP_TYPE — distinguishes the APPL_TOP classification (for example, the base versus a patched or dual-filesystem edition); also part of the unique candidate AD_APPL_TOPS_U2 (NAME, APPLICATIONS_SYSTEM_NAME, APPL_TOP_TYPE).
• DESCRIPTION — free-text identification of the APPL_TOP.
• ACTIVE_FLAG — indicates whether the APPL_TOP row is currently enabled for the instance.
• SERVER_TYPE_ADMIN_FLAG, SERVER_TYPE_FORMS_FLAG, SERVER_TYPE_NODE_FLAG, SERVER_TYPE_WEB_FLAG — four flags that declare which server roles this APPL_TOP serves (administration, Forms, node, or Web), governing how AutoConfig and patching treat the directory tree.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard EBS audit columns that record row provenance and change history.

The distinction between the surrogate key (APPL_TOP_ID) and the two unique business-key candidates is important for data migration and reconciliation work, since NAME may not be globally unique but the three-column combination is.

Common Use Cases and Queries

DBAs query AD_APPL_TOPS to inventory the APPL_TOPs registered in an instance, to confirm which server roles are configured on each node, and to correlate patching activity with a specific filesystem.

SELECT appl_top_id, name, applications_system_name,
       appl_top_type, active_flag
FROM   applsys.ad_appl_tops
WHERE  active_flag = 'Y';

SELECT appl_top_id, name,
       server_type_admin_flag, server_type_forms_flag,
       server_type_web_flag, server_type_node_flag
FROM   applsys.ad_appl_tops;

A frequent reporting pattern joins AD_APPL_TOPS to AD_PATCH_RUNS to attribute each patch run to an APPL_TOP:

SELECT a.name, p.patch_name, p.start_date, p.end_date
FROM   applsys.ad_appl_tops a,
       applsys.ad_patch_runs p
WHERE  a.appl_top_id = p.appl_top_id
ORDER  BY p.start_date DESC;

Snapshot reconciliation uses AD_SNAPSHOTS and AD_SNAPSHOT_FILES with the same APPL_TOP_ID join key, and concurrent-processing diagnostics join AD_SESSIONS and AD_WORKING_RES_LOCKS.

Related Objects

AD_APPL_TOPS functions as a reference (parent) table for at least eleven documented foreign keys. The most operationally significant are:

• AD_PATCH_RUNS (AD_PATCH_RUNS.APPL_TOP_ID) — patch execution history per APPL_TOP.
• AD_SNAPSHOTS (AD_SNAPSHOTS.APPL_TOP_ID) — filesystem snapshot definitions.
• AD_SNAPSHOT_FILES / AD_SNAPSHOT_FILES_TEMP — individual files captured during snapshot operations.
• AD_SESSIONS — AD session tracking, recording the APPL_TOP in use.
• AD_WORKING_RES_LOCKS / AD_PLANNED_RES_LOCKS — resource lock management for AD utilities.
• AD_PA_ANAL_BUG_DEPS / AD_PA_ANALYSIS_RUN_BUGS — Patch Analyzer bug-dependency and analysis-run records.
• AD_UMS_ENGINE_RESULTS and AD_CHECK_FILE_TEMP — Unified Master Services engine output and file-check staging data.

All dependencies join on APPL_TOP_ID, confirming the hub role of this table and making it a reliable anchor for cross-module DBA reporting.