VDB icons have changed to represent datasets. You can quickly create a new dataset group or add a new dataset by clicking the plus button. You can also filter and locate a particular dataset. By reading further, you will learn where each of these improvements is located.
The screenshot below provides a visual orientation along with descriptive narratives to help you navigate to activities and viewing panels.
Datasets panel – The left-hand pane of the admin console allows you to collapse or expand groups to view dSources, VDBs, and vFiles associated with each group.
Add button – Click this button to add dataset groups, add dSources, or create vFiles.
Information pane – The right-hand pane of the admin console provides displays information for about the selected dSource, VDB, or vFiles.
The Datasets Panel
Clicking the plus sign allows you to add Dataset Groups, add dSources, and create vFiles.
You can use the Filter field to locate a particular dSource, VDB, or vFile regardless of which group the item is located in.
The buttons collapse or expand groups to view the associated dSources, VDBs, and vFiles.
The button collapses or expands the selected group. Within a group, dSources are listed first, followed by VDBs. The dSources and VDBs are displayed alphabetically; this display order cannot be changed.
New state icons have been introduced, such as for dSources and for VDBs. For a complete list of new icons, see State Icons.
A yellow bar next to a dSource or VDB indicates a warning fault. A red bar indicates a critical fault.
The Status tab provides a read-only view of information about the status of the selected object. In the screenshot below, a dSource was selected from the Datasets panel, and the Status tab displays information about the dSource. By selecting the pencil icon next to the Notes field, you can enter additional notes. The dataset information pane shown below, identifies new UI features you will want to familiarize yourself with.
Dataset information Pane
Clicking the pencil icon located next to the name after selecting a dSource or VDB allows you to edit the displayed nomenclature for that object at the top of the pane.
Selecting the Status tab provides a read-only view of information about the selected dSource, VDB, or vFiles.
Selecting the TimeFlow tab allows you to view, refresh, rewind, or provision depending on if you have chosen to view a single VDB, dSource, or vFiles.
Selecting the Configuration tab provides configuration information for any chosen Dataset such as dSource, VDB, or vFiles.
The Delphix Engine allows you to link to an external database by creating a dSource within the Delphix system. Once linked, the Delphix Engine keeps a complete history of the database, which it maintains through the use of SnapSync and LogSync. The database’s history is represented as a collection of snapshots and logs that create the TimeFlow. Clicking the TimeFlow tab allows you to quickly provision a VDB from a selected dSource at any time within your TimeFlow. Additionally, when VDBs are selected, you can quickly refresh the VDB from the TimeFlow tab.
To provision from a point in time within a snapshot, slide the LogSync slider to open the snapshot timeline, then move the arrow along the timeline.
The scrollbar allows you to select a snapshot. Note: You can take snapshots manually by selecting the Configuration tab, then clicking the Snapshot icon.
This section of the pane allows you to access important data operations such as refresh, rewind, and provision. Note: this section varies depending on whether you have selected a VDB or a dSource. For example, a new improvement has now brought the Refresh button to the TimeFlow pane whenever a VDB is selected (as shown in the figures below; VDB panel vs dSource panel) when a dSource is selected.
Other functions available include:
Refresh VDB – the Refresh VDB button has moved to the TimeFlow pane. This action allows you to refresh a VDB or vFiles.
Rewind – Allows you to rewind to a particular point in time.
V2P – Begin a virtual to physical process. A fter you have created a dSource or a VDB, you can export its contents and log files to a physical database. This process, called V2P , creates a set of directories in the target environment and populates them with the database data, log files, and scripts that are used to recover the physical database. The V2P button automatically starts the physical database recovery process as part of the V2P export.
Provision – Provision a virtual database (VDB) from the Delphix Engine
When you select the Configuration tab, you will be provided with information about the selected database as well as data management features that you can configure, such as retention policies. Within the Configuration tab, additional sub-tabs include masking considerations and hook information.
The Configuration tab contains three sub tabs: Standard, Masking, and Hooks. The Standard tab (shown above) displays information about the selected dSource, VDB, or vFiles. Fields with pencil icons next to them can be modified as required.
This menu bar provides access to various operations. For example, select the icon to take a snapshot or the icon to update a database.
Sliding the Auto VDB Restart button to On enables Delphix to automatically detect whether a target server has been rebooted and proactively restart the VDB.
For more information, see Automatic VDB Restart on Target Server After Reboot.
This drop-down menu allows you to view information about:
Top Wait Events
Top SQL by CPU
The information displayed on the Standard sub-tab varies a little depending on whether you selected a dSource, VDB, or vFiles.
The Masking sub-tab displays the masking jobs that you can use when configuring a VDB. For more information about masking, refer to the Delphix Masking Quick Start Guide.
The Hooks sub-tab displays operations performed on initial provision after a refresh. You can leverage hooks to run required scripts which address several different use cases. For instance, you may want to prevent your monitoring systems from triggering during VDB startup and shutdown. You can now leverage pre- and post-hooks to run required scripts for VDB start/stop operations.
For more information about hooks, refer to Customizing Oracle Management with Hook Operations.