Space Manager with LiveReorg 9.0 - User Guide

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.

Appendix

Use the Find Long LONGs Package

Use the Find Long LONGs Package

Space Manager with LiveReorg includes the Find Long LONGs package. This allows users and reorg tools to easily identify tables with “long LONG” columns. These are LONG or LONG RAW columns that are larger than 32,760 bytes in size.

The size of LONG and LONG RAW columns determines which data movement method can be used to reorganize their tables. Tables that contain LONG columns in which some rows contain data larger than 32,760 bytes must be reorganized with FastCopy (or DBMS_DataPump). Tables that contain LONG columns where all rows are 32,760 bytes or less can be reorganized with either FastCopy/DBMS_DataPump or SQL (PL/SQL is used).

If a table is not supported for FastCopy (or DBMS_DataPump) and its LONG columns are 32,760 bytes or less , run the long LONGs procedure to provide this information to Space Manager. This information may enable Space Manager to reorganize the table. If Space Manager does not know the size of a LONG column, its table is excluded from reorganization.

Reorg Manager automatically checks the Find Long LONGs table to identify tables with long LONGs. You can query the table yourself to identify these tables. See Query the Find Long LONGs table for more information.

The Find Long LONGs package (QUEST_SPC_FIND_LONG) is installed with Space Manager. (The package is installed via the SPC_PKG_FIND_LONG.SQL script, which is located in the INSTALL subdirectory of the Space Manager client directory.) The package includes the following:

• Find Long LONGs table—Called QUEST_SPC_LONG_TABLES, this contains information on the size of any LONG or LONG RAW columns contained in your tables. The Find Long LONGs table is created when you install Space Manager server components; it is located in the tablespace you specify for server components.

• Find Long LONGs procedure—Called QUEST_SPC_FIND_LONG.EXECUTE, this procedure populates the Find Long LONGs table with information on the size of any LONG or LONG RAW columns contained in your tables.

  For more information about the Find Long LONGs procedure or to learn how to run the procedure, see Populate the Find Long LONGs table.

Important: Before you can use the Find Long LONGs package, Oracle’s UTL_RAW package must be installed and valid on your database server.