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 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.
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.
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.
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
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 .
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.
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 .
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.
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
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.
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
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.
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
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.
To run the QSA Installer, select Tools | Admin | Quest Server Agent | Manage Quest Server Agent.
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
To uninstall QSA from a remote Windows server
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center