If you are experiencing difficulty, have a question, or find an issue with ORtera software, please check the list of known issues at the bottom of this page to see if it's already listed and if there's a work-around. You may also look for an answer in the User Guide.

If you can't find a solution in the list of known issues or the User Guide, or if you have a more general question, please contact us for assistance.

• The Managed Host server software must run as root.
• When tens of thousands of files are being accessed during a monitoring session, processing the result may take very long time, as the filename reconstruction and mapping algorithm is ineffecient at handling such a large number of filenames.
• When tens of thousands of files are being accessed during a monitoring session, a Java 1.4.2 internal error may cause the JVM to exit. Upgrading to Java 5 solves this problem.
• The GUI (Compass) can get completely stuck when it can't communicate with the server, e.g., because the server is shut down or because of network problems. As a work-around, kill the Compass process and start a new one.
• On very busy systems, the user may experience a delay between scheduling a monitoring session and receiving confirmation that the monitoring session has been scheduled. One work-around, to continue scheduling more monitoring sessions, is to open a second Compass window. Occasionally the confirmation never appears although the monitoring session has been scheduled. To continue scheduling kill and restart Compass, or refresh that Compass window.
• Under very rare circumstances, for instance, when discovery analysis data is being saved at exactly the same time as the monitoring or heuristics analysis data for the same application or filesystem is being saved, one of the database operations (and hence the analysis phase it is part of) may fail. As a work-around, rerun the analysis job.