Space Manager with LiveReorg 9.0 - User Guide

Configure Additional Notification Events

After enabling SMTP email or SNMP trap notification methods, you can specify additional notification events by configuring parameters in Quest Service Agent (QSA). You can specify which events will trigger a notification and which notification method to use for each event.

In addition, you can configure QSA to send a notification when a LiveReorg finishes that includes the reorganization results. This option is available for the SMTP email method only.

To configure notification details (SMTP email or SNMP trap)

1. Run Space Manager and connect to the target database for QSA. Connect as the Oracle DBA that installed the agent.

2. Select Tools | Admin | Quest Server Agent | Manage Quest Server Agent Installation.

3. Select Configure Quest Server Agent and click Next .
4. If your database resides on a UNIX or Linux server, a login window displays. Enter the login name and password of the UNIX or Linux account that installed the agent.

5. In the QSA Parameters page of the QSA Installer, for each event you want to monitor, enter one of the following four values based on the notification method you want to use (and have enabled):

   Value	Description
   "NONE"	Notification is disabled.
   "EMAIL"	Send SMTP email notification.
   "SNMP"	Send SNMP trap notification.
   "BOTH"	Send both SMTP email and SNMP trap notification.

6. Enter one of the values listed above into the value field for each parameter that corresponds to an event you want to monitor. Select from the following parameters:

   Note: To view all parameters, clear the Show only required fields with missing value checkbox.

   Parameter	Description
   SEND_GROUP_STATUS	Send notification of a static change to the group status.
   SEND_SCRIPT_START	Send notification when script starts (101).
   SEND_SCRIPT_RESTART	Send notification when script is restarted (104).
   SEND_SCRIPT_UNSCHEDULED	Send notification when script is unscheduled (110).
   SEND_SCRIPT_COMPLETE	Send notification when script completes (210).
   SEND_SCRIPT_CANCELLED	Send notification when script is cancelled (310).
   SEND_SCRIPT_ABORT	Send notification when script aborts (320).
   SEND_SCRIPT_HALTED	Send notification when script is halted (370).
   SEND_SCRIPT_SCHEDULED	Send notification when a script is scheduled (410).
   SEND_LR_WAIT_WINDOW	Send notification when a LiveReorg is waiting for window (620).
   SEND_LR_IN_WINDOW	Send notification when a LiveReorg is in the window (621).
   SEND_LR_WAIT_APPROVAL	Send notification when a LiveReorg is waiting for approval (630).
   SEND_LR_APPROVED	Send notification when a LiveReorg is approved (631).
   SEND_LR_START	Send notification when a LiveReorg starts (710).
   SEND_LR_RESTART	Send notification when a LiveReorg restarts (715).
   SEND_LR_COPY_START	Send notification when a LiveReorg table copy starts (720).
   SEND_LR_COPY_COMPLETE	Send notification when a LiveReorg table copy completes (730).
   SEND_LR_SWITCH_START	Send notification when a LiveReorg starts to switch (740).
   SEND_LR_SWITCH_COMPLETE	Send notification when a LiveReorg switch completes (750).
   SEND_LR_COMPLETE	Send notification when a LiveReorg completes (760). Setting this parameter sends an email without a results report. To include a results report, use one of the SEND_LR_COMPLETE parameters listed below.

   Tip: The parameter prefix indicates the level of the event. SEND_SCRIPT prefixes script-level events, which occur no more than once per script execution. SEND_LR prefixes live-reorganization-level events, which occur one or more times depending on the number of live reorganization objects in the script.

To configure SEND_LR_COMPLETE parameters (SMTP email only)

1. To specify the type of results report you want to include in a notification that is sent after a LiveReorg finishes, select from the following parameters:

   Parameter	Results Report Type	Description
   SEND_LR_COMPLETE	No report	No report
   SEND_LR_COMPLETE_DATA	Detail objects, summary by object type and total savings reports.	This report is the most detailed and includes the object details, detailed storage data, and a storage data summary by object.
   SEND_LR_COMPLETE_SUM	Summary by object type and total savings reports.	This report delivers a summary of the storage data by object.
   SEND_LR_COMPLETE_TOTAL	Total savings report.	This report lists the storage data totals only.

Note: To use this feature, you must also enable the type of notification method you want to use. See Enable Email (SMTP) Notification and Enable SNMP Traps Notification for more information.

Related Topics

Enable Email (SMTP) Notification

Enable SNMP Traps Notification

