Search Results g_log_dir

Overview

APPS.DOM_DOC_TEXT_PVT is a private PL/SQL package body in the Oracle E-Business Suite Document Management (DOM) module. It supports the generation and maintenance of Oracle Text indexes and text-based document content maintained within the DOM schema. The package encapsulates the logic required to build full-text search structures against document text using the CTXSYS Oracle Text facilities. It is classified as a PVT (private) package in ETRM, meaning its procedures are intended for internal consumption by other packages within the DOM product rather than for direct invocation by end users or external modules.

The package header (as seen in the source listing) declares a body named DOM_DOC_TEXT_PVT, with a package-level constant G_PKG_NAME set to 'DOM_TEXT_PVT'. It defines several private globals that track the CTXSYS schema name, the product and index owner schemas, and index/preference owner names. These globals configure the target schemas used when building Oracle Text indexes against document text columns.

Key Procedures and Functions

• SET_LOG_MODE — Establishes the logging behavior for the package. The body declares flags such as g_Log_Mode, g_Log_Sqlplus_Flag, g_Log_File_Flag, and g_Log_Dbdrv_Flag that govern whether diagnostics are written to the concurrent program log file, SQL*Plus output, or an external log destination. This procedure sets those modes.
• LOG_LINE — Writes a formatted diagnostic line to the enabled log destinations. It chunks the input buffer into 240-byte segments for FND_FILE logging, honoring the g_Log_File_Flag flag and related output flags. This is the internal logging utility used throughout the package.
• BUILD_DOC_TEXT_INDEX — The core procedure responsible for creating or rebuilding the Oracle Text index over document text content. It relies on the private global schema variables (g_Index_Owner, g_Pref_Owner, g_Ctx_Schema) to target the correct schema objects.
• GET_MSG_TEXT — Retrieves message text used for status reporting or error conditions, drawing on g_Msg_Text and related message handling logic within the package.

ETRM documents five procedures/functions in total; the excerpt identifies the four above by name. Parameter lists are not asserted here to avoid inventing undocumented signatures.

Tables Accessed

The only table referenced through APPS synonyms is V$PARAMETER. The package declares g_Log_Dir and g_Dump_Dir as v$parameter.value%TYPE, indicating it reads database initialization parameters — most notably the log directory and dump directory settings — to resolve file paths for log output. This is consistent with the g_Log_File and g_Out_File filename constants declared for SQL*Plus-based logging.

Usage Notes

DOM_DOC_TEXT_PVT is referenced by one other package, reflecting its private/utility role. The "g_log_dir" search term maps directly to the g_Log_Dir global, which is anchored to V$PARAMETER. This field is read when the package resolves the directory into which log files such as dom_doc_text_tl_srs.log are written during concurrent processing. The package is typically invoked indirectly — through the DOM functionality that constructs document text indexes — rather than through a form or direct API call. Custom code should not rely on these private routines; the supported entry points are the public DOM APIs, and this package is subject to change between EBS 12.1.1 and 12.2.2.