Hotsos Application Workload Characterization Solution (HAWCS)

Frequently Asked Questions (FAQ)

Q: Will we have a separate database created for the HAWCS repository? Can we just create a schema in an existing 10g database to use as repository? Are there any drawbacks for doing it that way?

A: You do not need a separate database specifically for using HAWCS. HAWCS can share a database with other software. We have many customers who put the HAWCS repository in the same database as their OEM repository. However, HAWCS cannot be installed in the same database instance as your E-Business Suite. HAWCS does some pretty heavy calculations and summarizations that could adversely affect the performance of your EBS Suite if located in the same instance.

Q: The installation guide specifies a 20 GB table space to support HAWCS schema in the HAWCS repository. Is the size of the repository database expected to grow substantially as we continue to collect data? If so, are there any procedures to purge obsolete data?

A: Every Oracle EBS installation is different and produces different amounts of data based on the way it is used. We suggest that you start out with a 20 gigabyte tablespace that is set to AutoExtend and then closely monitor the growth for the first few months.

There are procedures to purge data from the repository on an ad hoc basis. The purge utility can be found in the Admin menu of HAWCS, and there is documentation about purging from the command line in the User Guide. Detailed data is automatically summarized into tables that are not erased in the purge processes, so summary data will always be kept.

Q: Can multiple target databases share the same repository? If so, do we have to re-run all of the scripts on the repository database for each target database?

A: You can indeed monitor multiple EBS instances with one HAWCS repository. Monitoring multiple EBS instances is a function of adding either a new database to an existing site, or alternatively adding a new site/database combination.

To add a new database to an existing site, refer to the section in the User Guide that discusses this topic.

To add a new site/database combination, refer to the User Guide that discusses "Adding a Site" and "Adding a Database".

Once the new database is created, the HAWCS data collection engine automatically collects data from the new instance on its next execution.

Q: We are only installing the data collector, not the presentation layer. How can we verify/test the data collection in this case? How do we review the data collected?

A: The best way to verify data collections is by running an .inspection log. and sending the output to The Hotsos support team will perform an analysis and promptly send a report on the condition of data collections.

An arrangement can also be made with Hotsos to export all the data collected by HAWCS and provide that data to Hotsos. It can then be loaded into an existing GUI shell for analysis by our Consulting group and display to you via the web.

Q: How often is data collected from the EBS database? Can I force HAWCS to collect data when I wish?

A: A data collection can be forced through either of two methods: there is an online utility that is accessed in the .Admin. tab of the HAWCS Application; or, a script is provided that can be run to accomplish the collection. Refer to the User Guide for details.


For more information, please write to or call +1.888.8HOTSOS.