Overview - Install Server Agent
Install Server Agent on UNIX or Linux
Install Server Agent on Windows
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.
Beginning with Space Manager 8.5, for each Oracle 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.
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
Change the BEQUEATH_DETACH setting from NO to YES or add the following entry to the file:
bequeath_detach=yes
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.
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 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.
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 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
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.
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.
Note: Before the Server Agent is installed, you may encounter one of the following messages:
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:
Change to the agent installation directory using the following command:
# cd /$ORACLE_HOME/Quest/QSA/SID/inst
Run the following root.sh script:
# ./root.sh
This section describes how to install the Server Agent on a local or a remote Windows server:
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.
Note: If upgrading the server agent, perform the upgrade when no scheduled scripts are executing or about to execute.
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
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.
Note: Before the Server Agent is installed, you may encounter one of the following messages:
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
To install the Server Agent on a remote Windows server
Extract the files to a temporary directory.
Note: Make sure the temporary directory is empty before you extract the files.
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.
© ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책 Cookie Preference Center