Space Manager with LiveReorg 8.5 - Installation Guide

Install Server Agent

Overview - Install Server Agent

This chapter describes how to install QSA for Oracle databases on UNIX, Linux, and Windows servers. It also describes agent parameters and best practices to install the agent in an OPS or RAC environment.

You must install QSA in each database you plan to manage with Space Manager. The agent should be installed after Space Manager server components are installed. It must be installed before you can run scheduled scripts.

To install the agent, the QSA Installer uses files that are copied to the Space Manager client computer during client installation. The files are stored in the Quest Server Agent folder under the Space Manager folder.

During agent installation, the QSA Installer determines whether the agent files for your environment are available and current. It also determines whether your database and operating system versions are supported.

Note: Login fields in the QSA Installer are case sensitive. If you enter a user name or password in the wrong case, “logon invalid” displays at the bottom of the installer.

Before Installing the Server Agent

Specify Password Version for Oracle 12cR2 Database

Beginning with Space Manager 8.5, for each Oracle 12c Release 2 database you intend to manage, specify a password version in the SQLNET.ORA file of the target database.

See Overview - Install Server Components for more information.

Set BEQUEATH_DETACH for the Agent

Before you install the Server Agent, set BEQUEATH_DETACH to YES in the SQLNET.ORA file for the target database. If you do this after the agent is installed, stop and start the agent to ensure that the change is recognized.

When BEQUEATH_DETACH is set to NO or is not set for a database, the agent’s job scheduler cannot detect when scripts have been cancelled or aborted. As a result, cancelled and aborted scripts cannot be restarted from Space Manager. If you try to restart a script when BEQUEATH_DETACH is set to NO, one of the errors that might display is:

“QSA-20311: Table conflict with script already executing.”

To set BEQUEATH_DETACH

1. Open the SQLNET.ORA file for the target database. The file is stored in a default directory or one specified with the TNS_ADMIN environment variable. The default directory varies by platform:
   • On UNIX and Linux database servers, the default directory is $ORACLE_HOME/network/admin
   • On Windows database servers, the default directory is ORACLE_HOME\network\admin

2. Change the BEQUEATH_DETACH setting from NO to YES or add the following entry to the file:

   bequeath_detach=yes

3. Save the SQLNET.ORA file.

When to Install/Upgrade/Reinstall the Server Agent

Install the Server Agent After Initially Installing the Client

After initially installing the Space Manager client, install the server components and the Server Agent on each database you intend to manage with Space Manager.

The first time you connect to a database in which Space Manager server components are not installed, you are prompted to install them. After component installation is finished, the Server Agent Installer opens allowing you to install the agent.

Upgrade the Server Agent After Upgrading the Client

You must upgrade the Server Agent when you upgrade the Space Manager client. The first time you connect to a database after upgrading the Space Manager client, you are prompted to upgrade the server components. When component upgrade is finished, the Server Agent installer opens allowing you to upgrade the agent.

Just like the server components, the server agent must be upgraded by the DBA account that installed it. Agent tables are automatically upgraded in the tablespace where they were first installed. Agent executables are automatically upgraded in the installation directory where they are currently installed.

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

Reinstall the Server Agent after Upgrading the Oracle Database

Reinstall the server agent along with the server components after you upgrade to a major new version of Oracle Database. Uninstall the server components and the server agent before upgrading the Oracle database, then reinstall the server components and server agent after upgrading the Oracle database. See Oracle Upgrade for more information.

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

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. Extract the files to a temporary directory.

   Note: Make sure the temporary directory is empty before you extract the files.

3. After the files are extracted, the GUI installer automatically opens.
4. 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.
5. Follow the instructions in the previous section, “Install the Agent on a Local Server,” beginning with step 3.

6. 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.