Space Manager with LiveReorg®
Version 6.6
Release Notes
May 2008
Space Manager with LiveReorg is Quest Software’s solution for optimizing space use and performance in Oracle databases. It provides DBAs with a comprehensive set of tools for making the most of storage resources. These allow you to collect statistics, visualize space use, detect space-use problems, reorganize and resize objects to reclaim wasted space, repair chained rows, create tablespaces, resize datafiles, and partition objects. Space Manager's powerful reorganization functionality makes it possible to reorganize and restructure large, volatile databases while tables are online.
As you manage capacity with Space Manager, you can monitor it with Quest Capacity Manager for Oracle. Capacity Manager is Quest Software's solution for tracking and planning capacity across multiple Oracle databases. Designed to report on collective space use in databases, Capacity Manager lets you evaluate current allocation, forecast future growth, and identify emerging issues. To resolve these issues, you can run Space Manager from Capacity Manager. Launch points are provided throughout the Capacity Manager interface.
Together, Space Manager and Capacity Manager provide the information and control you need to efficiently maintain and plan your database resources. Capacity Manager uses the Space Manager license and can be installed when you install Space Manager.
As of release 6.5, 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 SupportLink. Space Manager with LiveReorg 6.6 includes the following new features:
Reorganization History report: This report documents your reorganization activities for a specific time period, which allows you to effectively plan for future reorganizations and extrapolate space savings based on data from past reorganizations.
Quest Server Agent: There is now a Windows 64-bit version for AMD Athlon 64, AMD Opteron, Intel Xeon with Intel EM64T support, Intel Pentium 4 with Intel EM64T support.
This release also includes a number of enhancements and resolved issues. All are described in the next section. This version works with Capacity Manager for Oracle 1.1 and Quest Server Agent 6.6, a script execution agent. The agent must be used to execute scheduled scripts, live reorganization scripts, scripts with FastCopy (a data movement method), and scripts that include parallel processing by the agent.
Note: Version 6.6 does not support Oracle 8.0.6. Version 6.2 was the last version of Space Manager with LiveReorg that supported Oracle 8.0.6.
The following is a list of issues addressed and enhancements implemented in Space Manager with LiveReorg 6.6.
|
Feature |
Resolved Issue |
Defect ID |
| Reports | Benefit reports: Enhancements to
the Predicted Reorganization Benefit report include:
|
ST#45885 |
| Reorg Manager | Switch types: The switch type selected from the Predicted Reorganization Benefit report now determines the Reorg type. For example, if the user chooses tables with ONLINE as the Method, then Reorg Manager defaults to “Optimize for Availablity” and "Online where available." | ST#45886 |
| Performance: Improved time it takes to open Reorg Manager from Map or Explorer on Oracle 10. | ST#47781 | |
| Table order: The reorganization retains table order so that the scripted order of the tables corresponds to the selection order. | ||
| Attributes: The Cache and Parallel attributes are now changed when requested. | ST#40872 | |
| LiveReorg | Reorganizing IOT tables: Improved scripting of the compare index routine to avoid ORA-20553 errors when reorganizing IOT tables. | ST#40972 |
| Analysis Groups | Temporary indexes: Temporary indexes are now excluded from analysis. | ST#40974 |
| Statistics: Changed the handling of table names when using FND_STATS to avoid ORA-01401 errors. | ST#40971 | |
| Explorer | Tree node: Explorer no longer expands the detail list when you right-click a tree node. In some cases, such as when opening the Tablespace Map for a large tablespace, this reduces both time and memory usage. | ST#40935 |
| Quest Server Agent (QSA) | Log retention: Setting MAX_HISTORY to zero now keeps log files indefinitely. Previously, a setting of zero for this attribute caused the log files to be purged nightly. | ST#43182 |
| Capacity Manger for Oracle | Repository install: Fixed query to avoid "ORA-00959 Tablespace <number> does not exist" error during repository install. | ST#44103 |
The following is a list of issues known to exist at the time Space Manager with LiveReorg 6.6 was released.
|
Feature |
Known Issue |
Defect ID |
| Capacity Manager | ||
| If you upgrade Capacity Manager without uninstalling the previous version, the upgrade may not install the current version. To install the current version; uninstall Capacity Manager (the client only, you do not need to uninstall the repository) and then install the Capacity Manager client again. | ||
| Oracle9i Support | ||
| Tablespaces using Oracle-managed files: When you add datafiles to tablespaces with Oracle-managed files, be aware that Tablespace Properties will automatically put ORA_ at the beginning of each new file name. However, tablespaces using Oracle-managed files can only have one datafile named ORA_%. If you leave ORA_ in place for a new file, the following error will occur when you run the script to add it. “ORA-01276. Cannot add a file with an Oracle Managed Files file name.” To avoid the error, remove ORA_ from the beginning of a new file name before you run the script. | ||
| 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. |
ST#48247
ST#48257 | |
| Reorg History Report | ||
| Application error: The Reorg History
report does not open but displays an error similar to: "Application Error:
The type initializer for "reorgHistoryReport.Utilities" threw an
exception".
Cause: This occurs when the date separator is not a slash. Workaround: Change the date separator to "/" through the Customize Regional option. You can also contact Quest Support to get an updated Reorg History DLL that corrects this problem. |
ST#626593 |
The following describes a third-party issue discovered after Space Manager with LiveReorg 6.5 was released. This issue also relates to release 6.6.
|
Feature |
Known Issue |
| Online Switch Reorg | |
| One of our customers has reported an issue
that can occur if you change the In Row/Out of Row attribute of the LOB
Storage clause when doing an exchange partition. This issue has been
reported to Oracle for further investigation (ST#47529).
To avoid this problem: A modification to Reorg Manager prevents changing the In Row/Out of Row attribute of an LOB column when you use the Online Switch or a Standard Reorg that uses the Exchange Partition.
Tip: Use a T-Lock reorg if you need to change the In Row/Out of Row attribute of a LOB column. |
If you have Space Manager 6.5 with Capacity Manager 1.1 installed, you must uninstall the Capacity Manager client (the repository does not need to be uninstalled) prior to upgrading.
When you upgrade to Space Manager 6.6, you can also install or upgrade to Capacity Manager for Oracle 1.1. The clients for both applications are installed with the Quest Installer. For more information, see Getting Started in these release notes.
After you upgrade the Space Manager client, when you connect to a database with Space Manager server objects already installed. you are prompted to upgrade server components and the Quest Server Agent.
Before installing Space Manager and Capacity Manager, ensure that your system meets the following minimum hardware and software requirements.
The Space Manager and Capacity Manager clients must be installed on the same computer. The computer must meet the requirements below.
| Requirement | Space Manager | Capacity Manager |
| Oracle Client | Supported by both Space Manager and Capacity
Manager:
Space Manager also supports Oracle Net 8.1.7. |
See the Space Manager column. Capacity Manager also supports Instant Client. |
| Operating System | Supported by both Space Manager and Capacity
Manager:
|
See the Space Manager column.
|
| Processor | Pentium III or compatible processor minimum; Pentium IV recommended. | See the Space Manager column.
|
| Memory | 512 MB of RAM minimum; 1 GB recommended. | See the Space Manager column. |
| Display Settings | 1024 by 768 resolution; true color or high color; small fonts. | See the Space Manager column.
|
| Disk Space | Approximately 300 MB | 10 MB |
| .NET Framework | Microsoft .NET Framework 2.0 | See the Space Manager column. |
Each database being managed with Space Manager and monitored with Capacity Manager must meet the requirements below.
| Requirement | Space Manager | Capacity Manager |
| Quest Components | Each database must have Space Manager server components and QSA installed. | Each database must be assigned to a repository. It should be assigned only once to that repository. |
| Oracle Database | Supported by both Capacity and Space Manager:
|
See the Space Manager column. |
| Database Server Operating System | Space Manager supports the following operating
systems:
|
Not applicable for Capacity Manager. However, Space Manager can only be run for monitored databases on the operating systems it supports. |
| Disk Space | Disk-space requirements are:
|
A negligible amount of disk space is needed for the collector package. This collects space-use snapshots from a monitored database. |
| Oracle Packages | Oracle package requirements are:
|
Not applicable for Capacity Manager. |
| 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. | Not applicable for Capacity Manager. |
| XDB Schema | Required for XMLType datatypes in Oracle 9.2 or higher. | Not applicable for Capacity Manager. |
The database used for the Capacity Manager repository must meet the requirements below.
| Requirement | Capacity Manager | Space Manager |
| Oracle Databases | Supported for the repository:
|
Not applicable for Space Manager. Space Manager does not use the Capacity Manager repository. |
| 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:
| |
| Oracle Initialization Parameters |
Oracle initialization parameters should be set as
follows:
| |
| 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. |
This section contains information about installing and operating Space Manager in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation. This release supports any single-byte or multi-byte character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.
Before you run Space Manager for a non-ASCII database, be aware of the following configuration requirements and limitations:
Japanese Windows client computers: The Oracle client must be configured to use an encoding that matches the system default code page for the specific language version of Windows where it is installed. For example, on Japanese Windows, the system active code page is CP932 (Shift-JIS). The corresponding Oracle encoding is JA16SJIS and this encoding must be set in the NLS_LANG variable in the ORA_HOME for the client used by Space Manager. The default installation is normally correct, provided the Regional Options for Windows have not been changed since the Oracle client has been installed. For more information on choosing and setting the NLS_LANG on Windows, see the Oracle Database Globalization Support Guide for your specific version of Oracle.
Windows database servers: When the operating system for the database server is Windows, Space Manager does not support use of JA16EUC as the database character set.
Remote Windows servers: When you install the Quest Server Agent in a database on a remote Windows server (one that does not reside on your Space Manager client computer), you must work directly from the server to perform the installation.
AL32UTF8 and 8.1.7 clients: Space Manager cannot be used in an environment where the Oracle client is version 8.1.7, the Oracle database is version 9i or 10g, and the database character set is AL32UTF8. Although Space Manager can connect to the database, errors will occur when it is run.
For more information, see “Global Operation for Space Manager” in Space
Manager Online Help or in Appendix E of the Space Manager with LiveReorg
User’s Guide.
Space Manager with LiveReorg 6.6 and Capacity Manager for Oracle 1.1 include the following documentation:
Space Manager with LiveReorg online help, and user guide
Note: The installation guide is not included with Space Manager or on the CD. You can download it from SupportLink.
The clients for Space Manager with LiveReorg 6.6 and Capacity Manager for Oracle 1.1 can be installed together with the Quest Installer.
The installer is identified as the Space Manager with Live Reorg 6.6 Installer. The executable for the installer is called SpaceMgrCMOSetup.exe. It is available on SupportLink and on the installation CD for Space Manager with LiveReorg.
After installing the Space Manager client, you install server components and Quest Server Agent 6.6. 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.
Refer to the Space Manager with LiveReorg Installation Guide for information on installing Space Manager.
Get the latest product information, find helpful resources, and join a discussion with the Space Manager with LiveReorg Quest team and other community members. Join the Space Management Community at http://spacemanagementoracle.inside.quest.com/.
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA | |
| Web |
Refer to our web site for regional and international office information.
Quest Support is available to customers who have a trial version of a Quest
product or who have purchased a commercial version and have a valid maintenance
contract.
Quest Support provides around the clock coverage with SupportLink,
our web self-service. Visit SupportLink at http://support.quest.com/.
From SupportLink, you can do the following:
View the Global Support Guide for a detailed explanation of support programs,
online services, contact information, and policy and procedures.
The guide
is available at: http://support.quest.com/pdfs/Global%20Support%20Guide.pdf.
© 2008 Quest Software, Inc.
ALL RIGHTS RESERVED.
This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.
If you have any questions regarding your potential use of this material, contact:
| Quest
Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656
Email: legal@quest.com |
Refer to our web site for regional and international office information.
Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, Knowledge Xpert, LeccoTech, LiteSpeed, LiveReorg, Matrix Insight, Matrix.Net, MIQ, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
This product includes software developed by FastSharemem, SynEdit, and ZipMaster.
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.