Space Manager with LiveReorg 9.2 - Installation Guide

Create Database Connections

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

• Oracle client must match architecture (bitness) of Space Manager. Install an Oracle client that matches the bitness of the Space Manager application. For example, 64-bit Space Manager requires a 64-bit Oracle client and 32-bit Space Manager requires a 32-bit Oracle client.
• Tnsnames file. Make sure the tnsnames.ora file on the Space Manager client computer contains service names for all databases to be managed with Space Manager.

To create a new database connection

1. Select File | Add New Connection.

2. 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.
   Server	(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.
   User Name	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.
   Password	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.

3. Click Add Database to save the profile. Space Manager adds the connection to the tree view in the Explorer window.

To connect

Use one of the following methods to open a connection:

• Select a database connection in the tree view (left pane) in the Explorer.
• Right-click a database connection and select Connect .
• Select a connection and click .

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.

To disconnect

Do one of the following:

• Right-click the connection name in the tree-list and select Disconnect.
• Select a connection name in the tree-list and click .
• Select a window that is connected to the database from which you want to disconnect. With this window as the active window, click .

Note: If you disconnect from a database, all Space Manager windows associated to that database connection will close.

To modify connection properties

• Right-click a connection in the tree-list and select Edit Connection Parameters.

Working with Multiple Connections

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:

• In the Explorer window, select the database connection in the Explorer tree-list.
• Select a window associated to the database connection.

Install Space Manager Server Componenets

Overview

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.

SAP Users

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.

Demonstration Data

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.

Before Installing Server Components

Specify Password Version for Oracle 12c R2 and 19c Databases

This procedure applies to Oracle 12c Release 2 and 19c databases that you intend to manage with Space Manager.

Beginning with Space Manager 8.5, for each Oracle database you intend to manage, specify a password version in the SQLNET.ORA file of the target database.

If you attempted to install QSA without performing this procedure and encountered an Oracle error, see Troubleshooting.

To specify password version for target database

1. 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.

2. If results returned include "10G, 11G, 12c" in the PASSWORD VERSIONS column, then this procedure is not necessary for this database.
3. If results do not include 10G, you must perform this procedure for the target database.
4. Open the SQLNET.ORA file for the target database. The file is stored in a default directory or one specified with the TNS_ADMIN environment variable. The default directory varies by platform:
   • On UNIX and Linux database servers, the default directory is $ORACLE_HOME/network/admin
   • On Windows database servers, the default directory is ORACLE_HOME\network\admin

5. Enter the following:

   SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8

   SQLNET.ALLOWED_LOGON_VERSION_CLIENT = 8

   BEQUEATH_DETACH = YES

6. Save the SQLNET.ORA file.
7. Add the below command in the listener.ora file.

   USE_SID_AS_SERVICE_<oracle-sid>=on

8. Stop and restart the listener. Use the following commands:

   lsnrctl stop

   lsnrctl start

   The listener may take a few minutes to fully restart.

9. 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;

10. Reset the sys password using alter, for example:

    alter user sys identified by syspassword;

11. 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.

12. You can also verify the change for the sys user.

    select username, password_versions

    from dba_users

    where username = 'SYS'

13. If results returned from the queries include "10G, 11G, 12c" in the PASSWORD VERSIONS column, the password version was successfully set.

For additional information, see the Oracle documentation: https://docs.oracle.com/database/121/NETRF/sqlnet.htm#NETRF2010.

Troubleshooting

When to Install/Upgrade/Reinstall Server Components

Install Server Components After Initially Installing the Client

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.

Upgrade Server Components After Upgrading the Client

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 after Upgrading the Oracle Database

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

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

1. Launch the Space Manager client.

2. 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.

3. (Upgrade only) If this is an upgrade, one or more of the following messages display:
   • Upgrade required—The is the default message. Click Yes.
   • Running scripts—The install program has found scripts that the Server Agent is executing. Click OK to cancel the upgrade and perform it later.
   • Scheduled scripts—The install program has found scripts that are scheduled for execution by the Server Agent. If you are sure the upgrade will complete before the first script executes, click Yes. Otherwise, click No to cancel the upgrade. You will need to upgrade later.

4. When the Create Space Manager with LiveReorg Objects dialog opens, specify an owner and tablespace for the components. See the following for more information.

   Field	Description
   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.
   Tablespace	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.
   Recommended (upgrade only)	Verify the recommended space allocation for Space Manager objects. The recommendations allow for one year of growth in statistics tables. Small is for databases with less than 1,000 non-SYS segments Medium is for databases with 1,000 to 9,999 non-SYS segments Large is for databases with 10,000 to 24,999 non-SYS segments Huge is for databases with more than 25,000 non-SYS segments 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 (install only)	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 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.

5. 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.

6. You will encounter a prompt if QUEST_COM_PRODUCTS_% tables are already installed for the target database but the owner is not the installation DBA for Space Manager.
   • To continue, click Yes. The Space Manager objects will be owned by the installation DBA. And QUEST_COM_PRODUCTS_% tables will continue to be owned by their current owner. (Public synonyms and certain views will be owned by SYS.)
   • To cancel installation, click No. Then, when you start the installation again, use the QUEST_COM_PRODUCTS_% table owner as the installation DBA. Space Manager objects and QUEST_COM_PRODUCTS_% tables will be owned by this user. (Public synonyms and certain views will be owned by SYS.)
7. If O7_DICTIONARY_ACCESSIBILITY is FALSE for the target database and the installation DBA does not have EXECUTE on SYS.DBMS_SYS_SQL, you are allowed to run scripts to grant the privilege.
   • When prompted, enter the user name and password for a SYSDBA account. The first script prompts you to enter the name of the installation DBA.
8. When server component installation is finished, one of the following displays:
   • A “success” message displays if you are not installing demonstration data. Click OK. Then the Server Agent Installer displays so that you can install the agent. See Install or Upgrade Server Agent on UNIX or Linux for more information.

   • The Install/Refresh Demonstration Data window displays if you are installing demonstration data. See the next step.

9. 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.

10. 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.