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, we do NOT recommend putting the HAWCS repository 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 500M 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: The installation guide mentions 500M as a suggested size. Every Oracle EBS installation is different and produces different amounts of data based on the way it is used. What we suggest is that you start out with a 500M table space that is set to AutoExtend and then closely monitor the growth for the first few months.
Starting with Version 2.1, 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 will also be documentation about purging from the command line in the User Guide. Detailed data is automatically summarized so data purging will not permanently erase the important summaries.

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, run the CREATE_DATABASE_REFERENCE.SQL script.

To add a new site/database combination, run the CREATE_SITE_REFERENCE.SQL script, then run the CREATE_DATABASE_REFERENCE.SQL script.

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: There are scripts to help verify and validate that the installation and collections are successful.

As part of the install, run the HAWCS_INSPECTION.SQL script and e-mail its contents to support@hotsos.com. This script is fairly cryptic in its output but we will help decipher it.

Other scripts that help determine if everything is set up properly are:

  • DISPLAY_COLLECTION_FLAGS.SQL - This script is run against the repository as the repository owner and displays the flags for all collecting statements for all databases so that the user can understand which are set for collection and which are not.
  • HAWCS_VERIFY_CONNECTIONS.SQL - This script is run against the repository as the repository owner to verify database link connections, verify that the grants on remote data sources are set correctly and that all indexes are in place, and then enables or disables collection against each data source dependent upon what the script finds.
  • TARGET_INSPECTION.SQL - This script is run against the EBS Target as the HOTSOS user and displays summary information about the HAWCS objects in the target EBS database. This script is only valid for versions 2.0.X and above.
To force a collection, log into the repository as the owner and run the RUN_HAWCS_COLLECTION.SQL script from the "register_target" folder. The script will prompt you to enter the Site ID and Database ID for the target from which you wish to collect.

Verify the collection attempt's success or failure by selecting from the HWC_COLL_ATTM table. Ensure that the column RUN_STATUS='C' (complete) and the column EXECUTION_STATUS='S' (success). The column ATT_ERROR will contain any error messages that may have occurred during the collection attempt.

Discussion Groups

Have a question about HAWCS? Hotsos discussion groups are your gateway for asking product usage questions, proposing new features, and inquiring about Hotsos HAWCS.

Information

For more information, please write to sales@hotsos.com or call +1.888.8HOTSOS.