SpaceManager 8.3 InstallGuide

SpaceManager
withLiveReorg8.3
Installation Guide
Copyright2017QuestSoftwareInc.
ALLRIGHTSRESERVED.
Thisguidecontainsproprietaryinformationprotectedbycopyright.Thesoftwaredescribedinthisguideis
furnishedunderasoftwarelicenseornondisclosureagreement.Thissoftwaremaybeusedorcopiedonlyin
accordancewiththetermsoftheapplicableagreement.Nopartofthisguidemaybereproducedortransmitted
inanyformorbyanymeans,electronicormechanical,includingphotocopyingandrecordingforanypurpose
otherthanthepurchaserspersonalusewithoutthewrittenpermissionofQuestSoftwareInc.
TheinformationinthisdocumentisprovidedinconnectionwithQuestSoftwareproducts.Nolicense,express
orimplied,byestoppelorotherwise,toanyintellectualpropertyrightisgrantedbythisdocumentorin
connectionwiththesaleofQuestSoftwareproducts.EXCEPTASSETFORTHINTHETERMSAND
CONDITIONSASSPECIFIEDINTHELICENSEAGREEMENTFORTHISPRODUCT,QUESTSOFTWARE
ASSUMESNOLIABILITYWHATSOEVERANDDISCLAIMSANYEXPRESS,IMPLIEDORSTATUTORY
WARRANTYRELATINGTOITSPRODUCTSINCLUDING,BUTNOTLIMITEDTO,THEIMPLIEDWARRANTY
OFMERCHANTABILITY,FITNESSFORAPARTICULARPURPOSE,ORNON-INFRINGEMENT.INNOEVENT
SHALLQUESTSOFTWAREBELIABLEFORANYDIRECT,INDIRECT,CONSEQUENTIAL,PUNITIVE,
SPECIALORINCIDENTALDAMAGES(INCLUDING,WITHOUTLIMITATION,DAMAGESFORLOSSOF
PROFITS,BUSINESSINTERRUPTIONORLOSSOFINFORMATION)ARISINGOUTOFTHEUSEOR
INABILITYTOUSETHISDOCUMENT,EVENIFQUESTSOFTWAREHASBEENADVISEDOFTHE
POSSIBILITYOFSUCHDAMAGES.QuestSoftwaremakesnorepresentationsorwarrantieswithrespecttothe
accuracyorcompletenessofthecontentsofthisdocumentandreservestherighttomakechangesto
specificationsandproductdescriptionsatanytimewithoutnotice.QuestSoftwaredoesnotmakeany
commitmenttoupdatetheinformationcontainedinthisdocument.
Ifyouhaveanyquestionsregardingyourpotentialuseofthismaterial,contact:
QuestSoftwareInc.
Attn:LEGALDept
4PolarisWay
AlisoViejo,CA92656
RefertoourWebsite(www.quest.com)forregionalandinternationalofficeinformation.
Patents
SpaceManagerwithLiveReorgisprotectedbyU.S.PatentsNo.7,805,423and7,970,748.Additionalpatents
pending.Formoreinformation,gotowww.quest.com/legal.
Trademarks
Quest,QuestSoftware,LiveReorg,andtheQuestlogoaretrademarksofQuestSoftwareInc.intheU.S.A.and
othercountries.ForacompletelistofQuestSoftwaretrademarks,pleasevisitourwebsiteat
www.quest.com/legal.Microsoft,Windows,WindowsServer,andWindowsVistaareeitherregistered
trademarksortrademarksofMicrosoftCorporationintheUnitedStatesand/orothercountries.Oracleisa
trademarkorregisteredtrademarkofOracleand/oritsaffiliatesintheUnitedStatesandothercountries.UNIX
isaregisteredtrademarkofTheOpenGroup.LinuxisaregisteredtrademarkofLinusTorvaldsintheUnited
States,othercountries,orboth.Othertrademarksarepropertyoftheirrespectiveowners.
Legend
IMPORTANT, NOTE, TIP, MOBILE, VIDEO:Aninformationiconindicatessupportinginformation.
CAUTION:A CAUTION indicates potential damage to hardware or loss of data if instructions are
not followed.
WARNING:A WARNING indicates a potential for property damage, personal injury, or death.
SpaceManagerwithLiveReorg
InstallationGuide
January2017
Contents
Contents 3
Architecture and Requirements 5

Architecture 5
SpaceManagerClient 5
SpaceManagerServerComponents 5
ServerAgent 5
DemonstrationData 6
SystemRequirements 6
SpaceManagerUserRequirements 6
ServerObjectsInstallation 6
ServerAgentInstallation 7
RunningSpaceManager 8
GlobalOperationRequirements 8
UserNameandPasswordRequirements 8
CharacterSetRequirementsforAgentInstallation 8
Installation Overview 10
Overview-InstallationProcess 10
SmartStartforInstallingSpaceManager 10
Install Space Manager Client 12

InstallSpaceManagerClient 12
UpgradingSpaceManager 12
ConfigureDEPifEnabled 12
InstallorUpgradetheSpaceManagerClient 12
Licensing and Connections 14

LicenseKey 14
ConnecttoDatabases 14
WorkingwithMultipleConnections 16
Install Space Manager Server Componenets 17

Overview-InstallServerComponents 17
WhentoInstall/Upgrade/ReinstallServerComponents 17
InstallorUpgradeServerObjects 18
Install Server Agent 21

Overview-InstallServerAgent 21
BeforeInstallingtheServerAgent 21
WhentoInstall/Upgrade/ReinstalltheServerAgent 22
InstallorUpgradeServerAgentonUNIXorLinux 22
Space Manager with LiveReorg 8.3 Installation Guide

3
Contents
InstallServerAgentonWindows 23
InstalltheAgentonaLocalServer 24
InstalltheAgentonaRemoteServer 25
InstallServerAgentonOPSorRAC 25
InstallationGuidelines 26
ConnectionSetupforOPSorRAC 26
InstallationErrorsforOPSorRAC 26
QSAServerAgentParameters 27
SENDMAILParameters 29
SNMPTrapParameters 30
AdditionalNotificationParameters 30
SEND_LR_COMPLETEOptions 31
LocksReportingParameters 31
Uninstall Space Manager and Server Agent 33

Overview-UninstallSpaceManager 33
OracleUpgrade 33
Uninstall(Remove)ServerObjects 34
UninstalltheServerAgent 34
UninstallQSAfromUNIXorLinux 35
UninstallQSAfromWindows 35
UninstalltheSpaceManagerClient 36
Manually Install/Uninstall Server Agent 37

Overview-ManuallyInstallandUninstallServerAgent 37
WhentoUseManualInstallation 37
ManuallyInstallServerAgentonUNIXorLinux 37
ManuallyInstallServerAgentonWindows 39
Sampleqsaparms.batfile 39
ManuallyUninstallServerAgentfromUNIXorLinux 42
ManuallyUninstallServerAgentfromWindows 42
About Us 43
Wearemorethanjustaname 43
Ourbrand,ourvision.Together. 43
ContactQuest 43
TechnicalSupportResources 43

4
Contents
1
Architecture and Requirements
Architecture
SpaceManagerwithLiveReorgincludesaWindowsclient,servercomponents,andtheServerAgent,ascript
executionengine.Italsoincludesdemonstrationdata,whichyoucanusetoexploreSpaceManager
functionalityusingsimulatedobjectsandtablespaces.
YoucanmanagemultipleOracledatabasesfromasingleSpaceManagerclient.Servercomponentsandthe
ServerAgentmustbeinstalledforeachdatabaseyouplantomanage.Servercomponentsarenormally
installedforonedatabaseatatime.Toinstallthemformultipledatabasessimultaneously,createashellscript
torunthemanualinstallscript.
Space Manager Client

TheSpaceManagerclientisagraphicuserinterfacedesignedtoletyoueasilyandefficientlymanagespacein
Oracledatabases.
Space Manager Server Components

SpaceManagerservercomponentsincludeobjects,views,andpackages.SpaceManagertablesstore
scheduledscriptsandthestatisticscollectedbySpaceManager.Thescriptandstatisticstablescomprisethe
SpaceManagerrepository.Therepositoryislocatedinthetablespacespecifiedduringinstallationofserver
components.
SpaceManagerincludestheFindLongLONGspackagethatworksinconjunctionwiththeReorgManager
reorganizationwizard.TheFindLongLONGspackageallowsyoutofindtableswithLONGorLONGRAW
columnsthatarelargerthan32,760bytes(longLONGs).PopulatetheFindLongLONGstablebeforeyourun
theReorgManager.
Server Agent
TheServerAgentisascriptexecutionenginethatSpaceManagerusestorunreorganization,repair,and
statisticscollectionscriptsfromthedatabaseserveronascheduledbasis.Theagentmustbeusedtorunlive
reorganizationscriptsandscriptsthatuseFastCopy,FSCopy,orparallelagentprocesses.Scriptsare
automaticallyrunbytheagentwhentheyarescheduledandstoredintheSpaceManagerrepository.
Theagentisstartedwhenitisinstalled.Itthenrunscontinuously.OnUNIXandLinux,theagentrunsasa
daemon.OnWindows,itrunsasaservice.Theagentusesoneconnectionforitself.Itestablishesadditional
connectionsforeachscriptitrunsandforeachparallelprocessituses.
YoucanstopandstarttheagentfromtheSpaceManagerToolsmenuandtheScripts/JobMonitor.
Note:BeforeyouupgradetoamajornewversionofOracle,uninstalltheagent.AfterthenewOracle
databaseisinstalled,reinstalltheagent.Thisensuresthattheagentusesthecorrectfilesforthenew
versionofOracle.

5
Demonstration Data
Demonstrationdatacomprisesobjectsandtablespacesthataresubjecttothespace-useproblemsfoundina
typicaldatabase.YoucanuseittolearnhowSpaceManagerdetectsandresolvesproblems.Afteryouresolve
problems,youcanrefreshdemonstrationdatatorestoreitsoriginalcondition.
Installationofdemonstrationdataisoptional.Itrequires20MBor24MBofdiskspace,dependingonyour
defaultdatabaseblocksize.Thedemouseristheownerofalldemoobjects.
Note:Demonstrationdatafunctionsareonlyenabledfordatabaseadministrators.
System Requirements
RefertotheSpace Manager with LiveReorg Release Notesforthemostup-to-dateClient,database,and
CapacityManagerrepositoryrequirements.BeforeinstallingSpaceManagerandCapacityManager,ensure
thatyoursystemmeetstheminimumhardwareandsoftwarerequirements.
Space Manager User Requirements

Thissection describesthe privilegesrequired toinstall SpaceManager servercomponents andto run
SpaceManager.
Server Objects Installation

ToinstallSpaceManagerservercomponents,youmusthavetheDBAroleandfullprivilegesforthetarget
database.(DonotuseSYSorSYSTEM.)Yourusernamemustnotrequiredoublequotes.
Note:InOracle12c,theserverobjectsandServerAgentmustbeinstalledbyacommonuserwithDBA
privilegesonallcontainers.SeeInstallationDBAinOracle12c.
The DBA account that installs the Space Manager server objects (components) owns the objects. This
same DBA account must be used to upgrade and uninstall the server components (which include Space
Manager objects).
TheDBAaccountusedtoinstalltheservercomponentsshouldalsobeusedtoinstalltheServerAgent.
TheprivilegesneededtorunFND_STATSasanon-APPsuserareautomaticallygrantedduringinstallationof
SpaceManagerservercomponents.AnyuserwiththeDBAorQUEST_SPC_APP_PRIVrolecanrunFND_
STATSfromSpaceManager.
Installation DBA in Oracle 12c

InanOracle12cdatabase,theserverobjectsandServerAgentmustbeinstalledbyacommonuserwith
DBAprivilegesonallcontainers.Thisaccountmustbecreatedpriortoinstallationoftheserverobjectsand
ServerAgent.
1. IntheOracle12crootcontainer,usingacommonuseraccountsuchasSYSorSYSTEM,createanother
commonuseraccounttobeusedforinstallingserverobjects(andServerAgent).
2. GrantthenewcommonuseraccountDBAprivilegesacrossallcontainers.Forexample,useagrant
statementsuchasthefollowing:
grant dba to c##<user> container = all;

6
Privileges and the O7_DICTIONARY_ACCESSIBILITY Parameter
WhenOraclesO7_DICTIONARY_ACCESSIBILITYinitializationparameterissettoFALSEforatarget
database,thefollowingrequirementsmustbemet:
l Theinstallation DBAmust havethe EXECUTEon SYS.DBMS_SYS_SQLprivilege. During
installation,the installationDBA isprompted tolog inusing aSYSDBA accountand thenrun scripts
togrant thisprivilege.
l IfthetargetdatabasedoesnotallowremoteloginbyuserswiththeSYSDBAprivilege,theinstallation
DBAmusthaveremotedatabaseadministrationcapability.Thiscapabilitymustbegrantedpriorto
installation.
1. First,createanauthenticationpasswordfileforthetargetdatabase.
2. Second,settheREMOTE_LOGIN_PASSWORDFILEparametertoEXCLUSIVEfortheDBA
accountyouplantouseastheuserforSpaceManagerservercomponents.
Server Agent Installation

