Chatta subito con l'assistenza
Chat con il supporto

Space Manager with LiveReorg 9.2 - Release Notes

Known Issues

The following is a list of issues known to exist at the time of this release.

Feature Known Issue and Workaround (if applicable) Defect ID
General When running the Space Manager client (64-bit) in a 64-bit environment, some users might encounter the following error when attempting to submit a standard or live reorg script: “Error creating script group: Could not load file or assembly ManagedQP5.dll or one of its dependencies. is not a valid Win32 application.” SPC-409
Domain Indexes

Reorganizing tables with Domain indexes. Space Manager provides limited support for Domain indexes when performing reorganizations and warns that you might encounter a problem because of the Domain index. Space Manager scripts the reorganization of the domain index correctly. However, the underlying implementation of the index type may be very complex, and some unforeseen dependencies may cause runtime errors.

Important: It is recommended that you test the reorganization of a table with a Domain index on a non-production version of the table to make sure Space Manager reorganizes both the table and index correctly before you reorganize your production table. 

N/A

Installation

Error when installing QSA on Windows for Oracle Database 12cR2. Some users might encounter an "Error running setup" error after attempting to install the QSA Server Agent on Windows for Oracle Database 12c R2. Workaround: If you encounter this issue, contact Quest Support for assistance.

 SPC-491
Live Reorg

Error when running Live Reorg on Oracle Database 12cR2 in Windows. Some users might encounter the following error when attempting to run a Live Reorg script on Oracle 12c R2 in a Windows environment: "350: Aborted QSA - 20391 ORA - 01403 during internal SQL." Workaround: If you encounter this issue, contact Quest Support for assistance.

 SPC-493
Object Properties Attempting to open the Object Properties dialog for a recently-created partitioned table using a Direct connection type resulted in an error.

SPC-482

Partitioning Wizard After creating a table partitioned by range with a global index, using the Partitioning Wizard to change the partitioning method from range to hash unexpectedly changed to the index's locality to local.

SPC-483

System Requirements

Before installing Space Manager and Capacity Manager, ensure that your system meets the following minimum hardware and software requirements.

Requirements for the Client Computer

The Space Manager client must be installed on the same computer, and their requirements are the same unless otherwise specified. The computer must meet the following requirements:

Item Requirement
Oracle® Client

Oracle Net version 11g, 12c , and 19c

Note: The bitness (architecture) of the Oracle client must match the bitness of the Space Manager application.

Operating System
  • Windows 10
  • Windows 11
  • Windows Server 2016
  • Windows Server 2022

Note: The Space Manager client is tested on Windows Server 2022 with the QSA Agent and Oracle 19c hosted on AIX 7.2, and AIX 7.3.

Processor 1 GHz Processor (recommended minimum)
Memory 2 GB of RAM
Display Settings A resolution of 1024 x 768; true color or high color; small fonts
Disk Space

Space Manager: Approximately 800 MB

.NET Framework

Microsoft® .NET Framework 4 (including update 4.0.3)

Note: The .NET Framework 4 Full Profile is required. The Client Profile is not sufficient.

Requirements for Databases

Each database being managed with Space Manager must meet the following requirements:

Item Requirement
Oracle Database

  • Oracle 12c Release 2

    Additional Requirements for Oracle 12c Release 2: To be supported by Space Manager, an Oracle 12c Release 2 database is required to have the following sqlnet.ora profile parameter values specified:

    SQLNET.ALLOWED_LOGON_VERSION_CLIENT = 8

    SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8

    See "Additional Requirements for Oracle 12c Release 2" below for more information.

  • Oracle 19c

Notes:

  • Space Manager supports Oracle Enterprise Edition and Standard Edition databases.
  • Space Manager does not support Oracle databases which use Oracle Database Vault.
Database Server Operating System

Space Manager supports the following operating systems:

  • Oracle Solaris 11 and 11.1
  • IBM® AIX 7.1, 7.2, and 7.3
  • Red Hat® Linux Advanced Server 7.4 (64 bit)

  • Red Hat® Enterprise Linux 8.4 and 8.6 (64 bit)

  • Windows 11

  • Windows Server 2016 Datacenter (64 bit)

  • Windows Server 2022 (64 bit)

Disk Space

Disk-space requirements are:

  • 80 MB for statistics tables
  • 20 MB for scripts tables
  • 20 MB contiguous free space for LiveReorg objects in the LiveReorg tablespace (set with QSA’s LW_TABLESPACE parameter)
  • 40 MB in the filesystem for QSA executables and logs
Oracle Packages

Space Manager: DBMS_SQL, DBMS_PIPE, DBMS_LOCK, DBMS_SPACE_ADMIN

QSA: DBMS_SQL, DBMS_PIPE, DBMS_OUTPUT, DBMS_APPLICATION_INFO

Find Long LONGs feature: UTL_RAW

Email notifications: UTL_SMTP

Oracle's Partitioning Option

