Chat now with support
Chat mit Support

Space Manager with LiveReorg 9.1 - Installation Guide

Architecture and Requirements


Space Manager with LiveReorg® includes a Windows client, server components, and the Server Agent, a script execution engine. It also includes demonstration data, which you can use to explore Space Manager functionality using simulated objects and tablespaces.

You can manage multiple Oracle® databases from a single Space Manager client. Server components and the Server Agent must be installed for each database you plan to manage. Server components are normally installed for one database at a time. To install them for multiple databases simultaneously, create a shell script to run the manual install script.

Space Manager Client

The Space Manager client is a graphic user interface designed to let you easily and efficiently manage space in Oracle databases.

Space Manager Server Components

Space Manager server components include objects, views, and packages. Space Manager tables store scheduled scripts and the statistics collected by Space Manager. The script and statistics tables comprise the Space Manager repository. The repository is located in the tablespace specified during installation of server components.

Space Manager includes the Find Long LONGs package that works in conjunction with the Reorg Manager reorganization wizard. The Find Long LONGs package allows you to find tables with LONG or LONG RAW columns that are larger than 32,760 bytes (long LONGs). Populate the Find Long LONGs table before you run the Reorg Manager.

Server Agent

The Server Agent is a script execution engine that Space Manager uses to run reorganization, repair, and statistics collection scripts from the database server on a scheduled basis. The agent must be used to run live reorganization scripts and scripts that use FastCopy, FSCopy, or parallel agent processes. Scripts are automatically run by the agent when they are scheduled and stored in the Space Manager repository.

The agent is started when it is installed. It then runs continuously. On UNIX® and Linux®, the agent runs as a daemon. On Windows®, it runs as a service. The agent uses one connection for itself. It establishes additional connections for each script it runs and for each parallel process it uses.

You can stop and start the agent from the Space Manager Tools menu and the Scripts/Job Monitor.

Note: Before you upgrade to a major new version of Oracle, uninstall the agent. After the new Oracle database is installed, reinstall the agent. This ensures that the agent uses the correct files for the new version of Oracle.

Demonstration Data

Demonstration data comprises objects and tablespaces that are subject to the space-use problems found in a typical database. You can use it to learn how Space Manager detects and resolves problems. After you resolve problems, you can refresh demonstration data to restore its original condition.

Installation of demonstration data is optional. It requires 20 MB or 24 MB of disk space, depending on your default database block size. The demo user is the owner of all demo objects.

Note: Demonstration data functions are only enabled for database administrators.

System Requirements

Refer to the Space Manager with LiveReorg® Release Notes for the most up-to-date Client, database, and Capacity Manager repository requirements. Before installing Space Manager and Capacity Manager, ensure that your system meets the minimum hardware and software requirements.

User Requirements

This section describes the privileges required to install Space Manager server components and to run Space Manager.

Server Objects Installation

To install Space Manager server components, you must have the DBA role and full privileges for the target database. (Do not use SYS or SYSTEM.) Your user name must not require double quotes.

Note: In an Oracle database, the server objects and Server Agent must be installed by a common user with DBA privileges on all containers. See Installation DBA in Oracle 12c and 19c.

The DBA account that installs the Space Manager server objects (components) owns the objects. This same DBA account must be used to upgrade and uninstall the server components (which include Space Manager objects).

The DBA account used to install the server components should also be used to install the Server Agent.

The privileges needed to run FND_STATS as a non-APPs user are automatically granted during installation of Space Manager server components. Any user with the DBA or QUEST_SPC_APP_PRIV role can run FND_STATS from Space Manager.

Installation DBA in Oracle 12c and 19c

In an Oracle database, the server objects and Server Agent must be installed by a common user with DBA privileges on all containers. This account must be created prior to installation of the server objects and Server Agent.

  1. In the Oracle root container, using a common user account such as SYS or SYSTEM, create another common user account to be used for installing server objects (and Server Agent).
  2. Grant the new common user account DBA privileges across all containers. For example, use a grant statement such as the following:

    grant dba to c##<user> container = all;

Privileges and the O7_DICTIONARY_ACCESSIBILITY Parameter

When Oracle’s O7_DICTIONARY_ACCESSIBILITY initialization parameter is set to FALSE for a target database, the following requirements must be met:

  • The installation DBA must have the EXECUTE on SYS.DBMS_SYS_SQL privilege. During installation, the installation DBA is prompted to log in using a SYSDBA account and then run scripts to grant this privilege.
  • If the target database does not allow remote login by users with the SYSDBA privilege, the installation DBA must have remote database administration capability. This capability must be granted prior to installation.
    1. First, create an authentication password file for the target database.
    2. Second, set the REMOTE_LOGIN_PASSWORDFILE parameter to EXCLUSIVE for the DBA account you plan to use as the user for Space Manager server components.

Server Agent Installation

The Server Agent must be installed by user accounts with sufficient privileges. The agent must be upgraded, configured, and uninstalled by its installation account. On UNIX and Linux servers, the agent is installed by an operating system account and an Oracle DBA. On Windows servers, the agent is installed by an Oracle DBA.

Note: In an Oracle database, the server objects and Server Agent must be installed by a common user with DBA privileges on all containers. See Installation DBA in Oracle 12c and 19c.

UNIX and Linux Privileges

To install the agent on UNIX or Linux, you must have READ, WRITE, and DELETE privileges for the installation directory. During installation, the user connects to the database server host using SSH. The user needs privileges similar to the operating system user that installed Oracle.

Oracle Privileges

To install the agent on Oracle, you must have the UNLIMITED TABLESPACE system privilege and full privileges for the target database. (Do not use SYS or SYSTEM.) To install the agent on Windows, you must have all permissions for the agent installation folder.

On all supported platforms, the installation DBA must have the EXECUTE privilege on:


Normally, EXECUTE privileges are granted as part of the DBA role or during Server Agent installation. If the privileges cannot be granted during installation or if they are revoked, the agent does not run correctly. To fix the problem, grant the missing privileges to the installation DBA.

The installation DBA connects to the target database when QSA is installed. It also automatically connects the agent to the database each time the system is started.

Note: Use the same DBA account to install Space Manager server components and the Server Agent. The same account is automatically used when you run the Server Agent Installer from Space Manager immediately after server components are installed.

Running Space Manager

Space Manager can be run by DBA users and by non-DBA users that have the QUEST_SPC_APP_PRIV role. This section describes how to grant the QUEST_SPC_APP_PRIV role from Space Manager.

To grant privileges from Space Manager

To grant privileges from Space Manager, the installation DBA runs the following procedure in the SQL Editor (in the procedure, ‘USER NAME’ is the user name of the user being granted privileges):


quest_spc_user_manager.grant_user (‘USER NAME’);


The procedure should be run for non-DBA users that will run Space Manager. The procedure grants the QUEST_SPC_APP_PRIV role and additional privileges to non-DBAs. It grants only the QUEST_SPC_APP_PRIV role to non-installation DBAs.

Note: Privileges must be granted after each upgrade, as well as after the initial installation.

Knowledge Base
Benachrichtigungen und Warnmeldungen
Technische Dokumentationen
RSS Feed
Unterstützung bei der Lizenzierung
Technische Support
Alle anzeigen
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen