Global Operations Requirements
This section describes what is required to install Space Manager and QSA in non-English configurations such as those used outside North America.
Note: See the online help to learn all the requirements for non-English operation of Space Manager.
User Name and Password Requirements
The users that install Space Manager and QSA for non-English operation must meet the following requirements:
- The user name and password of the installation DBA must conform to Oracle guidelines.
- The user name and password of the installation DBA must use characters that can be converted between your client computer character set and your database character set.
- The user name of the installation DBA must not be in double quotation marks (“x”).
- The user name for QSA’s operating-system account on UNIX or Linux must use ASCII characters.
Character Set Requirements for Agent Installation
When QSA is installed in a non-English configuration, the configuration must meet the following character-set requirements:
| Host name for database server |
Must be a DNS name; IDN names are not supported |
Must be a DNS name; IDN names are not supported |
| Service name for database |
Can use database character set or ASCII |
Can use database character set or ASCII |
| User name for Oracle DBA that installs the agent |
Can use database character set or ASCII |
Can use database character set or ASCII |
| Password for Oracle DBA that installs the agent |
Can use database character set or ASCII |
Can use database character set or ASCII |
| User name for operating system user that installs the agent |
Must use ASCII |
No character-set requirement |
| Password for operating system user that installs the agent |
Must use ASCII |
No character-set requirement |
| Tablespace names for agent table and LW_TABLESPACE |
Can use database character set or ASCII; names must not require double quotes |
Can use database character set or ASCII; names must not require double quotes |
| Install directory and path for agent |
Must use ASCII |
Must use ASCII |
| Workdir directory and path for FastCopy |
Must use ASCII |
Must use ASCII |
| Overflow directory and paths for FastCopy |
Must use ASCII |
Must use ASCII |
Installation Overview
Overview - Installation Process
This chapter provides an overview of the Space Manager installation process. It also includes a Smart Start that lists the major steps in the process.
A complete installation of Space Manager includes the Space Manager client, Space Manager server components, and the Server Agent.
- Space Manager client—The Space Manager client is installed on a Windows computer using the Space Manager setup program. The client is available on SupportLink and on the CD.
- Space Manager server components—The server components are installed using the GUI install program that you can launch from the client. You should install the components in each database you plan to manage with Space Manager. The install program starts automatically the first time you connect with the client to a target database. You can run it at any time using the Reinstall Server function accessible from the client main menu. When you install server components, you can also install demonstration data.
- Quest Server Agent—The server agent is installed using the Server Agent Installer. You should install the agent for each database where Space Manager server components are installed. The Server Agent Installer starts automatically after the server components (or demonstration data) are installed. You can run it at any time by selecting Tools | Admin | Quest Server Agent | Manage Quest Server Agent from the client main menu.
Note: Before you install QSA in an OPS or RAC active-active environment, see Install Server Agent on OPS or RAC.
Smart Start
If this is your first time installing Space Manager, start here! This section outlines the basics steps to install the Space Manager desktop application, the server components, and the server agent.
Click the links provided for each step to see detailed information.
- Prepare for installation. Review the following before installing:
- System requirements—Make sure all system requirements are met. For example, make sure all required Oracle packages are installed and valid for each target database. If the LiveReorg option is licensed, make sure Oracle’s partitioning option is installed. See the System Requirements section of the Space Manager with LiveReorg Release Notes.
- tnsnames.ora—Make sure the tnsnames.ora file on the Space Manager client computer contains service names for all databases to be managed with Space Manager.
- OPS or RAC active-active—If you plan to run Space Manager in an active-active OPS or RAC environment, see Install Server Agent on OPS or RAC. QSA should be installed on only one instance for a cluster database. You need to connect to this instance when you run Space Manager for that database or install or update QSA.
- O7_DICTIONARY_ACCESSIBILITY—Check the setting for this initialization parameter in each target database. If the parameter is set to FALSE and a database does not allow remote login by users with the SYSDBA privilege, grant the installation DBA remote database administration capability. See Space Manager User Requirements for more information.
- Choose installation user accounts. Choose installation users for Space Manager server components and QSA for each target database. Server components must be installed by an Oracle DBA with full privileges for a target database. (Do not use SYS or SYSTEM.) See Space Manager User Requirements for more information. QSA must be installed by Oracle, UNIX, or Linux users with sufficient privileges. Use the same DBA account to install both the server components and the server agent.
-
Choose tablespaces. Choose or create a tablespace for Space Manager tables and indexes. During installation of server components, you have the opportunity to select the tablespace. It must have a standard name. For an upgrade, it must have enough free space for temporary copies of statistics and analysis-group tables. The copies are created for recovery purposes and dropped when an upgrade is successfully completed.
Also choose or create tablespaces for QSA’s permanent objects and temporary LiveReorg objects. The tablespace chosen for Space Manager objects is recommended for the agent’s permanent objects. A separate tablespace is recommended for LiveReorg objects. During installation of the agent, you have the opportunity to select agent tablespaces. The LiveReorg tablespace is specified with the LW_TABLESPACE parameter. It must be specified even if LiveReorg is not licensed.
Note: SAP users should use SAP administrative tools to create tablespaces for Space Manager and QSA.
- Install the Space Manager client. To install the Space Manager client on a Windows computer, use the installation executable available from SupportLink. See Install Space Manager Client for more information.
- Install Space Manager server components. The first time you connect to a database from the Space Manager client, you are prompted to install Space Manager server components. Connect as the Oracle DBA chosen to install both the server components and the server agent. See Install or Upgrade Server Objects for more information.
- Install demonstration data (optional). After server components are installed, you can install demonstration data for a target database. See Install or Upgrade Server Objects for more information.
- Install the Server Agent. The Server Agent Installer displays automatically after server components or demonstration data are installed. It is used to install QSA for a target database. The Oracle DBA that installed server components also installs the agent. The same DBA account should be used for both. See Overview - Install Server Agent for more information.
- Grant privileges to non-DBA users. To allow non-DBA users to use Space Manager for a target database, grant them the QUEST_SPC_APP_PRIV role. See Running Space Manager for more information.
-
Run the Find Long LONGs procedure for a target database. The Find Long LONGs EXECUTE procedure identifies tables that contain LONG or LONG RAW columns that are larger than 32,760 bytes. The size of LONG columns determines which data-movement method can be used for their tables during reorganization.
Note: After you upgrade Space Manager, you can run stored statistics collection scripts generated with an earlier version. However, you should not run stored reorganization and repair scripts generated with an earlier version. Instead, generate new reorganization and repair scripts with the new version.
