Some environments do not allow the use of the 'oracle' user to run the Performance Analysis (PA) StealthCollect agent. How to install PA using a non-dba account?
On the Monitored Host, the /quest_sc_collector/var/stderr.quest_sc_collector shows:
DB_State changed new state 4
DB_IS_DOWNCollector Agent cannot connect to the Oracle SGA
The installation will require three phases:
1: log in with the installing user and start PA installation with non-oracle user
in this phase the installation will begin, PA framework (skeleton files and directories) will be unzipped and when it comes to agent installation the non-oracle user wouldn't be able to provide with the oracle user name and password, and thus installation will fail
2: log in with oracle user and run quest_launcher_user
In this phase oracle user will be logged in and run the special PA quest_launcher_user script and will modify the needed files. This process will enable the installing user to complete the installation without being asked by PA to provide with oracle user and password
3: log in with installing user and complete the PA installation
After the slight modifications done by the oracle user, the installing user will be able to complete the installation without being aware of the oracle user/password.
We will now go over each phase in details.
1: log in with the installing user and start PA installation with non-oracle user
a.Log in with installing user
b.Start PA installation (run the LSI binary file)
c.When the installation comes to the point where it asks for oracle user/password, CTRL+C it.
d.Stop PA processes, by running <PA installation dir>/agents/bin/quest_launcher_daemon stop
2: log in with oracle user and run quest_launcher_user
a. Log in with oracle user
b. cd into <PA installtion directory>/agents/bin
c. Run quest_launcher_user script.
Two files should be created:
-quest_launcher.u<oracle_user_id>
-quest_launcher.g<oracle_user_group_id>
Note: ensure that quest_launcher.g101 is created
d. Change group and owner to the files created as demonstrated below:
-chown oracle quest_launcher.g<oracle_user_group_id>
-chgrp oracle_user_group quest_launcher.g<oracle_user_group_id>
-chown oracle quest_launcher.u<oracle_user_id>
-chgrp oracle_user_group quest_launcher.u<oracle_user_id
e. cd into <PA install dir>/agents/StealthCollect/6.0/launch_conf
f. Edit launch_config.quest_sc_collector.<host-sid>.user file (backup first!) as follows:
-USER.ID oracle
-GROUP.ID oracle_user_group_name
Note.: In some cases, the launch_config.quest_sc_collector.<host-sid>.user file may not exist. So just skip this particular step and proceed with the next. The file will evenutally be created.
g.Save the file and close.
Note: If on the /agents directory, there is no write privileges, issue the following:
E.G.
chmod -R 775 /ora/quest/app/pa/qam/agents
3: log in with installing user and complete the PA installation
a.Start PA processes, /bin/quest_launcher_daemon start
b.Start PA installtion (run the LSI binary file)
c. Complete the installation.
-This time PA will not ask for the oracle user/password as it uses the oracle information from phase 2
-Running the LSI again will not override the files and permissions modified in phase 2 as those files are not in the LSI path
Note: If the <PA install dir>/agents/StealthCollect/6.0/<host-sid> has been created, and it installed completely on step 1, just run the installer and it should overwrite the binaries for the <host-sid>. Make sure you select 'New Install' when performing this step
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center