Best practice guide of how to install/configure Space Manager (4255038)

Is there a best practice guide of how to install/configure Space Manager?

There are some preparations that DBA should do prior to installing Space Manager & LiveReorg

1. Create a separate user to store the server side objects. For example, you can call the user QUEST or SPACER. This user needs to have DBA role.
2. Create two separate tablespace for Space Manager such as:

• SPACER tablespace (this is the tablespace where the server side objects will resides)
• SPACER_LW (this is the LW_TABLESPACE when installing QSA for livereorg)

     3. Need to know a username/password that have SYSDBA access since the installation would prompt for the SYSDBA user to run scripts to    grant privilege

There are three parts of the Space Manager & LiveReorg installation:

1. Install the Space Manager & LiveReorg client
2. Install the server side objects
3. Install server side objects in a schema called QUEST or SPACER
4. This user must have DBA role. Do not use SYS or SYSTEM user
5. DBA must have EXECUTE  on SYS.DBMS_SYS_SQL privilege
6. During the installation, the installation DBA is prompted to log in as a user with the SYSDBA privilege and run scripts to grant privilege. If the target db does not allow remote login by users with SYSDBA privilege, the installation DBA must have remote database admin capability.
7. To allow non-DBA to use SM for the db, grant them the QUEST_SPC_APP_PRIV role.
8. Use SPACER tablespace when installing the server side objects.

Installing QSA:

1. QSA must be installed by user accounts with sufficient privileges. On UNIX and Linux server, the agent is installed by an OS and an Oracle DBA.
2. You can only use the QSA GUI Installer if you have both rexec and ftp access to the database server on Unix. Otherwise, you have to do the manual install/uninstall QSA for Unix.
3. Before you install QSA, set BEQUEATH_DETACH  to YES in the SQLNET.ORA file. If this parameter is set to NO, the agent’s job scheduler cannot detect when scripts have been cancelled or aborted.
4. To install the agent on Oracle, you must have the UNLIMITED TABLESPACE system privilege and full privileges for the target db. Do not use SYS or SYSTEM.
5. On Windows server, the agent is installed by an Oracle DBA
6. Must have READ, WRITE and DELETE privileges to install QSA on Unix
7. If the agent is installed by root, it must be run under another user account
8. If the agent is installed user an account other than root, it is run under the installation account.
9. 2 parameters need be edit during the installation of QSA:
10. LW_TABLESPACE is used for live-reorg. You would need to set up this parameter even if you are not licensed. It is recommended to create a separate tablespace for LW_TABLESPACE. For example, you can call it SPACER_LW.
11. WORKDIR is used for fastcopy. For example, the directory can be c:\temp if your QSA is on Windows.