Search Results dbms_lob_am_private

Overview

DBMS_LOB_AM_PRIVATE is an Oracle-supplied PL/SQL package residing in the SYS schema. It forms part of the internal infrastructure supporting the DBMS_LOB hierarchical large object (LOB) architecture, specifically the abstract access method (AM) layer. In Oracle EBS 12.1.1 and 12.2.2, this package is not an application-facing API and carries no EBS business logic. Instead, it operates beneath the public DBMS_LOB interface, providing the private callbacks and dispatch routines required to route LOB operations to the correct access method — for example, the basic file, secure file, or other internal LOB storage implementations introduced across Oracle database releases.

The ETRM metadata classifies DBMS_LOB_AM_PRIVATE as API classification OTHER with zero documented procedures or functions, and records no references from other EBS packages. Its status is VALID, confirming it compiles and is present in the database dictionary. Its dependency footprint is intentionally minimal: it references only STANDARD, and it is referenced by the DBMS_LOB package body itself. This tight coupling confirms its role as a private implementation detail rather than a standalone utility.

Key Procedures and Functions

The ETRM documentation for this object lists no documented procedures or functions. Accordingly, no public entry points are exposed for developer or EBS application use. The package body exists to support internal DBMS_LOB processing, and its routines are private by design and subject to change without notice across database patch levels. Because no callable signatures are published in the ETRM metadata, none are reproduced here; any assumption about parameter lists would be speculative.

Tables Accessed

The documented metadata records no tables referenced through APPS synonyms, and no base tables are enumerated in the dependency listing. This is expected: the package operates on LOB locators and access method descriptors in memory rather than issuing direct SQL against application tables. In an EBS context, the underlying LOB data typically resides in tables such as FND_LOBS or other tables with LOB columns, but those accesses are performed by the public DBMS_LOB layer and by application code, not by DBMS_LOB_AM_PRIVATE directly.

Usage Notes

DBMS_LOB_AM_PRIVATE is not invoked directly from Oracle Forms, concurrent programs, or custom EBS code. It is exercised implicitly whenever the DBMS_LOB package performs a read, write, trim, copy, or getLength operation against a LOB locator. Because the DBMS_LOB package is heavily used by EBS components — including the attachments and document management functionality that stores files in LOB columns — this package executes indirectly and frequently in a running E-Business Suite instance.

From an administration standpoint, DBMS_LOB_AM_PRIVATE should be treated as part of the Oracle database kernel-supplied infrastructure. It must not be modified, wrapped, or recompiled manually, and its presence in a dependency tree or invalidation report is generally benign. If the object is reported as INVALID, the correct remediation is to recompile the dependent DBMS_LOB package, after which the private access method package should be validated again. When diagnosing EBS attachment or LOB-related failures, administrators should focus on the public DBMS_LOB interface and the underlying storage configuration rather than on this private object, since it is not directly customizable or addressable through supported EBS APIs.

PACKAGE: SYS.DBMS_LOB_AM_PRIVATE 12.2.2
owner:SYS, object_type:PACKAGE, object_name:DBMS_LOB_AM_PRIVATE, status:VALID,
PACKAGE: SYS.DBMS_LOB_AM_PRIVATE 12.1.1
owner:SYS, object_type:PACKAGE, object_name:DBMS_LOB_AM_PRIVATE, status:VALID,
PACKAGE BODY: SYS.DBMS_LOB_AM_PRIVATE 12.2.2
owner:SYS, object_type:PACKAGE BODY, object_name:DBMS_LOB_AM_PRIVATE, status:VALID,
PACKAGE BODY: SYS.DBMS_LOB_AM_PRIVATE 12.1.1
owner:SYS, object_type:PACKAGE BODY, object_name:DBMS_LOB_AM_PRIVATE, status:VALID,
PACKAGE: SYS.DBMS_TYPES 12.1.1
owner:SYS, object_type:PACKAGE, object_name:DBMS_TYPES, status:VALID,
PACKAGE: SYS.DBMS_TYPES 12.2.2
owner:SYS, object_type:PACKAGE, object_name:DBMS_TYPES, status:VALID,
PACKAGE: SYS.DBMS_LOB_AM_PRIVATE 12.1.1
PACKAGE: SYS.DBMS_LOB_AM_PRIVATE 12.2.2
PACKAGE BODY: SYS.DBMS_LOB_AM_PRIVATE 12.1.1
PACKAGE: SYS.DBMS_DBFS_CONTENT 12.2.2
owner:SYS, object_type:PACKAGE, object_name:DBMS_DBFS_CONTENT, status:VALID,
PACKAGE BODY: SYS.DBMS_LOB_AM_PRIVATE 12.2.2
TYPE: SYS.DBMS_DBFS_CONTENT_PROPERTIES_T 12.1.1
owner:SYS, object_type:TYPE, object_name:DBMS_DBFS_CONTENT_PROPERTIES_T, status:VALID,
TYPE: SYS.DBMS_DBFS_CONTENT_PROPERTIES_T 12.2.2
owner:SYS, object_type:TYPE, object_name:DBMS_DBFS_CONTENT_PROPERTIES_T, status:VALID,
PACKAGE: SYS.DBMS_DBFS_CONTENT 12.1.1
owner:SYS, object_type:PACKAGE, object_name:DBMS_DBFS_CONTENT, status:VALID,
TYPE: SYS.DBMS_DBFS_CONTENT_PROPERTY_T 12.1.1
owner:SYS, object_type:TYPE, object_name:DBMS_DBFS_CONTENT_PROPERTY_T, status:VALID,
TYPE: SYS.DBMS_DBFS_CONTENT_PROPERTY_T 12.2.2
owner:SYS, object_type:TYPE, object_name:DBMS_DBFS_CONTENT_PROPERTY_T, status:VALID,
12.2.2 DBA Data 12.2.2
12.2.2 DBA Data 12.2.2
12.1.1 DBA Data 12.1.1
12.1.1 DBA Data 12.1.1
PACKAGE: SYS.PLITBLM 12.1.1
owner:SYS, object_type:PACKAGE, object_name:PLITBLM, status:VALID,
PACKAGE: SYS.PLITBLM 12.2.2
owner:SYS, object_type:PACKAGE, object_name:PLITBLM, status:VALID,
SYS.DBMS_LOB_AM_PRIVATE dependencies on DBMS_LOB_AM_PRIVATE 12.1.1
SYS.DBMS_LOB_AM_PRIVATE dependencies on DBMS_LOB_AM_PRIVATE 12.2.2
PACKAGE: SYS.DBMS_ASSERT 12.2.2
owner:SYS, object_type:PACKAGE, object_name:DBMS_ASSERT, status:VALID,
PACKAGE: SYS.DBMS_ASSERT 12.1.1
owner:SYS, object_type:PACKAGE, object_name:DBMS_ASSERT, status:VALID,
PACKAGE: SYS.STANDARD 12.1.1
owner:SYS, object_type:PACKAGE, object_name:STANDARD, status:VALID,