Tuesday, January 03, 2017
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 tools allow you to collect statistics, visualize space use, detect space-use problems, reorganize and resize objects to reclaim wasted space, create tablespaces,
As you manage capacity with Space Manager, you can monitor it with 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.
Note: Capacity Manager is not available in a 64-bit version at this time and is not included in the 64-bit installer.
Space Manager with LiveReorg includes the following new features and enhancements.
New 64-bit version of Space Manager
Beginning with release 8.3, Space Manager is now available in a 64-bit version, as well as a 32-bit version.
Window tabs identify the associated connection
Instruct Space Manager to use FsCopy/DataPump
For special situations, you can now instruct Space Manager to use only FsCopy or only DataPump as the data movement method. If the database is Oracle 9, 10, or 11, the Reorg Manager allows you to specify FsCopy. If the database is Oracle 12, the Reorg Manager allows you to specify DataPump.
When to use the FsCopy/DataPump option
Selecting the Use FsCopy or Use DataPump option is recommended only for tables that would otherwise get a "snapshot too old" error during table copy. FsCopy and DataPump are not the most efficient data movement methods and should be selected only for large tables where table copy may cause a "snapshot too old" Oracle error.
Important: Because FsCopy and DataPump use the file system to store a copy of the table, make sure that the file system is prepared and the QSA parameter WORKDIR is set correctly. If using FsCopy, make sure the QSA parameter OVERFLOW_DIR_## is also set correctly.
What is Space Manager FsCopy? FsCopy uses an import and export process to move data. It is one of the actions included in the Space Manager FastCopy data movement method.
How to use this feature:
This release of Space Manager now supports the following Oracle database 12c features.
Reorg scripts. New options supporting 12c features in Reorg scripts.
Note: Space Manager does not support Oracle database releases later than 184.108.40.206.0.
Reorder databases in Explorer tree-list
Oracle 12c PDB. Oracle 12c pluggable (PDB) databases are now nested under the 12c container (CDB) database in the Explorer tree-list.
This release includes a new Advanced Search feature in the Explorer. The advanced search allows you to use multiple search criteria to find objects or filter the list. This is useful when you want to find a diverse set of objects to include in one reorganization script group.
Display latest execution logs for a script group
Cancel and Clean Up command
The following is a list of issues addressed in this release.
|Feature||Enhancement / Resolved Issue||Defect ID|
|Reorg Manager||Improved performance when the analysis option "Restore original statistics in data dictionary for the CBO" is selected on the Scripting Options page of the Reorg Manager.||SPC-241|
|Scripts/Job Monitor||When deleting a script group, if the Detail pane is open, the list of scripts no longer persists in the Details pane after the group is deleted.||SPC-122|
|SQL Editor||Corrected an issue that caused an "access violation" error when attempting to edit a very large script or enter characters very quickly.||SPC-243|
|SQL Editor||Corrected an issue that caused Space Manager to become unresponsive when attempting to run a SELECT statement containing duplicate column names.||SPC-244|
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|
Some wizard screens do not display correctly on Windows 7 if your text size setting is greater than 100%.
Set text size to 100%.
|Oracle 12c Support||
Space Manager does not support Oracle database releases later than 220.127.116.11.0.
|Oracle 9i 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.
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.