Space Manager with LiveReorg 9.1 - User Guide

Server Agent Locking Strategies

You can use parameters for the Quest Server Agent (QSA) to configure advanced options for locking strategies. The following locking strategies are available for a LiveReorg.

Wait Mode

Wait mode is the default locking strategy used for a LiveReorg. This locking strategy assumes the success of the LiveReorg is the primary objective. When Space Manager issues a table lock using this strategy, the lock type is a blocking exclusive table lock. Blocking occurs within Oracle and causes the lock to wait in a queue until the process obtains the lock.

Wait for No Locks

The Wait for No Locks strategy forces the LiveReorg to wait until a table has no locks before attempting to lock the table. Lock attempts for a table are indicated by an asterisk (*) before the keyword Locking in the status message of the Script/Job Monitor. The process scans the table for locks. If the process finds a lock, it sleeps for a second and rescans the table locks. Once the process does not find a lock on table, it attempts the lock.

No-Wait Mode

You can use No-wait mode as the locking strategy for the initial table copy and switch when the success of the LiveReorg is not the primary objective. This strategy should not be used in most environments. The advantage of this strategy is that the exclusive table lock never blocks and prevents other locks from completing.

Note: You can configure table copy synchronization or online switch locking to use No-Wait mode. However, all QSA parameters to enable No-wait mode are hidden by default. Contact Quest Software technical support for instructions to enable No-Wait mode.

Related Topics  

QSA Server Agent Locks Reporting Parameters

Install Server Agent on UNIX or Linux

Use the following procedure to install (or upgrade) the Server Agent in an Oracle database on a UNIX or Linux server. You can use the Server Agent Installer if you have both SSH and SFTP access to your database server. If you do not have both, you must install the agent manually. See "Manually Install Server Agent on UNIX or Linux" in the Space Manager Installation Guide for more information.

Install the Server Agent using the same DBA account used to install the server components. For information about installation DBA account requirements, see Space Manager User Requirements.

Notes:

• If the target database is in an OPS or RAC system that uses the active-active configuration, see "Install Server Agent on OPS or RAC" in the Space Manager Installation Guide for more information.

• If upgrading the server agent, perform the upgrade when no scheduled scripts are executing or about to execute.

To install (or upgrade) the Server Agent on UNIX or Linux

1. Run the Space Manager client and connect to the target database as the DBA that installed the Space Manager server components.

   Note: If the Server Agent Installer automatically opens after installing the server components, it opens to the Log on to Server page. Skip ahead to step 4.

2. To run the Server Agent Installer, select Tools | Admin | Quest Server Agent | Manage Quest Server Agent Installation.
3. (Upgrade only) If you are upgrading a currently installed instance of QSA, select Upgrade Quest Server Agent on the Select Installation Type page and click Next.
4. In the Log on to Server window, enter the user name and password of the UNIX or Linux account. Enter the host server name if it is not displayed. Click Next.
5. In the Oracle Connection Info window, review the information. If necessary, complete or modify any fields. Click Next. If you are upgrading, you can only edit the staging directory path in this window.
6. In the Install Quest Server Agent window, click Install to install QSA. In the Agent Installation Complete window, click Next.

7. In the QSA Parameters window, specify values for QSA parameters or use the default values.

   Note: Deselect Show only required fields with missing value to see all parameters.

   Values apply to the target database. You must enter values for WORKDIR (used for FastCopy/DBMS_DataPump) and LW_TABLESPACE (used for live reorganizations and required even if LiveReorg is not licensed). Click Next when finished. See QSA Server Agent Parameters for more information.

8. In the Installation Finished window, click Finish to exit the Server Agent Installer.

Note: Before the Server Agent is installed, you may encounter one of the following messages:

• Files not current—The agent installation files are either not available or not current. Exit the Server Agent Installer, install the most recent Space Manager client. New agent files are copied to Server Agent folder on the client computer. You can then install the agent.
• Environment not supported / cannot proceed—Both your Oracle version and operating system version are not supported. The agent cannot be installed. You must upgrade to a supported Oracle version and a supported operating system. See the Space Manager Release Notes for a list of supported Oracle Database and Operating System versions.
• Environment not supported / can proceed—Either your Oracle version or your operating system version is not supported. In most cases, a supported version of Oracle is running on an unsupported operating system version. Although you can proceed with the installation, you may have problems.

