Results for “jtf_mon_dstat”

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

Overview

The view JTF_MON_DSTAT belongs to the JTF – CRM Foundation product family within Oracle E-Business Suite. It exposes monitoring and diagnostic data captured by the CRM Foundation monitoring subsystem, which is used to track runtime statistics and status attributes generated by CRM and Telephony components. The view presents a denormalized, readable projection of monitoring data values by joining stored data attributes to their corresponding lookup definitions. Because it surfaces internal monitoring metrics rather than transactional CRM data, it is primarily relevant to diagnostics, performance analysis, and internal health reporting rather than mainstream CRM functional reporting.

The ETRM metadata indicates that the view is documented but not implemented in every environment. In the excerpt provided, the "Not implemented in this database" note and the absence of a documented owner indicate that JTF_MON_DSTAT is present only in installations where the underlying CRM Foundation monitoring schema objects have been deployed. In Oracle EBS 12.1.1 and 12.2.2 alike, the availability of the view therefore depends on whether the JTF monitoring components are installed and populated.

Underlying Base Objects

The view is defined over two base tables, both belonging to the JTF monitoring dictionary:

• JTF_MON_DATA_ATTR — stores the raw monitored attribute values, keyed by DATA_ID and an ACCESSKEY, with a primary value in DATA_VAL and an optional secondary value in DATA_VAL_OPT.
• JTF_MON_DATA_LOOKUP — provides the naming metadata for each monitored item, including the NAME_SPACE, VAR_NAME, and the shared DATA_ID key.

The view joins these tables on DATA_ID, correlating each stored data value with its namespace and variable name. The documented ETRM metadata lists no referenced base objects, but the embedded view text establishes the join relationship as DAT.DATA_ID = DATNAME.DATA_ID. This is an inner join, so only attribute rows with a matching lookup definition are returned.

Key Columns

The view text exposes the following projected columns:

• ACCESSKEY — the access key from JTF_MON_DATA_ATTR, identifying the monitored component or context.
• NAME_SPACE — the logical namespace of the monitored variable, taken from the lookup table, used to group related metrics.
• VAR_NAME — the variable name of the monitored item, providing the human-readable identifier.
• DATA_VAL — the primary stored value for the attribute.
• DATA_VAL_OPT — the optional secondary or alternate value for the attribute.

The column listing in the ETRM metadata also references ACCKEY, NAMESPACE, VARNAME, and NUM_VAL; these appear to be the underlying or alternate naming conventions for the same projected fields, with NUM_VAL representing the numeric interpretation of a monitored value.

Common Use Cases and Queries

Because this view returns diagnostic monitoring data, it is most useful for support engineers constructing ad hoc queries to inspect CRM Foundation runtime metrics. A typical query filters by namespace and variable:

SELECT ACCESSKEY, NAME_SPACE, VAR_NAME, DATA_VAL, DATA_VAL_OPT
FROM JTF_MON_DSTAT
WHERE NAME_SPACE = :namespace
AND VAR_NAME = :varname;

Analysts can group results by namespace to enumerate all monitored variables, or join the view back to JTF_MON_DATA_ATTR on ACCESSKEY to correlate values with additional attribute detail. Before relying on the view, it is advisable to confirm its existence in the target environment, since the ETRM record explicitly notes it may not be implemented in a given database. Where the view is absent, the same information can be obtained directly by joining the two base tables.