TheServerAgentmustbeinstalledbyuseraccountswithsufficientprivileges.Theagentmustbeupgraded,
configured,anduninstalledbyitsinstallationaccount.OnUNIXandLinuxservers,theagentisinstalledbyan
operatingsystemaccountandanOracleDBA.OnWindowsservers,theagentisinstalledbyanOracleDBA.
Note:InOracle12c,theserverobjectsandServerAgentmustbeinstalledbyacommonuserwithDBA
privilegesonallcontainers.SeeInstallationDBAinOracle12c.
UNIX and Linux Privileges

ToinstalltheagentonUNIXorLinux,youmusthaveREAD,WRITE,andDELETEprivilegesfortheinstallation
directory.Duringinstallation,theuserconnectstothedatabaseserverhostusingSSH.Theuserneeds
privilegessimilartotheoperatingsystemuserthatinstalledOracle.
Oracle Privileges
ToinstalltheagentonOracle,youmusthavetheUNLIMITEDTABLESPACEsystemprivilegeandfullprivileges
forthetargetdatabase.(DonotuseSYSorSYSTEM.)ToinstalltheagentonWindows,youmusthaveall
permissionsfortheagentinstallationfolder.
Onallsupportedplatforms,theinstallationDBAmusthavetheEXECUTEprivilegeon:
l DBMS_PIPE
l DBMS_SQL
l DBMS_SYS_SQL
l DBMS_LOB
Normally,EXECUTEprivilegesaregrantedaspartoftheDBAroleorduringServerAgentinstallation.Ifthe
privilegescannotbegrantedduringinstallationoriftheyarerevoked,theagentdoesnotruncorrectly.Tofixthe
problem,grantthemissingprivilegestotheinstallationDBA.
TheinstallationDBAconnectstothetargetdatabasewhenQSAisinstalled.Italsoautomaticallyconnectsthe
agenttothedatabaseeachtimethesystemisstarted.
Note:UsethesameDBAaccounttoinstallSpaceManagerservercomponentsandtheServerAgent.The
sameaccountisautomaticallyusedwhenyouruntheServerAgentInstallerfromSpaceManager
immediatelyafterservercomponentsareinstalled.

7
Running Space Manager
SpaceManagercanberunbyDBAusersandbynon-DBAusersthathavetheQUEST_SPC_APP_PRIVrole.
ThissectiondescribeshowtogranttheQUEST_SPC_APP_PRIVrolefromSpaceManager.
To grant privileges from Space Manager

TograntprivilegesfromSpaceManager,theinstallationDBArunsthefollowingprocedureintheSQLEditor(in
theprocedure,USERNAMEistheusernameoftheuserbeinggrantedprivileges):
Begin
quest_spc_user_manager.grant_user (USER NAME);
End;
Theprocedureshouldberunfornon-DBAusersthatwillrunSpaceManager.Theproceduregrantsthe
QUEST_SPC_APP_PRIVroleandadditionalprivilegestonon-DBAs.ItgrantsonlytheQUEST_SPC_APP_
PRIVroletonon-installationDBAs.
Note:Privilegesmustbegrantedaftereachupgrade,aswellasaftertheinitialinstallation.
Global Operation Requirements

ThissectiondescribeswhatisrequiredtoinstallSpaceManagerandQSAinnon-Englishconfigurationssuch
asthoseusedoutsideNorthAmerica.
Note:Seetheonlinehelptolearnalltherequirementsfornon-EnglishoperationofSpaceManager.
User Name and Password Requirements

TheusersthatinstallSpaceManagerandQSAfornon-Englishoperationmustmeetthefollowingrequirements:
l TheusernameandpasswordoftheinstallationDBAmustconformtoOracleguidelines.
l TheusernameandpasswordoftheinstallationDBAmustusecharactersthatcanbeconverted
betweenyourclientcomputercharactersetandyourdatabasecharacterset.
l TheusernameoftheinstallationDBAmustnotbeindoublequotationmarks(x).
l TheusernameforQSAsoperating-systemaccountonUNIXorLinuxmustuseASCIIcharacters.
Character Set Requirements for Agent Installation

WhenQSAisinstalledinanon-Englishconfiguration,theconfigurationmustmeetthefollowingcharacter-set
requirements:
Installation Factor UNIX and Linux Windows
Hostnamefordatabase MustbeaDNSname;IDNnames MustbeaDNSname;IDNnames

server arenotsupported arenotsupported
Servicenamefordatabase Canusedatabasecharactersetor Canusedatabasecharactersetor

ASCII ASCII
UsernameforOracleDBA Canusedatabasecharactersetor Canusedatabasecharactersetor

thatinstallstheagent ASCII ASCII

8
Installation Factor UNIX and Linux Windows
PasswordforOracleDBA Canusedatabasecharactersetor Canusedatabasecharactersetor

thatinstallstheagent ASCII ASCII
Usernameforoperating MustuseASCII Nocharacter-setrequirement

systemuserthatinstallsthe
agent
Passwordforoperating MustuseASCII Nocharacter-setrequirement

systemuserthatinstallsthe
agent
Tablespacenamesforagent Canusedatabasecharactersetor Canusedatabasecharactersetor

tableandLW_TABLESPACE ASCII;namesmustnotrequire ASCII;namesmustnotrequire
doublequotes doublequotes
Installdirectoryandpathfor MustuseASCII MustuseASCII

agent
Workdirdirectoryandpath MustuseASCII MustuseASCII

forFastCopy
Overflowdirectoryandpaths MustuseASCII MustuseASCII

forFastCopy

9
2
Installation Overview
Overview - Installation Process

ThischapterprovidesanoverviewoftheSpaceManagerinstallationprocess.ItalsoincludesaSmartStartthat
liststhemajorstepsintheprocess.
AcompleteinstallationofSpaceManagerincludestheSpaceManagerclient,SpaceManagerserver
components,andtheServerAgent.
l Space Manager clientTheSpaceManagerclientisinstalledonaWindowscomputerusingtheSpace
Managersetupprogram.TheclientisavailableonSupportLinkandontheCD.
l Space Manager server componentsTheservercomponentsareinstalledusingtheGUIinstall
programthatyoucanlaunchfromtheclient.Youshouldinstallthecomponentsineachdatabaseyou
plantomanagewithSpaceManager.Theinstallprogramstartsautomaticallythefirsttimeyouconnect
withtheclienttoatargetdatabase.YoucanrunitatanytimeusingtheReinstallServerfunction
accessiblefromtheclientmainmenu.Whenyouinstallservercomponents,youcanalsoinstall
demonstrationdata.
l Quest Server AgentTheserveragentisinstalledusingtheServerAgentInstaller.Youshouldinstall
theagentforeachdatabasewhereSpaceManagerservercomponentsareinstalled.TheServerAgent
Installerstartsautomaticallyaftertheservercomponents(ordemonstrationdata)areinstalled.Youcan
runitatanytimebyselectingTools | Admin | Quest Server Agent | Manage Quest Server Agentfrom
theclientmainmenu.
Note: Before you install QSA in an OPS or RAC active-active environment, see Install Server Agent
on OPS or RAC.
Smart Start for Installing Space Manager

IfthisisyourfirsttimeinstallingSpaceManager,starthere!Thissectionoutlinesthebasicsstepstoinstallthe
SpaceManagerdesktopapplication,theservercomponents,andtheserveragent.
Clickthelinksprovidedforeachsteptoseedetailedinformation.
1. Prepare for installation.Reviewthefollowingbeforeinstalling:
l System requirementsMakesureallsystemrequirementsaremet.Forexample,makesureall
requiredOraclepackagesareinstalledandvalidforeachtargetdatabase.IftheLiveReorg
optionislicensed,makesureOraclespartitioningoptionisinstalled.SeetheSystem
RequirementssectionoftheSpace Manager with LiveReorg Release Notes.
l tnsnames.oraMakesurethetnsnames.orafileontheSpaceManagerclientcomputer
containsservicenamesforalldatabasestobemanagedwithSpaceManager.
l OPS or RAC active-activeIfyouplantorunSpaceManagerinanactive-activeOPSorRAC
environment,seeInstallServerAgentonOPSorRAC.QSAshouldbeinstalledononlyone
instanceforaclusterdatabase.YouneedtoconnecttothisinstancewhenyourunSpace
ManagerforthatdatabaseorinstallorupdateQSA.

10
l O7_DICTIONARY_ACCESSIBILITYCheckthesettingforthisinitializationparameterineach
targetdatabase.IftheparameterissettoFALSEandadatabasedoesnotallowremoteloginby
userswiththeSYSDBAprivilege,granttheinstallationDBAremotedatabaseadministration
capability.SeeSpaceManagerUserRequirementsonpage6formoreinformation.
2. Choose installation user accounts.ChooseinstallationusersforSpaceManagerservercomponents
andQSAforeachtargetdatabase.ServercomponentsmustbeinstalledbyanOracleDBAwithfull
privilegesforatargetdatabase.(DonotuseSYSorSYSTEM.)SeeSpaceManagerUserRequirements
onpage6formoreinformation.QSAmustbeinstalledbyOracle,UNIX,orLinuxuserswithsufficient
privileges.UsethesameDBAaccounttoinstallboththeservercomponentsandtheserveragent.
3. Choose tablespaces.ChooseorcreateatablespaceforSpaceManagertablesandindexes.During
installationofservercomponents,youhavetheopportunitytoselectthetablespace.Itmusthavea
standardname.Foranupgrade,itmusthaveenoughfreespacefortemporarycopiesofstatisticsand
analysis-grouptables.Thecopiesarecreatedforrecoverypurposesanddroppedwhenanupgradeis
successfullycompleted.
AlsochooseorcreatetablespacesforQSAspermanentobjectsandtemporaryLiveReorgobjects.The
tablespacechosenforSpaceManagerobjectsisrecommendedfortheagentspermanentobjects.A
separatetablespaceisrecommendedforLiveReorgobjects.Duringinstallationoftheagent,youhave
theopportunitytoselectagenttablespaces.TheLiveReorgtablespaceisspecifiedwiththeLW_
TABLESPACEparameter.ItmustbespecifiedevenifLiveReorgisnotlicensed.
Note: SAP users should use SAP administrative tools to create tablespaces for Space
Manager and QSA.
4. Install the Space Manager client.ToinstalltheSpaceManagerclientonaWindowscomputer,usethe

installationexecutableavailablefromSupportLink.SeeInstallSpaceManagerClientonpage12for
moreinformation.
5. Install Space Manager server components.ThefirsttimeyouconnecttoadatabasefromtheSpace
Managerclient,youarepromptedtoinstallSpaceManagerservercomponents.ConnectastheOracle
DBAchosentoinstallboththeservercomponentsandtheserveragent.SeeInstallorUpgradeServer
Objectsonpage18formoreinformation.
6. Install demonstration data (optional).Afterservercomponentsareinstalled,youcaninstall
demonstrationdataforatargetdatabase.SeeInstallorUpgradeServerObjectsonpage18formore
information.
7. Install the Server Agent.TheServerAgentInstallerdisplaysautomaticallyafterservercomponentsor
demonstrationdataareinstalled.ItisusedtoinstallQSAforatargetdatabase.TheOracleDBAthat
installedservercomponentsalsoinstallstheagent.ThesameDBAaccountshouldbeusedforboth.
SeeOverview-InstallServerAgentonpage21formoreinformation.
8. Grant privileges to non-DBA users.Toallownon-DBAuserstouseSpaceManagerforatarget
database,grantthemtheQUEST_SPC_APP_PRIVrole.SeeRunningSpaceManageronpage8for
moreinformation.
9. Run the Find Long LONGs procedure for a target database.TheFindLongLONGsEXECUTE
procedureidentifiestablesthatcontainLONGorLONGRAWcolumnsthatarelargerthan32,760bytes.
ThesizeofLONGcolumnsdetermineswhichdata-movementmethodcanbeusedfortheirtablesduring
reorganization.
Note:AfteryouupgradeSpaceManager,youcanrunstoredstatisticscollectionscriptsgeneratedwithan
earlierversion.However,youshouldnotrunstoredreorganizationandrepairscriptsgeneratedwithan
earlierversion.Instead,generatenewreorganizationandrepairscriptswiththenewversion.

11
3
Install Space Manager Client

InstallSpaceManagerusingthesetupprogramthatisavailableontheCDandfromtheSupportPortal.See
AboutUsonpage43formoreinformation.
ThesetupprograminstallsbothSpaceManagerandCapacityManagerforOracle.YoucanrunSpace
ManagerfromCapacityManager.Formoreinformation,seetheCapacityManageronlinehelp.
Note:CapacityManagerisnotincludedinthe64-bitinstaller.A64-bitversionofCapacityManagerisnot
availableatthistime.
YoucanmanagemultipledatabasesfromasingleSpaceManagerclient.
Note:Whenyouperformafirst-timeinstallation,youarepromptedtoenteryourSpaceManagerlicense
key.ThiskeyisalsousedforCapacityManagerforOracle,whichdoesnotrequireaseparatekey.
Upgrading Space Manager