To instruct the Server Agent to restart automatically after a server restart

If you want the Server Agent to start automatically each time the server is started, perform the following steps:

1. Log in to UNIX or Linux as root.

2. Change to the agent installation directory using the following command:

   # cd /$ORACLE_HOME/Quest/QSA/SID/inst

3. Run the following root.sh script:

   # ./root.sh

For more information about installing and upgrading Space Manager, the Server Agent, and server objects, see the Space Manager Installation Guide at Quest Software Technical Documentation .

Related Topics

QSA Server Agent Parameters

Install Server Agent on Windows

This section describes how to install the Server Agent on a local or a remote Windows server:

• Local server—A server is local if it resides on your Space Manager client computer. When a server is local, you must work from the client computer to install the Server Agent. It must be installed on a local drive.
• Remote server—A server is remote if it does not reside on your Space Manager client computer. When a server is remote, you should work from the server to install the Server Agent.

Install the Server Agent using the same DBA account used to install the server components. For information about installation DBA account requirements, see Space Manager User Requirements.

Prerequisites

• For installation on either a local or a remote Windows server, the installation Oracle DBA must have all permissions for the agent installation folder.
• On a remote server, the folder must be shared or copied to the server.

Note: If upgrading the server agent, perform the upgrade when no scheduled scripts are executing or about to execute.

Install the Agent on a Local Server

Use the following procedure to install QSA in a database on a local Windows server.

To install (or upgrade) the Server Agent on a local Windows server

1. Run the Space Manager client and connect to the target database using the DBA account that installed the Space Manager server components.

   Note: If you installed (or upgraded) the server components, the Server Agent Installer opens automatically after component installation is finished. Skip ahead to step 4.

2. To run the QSA Installer, select Tools | Admin | Quest Server Agent | Manage Quest Server Agent Installation.
3. (Upgrade only) If you are upgrading QSA, the Select Installation Type window displays. Select Upgrade Quest Server Agent and click Next.
4. In the Oracle Connection Info window, review the information. If necessary, complete or modify any fields. Click Next. If you are upgrading, you can only edit the staging directory path in this window.
5. In the Install Quest Server Agent window, click Install to install QSA. In the Agent Installation Complete window, click Next.
6. In the QSA Parameters window, specify values for QSA parameters or use the default values. Values apply to the target database. You must enter values for WORKDIR (used for FastCopy/DBMS_DataPump) and LW_TABLESPACE (used for live reorganizations and required even if LiveReorg is not licensed). Click Next when finished. See QSA Server Agent Parameters for more information.
7. In the Installation Finished window, click Finish to exit the QSA Installer.

Note: Before the Server Agent is installed, you may encounter one of the following messages:

• Files not current—The agent installation files are either not available or not current. Exit the Server Agent Installer, install the most recent Space Manager client. New agent files are copied to Server Agent folder on the client computer. You can then install the agent.
• Environment not supported / cannot proceed—Both your Oracle version and operating system version are not supported. The agent cannot be installed. You must upgrade to a supported Oracle version and a supported operating system. See the Space Manager Release Notes for a list of supported Oracle Database and Operating System versions.
• Environment not supported / can proceed—Either your Oracle version or your operating system version is not supported. In most cases, a supported version of Oracle is running on an unsupported operating system version. Although you can proceed with the installation, you may have problems.

Install the Agent on a Remote Server

To install QSA on a remote Windows server, you must copy the QSA installer from the Space Manager application directory to the Windows server.

To manually install QSA on Windows, see "Manually Install and Uninstall the Server Agent on Windows" in the Space Manager Installation Guide.

Note: Best practice is to install locally. During remote installation, if you encounter problems or error messages such as “QSA-20375: Cannot install the daemon.” or “Network path not found” use the local install procedure.

To copy the QSA Installer to remote Windows server

1. Navigate to the Space Manager client application directory:
   • In Windows Explorer, navigate to: C:\Program Files\Quest Software\Space Manager <version number>
2. Open the QuestServerAgent folder and copy QSA_version_build-QSASetup.exe to the Windows server.

To install the Server Agent on a remote Windows server

