Abstract: A manager file system (MFS), implemented using an OS process, exposes a path in the native file system as the root of its file system (e.g., mount point). The MFS informs the OS kernel that any file system operation whose path contains the mount point as its prefix, should be handed over to the process by invoking an appropriate interface method that the process implements as part of its file system implementation. The MFS manages one or more applications and leverages the authentication mechanism of the OS to provide fined-grained access control of MFS managed applications.

Abstract: A manager file system (MFS) runs as a user space file system. The MFS, implemented using an OS process, exposes a mount point as a communication endpoint to the single process. Mounting, unmounting, and changing configuration of individual database file systems (DBFSs) are done by overloading extended attributes on the mount point. The MFS services all DBFSs mounted at different mount points registered to the single process of the MFS and ensures optimal resource utilization among the DBFSs in the single process while guaranteeing resource isolation.

Abstract: A manager file system (MFS) runs as a user space file system. The MFS, implemented using an OS process, exposes a mount point as a communication endpoint to the single process. Mounting, unmounting, and changing configuration of individual database file systems (DBFSs) are done by overloading extended attributes on the mount point. The MFS services all DBFSs mounted at different mount points registered to the single process of the MFS and ensures optimal resource utilization among the DBFSs in the single process while guaranteeing resource isolation. Multiple MFSs may be created to manage sets of DBFSs.

Abstract: A manager file system (MFS) runs as a user space file system. The MFS, implemented using an OS process, exposes a mount point as a communication endpoint to the single process. Mounting, unmounting, and changing configuration of individual database file systems (DBFSs) are done by overloading extended attributes on the mount point. The MFS services all DBFSs mounted at different mount points registered to the single process of the MFS and ensures optimal resource utilization among the DBFSs in the single process while guaranteeing resource isolation.

Abstract: A manager file system (MFS) runs as a user space file system. The MFS, implemented using an OS process, exposes a mount point as a communication endpoint to the single process. Mounting, unmounting, and changing configuration of individual database file systems (DBFSs) are done by overloading extended attributes on the mount point. The MFS services all DBFSs mounted at different mount points registered to the single process of the MFS and ensures optimal resource utilization among the DBFSs in the single process while guaranteeing resource isolation. Multiple MFSs may be created to manage sets of DBFSs.

Abstract: A manager file system (MFS), implemented using an OS process, exposes a path in the native file system as the root of its file system (e.g., mount point). The MFS informs the OS kernel that any file system operation whose path contains the mount point as its prefix, should be handed over to the process by invoking an appropriate interface method that the process implements as part of its file system implementation. The MFS manages one or more applications and leverages the authentication mechanism of the OS to provide fined-grained access control of MFS managed applications.

Abstract: Systems for high-performance, low-latency database log mining applications. A method commences upon receiving a log mining query. The query specifies desired results that correspond to a prior logical state of the database system. A first type of processing entity is invoked to process contents of the redo stream by loading metadata into a data dictionary, and a second type of processing entity is invoked to construct metadata from the redo stream, wherein the constructed metadata pertains only database objects referenced in the query. During the time that the first type of processing entity is processing contents of the redo stream by loading metadata into a data dictionary, a process of a second type serves incoming queries using a subset of entries in the redo stream. When the data dictionary is completed, a switchover point is reached and thenceforth, incoming queries are served using the first type of processing entity.

Abstract: Systems for high-performance, low-latency database log mining applications. A method commences upon receiving a log mining query. The query specifies desired results that correspond to a prior logical state of the database system. A first type of processing entity is invoked to process contents of the redo stream by loading metadata into a data dictionary, and a second type of processing entity is invoked to construct metadata from the redo stream, wherein the constructed metadata pertains only database objects referenced in the query. During the time that the first type of processing entity is processing contents of the redo stream by loading metadata into a data dictionary, a process of a second type serves incoming queries using a subset of entries in the redo stream. When the data dictionary is completed, a switchover point is reached and thenceforth, incoming queries are served using the first type of processing entity.

Abstract: Techniques are provided for data definition language (DDL) expression annotation. DDL expression text is captured. The DDL expression text corresponds to a DDL change in a source database. A component set is determined. The component set includes at least one component in the DDL expression text. An annotation set is generated. The annotation set includes at least one annotation for at least one component of the component set. Each annotation includes hierarchical data describing at least one hierarchical relationship in the component set. For example, an annotation may include a component ID, a component position, a component length, a component type, and a parent component ID. The annotation set and a change record comprising the DDL expression text are transmitted to a replication client.