Important Information about Script Compatibility
AscriptiscompatiblewiththeversionofSpaceManagerthatwasusedtogeneratethescript.Ifafterupgrading
SpaceManageryourunascriptgeneratedinapreviousversionandthenscriptexecutionfailswithaQSA-
20500error,regeneratethescript.SeeQSA Error MessagesintheonlineHelpformoreinformation.
Configure DEP if Enabled

IfinstallingonWindows2003orWindowsXPwhereDataExecutionPrevention(DEP)enabled,theSpace
Managerclientwillnotrun.YoumustfirstconfigureDEP.
To configure DEP
UseoneofthefollowingmethodstoconfigureDEP:
l SelectthefollowingoptionintheWindowsControlPanel:Turn on DEP for Essential Windows programs
and services only.
l AddtheSpaceManagerexecutabletothelistofexcludedprogramsforDEP.Tochangesettingsfor
DEP,selectControl Panel | System | Advanced | Performance | Data Execution Prevention.Consult
yoursystemadministratorbeforealteringthesesettings.
Install or Upgrade the Space Manager Client

Beginningwithrelease8.3,SpaceManagerisavailableina32-bitversionanda64-bitversion.
UsethefollowingproceduretoinstallorupgradetheSpaceManagerclient.

12
To install (or upgrade) the Space Manager client
1. RuntheSpaceManagersetupprogram(Installer).ThisisavailablefromtheCDorfromtheQuest
SoftwareSupportPortal.Runeitherthe32-bitorthe64-bitInstaller.
2. FromtheInstaller,selecttheproductsyouwanttoinstall.InstallSpaceManagerandCapacityManager
andanyotherproductsorupdates.
Note:CapacityManagerisnotavailableina64-bitversionandisnotincludedinthe64-bitinstaller.
3. Whentheinstallationisfinished,dooneofthefollowingtolaunchSpaceManager:
l SelectStart | All Programs | Quest | Space Manager version
l Onyourdesktop,double-clicktheSpaceManagericon.
4. IftheSpaceManagerLicensedialogdisplays,enteryourlicensekeyandsitemessage.
5. SpaceManagerstarts.Ifnecessary,createanewdatabaseconnection.SeeConnecttoDatabaseson
page14formoreinformation.
l IfthedatabasedoesnothaveSpaceManagerservercomponentsinstalled,youwillbeprompted
toinstallthem.SeeInstallorUpgradeServerObjectsonpage18formoreinformation.
Side-by-Side Installation
SpaceManager8.3(orlater)supportsside-by-sideinstallationofversionswithdifferentarchitecture(bitness)as
longastheyarealsodifferentreleases(e.g.,8.2and8.3).
Forexample,youcouldinstallthefollowingside-by-side:
l 32-bitSpaceManager8.2and64-bitSpaceManager8.3

13
4
Licensing and Connections
License Key
AfteryoufirstinstalltheSpaceManagerclientandtrytoconnecttoadatabase,youarepromptedtoentera
licensekey.Onceyouenterapermanentkey,youdonotneedtoenteritagain.Itispreservedduringupgrades.
Youonlyneedtochangeorre-enteralicensekeywhen:
l Yourtrialkeyexpires.
l Youswitchfromatrialkeytoapermanentkey.
l YouchangeyourlicensingagreementwithQuestSoftware.
l YouuninstallandthenreinstalltheSpaceManagerclient.
To update a license key

1. SelectTools | Admin | License Key.
2. Enteryourpermanentortriallicensekey.
Connect to Databases
SpaceManagerallowsyoutocreateconnectionprofilestostoredatabaseconnectioninformation.Eachprofile
iscomprisedoftheservicename,username,andpasswordforadatabaseconnection.Whenyouselecta
connectionfromthetree-listintheExplorer,thesevaluesareenteredautomatically.
TheprofilescreatedfromaSpaceManagerclientareforthatclientonly.Youcancreateasmanyprofilesas
neededfordifferentdatabasesorthesamedatabase.Adatabasecanhavedifferentprofilesfordifferentusers.
YoucanhavemultipledatabaseconnectionsopenconcurrentlyduringaSpaceManagersession.
Note:ConnectioninformationforthecurrentconnectionisdisplayedintheSpaceManagertitlebar.
Informationconsistsofservicenameforthecurrentconnectionandusernameoftheconnectinguser.
Before creating a new connection

l Oracle client must match architecture (bitness) of Space Manager.InstallanOracleclientthat
matchesthebitnessoftheSpaceManagerapplication.Forexample,64-bitSpaceManagerrequiresa
64-bitOracleclientand32-bitSpaceManagerrequiresa32-bitOracleclient.
l Tnsnames file.Makesurethetnsnames.orafileontheSpaceManagerclientcomputercontainsservice
namesforalldatabasestobemanagedwithSpaceManager.
To create a new database connection

1. SelectFile | Add New Connection.
2. EntertheconnectioninformationintheConnectiondialog.Reviewthefollowingforadditional

14
information:
TNS/Direct Selectthetypeofconnectiontocreate.
TNSSelectifusingaTNSNames.orafile.
DirectSelecttoenterdatabaseaddressinformationdirectly,without
usingaTNSNames.orafile.
Server (TNSonly)SelecttheTNSname(netservicename)forthetarget
database.ThefieldlistsallnamesintheTNSNames.orafileontheclient
computer.
NoteIfyouarerunningSpaceManagerinanactive-activeOPSor
RACenvironment,selecttheservicenamefortheinstancewherethe
QuestServerAgent(QSA)isinstalled.
SID (Directonly)EntertheSIDorservicenameforthetargetdatabase.
Host (Directonly)Enterthehostnameforthetargetdatabase.
Port (Directonly)Enterportnumber,ifotherthanthedefault.
UserName EntertheusernameofanOracleuser.TheusermusthavetheDBArole
ortheQUEST_SPC_APP_PRIVrole.SeeSpaceManagerUser
Requirementsonpage6formoreinformation.
Password EnterthepasswordfortheOracleuser.
Note:Savedpasswordsareencrypted.
ProfileName Enteranamefortheprofile.Thisnameisusedtoidentifytheconnection
intheExplorertree-list(leftpaneofExplorerwindow).
OracleHome AllowsyoutoselecttheOraclehometouse,ifyouhavemultipleOracle
homesspecified.SpaceManagerreadstheTNSNames.orafile
associatedwiththeselectedOraclehome.
3. ClickAdd Databasetosavetheprofile.SpaceManageraddstheconnectiontothetreeviewinthe
Explorerwindow.
To connect
Useoneofthefollowingmethodstoopenaconnection:
l Selectadatabaseconnectioninthetreeview(leftpane)intheExplorer.
l Right-clickadatabaseconnectionandselectConnect.
l Selectaconnectionandclick .
Note:SpaceManagerservercomponentsmustbeinstalledinthedatabasetowhichyouwanttoconnect.
SeeInstallorUpgradeServerObjectsonpage18formoreinformation.
To disconnect
Dooneofthefollowing:
l Right-clicktheconnectionnameinthetree-listandselectDisconnect.
l Selectaconnectionnameinthetree-listandclick .
l Selectawindowthatisconnectedtothedatabasefromwhichyouwanttodisconnect.Withthiswindow
astheactivewindow,click .

15
Note:Ifyoudisconnectfromadatabase,allSpaceManagerwindowsassociatedtothatdatabase
connectionwillclose.
To modify connection properties

l Right-clickaconnectioninthetree-listandselectEdit Connection Parameters.
Working with Multiple Connections

WhenmultipleconnectionsareopenforaSpaceManagersession,youcanselectoneasthecurrent
connection.Allfunctionsperformedandallwindowsopenedwillapplytothedatabasethatissetasthecurrent
databaseconnection.
To set the current connection (or switch connections)

Dooneofthefollowing:
l IntheExplorerwindow,selectthedatabaseconnectionintheExplorertree-list.
l Selectawindowassociatedtothedatabaseconnection.

16
5
Install Space Manager Server
Componenets
Overview - Install Server Components

ThischapterdescribeshowtoinstallSpaceManagerservercomponentsusingaGUI-basedmethod.
YoumustinstallSpaceManagerservercomponentsforeachdatabaseyouintendtomanagewithSpace
Manager.TheinstallationprogramautomaticallydetectswhichOracleversionyouareusingandinstallsthe
applicableservercomponents.
Youarepromptedtoinstall(orupgrade)servercomponentsthefirsttimeyouconnecttoadatabasefroma
newly-installed(orupgraded)SpaceManagerclient.ConnectastheOracleDBAchosentoinstalltheserver
componentsandQSA.
SAP Users
Servercomponentsareinstalledinthetablespaceyouspecifyduringinstallation.SAPusersshoulduseSAP
administrativetoolstocreatethetablespaceforSpaceManagerobjects.
Demonstration Data
Youcaninstallthedemonstrationdatawhenyouinstalltheservercomponents.Youcanalsoinstallthedataat
alatertime.Todoso,selectTools | Admin | Demonstration DatafromtheSpaceManagermainmenu.(This
functionisenabledforuserswiththeDBArole.)
Tip:Normally,servercomponentsareinstalledforonedatabaseatatime.Toinstallthemformultiple
databasesatthesametime,createashellscriptthatrunsamanualinstallscript.
When to Install/Upgrade/Reinstall Server Components
Install Server Components After Initially Installing the Client

AfterinitiallyinstallingtheSpaceManagerclient,installtheservercomponentsoneachdatabaseyouintendto
managewithSpaceManager.
ThefirsttimeyouconnecttoadatabaseinwhichSpaceManagerservercomponentsarenotinstalled,youare
promptedtoinstallthem.SeeInstallorUpgradeServerObjectsonpage18formoreinformation.
Upgrade Server Components After Upgrading the Client

YoumustupgradetheservercomponentswhenyouupgradetheSpaceManagerclient.Theversionofthe
servercomponentsmustmatchtheversionoftheSpaceManagerclientyouareusing.
ThefirsttimeyouconnecttoadatabaseafterupgradingtheSpaceManagerclient,youarepromptedto
upgradetheservercomponents.

17
Install Space Manager Server Componenets
ServercomponentsmustbeupgradedbytheDBAaccountthatinstalledthem.Analysisgroups,statistics,and
storedscriptsarepreservedduringtheupgrade.Thisisthecaseevenwhenyouselectadifferenttablespace
forSpaceManagerobjects.SeeInstallorUpgradeServerObjectsonpage18formoreinformation.
Reinstall Server Components after Upgrading the Oracle Database

Reinstallservercomponents(andtheserveragent)afteryouupgradetoamajornewversionofOracle
Database.Uninstalltheservercomponents(andtheserveragent)beforeupgradingtheOracledatabase,then
reinstalltheservercomponents(andserveragent)afterupgradingtheOracledatabase.SeeOracleUpgrade
onpage33formoreinformation.
Install or Upgrade Server Objects

InstallservercomponentsafterinstallingtheSpaceManagerclient.Installservercomponentsforeach
databaseyouwanttomanagewithSpaceManager.
UpgradetheservercomponentsafterupgradingtheSpaceManagerclient.
UsethesameDBAaccounttoinstallservercomponentsandtheServerAgent.SeeSpaceManagerUser
Requirementsonpage6formoreinformation.
To install (or upgrade) server objects

1. LaunchtheSpaceManagerclient.
2. WhentheConnectdialogdisplays,connecttothedatabaseusingtheOracleDBAaccountchosento
installtheservercomponentsandtheServerAgent.
Note:Formoreinformationaboutcreatingaconnection,seeConnecttoDatabases.
3. (Upgradeonly)Ifthisisanupgrade,oneormoreofthefollowingmessagesdisplay:
l Upgrade requiredTheisthedefaultmessage.ClickYes.
l Running scriptsTheinstallprogramhasfoundscriptsthattheServerAgentisexecuting.Click
OKtocanceltheupgradeandperformitlater.
l Scheduled scriptsTheinstallprogramhasfoundscriptsthatarescheduledforexecutionby
theServerAgent.Ifyouaresuretheupgradewillcompletebeforethefirstscriptexecutes,click
Yes.Otherwise,clickNotocanceltheupgrade.Youwillneedtoupgradelater.
4. WhentheCreateSpaceManagerwithLiveReorgObjectsdialogopens,specifyanownerand
tablespaceforthecomponents.Seethefollowingformoreinformation.
Field Description
Owner Ifthisisafirst-timeinstallation,specifytheinstallationDBA.Bydefault,the
fielddisplaystheconnectinguser.TouseadifferentDBA,entertheuser
nameintheOwnerfield.AfteryouclickOK,apasswordpromptdisplays.
Tablespace SelectatablespaceforSpaceManagerobjects.Thetablespacemusthavea
standardnameandfreespaceequaltoorgreaterthantheamountfor
ExpectedAllocation.Foranupgrade,itmustalsohaveenoughfreespacefor
copiesofexistingSpaceManagertables(createdforrecoverypurposesand
droppedwhenanupgradeiscomplete).
Objectsareupgradedintheircurrenttablespace.Ifyouselectadifferent
tablespace,objectsareupgradedinthattablespaceanddroppedfromthe
currenttablespace.

