-
Title
How to apply the HF-i in the Oracle Agent. -
Description
In this example, we will be implementing HF-i in the Oracle Agents VISDB-DEV and VISDB-PROD. -
Cause
This is applicable to Stat 6.2 HF-m (6.2.0.650) and Stat 6.3. HF-i (6.3.0.949) -
Resolution
1. Stop the Stat Oracle Agent(s). The environments are VISDB-PROD and VISDB-DEV.
2. Under the STAT_HOME/lib/ location, backup and delete the apache and quest folders.
3. Under the STAT_HOME/bin/ location, backup statctl.sh.
4. Unzip the stat_ora.zip into the STAT_HOME. This step should overwrite existing files with the updated ones.:
Place the stat_ora.zip in the OA environment. In this case It will be /home/applmgr/andreawork
Unzip the file onto the STAT_HOME using the -a parameter. E.g.: unzip -a stat_ora.zip -d /home/oracle/statagent63
5. Under the STAT_HOME/conf/ location, edit the stat.conf commenting all the 6 lines referencing the ENV.log.env. Like below:
6. Configure log4j2.xml under the STAT_HOME/conf location as required per environment. Refer to the Stat_6.3.0_Sys_Admin-HF-i | Appendix J. Follow the steps below:
Original: Log4j2.xml:
- Rename log4j2.xml to the name of the instance/environment. For example, if the name of the instance/environment is VISDB-PROD then re-name the log4j2.xml as VISDB-PROD.xml
- Parameters to be modified in the log4j2.xml: log-path and ENV. Replacing the log-path in the properties section with the entire path where the logs will be written, and the ENV with the instance name.
- In the case of running multiple environments, you must duplicate the log4j2.xml as many times as the number of instances. In the example below I have 2 instances: VISDB-PROD, and VISDB-DEV. The STAT_HOME/conf location should look like the below:
7. Restart the Oracle Agent(s). Make sure statctl.sh has write and execute permission.:
Under STAT_HOME/bin/: chmod 775 statctl.sh8. Verify that the Product Version is set to 6.2.0.650 or 6.3.0.949 looking for the message with the whole product number at the startup of the Oracle Agent. The Oracle Agent.log can be found in the PATH given in the log-path property-name section in the ENV.xml for the instance(s.).
-
Additional Information
Refer to How to enable DEBUG mode in the Oracle Agent (338922) for further information.