Search Results table_maxsize

Overview

APPS.DT_CHECKINT is a DateTrack validation utility package shipped with Oracle EBS Human Resources (Oracle HRMS). Its purpose is to verify the structural integrity of tables that participate in the DateTrack feature — the temporal data model that stores effective-dated rows (effective_start_date / effective_end_date) so that HR records retain full history. The package body is largely a diagnostic and consistency-checking engine: it inspects database catalog views to confirm, for a supplied table, that the expected DateTrack columns, primary/unique constraints, and supporting indexes exist and are correctly configured. The header comment identifies the source file as dtchkint.pkb (version 115.1), and the presence of DBMS_OUTPUT and DBMS_PIPE trace handling indicates that the package is intended to emit diagnostic messages for the DBA or developer performing the validation.

The public interface is deliberately small — three documented entry points — and the package is referenced by no other database package, which classifies it as a standalone diagnostic tool rather than a runtime dependency of the HRMS application logic.

Key Procedures and Functions

• SET_OPTIONS — Configures the operational behaviour of the package before a validation run. Based on the package-level globals (g_output, g_schema), this procedure allows the caller to select the output/trace destination (for example DBMS_OUTPUT versus DBMS_PIPE) and the schema whose objects should be examined.
• CHECK_TABLE — The focal routine implied by the user's search term "check_table". It validates a single named table as a DateTrack-enabled structure. The body declares a table_info record holding the table name, schema name, and a has_who_cols flag, and caches results in the declarative tab_* collection types. This is the procedure to invoke when investigating a specific table's DateTrack compliance.
• CHECK_ALL_TABLES — Extends CHECK_TABLE by iterating over the full set of candidate DateTrack tables and reporting their status, using the same caching and output mechanisms. It is suited to a one-off audit of an entire HRMS schema.

The body additionally contains a private routine, initialize_output, which enables tracing via hr_utility.trace_on when the output mode is DBMS_PIPE. The constant TABLE_MAXSIZE (20) caps the number of DateTrack changes tracked per identifier.

Tables Accessed

The package reads Oracle data dictionary views exclusively; it does not modify application data:

• ALL_TAB_COLUMNS — used to verify that a table contains the DateTrack columns (id, effective_start_date, effective_end_date, creation_date, last_update_date).
• ALL_CONSTRAINTS — used to confirm that the expected primary key or unique constraints are present on the table.
• ALL_IND_COLUMNS — used to confirm that the indexes required to support the constraint and DateTrack lookups exist and reference the correct columns.
• DBMS_OUTPUT / DBMS_SQL — the output and dynamic SQL engine packages through which results are reported and dynamic queries are constructed.

Usage Notes

DT_CHECKINT is not called by other packaged code and does not run automatically, so it must be invoked explicitly. Typical invocation scenarios include: a DBA or consultant running SET_OPTIONS followed by CHECK_TABLE from SQL*Plus or SQL Developer to diagnose a DateTrack table after a patch or upgrade; a custom concurrent program (or anonymous PL/SQL block) that loops over CHECK_ALL_TABLES to produce an audit report during implementation or migration testing; and custom code that calls CHECK_TABLE defensively before registering a new effective-dated table in the HRMS schema. Because output is routed through DBMS_OUTPUT or DBMS_PIPE, DBMS_OUTPUT must be enabled in the calling session to view results. The package is valid across both EBS 12.1.1 and 12.2.2, as both releases share the same HRMS DateTrack infrastructure.