18
Field Description
Recommended VerifytherecommendedspaceallocationforSpaceManagerobjects.The
(upgradeonly) recommendationsallowforoneyearofgrowthinstatisticstables.
l Smallisfordatabaseswithlessthan1,000non-SYSsegments
l Mediumisfordatabaseswith1,000to9,999non-SYSsegments
l Largeisfordatabaseswith10,000to24,999non-SYSsegments
l Hugeisfordatabaseswithmorethan25,000non-SYSsegments
Note:Usethefollowingguidelinesfordeterminingspaceallocation:
smallforupto100GB,mediumforupto500GB,etc.
Allocationtouse SelectaspaceallocationforSpaceManagerobjects.Therecommended
allocationisenteredbydefault.
Expected VerifytheexpectedspaceallocationforSpaceManagerobjects.This
allocation correspondstotheAllocationtousevalue.
InstallSpace Ifyouwanttoinstalldemonstrationdataafterservercomponentsareinstalled,
Manager selectthischeckbox.Demonstrationdatarequires20MBor24MBofdisk
Demonstration space,dependingonyourdatabaseblocksize.
Data Note:IftheRecycleBinforanOracle10gdatabasecontainsmany
(installonly) objects,theCreateSpaceManagerwithLiveReorgObjectswindowmight
requirealongtimetodisplay.Toavoidthisproblem,emptytherecycle
binbeforeyoubegintheinstallation.
5. ClickOK.TheinstallationprogressdisplaysintheExecutingCreatedialog.Tocancelinstallation,
clickCancel.
Note:Insomecases,SpaceManagermaytrytoallocatemorethantheexpectedallocation.Itdoes
thiswhenatablespacehasalargeminimumextentsizeorislocallymanagedandusesuniform
extentallocation.Ineithercase,installationmayfail.Ifitdoes,clickOKtocleartheinstallationerror.
BegininstallationagainandselectalargertablespaceforSpaceManagerobjects.
6. YouwillencounterapromptifQUEST_COM_PRODUCTS_%tablesarealreadyinstalledforthetarget
databasebuttheownerisnottheinstallationDBAforSpaceManager.
l Tocontinue,clickYes.TheSpaceManagerobjectswillbeownedbytheinstallationDBA.And
QUEST_COM_PRODUCTS_%tableswillcontinuetobeownedbytheircurrentowner.(Public
synonymsandcertainviewswillbeownedbySYS.)
l Tocancelinstallation,clickNo.Then,whenyoustarttheinstallationagain,usetheQUEST_
COM_PRODUCTS_%tableownerastheinstallationDBA.SpaceManagerobjectsandQUEST_
COM_PRODUCTS_%tableswillbeownedbythisuser.(Publicsynonymsandcertainviewswill
beownedbySYS.)
7. IfO7_DICTIONARY_ACCESSIBILITYisFALSEforthetargetdatabaseandtheinstallationDBAdoesnot
haveEXECUTEonSYS.DBMS_SYS_SQL,youareallowedtorunscriptstogranttheprivilege.
l Whenprompted,entertheusernameandpasswordforaSYSDBAaccount.Thefirstscript
promptsyoutoenterthenameoftheinstallationDBA.
8. Whenservercomponentinstallationisfinished,oneofthefollowingdisplays:
l Asuccessmessagedisplaysifyouarenotinstallingdemonstrationdata.ClickOK.Thenthe
ServerAgentInstallerdisplayssothatyoucaninstalltheagent.SeeInstallorUpgradeServer
AgentonUNIXorLinuxonpage22formoreinformation.
l TheInstall/RefreshDemonstrationDatawindowdisplaysifyouareinstallingdemonstrationdata.
Seethenextstep.

19
9. Toinstalldemonstrationdata,clickInstallintheInstall/RefreshDemonstrationDatawindow.Itis
recommendedthatyouusethedefaultdemonstrationusername,tablespacenames,anddatafile
names.Apasswordisnotrequired.Ifyouspecifydifferentdirectoriesfordemonstrationdatafiles,the
directoriesmustalreadyexist.
10. Whendemonstrationdatainstallationisfinished,twosuccessmessagesdisplay.ClickOK.TheServer
AgentInstallerdisplayssothatyoucaninstall(orupgrade)QSA.SeeInstallorUpgradeServerAgenton
UNIXorLinuxonpage22formoreinformation.
Note:During installationof servercomponents inOracle 9.2.0.7,if youencounter ORA-600,ORA-
01001.Invalid cursoror ORA-01921Role nameQUEST_SPC_APP_PRIV conflictswith anotherrole
oruser name,contact QuestSoftware Supportfor aworkaround oruse thesolution providedin Oracle
note339070.1.

20
6
Install Server Agent
Overview - Install Server Agent

ThischapterdescribeshowtoinstallQSAforOracledatabasesonUNIX,Linux,andWindowsservers.Italso
describesagentparametersandbestpracticestoinstalltheagentinanOPSorRACenvironment.
YoumustinstallQSAineachdatabaseyouplantomanagewithSpaceManager.Theagentshouldbeinstalled
afterSpaceManagerservercomponentsareinstalled.Itmustbeinstalledbeforeyoucanrunscheduledscripts.
Toinstalltheagent,theQSAInstallerusesfilesthatarecopiedtotheSpaceManagerclientcomputerduring
clientinstallation.ThefilesarestoredintheQuestServerAgentfolderundertheSpaceManagerfolder.
Duringagentinstallation,theQSAInstallerdetermineswhethertheagentfilesforyourenvironmentare
availableandcurrent.Italsodetermineswhetheryourdatabaseandoperatingsystemversionsaresupported.
Note:LoginfieldsintheQSAInstallerarecasesensitive.Ifyouenterausernameorpasswordinthewrong
case,logoninvaliddisplaysatthebottomoftheinstaller.
Before Installing the Server Agent
Set BEQUEATH_DETACH for the Agent

BeforeyouinstalltheServerAgent,setBEQUEATH_DETACHtoYESintheSQLNET.ORAfileforthetarget
database.Ifyoudothisaftertheagentisinstalled,stopandstarttheagenttoensurethatthechangeis
recognized.
WhenBEQUEATH_DETACHissettoNOorisnotsetforadatabase,theagentsjobschedulercannotdetect
whenscriptshavebeencancelledoraborted.Asaresult,cancelledandabortedscriptscannotberestarted
fromSpaceManager.IfyoutrytorestartascriptwhenBEQUEATH_DETACHissettoNO,oneoftheerrorsthat
mightdisplayis:
QSA-20311:Tableconflictwithscriptalreadyexecuting.
To set BEQUEATH_DETACH
1. OpentheSQLNET.ORAfileforthetargetdatabase.Thefileisstoredinadefaultdirectoryorone
specifiedwiththeTNS_ADMINenvironmentvariable.Thedefaultdirectoryvariesbyplatform:
l OnUNIXandLinuxdatabaseservers,thedefaultdirectoryis$ORACLE_HOME/network/admin
l OnWindowsdatabaseservers,thedefaultdirectoryisORACLE_HOME\network\admin
2. ChangetheBEQUEATH_DETACHsettingfromNOtoYESoraddthefollowingentrytothefile:
bequeath_detach=yes
3. SavetheSQLNET.ORAfile.

21
When to Install/Upgrade/Reinstall the Server Agent
Install the Server Agent After Initially Installing the Client

AfterinitiallyinstallingtheSpaceManagerclient,installtheservercomponentsandtheServerAgentoneach
databaseyouintendtomanagewithSpaceManager.
ThefirsttimeyouconnecttoadatabaseinwhichSpaceManagerservercomponentsarenotinstalled,youare
promptedtoinstallthem.Aftercomponentinstallationisfinished,theServerAgentInstalleropensallowingyou
toinstalltheagent.
Upgrade the Server Agent After Upgrading the Client

YoumustupgradetheServerAgentwhenyouupgradetheSpaceManagerclient.Thefirsttimeyouconnectto
adatabaseafterupgradingtheSpaceManagerclient,youarepromptedtoupgradetheservercomponents.
Whencomponentupgradeisfinished,theServerAgentinstalleropensallowingyoutoupgradetheagent.
Justliketheservercomponents,theserveragentmustbeupgradedbytheDBAaccountthatinstalledit.Agent
tablesareautomaticallyupgradedinthetablespacewheretheywerefirstinstalled.Agentexecutablesare
automaticallyupgradedintheinstallationdirectorywheretheyarecurrentlyinstalled.
Note:Ifupgradingtheserveragent,performtheupgradewhennoscheduledscriptsareexecutingorabout
toexecute.
Reinstall the Server Agent after Upgrading the Oracle Database

ReinstalltheserveragentalongwiththeservercomponentsafteryouupgradetoamajornewversionofOracle
Database.UninstalltheservercomponentsandtheserveragentbeforeupgradingtheOracledatabase,then
reinstalltheservercomponentsandserveragentafterupgradingtheOracledatabase.SeeOracleUpgradeon
page33formoreinformation.
Install or Upgrade Server Agent on UNIX

or Linux
Usethefollowingproceduretoinstall(orupgrade)theServerAgentinanOracledatabaseonaUNIXorLinux
server.YoucanusetheServerAgentInstallerifyouhavebothSSHandSFTPaccesstoyourdatabaseserver.
Ifyoudonothaveboth,youmustinstalltheagentmanually.See"ManuallyInstallServerAgentonUNIXor
Linux"intheSpace Manager Installation Guideformoreinformation.
InstalltheServerAgentusingthesameDBAaccountusedtoinstalltheservercomponents.Forinformation
aboutinstallationDBAaccountrequirements,seeSpaceManagerUserRequirements.
Notes:
l IfthetargetdatabaseisinanOPSorRACsystemthatusestheactive-activeconfiguration,see
"InstallServerAgentonOPSorRAC"intheSpace Manager Installation Guideformoreinformation.
l Ifupgradingtheserveragent,performtheupgradewhennoscheduledscriptsareexecutingor
abouttoexecute.

22
To install (or upgrade) the Server Agent on UNIX or Linux
1. RuntheSpaceManagerclientandconnecttothetargetdatabaseastheDBAthatinstalledtheSpace
Managerservercomponents.
Note:IftheServerAgentInstallerautomaticallyopensafterinstallingtheservercomponents,it
openstotheLogontoServerpage.Skipaheadtostep4.
2. ToruntheServerAgentInstaller,selectTools | Admin | Quest Server Agent | Manage Quest Server

Agent Installation.
3. (Upgradeonly)IfyouareupgradingacurrentlyinstalledinstanceofQSA,selectUpgrade Quest Server
AgentontheSelectInstallationTypepageandclickNext.
4. IntheLogontoServerwindow,entertheusernameandpasswordoftheUNIXorLinuxaccount.Enter
thehostservernameifitisnotdisplayed.ClickNext.
5. IntheOracleConnectionInfowindow,reviewtheinformation.Ifnecessary,completeormodifyany
fields.ClickNext.Ifyouareupgrading,youcanonlyeditthestagingdirectorypathinthiswindow.
6. IntheInstallQuestServerAgentwindow,clickInstalltoinstallQSA.IntheAgentInstallationComplete
window,clickNext.
7. IntheQSAParameterswindow,specifyvaluesforQSAparametersorusethedefaultvalues.
Note:DeselectShowonlyrequiredfieldswithmissingvaluetoseeallparameters.
Valuesapplytothetargetdatabase.YoumustentervaluesforWORKDIR(usedforFastCopy/DBMS_
DataPump)andLW_TABLESPACE(usedforlivereorganizationsandrequiredevenifLiveReorgisnot
licensed).ClickNextwhenfinished.SeeQSAServerAgentParametersonpage27formore
information.
8. IntheInstallationFinishedwindow,clickFinishtoexittheServerAgentInstaller.
Note:BeforetheServerAgentisinstalled,youmayencounteroneofthefollowingmessages:
l Files not currentTheagentinstallationfilesareeithernotavailableornotcurrent.ExittheServer
AgentInstaller,installthemostrecentSpaceManagerclient.NewagentfilesarecopiedtoServer
Agentfolderontheclientcomputer.Youcantheninstalltheagent.
l Environment not supported / cannot proceedBothyourOracleversionandoperatingsystem
versionarenotsupported.Theagentcannotbeinstalled.YoumustupgradetoasupportedOracle
versionandasupportedoperatingsystem.SeetheSpace Manager Release Notesforalistof
supportedOracleDatabaseandOperatingSystemversions.
l Environment not supported / can proceedEitheryourOracleversionoryouroperatingsystem
versionisnotsupported.Inmostcases,asupportedversionofOracleisrunningonanunsupported
operatingsystemversion.Althoughyoucanproceedwiththeinstallation,youmayhaveproblems.
To instruct the Server Agent to restart automatically after a server restart