1. After copying the Server Agent installer (QSA_version_build-QSASetup.exe) to the Windows server, double-click QSA_version_build-QSASetup.exe to run it.
2. Setup will extract the files in temporary folder / Directory and GUI installer opens automatically.
3. In the Connect to Oracle Database window, enter the service name of the target database and connect using the DBA account that installed the Space Manager server components.
4. Follow the instructions in the previous section, “Install the Agent on a Local Server,” beginning with step 3.

5. After installation, from the Windows Services window, verify that QSA is running. If Started does not display as the QSA status, start the agent from the Services window or run the QSAStart.cmd from the \bin folder under the agent installation folder (<installation path>\Quest Server Agent\<ORACLE_SID>\bin).

   Tip: If the agent is installed for more than one database on the server, look for the “Quest Server Agent” name that includes the target database SID.

For more information about installing and upgrading Space Manager, the Server Agent, and server objects, see the Space Manager Installation Guide at Quest Software Technical Documentation .

Uninstall Server Agent

The Server Agent must be uninstalled individually from each database for which it is installed. It must be uninstalled by the user that installed it.

Note: If you used the QSA Installer or the manual install method to install the agent, use the same method to uninstall it.

Uninstall QSA from UNIX or Linux

This section describes how to uninstall QSA from an Oracle database on a UNIX or Linux server with the QSA Installer. You can use the QSA Installer if you have both SSH and SFTP access to the database server. If you do not have both, you must use a manual procedure. See "Manually Uninstall Server Agent from UNIX or Linux" in the Space Manager Installation Guide for more information.

To uninstall the agent from UNIX or Linux

1. Run the Space Manager client and connect to the target database as the DBA that installed QSA.

   Note: After uninstalling the server components, the Server Agent Installer automatically opens to the Log on page. Skip ahead to step 4.

2. To run the QSA Installer, select Tools | Admin | Quest Server Agent | Manage Quest Server Agent.
3. In the Select Installation Type window, select Remove Quest Server Agent, and then click Next.
4. In the Log on to Server window, enter the user name and password for the UNIX or Linux account that installed the agent. Enter the host server name if it is not displayed. Click Next.
5. In the Uninstall Quest Server Agent window, click Remove.
6. In the Installation Finished window, click Finish to exit the QSA Installer.

7. If you did not uninstall QSA as root, log into the server as root and run the ROOT_UNINSTALL.SH script as follows. Use SID for the target database.

   # /tmp/root_uninstall.sh SID

Uninstall QSA from Windows

This section describes how to uninstall the Server Agent from a local or remote Windows server.

Note: The agent must be running when you uninstall it from a Windows server. You can start the agent from the Windows Services window, or run QSAStart.cmd in the \bin folder under the agent install folder (<installation path>\Quest Server Agent\<ORACLE_SID>\bin).

To manually uninstall the Server Agent from Windows, see "Manually Uninstall Server Agent from Windows" in the Space Manager Installation Guide.

Local Windows Server

To uninstall QSA from a local Windows server, you can run the Server Agent Installer from the Space Manager application.

To uninstall QSA from a local Windows server

1. Run the Space Manager client and connect to the target database as the DBA that installed QSA.

   Note: After uninstalling server components, the Server Agent Installer automatically opens. Skip ahead to step 3.

2. To run the QSA Installer, select Tools | Admin | Quest Server Agent | Manage Quest Server Agent.

3. In the Select Installation Type window, select Remove Quest Server Agent, and then click Next.
4. In the Uninstall Quest Server Agent window, click Remove.
5. In the Installation Finished window, click Finish to exit the QSA Installer.

Remote Windows Server

To uninstall QSA from a remote Windows server, you must copy the Server Agent Installer from the Space Manager application directory to the Windows server. (Installing QSA on the remote Windows server also required copying the Server Agent Installer to the Windows server.)

To copy the QSA Installer to remote Windows server

1. Navigate to the Space Manager application directory:
   • In Windows Explorer, navigate to: C:\Program Files\Quest Software\Space Manager <version number>
2. Open the QuestServerAgent folder and copy QSA_version_build-QSASetup.exe to the Windows server.

To uninstall QSA from a remote Windows server

1. Log in to the remote Windows server as a member of the Windows Administrators Group.
2. After copying the Server Agent installer (QSA_version_build-QSASetup.exe) to the Windows server, double-click QSA_version_build-QSASetup.exe to run it.
3. Follow the instructions in the previous section, “To uninstall QSA from a local Windows server” beginning with step 3.

Related Topics

Uninstall (Remove) Server Objects