Search Results createfilesystem_log

Overview

SYS.DBMS_DBFS_SFS_ADMIN is a VALID Oracle-supplied PL/SQL package that provides the administrative interface for the SecureFiles File System (SFS) implementation of the Database File System (DBFS). In Oracle EBS 12.1.1 and 12.2.2 environments, this package is a foundational infrastructure component rather than an E-Business Suite application API. It exposes the privileged operations required to create, register, initialise, configure, and tear down DBFS stores that are physically backed by SecureFiles LOB segments within the database. Because DBFS allows unstructured content to be managed through ordinary database tablespaces and LOB storage, DBMS_DBFS_SFS_ADMIN is the mechanism by which DBAs and application schema owners provision the storage containers that higher-level DBFS content APIs and file system mounts subsequently consume. The package owner is SYS, and the ETRM metadata classifies its API classification as OTHER, confirming that it is an Oracle-managed control package rather than a business-facing EBS API. Its dependent objects include SYS.DBMS_DBFS_CONTENT_PROPERTIES_T and SYS.DBMS_DBFS_SFS, and it is granted to PUBLIC, which allows appropriately privileged callers in any schema to invoke its routines.

Key Procedures and Functions

The ETRM metadata documents 42 procedures and functions in this package. The principal administrative routines include CREATEFILESYSTEM and CREATEFILESYSTEM_LOG, which define a new SecureFiles-based file system and provide a logging variant for diagnostics. REGISTERFILESYSTEM and REGISTERFILESYSTEM_LOG make an existing store known to the DBFS content framework, while UNREGISTERFILESYSTEM and UNREGISTERFILESYSTEM_LOG perform the inverse operation. INITFILESYSTEM and INITFILESYSTEM_LOG initialise the internal structures of a registered file system. DROPFILESYSTEM and DROPFILESYSTEM_LOG permanently remove a file system and its associated storage. SETFSPROPERTIES and SETFSPROPERTIES_LOG alter configuration properties of an existing file system. Management and reporting routines include GETSTOREID, which returns the store identifier, plus the capacity and diagnostic functions SPACEUSAGE, SPACEDEPENDENTS, DEFAULTTABLESPACE, TBSUSAGE, and LOBUSAGE. CREATESNAPSHOT supports point-in-time snapshot creation, and BLESSUSER grants the privileges required for a user to administer or access the store. The _LOG variants of the creation, registration, initialisation, property, and drop routines return diagnostic output that is useful for troubleshooting provisioning failures.

Tables Accessed

The ETRM documentation for this object does not list direct table references through APPS synonyms, which is expected for a SYS-owned package. Instead, the package operates on the DBFS infrastructure dictionary tables and SecureFiles LOB segments that DBFS itself maintains. Administrative operations such as creation, registration, initialisation, and property changes write to and read from the DBFS store registry and content metadata structures, while the usage and dependent-space functions read storage allocation data associated with the underlying tablespaces and LOB segments. The declared dependencies on DBMS_DBFS_CONTENT_PROPERTIES_T and DBMS_DBFS_SFS reflect this indirect access: the package uses the content properties type and the base SFS package to manipulate store metadata rather than issuing SQL against EBS application tables. Consequently, no E-Business Suite transactional or setup tables are touched by this package.

Usage Notes

DBMS_DBFS_SFS_ADMIN is typically invoked by a DBA or privileged application schema owner from SQL*Plus, a deployment script, or an installation driver during the provisioning and maintenance of DBFS stores. It is not normally called from EBS forms or concurrent programs; when DBFS-backed attachments or content repositories are deployed, the runtime access path is through the DBFS content APIs and mounts, while this package handles the one-time and lifecycle administration. The _LOG procedures should be used in scripted deployments so that output can be captured for audit and error resolution. Because the package is owned by SYS and granted to PUBLIC, execution privilege alone does not imply suitability for ad hoc use; administrative operations such as DROPFILESYSTEM are destructive and should be reserved for controlled change windows. The ETRM metadata also records that the package is referenced by one other package, indicating that internal Oracle components depend on it, and custom code should avoid bypassing the documented entry points or manipulating DBFS dictionary tables directly.