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 |
---|---|---|
General |
Some wizard screens do not display correctly on Windows 7 if your text size setting is greater than 100%. Workaround: Set text size to 100%.
|
N/A |
General | When running the Space Manager client (64-bit) in a 64-bit environment, some users might encounter the following error when attempting to submit a standard or live reorg script: “Error creating script group: Could not load file or assembly ManagedQP5.dll or one of its dependencies. is not a valid Win32 application.” | SPC-409 |
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. |
N/A |
Installation |
Error when installing QSA on Windows for Oracle Database 12cR2. Some users might encounter an "Error running setup" error after attempting to install the QSA Server Agent on Windows for Oracle Database 12c R2. Workaround: If you encounter this issue, contact Quest Support for assistance. |
SPC-491 |
Live Reorg |
Error when running Live Reorg on Oracle Database 12cR2 in Windows. Some users might encounter the following error when attempting to run a Live Reorg script on Oracle 12c R2 in a Windows environment: "350: Aborted QSA - 20391 ORA - 01403 during internal SQL." Workaround: If you encounter this issue, contact Quest Support for assistance. |
SPC-493 |
Object Properties | Attempting to open the Object Properties dialog for a recently-created partitioned table using a Direct connection type resulted in an error. |
SPC-482 |
Partitioning Wizard | After creating a table partitioned by range with a global index, using the Partitioning Wizard to change the partitioning method from range to hash unexpectedly changed to the index's locality to local. |
SPC-483 |
Before installing Space Manager and Capacity Manager, ensure that your system meets the following minimum hardware and software requirements.
The Space Manager client must be installed on the same computer, and their requirements are the same unless otherwise specified. The computer must meet the following requirements:
Item | Requirement |
---|---|
Oracle® Client |
Oracle Net version 11g, 12c , and 19c Note: The bitness (architecture) of the Oracle client must match the bitness of the Space Manager application. |
Operating System |
|
Processor | 1 GHz Processor (recommended minimum) |
Memory | 2 GB of RAM |
Display Settings | A resolution of 1024 x 768; true color or high color; small fonts |
Disk Space |
Space Manager: Approximately 800 MB |
.NET Framework |
Microsoft® .NET Framework 4 (including update 4.0.3) Note: The .NET Framework 4 Full Profile is required. The Client Profile is not sufficient. |
Each database being managed with Space Manager must meet the following requirements:
Item | Requirement |
---|---|
Oracle Database |
Notes:
|
Database Server Operating System |
Space Manager supports the following operating systems:
|
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. |
Before installing the server components (and QSA), specify a password version for the database by performing the following procedure.
First, to verify that this procedure is necessary for the target database, run the following query:
select username, password_versions
from dba_users
where username = 'SPACER'
Note: Username is the installation DBA.
Enter the following:
SQLNET.ALLOWED_LOGON_VERSION_SERVER=8
SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8
BEQUEATH_DETACH=YES
Add the below command in the listener.ora
file.
USE_SID_AS_SERVICE_<oracle-sid>=on
Stop and restart the listener. Use the following commands:
lsnrctl stop
lsnrctl start
The listener may take a few minutes to fully restart.
Alter the password for the installation DBA to a temporary password and then back again to reset it, for example:
alter user spacer identified by X;
alter user spacer identified by spacer;
Reset the sys password using alter, for example:
alter user sys identified by syspassword;
Now run the query again to verify the change.
select username, password_versions
from dba_users
where username = 'SPACER'
Note: Username is the installation DBA.
You can also verify the change for the sys user.
select username, password_versions
from dba_users
where username = 'SYS'
For additional information, see the Oracle documentation: https://docs.oracle.com/database/121/NETRF/sqlnet.htm#NETRF2010.
Note: Capacity Manager is not available in a 64-bit version at this time and is not included in the 64-bit installer.
The database used for the Capacity Manager repository must meet the following requirements:
Item | Requirement |
---|---|
Oracle Database |
Supported for the repository: Oracle 12c |
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. |
To activate a trial license
In the License Key dialog, enter your Authorization Key.
Enter the Site Message included with your Authorization Key.
To activate a purchased commercial license
In the License Key dialog, enter your Authorization Key.
Enter the Site Message included with your Authorization Key.
Note: License validation will happen in Space Manager, QSA independently will not authorize the license key.
Space Manager with LiveReorg 9.1 and Capacity Manager for Oracle 1.4 include the following documentation:
Capacity Manager 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 the Quest Software Support Portal.
The clients for Space Manager with LiveReorg 9.1 and Capacity Manager for Oracle 1.4 can be installed together using the Installer.
Note: Capacity Manager is not available in a 64-bit version at this time and is not included in the 64-bit installer.
After installing the Space Manager client, you install server components and the QSA Server Agent. Each database you plan to manage with Space Manager must have server components and an agent. Job scheduling
QSA Server Agent version 8.5 is included in this release of Space Manager with LiveReorg 9.1.
Refer to the Space Manager with LiveReorg Installation Guide for more information about installing Space Manager.
© ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center