Required for the Online Switch (a feature available for live reorganizations) and the Partitioning Wizard; Partitioning Option must be installed and licensed.

XDB Schema

Required for XMLType datatypes.

Additional Requirements for Oracle 12c Release 2 and Oracle 19c

Before installing the server components (and QSA), specify a password version for the database by performing the following procedure.

  1. First, to verify that this procedure is necessary for the target database, run the following query:

    select username, password_versions

    from dba_users

    where username = 'SPACER'

    Note: Username is the installation DBA.

  2. If results returned include "10G, 11G, 12c" in the PASSWORD VERSIONS column, then this procedure is not necessary for this database.
  3. If results do not include 10G, you must perform this procedure for the target database.
  4. Open the SQLNET.ORA file for the target database.

  5. Enter the following:

    SQLNET.ALLOWED_LOGON_VERSION_SERVER=8

    SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8

    BEQUEATH_DETACH=YES

  6. Save the SQLNET.ORA file.

  7. Add the below command in the listener.ora file.

    USE_SID_AS_SERVICE_<oracle-sid>=on

  8. Stop and restart the listener. Use the following commands:

    lsnrctl stop

    lsnrctl start

    The listener may take a few minutes to fully restart.

  9. Alter the password for the installation DBA to a temporary password and then back again to reset it, for example:

    alter user spacer identified by X;

    alter user spacer identified by spacer;

  10. Reset the sys password using alter, for example:

    alter user sys identified by syspassword;

  11. Now run the query again to verify the change.

    select username, password_versions

    from dba_users

    where username = 'SPACER'

    Note: Username is the installation DBA.

  12. You can also verify the change for the sys user.

    select username, password_versions

    from dba_users

    where username = 'SYS'

  13. If results returned from the queries include "10G, 11G, 12c" in the PASSWORD VERSIONS column, the password version was successfully set.

For additional information, see the Oracle documentation: https://docs.oracle.com/database/121/NETRF/sqlnet.htm#NETRF2010.

Requirements for the Capacity Manager Repository

Note: Capacity Manager is not available in a 64-bit version at this time and is not included in the 64-bit installer.

The database used for the Capacity Manager repository must meet the following requirements:

Item Requirement
Oracle Database

Supported for the repository: Oracle 12c

Disk Space

8 MB recommended per monitored database assigned to a repository (accommodates one year of growth in repository objects)

Job Scheduler

One of the following schedules is needed for snapshot jobs, report scheduling, and Windows scheduling:

  • Oracle DBMS_SCHEDULER is used for scheduling snapshot jobs.
  • A third-party job scheduler can be used instead of an Oracle DBMS package.
Oracle Initialization Parameters

Oracle initialization parameters should be set as follows:

  • OPEN_LINKS—The value for OPEN_LINKS initialization parameter should be equal to or greater than the number of monitored databases assigned to a repository. The default value for this parameter is 4; the maximum is 255.
  • JOB_QUEUE_PROCESSES—For optimal performance of snapshot jobs, the value for the JOB_QUEUE_PROCESSES initialization parameter should be equal to or greater than the number of monitored databases assigned to a repository. The maximum is 1,000.
Character Set

Must be a superset of the character sets for all monitored databases. A UTF8 character set is recommended.

Activity Level

Light activity level.

Product Licensing

To activate a trial license

  1. In the License Key dialog, enter your Authorization Key.

  2. Enter the Site Message included with your Authorization Key.

To activate a purchased commercial license

  1. In the License Key dialog, enter your Authorization Key.

  2. Enter the Site Message included with your Authorization Key.

Note: License validation will happen in Space Manager, QSA independently will not authorize the license key.

Getting Started

Contents of the Release Package

Space Manager with LiveReorg 9.2 and Capacity Manager for Oracle 1.4 include the following documentation:

  • Space Manager online help and user guide

  • Capacity Manager online help

Note: The Installation Guide and Release Notes are not included in the setup executable and need to be downloaded separately. These documents are also available from the Quest Software Support Portal.

Installation Instructions

The clients for Space Manager with LiveReorg 9.2 and Capacity Manager for Oracle 1.4 can be installed together using the Installer.

Note: Capacity Manager is not available in a 64-bit version at this time and is not included in the 64-bit installer.

The installer is identified as the Space Manager with LiveReorg 9.2 Installer. The executable for the installer is available at our Support Portal at https://support.quest.com/ and on the installation CD for Space Manager with LiveReorg.

After installing the Space Manager client, you install server components and the QSA Server Agent. Each database you plan to manage with Space Manager must have server components and an agent. Job scheduling and LiveReorg require an agent. After installing the Capacity Manager client, you install the repository and assign monitored databases to the repository. Each database you plan to manage with Capacity Manager must be assigned to the repository.

QSA Server Agent version 8.5 is included in this release of Space Manager with LiveReorg 9.2.

Refer to the Space Manager with LiveReorg Installation Guide for more information about installing Space Manager.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione