The installation will require three phases:
-
Log in with the installing user and start PA installation with non-DB2 OS user
-
Log in with DB2 OS user and run quest_launcher_user script
-
Log in with installing user and complete the PA installation
1. Start the installation with no DB2 OS user
-
Log in with installing user
-
Start PA installation (run the LSI binary file)
-
When the installation comes to the point where it asks for DB2 OS user, CTRL+C it.
-
Stop PA processes, by running <PA installation dir>/agents/bin/quest_launcher_daemon stop
-
Set WRITE permissions to all users to the <PA installation dir>/agents/bin/
2. Log in with DB2 OS user and run quest_launcher_user script
-
Log in with oracle user or DB2 OS user
-
cd into <PA installation directory>/agents/bin
-
Run quest_launcher_user script.
What the quest_launcher_user script does?
After running the script, two files should be created, with the DB2 OS user group and ownership:
-
_quest_launcher.u<DB2_OS_user_id>
- quest_launcher.g<DB2_OS_user_group_id>
Also, a PA config file will change according to the new user:
The file launch_config.quest_sc_collector.<host-sid>.user which is located under <PA install dir>/agents/StealthCollect/6.0/launch_conf will now show:
-
USER.ID DB2
-
DB2 user_group_name
3. Log in with installing user and complete the PA installation
-
Start PA processes, /agents/bin/quest_launcher_daemon start
-
Start PA installation (run the LSI binary file)
-
Complete the installation - this time no prompt for the DB2 OS user will be prompt for