IfyouwanttheServerAgenttostartautomaticallyeachtimetheserverisstarted,performthefollowingsteps:
1. LogintoUNIXorLinuxasroot.
2. Changetotheagentinstallationdirectoryusingthefollowingcommand:
# cd /$ORACLE_HOME/Quest/QSA/SID/inst
3. Runthefollowingroot.shscript:
# ./root.sh
Install Server Agent on Windows

ThissectiondescribeshowtoinstalltheServerAgentonalocaloraremoteWindowsserver:

23
l Local serverAserverislocalifitresidesonyourSpaceManagerclientcomputer.Whenaserveris
local,youmustworkfromtheclientcomputertoinstalltheServerAgent.Itmustbeinstalledona
localdrive.
l Remote serverAserverisremoteifitdoesnotresideonyourSpaceManagerclientcomputer.When
aserverisremote,youshouldworkfromtheservertoinstalltheServerAgent.
InstalltheServerAgentusingthesameDBAaccountusedtoinstalltheservercomponents.Forinformation
aboutinstallationDBAaccountrequirements,seeSpaceManagerUserRequirements.
Prerequisites
l ForinstallationoneitheralocaloraremoteWindowsserver,theinstallationOracleDBAmusthaveall
permissionsfortheagentinstallationfolder.
l Onaremoteserver,thefoldermustbesharedorcopiedtotheserver.
Note:Ifupgradingtheserveragent,performtheupgradewhennoscheduledscriptsareexecutingorabout
toexecute.
Install the Agent on a Local Server

UsethefollowingproceduretoinstallQSAinadatabaseonalocalWindowsserver.
To install (or upgrade) the Server Agent on a local Windows server

1. RuntheSpaceManagerclientandconnecttothetargetdatabaseusingtheDBAaccountthatinstalled
theSpaceManagerservercomponents.
Note:Ifyouinstalled(orupgraded)theservercomponents,theServerAgentInstalleropens
automaticallyaftercomponentinstallationisfinished.Skipaheadtostep4.
2. ToruntheQSAInstaller,selectTools | Admin | Quest Server Agent | Manage Quest Server Agent

Installation.
3. (Upgradeonly)IfyouareupgradingQSA,theSelectInstallationTypewindowdisplays.SelectUpgrade
Quest Server AgentandclickNext.
4. IntheOracleConnectionInfowindow,reviewtheinformation.Ifnecessary,completeormodifyany
fields.ClickNext.Ifyouareupgrading,youcanonlyeditthestagingdirectorypathinthiswindow.
5. IntheInstallQuestServerAgentwindow,clickInstalltoinstallQSA.IntheAgentInstallationComplete
window,clickNext.
6. IntheQSAParameterswindow,specifyvaluesforQSAparametersorusethedefaultvalues.Values
applytothetargetdatabase.YoumustentervaluesforWORKDIR(usedforFastCopy/DBMS_
DataPump)andLW_TABLESPACE(usedforlivereorganizationsandrequiredevenifLiveReorgisnot
licensed).ClickNextwhenfinished.SeeQSAServerAgentParametersonpage27formore
information.
7. IntheInstallationFinishedwindow,clickFinishtoexittheQSAInstaller.
Note:BeforetheServerAgentisinstalled,youmayencounteroneofthefollowingmessages:
l Files not currentTheagentinstallationfilesareeithernotavailableornotcurrent.ExittheServer
AgentInstaller,installthemostrecentSpaceManagerclient.NewagentfilesarecopiedtoServer
Agentfolderontheclientcomputer.Youcantheninstalltheagent.
l Environment not supported / cannot proceedBothyourOracleversionandoperatingsystem
versionarenotsupported.Theagentcannotbeinstalled.YoumustupgradetoasupportedOracle
versionandasupportedoperatingsystem.SeetheSpace Manager Release Notesforalistof
supportedOracleDatabaseandOperatingSystemversions.

24
l Environment not supported / can proceedEitheryourOracleversionoryouroperatingsystem
versionisnotsupported.Inmostcases,asupportedversionofOracleisrunningonanunsupported
operatingsystemversion.Althoughyoucanproceedwiththeinstallation,youmayhaveproblems.
Install the Agent on a Remote Server

ToinstallQSAonaremoteWindowsserver,youmustcopytheQSAinstallerfromtheSpaceManager
applicationdirectorytotheWindowsserver.
TomanuallyinstallQSAonWindows,see"ManuallyInstallandUninstalltheServerAgentonWindows"inthe
Space Manager Installation Guide.
Note:Bestpracticeistoinstalllocally.Duringremoteinstallation,ifyouencounterproblemsorerror
messagessuchasQSA-20375:Cannotinstallthedaemon.orNetworkpathnotfoundusethelocal
installprocedure.
To copy the QSA Installer to remote Windows server

1. NavigatetotheSpaceManagerclientapplicationdirectory:
l InWindowsExplorer,navigateto:C:\ProgramFiles\Quest\SpaceManager<versionnumber>
2. OpentheQuestServerAgentfolderandcopyQSA_version_build-QSASetup.exetotheWindowsserver.
To install the Server Agent on a remote Windows server

1. AftercopyingtheServerAgentinstaller(QSA_version_build-QSASetup.exe)totheWindowsserver,
double-clickQSA_version_build-QSASetup.exetorunit.
2. Extractthefilestoatemporarydirectory.
Note:Makesurethetemporarydirectoryisemptybeforeyouextractthefiles.
3. Afterthefilesareextracted,theGUIinstallerautomaticallyopens.
4. IntheConnecttoOracleDatabasewindow,entertheservicenameofthetargetdatabaseandconnect
usingtheDBAaccountthatinstalledtheSpaceManagerservercomponents.
5. Follow the instructions in the previous section, Install the Agent on a Local Server, beginning
with step 3.
6. After installation, from the Windows Services window, verify that QSA is running. If Started does
not display as the QSA status, start the agent from the Services window or run the QSAStart.cmd
from the \bin folder under the agent installation folder (<installation path>\Quest Server
Agent\<ORACLE_SID>\bin).
Tip:Iftheagentisinstalledformorethanonedatabaseontheserver,lookfortheQuestServer
AgentnamethatincludesthetargetdatabaseSID.
Install Server Agent on OPS or RAC

ThissectionprovidesadditionalinformationandguidelinestofollowwheninstallingQSAinanOPSorRAC
environmentthatusesanactive-activeconfiguration.
Note:TheServerAgentdoesnotfailoverfromoneinstancetoanotherinanactive-activeenvironment.If
theagentinstancefailsduringscriptexecutionbytheagent,executionaborts.Toresolvethisproblem,
bringuptheinstancewheretheagentisinstalledandrestartscriptexecution.Ifyoucannotbringupthe
agentinstance,contactQuestSoftwareSupportforassistance.

25
Installation Guidelines
QSAshouldbeinstalledononlyoneinstanceinanactive-activeOPSorRACenvironment.Theinstance
shouldbetheprimaryinstance.
Toensurethatyouconnecttothecorrectinstance,createaconnectionforthatinstancebeforeyouinstallthe
agent.Seethefollowingsection,ConnectionSetupforOPSorRAC.
Whentheconnectionisavailable,theconnectioninformationisautomaticallypassedtotheQSAInstallerwhen
yourunittoinstallorupgradeQSA.ThisalsohappenswhenyouconnecttotheagentinstancefromSpace
ManageranduseTools | Admin | Quest Server Agent | Manage Quest Server AgenttostarttheQSAInstaller.
Ifaconnectionisnotavailable,Oraclerandomlyconnectstoaninstance.
Note:UpgradeQSAontheinstancewhereitiscurrentlyinstalled.Ifyouwanttoupgradetheagentona
differentinstance,firstuninstalltheagentfromitscurrentinstance.
Connection Setup for OPS or RAC

TocreateaconnectiontotheinstanceforQSA,youmustconfiguretheTNSNAMES.ORAfile,theOracleNames
server,orthedirectoryservice.Youconfigureitwithinformationsuchastheservicenameandinstancename
fortheagentinstance.
ToconfiguretheTNSNAMES.ORAfilewithconnectioninformationfortheagentinstance,includeanentryfor
thisinstanceinthefile.TheCONNECT_DATAdescriptorshouldcontaintheservicenameandinstancename
fortheinstance.SIDisnotneeded.
Usethefollowingexampleasamodel:
rac11.mycompany.com=
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=srv01)(PORT=1521))
)
(CONNECT_DATA=
(SERVICE_NAME=rac1)
(INSTANCE_NAME=rac11)
)
)
Installation Errors for OPS or RAC

IfanerroroccursduringanupgradeofQSAinanactive-activeOPSorRACenvironment,eitherahostoran
instancemessagemaydisplay.
Actions to Perform When a Host Message Displays

Ahostmessagedisplaysifyouarenotconnectedtothedatabaseserverhostwheretheagentiscurrently
installed.Themessagepromptsyoutomanuallyuninstalltheolderversionoftheagent.

26
Performoneofthefollowingactions:
l Uninstalltheagentfromitscurrenthost.Theninstallitonanotherhost.(Thiscanbethehostyouare
currentlyconnectedto.)
1. ExittheQSAInstallerandSpaceManager.
2. Manuallyuninstalltheagent.
3. ConnecttothetargetinstancewithSpaceManager,runtheQSAInstaller,andinstalltheagent.
l Upgradetheagentonitscurrenthostandinstance.
2. PerformconnectionsetupfortheinstanceasdescribedinConnectionSetupforOPSorRAC.
3. Connect to the target instance with Space Manager, run the QSA Installer, and upgrade
the agent.
Action to Perform When an Instance Message Displays

Aninstancemessagedisplaysifyouarenotconnectedtotheinstancewheretheagentiscurrentlyinstalled.
Themessagepromptsyoutoconnecttotheagentinstance.Themessagetypicallydisplaysifyouhavenot
performedconnectionsetup.Inthiscase,OraclerandomlyconnectstheQSAInstallertoaninstancethatisnot
theagentinstance.
2. PerformconnectionsetupasdescribedinConnectionSetupforOPSorRAC.
3. ConnecttothetargetinstancewithSpaceManager,runtheQSAInstaller,andupgradetheagent.
QSA Server Agent Parameters

ThissectiondescribesQSAparameters.AllparametersexceptLW_TABLESPACEandWORKDIRhave
defaultvalues.TheusermustspecifyLW_TABLESPACEandWORKDIRparameters.Youcanchangedefault
valuesasneeded.
ThefollowingtablecontainsalistofQuestServerAgentparametersanddescriptions.
Parameter Description
LW_TABLESPACE LW_TABLESPACEspecifiesthetablespaceforobjectscreatedbyQSAduring
alivereorganization.OnesetofLiveReorgobjectsiscreatedforeachtableina
livereorganizationscript.Theobjectsareautomaticallydroppedafteratableis
reorganized.
LW_TABLESPACEmusthaveastandardnameandadatafilethatisatleast50
MBinsize.Thedatafilemusthaveatleast20MBofcontiguousfreespace.
Note:AtablespacemustbeselectedfortheLW_TABLESPACEparameter
evenifLiveReorgisnotlicensed.
WORKDIR WORKDIRspecifiesthemaindirectorythatFastCopy(orDBMS_DataPump)
shoulduseforthedataexportedtothefilesystemduringareorganization.If
QSAisinstalledonaremoteWindowsserver(separatefromtheSpace
Managerclientcomputer),specifythisdirectoryasifitwereonalocaldrive,for
example,C:\TEMP.EnterthedirectoryandpathinASCIIcharacters.
COMMIT_SIZE COMMIT_SIZEdeterminestheamountofdataFastCopyorFSCopyimports
fromthefilesystemintothedatabasebeforeaCOMMITisperformed.The
parametervaluecanrangefrom1MBto1024MB.Thedefaultis10MB.

