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, and their requirements are the same unless otherwise specified. The computer must meet the following requirements:
| Oracle Client | Supported by both Space Manager and Capacity Manager: - Oracle SQL*Net version 2.1 minimum (32-bit)
- Oracle Net version 9.2, 10g, and 11g
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: - Windows Server 2003
- Windows XP
- Windows Vista (FDCC compliant)
- Windows Server 2008
- Windows 7
- Citrix Metaframe XP
|
| Processor | Pentium IV Processor |
| Memory | 512 MB of RAM minimum; 1 GB recommended |
| Display Settings | A resolution of 1024 x 768; true color or high color; small fonts |
| Disk Space | Space Manager: Approximately 600 MB Capacity Manager: Approximately 13 MB |
| .NET Framework | Microsoft .NET Framework 2.0 |
Requirements for Databases
Each database being managed with Space Manager must meet the following requirements:
| Oracle Database | Supported by both Capacity and Space Manager: - Oracle 9.2
- Oracle 10.2
- Oracle 11g
- Oracle 11g R2
Note: Space Manager supports Oracle Enterprise Edition and Standard Edition databases. |
| Database Server Operating System | Space Manager supports the following operating systems: - HP-UX 11 and 11i on PA_RISC
- HP-UX 11i on Itanium
- 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 3.0, 4.0, and 5.1
- Oracle Linux 4 and 5
- Oracle Linux 5 with Unbreakable Enterprise Kernel
- SuSE Linux Enterprise Server 9 and 10
- Windows 2000 Server and Windows Server 2003 and 2008
Note: When using Oracle 11.1 or earlier on 64-bit systems, the installing user must be configured to use the Oracle 32-bit client libraries. For Oracle 11.2 or later on 64-bit systems, the installing user can use the Oracle 64-bit client libraries. |
| 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
|
| 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. |
Requirements for the Capacity Manager Repository
The database used for the Capacity Manager repository must meet the following requirements:
| Oracle Database | Supported for the repository: - Oracle 9.2
- Oracle 10.2
- Oracle 11g
- Oracle 11g R2
|
| 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, report scheduling, and Windows scheduling: - 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. |
Language Supported: