Search Results oki_dbi_reset_pub

Overview

OKI_DBI_RESET_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the Oracle Knowledgebase Installer (OKI) product family, the component responsible for deploying and maintaining the Oracle Knowledge Management and interaction-center data structures used by TeleService, iSupport, and related customer-support modules. The DBI segment of the name identifies it as a database-initialization utility, and the package is classified as a public API, meaning it is intended for external invocation rather than internal use only.

The package declares AUTHID CURRENT_USER, so its statements execute with the privileges of the calling session rather than the definer. Combined with the $Header stamp (OKIPIRSS.pls 115.3, dated 2002), this confirms the package is a long-standing component of the OKI schema whose behavior has remained stable across the 11i, 12.1.1, and 12.2.2 releases.

Key Procedures and Functions

• RESET_BASE_TABLES — The single documented procedure. It returns the standard concurrent-program error buffer and completion code (errbuf and retcode), which indicates that it is designed to run as an executable called by the Concurrent Manager. Its purpose is to reset the base tables that support the OKI / DBI installer and knowledgebase setup, returning them to a known baseline state so that installation, upgrade, or reconfiguration can proceed from a clean point. No other procedures or functions are exposed by this package.

Tables Accessed

The ETRM metadata records no direct table references via APPS synonyms for this package. In practice, the procedure performs its work against the installer and setup tables within the OKI schema, clearing or re-initializing rows that track installation state, configuration snapshots, and staging data. Because the metadata does not enumerate these objects, administrators should treat the exact set of affected tables as release-specific and confirm it against the package body in the target environment before execution.

Usage Notes

Because RESET_BASE_TABLES follows the concurrent-program calling convention, it is normally invoked through a Concurrent Manager executable registered against the package rather than from a form or ad hoc SQL session. Typical usage occurs during OKI installer or knowledgebase reconfiguration, when a prior run has left base tables in an inconsistent state and a controlled reset is required before retrying. It may also be called from custom installation scripts or wrapper programs that supply the two OUT parameters.

The package is referenced by no other documented packages, so it sits at the outer edge of the dependency chain and is not called internally by other application code. This makes its invocation a deliberate administrative action. Given that the procedure resets data rather than merely reading it, it should be run only during planned maintenance windows, with a validated backup of the affected schema and a clear understanding of downstream impacts on knowledgebase and interaction-center configuration. Oracle does not sanction casual execution of this API, and the lack of documented table references reinforces the need to review the package body and test in a non-production environment before deployment.