27
COUNT_STAR ThisparameterdetermineswhetherQuestServerAgent(QSA)performsa
selectcount(*)ontheorig_tableandcomparesthistothenumberofrows
copied.Selectoneofthefollowingtoindicatewhetheryouwanttheagentto
performthisextracheck.
Select1toperformthecheck.Thisisthedefault.
Select0toNOTperformthecheck.
DISKSPACE_ DISKSPACE_RESERVEdetermineshowmuchspaceisreservedfor
RESERVE applicationsinWORKDIRandOVERFLOWdirectories.Unreservedspacecan
beusedbyFastCopy/DBMS_DataPumporFSCopyfordataexportedduringa
reorganization.OnceFastCopy/DBMS_DataPumporFSCopyusesall
unreservedspaceintheWORKDIRdirectory,itusesunreservedspaceinthe
firstOVERFLOWdirectory.Theparametervaluecanrangefrom1MBto1024
MB.Thedefaultis10MB.
EXPORT_BUFFER_ EXPORT_BUFFER_SIZEdeterminesthemaximumsizeoftheexportbuffer
SIZE usedbyFastCopyorFSCopy.Reorganizationsarefasterwhenexportbuffer
sizeisatleastthesizeofthelargestrowbeingreorganized.Theparameter
valuecanrangefrom32KBto1024MB.Thedefaultis1MB.
IMPORT_METHOD IMPORT_METHODdetermineshowFastCopyorFSCopyimportsdatafromthe
filesystemintothedatabase.Therearethreeoptions:
l AUTOFastCopyorFSCopyusesseveralfactors(unsupporteddata
types,rowslargerthan64KB,andSQL*Loadererrors)todetermine
whethertousethedirectorconventionalimportmethod.FastCopyor
FSCopytriesthedirectmethodfirst.Ifunsuccessful,itautomatically
switchestotheconventionalmethod.
l DIRECTFastCopyorFSCopyusesSQL*Loadersdirectpathload.
Thedirectmethodisfasterthantheconventionalbecauseitusesthe
directpathAPItomovedataandbypassesSQLprocessing.FastCopy
orFSCopyabortsthereorganization,however,ifitencountersan
unsupporteddatatype,arowlargerthan64KB,oraSQL*Loadererror.
l CONVENTIONALFastCopyorFSCopyusesOCIarrayinsertstomove
data.Althoughslowerthanthedirectmethod,theconventionalmethod
hasfewerlimitationsandassociatedproblems.Thisisthedefault.
IMPORT_BUFFER_ IMPORT_BUFFER_SIZEdeterminesthemaximumsizeoftheimportbufferthat
SIZE FastCopyorFSCopyusesduringimportswiththeconventionalmethod.The
parametervaluecanrangefrom1MBto1024MB.Thedefaultis10MB.
LW_NULL_COLUMNS Thisparameterdeterminesthemaximumnumberofcolumnstocheckfora
NULLvalue.Thedefaultis32andshouldnotbechanged.
MAX_FILE_SIZE MAX_FILE_SIZEdeterminesthemaximumsizeofFastCopyorFSCopyexport
files,whichareusedforthedataexportedfromthedatabasetothefilesystem.
(FastCopyfilesareinaproprietaryformat.)Whenthefirstfilereachesthe
maximumsize,asecondfileiscreatedautomatically,andsoon.Theparameter
valuecanrangefrom1MBto1024MB.(Itmustbelessthanyoursystems
defaultmaximumfilesize.)Thedefaultis100MB.
MAX_HISTORY_AGE MAX_HISTORY_AGEdeterminesthemaximumnumberofdaysthatrecords
arekeptintheQUEST_SCRIPT_HISTORYtable.Thetablecontainsahistoryof
scriptexecutionbyQSAandisusedtoassociatescriptlogswiththeirscripts.
Theparametervaluecanrangefrom0to32765.(Itshouldbegreaterthanthe
valueforMAX_LOG_AGE.)Thedefaultis365.

28
MAX_LOG_AGE MAX_LOG_AGEdeterminesthemaximumnumberofdaysthatscriptexecution
logsandQSAlogarekept.Scriptlogscanbeusedtotroubleshootscript
executionbytheagent.Theagentlog(QEXECD.LOG)canbeusedto
troubleshootallagentactivity.YoucanviewlogsfromSpaceManagers
Script/JobMonitor.YoucansendthemtoQuestSoftwareSupport.The
parametervaluecanrangefrom0to365.(0retainslogsuntilSpaceManager
isuninstalled.)Thedefaultis30.
MULTIBLOCK_READ_ MULTIBLOCK_READ_COUNTdeterminesthenumberofdatablocksthat
COUNT OraclereadsatonetimeduringaFastCopyreorganization.Thenumbershould
beamultipleofthesizeofyouroperatingsystemreadbufferdividedbyyour
databaseblocksize.Forexample,ifyouroperatingsystemreadbufferis256
KBandyourdatabaseblocksizeis8KB,settheparametertoamultipleof32
KB.Theparametervaluemustbegreaterthanorequalto0.Thedefaultis100.
OVERFLOW_DIR_01 OVERFLOW_DIRspecifiesdirectoriesthatcanbeusedinadditiontothe
thruDIR_05 WORKDIRdirectoryforthedataFastCopy/DBMS_DataPumpexports.
FastCopy/DBMS_DataPumpusesoverflowdirectorieswhenWORKDIRisfull.
Youcanspecifyupto5directories.Anewdirectoryisusedwhenthelastone
usedisfull.DirectoryandpathnamesmustbeenteredinASCIIcharacters.
Note:Eachoverflowdirectorymustbeonadifferentdisk.TheWORKDIR
diskmustnotbeusedforanOVERFLOW_DIR.
SENDMAIL Parameters
SENDMAILparametersallowyoutoconfigureQSAtoautomaticallysendemailnotificationswhenscheduled
scriptexecutionfails.Notificationsidentifythefailurereason,scriptname,executionstartandstoptimes,
databaseserverhostname,anddatabaseOracleSID.ThesubjectfielddisplaysScriptFailureNotice!
SENDMAILincludesthefollowingparameters(allexceptSENDMAIL_TO1requirevalues).
QSA Parameter Description
SENDMAIL_ Specifiesthedomainnameofthemailserverorrelayserver.Forexample:
DOMAIN yourcompany.com.
SENDMAIL_HOST Specifiestheaddressorfully-qualifiednameofthemailserverorrelayserver
host,forexample:www.quest.com.
SENDMAIL_PORT Specifiestheportnumberonwhichthemailserverorrelayserverislistening.
SENDMAIL_FROM Specifieswhosenttheemailnotification.Thetextstringyouentershouldbethe
emailaddressofanindividualorgroup,suchas
Administrator@yourcompany.com.
SENDMAIL_TO Specifiestheemailrecipient.Mustbetheemailaddressofanindividualorgroup,
suchasDBA@yourcompany.com.Theaddressmustbevalid.Onlyoneaddress
maybeentered.
SENDMAIL_TO1 Specifiesasecondrecipientforemailnotifications.
Tospecifythreeormorerecipients,insertarowforeachrecipientintheQUEST_
EXEC_PARAMETERtable,whereNAMEisSENDMAIL_TO#andVALUEisa
validemailaddress.EachSENDMAIL_TO#entryshouldincrementby1;for
example,SENDMAIL_TO3,SENDMAIL_TO4.Ifthereisabreakinthenumber
sequence,emailsarenotsenttorecipientsafterthebreak.Ifyoudeletearecipient
row,updatetheNAMErowsthatfollowsothenumbersequenceispreserved.You
canspecifyamaximumof99recipients.

29
Note:ForQSAtosendemail,OraclesUTL_SMTPpackagemustbeinstalledonthedatabaseserver.The
packagemusthaveaccesstoanSMTPmailserverorrelayserver.
SNMP Trap Parameters

ThefollowingparametersareusedtoconfigureSimpleNetworkManagementProtocol(SNMP)Trap
notifications.
QSA Parameter Description
SNMP_TO_HOST EnterthehostnamefortheSNMPmonitor.
SNMP_PORT EntertheportnumberthattheSNMPmonitorislisteningon.
SNMP_COMMUNITY EnterthenameofyourSNMPcommunity(oranyuniquestringvalue).
Additional Notification Parameters

AfterenablingSMTPemailorSNMPtrapnotificationmethods,youcanspecifyadditionalnotificationeventsby
configuringthefollowingparameters.
SEND_GROUP_STATUS Sendnotificationofastaticchangetothegroupstatus.
SEND_SCRIPT_START Sendnotificationwhenscriptstarts(101).
SEND_SCRIPT_RESTART Sendnotificationwhenscriptisrestarted(104).
SEND_SCRIPT_ Sendnotificationwhenscriptisunscheduled(110).
UNSCHEDULED
SEND_SCRIPT_COMPLETE Sendnotificationwhenscriptcompletes(210).
SEND_SCRIPT_CANCELLED Sendnotificationwhenscriptiscancelled(310).
SEND_SCRIPT_ABORT Sendnotificationwhenscriptaborts(320).
SEND_SCRIPT_HALTED Sendnotificationwhenscriptishalted(370).
SEND_SCRIPT_SCHEDULED Sendnotificationwhenascriptisscheduled(410).
SEND_LR_WAIT_WINDOW SendnotificationwhenaLiveReorgiswaitingforwindow(620).
SEND_LR_IN_WINDOW SendnotificationwhenaLiveReorgisinthewindow(621).
SEND_LR_WAIT_APPROVAL SendnotificationwhenaLiveReorgiswaitingforapproval(630).
SEND_LR_APPROVED SendnotificationwhenaLiveReorgisapproved(631).
SEND_LR_START SendnotificationwhenaLiveReorgstarts(710).
SEND_LR_RESTART SendnotificationwhenaLiveReorgrestarts(715).
SEND_LR_COPY_START SendnotificationwhenaLiveReorgtablecopystarts(720).
SEND_LR_COPY_COMPLETE SendnotificationwhenaLiveReorgtablecopycompletes(730).

30
SEND_LR_SWITCH_START SendnotificationwhenaLiveReorgstartstoswitch(740).
SEND_LR_SWITCH_ SendnotificationwhenaLiveReorgswitchcompletes(750).
COMPLETE
SEND_LR_COMPLETE SendnotificationwhenaLiveReorgcompletes(760).
Settingthisparametersendsanemailwithoutaresultsreport.To
includearesultsreport,useoneoftheSEND_LR_COMPLETE
parameterslistedbelow.
SEND_LR_COMPLETE Options
UsethefollowingparameterstospecifythetypeofresultsreporttoincludewhenusingtheSEND_LR_
COMPLETEparameter.
Parameter Results Report Type Description
SEND_LR_COMPLETE Noreport Noreport
SEND_LR_COMPLETE_ Detailobjects, Thisreportisthemostdetailedandincludes

DATA summarybyobject theobjectdetails,detailedstoragedata,anda
typeandtotalsavings storagedatasummarybyobject.
reports.
SEND_LR_COMPLETE_ Summarybyobject Thisreportdeliversasummaryofthestorage

SUM typeandtotalsavings databyobject.
reports.
SEND_LR_COMPLETE_ Totalsavingsreport. Thisreportliststhestoragedatatotalsonly.

TOTAL
Locks Reporting Parameters

Usethefollowingparameterstoconfigureadvancedoptionsforlocksreporting.
LOCKS_ SelectYEStoenablelocksreporting.
REPORTING Default: NO
Note:Whenyoudisablelocksreporting,thevaluesselectedfortheother
parametershavenoeffect.
LOCKS_ SelectYEStoenablereportingoflocksforcanceledjobs.
CANCELED_JOBS Default: YES
Note:SpaceManagerreportslocksheldbyOraclesessionsforcanceled
jobstotheqexecd.logfilebeforecancelingthejob.
LOCKS_SCRIPT_ SelectYEStoenablereportingoflockswhenatablelockoraT-Lockfailswitha
LOG resourcebusyerror(ORA-0054).
Default: YES

31
Note:SpaceManagerreportstheselockstothescriptexecutionlogthatyou
canviewusingtheScript/JobMonitor.
LOCKS_SYSTEM_ SelectYEStoenablereportingoflockstoasystemfile.
FILE_LOGS Default: NO
LOCKS_SYSTEM_ SelectYEStoappendthesystemfilecreatedforlocksreporting.
FILE_APPEND Default: YES
Note:Ifyoudisablethisparameter,thesystemfileonlycontainsinformation
forthemostrecentlockreported.
LOCKS_MAXIMUM_ Enteravalueforthenumberoftimestoreportlocksforaspecifictable.
REPORTS Range: 1 to 999
Default: 3
Tip:Asinglelockmayberetiredthousandsoftimesduringasingle
reorganization.Usethedefaultvaluetominimizechangestothesystemfile.
Note:SpaceManagercreatessystemfilesintheQSAlogfiledirectorywiththefollowingnaming
convention:<owner>.<folder>.<script>.<jobnumber>.lok

32
7
Uninstall Space Manager and Server
Agent
Overview - Uninstall Space Manager

ThischapterdescribeshowtouninstallSpaceManagerandQSA.
TouninstallSpaceManager,youremoveservercomponentsandQSAfromeachdatabaseinwhichtheyare
installed.YoualsoremovetheSpaceManagerclientanddemonstrationdata,ifinstalled.
Themainstepsintheuninstallprocessareasfollows:
1. ConnecttothedatabaseastheDBAthatinstalledtheservercomponents.
2. UninstallSpaceManagerservercomponents.
3. Manuallydeletethedatafilesforthetwodemonstrationtablespaces.
4. ConnecttothedatabaseastheDBAthatinstalledtheagent.
5. UninstalltheQuestServerAgent.
6. UninstalltheSpaceManagerclient.
Note:Makesurethatnoscriptsarerunningorscheduledtorunwhenuninstallingtheservercomponents
andtheServerAgent.
Oracle Upgrade
IfyouplantoupgradefromoneversionofOracleDatabasetoanother,uninstallQSAfirst.AfterthenewOracle
databaseisinstalled,reinstalltheserverandtheQSAagent.
When upgrading Oracle

