Search Results dt_checkint




Overview
Explore in AI Chat

Overview

APPS.DT_CHECKINT is an Oracle E-Business Suite database package that provides diagnostic and integrity verification utilities for DateTrack-enabled tables. DateTrack is the Oracle HRMS (and related Applications) mechanism that maintains effective-dated history on rows, using the effective_start_date and effective_end_date columns to record the validity period of each logical record. The DT_CHECKINT package exists to validate that these tables conform to the fundamental DateTrack integrity rules — for example, that effective date ranges do not overlap, are contiguous, and are consistent with the primary key definition. It is an internal, administrative helper rather than a functional business API, and is classified in the ETRM repository with an API classification of OTHER. The package is defined with AUTHID CURRENT_USER, meaning that its unqualified references to data dictionary views are resolved against the privileges and schema of the calling user, not the package owner.

Key Procedures and Functions

The package exposes three documented procedures:

  • SET_OPTIONS — The procedure that the user searched for. Its stated purpose is to allow default preferences to be overwritten. It accepts a schema name identifying the schema that owns the tables to be checked, and an output destination that determines how diagnostic results are delivered — the documentation indicates DBMS_OUTPUT as the default, with DBMS_PIPE as the alternative. This procedure therefore acts as a session-level configuration entry point that must be executed before running the checking routines.
  • CHECK_TABLE — Applies a number of DateTrack integrity rules to a single named table. Where an error is detected, the details of the offending row are written to the configured output destination. The procedure is documented to accept a maximum-error threshold, but the source notes explicitly record a known defect: the routine does not stop early, so the p_max_errors parameter currently has no effect. It raises an exception if the specified table cannot be found. It is designed for DateTrack tables whose primary key comprises an ID column plus effective_start_date and effective_end_date, and which carry the standard WHO columns; tables that do not conform are handled through the check_all_tables routine.
  • CHECK_ALL_TABLES — Iterates the set of DateTracked tables and applies the basic DateTrack rules across all of them, providing a schema-wide verification run.

Tables Accessed

Rather than business data tables, the package queries the data dictionary. The documented references are ALL_CONSTRAINTS, ALL_IND_COLUMNS and ALL_TAB_COLUMNS, which are used to identify candidate tables, confirm primary key and index column composition, and inspect column definitions such as the effective date and WHO columns. DBMS_OUTPUT and DBMS_SQL are also referenced: the former for reporting results to the calling session, the latter for the dynamic SQL required to inspect and iterate arbitrary DateTrack tables at runtime.

Usage Notes

DT_CHECKINT is a support and diagnostic utility, not a transactional API. It is not referenced by any other documented package in the ETRM repository, confirming that it is invoked directly rather than called from application code. Typical use is by a DBA or technical consultant working in a development or test environment, invoked from SQL*Plus or a similar tool, for example by first calling set_options to select the target schema and output destination and then calling check_table or check_all_tables. It should not be scheduled as a routine concurrent program in a production instance, and any anomalies it reports should be investigated before corrective action is taken, since the utility produces diagnostics only and does not repair data.