Central Console: Managing Databases



This page provides the user access to all the various database and daemon-related tasks that are required to keep a Source or Standby location in good operational condition.

All actions are Configuration/DDC-specific. The full list of available actions is as follows:

  1. The time gap between source and destination[ 1]
  2. Log Gap Report [2]
  3. Send Logs [3]
  4. Apply Logs [4]
  5. Database Actions → (Status/Restart/Start/Stop) [5]
  6. Daemon Actions → (Status/Start/Stop) [6]
  7. Recreate Standby Control File [7]
  8. Refresh One Data File [8]
  9. Send One Log File [9]
  10. This graph shows the precise time gap between the Source and Destination databases. This graph is updated on every database action, e.g. send logs, or log gap report.Viewing this graph is a good way of quickly determining if a problem exists with the regular synchronization of the backup database

Actions 1-5 are not considered major processes - when these are clicked/initiated, a "Working..." message appears on-screen briefly, and is then replaced by the result(s) of the action.

Actions 6-8 are considered major processes - when these are initiated, they generate Tasks that appear in the Active Task List, and can be tracked/managed by the user from there.

1. The Log Gap Report

The Log Gap Report allows you to quickly see at a glance the time difference and log gap between the Source and Destination Hosts.

2.  Send Archive Logs to Standby from Primary

Launching this action will initiate the transfer of archive logs from the Primary Host. While typically done automatically on a schedule, this manual action can be useful to run, for example, before attempting to run the Synchronize process.

Clicking the button [1] starts the process. Since Send Logs counts as a major process (see the full list of major processes in section 10.0), it generates a Task object [2]. Clicking on the task object shows the live progress log [3].

3. Applying Archive Logs on Standby

The matching action of Send Logs above, Apply Logs causes the archive logs transferred from the Primary to the Destination Host to be applied. This should almost always be done after a successful Send Logs process.

4.  Database Status, Restart, Start and Stop

These actions allow you to issue basic commands to the Host databases from the GUI. You must first select a Host to work with [1], and then click the button for the action you would like to take [2].

5. Daemon Status, Start and Stop

Very similar to the Database actions above, here you can issue basic commands to the Standby Daemon process. Select the Host to contact [1], then the action to take [2].

5.1 Daemon Controls on a Windows Environment

If you are running Standby on a Windows environment, the available Daemon Control options are a little different. In order to work with the Daemon, Dbvisit must first install a Windows Service to manage the communication.

You can check whether the required Service is installed and/or running by selecting the host [ 1 ] and the Status is displayed for the particular host [2]. To start the daemon click on the start button [3]

This command will return whether the Service is (a) installed, and (b) running. The Service must be both installed and running to work.

If the Service is not installed, all other commands (Uninstall, Start, Stop) will fail, and may incorrectly report an error. Therefore, you should always run the Status command if in doubt over the status of the Daemon Service

To install the Service, click the Install button.

Once the Service is installed, you may use the other commands at will exactly as you would as per section 5.

6. Recreate the Standby Control File

Using this action, you can resolve problems with a corrupt/malformed Standby control file by replacing it from the Source Host.

NOTE: Initiating this action [1] will restart the standby database, and thus may take some time.

Also, because this action is considered a major process, it generates a Task once started [2].

7. Refresh a Standby Database Datafile

This action allows you to refresh a single database backup file, from Source to Destination. This can be extremely useful in case a single file was corrupted during transfer, and you do not have the time or network resources to perform the entire backup process again.

You will need to know the file number that you want to refresh/replace. Enter it in the input field [1], and then press Submit [4]. As a major process, this action will generate a Task object. Temporary locations can be used for backing up the datafiles in source and can be transferred to another temporary location in standby (options [ 2] and [ 3] ). This is usually used if the datafile is too large to be backed up in the DBVISIT_BASE/standby/tmp location.

8. Send One Log File

This action allows you to re-send a single archive log file, most frequently useful in cases of data corruption. Enter the desired Sequence [1] and Thread [2] numbers, and initiate by clicking Submit [3]. As a major process, this action will generate a Task object.

Have more questions? Submit a request