1. UninstalltheServerAgent.
a. FromtheSpaceManagermainmenu,selectTools | Admin | Quest Server Agent | Manage
Quest Server Agent Installation.
b. SelectRemove Quest Server AgentandcompletetheServerAgentInstallerwizard.See
UninstalltheServerAgentonpage34formoreinformation.
2. UpgradeOracleDatabase.
3. Reinstallservercomponents.
a. ReturntoSpaceManagerandfromthemainmenuselectTools | Admin | Reinstall Space
Manager Server Objects.ThisrecreatesalltheSpaceManagerviewsandtriggersthe
installationoftheServerAgent.

33
Uninstall Space Manager and Server Agent
b. Wheninstallationoftheservercomponentsisfinished,theServerAgentInstalleropensand
promptsyoutoinstalltheagent.
4. InstalltheServerAgent.ThisensuresthatthecorrectOraclelibrariesareusedwhenyouupgradeSpace
Manager.SeeInstallorUpgradeServerAgentonUNIXorLinuxonpage22formoreinformation.
Uninstall (Remove) Server Objects

TheRemove Space Manager Server Objectsfunctioncanbeusedtouninstallservercomponentsfroma
databasewheneverneeded.ThisfunctiondropsallSpaceManagerobjectsfromadatabase,including
statisticstablesandscripttables.Italsodropsthedemonstrationdata.
Note:Datafilesfordemonstrationdatatablespacesmustberemovedfromtheservermanually.
ServercomponentsmustbeuninstalledbytheDBAthatinstalledthem.Theymustberemovedindividuallyfrom
eachdatabaseinwhichtheyareinstalled.
Normally,demonstrationdataisautomaticallyremovedalongwithservercomponents.However,thedataisnot
removedwhendemonstrationtablespacescontainobjectsthatarenotownedbythedemonstrationuser.To
ensurethatdemonstrationdataisremoved,relocatenon-demonstrationobjectsbeforeyouuninstalltheserver
components.
Afterdemonstrationdataisuninstalled,manuallydeletethedemonstrationdatafiles,SPCDEMO01_nn.dbfand
SPCDEMO02_nn.dbf.
To uninstall (remove) server objects and demonstration data

1. RuntheSpaceManagerclientandconnecttothetargetdatabaseastheDBAthatinstalledserver
components.
2. Touninstallservercomponents,selectTools | Admin | Remove Space Manager Server Objects.If
demonstrationdataisinstalled,itisremovedalongwithservercomponents.
Note:AfterservercomponentsandQSAareuninstalled,manuallydeletedemonstrationdatafiles,
SPCDEMO01_nn.dbfandSPCDEMO02_nn.dbf.
3. IftheuninstallprogramdetectsscriptsthatarebeingexecutedbyQSA,youmustcanceltheuninstall.
Youcanfinishtheuninstallafterscriptexecutioniscomplete.
4. Iftheuninstallprogramdeterminesthatoneormorescriptsarescheduledtorun,amessagedisplays
thedateandtimeforthefirstscriptandasksifyouwanttocontinuetheuninstall:
l Ifyouwanttocontinueandaresurethattheuninstallprocesswillfinishbeforethefirstscript
runs,clickYes.
l Ifyouwanttocanceltheuninstall,clickNo.
5. Onceverificationsarecomplete,aconfirmationmessageexplainsthatallSpaceManagerobjectswillbe
removedfromtheserver.ClickYes.TheSQLExecdialogdisplaystheuninstallprogressandstatus.
6. Afterservercomponentsareuninstalled,theQSAInstallerdisplayssothatyoucanremovetheagent.
SeeUninstalltheServerAgentonpage34formoreinformation.
Uninstall the Server Agent

TheServerAgentmustbeuninstalledindividuallyfromeachdatabaseforwhichitisinstalled.Itmustbe
uninstalledbytheuserthatinstalledit.
Note:IfyouusedtheQSAInstallerorthemanualinstallmethodtoinstalltheagent,usethesamemethodto
uninstallit.

34
Uninstall QSA from UNIX or Linux
ThissectiondescribeshowtouninstallQSAfromanOracledatabaseonaUNIXorLinuxserverwiththeQSA
Installer.YoucanusetheQSAInstallerifyouhavebothSSHandSFTPaccesstothedatabaseserver.Ifyoudo
nothaveboth,youmustuseamanualprocedure.See"ManuallyUninstallServerAgentfromUNIXorLinux"in
theSpace Manager Installation Guideformoreinformation.
To uninstall the agent from UNIX or Linux

1. RuntheSpaceManagerclientandconnecttothetargetdatabaseastheDBAthatinstalledQSA.
Note:Afteruninstallingtheservercomponents,theServerAgentInstallerautomaticallyopenstothe
Logonpage.Skipaheadtostep4.
2. ToruntheQSAInstaller,selectTools | Admin | Quest Server Agent | Manage Quest Server Agent.
3. IntheSelectInstallationTypewindow,selectRemove Quest Server Agent,andthenclickNext.

4. IntheLogontoServerwindow,entertheusernameandpasswordfortheUNIXorLinuxaccountthat
installedtheagent.Enterthehostservernameifitisnotdisplayed.ClickNext.
5. IntheUninstallQuestServerAgentwindow,clickRemove.
7. IfyoudidnotuninstallQSAasroot,logintotheserverasrootandruntheROOT_UNINSTALL.SHscript
asfollows.UseSIDforthetargetdatabase.
#/tmp/root_uninstall.shSID
Uninstall QSA from Windows

ThissectiondescribeshowtouninstalltheServerAgentfromalocalorremoteWindowsserver.
Note:TheagentmustberunningwhenyouuninstallitfromaWindowsserver.Youcanstarttheagentfrom
theWindowsServiceswindow,orrunQSAStart.cmdinthe\binfolderundertheagentinstallfolder
(<installation path>\QuestServerAgent\<ORACLE_SID>\bin).
TomanuallyuninstalltheServerAgentfromWindows,see"ManuallyUninstallServerAgentfromWindows"in
theSpace Manager Installation Guide.
Local Windows Server

TouninstallQSAfromalocalWindowsserver,youcanruntheServerAgentInstallerfromtheSpaceManager
application.
To uninstall QSA from a local Windows server

1. RuntheSpaceManagerclientandconnecttothetargetdatabaseastheDBAthatinstalledQSA.
Note:Afteruninstallingservercomponents,theServerAgentInstallerautomaticallyopens.Skip
aheadtostep3.
2. ToruntheQSAInstaller,selectTools | Admin | Quest Server Agent | Manage Quest Server Agent.

3. IntheSelectInstallationTypewindow,selectRemove Quest Server Agent,andthenclickNext.
4. IntheUninstallQuestServerAgentwindow,clickRemove.

35
Remote Windows Server
TouninstallQSAfromaremoteWindowsserver,youmustcopytheServerAgentInstallerfromtheSpace
ManagerapplicationdirectorytotheWindowsserver.(InstallingQSAontheremoteWindowsserveralso
requiredcopyingtheServerAgentInstallertotheWindowsserver.)
To copy the QSA Installer to remote Windows server

1. NavigatetotheSpaceManagerapplicationdirectory:
2. OpentheQuestServerAgentfolderandcopyQSA_version_build-QSASetup.exetotheWindowsserver.
To uninstall QSA from a remote Windows server

1. LogintotheremoteWindowsserverasamemberoftheWindowsAdministratorsGroup.
2. AftercopyingtheServerAgentinstaller(QSA_version_build-QSASetup.exe)totheWindowsserver,
double-clickQSA_version_build-QSASetup.exetorunit.
3. Followtheinstructionsintheprevioussection,TouninstallQSAfromalocalWindowsserverbeginning
withstep3.
Uninstall the Space Manager Client

ThissectiondescribeshowtouninstalltheSpaceManagerclient.
To uninstall the Space Manager client

1. Exitfromallapplications,includingtheSpaceManagerclient.
2. UninstallSpaceManagerusingyourWindowsadd/removeprogramsfeature.
l Forexample,inWindows7,selectControl Panel | Programs | Programs and Features |
Uninstall a program.
3. SelectSpaceManagerandthenclickUninstall.
4. ThisremovesallSpaceManagerfiles,folders,andregistrykeysfromyoursystem.

36
8
Manually Install/Uninstall Server Agent
Overview - Manually Install and Uninstall

Server Agent
ThischapterdescribeshowtomanuallyinstallanduninstallQSAforOracledatabasesonUNIX,Linux,and
Windowsdatabaseservers.
When to Use Manual Installation

UsemanualinstallationwhenSSHandSFTPareunavailable.ManualinstallationoftheQuestServerAgent
(QSA)isanalternativetoinstallationwiththeQSAInstaller.IfyoudonothavebothSSHandSFTPaccesstothe
UNIXandLinuxservers,youmustinstallanduninstalltheagentmanually.
Manually Install Server Agent on UNIX or

Linux
ThissectiondescribeshowtomanuallyinstallorupgradeQSAonUNIXandLinuxservers.Youperforma
manualinstallationwiththeINSTALL.SHscriptandamanualuninstallwiththeUNINSTALL.SHscript.Both
scriptsarerunfromthedatabaseserver.
Caution: Before you manually install QSA, set the SQL*Plus PAUSE command to OFF (the default
setting). If another setting is used, such as ON or PAGE, manual installation fails. After installation is
complete, you can set the PAUSE command to any value.
To manually install (or upgrade) QSA on UNIX and Linux

1. Fromthedatabaseserver,loginusingtheUNIXorLinuxaccountchosentoinstallQSA.
2. Next,copytheQSAinstallationfilesfromtheSpacedManagerapplicationdirectory.Navigatetothe
SpaceManagerclientapplicationdirectory:
3. OpentheQuestServerAgentfolderintheapplicationdirectoryandselecttheQuestServerAgentfile(a
TARfile)foryouroperating-systemversionandOracleversion.EachTARfilehasthefollowingnaming
format:QSA_version_build-operating system-OS version-CPU type-Oracle version.tar.Z
ThencopythefiletotheUNIX/Linuxserver.
Note: If you download multiple TAR files to the same server, download each file to a
different directory.
4. ToextractagentinstallationfilesfromtheServerAgentTARfile,usethefollowingcommand(filenameis

37
thenameoftheTARfile):
# uncompress < filename.tar.z tar xvf -
5. Torunthemanualinstallscriptfromthedownloaddirectory,usethefollowingcommandandcases:
# ./Install.sh
6. AttheORACLE_SIDprompt,entertheSIDforthetargetdatabase.
7. AttheORACLE_HOMEprompt,pressEntertoacceptthepathtotheOraclehomedirectoryforthe
targetdatabase.
8. LogintoOracleastheDBAchosentoinstalltheagent(ifthisisanupgrade,loginastheDBAthat
installedtheagent):
l AttheOracle login nameprompt,entertheaccountusername.
l AttheOracle passwordprompt,entertheaccountpassword.
9. Ifthisisafirst-timeinstallation,specifythetablespaceforagenttables(thetablespaceusedforSpace
Managerobjectsisrecommended):
l Tousethetablespaceselectedbydefault,pressEnterattheTablespaceprompt.
l Touseadifferenttablespace,enterthenameattheTablespaceprompt.ThenpressEnter.
10. Specifyanaccountunderwhichtheagentshouldrun(runningaccount):
l Touseoracle,thedefaultrunningaccount,pressEnterattheUser to run asprompt.
l Touseanotheraccount,entertheaccountloginnameattheUser to run asprompt.Then
pressEnter.
11. Afteryoulogintotheoperatingsystem,oneoftwomessagesmightappear:
l Environment not supported/cannot proceedBothyourOracleversionandoperatingsystem
versionarenotsupportedTheagentcannotbeinstalled.Youmustupgradetoasupported
Oracleversionandasupportedoperatingsystem.SeeSystemRequirements"intheSpace
Manager Release Notes.
l Environment not supported/can proceedEitheryourOracleversionoroperatingsystem
versionisnotsupported.Inmostcases,asupportedversionofOracleisbeingrunonan
unsupportedoperatingsystemversion.Althoughyoucanproceedwiththeinstallation,youmay
haveproblems.
12. Ifthisisafirst-timeinstallation,specifythebaseinstalldirectory:
l Tousethedefaultbaseinstalldirectory,pressEnterattheInstallation directoryprompt.The
defaultis$ORACLE_HOME.
l Touseadifferentbaseinstalldirectory,enterthedirectorynameandpathattheInstallation
directoryprompt.ThenpressEnter.
Note:Afteryouspecifythebaseinstalldirectory,/Quest/QSA/$ORACLE_SIDisaddedtothe
directorypath.
13. Tobegintheagentinstallationorupgrade,enterYattheProceedprompt.
14. FromtheQuestServerAgentParameterswindow,specifyagentparametervaluesforthetarget
database.YoumustentervaluesforWORKDIR(usedforFastCopy)andLW_TABLESPACE(usedfor
livereorganizations;requiredevenifLiveReorgisnotlicensed).Respondtopromptsasfollows:
a. AttheDo you wish to modify any of these parametersprompt,enterY.
b. AtthePlease enter the ID number of the parameterprompt,entertheIDnumberofthe
parameteryouwanttomodify.
c. Attheparameterprompt,enterormodifytheparametervalue.
d. Repeatstepsathroughcforeachparameteryouwanttoset.

