Search Results fs_unlink




Overview
Explore in AI Chat

Overview

SYS.DBMS_FUSE is an Oracle Database-supplied PL/SQL package owned by the SYS schema and shipped with the database kernel, not with the Oracle E-Business Suite application schema. Its purpose is to expose a Filesystem in Userspace (FUSE) interface from within the database, allowing database-resident content—principally SecureFiles and other content managed through the DBFS Content API—to be surfaced to an operating-system file system. The package acts as the server-side bridge that services file-system callbacks (attribute lookup, read, write, directory traversal, and so on) issued by an external FUSE mount process.

Within an EBS 12.1.1 or 12.2.2 environment, DBMS_FUSE is not part of any EBS business flow. It is present because it is a component of the standard Oracle Database installation. EBS documentation classifies the package under API classification OTHER, reinforcing that it is not an EBS-owned or EBS-supported application programming interface. It depends on SYS.DBMS_DBFS_CONTENT_RAW_T and the STANDARD package, confirming that its operations are layered on top of the DBFS content store.

Key Procedures and Functions

The ETRM metadata documents 66 procedures and functions for this package. The first twenty entries, which illustrate the scope of the interface, are:

  • FS_GETATTR — returns file or directory attributes such as size, timestamps, ownership, and permissions.
  • FS_READLINK — resolves the target of a symbolic link.
  • FS_MKNOD — creates a file-system node, typically a regular file.
  • FS_MKDIR — creates a directory entry in the DBFS content hierarchy.
  • FS_UNLINK — removes a file entry from the content store.
  • FS_RMDIR — removes an empty directory.
  • FS_SYMLINK — creates a symbolic link.
  • FS_RENAME — renames a file or directory within the same path context.
  • FS_MOVE — relocates a file or directory to a different path.
  • FS_LINK — creates a hard link between path entries.
  • FS_CHMOD — changes permission bits on a content node.
  • FS_CHOWN — changes the owner or group associated with a content node.
  • FS_TRUNCATE — reduces or extends a file to a specified length.
  • FS_UTIME — updates access and modification timestamps.
  • FS_OPEN — opens a file handle in preparation for read or write activity.
  • FS_READ — reads a block of content from an open file.
  • FS_WRITE — writes a block of content to an open file.
  • FS_STATFS — reports file-system level statistics such as capacity and free space.
  • FS_FLUSH — flushes pending changes associated with an open file handle.
  • FS_RELEASE — releases a previously opened file handle.

The remaining functions follow the same POSIX-oriented naming convention, covering additional directory enumeration, locking, and handle-management operations. They are intended for consumption by the FUSE mount daemon rather than by application code.

Tables Accessed

The ETRM metadata records no application tables referenced through APPS synonyms for this package, and it documents no direct table dependencies beyond SYS.DBMS_DBFS_CONTENT_RAW_T. This is consistent with the package's design: all persistent state is held in the DBFS content repository managed by the DBFS Content API, not in EBS application tables. Because no APPS synonyms are involved, the package operates entirely within the database kernel schema and does not touch EBS transactional data.

Usage Notes

DBMS_FUSE is referenced by PUBLIC and by SYS itself, and the documentation records that it is referenced by zero other packages in the EBS schema set. It is not invoked from EBS forms, concurrent programs, or standard application code. The package has no role in EBS functional processing, and its presence in an EBS instance should be treated as an artifact of the underlying database release.

If the package appears during dependency analysis or patching, it is most likely the result of a database-level query or an automated inventory scan rather than an application dependency. Custom development within EBS should not call DBMS_FUSE directly; use of the DBFS Content API or the supported DBMS_LOB and SecureFiles interfaces is the appropriate alternative. Any FUSE mount configuration would be performed outside the EBS application tier, at the database host level, using the standard Oracle DBFS client tooling.