Abstract: Techniques are provided for using a sparse file to create a hot archive of a pluggable database of a container database. In an embodiment and while a source pluggable database is in service, a source database server creates a clone of the source pluggable database. Also while the source pluggable database is in service, the source database server creates an archive of the source pluggable database that is based on the clone. Eventually, a need arises to consume the archive. A target database server (which may also be the source database server) creates a target pluggable database based on the archive.

Abstract: In accordance with an embodiment, described herein is a system and method for use of immutable accessors with dynamic byte arrays. In accordance with an embodiment, a database driver provides access by software applications executing at an application server to data at a database, including associating a result set cache manager with a pool of result set caches. Each result set cache can be associated with one or more immutable accessors. In response to receiving a request from an application, to access a set of data, the set of data from the database is received into a particular result set cache. In response to receiving a subsequent request for a same set of data, from a same or another application using a same or another database connection, access is provided to the immutable accessor associated with the particular result set cache, for use in accessing the data therein.

Abstract: A system and method for facilitating integrating enterprise data from multiple sources for display via in a common interface. An example method includes displaying, via a first user interface display screen, a first set of one or more personnel icons representative of one or more enterprise personnel, and providing a first user option to select one or more of the personnel icons. A second user interface display screen may be displayed in response to or after selection of one or more of the personnel icons. The second user interface display screen presents a first type of data. The second user interface display screen further provides a second user option to select one or more user interface features associated with the first type of data, and to then trigger display of a third user interface display screen. The third user interface display presents a second type of data that is associated with the first type of data.

Abstract: Various techniques are provided for facilitating the management of hierarchical data within a relational database system. One such technique involves separating the storage structures used to store data that captures the information about the hierarchy (the “hierarchy structures”), from the storage structures used to store the content of the resources that belong to the hierarchy (the “content structures”). Techniques are also provided for allowing users to customize the metadata attributes associated with resources that belong to the information hierarchy. One technique involves registering XML schemas that specify the metadata attributes desired by a user. Another technique involves storing attributes that do not correspond to any declared field in a “catch-all” column within the resource table. Techniques are provided for determining how to store resources as they are added to the database. According to one technique, the database server searches the data of the resource to find content-type information.