Space Manager with LiveReorg

Database capacity optimization in Oracle databases

Deliver capacity optimization, Oracle reorganization and peak performance with ease.

Space Manager with LiveReorg™ enables you to reorganize Oracle data, optimize I/O performance, and maximize database capacity. You can prevent application and database downtime by performing online Oracle reorganizations to reclaim space.  The Oracle partitioning tool also allows you to resolve performance issues due to fragmentation when archiving Oracle data. You’ll find this especially useful for business-critical ERP applications, such as Oracle e-Business Suite, Siebel and SAP, where high-transaction volumes require you to routinely archive data.

Features

Oracle reorganization and space reclamation

  • Reorganizes data to reclaim your wasted space and optimize your database capacity and performance on archived tables, eliminating the need to buy additional disk space.
  • Prevents your organization from experiencing application and database downtime by performing online reorganizations.
  • Determines indexes and tables to reorganize data. Enables you to perform proactive analysis and planning by reclaiming maximum space and tracking historical reorganization activity.
  • Supports multiple datatypes and objects for standard and live reorgs, including individual partitions, domain indexes, user-defined datatypes, and tables with both LOB datatypes and LONG columns.
  • Automatically resumes script execution from point of failure or clean up of residual objects by providing restart and clean-up capabilities for failed reorganization scripts.

Database capacity optimization

  • Using simple charts, easily view existing space usage and future growth in databases that use the same storage resources.
  • Estimate your organization’s future storage needs based on detailed trend charts showing historical growth rates, as well as hypothetical “what if” scenarios.
  • Quickly determine where to utilize space more efficiently with alerts on emerging issues, such as limited free space or space reclamation opportunities.

Oracle partitioning

  • Use a built-in partitioning wizard to minimize downtime by partitioning objects live, while users and applications remain online.
  • Partition, repartition, and remove/add/modify partitions to identify best fit for data access to data.
  • Confirm that you have sufficient space available to ensure reorg success with multiple automatic space-check audits.

Specifications

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 and Capacity Manager clients must be installed on the same computer, and their requirements are the same unless otherwise specified. The computer must meet the following requirements:

Oracle client

Supported by both Space Manager and Capacity Manager:

  • Oracle SQL*Net version 2.1 minimum (32-bit)
  • Oracle Net version 9.2, 10g, and 11g

Space Manager also supports Oracle Net 8.1.7. Capacity Manager also supports Instant Client.

Operating system

Supported by both Space Manager and Capacity Manager:

  • Windows Server 2003
  • Windows XP
  • Windows Vista (FDCC compliant)
  • Windows Server 2008
  • Windows 7
  • Citrix Metaframe XP
ProcessorPentium IV Processor
Memory512 MB of RAM minimum; 1 GB recommended
Display settingsA resolution of 1024 x 768; true color or high color; small fonts
Disk space

Space Manager: Approximately 600 MB

Capacity Manager: Approximately 13 MB

.NET FrameworkMicrosoft .NET Framework 2.0

Requirements for databases

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

Oracle database

Supported by both Capacity and Space Manager:

  • Oracle 9.2
  • Oracle 10.2
  • Oracle 11g
  • Oracle 11g R2

Note: Space Manager supports Oracle Enterprise Edition and Standard Edition databases.

Database server operating system

Space Manager supports the following operating systems:

  • HP-UX 11 and 11i on PA_RISC
  • HP-UX 11i on Itanium
  • Sun Solaris 2.8, 2.9, and 10
  • IBM AIX Version 5.1, 5.2, 5.3, and 6.1
  • Red Hat Linux Advanced Server 3.0, 4.0, and 5.1
  • Oracle Linux 4 and 5
  • Oracle Linux 5 with Unbreakable Enterprise Kernel
  • SuSE Linux Enterprise Server 9 and 10
  • Windows 2000 Server and Windows Server 2003 and 2008

Note: When using Oracle 11.1 or earlier on 64-bit systems, the installing user must be configured to use the Oracle 32-bit client libraries. For Oracle 11.2 or later on 64-bit systems, the installing user can use the Oracle 64-bit client libraries.

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.

Requirements for the Capacity Manager epository

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

Oracle database

Supported for the repository:

  • Oracle 9.2
  • Oracle 10.2
  • Oracle 11g
  • Oracle 11g R2
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_JOBs is used for scheduling snapshot jobs on Oracle8i and Oracle9i.
  • Oracle DBMS_SCHEDULER is used for scheduling snapshot jobs on Oracle10g.
  • 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—The value for the JOB_QUEUE_PROCESSES initialization parameter should be greater than zero in Oracle 9.2 databases. For optimal performance of snapshot jobs, it 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.

Language supported:

  • US English

Screenshots

loading

Datafile map’s segment-type view

Datafile map’s segment-type view

See where data and segments with blocking extents are. Identify a reorganization candidate and launch the reorg manager directly from the datafile map.

Datafile map’s reorg-need view

Datafile map’s reorg-need view

Easily see which segments need reorganization. Change the threshold values indicating reorg need severity to match your organization’s requirements. Use the information in the segments-with-blocking-extents panel for datafile-level space reclamation opportunities.

Explorer window

SQL procedure debugger

Easily view multiple databases and their tablespaces. Quickly view space distribution, database statistics, and a list of space-related issues for each database. Launch reorg manager directly from the list to address an issue.

Explorer

Explorer

Quickly view segment lists and statistics for each tablespace. Easily determine which segments have the greatest reorg need per tablespace.

Explorer

Explorer

Easily navigate between database, tablespace, datafile, segment, and schema information.

Reporting

Reporting

Space Manager provides several reports to help you quickly identify reorganization candidates and plan future capacity.

Largest segments by tablespace report

Largest segments by tablespace report

Identify the largest segments in each tablespace.

Scripts/job monitor

Scripts/job monitor

Monitor reorg script execution. Easily view the script and log file for each table in a single or multi-table (script group) reorganization.