Use LiveReorg Shell

Live Reorg Shell (LRSH) is a command line tool you can use to monitor Live Reorg scripts. Many of the tasks you can perform using the Scripts/Job Monitor you can perform using Live Reorg Shell.

This tool can be useful for server Administrators and others who do not have access to the Space Manager desktop application, but would like to monitor or run Live Reorg scripts.

Live Reorg Shell vs Desktop Application

When to use Live Reorg Shell

Use Live Reorg Shell when you do not have access to the Space Manager desktop application, but you need to stop a script, run a script, approve a switch, or just monitor a job.

How to access Live Reorg Shell

Live Reorg Shell is installed on the server along with QSA. You can access Live Reorg Shell directly from the server or remotely. To access Live Reorg Shell remotely, use Telnet or any similar secure-shell remote-access utility.

What you can do using Live Reorg Shell

Live Reorg Shell allows you to perform many of the same tasks you normally perform using the Scripts/Job Monitor. You can do the following using Live Reorg Shell:

• Start a job
• Stop (Cancel) a job
• Restart a job
• Approve a switch
• View job lists and script lists
• View job logs
• View scripts

Important: You cannot use LiveReorg Shell to clean up jobs. If you cancel a job using LiveReorg Shell, you must then use the Space Manager application to perform clean-up tasks, if required.

How to Use Live Reorg Shell

To start Live Reorg Shell

1. Start Telnet or other secure-shell remote-access utility.
2. Connect to the server where the database is located.
3. Using the command line, navigate to the directory containing the database on which the scripts you want to monitor are running.
4. When you are in the database directory, at the prompt type ./lrsh to start Live Reorg Shell.
5. When prompted, enter your Oracle user name and password.
6. At the lrsh prompt, type commands to monitor jobs or perform tasks.

To get help (list commands)

• At the lrsh prompt, type help. Live Reorg Shell lists all relevant commands and their descriptions.

  Note: Live Reorg Shell help is context-sensitive. LRSH lists only the commands that are relevant to the level at which the prompt is currently located.

To monitor jobs and scripts

1. After starting LRSH, at the lrsh prompt, type list to list the current jobs for this database. A list of jobs (script groups) displays, including start, schedule, and finish dates, and job status.

   Note: If the list is incomplete, type ENTER to display additional jobs (script groups).

2. To select a job, type the job number after the list displays. The job's status information displays.

   Note: To refresh the job status information, press ENTER.

3. After selecting a job, you can view all scripts or take action on this job.
   • To view all scripts in the job, type list. The list includes the table name and the script status.

   • To take action on the job, type a command to start, cancel, restart, un-schedule, or approve the job (script group).

     Note: Type h here to list relevant commands.

4. After the script list displays, type a to approve the script waiting for approval.
5. To select a script, type the script number (after the script list displays).
6. After you select a script, you can view log files for the selected script.
   1. To view script log files, press ENTER after selecting the script.
      • To select and view a particular log, type the log file number. Press ENTER to view more log file data.
7. After completing a task, you can type q to go up a level and/or to eventually exit from LRSH.

List of Commands

Use the following commands to start Live Reorg Shell or to display run options.

The following table lists some of the most-frequently used commands in Live Reorg Shell.

Note: Live Reorg Shell commands are case-sensitive.

Tip: To exit Telnet, type exit.

Manage and Monitor QSA

As you monitor and manage scheduled scripts from the Scripts/Job Monitor window, you can also monitor and manage the Quest Server Agent (QSA). This allows you to easily check the status of QSA, which is used to run stored scripts. Most management functions can only be used when QSA is running.

Check QSA Status

You can check the status of QSA from the QSA Status panel at the top of the Scripts/Job Monitor window. You can also check its status in the QSA field in the top-right corner of the Script Properties dialog.

QSA can be in one of four states:

• Running—When QSA is running for a database, Running is displayed in the monitor. QSA is running is displayed in the Script Properties dialog.
• Not running—When QSA is installed but not running for a database, Not running is displayed in the monitor. QSA is not operable is displayed in the Script Properties dialog. QSA must be running before scheduled scripts can be run.
• Not installed—When QSA is not installed for a database, Not installed is displayed in the monitor. QSA is not operable is displayed in the Script Properties dialog.
• Obsolete—When QSA is installed for a database, but not current, Obsolete is displayed in the monitor. QSA is considered to be current when its version number is the same as Space Manager’s version number.

