Space Manager allows you to create connection profiles to store database connection information. Each profile is comprised of the service name, user name, and password for a database connection. When you select a connection from the tree-list in the Explorer, these values are entered automatically.
The profiles created from a Space Manager client are for that client only. You can create as many profiles as needed for different databases or the same database. A database can have different profiles for different users.
You can have multiple database connections open concurrently during a Space Manager session.
Note: Connection information for the current connection is displayed in the Space Manager title bar. Information consists of service name for the current connection and user name of the connecting user.
Before creating a new connection
To create a new database connection
Enter the connection information in the Connection dialog. Review the following for additional information:
TNS / Direct
Select the type of connection to create.
TNS—Select if using a TNSNames.ora file.
Direct—Select to enter database address information directly, without using a TNSNames.ora file.
(TNS only) Select the TNS name (net service name) for the target database. The field lists all names in the TNSNames.ora file on the client computer.
Note If you are running Space Manager in an active-active OPS or RAC environment, select the service name for the instance where the Quest Server Agent (QSA) is installed.
|SID||(Direct only) Enter the SID or service name for the target database.|
|Host||(Direct only) Enter the host name for the target database.|
|Port||(Direct only) Enter port number, if other than the default.|
Enter the user name of an Oracle user. The user must have the DBA role or the QUEST_SPC_APP_PRIV role. See Space Manager User Requirements for more information.
Enter the password for the Oracle user.
Note: Saved passwords are encrypted.
|Profile Name||Enter a name for the profile. This name is used to identify the connection in the Explorer tree-list (left pane of Explorer window).|
|Oracle Home||Allows you to select the Oracle home to use, if you have multiple Oracle homes specified. Space Manager reads the TNSNames.ora file associated with the selected Oracle home.|
Use one of the following methods to open a connection:
Note: Space Manager server components must be installed in the database to which you want to connect. See Install or Upgrade Server Objects for more information.
Do one of the following:
Note: If you disconnect from a database, all Space Manager windows associated to that database connection will close.
To modify connection properties
When multiple connections are open for a Space Manager session, you can select one as the current connection. All functions performed and all windows opened will apply to the database that is set as the current database connection.
To set the current connection (or switch connections)
Do one of the following:
This chapter describes how to install Space Manager server components using a GUI-based method.
You must install Space Manager server components for each database you intend to manage with Space Manager. The installation program automatically detects which Oracle version you are using and installs the applicable server components.
You are prompted to install (or upgrade) server components the first time you connect to a database from a newly-installed (or upgraded) Space Manager client. Connect as the Oracle DBA chosen to install the server components and QSA.
Server components are installed in the tablespace you specify during installation. SAP users should use SAP administrative tools to create the tablespace for Space Manager objects.
You can install the demonstration data when you install the server components. You can also install the data at a later time. To do so, select Tools | Admin | Demonstration Data from the Space Manager main menu. (This function is enabled for users with the DBA role.)
Tip: Normally, server components are installed for one database at a time. To install them for multiple databases at the same time, create a shell script that runs a manual install script.
After initially installing the Space Manager client, install the server components on each database you intend to manage with Space Manager.
The first time you connect to a database in which Space Manager server components are not installed, you are prompted to install them. See Install or Upgrade Server Objects for more information.
You must upgrade the server components when you upgrade the Space Manager client. The version of the server components must match the version of the Space Manager client you are using.
The first time you connect to a database after upgrading the Space Manager client, you are prompted to upgrade the server components.
Server components must be upgraded by the DBA account that installed them. Analysis groups, statistics, and stored scripts are preserved during the upgrade. This is the case even when you select a different tablespace for Space Manager objects. See Install or Upgrade Server Objects for more information.
Reinstall server components (and the server agent) after you upgrade to a major new version of Oracle Database. Uninstall the server components (and the server agent) before upgrading the Oracle database, then reinstall the server components (and server agent) after upgrading the Oracle database. See Oracle Upgrade for more information.
Install server components after installing the Space Manager client. Install server components for each database you want to manage with Space Manager.
Upgrade the server components after upgrading the Space Manager client.
Use the same DBA account to install server components and the Server Agent. See Space Manager User Requirements for more information.
To install (or upgrade) server objects
When the Connect dialog displays, connect to the database using the Oracle DBA account chosen to install the server components and the Server Agent.
Note: For more information about creating a connection, see Connect to Databases.
When the Create Space Manager with LiveReorg Objects dialog opens, specify an owner and tablespace for the components. See the following for more information.
|Owner||If this is a first-time installation, specify the installation DBA. By default, the field displays the connecting user. To use a different DBA, enter the user name in the Owner field. After you click OK, a password prompt displays.|
Select a tablespace for Space Manager objects. The tablespace must have a standard name and free space equal to or greater than the amount for Expected Allocation. For an upgrade, it must also have enough free space for copies of existing Space Manager tables (created for recovery purposes and dropped when an upgrade is complete).
Objects are upgraded in their current tablespace. If you select a different tablespace, objects are upgraded in that tablespace and dropped from the current tablespace.
Verify the recommended space allocation for Space Manager objects. The recommendations allow for one year of growth in statistics tables.
Note: Use the following guidelines for determining space allocation: small for up to 100 GB, medium for up to 500 GB, etc.
|Allocation to use||Select a space allocation for Space Manager objects. The recommended allocation is entered by default.|
|Expected allocation||Verify the expected space allocation for Space Manager objects. This corresponds to the Allocation to use value.|
Install Space Manager Demonstration Data
If you want to install demonstration data after server components are installed, select this checkbox. Demonstration data requires 20 MB or 24 MB of disk space, depending on your database block size.
Note: If the Recycle Bin for an Oracle 10g database contains many objects, the Create Space Manager with LiveReorg Objects window might require a long time to display. To avoid this problem, empty the recycle bin before you begin the installation.
Click OK. The installation progress displays in the Executing Create dialog. To cancel installation, click Cancel.
Note: In some cases, Space Manager may try to allocate more than the expected allocation. It does this when a tablespace has a large minimum extent size or is locally managed and uses uniform extent allocation. In either case, installation may fail. If it does, click OK to clear the installation error. Begin installation again and select a larger tablespace for Space Manager objects.
The Install/Refresh Demonstration Data window displays if you are installing demonstration data. See the next step.
To install demonstration data, click Install in the Install/Refresh Demonstration Data window. It is recommended that you use the default demonstration user name, tablespace names, and datafile names. A password is not required. If you specify different directories for demonstration datafiles, the directories must already exist.
When demonstration data installation is finished, two “success” messages display. Click OK. The Server Agent Installer displays so that you can install (or upgrade) QSA. See Install or Upgrade Server Agent on UNIX or Linux for more information.
Note: During installation of server components in Oracle 220.127.116.11, if you encounter ORA-600, “ORA-01001. Invalid cursor” or “ORA-01921” Role name ‘QUEST_SPC_APP_PRIV’ conflicts with another role or user name,” contact Quest Software Support for a workaround or use the solution provided in Oracle note 339070.1.