Space Manager with LiveReorg®

Version 6.7

Release Notes

October 23, 2008

Welcome to Space Manager with LiveReorg	New in this Release	Resolved Issues and Enhancements	Known Issues	Third Party Known Issues
Upgrade and Compatibility	System Requirements	Global Operations	Getting Started	For More Information

Welcome to Space Manager with LiveReorg

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.

New in This Release

Space Manager with LiveReorg 6.7 supports Oracle 11g. You can use the Reorg Manager and live Partitioning Wizard to leverage the new Oracle 11g partitioning features. While applications and users remain online, you can reorganize, partition, repartition, or unpartition tables and indexes.

The release also includes a number of enhancements and resolved issues, including:

The performance of the “re-architected” Tablespace Map has been significantly improved for very large tablespaces where up to 200,000 segments reside.
The new Pause Posting feature eliminates contention by pausing posting during index creation.
Additional features have been engineered to improve support for very busy databases (ST#40953, ST#43166).

Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in Space Manager with LiveReorg 6.7.

Feature	Resolved Issue	Defect ID
Installation	Upgrading the Space Manager server objects now retains repository information. (This was a problem in Space Manager 6.5 and 6.6)	ST#52,853
Reports	The Reorg History report now supports additional date separators, including periods (.), colons (:), and spaces. This solves the exception in type initializer for ReorgHistoryReport.Utilities.	ST#49,663
Reorg Manager	You can now perform an Online Switch live reorganization in Oracle 8i databases.	ST#50,090
	The Find Long LONGs Execute procedure no longer gives the "ORA-01031: insufficient privileges" error when attempting to run against recycle bin objects. Recycle bin objects are now excluded.	ST#50,345
	The Reorg History capture has been tuned to minimize execution time.	ST#49,736
Tablespace Maps	The Tablespace Map has been improved to use less memory. It now supports tablespaces with up to 200,000 segments.	ST#51,721
Quest Server Agent (QSA)	The QSA configuration file encryption method has been updated.	ST#48,503
	QSA is now limited to five Overflow directories.	ST#43,174, ST#49,169
	QSA automatically retries on Resource Busy errors. It is now possible to change this behavior to limit how long it retries before aborting the script. Contact Quest Support for instructions on enabling this feature.	ST#40,953
	By default, the BEGIN_COPY and ONLINE_SWITCH commands acquire an exclusive lock in WAIT mode. It is now possible to acquire the lock in NOWAIT mode. Contact Quest Support for instructions on how to enable this feature.	ST#43,166
	On AIX 5L (and above) and Oracle 9i+, the QSA installation now maps the Oracle 32-bit libraries at setup time. This will avoid issues some sites have with the LIBPATH environment variable.	ST#49,235
	Posting LONG columns has been improved.	ST#46,918, ST#51,177, ST#51,184
Capacity Manger	You may now upgrade Capacity Manager without uninstalling the previous version.	ST#48,957
Capacity Manger	The Capacity Manager Repository can now be installed on Oracle 9i databases.

Known Issues

The following is a list of issues known to exist at the time Space Manager with LiveReorg 6.7 was released:

Feature	Known Issue	Defect ID
Oracle9i Support
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
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

Third Party Known Issues

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.

Upgrade and Compatibility

When you upgrade to Space Manager 6.7, 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.

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 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: Oracle SQL*Net version 2.1 minimum (32-bit) Oracle Net version 9.2 and 10g 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: Windows 2000 Windows 2003 Windows XP Citrix Metaframe XP	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.

If you would like to read the User Guide or Installation Guide, you must open the files with Adobe Reader 8 or later.

Requirements for Databases

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: Oracle 8.1.7 Oracle 9.2 Oracle 10.2 Oracle 11g Note: If you would like support for Oracle 11g on HP-UX, please contact Support.	See the Space Manager column.
Database Server Operating System	Space Manager supports the following operating systems: HP-UX 11 and 11i on PA_RISC HP-UX 11i on Itanium 2 HP Tru64 UNIX 4.0, 5.0, and 5.1 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 2.1, 3.0, and 4.0 SuSE Linux Enterprise Server 8, 9, and 10 Windows NT Server, Windows 2000 Server and Windows Server 2003 Windows 2003 Itanium IMPORTANT: Space Manager 6.7 no longer supports Sun Solaris 2.6 and 2.7. The Space Manager release after 6.7 will not support Windows NT, Red Hat 2.1, SuSE 8.0, HP Tru64 4.0, and HP Tru64 5.0. On AIX 64-bit systems, the installing Unix user must be configured to use the Oracle 32-bit client libraries.	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: 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	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: For Space Manager: DBMS_SQL, DBMS_PIPE, DBMS_LOCK, DBMS_SPACE_ADMIN. For QSA: DBMS_SQL, DBMS_PIPE, DBMS_OUTPUT, DBMS_APPLICATION_INFO. DBMS_STATS: Required for statistics collection with DBMS_STATS and FND_STATS; also required for statistics preservation in the data dictionary. FND_STATS: Required for statistics collection with FND_STATS. DBMS_REDEFINITION: Required for online redefinition UTL_RAW: Required for Space Manager’s Find Long LONGs package. UTL_SMTP: Required for e-mailing notifications on aborted script execution from Space Manager (Java Option also required in Oracle8i databases); package needs access to an SMTP mail server or relay server.	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.

Requirements for the Capacity Manager Repository

The database used for the Capacity Manager repository must meet the requirements below.

Requirement	Capacity Manager	Space Manager
Oracle Databases	Supported for the repository: Oracle 9.2 Oracle 10.2 Oracle 11g	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 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.

Global Operations

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.

Getting Started

Contents of the Release Package

Space Manager with LiveReorg 6.7 and Capacity Manager for Oracle 1.1 include the following documentation:

Space Manager with LiveReorg online help and user guide
Capacity Manager for Oracle 1.0 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 SupportLink.

Installation Instructions

The clients for Space Manager with LiveReorg 6.7 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.7 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.7. 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.

For More Information

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.

Contacting Quest Software:

Email	info@quest.com
Mail	Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA
Web	http://www.quest.com/

Refer to our web site for regional and international office information.

Contacting Quest Support:

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:

Quickly find thousands of solutions (Knowledgebase articles/documents).
Download patches and upgrades.
Seek help from a Support engineer.
Log and update your case, and check its status.

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.

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

www.quest.com

Email: legal@quest.com

Refer to our web site for regional and international office information.

Trademarks

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.

Third Party Contributions

This product includes software developed by FastSharemem, SynEdit, and ZipMaster.

Disclaimer

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.