Space Manager with LiveReorg®
Version 7.0
Release Notes
October 26, 2009
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.
Space Manager with LiveReorg 7.0 includes a number of enhancements and resolved issues, including:
The following is a list of issues addressed and enhancements implemented in the Space Manager with LiveReorg 7.0 release:
|
Feature |
Resolved Issue |
Defect ID |
| Reorg Manager | ||
| You can now save Reorg Manager setting as an XML file at any point in the wizard. You can use the XML file to perform reorganizations through the command-line interface. | ST#40,978 | |
| Both Create Table as Select and Insert as Select are now allowed as data movement methods if you chose Unrecoverable. | ST#60,568 | |
| You can now add compression to a table or index during a reorganization in the Reorg Manager. | ST#62,018 | |
| You can now add or remove ROWDEPENDENCIES as part of a table reorganization. | ST#62,617 | |
| Partitioned tables with global indexes now use the UPDATE GLOBAL INDEXES syntax when appropriate for a reorganization. | ST#62,848 | |
| Reorg Manager scripts no longer include UPDATE GLOBAL INDEXES when it is not necessary. | ST#63,070 | |
| Space Manager now supports Oracle's Transparent Data Encryption (TDE) feature. | ST#63,966 | |
| Space Manager now includes a switch summary in the Notes section of the Schedule Script Execution page. The summary helps you schedule the reorganization by identifying the switch type and number of dependencies. | ST#63,999 | |
| The query response time in Reorg Manager has been improved. | ST#65,161 | |
| The Online Switch now supports tables referenced by foreign keys. | ST#66,369 | |
| Reorganization scripts now retain the Validate state of NOT NULL constraints. When the NOT NULL constraint is ENABLE NOVALIDATE it does not show when using Oracle’s DESCRIBE command, but the constraint is enabled and active in either state. | ST#66,567 | |
| The space check in Reorg Manager now avoids extent-level analysis when the target tablespace is managed locally. For some databases, this dramatically reduces the time needed to generate the script. In addition, there are new Space Manager parameters available to turn off the extent-level analysis for dictionary-managed tablespaces and to turn it on for autoallocate tablespaces. Contact Quest Support for more information on these new parameters. | ST#67,303 | |
| Reports | The chained row percentage now displays
correctly in the Object Needing Reorganization Report. |
ST#57,750 |
| An overflow issue on the Tablespace Failure Prediction report that resulted from a very low growth rate has been corrected. | ST#66,257 | |
| Tablespace Maps | Loading a Tablespace Map file where some of the segments have an extremely large allocation no longer causes errors. | ST#60,032 |
| Tablespace Map performance has been improved. | ST#64,056 | |
| Objects in a multi-file tablespace are no longer omitted from the Tablespace Map display. | ST#66,377 | |
| Quest Server Agent (QSA) | A check engine error no longer causes multi-threaded analysis group jobs to fail. | ST#63,094 |
| Scripts/Job Monitor | The Scripts/Job Monitor now displays the number of entries (if any) in the long posting detail queue in the LiveReorg detail pane. | ST#55,210 |
| Aborted or canceled scripts can no longer be deleted from the Scripts/Job Monitor. They must be completed (Restart) or cleaned up first. | ST#60,074 | |
| The Script/Job Monitor now displays "N/A" when the end date is null. | ST#60,799 | |
| General | Certain date formats no longer prevent the Object Properties window from launching. | ST#61,561 |
| The manual install script has been updated to match the automated install. | ST#64,600 |
The following is a list of issues known to exist at the time Space Manager with LiveReorg 7.0 was released:
|
Feature |
Known Issue |
Defect ID |
| Reorg Manager | ||
| If you select "Fixed Extent Size" and "Choose
extent size to…" on the Define Storage Strategy page, you may get a divide
by zero error. Workaround: Enter a number (any number) in the box next to "All Extents". |
ST#67,684 | |
| Script Generation | Encryption passwords are scripted with a single
quote (') instead of double quotes ("). For example, assume Space Manager
generates the following script: Create table (col1 number encrypt identified by 'test');
|
ST#67,940 |
| 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#48257 |
The following describes a third-party issue in Space Manager with LiveReorg 6.5 and above:
|
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. |
When you upgrade to Space Manager 7.0, 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, and their requirements are the same unless otherwise specified. The computer must meet the requirements below.
| Oracle Client | Supported by both Space Manager and Capacity
Manager:
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:
|
| Processor | Pentium III or compatible processor minimum; Pentium IV recommended. |
| Memory | 512 MB of RAM minimum; 1 GB recommended. |
| Display Settings | 1024 by 768 resolution; true color or high color; small fonts. |
| Disk Space | Space Manager: Approximately 300 MB Capacity Manager: 10 MB |
| .NET Framework | Microsoft .NET Framework 2.0 |
If you would like to read the User Guide or Installation Guide, you must open the files with Adobe Reader 8 or later.
Each database being managed with Space Manager must meet the requirements below.
| Oracle Database | Supported by both Capacity and Space Manager:
Notes:
|
| Database Server Operating System | Space Manager supports the following operating
systems:
Note: On AIX 64-bit systems, the installing Unix user must be configured to use the Oracle 32-bit client libraries. |
| Disk Space | Disk-space requirements are:
|
| 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. |
The database used for the Capacity Manager repository must meet the requirements below.
| Oracle Databases | Supported for the 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 this product
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.
The release is localized to the following languages: Japanese.
Space Manager with LiveReorg 7.0 and Capacity Manager for Oracle 1.1 include the following documentation:
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 SupportLink.
The clients for Space Manager with LiveReorg 7.0 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 7.0 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 7.0. 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.
© 2009 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, and LiveReorg 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.
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.