QSA starts automatically during installation on UNIX servers and local Windows servers (those that reside on your Space Manager client computer). To start QSA on a remote Windows server, use the Windows Services window on the server.

Notes:

• You can specify the interval at which Space Manager checks the Server Agent status in Options (Tools | Options | Server Agent).
• If you are running Space Manager in an active-active OPS or RAC environment, the acronym RAC is displayed beside QSA Status panel. The Space Manager client must be connected to the instance used for QSA before you can start and stop QSA.
• If QSA is not installed (or not current), you can install (or upgrade) it using the QSA Installer or the manual install script available for UNIX and Linux. See About QSA Server Agent for more information. For detailed information about installing the Quest Server Agent, see the Space Manager with LiveReorg Installation Guide .

Start QSA from the Scripts/Job Monitor

In most cases, QSA starts automatically when it is installed. It then runs continuously, waiting to execute scripts at their scheduled times. Normally, QSA only needs to be restarted if it was stopped using the Stop Quest Server Agent function.

The Start Quest Server Agent function can be used to start QSA on local Windows servers (those that reside on your Space Manager client computer) and on UNIX and Linux servers to which you have both SSH and SFTP access. See Start QSA Under Special Circumstances for more information about starting QSA with other configurations.

Note: If QSA is not running when a script’s scheduled execution time occurs, you have 10 minutes in which to start it. The script is executed when QSA starts. If QSA starts after the 10-minute time window ends, the script aborts with this error: “QSA-20312: Scheduled launch time expired”. To run a script whose launch time has expired, execute it on demand or reschedule it from the Scripts/Job Monitor.

To start QSA from the Scripts/Job Monitor

1. Select QSA | Start Quest Server Agent or click in the monitor toolbar.
2. If your database resides on a UNIX or Linux server, the server login dialog displays. Enter the login name and password of the UNIX or Linux account that runs QSA.
3. When the Quest Server Agent Started message displays, click OK to clear it.
4. Check the QSA Status panel at the top of the monitor to confirm that QSA is now running.

Restart QSA from the Scripts/Job Monitor

Use the Restart Quest Server Agent function when you do not have the permission level necessary to start the Quest Server Agent. The Restart Quest Server Agent function automatically stops and restarts the agent. This only requires the same permission level as that for stopping the agent.

To restart QSA from the Scripts/Job Monitor

1. Click in the monitor toolbar.
2. After the agent restarts, a Quest Server Agent restarted message displays.

Stop QSA from the Scripts/Job Monitor

The Stop Quest Server Agent function can be used to stop QSA on local Windows servers (those that reside on your Space Manager client computer) and on UNIX and Linux servers to which you have both SSH and SFTP access. See Stop QSA Under Special Circumstances for more information about stopping QSA with other configurations.

To stop QSA from the Scripts/Job Monitor

1. Select QSA | Stop Quest Server Agent or click in the monitor toolbar.
2. When the Quest Server Agent Stopped message displays, click OK to clear it.
3. Check the Quest Server Agent Status panel at the top of the monitor to confirm that QSA is no longer running.

Tip: You can also start, restart, and stop QSA using the Tools | Admin | Quest Server Agent menu. See Start or Stop QSA Server Agent for more information.

Monitor Statistics Collection Scripts

Note: Analysis Groups is a discontinued feature in Space Manager. This topic is provided for users who may continue to run existing statistics-collection scripts that were created in a previous version of Space Manager.

As you monitor statistics collection scripts, be aware that three scripts can be run for one analysis group:

• Collection script—This is used to collect statistics. It is the only script that remains displayed in the Scripts/Job Monitor after collection is performed.
• Collection rescheduler script—This is used to schedule statistics collection. Collection rescheduler scripts have an “s” in parentheses beside their names, for example “Rescheduler (s)”.
• Collection worker script—This tells QSA to perform collection using parallel processes. Collection worker scripts have a “p” in parentheses beside their names, for example “Worker (p)”.

The statistics collection script runs first. Immediately after this script completes, its status is “Completed”. After the rescheduler script runs, the collection script’s status is changed to “Scheduled”. If a collection script is scheduled to run only once, it is cleared from the monitor when it completes.

If QSA parallel processing is selected for an analysis group, the worker script runs next. When it completes, its status is displayed as “Completed” and it is cleared from the Scripts/Job Monitor (it remains in the monitor if statistics collection is aborted).

The rescheduler script runs last. After it completes, its status is “Completed”.