38
e. AttheDo you wish to modify any of these parametersprompt,enterNwhenyouarefinished.
f. At the Do you wish to save the parameter changes youve made prompt, enter Y to
save all new values. (To revert to previous values, enter N.) The Parameters Updated
message displays.
15. WhentheCompletedmessagedisplays,QuestServerAgentinstallationisfinished.
To instruct QSA to restart automatically after a server restart

IfyouwanttheServerAgenttostartautomaticallyeachtimetheserverisstarted,performthefollowingsteps:
1. LogintoUNIXorLinuxasroot.
2. Changetotheagentinstallationdirectoryusingthefollowingcommand:
# cd /$ORACLE_HOME/Quest/QSA/SID/inst
3. Runthefollowingroot.shscript:
# ./root.sh
Manually Install Server Agent on Windows

UsethefollowingproceduretomanuallyinstallQSAonWindowsservers.
To install (or upgrade) QSA manually on Windows servers

1. UseoneofthefollowingmethodstonavigatetotheSpaceManagerclientapplicationdirectory:
2. OpentheQuestServerAgentfolderintheapplicationdirectoryandselecttheQuestServerAgent
executablefileappropriateforyourWindowsenvironment:
l Fora32-bitWindowsenvironment,useQSA_version_build-Win32.exe.
l Fora64-bitWindowsenvironment,useQSA_version_build-Win64.exe.
3. Usebinarymodetocopytheappropriateexecutabletotheserver.Copythefiletoanemptydirectoryon
yourserver.
4. Runtheexecutableandextractthesefilestoatemporarydirectory.
Note:Makesurethetemporarydirectoryisemptybeforeyouextractthefiles.
5. Edittheqsaparms.batfile.Seetheexampleinthefollowingsection,Sampleqsaparms.batfile."
Note:Theqsaparms.batfilecontainsbriefinstructionsonwhatyoushouldchange.
6. ExecuteInstall.bat.
Note:Forbestresults,usethecommandwindowtoexecutethisfile.Thiswillallowyoutosee
progressanderrormessages.
7. AfteryouinstalltheQSAserverandverifythatitisworking,completelyremovetheinstallationfilesfrom
thetemporarydirectory.
Sample qsaparms.bat file

Somebriefinstructions(notes)arecontainedintheqsaparms.batfile.Thefollowingaredescriptionsforafew
keyparameters.

39
l QSA_BASE_DIRUsethisparametertospecifyaneworexistinginstallationbasedirectory."Quest"is
thedefault.
l TABLE_SPACEUsethisparametertospecifytheServerAgentinstallationtablespace.Itmustalready
exist.Usuallyitisthesametablespacethatisusedforserverobjects.
l LW_TBLSPCUsethisparametertospecifythetablespaceforobjectscreatedbyQSAduringalive
reorganization.
Parametersthatrequireeditingareinbold.
rem *******************************************
rem qsaparms.bat: QSA manual installation
rem script parameter file
rem
rem *******************************************
rem *******************************************
rem START USER CONFIGURABLE SECTION
rem *******************************************
rem *******************************************
rem *******************************************
rem set the values for the following variables
rem any default values have been pre-assigned
rem *******************************************
rem
rem QSA_GUI when set to YES will cause the
rem installer to not pause
rem
set QSA_GUI=NO
rem
rem NOTE: Setting qsagetparms to NO,
rem will cause this script to ignore
rem parms contained in the database
rem and will use what is defined here
rem for upgrades and uninstalls.
rem
rem set qsagetparms=NO
rem *********************
set qsagetparms=YES
rem *********************
rem
rem ***********************
rem ***********************
rem Set qsaparms value to
rem YES after you have
rem finished editing this
rem script.
rem ***********************
rem ***********************
rem
set qsaparms=NO
rem
rem ***********************
rem ***********************
rem Set qsaforce value to
rem YES if the install
rem fails because the platform
rem is not correct. qsaforce
rem will prevent the platform
rem validation from executing.
rem ***************************
rem ***************************
rem

40
set qsaforce=NO
rem
rem
rem
rem Oracle SID
rem ***************
set ORACLE_SID=orcl
rem ***************
rem
rem Oracle HOME
rem *********************
set ORACLE_HOME=C:\Oracle
rem *********************
rem
rem Oracle USER (SpaceManager Oracle User)
rem ******************
set ORACLE_USER=quest
rem ******************
rem
rem Oracle user's PASSWORD
rem *******************
set ORACLE_PASS=quest
rem *******************
rem
rem QSA Windows user (this user does not need to exist)
rem ****************
set QSA_USER=QSA_DBA
rem ****************
rem
rem QSA Installation Base Directory
rem *******************
set QSA_BASE_DIR=\Quest
rem *******************
rem
rem QSA Base Installation Drive
rem *****************
set QSA_BASE_DRIVE=C:
rem *****************
rem
rem QSA Installation Tablespace
rem *****************
set TABLE_SPACE=TOOLS
rem *****************
rem
rem QSA Work Directory Parameter
rem ********************
set QSA_WORK_DIR=C:\temp
rem ********************
rem
rem QSA LW Tablespace Parameter
rem ***************
set LW_TBLSPC=TOOLS
rem ***************
rem
rem ** NOTE **
rem if you want to changes storage parameters
rem see "qsastor.bat"
rem
rem do not change anything bellow this line
rem
rem *******************************************
rem *******************************************
rem END OF USER CONFIGURABLE SECTION
rem *******************************************
rem *******************************************
set TABLE_EXISTS=%ORACLE_USER%

41
rem ** the version of quest script required **
set QSA_SCRIPT_VERS=none
rem ** QSA versions **
set QSA_VERSION=none
set QSA_BASE_VERSION=none
Manually Uninstall Server Agent from

UNIX or Linux
UsethefollowingproceduretomanuallyuninstallQSAfromOracledatabasesonUNIXandLinuxservers.
To manually uninstall QSA from UNIX or Linux

1. Fromyour databaseserver, login toUNIX orLinux underthe operating-systemaccount that
installedQSA.
2. Usethefollowingcommandtochangetotheagentinstalldirectoryforthetargetdatabase(the
commanddisplaysthedefaultinstalldirectory):
# cd /$ORACLE_HOME/Quest/QSA/$ORACLE_SID/inst
3. Usethefollowingcommandandcasestorunthemanualuninstallscript:
# ./Uninstall.sh
4. AttheORACLE_SIDprompt,entertheSIDforthetargetdatabase.
5. AttheORACLE_HOMEprompt,pressEntertoacceptthepathtotheOraclehomedirectoryforthetarget
database.ThisisenteredautomaticallyafteryouentertheSID.
6. AttheOracle login nameprompt,entertheusernameoftheDBAthatinstalledtheagent.
7. AttheOracle passwordprompt,enterthepasswordoftheDBA.
8. IntheReadytoUninstallwindow,enterYattheProceedprompttoremovetheagent.
9. Ifyoudidnotuninstalltheagentasroot,logintoUNIXorLinuxasrootandusethefollowingcommand
toruntheROOT_UNINSTALL.SHscript($ORACLE_SIDistheSIDforthetargetdatabase):
# /tmp/root_uninstall.sh $ORACLE_SID
Manually Uninstall Server Agent from

Windows
IfyouinstalledQSAmanuallyonaWindowsserver,youmustalsousethemanualuninstallprocedureto
uninstalltheagent.
To manually uninstall QSA from Windows

1. Locatetheuninstallbatchfile(uninstall.bat).
Note:Duringthemanualinstallationprocess,theuninstallfilesarecopiedtotheServerAgent
installationdirectory(\inst).
2. Rununinstall.bat.

42
About Us
We are more than just a name

Weareonaquesttomakeyourinformationtechnologyworkharderforyou.Thatiswhywebuildcommunity-
drivensoftwaresolutionsthathelpyouspendlesstimeonITadministrationandmoretimeonbusiness
innovation.Wehelpyoumodernizeyourdatacenter,getyoutothecloudquickerandprovidetheexpertise,
securityandaccessibilityyouneedtogrowyourdata-drivenbusiness.CombinedwithQuestsinvitationtothe
globalcommunitytobeapartofitsinnovation,andourfirmcommitmenttoensuringcustomersatisfaction,we
continuetodeliversolutionsthathavearealimpactonourcustomerstodayandleavealegacyweareproudof.
Wearechallengingthestatusquobytransformingintoanewsoftwarecompany.Andasyourpartner,wework
tirelesslytomakesureyourinformationtechnologyisdesignedforyouandbyyou.Thisisourmission,andwe
areinthistogether.WelcometoanewQuest.YouareinvitedtoJointheInnovation.
Our brand, our vision. Together.

Ourlogoreflectsourstory:innovation,communityandsupport.Animportantpartofthisstorybeginswiththe
letterQ.Itisaperfectcircle,representingourcommitmenttotechnologicalprecisionandstrength.Thespacein
theQitselfsymbolizesourneedtoaddthemissingpieceyoutothecommunity,tothenewQuest.
Contact Quest
Forsalesorotherinquiries,visitwww.quest.com/company/contact-us.aspxorcall1-949-754-8000.
Technical Support Resources

TechnicalsupportisavailabletoQuestcustomerswithavalidmaintenancecontractandcustomerswhohave
trialversions.YoucanaccesstheQuestSupportPortalathttps://support.quest.com.
TheSupportPortalprovidesself-helptoolsyoucanusetosolveproblemsquicklyandindependently,24hours
aday,365daysayear.TheSupportPortalenablesyouto:
l SubmitandmanageaServiceRequest
l ViewKnowledgeBasearticles
l Signupforproductnotifications
l Downloadsoftwareandtechnicaldocumentation
l Viewhow-to-videos
l Engageincommunitydiscussions
l Chatwithsupportengineersonline
l Viewservicestoassistyouwithyourproduct

43
About Us

SpaceManager 8.3 InstallGuide

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SpaceManager 8.3 InstallGuide

Enviado por

Direitos autorais:

Formatos disponíveis

SpaceManager

IMPORTANT, NOTE, TIP, MOBILE, VIDEO:Aninformationiconindicatessupportinginformation.

Architecture and Requirements 5

Install Space Manager Client 12

Licensing and Connections 14

Install Space Manager Server Componenets 17

Install Server Agent 21

Space Manager with LiveReorg 8.3 Installation Guide

Uninstall Space Manager and Server Agent 33

Manually Install/Uninstall Server Agent 37

Space Manager with LiveReorg 8.3 Installation Guide

Space Manager Client

Space Manager Server Components

Space Manager with LiveReorg 8.3 Installation Guide

Space Manager User Requirements

Server Objects Installation

Installation DBA in Oracle 12c

Space Manager with LiveReorg 8.3 Installation Guide

Server Agent Installation

UNIX and Linux Privileges

Space Manager with LiveReorg 8.3 Installation Guide

To grant privileges from Space Manager

Global Operation Requirements

User Name and Password Requirements

Character Set Requirements for Agent Installation

Installation Factor UNIX and Linux Windows

Hostnamefordatabase MustbeaDNSname;IDNnames MustbeaDNSname;IDNnames

Servicenamefordatabase Canusedatabasecharactersetor Canusedatabasecharactersetor

UsernameforOracleDBA Canusedatabasecharactersetor Canusedatabasecharactersetor

Space Manager with LiveReorg 8.3 Installation Guide

PasswordforOracleDBA Canusedatabasecharactersetor Canusedatabasecharactersetor

Usernameforoperating MustuseASCII Nocharacter-setrequirement

Passwordforoperating MustuseASCII Nocharacter-setrequirement

Tablespacenamesforagent Canusedatabasecharactersetor Canusedatabasecharactersetor

Installdirectoryandpathfor MustuseASCII MustuseASCII

Workdirdirectoryandpath MustuseASCII MustuseASCII

Overflowdirectoryandpaths MustuseASCII MustuseASCII

Space Manager with LiveReorg 8.3 Installation Guide

Overview - Installation Process

Smart Start for Installing Space Manager

Space Manager with LiveReorg 8.3 Installation Guide

4. Install the Space Manager client.ToinstalltheSpaceManagerclientonaWindowscomputer,usethe

Space Manager with LiveReorg 8.3 Installation Guide

Install Space Manager Client

Upgrading Space Manager

Configure DEP if Enabled

Install or Upgrade the Space Manager Client

Space Manager with LiveReorg 8.3 Installation Guide

Space Manager with LiveReorg 8.3 Installation Guide

To update a license key

Before creating a new connection

To create a new database connection

Space Manager with LiveReorg 8.3 Installation Guide

Space Manager with LiveReorg 8.3 Installation Guide

To modify connection properties

Working with Multiple Connections

To set the current connection (or switch connections)

Space Manager with LiveReorg 8.3 Installation Guide

Overview - Install Server Components

When to Install/Upgrade/Reinstall Server Components

Install Server Components After Initially Installing the Client

Upgrade Server Components After Upgrading the Client

Space Manager with LiveReorg 8.3 Installation Guide

Reinstall Server Components after Upgrading the Oracle Database